> On 27 Jul 2018, at 15:25, Sven Van Caekenberghe wrote:
>
> Right, but that guess is wrong (check the resulting string).
Actually, the encoding used is GBK,
https://en.wikipedia.org/wiki/GBK_(character_encoding)
This is a variable length encoding used in China. It is not currently
> On 27 Jul 2018, at 13:58, Ben Coman wrote:
>
> On 27 July 2018 at 18:39, Offray Vladimir Luna Cárdenas
> wrote:
>> Hi,
>>
>> I was ready to show a friend the Pharo web capabilities with the
>> classical "myString asUrl retrieveContents", but the friend gave me a
>> url that contains non
On 27 July 2018 at 18:39, Offray Vladimir Luna Cárdenas
wrote:
> Hi,
>
> I was ready to show a friend the Pharo web capabilities with the
> classical "myString asUrl retrieveContents", but the friend gave me a
> url that contains non Latin characters[1] and then I got an
> ZnInvalidUTF8 error.
>
Hi Offray,
> On 27 Jul 2018, at 12:39, Offray Vladimir Luna Cárdenas
> wrote:
>
> Hi,
>
> I was ready to show a friend the Pharo web capabilities with the
> classical "myString asUrl retrieveContents", but the friend gave me a
> url that contains non Latin characters[1] and then I got an
>
Offray Vladimir Luna Cárdenas wrote on 27. 7. 2018 12:39:
Hi,
I was ready to show a friend the Pharo web capabilities with the
classical "myString asUrl retrieveContents", but the friend gave me a
url that contains non Latin characters[1] and then I got an
ZnInvalidUTF8 error.
[1]
Hi,
I was ready to show a friend the Pharo web capabilities with the
classical "myString asUrl retrieveContents", but the friend gave me a
url that contains non Latin characters[1] and then I got an
ZnInvalidUTF8 error.
[1]
