Bill de hÓra wrote:
> I need to test this properly and fill in the mappings
The official Cyrillic-Latin mapping could be found here:
http://en.wikipedia.org/wiki/Translit
It could be like this:
var RUSSIAN_MAP =
{
"а": "a","к": "k","х": "kh,
"б": "b","л": "l","ц": "ts",
"в": "v"
Jacob Kaplan-Moss wrote:
> "... with too many backwards-incompatible changes ..." -- as Hugo
> points out, this will break a lot of existing code.
Well, some day Django will have to switch to unicode anyway (even Python-3000
is going to use unicode strings everywhere). Right now is a good time f
Hi,
I am using Django for about half a year and it rocks. Indeed, it would rock
even more if it switched from using UTF-8 bytestrings to use unicode strings
everywhere.
The main drawbacks of using UTF-8 strings are:
- regexps won't work on utf-8 bytestrings containing non-ASCII characters;
- l
