jerakeen.org

the google appengine uploader isn’t unicode aware. Grrr. Easily fixable, but still an irritating oversight.

http://code.google.com/p/googleappengine/issues/detail?id...

This utility is great and I could not live without it.

http://earthlingsoft.net/ssp/blog/2007/02/unicodechecker_112

Looks like it solves my favourite all-time problem in perl - no clear distinction between characters and byte sequences. Horay.

http://search.cpan.org/dist/encoding-warnings/lib/encodin...

http://www.unicode.org/charts/

..and not a single non-ascii character on the page.

http://www.crockford.com/JSON/example.html

http://www.amk.ca/python/howto/unicode

Firstly, tell your local terminal application that you want a utf-8 window. This is left to you, but under macos (which I use), right click the window, select ‘Window settings’, pick the ‘Display’ option from the drop-down, and pick utf-8 under ‘Character set encoding’.

Next, when you start the screen session, pass the ‘-U’ flag. This has to be passed to a new screen session - you can’t connect to an existing one this way.

screen -U

Alternatively, you can turn on the utf-8 flag for a single existing screen window by typing your hotkey (ctrl-a by default), then ‘:utf8 on’. This is good if you don’t want all of your windows to be utf now.

On the remote machine, make sure that the ‘LANG‘ environment variable is set to something UTF-8 like, for instance, I use

export LANG=en_GB.UTF-8

in my .bashrc.

Finally, you need to tell irssi to use UTF-8. Start it up in your new utf-8 window, and type

/set term_type utf-8

Hopefully everything should work now.

Does no-one in the world care about non-ASCII characters? It’s pathetic. I’m trying to make HTML form uploads work for files with non-ASCII characters in their names, and I’m hitting the stupidest problems.

The main bugbear is mozilla - you can’t upload files with wide characters in their names. At all. Piece of shit. Safari seems to be encoding the upload filenames with some made-up encoding that I can’t figure out, so that’s out of luck. At least safari sends the actual contents of the files.

The one browser I’ve tried that works flawlessly is Internet Explorer. Microsoft, at least, seem to care about the non-US market.

Today I discovered that safari ‘magically’ downgrades latin-1 input in form password fields to their nearest ascii equivalents - typing ‘pásswörd’ into a password box actually submits ‘password’. But you can cut and paste non-ascii in and it works fine. I’m very confused.

http://www.macchiato.com/unicode/charts.html