6 replies to this topic

[Goofy]

If you are an extension developer wishing to get translations for AMO metadata fields as mentioned on this page there are various possibilities:

* Your extension is already submitted here, you can just use your own extension topic to add a request for AMO metadata translation (example here), or use this very sub forum if you prefer to get a separate thread.

* Your extension is not yet submitted here, you are welcome to do it on this page , but you can request for AMO metadata translation anyway.

1. Create a new topic here with a title of this format

[AMO] Extension Name

2. Drop a little message with details or instructions you wish and paste your en-US metadata

3. Volunteer translators will answer on the same topic and attach their language fields as a single .txt file (or paste their translation in their answer)

Note that in the future, the AMO fields replica will be fully implemented in the Web Translation System

[peteburgers]

I've just had a thought - I'm considering adding a "fake" .properties file in the extension I submit to Babelzilla that contains the text for the AMO page. That way all of the translations can be done in one place in the WTS.

This could be extended to including help webpage content, etc.

It'll be great when this is handled in the WTS, but in the meantime what do you think?

[Goofy]

I've just had a thought - I'm considering adding a "fake" .properties file in the extension I submit to Babelzilla that contains the text for the AMO page. That way all of the translations can be done in one place in the WTS.

This could be extended to including help webpage content, etc.

It'll be great when this is handled in the WTS, but in the meantime what do you think?

Of course yes it is handy solution, just drop your sentences with a variable for each, as in usual properties files.

summary=blah blah
description=blah blah
devcomment=jjkù
...

[eviljeff]

I've just had a thought - I'm considering adding a "fake" .properties file in the extension I submit to Babelzilla that contains the text for the AMO page. That way all of the translations can be done in one place in the WTS.

This could be extended to including help webpage content, etc.

It'll be great when this is handled in the WTS, but in the meantime what do you think?

I'm going to write an add-on that automates extracting the information from the properties file and copying to the AMO page. Is there any kind of standard name that's become adopted for this "fake" file?

[markh]

I'm going to write an add-on that automates extracting the information from the properties file and copying to the AMO page. Is there any kind of standard name that's become adopted for this "fake" file?

I'm afraid not, so you're free to set the standard. How about ‘amo.properties’?

[eviljeff]

I'm afraid not, so you're free to set the standard. How about ‘amo.properties’?

that was my guess too I've specified it as a pref so it could be changed anyway.

Just need to iron out a bug and then I'll stick up version 0.1 on amo. At the moment it only has one string and thats the name of the Addon in the menu so localisation can wait till 0.2
Hopefully people will find it useful.

[eviljeff]

that was my guess too I've specified it as a pref so it could be changed anyway.

Just need to iron out a bug and then I'll stick up version 0.1 on amo. At the moment it only has one string and thats the name of the Addon in the menu so localisation can wait till 0.2
Hopefully people will find it useful.

Okay, I've got to version 0.2 and it needs some localisation. The more locales I get the better I can test the add-on with the locales!
http://www.babelzilla.org/forum/index.php?showtopic=4601