yes, encodings once again :) My CSS has UTF8 content that gets displayed: I'm using foo:after { contents: '»'; } (that's a french closing guillemot in there, looks like >> ) I'm loading it in a subclass of WAFileLibrary using #addAllFilesIn: When I use WAKom, the guillemot becomes an error character. With WAKomEncoded it's displayed correctly. but then I can't use some characters when editing pages. My understanding was that WAKomEncoded converts to the squeak internal representation, and WAKom does nothing, so WAKom should work (as long as I have UTF in my files, which is the case), and WAKomEncoded could fail if it tries to convert what's in the FileLibrary from squeak to utf before serving… Why is it the reverse in practice? -- Damien Pollet type less, do more [ | ] http://typo.cdlm.fasmz.org