> On 29 Jul 2016, at 00:15, monty <mon...@programmer.net> wrote:
> 
> Good for finding one of the fixes, but please use #parseURL:/#onURL: instead 
> of #asUrl/#asZnUrl with #retrieveContents, because that will result in Zinc 
> eagerly decoding the response without looking at the <?xml ?> declaration as 
> the XML spec requires.
> 
> #parseURL:/#onURL: use Zinc correctly, doing their own XML-aware encoding on 
> top of it.

Yes, you are right. Thanks for implementing all this logic, I known it is quite 
complicated and tricky.

>> Sent: Thursday, July 28, 2016 at 5:29 PM
>> From: "Sven Van Caekenberghe" <s...@stfx.eu>
>> To: "Any question about pharo is welcome" <pharo-users@lists.pharo.org>
>> Subject: Re: [Pharo-users] XMLParser Claims U+00A0 is “Invalid UTF-8”
>> 
>> In my older work image, the following just works:
>> 
>> XMLDOMParser parse:
>> ('http://forum.world.st/file/n4908531/illegal-UTF-sms.xml' asUrl 
>> retrieveContents).
>> 
>> But I guess that is because my (older) XML parser version ignores the 
>> encoding, or is more lenient.
>> 
>> You could try to edit the incoming file, or have a look at 
>> #decodesCharacters: 
>> 
>> (XMLDOMParser on:
>> ('http://forum.world.st/file/n4908531/illegal-UTF-sms.xml' asUrl 
>> retrieveContents) readStream) decodesCharacters: false; parseDocument.
>> 
>> But I am no expert in the deeper aspects of XML Support.
>> 
>>> On 28 Jul 2016, at 22:29, Sean P. DeNigris <s...@clipperadams.com> wrote:
>>> 
>>> Sven Van Caekenberghe-2 wrote
>>>> Your XML file is not UTF-8 encoded, it is plain Unicode. At least the way
>>>> it is served from the URL you gave.
>>>> ..
>>>> You see ?
>>> 
>>> Unfortunately, no! ha ha. I didn't generate the file and I took it's
>>> assertion that it was UTF-8 at face value. How do I properly feed the file
>>> into XMLParser?
>>> 
>>> 
>>> 
>>> -----
>>> Cheers,
>>> Sean
>>> --
>>> View this message in context: 
>>> http://forum.world.st/XMLParser-Claims-U-00A0-is-Invalid-UTF-8-tp4908525p4908539.html
>>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
>>> 
>> 
>> 
>> 
> 


Reply via email to