Translation support for project documents

Registered by Ian Y. Choi on 2018-02-16

Documents in openstack-manuals previously were successfully migrated to project docs [1].
Migrated project docs can be also translation targets and plans in I18n team.

[1] http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Ian Y. Choi
Direction:
Needs approval
Assignee:
Ian Y. Choi
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

- Indexes for translated documentations can be optional.

- POT generation for project documents: https://review.openstack.org/#/c/545377/

[amotoki - Feb 17, 2018] Could you consider generating POT files per documents like install guide, user guide, admin guide, configuration reference, and so on. It is because it is not common that translators translates the whole document including contributor documents. By splitting POT files per document, translators can easily track the progress of translations. We have the guideline for document structure but it potentially varies across projects, so it would be better to allow to configure it per project.

From the perspective of a language coordinator of Japanese team, I have no strong opinion on POT file structure though (as translating documentation is not active in Japanese team and from my survey it is less interested compared to GUI). => good idea and thanks a lot for reflecting this idea into the patch!

(?)

Work Items

Work items:
Identification of project doc targets: DONE
POT generation for project documents: TODO
Adding translated documentation generation into PTI: TODO

This blueprint contains Public information 
Everyone can see this information.