Skip to end of metadata
Go to start of metadata

Preface

The Traffic Server documentations are using reST and Sphinx, and hosted on ReadTheDocs. This documentation describes workflow of internationalization using sphinx-intl, ReadTheDocs, GitHub and Transifex.

Tools

Before start you need below tools.

  • gettext
  • sphinx
  • sphinx-intl
  • transifex-client

 

Below workflow is deprecated favor of to stop using ReadTheDocs. See more details in TS-4428 (May 2016)

 

Internationalization Workflow

Relationships between GitHub, ReadTheDocs and Transifex

Transifex doesn't have branch or version features, thus we need a project for each LTS version.

Basics

We're following Sphinx's Internationalization workflow with sphinx-int and gettext.

Update PO files

You got a directory that contain po files. 

  •  ./locale/<LANG>/LC_MESSAGES/ 

Synchronise GitHub and Transifex

This will be done by administrators of each language periodically. 

Transifex → GitHub

  1. Pull translations from Transifex

  2. Format PO files

  3. Commit PO files
  4. Push to repositories of your languages on GitHub

GitHub → Transifex

CAUTION: When you upload po files on transifex.com, it will over write translations on transifex.com. This means translations which only on transifex.com will be deleted.

  1. Pull source files from apache/trafficserver

  2. Generate POT files from rst files

  3. Update config file of tx command

  4. Upload POT files

Building the translated documentation in local

Generate mo files with translated PO files

Build HTML with MO files 

ReadTheDocs Theme

If you want to apply RTD theme, install sphinx_rtd_theme via pip.

Add new language

  1. Create new repositories on GitHub
  2. Create new project on ReadTheDocs
  3. Request to add new language on Transifex
  4. Request to committer or PMC on ML to add relations on ReadTheDocs
  5. Request to committer or PMC on ML to add new remap rules on docs.trafficserver.apache.org

See Also

  • No labels