Opened 13 months ago

Last modified 13 months ago

#27401 new New feature

Add Transifex config to build translated docs

Reported by: Jeho, Sung Owned by: nobody
Component: Documentation Version: master
Severity: Normal Keywords: transifex, document
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: yes
Easy pickings: no UI/UX: no

Description (last modified by Tim Graham)

It need Transifex config for docs/

tx pull -l <LANG>
LANGUAGE=<LANG> make html

Attachments (1)

patch.diff (1.6 KB) - added by Jeho, Sung 13 months ago.

Download all attachments as: .zip

Change History (6)

Changed 13 months ago by Jeho, Sung

Attachment: patch.diff added

comment:1 Changed 13 months ago by Tim Graham

Description: modified (diff)
Summary: need Transifex config file for docsAdd Transifex config to build translated docs
Type: UncategorizedNew feature

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?

PR

comment:2 in reply to:  1 Changed 13 months ago by Jeho, Sung

Replying to 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?

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,

comment:3 Changed 13 months ago by Claude Paroz

Patch needs improvement: set

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).

comment:4 Changed 13 months ago by Tim Graham

Triage Stage: UnreviewedAccepted

comment:5 in reply to:  3 Changed 13 months ago by Jeho, Sung

Replying to 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.

Note: See TracTickets for help on using tickets.
Back to Top