Re: i18n -- let's do it!

2005-08-04 Thread Carlo C8E Miron
hi folks 2005/8/2, Radek Svarz <[EMAIL PROTECTED]>: > > As a tool for translators I suggest poEdit (http://www.poedit.org/). It > is very comfortable editor. Another alternative is to use Rosetta * https://launchpad.net/rosetta Rosetta is the translation portal of (but not limited to) the Ub

Re: i18n -- let's do it!

2005-08-04 Thread Nebojša Đorđević - nesh
On 3-08-2005, at 14:23, Ksenia Marasanova wrote: I didn't digget into it yet but it looks like the solution is do not use "install()" method. http://barry.warsaw.us/papers/mailman-freenix-2003/node8.html And here is implementation - put files in django/core/i18n or similar. Usage: set_languag

Re: i18n -- let's do it!

2005-08-03 Thread Ksenia Marasanova
> Given this, I cannot possibly see how installing more than one language can > work. More to the point, even if it did, install() modifies __builtin__, > which sounds incredibly thread-unsafe to me. We can still use the > GNUTranslation objects, we just can't install them. _() needs to generate a

Re: i18n -- let's do it!

2005-08-03 Thread Moof
Nebojša Đorđević - nesh wrote: > Ok, too bad for that, now we must make some replacement for formatting > date, numbers and stuff. I've creted a page on the Wiki with an overview of the i18n discussion as I see it. it looks rather tainted to my prejudices at the moment, so I invite you all to h

Re: i18n -- let's do it!

2005-08-03 Thread Moof
Nebojša Đorđević - nesh wrote: > Changing languages on the fly: http://docs.python.org/lib/node331.html > > As I understood python gettext manual strings are translated when _() > are called, not at module load time. And _() is installed into builtin > namespace after .install() is called. Lo

Re: i18n -- let's do it!

2005-08-03 Thread Nebojša Đorđević - nesh
On 3-08-2005, at 12:25, Moof wrote: Havign had a closer look at the gettext module: It sucks for what we want to use it for. I think we may need to end up defining our own subclass of string. The gettext format is fine, and I suggest we keep to that, but don't use the standard gettext pro

Re: i18n -- let's do it!

2005-08-03 Thread Nebojša Đorđević - nesh
On 3-08-2005, at 1:05, Moof wrote: By "not threadsafe" it means that settign the locale is a global thing. So you can't have two threads with different locales, and you mgiht end up changing locale half way though the execution of a locale-dependent method. Also, from experience, setloc

Re: i18n -- let's do it!

2005-08-03 Thread Moof
Ksenia Marasanova wrote: >>OTOH, maybe we can go for database based solution like some PHP CMS I >>seen? > > > -1 > It's my first i18n experience, but I think it's better to stick to an > accepted standard here. Havign had a closer look at the gettext module: It sucks for what we want to use

Re: i18n -- let's do it!

2005-08-02 Thread Moof
Nebojša Đorđević - nesh wrote: > I agree, after a day of digging through the net and gettext > documentation I think that gettext way is the right way :). If and only if it's independent of locale. > And another question: > Should we go for "full" localization -> use locale python module

Re: i18n -- let's do it!

2005-08-02 Thread Nebojša Đorđević - nesh
On 2-08-2005, at 16:46, Ksenia Marasanova wrote: -1 It's my first i18n experience, but I think it's better to stick to an accepted standard here. I agree, after a day of digging through the net and gettext documentation I think that gettext way is the right way :). And another question:

Re: i18n -- let's do it!

2005-08-02 Thread Moof
Ksenia Marasanova wrote: > 2005/8/1, Adrian Holovaty <[EMAIL PROTECTED]>: > >>Nebojša, or somebody else who's knowledgable, can you provide a basic >>checklist of all the things we need to do to get i18n up and running? >>I've seen your patches, but I'd appreciate a higher-level overview of >>all

Re: i18n -- let's do it!

2005-08-02 Thread Ksenia Marasanova
2005/8/1, Adrian Holovaty <[EMAIL PROTECTED]>: > Nebojša, or somebody else who's knowledgable, can you provide a basic > checklist of all the things we need to do to get i18n up and running? > I've seen your patches, but I'd appreciate a higher-level overview of > all the steps we need to take. T

Re: i18n -- let's do it!

2005-08-02 Thread Nebojša Đorđević - nesh
OTOH, maybe we can go for database based solution like some PHP CMS I seen? This is, maybe, more user-friendlier way? Good thing is that users can change messages within admin interface, no need for external software on the server (for online editing of translations) and all apps can hav

Re: i18n -- let's do it!

2005-08-02 Thread Nebojša Đorđević
On 1-08-2005, at 20:12, Adrian Holovaty wrote: Nebojša, or somebody else who's knowledgable, can you provide a basic checklist of all the things we need to do to get i18n up and running? I've seen your patches, but I'd appreciate a higher-level overview of all the steps we need to take. Well,

Re: i18n -- let's do it!

2005-08-01 Thread Radek Svarz
As a tool for translators I suggest poEdit (http://www.poedit.org/). It is very comfortable editor.

i18n -- let's do it!

2005-08-01 Thread Adrian Holovaty
Thanks to Nebojša Đorđević for submitting some internationalization patches. I admit this i18n stuff is completely new to me, although I've taken some time to read the gettext documentation at http://www.python.org/doc/current/lib/module-gettext.html and am excited about adding this as soon as poss