User:Jibecfed/fedoradoc-antora-localization/pt

In other languages: English (en) português (pt) [edit]

Trabalho em progresso
Objetivo: para poder traduzir a documentação «Projeto da Documentação» do Fedora na nossa «Plataforma de Tradução L10N»

• FAD neste assunto será no dia 12 e 13 de abril: https://pagure.io/Fedora-Council/tickets/issue/250
• Relatório em inglês: https://communityblog.fedoraproject.org/fedora-docs-translations-fad-report/
• Relatório em francês: https://jibecfed.fedorapeople.org/blog-hugo/fr/2019/04/notre-documentation-pourra-bient%C3%B4t-%C3%AAtre-traduite-/

Colaboradores:

• user:asamalik (utilização e scripting de antora),
• user:jibecfed (scripting, testes, internacionalização, plataforma de tradução),
• user:bex (correções po4a (patches)

Sinopse

Fonte inglês -> ficheirios POT -> ficheiros PO -> fonte traduzida -> sites traduzido

Crie uma pipeline de documentos do Fedora, incluindo a internacionalização e a tradução

Organização Git

1. Fonte inglês => reprositório de Documentos ==> (D)
   1. A maioria em https://pagure.io/projects/fedora-docs/%2A
2. Ficheiros POT -> ficheiros PO => repositório de tradução ==> (L)
   1. https://pagure.io/projects/fedora-l10n/%2A
3. Ficheiros PO -> conteúdo traduzido
   1. https://pagure.io/fedora-docs/translated-sources/
4. fonte traduzida => repositório da "Web"==> (W)
   1. https://pagure.io/fedora-docs/fedora-docs-web/ (ver ramos)

Processo

1. When there is a change in (D), it will call a job, and update pot files in (L)
2. When there is a change in (L), translation platform will know and get updated
3. When there is a change in translation platform, it will update content in (L)
4. Every day or night, content from (D for EN) and (L for every other languages) are used to generate content for (W), and publish it

Fase atual

• 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/

Como criar (build)

To build translated website, just run the "build-translated.sh" file from: https://pagure.io/fedora-docs/docs-fp-o Note: I wrote an updated script (using local cache to save a LOT OF TIME): https://pagure.io/fork/jibecfed/fedora-docs/docs-fp-o/tree/tracking

To produce new pot from source and new localized content from po files: https://pagure.io/fedora-docs/translations-scripts/ Note: you need commit right on multiple repositories to do so.

Requisitos para entrar na 'Fase Beta'

A fase 'Beta' significa:

1. translation is open for a few more languages, testing is still active.
2. translation platform is still Weblate as a test tool

• Concluído:
  • #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
  • 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)
  • Generate the list of docs to convert for translation in all-src-to-pot from site.yml
  • Create all required fedora-l10n repositories
  • Generate the list of translated language from localization repositories
  • #116 Translated UI — determine how it's gonna work
  • #117 Translated UI — create it
• TODO:
  • Generate localized version of yml files
  • #122 (spike) How do we deal with images?
  • use the same [script for language redirection as the one for fedora-wesites https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/fedora-web/getfedora/files/languages.conf]

Requisitos para entrar na 'Disponibilidade Pública'

'Disponibilidade Pública' significa:

1. translation is open for every needed languages.
2. translation platform is Zanata or any other tool the Fedora community decide to use

CONCLUÍDO:

• don't assume language list in all-po-to-src

TODO:

• • Infra ticket is open: https://pagure.io/fedora-infrastructure/issue/7696
• #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
• Doc generation should use fedora infrastructure (and not Asamalik's fedorapeople)

Outros melhoramentos necessários

• 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

Outras ferramentas de acompanhamento

Taiga follow-up: https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/epic/1