On 28 Jul 2006, at 18:35, Steven Armstrong wrote:
On 07/28/06 18:09, GinTon wrote: <snip>I say you the disadvantages about use LC*: 1) You need all locales installed in your system to let the correct localization to users of whatever country.I would actually prefer the LC_* approach, but GinTon has a point with this.It's bitten me before in a PHP project. I'm from Switzerland, where we have 4 languages/locales, but the site was hosted on a server in the US. The sysadmin refused to install themissing locales so the only solution was a ugly "emulate missing systemlocales" hack.
Because that I propose to copy all of the needed LC_* data into django locale directory so it will be system independent. If you need another locale just add it yourself - no need to sysadmin intervention.
It's the same system that we using now for translations. So let me emphasize that again:Yes, we will be using LC_* based l10n data but all of the required files will be *inside* django distribution like LC_MESSAGES we are using now. It will work even on windows which don't have any ability to use this type of data and all of the locale settings and data will be *local* to the django installation and independent of current server setup.
-- Nebojša Đorđević - nesh Studio Quattro - Niš - Serbia http://studioquattro.biz/http://djnesh.blogspot.com/ | http://djnesh-django.blogspot.com/ | http://trac.studioquattro.biz/djangoutils/
Registered Linux User 282159 [http://counter.li.org]
PGP.sig
Description: This is a digitally signed message part
