Hey,
Although the tag name issue is a valid point, it has nothing to do with my
original email. So please start a separate discussion rather then hijacking
this thread.
Cheers
--
Jeroen De Dauw
http://blog.bn2vs.com
Don't panic. Don't be evil.
--
On 13 January 2011 03:19, Daniel Friesen <lists(a)nadir-seen-fire.com> wrote:
<tag name>...</tag name>
Definitely sounds like something we shouldn't support. That kind of
thing just screams "you're at the mercy of whatever developer in the
future decides to change the parser to 'actually' parse out xml tags
with more xml or html-like parsing, instead of simply doing a search and
replace based on a list of tag names".
Not to mention it's confusing and counterintuitive in articles
themselves. What if the <display> tag actually supported a map argument?
<display map foo> gets treated as a <display map> tag, but <display foo
map> gets properly treated as a <display> tag? bleeeeech... And I have
to feel sorry for the users that actually understand any small level of
xml or html that are looking at <display map> in a random page and
reading that as a tag with the tagName 'display'.
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [
http://daniel.friesen.name]