I'm writing an extension that will let our users use markdown to apply particular styles as wrapper divs, without making them learn how to properly open and close div tags.
So, I thought that using HTML comments would be a good idea, since, if you don't have our CSS running, the extension would simply output valid code without littering it with useless, formatting-only stuff.
Essentially, I have stuff like this:
<!-- naz:showhide -->
## Headline ##
### Subhead ###
Showhide body copy lorem ipsum
### Subhead ###
More body copy dolor sit amet
<!-- /naz:showhide -->
My preprocessor basically says 'if the line is <!-- naz:showhide -->, replace it with <div class="showhide">'.
In 2.0.3, I could do this with basic string operations, but in the trunk, the comments are stored in the "lines" list as some sort of weird string, and they're no longer matching. For example, "<!-- naz:showhide -->" is "\x02wzxhzdk:0\x03" by the time it gets to my extension.
I tried to dig through the commit logs to see where this changed, but came up empty.
Any suggestions of what to try next?
Thanks!
====================================
Steven L Smith, Web Developer
Department of Information Technology Services
Nazareth College of Rochester
585-389-2085 | ssm...@na... | KC2YTC
http://www.naz.edu/pub/~ssmith46
====================================
|
