xerces-c-110 parsing: newline problem

[michael gaida <mi...@firemail.de>]

I don't get DOMParser parse files. Starting the DOMPrint 
or the SAXPrint sample (on Win32 build with BCB4.0) I get 
the exception:

(DOMPrint)
Fatal Error at file "h:\s02.xml", line 1, column 45
   Message:
<?xml version='1.0' encoding='ISO-8859-1' ?>

(SAXPrint)
Fatal Error at (file h:\s02.xml, line 1, char 45):

s02.xml was made with the joe editor on linux so it should 
use ISO-8859-1 encoding (I think so). It looks like 
something goes wrong with the line break (char 45) while
parsing.


I don't think this is a big problem, but I simply don't 
get it. 

Could anybody tell me where I can find documentation 
about io, encoding or handling newlines esp. with the 
xercess parser? I have already read the faq.


Thanks

Michael Gaida


___________________________________________________________
http://www.firemail.de - Ihr Briefkasten im Web. Einfach, schnell, sicher.
Neu! Jetzt auch mit kostenlosem Fax-Empfang und Voicemail!

Re: xerces-c-110 parsing: newline problem

[Andy Heninger <he...@us.ibm.com>]

Things to try to narrow this problem down -

o   Do the prebuilt versions of DOMPrint and SAXPrint work on
    your system, running with the prebuilt xerces DLL and the
    personal.xml sample file?

o   Will the prebuilt xerces + samples parse your s02.xml file?

o   Will your build of xerces + samples parse the personal.xml
    test file?

This should be enough to tell whether the problem is with your xml file, or
with your build, or something else with your environment.  ISO-8859-1
encoding should be fine.

XML new-line handling is described in the XML specification at
http://www.w3.org/TR/REC-xml#sec-line-ends  XML files can use
any of the common new-line conventions - LF only, CR/LF, or CR only.

  -- Andy



> (DOMPrint)
> Fatal Error at file "h:\s02.xml", line 1, column 45
>    Message:
> <?xml version='1.0' encoding='ISO-8859-1' ?>
>
> (SAXPrint)
> Fatal Error at (file h:\s02.xml, line 1, char 45):
>
> s02.xml was made with the joe editor on linux so it should
> use ISO-8859-1 encoding (I think so). It looks like
> something goes wrong with the line break (char 45) while
> parsing.
>
>
> I don't think this is a big problem, but I simply don't
> get it.
>