Roundtable: improve translations
Roundtable discussion about what we can improve regarding translations for the Karmic cycle
Blueprint information
- Status:
- Complete
- Approver:
- Martin Pitt
- Priority:
- Medium
- Drafter:
- Arne Goetje
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Not started
- Milestone target:
- None
- Started by
- Completed by
- Martin Pitt
Whiteboard
2009-06-01, pitti: This spec contains a lot of actionable items for a lot of different places and is marked "informational". Please split out the agreed points to separate per-topic blueprints (or bug reports for small items).
BoF notes:
---------------
== Launchpad items, collected with Jeroen Vermeulen ==
-> file bugs and blueprints for Rosetta
Launchpad Translations work that could help Ubuntu:
* improve translation import approval
* get the translation domain from the .pot filename
* check if the same template exists already in the database, but for a different source package
* detect if a template has been renamed by using heuristics
• revert-
• Allow translators to filter the templates overview for upstream category (Gnome, KDE, Debian, Ubuntu, Unclassified). Look for debtags keys "suite::gnome," "suite::kde," "suite::debian," "suite::mozilla." Some package headers provide origin::ubuntu.
• Why do we get multiple architecture-
• XPIPO imports for XPI-based translations. Assume every PO file uploaded to an XPI-based template is in XPIPO format: ignore msgids since they map to "English translations" which may have changed. Identify messages by the file's msgctx instead; a message without context is an error.
• Translate help files: recognize help templates on import somehow, and tag their PO files on export. Then we can pick them out of the language pack & convert them to their ultimate formats. Analyze Gnome help POT files to see if there's anything we can recognize them by.