Translating Fedora Documentation: Indonesian Team Perspective
0 likes74 views
This document summarizes the perspective of the Indonesian translation team on translating Fedora documentation. It provides background on the Indonesian language and motivation for translation. It then discusses the team's involvement starting in 2017, peak productivity in 2020, and approach to translating documentation efficiently by carrying over translations from previous releases when possible. It raises questions about alternative translation approaches, such as starting with command line help instead of user interfaces, and discusses potential drawbacks to that approach.
Translating Fedora Documentation: Indonesian Team Perspective
- 1. Translating Fedora Documentation: Indonesian Team Perspective Andika Triwidada <andika at gmail dot com>
- 2. $ whoami ● Use various OSes from DOS to mainframe, *nix ● Programming Z80, 8086 & 8087 assembly, Fortran, Pascal, C, .. ● IT security consultant since 2000 ● GNOME Indonesian translation coordinator; Indonesian translator of LibreOffice and many other ● … occasionally has too much free times
- 3. 270 mil Languages: Indonesian - 210M Javanese - 84M Sundanese - 42M Madurese - 13M Minang - 5.5M Bugis - 5M ... source: wikipedia
- 4. Why? ● Why translate? ● Why translate Fedora? ● Why translate Fedora documentation?
- 7. Fedora Involvement ● Starting around F26 release, June 2017 ● Peak productivity ~April-May 2020, or before (?), can’t recall due to migration from Zanata to Weblate
- 11. How To Achieve Speed? ● Offline tool: Poedit (or Gtranslator, Lokalize) ○ Quicker navigation ○ More TransMem content from other projects ● Documentation structure ○ Every releases has System Administration Guide, Installation Guide, and Release Notes ○ Most strings from SAG & IG intact between releases, many strings from RN are also unchanged
- 14. How To Achieve Speed On New Release? ● Download version from previous release ● Upload to new release ● Finish the rest
- 15. What NOT to Copy? ● Single fighter (fortunately, not anymore)
- 16. Translation Approach Alternative What do you think about … ● … command line? who use them? do they need translation? ● … UI? dialogs, menus, shortcuts, … will users have problem with untranslated UI if they can get appropriate help?
- 17. Alternative Drawbacks ● Starting with translating help will: ○ Need more works because help texts are much, much longer than typical UI strings ○ Need more skilled translator who are able to process complete, long sentences ● Since UI has not been translated yet, this initial help version will need to preserve UI strings (not to use translated ones) ● If UI has started to be translated, then this help version will need to be modified ○ Two translation variants? One with untranslated UI, the other with translated UI? ○ How do we call that language variant? ■ id, id_ID, en_ID, id_EN, id@latin
- 18. Thank You
- 19. Q & A