Fun fact:
Having one “wide” character somewhere in one method or comment and 
Filing out an mcz, the sources.st becomes a persisted WideString (utf16?)
And you won't know it...

Am 22.05.2013 um 23:16 schrieb Nicolas Cellier <nicolas.cellier.aka.nice at gmail.com>:

> 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://en.wikipedia.org/wiki/Byte_order_mark, it's valueless, and not recommended. It were a Squeak way to specify that a Squeak source file would use UTF-8 rather than MacRoman, but now this should be obsolescent.
> 
> 
> 2013/5/22 Nicolas Cellier <nicolas.cellier.aka.nice at gmail.com>
>> http://stackoverflow.com/questions/16645848/squeak-monticello-character-encoding
>> Let's kill this one, it's totally insane
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20130523/d663ec6e/attachment.htm