Why can't I approve translation imports on my own project?

Asked by Michael Mulqueen

Why can't I approve translation imports on my own project?

Project: https://translations.launchpad.net/zimcapture/

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Jeroen T. Vermeulen (jtv) said :
#1

You've uploaded an XPI file called zimcapture.xpi. This is incorrect. XPI doesn't really have templates; the en_US "translation" acts as the template instead. So please upload the US-English XPI with the name "en-US.xpi" (note convention in the XPI world is to use a dash there, not an underscore) and that will be recognized as your template.

Another issue is that a manual upload still needs to be reviewed. With gettext this wouldn't be an issue; you'd just have those imported from your branch. But you probably don't want to keep a built version of your XPI in your branch. But once your template is reviewed, all future uploads for trunk should be approved automatically.

Revision history for this message
Michael Mulqueen (michael.mulqueen) said :
#2

I'm a bit unclear about what should actually be in en-US.xpi (and in
fact, I'd rather upload en-GB). Is it just the normal xpi renamed or
what? After all, you can have multiple languages in an xpi file.

On Thu, Jul 1, 2010 at 8:10 AM, Jeroen T. Vermeulen
<email address hidden> wrote:
> Your question #116292 on Launchpad Translations changed:
> https://answers.edge.launchpad.net/rosetta/+question/116292
>
>    Status: Open => Answered
>
> Jeroen T. Vermeulen proposed the following answer:
> You've uploaded an XPI file called zimcapture.xpi.  This is incorrect.
> XPI doesn't really have templates; the en_US "translation" acts as the
> template instead.  So please upload the US-English XPI with the name
> "en-US.xpi" (note convention in the XPI world is to use a dash there,
> not an underscore) and that will be recognized as your template.
>
> Another issue is that a manual upload still needs to be reviewed.  With
> gettext this wouldn't be an issue; you'd just have those imported from
> your branch.  But you probably don't want to keep a built version of
> your XPI in your branch.  But once your template is reviewed, all future
> uploads for trunk should be approved automatically.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https://answers.edge.launchpad.net/rosetta/+question/116292/+confirm?answer_id=0
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.edge.launchpad.net/rosetta/+question/116292
>
> You received this question notification because you are a direct
> subscriber of the question.
>

Revision history for this message
Jeroen T. Vermeulen (jtv) said :
#3

Launchpad only supports one language per XPI, and is hardwired to see en-US.xpi as the template. The language inside the manifest is ignored as far as I remember, so just uploading en-GB.xpi but with with the name changed to en-US.xpi should work. Spelling "colour" correctly may confuse a few en-US readers though. :-)

Can you help with this problem?

Provide an answer of your own, or ask Michael Mulqueen for more information if necessary.

To post a message you must log in.