On 2010-03-28, at 10:02 AM, Stéphane Ducasse wrote: > >> You should ask Sophie team, their knowledge certainly is far more >> advanced than mine. > > The problem is that most of them disappeared after the java rewrite announce.
Ok, well it's not as if we disappeared from the planet... The UTF8 work came out of work done on the OLPC/eToys, check with Bert You need to carefully check that some of the UTF8 encoders/decoder methods, or classes actually DO make UTF8 One of them lied and did a UTF8ToMacRoman or was that UTF8ToLatin1 conversion when it claimed a UTF8ToUnicode32. In Sophie because we wrote it's own storage subsystem we could ensure that all textual data going to storage was UTF8, and all text coming in was UTF8->WideStrings. Also all references to external resources were made into URI that were UTF8 and http encoded safe. Mind we did have a tiny disagreements at times about unicode characters and encoding in URLs between Safari and FireFox, never was quite sure who had the bug. -- =========================================================================== John M. McIntosh <[email protected]> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
