Re: [Pharo-dev] MC should really write snaphsot/source.st in UTF8

2013-05-23 Thread stephane ducasse
You know. I'm jealous. I'm jealous because I have to fight hard to concentrate and to get focused. So this is cool to see that some of you can. I have to handle so many tihngs that are still important to do… anyway keep get focused. Stef On May 23, 2013, at 4:19 PM, Henrik Sperre Johansen wro

Re: [Pharo-dev] MC should really write snaphsot/source.st in UTF8

2013-05-23 Thread Henrik Sperre Johansen
On 23.05.2013 12:52, Nicolas Cellier wrote: The snapshot/source.st does not contain a mix of ByteString and WideString because a single String is written during the process (all code is written into a String new writeStream which will make the String wide at first wide Charac

Re: [Pharo-dev] MC should really write snaphsot/source.st in UTF8

2013-05-23 Thread Nicolas Cellier
The snapshot/source.st does not contain a mix of ByteString and WideString because a single String is written during the process (all code is written into a String new writeStream which will make the String wide at first wide Character), so it should work. 2013/5/23 Henrik Sperre Johansen > On

Re: [Pharo-dev] MC should really write snaphsot/source.st in UTF8

2013-05-23 Thread Henrik Sperre Johansen
On 23.05.2013 00:06, Nicolas Cellier wrote: That sounds good. We could even try to fallback to UT-32 if we encounter zeros (but his should be very rare...). For write, ZipArchive are un-aware of any encoding... They use latin1. In Squeak, I could place some squeakToUTF8 sends in MCMczWriter, an

Re: [Pharo-dev] MC should really write snaphsot/source.st in UTF8

2013-05-22 Thread Stéphane Ducasse
+ 1000 :) On May 22, 2013, at 11:16 PM, Nicolas Cellier wrote: > First thing would be to simplify #setConverterForCode and > #selectTextConverterForCode. > Do we still want to use a MacRomanTextConverter, seriously? I'm not even sure > I've got that many files with that encoding on my Mac-OS

Re: [Pharo-dev] MC should really write snaphsot/source.st in UTF8

2013-05-22 Thread Nicolas Cellier
That sounds good. We could even try to fallback to UT-32 if we encounter zeros (but his should be very rare...). For write, ZipArchive are un-aware of any encoding... They use latin1. In Squeak, I could place some squeakToUTF8 sends in MCMczWriter, and equivalent UTF8TextConverter in Pharo #serial

Re: [Pharo-dev] MC should really write snaphsot/source.st in UTF8

2013-05-22 Thread Norbert Hartl
Am 22.05.2013 um 23:16 schrieb Nicolas Cellier : > First thing would be to simplify #setConverterForCode and > #selectTextConverterForCode. > Do we still want to use a MacRomanTextConverter, seriously? I'm not even sure > I've got that many files with that encoding on my Mac-OSX... > Do we re

Re: [Pharo-dev] MC should really write snaphsot/source.st in UTF8

2013-05-22 Thread Norbert Hartl
+1 Am 22.05.2013 um 22:57 schrieb Nicolas Cellier : > http://stackoverflow.com/questions/16645848/squeak-monticello-character-encoding > Let's kill this one, it's totally insane

Re: [Pharo-dev] MC should really write snaphsot/source.st in UTF8

2013-05-22 Thread Nicolas Cellier
First thing would be to simplify #setConverterForCode and #selectTextConverterForCode. Do we still want to use a MacRomanTextConverter, seriously? I'm not even sure I've got that many files with that encoding on my Mac-OSX... Do we really need to put a ByteOrderMark for UTF-8, seriously? See http:/

[Pharo-dev] MC should really write snaphsot/source.st in UTF8

2013-05-22 Thread Nicolas Cellier
http://stackoverflow.com/questions/16645848/squeak-monticello-character-encoding Let's kill this one, it's totally insane