tx pull -l <LANG>
LANGUAGE=<LANG> make html
--
Ticket URL: <https://code.djangoproject.com/ticket/27401>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* Attachment "patch.diff" added.
* type: Uncategorized => New feature
Old description:
> It need Transifex config for docs/
>
> tx pull -l <LANG>
> LANGUAGE=<LANG> make html
New description:
It need Transifex config for docs/
tx pull -l <LANG>
LANGUAGE=<LANG> make html
--
Comment:
Claude, could you advise about this? I'm not sure if it's duplicating
anything that's implemented for the djangoproject.com builds. If accepted,
should we also add some docs about building the translated docs locally?
[https://github.com/django/django/pull/7450 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/27401#comment:1>
Comment (by Jeho, Sung):
Replying to [comment:1 Tim Graham]:
> Claude, could you advise about this? I'm not sure if it's duplicating
anything that's implemented for the djangoproject.com builds. If accepted,
should we also add some docs about building the translated docs locally?
>
> [https://github.com/django/django/pull/7450 PR]
sorry for my pool english, I try to explain.
this configuration is integrate with transifex service.
1. contributors(yes, they need to register at `django-docs` on transifex)
can `pull docs/locale/<lang>/LC_MESSAGES/` anytime.
2. contributors can build docs locally, and check it.
3. contributors can upload `.po` file by `tx push` in command line
environment
4. contributors can check warning by local build
5. and yes, it need to some modify on `README` and `Makefile`
Ok, I'm not expert and almost newbie- but if you help me(eg: correction
typo, syntax...),
I want to contribute this ticket myself. (anyway it's my first ticket on
django)
> I'm not sure if it's duplicating anything that's implemented for the
djangoproject.com builds.
yhea, that's problem.
if any existing repository like "django/docs" on the github, it would be
happy- but not exists such repository.
So i forked django official repository, and write some configuration.
Could you check about this by forwarding this ticket? actually i don't
know about `djangoproject.com`'s build plan,
--
Ticket URL: <https://code.djangoproject.com/ticket/27401#comment:2>
* needs_better_patch: 0 => 1
Comment:
Currently, this is handled in the django-docs-translation repository
(https://github.com/django/django-docs-translations/tree/stable/1.10.x),
and the translation process is described in
https://code.djangoproject.com/wiki/TranslatingDocumentation.
I'm not against improving this toolchain (it was a bit experimental at the
time) and integrating part of all of it directly inside the Django main
repository, but the patch should also include functional instructions in
the Django docs (How to build translated documentation).
--
Ticket URL: <https://code.djangoproject.com/ticket/27401#comment:3>
* stage: Unreviewed => Accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/27401#comment:4>
Comment (by Jeho, Sung):
Replying to [comment:3 Claude Paroz]:
> Currently, this is handled in the django-docs-translation repository
(https://github.com/django/django-docs-translations/tree/stable/1.10.x),
and the translation process is described in
https://code.djangoproject.com/wiki/TranslatingDocumentation.
>
> I'm not against improving this toolchain (it was a bit experimental at
the time) and integrating part of all of it directly inside the Django
main repository, but the patch should also include functional instructions
in the Django docs (How to build translated documentation).
Oh. what a shame..
I didn't know about django-docs-translation repository.
You don't need doing "experimental", keep it safe.
please roll back my PR.
If this "improvement" really need it, I'll request again.
sorry again.
--
Ticket URL: <https://code.djangoproject.com/ticket/27401#comment:5>