From Fedora Project Wiki
(creation) |
(improvments) |
||
Line 3: | Line 3: | ||
== Current phase == | == Current phase == | ||
− | * We are in | + | * We are in '''Alpha''' |
* We translate in French to validate the tooling. | * We translate in French to validate the tooling. | ||
* We create a few other languages to validate the tool. | * We create a few other languages to validate the tool. | ||
Line 15: | Line 15: | ||
# translation platform is still Weblate as a test tool | # translation platform is still Weblate as a test tool | ||
− | * #110 POT+PO repositories — design the structure | + | * Done: |
− | * #111 POT+PO repositories — create them | + | ** #110 POT+PO repositories — design the structure |
− | * #112 Translated source repositories — design the structure | + | ** #111 POT+PO repositories — create them |
− | * #113 Translated source repositories — create them | + | ** #112 Translated source repositories — design the structure |
− | * #114 English source -> POT script — write it | + | ** #113 Translated source repositories — create them |
− | * #115 PO -> translated source script — write it | + | ** #114 English source -> POT script — write it |
− | * #116 Translated UI — determine how it's gonna work | + | ** #115 PO -> translated source script — write it |
− | * #117 Translated UI — create it | + | ** #119 Build script for translated site — write it |
− | * | + | ** #123 Redesign the structure of the PO and POT repositories |
− | + | * TODO: | |
+ | ** Fix the language code (we should stick to IETF BCP 47 language tag and not assume anything) | ||
+ | *** Context: a language can have multiple regional declination (and variants, etc.). | ||
+ | *** In this URL: https://docs.fedoraproject.org/fr-FR/docs/ the language code should be fr, because it's how the folder is named. https://pagure.io/fedora-l10n/docs/blob/master/f/po (it's the translation platform who will create the correct folder name) | ||
+ | ** #116 Translated UI — determine how it's gonna work | ||
+ | *** Includes: browser's language detection for redirection and language button? '''needs better description''' | ||
+ | ** #117 Translated UI — create it | ||
+ | *** what does it includes? '''needs better description''' | ||
− | == | + | == Requirements to enter Public Availability == |
Public Availability means: | Public Availability means: | ||
Line 36: | Line 43: | ||
* #130 Fix: Clicking on the logo should go to a homepage of the current language | * #130 Fix: Clicking on the logo should go to a homepage of the current language | ||
* #122 (spike) How do we deal with images? | * #122 (spike) How do we deal with images? | ||
+ | * Doc generation should use fedora infrastructure (and not Asamalik's computer) | ||
− | == | + | == Other needed improvements == |
− | * #133 include localized URL in sitemaps | + | * TODO: |
− | * #35 We need to be able to generate “href lang attributes” | + | ** #133 include localized URL in sitemaps |
− | * RTL texts (arabic, ...) | + | ** Generally speaking, respect i18n-checker advices https://validator.w3.org/i18n-checker/ |
− | * Dedicated documentation | + | *** #35 We need to be able to generate “href lang attributes” |
+ | ** RTL texts (arabic, ...) | ||
+ | ** Dedicated documentation |
Revision as of 12:26, 25 February 2019
Taiga follow-up: https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/epic/1
Contents
Current phase
- We are in Alpha
- We translate in French to validate the tooling.
- We create a few other languages to validate the tool.
- We use a Weblate as a test tool http://translate.holcroft.fr/
Requirements to enter Beta Phase
Beta phase means:
- translation is open for a few more languages, testing is still active.
- translation platform is still Weblate as a test tool
- Done:
- #110 POT+PO repositories — design the structure
- #111 POT+PO repositories — create them
- #112 Translated source repositories — design the structure
- #113 Translated source repositories — create them
- #114 English source -> POT script — write it
- #115 PO -> translated source script — write it
- #119 Build script for translated site — write it
- #123 Redesign the structure of the PO and POT repositories
- TODO:
- Fix the language code (we should stick to IETF BCP 47 language tag and not assume anything)
- Context: a language can have multiple regional declination (and variants, etc.).
- In this URL: https://docs.fedoraproject.org/fr-FR/docs/ the language code should be fr, because it's how the folder is named. https://pagure.io/fedora-l10n/docs/blob/master/f/po (it's the translation platform who will create the correct folder name)
- #116 Translated UI — determine how it's gonna work
- Includes: browser's language detection for redirection and language button? needs better description
- #117 Translated UI — create it
- what does it includes? needs better description
- Fix the language code (we should stick to IETF BCP 47 language tag and not assume anything)
Requirements to enter Public Availability
Public Availability means:
- translation is open for every needed languages.
- translation platform is Zanata or any other tool the Fedora community decide to use
- #120 Process for adding new content — draft it
- #121 Process for adding a new language — draft it
- #130 Fix: Clicking on the logo should go to a homepage of the current language
- #122 (spike) How do we deal with images?
- Doc generation should use fedora infrastructure (and not Asamalik's computer)
Other needed improvements
- TODO:
- #133 include localized URL in sitemaps
- Generally speaking, respect i18n-checker advices https://validator.w3.org/i18n-checker/
- #35 We need to be able to generate “href lang attributes”
- RTL texts (arabic, ...)
- Dedicated documentation