<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Fun fact:</div><div>Having one “wide” character somewhere in one method or comment and </div><div>Filing out an mcz, the sources.st becomes a persisted WideString (utf16?)</div><div>And you won't know it...</div><div><br>Am 22.05.2013 um 23:16 schrieb Nicolas Cellier <<a href="mailto:nicolas.cellier.aka.nice@gmail.com">nicolas.cellier.aka.nice@gmail.com</a>>:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div>First thing would be to simplify #setConverterForCode and #selectTextConverterForCode.<br>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...<br>
</div><div>Do we really need to put a ByteOrderMark for UTF-8, seriously? See <a href="http://en.wikipedia.org/wiki/Byte_order_mark">http://en.wikipedia.org/wiki/Byte_order_mark</a>, 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.<br>
</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/5/22 Nicolas Cellier <span dir="ltr"><<a href="mailto:nicolas.cellier.aka.nice@gmail.com" target="_blank">nicolas.cellier.aka.nice@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><a href="http://stackoverflow.com/questions/16645848/squeak-monticello-character-encoding" target="_blank">http://stackoverflow.com/questions/16645848/squeak-monticello-character-encoding</a><br>
Let's kill this one, it's totally insane<br>
</div>
</blockquote></div><br></div>
</div></blockquote><blockquote type="cite"><div><span></span><br></div></blockquote></body></html>