tickets: 739
This data as json
| id | created | changetime | last_pulled_from_trac | stage | status | component | type | severity | version | resolution | summary | description | owner | reporter | keywords | easy | has_patch | needs_better_patch | needs_tests | needs_docs | ui_ux |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 739 | 2005-11-06 18:09:38 | 2007-01-17 22:12:17 | 2022-03-06 03:21:33.336051 | Unreviewed | closed | Documentation | task | normal | 1.0 | fixed | tutorial and docs translations | I believe that next step in i18n is to have and maintain tutorial translations. I don't know, what are the sources of tutorial texts (website? .txt files?) But I think that we should provide both forms translated. In the filesystem we could use locale code therefore I propose following structure in /django/docs: ./en all current files in english ./cs some translated files in czech ./de some translated files in german ... I am not sure about the djangoproject website yet (so it's up to you), but it would surely prove the framework to be i18n friendly. | jacob | radek <translate@svarz.cz> | 0 | 0 | 0 | 0 | 0 | 0 |