From Fedora Project Wiki
< L10n
(page creation) |
(add guidelines example) |
||
| Line 3: | Line 3: | ||
Why should the Fedora community pay to host someone else project? | Why should the Fedora community pay to host someone else project? | ||
* We support any project sharing the same values as the Fedora Project | * We support any project sharing the same values as the Fedora Project | ||
* | * To improve upstream i18n support | ||
* It is a source of growth of our community | * It is a source of growth of our community | ||
| Line 9: | Line 9: | ||
* Team management and review (--> quality of translation) | * Team management and review (--> quality of translation) | ||
* Upstream contribution to improve localization features | * Upstream contribution to improve localization features | ||
Upstream project: | |||
* MUST credit translators in application and release notes | |||
* MUST use named variables | |||
* SHOULD prevent sentence splits | |||
* SHOULD enable translation of man pages | |||
* SHOULD enable translation of documentation | |||
References: | |||
* https://wiki.gnome.org/TranslationProject/DevGuidelines | |||
* https://community.kde.org/Guidelines_and_HOWTOs/Internationalization | |||
Revision as of 06:08, 7 February 2020
Using the Fedora translation platform is easy, but what is the difference between it and other translation platforms?
Why should the Fedora community pay to host someone else project?
- We support any project sharing the same values as the Fedora Project
- To improve upstream i18n support
- It is a source of growth of our community
Why would a project use our infrastructure?
- Team management and review (--> quality of translation)
- Upstream contribution to improve localization features
Upstream project:
- MUST credit translators in application and release notes
- MUST use named variables
- SHOULD prevent sentence splits
- SHOULD enable translation of man pages
- SHOULD enable translation of documentation
References: