Re: Issue 82 in glassdb: encodeForHTTP broken for nonascii characters

Updates:
        Labels: -Milestone-3.0 Milestone-1.0-beta.8.5

Comment #5 on issue 82 by [hidden email]: encodeForHTTP broken for  
nonascii characters
http://code.google.com/p/glassdb/issues/detail?id=82

Changed milestone ... I think this one might be address already?

Comment #6 on issue 82 by [hidden email]: encodeForHTTP broken for  
nonascii characters
http://code.google.com/p/glassdb/issues/detail?id=82

I'm thinking of Issue 109...

Comment #7 on issue 82 by philippe.marschall: encodeForHTTP broken for  
nonascii characters
http://code.google.com/p/glassdb/issues/detail?id=82

Note that there is no "right" implementation. What the correct encoding is  
depends on the server. IIRC Squeak 3.9 switched from ISO-8859-1 to UTF-8.

To control the encoding Squeak/Pharo have #encodeForHTTPWithTextEncoding:.

Updates:
        Status: Fixed

Comment #8 on issue 82 by [hidden email]: encodeForHTTP broken for  
nonascii characters
http://code.google.com/p/glassdb/issues/detail?id=82

See Issue 195:

CharacterCollection>>encodeForHTTPWithTextEncoding: has been added to  
GemStone:

   Gofer project load: 'GsPharo' version: '0.9'

Note that GsPharo 0.9 is currently in development.