#18108 closed New feature (fixed)
Official translations of the documentation
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | Documentation | Version: | |
Severity: | Normal | Keywords: | documentation translation |
Cc: | hirokiky@… | Triage Stage: | Ready for checkin |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
In the docs, the url is prefixed by en/version, if i change to another language i found 404 pages.
I think this point is important and that many tranlators have stopped theirs job because they are not published (if you show this page wiki1 and this other wiki2), you can see that many efforts have been made.
I take this report as blocked, because i think that for too much developpers, don't to read docs in theirs language is blocking. For me even if i can read and write english, i read and write slowly than in my mother language. For coding this is a little problem (signs are near math formulas), for docs, this is a strong problem, as you read many sentences in shorts times.
To conclude my questions are :
- Is it possible with actual system to publish translation.
- If yes :
- when django will permit to send translations and to publish them?
- where? (svn, git, a special django system...)
- what will be the translation process? acceptance - failover...
If this is possible, i will participates and many others. Be sure that this interessests many people.
Whatever your answer, thanks for your works, this site is so clear and django is a powerfull framework.
Best Regard,
Nicolas
Attachments (2)
Change History (20)
comment:1 by , 13 years ago
Severity: | Release blocker → Normal |
---|
comment:2 by , 13 years ago
Component: | Djangoproject.com Web site → Internationalization |
---|---|
Has patch: | set |
Patch needs improvement: | set |
Triage Stage: | Unreviewed → Accepted |
Type: | Uncategorized → New feature |
We are very close to a working process for translating the Django documentation. Just attaching a work-in-progress patch to share my experiments until now.
comment:3 by , 12 years ago
I published a workflow proposal on a wiki page: TranslatingDocumentation
Please read and review/comment.
comment:4 by , 12 years ago
Component: | Internationalization → Documentation |
---|---|
Summary: | Where are translations for docs → Official translations of the documentation |
Marking #8940 as a duplicate of this ticket since this one has more recent activity.
follow-up: 6 comment:5 by , 12 years ago
I've reviewed the TranslatingDocumentation page and agree with it, although have a few questions:
What do we need to modify in the djangoproject.com code to search the different languages?
When do we pull the changes from Transifex?
comment:6 by , 12 years ago
Replying to jezdez:
What do we need to modify in the djangoproject.com code to search the different languages?
Oh well, I didn't think about that. Probably we should create a different search index for each language. I will add a note on the Wiki.
When do we pull the changes from Transifex?
This is still undecided, might be once a week, for example. It depends also on the automation we'll achieve with the whole process.
comment:7 by , 12 years ago
Git repo: https://github.com/django/django-docs-translations
Transifex project: https://www.transifex.com/projects/p/django-docs/
The question arose about sharing translation teams with Django Transifex. Mixing 17185 translatable strings (344891 words) in django-docs with django's 3042 words would make translation stats looks imbalanced. The current feeling is to not share teams (small overhead to manage 2 different team sets).
comment:8 by , 12 years ago
Anyone at ease with writing Makefiles to create one to compile po files into mo files in https://github.com/django/django-docs-translations ?
comment:9 by , 12 years ago
Cc: | added |
---|
I sent a pull-request adding a Makefile to compile po files into mo files.
comment:10 by , 11 years ago
I want to use machine translation on Web interface of Transifex.
But, I'm not have a permission to change the setting of this project (https://www.transifex.com/projects/p/django-docs/).
Would someone set the cooperation to translation service?
comment:11 by , 11 years ago
@hirokiky I've just enabled the Google machine translation ability (with my personal account).
comment:13 by , 10 years ago
Has patch: | unset |
---|---|
Patch needs improvement: | unset |
I think the main task is to increase visibility of the translation documentation (#22061), but I'll leave this open for Claude to confirm.
comment:14 by , 10 years ago
Timo, shouldn't we complement the https://docs.djangoproject.com/en/dev/internals/contributing/localizing page about documentation translation? I would write something like this, but feel free to rewrite it in a better English.
Documentation ============= There is also the opportunity to translate the documentation, even if this is a huge work to complete entirely (you have been warned!). We use the same Transifex tool, but at this URL: https://www.transifex.com/projects/p/django-docs/. The translation will appear on the docs.djangoproject.com Web site as soon as at least the ``intro`` part is fully translated in your language.
by , 10 years ago
Attachment: | 18108.diff added |
---|
comment:16 by , 10 years ago
Triage Stage: | Accepted → Ready for checkin |
---|
Great (as usual). Please commit and close the ticket.
comment:17 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Technically this isn't a release blocker. It sounds more like a social issue that a code issue, too.