Comments on The Python & Marc Garcia: Translating Django apps. Good practices

it is not clear how to keep the translations for t...

2009-04-04T16:35:00.000+02:00

it is not clear how to keep the translations for the applications separately inside of one project.

Hi Robert,

there is no TransSlugField inclu...

2008-09-23T02:50:00.000+02:00

Hi Robert,

there is no TransSlugField included in transdb, so you won't be able to use it directly. I don't know how much difficult will be implementing a slugfield using a TransCharField, probably not so much.

As for TransDB.

Can I use it with slugfield...

2008-09-22T15:51:00.000+02:00

As for TransDB.

Can I use it with slugfield ?
As far as I know there should be an sql index created for slugfield,
which means I can't store it as it's stored as dict.

Please correct me if I'm wrong.

Thanks!

Thanks for your comment David, I escaped the chara...

2008-08-14T00:39:00.000+02:00

Thanks for your comment David, I escaped the characters to let user see it as is.

I didn't know that in French you use a space before the colon. This make my example be useless... I don't want to know how can it be in Chinese... :)

For the dynamic string using names parameters (f.e. "My name is %(person_name)s") and also with comments should be enough for more cases.

Of course it's really difficult to have a i18n that works in all languages. And I'm not a real expert...

Your "native language" doesn't need to be "copy-re...

2008-08-04T08:00:00.000+02:00

Your "native language" doesn't need to be "copy-ready" text in any language! You can use a string that is more descriptive of the way the text will be used, then translate it to all your languages, even your native one. In the "play" example, you might have the strings:

"play [a musical instrument]"
"play [a sport]"
"play [intransitive]"

You translate all of them to "play" in English, but "jugar" and "tocar", etc., as appropriate.

In that example, you might want to use a string interpolation (e.g., "play %(musical_instrument)s"), in case a target language has unusual rules about how the phrase is formed.

Still, all this semi-automatic internationalization stuff is really automated code-writing for natural-language generation. We have a few barely-adequate domain-specific languages (gettext and string interpolation, locale-specific currency, etc.), but the problem really requires the full power of programming. More on that later, perhaps.

Excellent writeup Marc. This is quite helpful.

2008-08-03T17:20:00.000+02:00

Excellent writeup Marc. This is quite helpful.

thanks for the demonstration!
it saves quite a ...

2008-08-03T06:01:00.000+02:00

thanks for the demonstration!
it saves quite a lot of time

Thanks for the correction Matthias, already correc...

2008-08-03T03:35:00.000+02:00

Thanks for the correction Matthias, already corrected it.

Very good tips, but I think you've got the last on...

2008-08-02T14:31:00.000+02:00

Very good tips, but I think you've got the last one backwards: It's actually _less_ work to change a string from a translation than from the main language. Otherwise, thanks for the round-up.

Very cool tips!
gracias
SAn

2008-08-01T22:44:00.000+02:00

Very cool tips!
gracias
SAn

Comments on The Python & Marc Garcia: Translating Django apps. Good practices

it is not clear how to keep the translations for t...

Hi Robert,there is no TransSlugField inclu...

As for TransDB.Can I use it with slugfield...

Thanks for your comment David, I escaped the chara...

Your "native language" doesn't need to be "copy-re...

Excellent writeup Marc. This is quite helpful.

thanks for the demonstration!it saves quite a ...

Thanks for the correction Matthias, already correc...

Very good tips, but I think you've got the last on...

Very cool tips!graciasSAn

Hi Robert,

there is no TransSlugField inclu...

As for TransDB.

Can I use it with slugfield...

thanks for the demonstration!
it saves quite a ...

Very cool tips!
gracias
SAn