Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Conformance problem in MSXML
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Aung Aung  
View profile  
 More options Aug 2 2001, 6:57 pm
Newsgroups: microsoft.public.xml.msxml-webrelease
From: xmlfeedbac...@microsoft.com (Aung Aung)
Date: Thu, 02 Aug 2001 22:55:30 GMT
Local: Thurs, Aug 2 2001 6:55 pm
Subject: Re: Conformance problem in MSXML

No, IE does not reject perfectly valid character.

The problem only happens if one uses IE as xml parser.
The habbit of using IE as XML paraser is just wrong. First IE does not XML
validate (dtd or schema). IE just display content and data, the fact that
IE was build in to parse XML is a side effect. One should always parser the
data before pushing to IE to display.

So, if you parse the XML and display it in an IE <div> or <textarea> all
character will be displayed as long as IE take it.

-Aung

--------------------

> From: "Julian F. Reschke" <julian.resc...@nospam-greenbytes.de>
> References: <#ded#qpFBHA.2056@tkmsftngp05>

<bJLu35uFBHA....@cppssbbsa01.microsoft.com> <ensxouyFBHA.1364@tkmsftngp05>
<v5dQNMVGBHA....@cppssbbsa01.microsoft.com> <eJcZl2YGBHA.436@tkmsftngp05>
<eUwwL5bGBHA.1408@tkmsftngp03> <PNrJsjsGBHA....@cppssbbsa01.microsoft.com>
<#JZ8H3zGBHA.1740@tkmsftngp03>
> Subject: Re: Conformance problem in MSXML
> Date: Thu, 2 Aug 2001 13:05:33 +0200
> Lines: 53
> X-Priority: 3
> X-MSMail-Priority: Normal
> X-Newsreader: Microsoft Outlook Express 5.50.4522.1200
> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
> Message-ID: <uAUfQM0GBHA.1852@tkmsftngp07>
> Newsgroups: microsoft.public.xml.msxml-webrelease
> NNTP-Posting-Host: mail.greenbytes.de 217.5.201.10
> Path: cppssbbsa01.microsoft.com!tkmsftngp01!tkmsftngp07
> Xref: cppssbbsa01.microsoft.com

microsoft.public.xml.msxml-webrelease:12934
> X-Tomcat-NG: microsoft.public.xml.msxml-webrelease

> I have some sympathy for Microsoft (ine IE's XML) not willing to break
> documents that used to work with earlier MSXML versions, but what's the
> point it rejecting perfectly valid characters???

> "David Carlisle" <dav...@nag.co.uk> schrieb im Newsbeitrag
> news:#JZ8H3zGBHA.1740@tkmsftngp03...

> > "Aung Aung" <xmlfeedbac...@microsoft.com> wrote in message
> > news:PNrJsjsGBHA.181@cppssbbsa01.microsoft.com...

> > > Yes, that's the same issue.
> > > IE is using an older parser (for backward app competibility issue, we
> > > cannot change this) for XML, which incorrectly parse character in
> > following
> > > way. It will wrongly accept invalid char less than #x20, and wrongly
> > reject
> > > valid char hight than #x10000.

> > > So, do not use IE mimeViewer to do parsing and Please parser your data
> > > before pusing to IE.

> > > Thanks,
> > > -Aung

> > No, I am sorry but this is completely utterly broken.

> > The idea of XML is and was "SGML for the web" we need to serve XML files
> > that contain the semantic content we wish to express. In the case of
> MathML
> > this will involve a large number of plane 1 characters. Asian character
> sets
> > will have similar issues, as they will also use the new plane 1
additions
> in
> > Unicode 3.1.

> > A solution that requires every XML file being served has a wrapper HTML
> file
> > which calls a vendor specific parser is no solution at all. I understand
> > that msxml-webrelease isn't the right forum to discus this, but what is
> the
> > right forum?

> > David Carlisle

> > Co Editor W3C MathML 2 Recommendation (but speaking for myself, not for
> the
> > working group)


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.