bzr-l10n team mailing list archive

[David Planella <david.planella@xxxxxxxxxx>]

El Mo 22 de 03 de 2010 a les 12:30 +0200, en/na Alexander Belchenko va
escriure:
> David Planella пишет:
> > 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.
> 
> OK, this is may case actually. Although I don't do translations on 
> regular basis but from time to time I'd like to get my 2 cents in.
> 
> I'll think about joining that group. Although I'm not really sure I have 
> enough resources to translate other projects.
> 
> I will change the permissions now and will see how it's going.

For the benefit of others following the discussion, I've had a chat with
Alexander and he's decided to change the permissions to Structured now.

For those languages which haven't got a team in the Launchpad
Translators group, permissions will be effectively Open, and for those
with a team, the team members will act as reviewers and will be able to
submit translations and accept the suggestions from everyone else.

https://translations.launchpad.net/+groups/launchpad-translators

For those interested in creating a new translation team, do ask us by
filing a support request, and we'll guide you through the process of
creating one and appointing it for the translation in your language:

https://answers.launchpad.net/rosetta/+addquestion

> I'll come back to automatic import/export a bit later. Today I'm OK with 
> manual process we have, but if somebody else (Ian?) will want to use 
> automatic, I'm OK.
> 

Sure, ultimately it's the developer's decision. Let me know if I can
help you in setting up automatic imports/export when you come back to
it.

> >> 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.
> 
> Excuse me, but those prefixes is not my idea. That's exactly what I've 
> got from tarball with translations exported from LP. Initially (in 
> 2007-2008) LP exported translations without that domain prefix. But then 
> in 2008 or 2009 it suddenly starts to add that prefix to the files.
> I have no idea why but I've just adjusted my import script and go on.
> 

Ah, that's true, sorry. That's a bug in the (manual) export from
Launchpad. I would still recommend you to work around it by letting your
'import_po' script rename the files to ll.po instead of qbzr-ll.po. 

Regards,
David.

-- 
David Planella
Ubuntu Translations Coordinator
david(dot)planella(at)ubuntu(dot)com
www.ubuntu.com

Attachment: signature.asc
Description: Això és una part d'un missatge signada digitalment