Hi Richard,
At 10:01 AM 6/24/2003 +0200, you wrote:
Hi Mark, Jake,
On Monday 23 June 2003 22:36, Jacob Kjome wrote:
> Just pinging the list about a conversation I had with David Li about
making
> XMLC output HTML in lower case. HTML tags are not case
sensitive, but
> XHTML is (because it is XML compliant). Now, the reason why
having XMLC
> output tags in all upper case is kind of annoying (besides the
ugliness of
> all upper case) is for things like XPath which, being an application
of
> XML, is also case sensitive. If I write an XPath _expression_,
it will only
> work on HTML and not XHTML or vice-versa, but not both.
I'm all for it. Maybe make this configurable in the output options and
have it
default to upper case so we don't break any existing apps.
Cool, yes, it should probably be configurable.
On Tuesday 24 June
2003 01:42, Mark Diekhans wrote:
> The string written for a tag is not actually under XMLC's
control. It uses
> the name returned by Element.getTagName().
Well, that's only part of the truth :-) XMLC still prints the tag name
and can
just as well convert it to lower case first.
This is one are where I am not completely comfortable with making
a change. I'm not sure all the places that would have to be
modified to make this possible. Do you have time to do
this? Also, if we are to do this, would this solve the original
problem of the case-sensitivity of XPath? That is, would the DOM
actually be stored in lower case so that XPath can search through the
html dom in lower case or would this only change the printing output of
the html DOM? If only the latter, then the change is probably not
worth the effort, but if the former, then this change would be very, very
nice to have.
Jake
--
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
| 