[Seaside-dev] 2.9a3 encoding broken?
Sebastian Sastre
ssastre at seaswork.com
Mon Mar 23 11:54:19 UTC 2009
to discard basic problems, I've loaded a 2.9a3 in a pharo 259.
Same issue.
Using WABrowser you can't see diacritics in a method with a string which shows
diacritics in the squeak class browser properly.
With a 2.9a2 it works just fine in both.
I'll try to take a look at the code changes about encoding between versions
Any pointer appreciated,
sebastian
> -----Mensaje original-----
> De: seaside-dev-bounces at lists.squeakfoundation.org
> [mailto:seaside-dev-bounces at lists.squeakfoundation.org] En
> nombre de Sebastian Sastre
> Enviado el: Saturday, March 21, 2009 15:09
> Para: 'Seaside - developer list'
> Asunto: [Seaside-dev] 2.9a3 encoding broken?
>
> hi there,
> is the encoding broken for 2.9a3?
> I've migrated and found problems about diacritics.
> After seeing that I've went to the WAEncodingFunctionalTest.
> It works for the
> heading but does not for the text. When uses
> #renderCharacterByCharacter:
> diacritics are broken
> I'm missing something?
> sebastian
>
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
More information about the seaside-dev
mailing list