<div dir="ltr">Yes, it's a small change<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/7/30 Bert Freudenberg <span dir="ltr"><<a href="mailto:bert@freudenbergs.de" target="_blank">bert@freudenbergs.de</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">FWIW, the server image is a Squeak 3.11alpha image #8824 with Monticello-bf.356. I'm afraid simply loading a current MC version is not going to work, but maybe the utf8 changes could be backported?<span class="HOEnZb"><font color="#888888"><div>
<br></div><div>- Bert -</div></font></span><div><div class="h5"><div><br><div><div>On 30.07.2013, at 22:26, Nicolas Cellier <<a href="mailto:nicolas.cellier.aka.nice@gmail.com" target="_blank">nicolas.cellier.aka.nice@gmail.com</a>> wrote:</div>
<br><blockquote type="cite"><div dir="ltr"><div><div>To me, the server should try and read in utf8, then fallback to old encoding like current trunk does.<br></div>Then, whether it should continue to write with old encoding or utf8 is a question of how we want to support serving older images.<br>
</div>Would it be possible to provide a hackish transition: create mcd with same encoding as mcz?<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/7/30 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"><div><div><div><div><div><div>A possible scenario:<br></div>For some reason (?) the snapshot.bin fails. In that case, the server used the sources in .st format.<br>
</div>But newly produced sources are in utf8 and the server is probably not utf8 aware...<br>
</div>In which case the server re-interprets bad characters for building the .mcd and put them in patch.bin stone<br></div>Makes sense?<br><br></div>Is it possible to backport the utf8 correction to the server ?<br></div>
I mean, is it going to cause forward compatibility problems ?<br><div><br><br></div></div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/7/30 Bert Freudenberg <span dir="ltr"><<a href="mailto:bert@freudenbergs.de" target="_blank">bert@freudenbergs.de</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>If the MCZ works and the MCD does not, then whatever fix we make needs to be applied to our squeaksource server image, which generates the MCDs.</div>
<span><font color="#888888"><div><br></div><span style="font-family:Helvetica;font-size:12px">- Bert -</span></font></span><div><font face="Helvetica"><br></font><div><div>On 2013-07-30, at 14:59, Nicolas Cellier <<a href="mailto:nicolas.cellier.aka.nice@gmail.com" target="_blank">nicolas.cellier.aka.nice@gmail.com</a>> wrote:</div>
<br><blockquote type="cite"><div dir="ltr"><div><div><div>I tried to debug late at night and it seems to come from the patch.bin member of a .mcd<br></div>I'm not an expert of MC and I do not really know when a .mcd is used vs a .mcz, nor how this binary member is created.<br>
But presumably, there is an extra or missing utf8 conversion in some path...<br>I had to stop to get some sleep...<br></div>I suggest we keep trying a couple of days and solve the problem while under our hands.<br><br></div>
<div>Nicolas<br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/7/30 Frank Shearar <span dir="ltr"><<a href="mailto:frank.shearar@gmail.com" target="_blank">frank.shearar@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 30 July 2013 02:17, Nicolas Cellier<br>
<div><<a href="mailto:nicolas.cellier.aka.nice@gmail.com" target="_blank">nicolas.cellier.aka.nice@gmail.com</a>> wrote:<br>
> Hmm it looks like some UTF8 mess<br>
> I did only change Base64MimeConverter... Did I break it?<br>
<br>
</div>Yep, I'm afraid so. When it loads it throws a SyntaxError:<br>
<div><br>
asCharacter<br>
"Answer the receiver's first character, or '*' if none.<br>
Idiosyncratic, provisional."<br>
<br>
</div>^ self size > 0 ifTrue: [self first] ifFalse:[$·Argument expected ->]<br>
<br>
Is that supposed to be a middle dot just before "Argument" ? Note how<br>
the original source doesn't show the A-with-caret.<br>
<span><font color="#888888"><br>
frank<br>
</font></span><div><br>
> 2013/7/30 <<a href="mailto:commits@source.squeak.org" target="_blank">commits@source.squeak.org</a>><br>
><br>
>> Nicolas Cellier uploaded a new version of Collections to project The<br>
>> Trunk:<br>
>> <a href="http://source.squeak.org/trunk/Collections-nice.527.mcz" target="_blank">http://source.squeak.org/trunk/Collections-nice.527.mcz</a><br>
>><br>
>> ==================== Summary ====================<br>
>><br>
>> Name: Collections-nice.527<br>
>> Author: nice<br>
>> Time: 30 July 2013, 2:13:07.506 am<br>
>> UUID: 17e38fb5-76dd-499b-aa6d-bfe07045c28d<br>
>> Ancestors: Collections-fbs.526<br>
>><br>
>> Simplify Base64MimeConverter class initialization with Character>>to:<br>
>><br>
>> =============== Diff against Collections-fbs.526 ===============<br></div></blockquote></div></div></blockquote></div></div></div></blockquote></div></div></div></div></blockquote></div></div></blockquote></div>
<div><span style="border-spacing:0px 0px;text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:12px;white-space:normal;font-family:Lucida Grande;word-spacing:0px"><br>
</span>
</div>
<br></div></div></div></div><br><br>
<br></blockquote></div><br></div>