Hi Hernán, Thanks for your file. I added as a test in XML-Parser. Cheers, Alexandre On 28 Mar 2010, at 14:47, Hernán Morales Durand wrote:
Hi Alex, Try with the attached XML file in your Pharo directory
XMLDOMParser parseDocumentFromFileNamed: (FileDirectory default fullNameFor: 'likelySubtags.xml')
however, it seems to be fixed in XML-Parser-JAAyer.72 Cheers,
Hernán
2010/3/27 Alexandre Bergel <alexandre@bergel.eu>:
Can you send me the file please?
Alexandre
On 27 Mar 2010, at 12:47, Fabrizio Perin wrote:
Hi Alex, thanks for your effort. Actually the problem was related exactly to the readStream, my method to import the XML files uses the class FileStream, instead now it use StandardReadStream and everything works fine. All Tests where green in my image too (including your new test) but the error still raises trying to import from a file. So i investigate in the direction of the readStream from a file and i found the solution. I'm still not sure which is the problem using FileStream instead StandardFileStream.
Thanks a lot,
Fabrizio
2010/3/26 Alexandre Bergel <alexandre@bergel.eu> Hi Fabrizo,
I think you're in the right place to talk about that.
I haven't been able to reproduce your error. I added a test:
XMLParserTest>>testNonUTF8Characters
self shouldnt: [XMLDOMParser parseDocumentFrom: '<foo>Bean BLABLABLA Eidgenössisches Institut für BLABLALBLA</foo>' readStream] raise: Error.
It goes green in my image. Do you have a different way to get the readStream from the String?
Cheers, Alexandre
On 26 Mar 2010, at 12:14, Fabrizio Perin wrote:
Hi, I was parsing an XML File with the last version of XML Parser (XML-Parser-JAAyer.68) and i get an error related to a not UTF-8 character that the parser found into the document. The XML document contains some german character:
<![CDATA[SES: Bean BLABLABLA Eidgenössisches Institut für BLABLALBLA]]>
Actually i'm not sure if the error is which is in the UTF8TextConverter or something is wrong in the invokation from the parser. Anyway i parse several time the same document with older versions of the XML-Parser (XML-Parser-JAAyer.57) and it always works well. I'm not sure if the mailing list of Pharo is the right place to report this problem in the case i'm i'm sorry.
Here the trace from the log:
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. <likelySubtags.zip>_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.