<div dir="ltr"><br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Nicolas Cellier</b> <span dir="ltr"><<a href="mailto:nicolas.cellier.aka.nice@gmail.com">nicolas.cellier.aka.nice@gmail.com</a>></span><br>
Date: 2013/5/23<br>Subject: Re: [Pharo-dev] MC should really write snaphsot/<a href="http://source.st">source.st</a> in UTF8<br>To: Discusses Development of Pharo <<a href="mailto:pharo-dev@lists.pharo.org">pharo-dev@lists.pharo.org</a>><br>
<br><br><div dir="ltr"><div>That sounds good. We could even try to fallback to UT-32 if we encounter zeros (but his should be very rare...).<br><br></div>For write, ZipArchive are un-aware of any encoding... They use latin1.<br>
<div>
In Squeak, I could place some squeakToUTF8 sends in MCMczWriter, and equivalent UTF8TextConverter in Pharo #serializeDefinitions:, maybe this is needed in some other serialize* (version, dependencies who knows...)<br></div>
<div><br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">2013/5/22 Norbert Hartl <span dir="ltr"><<a href="mailto:norbert@hartl.name" target="_blank">norbert@hartl.name</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto"><div><br></div><div><br>Am 22.05.2013 um 23:16 schrieb Nicolas Cellier <<a href="mailto:nicolas.cellier.aka.nice@gmail.com" target="_blank">nicolas.cellier.aka.nice@gmail.com</a>>:<br><br></div><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" target="_blank">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></blockquote><div><br></div></div>A BOM for utf-8 does not make sense. It could act as a switch between legacy encoding and utf-8. But it would also be a decision that will be regretted shortly after. Most files in monticello are 7bit so there wouldn't be a problem changing the default encoding. For every other file an exception will be thrown. So reading utf-8 and on exception reading the same thing in legacy might be a way to go. <span><font color="#888888"><div>
<br></div></font></span><div><span><font color="#888888">Norbert</font></span><div><br><blockquote type="cite"><div><div dir="ltr"><div>
</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></div></div></div></blockquote></div><br></div>
</div></div></div><br></div>