<div dir="ltr">Yes, this is the easy part, I was speaking of how the hell we can write a 32bits Word-oriented collection into a Byte-oriented stream and magically end up with ut-32be ;)<br></div><div class="gmail_extra"><br>
<br><div class="gmail_quote">2013/5/23 Tobias Pape <span dir="ltr"><<a href="mailto:Das.Linux@gmx.de" target="_blank">Das.Linux@gmx.de</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 23.05.2013 um 00:11 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 class="im">
<blockquote type="cite"><div><div dir="ltr">Yes, it's UTF-32BE, see SO post. And you get a bonus point if you can find by what magic this happens without tracing in a Debugger ;)<br></div></div></blockquote><div><br></div>
</div><div>That one might be easy, as it bit me several times.</div><div>First, the stream that is uses for <a href="http://sources.st" target="_blank">sources.st</a> is backed by a simple ByteString, but</div><div>during the writing of the definitions, comments, etc, once you hit a method with a wide</div>
<div>Character, its source is a WideString, and putting that onto the stream makes</div><div>the underlying string #become a WideString, too. Which will then be written us g utf32be (as i just learned).</div><div class="im">
<div><br></div><blockquote type="cite"><div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/5/23 Tobias Pape <span dir="ltr"><<a href="mailto:Das.Linux@gmx.de" target="_blank">Das.Linux@gmx.de</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>Fun fact:</div><div>Having one “wide” character somewhere in one method or comment and </div><div>
Filing out an mcz, the <a href="http://sources.st" target="_blank">sources.st</a> becomes a persisted WideString (utf16?)</div><div>And you won't know it...</div><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><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 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></div></div></div><br><br>
<br></blockquote></div><br></div>
</div></blockquote><blockquote type="cite"><div><span></span><br></div></blockquote></div></div><br><br>
<br></blockquote></div><br></div>