From Fedora Project Wiki
m (→Reach user: added : badges for l10n) |
|||
| Line 10: | Line 10: | ||
== Reach user == | == Reach user == | ||
* When selecting a new language, add a l10n welcome message and a way to point to | * When selecting a new language, add a l10n welcome message and a way to point to | ||
* Create badges for localization contributors base on number of different projects edited with number of words translated | |||
= Zanata = | = Zanata = | ||
Revision as of 12:46, 10 December 2015
g11n
Organization
- List Fedora website and tell translation status : is translatable ? if yes how ? if no why ?
- Make sure with Docs Team we'll never have to translate such difficult changelog as Perl's one : https://docs.fedoraproject.org/en-US/Fedora/23/html/Release_Notes/sect-Release_Notes-Changes_for_Developers.html#sect-devel
- Refresh l10n pages for Team's
Bugs
- Make fedmenu translatable : https://github.com/fedora-infra/fedmenu
Reach user
- When selecting a new language, add a l10n welcome message and a way to point to
- Create badges for localization contributors base on number of different projects edited with number of words translated
Zanata
Tiny improvements :
- Translation Memory : when accessing origin of suggestion, add a direct link to source file to correct it
- Translation Memory : when accessing origin of suggestion, list all results
- Document lock : when a document is locked, write explicitly who to contact to grant access
- Add a button to file a bug about wrong English translation
- Where do we translate Zanata's 1st page ?
Activity
- Add a feed to know when new document or versions are added to project
- Add a feed to know when new strings are added to project
- Add a feed to know the activity of a translation team
- Add a feed to know what append last on a project
Automation
- Add a tool that suggest to copy 100% matching string, at least on same project (documentation)
- Make every po file available for download once a day or week (manual search of typos)