UbuntuTranslationsCoordinators
Differences between revisions 14 and 39 (spanning 25 versions)
|
Size: 10078
Comment:
|
← Revision 39 as of 2013-07-13 15:21:10 ⇥
Size: 3341
Comment: remove obsolete page about Karmic KDE translations
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| = Purpose = | |
| Line 6: | Line 7: |
| == Launchpad Translations import queue management == | The Ubuntu Translations Coordinators team is a group of community members actively involved in the Ubuntu translation process who take care of all the associated administrative and coordinative actions. They will also act as mediators and take a leading role if disputes or conflict situations regarding translations arise. |
| Line 8: | Line 9: |
| === Import queues === * [[https://translations.edge.launchpad.net/ubuntu/hardy/+imports?field.filter_extension=pot&field.filter_status=NEEDS_REVIEW|Hardy]] * [[https://translations.edge.launchpad.net/ubuntu/intrepid/+imports?field.filter_extension=pot&field.filter_status=NEEDS_REVIEW|Intrepid]] * [[https://translations.edge.launchpad.net/ubuntu/jaunty/+imports?field.filter_extension=pot&field.filter_status=NEEDS_REVIEW|Jaunty]] * [[https://translations.edge.launchpad.net/ubuntu/karmic/+imports?field.filter_extension=pot&field.filter_status=NEEDS_REVIEW|Karmic]] |
* [[https://launchpad.net/~ubuntu-translations-coordinators/+mugshots|Team members in Launchpad]] * [[../Translations/Contact#UTC|Contact]] |
| Line 14: | Line 12: |
| === The auto-approver script === | {i} If you are instead looking for information on how to translate Ubuntu, you probably want to go to the general [[Translations|Ubuntu Translations site]]. |
| Line 16: | Line 14: |
| * Runs every ten minutes if it finishes in less than that, but with a long queue it may take up to an hour (or even two) for it to complete. | = Actions = |
| Line 18: | Line 16: |
| === General rules when doing approvals === * '''We only approve .pot templates''', not .po files. An exception to this rule is when a .po file has been uploaded manually. But normally, approving the template will pull in all .po files associated with it. * '''We don't approve help files, man pages, test cases and other package-specific documentation'''. Those items should set to "blocked". * "blocked" means the template won't show up again, "deleted" means the current entry is removed from the list. If there is a new upload of the same template, it will show up again. This is useful if there are two entries of the same template, dating from different package versions. In this case we would delete the old one and approve the new one. * When approving, we need to click onto the "Edit" button on the right hand side and fill in the template name and the translation domain. Usually the translation domain is the same name as the .pot file, just without ".pot". :) The template name is usually also the same, with two exceptions: 1. Underscores need to be replaced with hyphens ("_" -> "-"), 1. Usually the templates don't carry a package version number, while the translation domain and the .pot file do. This is actually a bug in the package and should be reported as such. '''.pot and .mo files should not contain version numbers'''. If you are not sure of the template name, click on the package name in the import queue to find out which templates exist already. * Sometimes it's necessary to dig in the source code of a package and build it locally to find out what to do with the templates. * If the .po files will not be compiled into .mo files during build time of the package, then we don't want those templates in our language-packs (and usually also not in Rosetta). Ubuntu-docs and debian-installer are accepted into Rosetta but will not be exported into language-packs for obvious reasons. For those templates the checkbox in the approval screen needs to be unchecked. |
''These are the actions or activities the team takes care of'' |
| Line 28: | Line 18: |
| === Checking package compatibility with language packs === | * [[/Actions/ImportQueueManagement|Ubuntu translations import queue management in Launchpad]] * [[/Actions/TranslationTeamsCoordination|Coordination of teams in the ubuntu-translators group]] * [[/Actions/LpTemplateAdministration|Administration of Ubuntu translation templates in Launchpad]] * [[/Actions/Announcements|Announcements related to translations]] * Bug triaging - note that this process is open to all the translations community, but the UTC team will generally take a more active role in filing and triaging bugs since they are the bugmail contact and usually the first ones to notice and report errors in the imports queue. * [[/Actions/AppointingNewMembers|Appointing new team members]] |
| Line 30: | Line 25: |
| There is nothing magic about language packs. In order to use the translations from langauge packs a package should read the .MO files from a predefined location specified at build time (/usr/share/locale-langpack/). | = Release process = |
| Line 32: | Line 27: |
| To check this functionalty you will need to build the binary package: | ''These are the regular actions the team takes care of during the release cycle'' |
| Line 34: | Line 29: |
| {{{ $ apt-get source PACKAGE_NAME $ find . -name "*.pot" $ dpkg-source -x PACKAGE_NAME.dsc $ cd PACKAGE_NAME $ debuild -us -uc $ find ./debian/PACKAGE_NAME -name "*.mo" }}} |
* Language packs * [[Translations/TranslationLifecycle/LanguagePackGeneration#RecipeLangpackSruUpdate|Initiate and coordinate stable release updates]] * Define the [[https://dev.launchpad.net/Translations/LanguagePackSchedule|language pack generation schedule]] * [[/Actions/LpTemplateAdministration#OpeningTranslations|Opening translations]] * [[/Actions/LpTemplateAdministration#SetTranslationFocus|Setting translation focus]] * [[/Actions/LpTemplateAdministration#FirefoxUploads|Importing Firefox translations]] * [[/Actions/Milestones/NonLanguagePackTranslationDeadline|Non language pack deadline actions]] * [[/Actions/Milestones/LanguagePackTranslationDeadline|Language pack deadline actions]] |
| Line 43: | Line 38: |
| If debuild will complain about unmet build dependencies, please install them. | = Ongoing projects = |
| Line 45: | Line 40: |
| Now we have the following case: | ''This is the list of ongoing projects the team is currently working on. Note that these are open to all community members to participate in. See also [[https://bugs.launchpad.net/ubuntu-translations/+bugs?field.tag=task|the tasks in Launchpad]]'' |
| Line 47: | Line 42: |
| ==== No POT file ==== | * [[/OngoingProjects/UnknownLanguages|Unknown languages]] * [[/OngoingProjects/UnknownDomains|Unknown translation domains]] -- almost a permanent project. * [[Translations/TemplatesPriority|Template prioritization]] * [[/OngoingProjects/ImportQueueCleaning|Import queue cleaning]] * [[/OngoingProjects/ExportsSchedule|Translation exports schedule]] * [[/Translations/Universe_Translations_in_LP|Universe translations in LP]] |
| Line 49: | Line 49: |
| If the first "find" command will not reveal any POT file, this means there are no strings available for translations and there is no way you can use Launchpad Translation for translating this package. | = Finalized projects = |
| Line 51: | Line 51: |
| If the source package is using a different format for handling the translation, please contact the package maintainer and see if the package can be converted to use gettext standards. The only exceptions are firefox and openoffice, but we will exclude them, as they require special/extra care. ==== No MO file ==== If the second "find" will not show any "MO" files, again the package can not be used with language packs". If the source package contains "POT" files, but the binary will not produce any "MO" files, this means that the translations are only used during the build phase, and not at runtime. For now on, you can block the specific "POT" files in the import queue, and inform the package maintainer that those translations can only be translated upstream. Also the package maintainer must take care not to include specific Ubuntu string in those "POT" files, of if he need to, then ask him to requiest help/guidance from UTCs. ==== MO file in /usr/share/locale ==== If the binary package contains "MO" files in /usr/share/locale, then evertying is OK and the "POT" template can be approved. ==== MO file in an arbitrary location ==== If the binary package contains "MO" files in arbitrary location and not at the "LOCALE" variable specified during build time, the package will not use the langauge packs. Please contact the package maintainer and see if you can modify to source package to use the standard LOCALE location. === Operations === The next sections provide step-by-step guides on how to perform some common operations when acting on the imports queue entries. ==== Disabling templates ==== 1. Uncheck the "Accept translations" checkbox 1. Uncheck the "Include translations for this template in language packs?" checkbox 1. Save changes ==== Renaming templates ==== 1. Locate the old template 1. Go to the old template and open the "Administrate" page 1. Rename the old template name and translation domain to the new one. If necessary, change the source package entry to the new package (if the template has been moved). * TODO, check: possibly renaming the template is enough, as the translation domain will be extracted from the approved new "Needs review" entry in the import queue. 1. Save the changes 1. In the import queue approve the new template with the same template name and translation domain like the one you have just modified 1. At this point the the new template and translations should be in the right place. '''Notes''': * Template names are internal to Launchpad and case-sensitive. We stick to using lower case names for convention. * Domain names should use the case format the application is using. * In case the new template has already been approved, we'll have a conflics and some manual work will be required (downloading translations and uploading them back again). That's the reason we follow the above procedure: updating the old template first to avoid such conflicts. === To do items === Items the UTC team needs to take action on: ==== Unknown translation domains ==== When generating language-packs, occasionally errors show up in the log. One of those errors is called "unknown translation domain", which indicates that a given translation domain is either not used by any package in 'main', or that the translation domain name is buggy (i.e. has been renamed or contains errors, like upper/lower case letters, etc.). For Karmic, the following translations domains have errors. We need to investigate how to resolve those errors. || '''Source package''' || '''Translation domain''' || '''Remarks''' || '''Resolution''' || || || bluetooth-manager || || || || || contact-lookup-applet || || || || || cupsddk || || || || || desktop-effects-kde || || || || || desktop_kdenetworkmanager || || || || || fast-user-switch-applet || || || || || initdb-8.3 || || || || || libmbca || || || || || libpq5 || || || || || libsmbios-2.2 || || || || || pg-config-8.3 || || || || || pg-controldata-8.3 || || || || || pg-ctl-8.3 || || || || || pg-dump-8.3 || || || || || pg-resetxlog-8.3 || || || || || pgscripts-8.3 || || || || || pidgin-libnotify || || || || || pidgin-otr || || || || || postgres-8.3 || || || || || psql-8.3 || || || || || pytz || || || || || seahorse-plugins || || || || || zope || || || ==== Unknown languages ==== The following languages don't have language-packs, because they don't have locale codes yet. The UTC team needs to get in touch with those who care about those languages ask them to create a locale and to submit it to upstream glibc. Also, if they need help, we should assist them with doing so. || '''Language code''' || '''Language''' || '''Contact person/team''' || '''Status''' || || ace || || || || || ak || || || || || ang || || || || || arn || || || || || ba || || || || || bal || || || || || bem || || || || || bho || || || || || bua || || || || || ce || || || || || ceb || || || || || ckb || || || || || co || || || || || cv || || || || || dsb || || || || || ewo || || || || || frm || || || || || frp || || || || || gn || || || || || grc || || || || || guc || || || || || haw || || || || || hil || || || || || inh || || || || || io || || || || || jbo || || || || || jv || || || || || kab || || || || || kbd || || || || || kok || || || || || ksh || || || || || lb || || || || || ln || || || || || mh || || || || || mo || || || || || mus || || || || || my || || || || || nap || || || || || no || || || || || oj || || || || || os || || || || || pam || || || || || pms || || || || || ps || || || || || qu || || || || || rm || || || || || rom || || || || || sco || || || || || sm || || || || || sml || || || || || sn || || || || || sw || || || || || syr || || || || || szl || || || || || tet || || || || || tlh || || || || || trv || || || Locale done; submitted to upstream || || udm@cyrillic || || || || || xal || || || || || zza || || || || === Other useful information === * [[https://dev.launchpad.net/Translations/LanguagePackSchedule|Language pack generation schedule]] |
* [[/OngoingProjects/SwitchToRestricted|Proposal to switch the ubuntu-translators group to a Restricted policy]] |
Purpose
The Ubuntu Translations Coordinators team is a group of community members actively involved in the Ubuntu translation process who take care of all the associated administrative and coordinative actions. They will also act as mediators and take a leading role if disputes or conflict situations regarding translations arise.
If you are instead looking for information on how to translate Ubuntu, you probably want to go to the general Ubuntu Translations site.
Actions
These are the actions or activities the team takes care of
- Bug triaging - note that this process is open to all the translations community, but the UTC team will generally take a more active role in filing and triaging bugs since they are the bugmail contact and usually the first ones to notice and report errors in the imports queue.
Release process
These are the regular actions the team takes care of during the release cycle
- Language packs
Ongoing projects
This is the list of ongoing projects the team is currently working on. Note that these are open to all community members to participate in. See also the tasks in Launchpad
Unknown translation domains -- almost a permanent project.
Finalized projects
UbuntuTranslationsCoordinators (last edited 2013-07-13 15:21:10 by fitojb)