Skip to content

Translation roadmap tracker #3

Description

@tamnd

Tracker for the long tail of translation work. Details live in ROADMAP.md once PR #2 lands.

Where we are

PR #1 landed machine translation of the PEP 545 language-switcher files (bugs, tutorial, library/functions). 1,860 entries, around 50,240 words, every string still fuzzy. That means Sphinx keeps rendering English on docs.python.org/vi/ until someone unfuzzies strings by hand.

What is left

About 1.76 million words across 516 .po files. Short version:

Section Files Words
library/ (minus functions.po) 325 791,751
whatsnew/ 25 566,964
c-api/ 77 120,511
howto/ 29 102,918
reference/ 11 67,740
using/ 9 30,792
faq/ 9 27,262
extending/ 7 21,920
root pages 8 20,017
deprecations/ 14 7,116
installing/ 1 1,003
distributing/ 1 30

See ROADMAP.md for the phase ordering and reasoning.

Milestones

  • PR MT seed: PEP 545 language-switcher milestone (bugs + tutorial + library/functions) #1: machine-translated seed for the language-switcher milestone
  • ROADMAP.md landed (PR Add ROADMAP.md #2)
  • GLOSSARY.md landed with terminology and pronoun policies
  • bugs.po fully unfuzzied
  • tutorial/*.po fully unfuzzied
  • library/functions.po fully unfuzzied
  • docsbuild-scripts inclusion requested (PEP 545 language-switcher entry)
  • Phase 1 complete: root pages and glossary.po
  • Phase 2 complete: reference/
  • Phase 3 complete: howto/ and faq/
  • Phase 4 complete: using/, extending/, installing/, distributing/
  • Phase 5 complete: c-api/
  • Phase 6 Tier A complete: top-20 most-read library modules
  • Phase 6 Tier B complete: remaining actively-used library modules
  • Phase 7 policy in place: whatsnew/3.14 translated, older versions excluded
  • Coordinator has signed the PSF CLA
  • Repo transfer to github.com/python/python-docs-vi requested

Ground rules

  • Before you start a file, open an issue titled Translate {path} and assign yourself. That stops two people translating the same file in parallel.
  • Branch name mirrors the file: library-os, reference-datamodel, etc.
  • Open the PR as a draft early. Early PRs let someone catch a bad terminology choice before you have applied it to 500 strings.
  • Only unfuzzy strings you have actually read. Sphinx skips fuzzy, so untouched MT is harmless until you sign off on it.
  • Run make verifs before pushing.

Things to decide before Phase 6

These matter most once we are deep in the library reference. Decide them during Phase 0 while reviewing PR #1.

  • Pronoun. Google picked bạn throughout. Vietnamese formal tech writing often drops the pronoun.
  • Technical nouns. Whether to translate or keep English for: list, tuple, dict, set, iterable, iterator, comprehension, decorator, callable, module, package, exception, context manager.
  • Heading style. Imperative vs noun form. Sentence case vs title case.

Put the decisions in GLOSSARY.md so they are discoverable, not lost in review threads.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions