Am Donnerstag, 5. Oktober 2006 23:11 schrieb Ivan Sagalaev: > Dirk Eschler wrote: > > In theory i can just use utf-8, but what if one participant in the line > > (os, db, browser, whatever) can't handle it? > > Talking about client side, only very old browsers can't handle utf-8 > (NN4 and IE4 can). Same goes for email clients. And even such simple and > 'legacy' software as Windows' Notepad can read and write utf-8 files > since year 2000. > > And talking about server side that store and transfer your data, this is > also safe as utf-8 was specifically designed to be compatible with old > software that treats characters as bytes. > > All this means that currently in most cases there is no reason to do > things in anything but utf-8 (edge cases where you can't do this are > cases like shared DB server in some legacy encoding that you can't change). > > > Encodings stay one of those long time > > mysteries to me. I'd happily adopt a practice that's fool proof. > > Unicode and utf-8 is specifically designed to eliminate all these > encoding problems, to be the one universal encoding (though many > Japanese developers don't think Unicode suits this goal).
Jup, i just stumbled into encoding problems with utf-8 pretty often. And that were situations where i thought that i didn't make any mistake. Mostly desktop related though, using older toolkits etc.. Nonetheless, i think it's about time to drop old habids and give utf-8 another try. Thanks everyone! -- Dirk Eschler <mailto:[EMAIL PROTECTED]> http://www.krusader.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
