Interesting thing about IE5, anyone else seen it...

[Craig Hohlbein <CraigH@xxxxxxxxxxxxx>]

I'm not really sure if this should come up here, in XSL, but it has
happened while we're trying to do some stylesheet work and I'm wondering
if anyone else has seen it and has developed a workaround.

We have what you might call a repository of XML files, and at one point,
using IE5 and data entry forms, we allow the user to pull the XML file
out of our repository and apply any stylesheets that might be associated
with the XML file.  How we associate stylesheets with the files isn't
really of importance, but doing so shows that it can be done(referring
to a thread of e-mails concerning such a matter a little bit ago).  When
the user chooses to view the file, we, through an procedure of calls,
create a stream that MSXML accepts.  The stream initializes MSXML, and
then we call API calls such as IXMLElement2::GettagName to retrieve the
information we need.

Here lies the problem, which is in Microsoft's Knowledge Base with no
solution.  MSXML sends back the tag names in all UPPERCASE letters, so
if the tag names were originally in mixed case or lowercase letters, and
the stylesheet is based upon that, it doesn't work due to case
sensitivity.  Now, you could say that you have to build stylesheets that
check for all the possible cases, or build them to only do uppercase
letters, but the stylesheets are also used elsewhere and that's not
really a viable solution.  We are not using DOM for this yet, mainly
just the Element2 to allow for IE4 users.  If switching over to DOM will
fix the problems, then that's a viable solution, but I was wondering if
there were any others.

So, has anyone else run into this problem?  And if so, have you come up
with any solutions?

Sorry for the length of the e-mail.

Thanks for the help.

Craig Hohlbein
Software Engineer
e: craigh@xxxxxxxxxxxxx


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list