Re: Internationalization and msxml
From: Developer (wanderer_at_mapinfo.nope.com)
Date: 08/03/04
- Next message: Daniel Bass: "Re: SelectNodes"
- Previous message: Developer: "Re: Internationalization and msxml"
- In reply to: Developer: "Re: Internationalization and msxml"
- Next in thread: Kevin Yu [MSFT]: "Re: Internationalization and msxml"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 3 Aug 2004 08:58:27 -0400
I was just told by one of our developers that the Java XML parsers don't
read the file, either.
"Developer" <wanderer@mapinfo.nope.com> wrote in message
news:%23y35VjVeEHA.3792@TK2MSFTNGP09.phx.gbl...
> Hello, Kevin,
>
> The client is running on Japanese Windows, connecting to a Japanese
server.
> Via HTTP, we prefer to use POST, but some servers only work with GET. In
> either case, we write the returned stream to a file.
> The header on the returned xml says it is UTF-8.
> We create a SaxReader, give it a content handler and an error handler, and
> call ISAXXMLReader->parseURL(filename). I can watch the startElement()
and
> endElement() methods as the file is read until the
> ISAXErrorHandler::fatalError() method is called with the error message "A
> name contained an invalid character".
>
> Internet Explorer displays the file correctly as a mix of English and
> single- and multi-byte Japanese characters. However, Mozilla FireFox and
> Opera 7.x browsers both indicate a problem with the xml -- "not well
> formed".
>
> The XmlDocument in my test app gives the error:
> Exception: System.Xml.XmlException: The '?' character, hexadecimal value
> 0xFF7A,
> cannot be included in a name. Line 15, position 15.
>
> As for the code that parses the file, it is a simple implementation of the
> ISAXXMLReader interface. In the startElement(), characters(), and
> endElement() methods the code simply writes the localName or characters to
> the console.
>
> Let me know what other information you need. I would be glad to send you
> the sample project(s), as well as the troublesome XML.
>
> Thanks for your help.
>
> "Kevin Yu [MSFT]" <v-kevy@online.microsoft.com> wrote in message
> news:NqQ4IuReEHA.1928@cpmsftngxa10.phx.gbl...
> > Hi Developer,
> >
> > First of all, I would like to confirm my understanding of your issue.
From
> > your description, I understand that you are having trouble parsing an
Xml
> > document both with SAX and XmlDocument. If there is any
misunderstanding,
> > please feel free to let me know.
> >
> > Based on my research, this might be an encoding issue. Could you please
> let
> > me know, how the Xml was gained and how it was parsed? Because we need
to
> > know the format that Xml is saved in. Have you tried to open it in IE?
If
> > yes, can you see the encoding mode of that file? If it can be opened by
IE
> > successfully, could you show me the code that you're using to parse the
> > file in .NET?
> >
> > If anything is unclear, please feel free to reply to the post.
> >
> > Kevin Yu
> > =======
> > "This posting is provided "AS IS" with no warranties, and confers no
> > rights."
> >
>
>
- Next message: Daniel Bass: "Re: SelectNodes"
- Previous message: Developer: "Re: Internationalization and msxml"
- In reply to: Developer: "Re: Internationalization and msxml"
- Next in thread: Kevin Yu [MSFT]: "Re: Internationalization and msxml"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
