Brion wants it changed to not allow \' and \"
as escapes for ' and "
inside quoted strings and to not allow whitespace between the opening
< and the name of the tag.
Brion,
I read this comment on the bugzilla. Whilst I agree that """
should be supported I am a little unsure what is wrong with supporting
the \" syntax?
Personally I dont do a lot of web development and my first instinct
would have been to reach for \" to put quotes within quotes. Surely the
goal is to have a syntax which is understandable to the general public?
Lets be clear though. Are we talking about stuff like the following:
<gallery caption="Ed said: \"Here is my gallery\"">
Which you think should *only* be allowed as:
<gallery caption="Ed said: "Here is my gallery"">
The former doesn't feel "inconsistent" to me? (But I am not a hardcore
web worker)
Can we not compromise and offer both syntax? Either way it seems like a
small detail which is holding back an otherwise very useful patch that
seems quite low risk. Eyeballing the patch it looks fairly
selfcontained, although my first thought is that we only need the one
tag parsing function, params would simply be null if there weren't any
params?
Brion: I don't want to run cvs based code on my website, and neither do
I want to maintain two versions of a patch. What do we realistically
need to do to get this finished off? Making it patch against head is
probably trivial, and whilst I would prefer the escaped quotes above it
doesn't seem to be a show stopper either way around?
Hoping that we might get such an easy patch moving and into 1.5 for release?
Thanks and good luck
Ed W