|
|
Re: ': msg#00035
java.enhydra.xmlc
Ah....., ok, look at this....
http://www.w3.org/TR/xhtml1/#guidelines
C.16. The Named Character Reference
'The named character reference '
(the apostrophe, U+0027) was introduced in XML 1.0 but does not appear in
HTML. Authors should therefore use ' instead of ' to
work as expected in HTML 4 user agents.
So, that is why IE is dying. It probably just doesn't understand
the entity reference. See if ' works better.
Jake
At 12:48 PM 4/7/2003 -0500, you wrote:
I believe double quotes are
mandatory for XML and, hence, XHTML. I understand that there are
people who write HTML with attributes such as...
id=blah
or
id='blah'
I would argue that both should be changed to the following whether it is
XML, XHTML, HTML, or any *ML...
id="blah"
I'm not sure how enforceable this is, though? Would it break some
peoples existing markup? Maybe, but if we were just strict about
it, and stated this fact in the Readme file, I think it would make things
be easier all around.
Jake
At 06:36 PM 4/7/2003 +0200, you wrote:
On Monday 07 April 2003 18:21,
Jacob Kjome wrote:
> Actually, double quotes are at issue they are used to enclose
attribute
> values. I never said that double quotes shouldn't be escaped;
they
> absolutely should! Single quotes don't have the same issues
that double
> quotes do. How would leaving single quotes alone but escaping
double
> quotes break anything?
I may misremember, but I think there's an option in XMLC to switch
between
single and double quotes for quoting attribute values (both are legal),
and
if you're using single quotes for attribute values, you get problems when
not
escaping them.
That said, its probably sensible to escape only the
"problematic" quotes (i.e.
the ones that are used for quoting attributes on that particular output)
and
leave the other variety unescaped...
--
Richard Kunze
[ t]ivano Software, Bahnhofstr. 18, 63263 Neu-Isenburg
Tel.: +49 6102 80 99 07 - 0, Fax.: +49 6102 80 99 07 - 1
http://www.tivano.de,
kunze@xxxxxxxxx
| |
