Hi Alexander,
El dv 19 de 03 de 2010 a les 17:54 +0200, en/na Alexander Belchenko va
escriure:
Hi David,
Thanks for sharing your expertise and valuable hints.
I have some questions, see below.
David Planella пишет:
I've noticed that both are translated with Open permissions. This is ok
if that is your decision, but perhaps you could consider using another
permission policy that puts the balance more on the quality rather than
on the quantity of translations.
The Launchpad help page summarizes the permission policies very well:
https://help.launchpad.net/Translations/YourProject/PermissionPolicies
I'd personally recommend using a Restricted policy, assigned to the
Launchpad Translators group [1] [2]
With this type of permission, everyone with a Launchpad account will be
able to submit translations, which will then have to be reviewed by a
group of trusted translators before being included in the program.
OK, I understand the value of switching to Restricted policy.
But I have one question though. Is it will be still possible for me to
upload POT templates via web-interface? Or I as maintainer of the
project, will be eliminated from translation process at all?
That setting only affects who can submit translations for the project.
It has no effect on the maintainership processes. You will still be able
to upload POT templates through the web interface.
There is something else: perhaps this is a corner case, but I thought
I'd mention it anyway. It might be that you are a maintainer and a
translator at the same time. In that case, if you'd like to submit
translations for your language and don't want to join a translation
team, you could still commit your translations directly to the code.
Although I'd recommend rather joining the translations team and
collaborating with, rather than bypassing them.
2) There is some restrictions on naming of POT and used directories. I
don't like the idea to put the messages.pot to the root of the
development tree, as I can see on the screencasts.
Perhaps there has been a misunderstanding here. You don't need to change
your current layout.
Looking at
http://bazaar.launchpad.net/~qbzr-dev/qbzr/trunk2a/files/head%3A/po/ and
http://bazaar.launchpad.net/~bzr-explorer-dev/bzr-explorer/trunk/files/head%3A/po/
po/qbzr.pot and po/explorer.pot are absolutely fine.
You see that the templates comply with the import policy as outlined in
https://help.launchpad.net/Translations/YourProject/ImportPolicy#Sample%
20directory%20layout
That policy was drafted following standard GNU naming practices, and
it's the one most translatable Open Source projects follow.
There is something I should mention regarding the translations, though.
It is a convention to name them simply after the language code (e.g.
ll.po or ll_CC.po). That is, simply 'ar.po' and 'zh_CN.po' instead of
'explorer-ar.po' and 'explorer-zh_CN.po'. If I'm not mistaken, the
convention stems from some build systems relying on that naming scheme,
and it makes easier to identify the files with language codes.
For this reason, I'd recommend you to remove the 'explorer-' and 'qbzr-'
prefixes from the .po files.
