Help - Search - Members - Calendar
Full Version: SmartTemplate4 - Ver. 0.9.3pre46
BabelZilla Board > Extensions > Thunderbird
Pages: 1, 2
Marky Mark DE
Maintainer: Marky Mark DE
Creator: Axel Grude

Ext. Version: 0.9.3pre46
Release date: 2012-11-03
Description: The SmartTemplate4 Add-on can customize 'quote headers' per account.
Extension is compatible to: ( 2.0 - 2.17.*) ( PostBox 2.0.0 - 3.*) ( 3.1.7 - 18.*)

Included locales: de en-US es-ES fi fr it ja ja-JP nl oc pl pt-BR ru sr sv-SE uk uk-UA zh-CN zh-TW

View on WTS -- Download the extension
markh
Welcome! welcomeani.gif

Just a bit of information for you: in case you have some queries about the WTS, you can find our Wiki here!

In case you're looking for a specific translator, please see the list of available translators on BabelZilla.
When you select the desired one, you can send him/her a P.M. or an e-mail (if and when public).

You may also insert a new Topic in the Help Section, in order to ask for specific translations, to write a general request about missing translations, etc.

May I suggest you remove the locales that are currently filled with English strings? The WTS will generate them automatically when a translator registers.
Marky Mark DE
QUOTE (markh @ Jun 30 2011, 13:36) *
Welcome! welcomeani.gif

Just a bit of information for you: in case you have some queries about the WTS, you can find our Wiki here!

In case you're looking for a specific translator, please see the list of available translators on BabelZilla.
When you select the desired one, you can send him/her a P.M. or an e-mail (if and when public).

You may also insert a new Topic in the Help Section, in order to ask for specific translations, to write a general request about missing translations, etc.

May I suggest you remove the locales that are currently filled with English strings? The WTS will generate them automatically when a translator registers.



i hope i have do it now right... ;-)
im new here and it's really complicated ;-)
markh
QUOTE (Newcomer01 @ Jun 30 2011, 16:29) *
i hope i have do it now right... ;-)
im new here and it's really complicated ;-)

Almost; just update your chrome.manifest before the next time you update (no need to do it immediately) to reflect the locales actually present. I have removed all empty locales without an assigned translator from the database; the locales in the WTS are what should be reflected in chrome.manifest/install.rdf. wink.gif
Marky Mark DE
QUOTE (markh @ Jun 30 2011, 22:19) *
Almost; just update your chrome.manifest before the next time you update (no need to do it immediately) to reflect the locales actually present. I have removed all empty locales without an assigned translator from the database; the locales in the WTS are what should be reflected in chrome.manifest/install.rdf. wink.gif


thank you!
Okay then i know it in the future: i need only the strings in chrome.manifest which locale i have...locale that need part translations i can let in (string in chrome and folder)?
markh
QUOTE (Newcomer01 @ Jun 30 2011, 23:28) *
thank you!
Okay then i know it in the future: i need only the strings in chrome.manifest which locale i have...locale that need part translations i can let in (string in chrome and folder)?

Yes. Take a moment to browse through our Wiki (see link above), it might be useful at times wink.gif
teo
Polish locale released.

My locale you can download from WTS in the proper format. smile.gif
Marky Mark DE
QUOTE (teo @ Jul 1 2011, 20:30) *
Polish locale released.

My locale you can download from WTS in the proper format. smile.gif


Thank you!
But i must correct all translations... not your fault...the WTS has an Problem with html which don't displayed converted..;-)
maurojs10
QUOTE (Newcomer01 @ Jul 1 2011, 20:10) *
Thank you!
But i must correct all translations... not your fault...the WTS has an Problem with html which don't displayed converted..;-)


Do you refer to the strings pref_html.label , pref_rep_br.label , pref_rep_br.cap in "smartTemplate.dtd" ?

To avoid that problem in pt-BR locale, I am replacing:
  • <b> with &amp;lt;b&amp;gt;
  • </b> with &amp;lt;/b&amp;gt;
  • <br> with &amp;lt;br&amp;gt;
Marky Mark DE
QUOTE (maurojs10 @ Jul 2 2011, 17:48) *
Do you refer to the strings pref_html.label , pref_rep_br.label , pref_rep_br.cap in "smartTemplate.dtd" ?

To avoid that problem in pt-BR locale, I am replacing:
  • <b> with &amp;lt;b&amp;gt;
  • </b> with &amp;lt;/b&amp;gt;
  • <br> with &amp;lt;br&amp;gt;


yes that i mean. But unfortunly is it however you submit it in WTS in the downloaded files wrong...
By this reason was it really nice when you can download your translated files (smartTemplate.dtd (important), calender.properties and help.html) and edit this parts like your examples inside the quellcode with notepad or notepad++ and submit it as reply here or via PM.
It would be really nice when you can test your translation inside my addon...before you send this files to me... sorry for this problems and the additional work... i don't have any other idea when i can't speak your language to fix it byself....
maurojs10
QUOTE (Newcomer01 @ Jul 2 2011, 15:33) *
yes that i mean. But unfortunly is it however you submit it in WTS in the downloaded files wrong...
By this reason was it really nice when you can download your translated files (smartTemplate.dtd (important), calender.properties and help.html) and edit this parts like your examples inside the quellcode with notepad or notepad++ and submit it as reply here or via PM.
It would be really nice when you can test your translation inside my addon...before you send this files to me... sorry for this problems and the additional work... i don't have any other idea when i can't speak your language to fix it byself....


Brazilian Portuguese (pt-BR) locale is released.

I have tested the translated files downloaded from Babelzilla, and they work just fine. I just had to add the following in the "help.html", right after the opening "<head>" tag:

CODE
<meta http-equiv="content-type" content="text/html; charset=UTF-8">


Anyway, you can find those files attached for you convenience.

Click to view attachment

Thank you.
Marky Mark DE
QUOTE (maurojs10 @ Jul 2 2011, 23:24) *
Brazilian Portuguese (pt-BR) locale is released.

I have tested the translated files downloaded from Babelzilla, and they work just fine. I just had to add the following in the "help.html", right after the opening "<head>" tag:

CODE
<meta http-equiv="content-type" content="text/html; charset=UTF-8">


Anyway, you can find those files attached for you convenience.

Click to view attachment

Thank you.


THANK YOU!
You did an great job many thanks for ;-)
The Idea with the "<head>" tag is great, now it's an fallback to UTF8 charset and all will display correct.... the small things....
I will wait on other loacale then i publish it on AMO, feel free to use the Addon with your translation ;-)
markh
Dutch locale released cool.gif With the exception of the < b > and < /b > tags, all worked well with the hack maurojs has described. Please find the files below.

@Newcomer01: there is currently no possibility to avoid the issues you had with HTML tags; fixing them would create other problems. You could try hardcoding them into the xul file, or replacing them by %S entries unsure.gif

Click to view attachment
Marky Mark DE
QUOTE (markh @ Jul 3 2011, 18:46) *
Dutch locale released cool.gif With the exception of the < b > and < /b > tags, all worked well with the hack maurojs has described. Please find the files below.

@Newcomer01: there is currently no possibility to avoid the issues you had with HTML tags; fixing them would create other problems. You could try hardcoding them into the xul file, or replacing them by %S entries unsure.gif

Click to view attachment


Thank you.
Sorry can you make an example what you understand as "hardcoding"... i couldn't set an head in the xul to set an fallback to UTF8 or also...
Whats happend with the "%s" entries... sorry i'm new (in the mozilla hackerszeene *lol*) and must learn and when you have additional infos i like to hear about ;-)
Thank you

Marc
markh
QUOTE (Newcomer01 @ Jul 3 2011, 18:54) *
Thank you.
Sorry can you make an example what you understand as "hardcoding"... i couldn't set an head in the xul to set an fallback to UTF8 or also...
Whats happend with the "%s" entries... sorry i'm new (in the mozilla hackerszeene *lol*) and must learn and when you have additional infos i like to hear about ;-)
Thank you

Marc

Well, if you leave the HTML tags in question outside the strings and only localize the sections that do not give any problems.

For instance, replace inside settings.xul
CODE
tooltiptext="&pref_rep_br.cap;"

by
CODE
tooltiptext="&pref_rep_br.cap; &lt;br&gt;"

and remove the last bit from the localized string.

Mind you, I am not a coder at all, so others might be able to provide better advice than me on this matter. Not able to help at all on the %s, all I know is that it can be used, but I don’t have a clue how.
maurojs10
QUOTE (markh @ Jul 4 2011, 06:34) *
Well, if you leave the HTML tags in question outside the strings and only localize the sections that do not give any problems.

For instance, replace inside settings.xul
CODE
tooltiptext="&pref_rep_br.cap;"

by
CODE
tooltiptext="&pref_rep_br.cap; &lt;br&gt;"

and remove the last bit from the localized string.

Mind you, I am not a coder at all, so others might be able to provide better advice than me on this matter. Not able to help at all on the %s, all I know is that it can be used, but I don’t have a clue how.


I don't think that hardcoding <br> in settings.xul will work for all languages. I mean, <br> may be the last word of pref_rep_br.cap in English, Dutch and Portuguese, but it may come before in German and Japanese, for example.

English : pref_rep_br.cap = "NOTE: Will not replace new-line which following an HTML tag with <br>."
German : pref_rep_br.cap = "HINWEIS: Es wird keine Leerstelle innerhalb des HTML Tag mit <br> eingefügt"
Japanese : pref_rep_br.cap = "注:HTMLタグに続く改行は<br>に変換されません。"


Marky Mark DE
QUOTE (maurojs10 @ Jul 4 2011, 15:56) *
I don't think that hardcoding <br> in settings.xul will work for all languages. I mean, <br> may be the last word of pref_rep_br.cap in English, Dutch and Portuguese, but it may come before in German and Japanese, for example.

English : pref_rep_br.cap = "NOTE: Will not replace new-line which following an HTML tag with <br>."
German : pref_rep_br.cap = "HINWEIS: Es wird keine Leerstelle innerhalb des HTML Tag mit <br> eingefügt"
Japanese : pref_rep_br.cap = "注:HTMLタグに続く改行は<br>に変換されません。"

Yes you are right.
It's not the last Bit in all Languages... by this reason only my solution worked... unfortunly more work for an Translator sad.gif
Bullshit, but i can't change it...

By the way: i heared from many Translators that the helpfile (help.html) don't be generated by WTS System... i have attached here the en-US Helpfile for there Translations (edit with notepad or notepad++)
You can translate this one in your Language and attached this translated file here
Thanks for our great Job here!
markh
QUOTE (Newcomer01 @ Jul 5 2011, 12:17) *
By the way: i heared from many Translators that the helpfile (help.html) don't be gerate by WTS System... i have attached here the en-US Helpfile for there Translations (edit with notepad or notepad++)

I think that is due to the fact that is encoded as UTF-16 LE rather than UTF-8 (and DOS rather than UNIX). If recoded, it should display fine wink.gif

Recoded version attached here:
Click to view attachment
markh
QUOTE (Newcomer01 @ Jul 5 2011, 12:17) *
Yes you are right.
It's not the last Bit in all Languages... by this reason only my solution worked... unfortunly more work for an Translator sad.gif
Bullshit, but i can't change it...

Maybe you could consider breaking up the phrase into three sections then? Before and after? Can’t think of which right now, but I know it has been done in other extensions too.

Something like
CODE
tooltiptext="&pref_rep_br.cap.before; &lt;br&gt; &pref_rep_br.cap.after"
, where &pref_rep_br.cap.after could be just ‘.’ or the second section of the sentence.
Marky Mark DE
QUOTE (markh @ Jul 5 2011, 14:12) *
I think that is due to the fact that is encoded as UTF-16 LE rather than UTF-8 (and DOS rather than UNIX). If recoded, it should display fine wink.gif

Recoded version attached here:
Click to view attachment


Can you apply this corrected (with UTF-8 Head) help in the Base of the WTS?
My en-US Version that i have attached was the UTF-8 corrected "head tag" too.
Its better when all files can be generated in WTS when start a new translation...
ch-CN (current translation), ru and fr the help are not displayed / generated?
-> please fix all present BUGs if you can.
Thank you!
markh
QUOTE (Newcomer01 @ Jul 5 2011, 21:47) *
Can you apply this corrected (with UTF-8 Head) help in the Base of the WTS?
My en-US Version that i have attached was the UTF-8 corrected "head tag" too.
Its better when all files can be generated in WTS when start a new translation...
ch-CN (current translation), ru and fr the help are not displayed / generated?
-> please fix all present BUGs if you can.
Thank you!

Done. The missing help files are simply not there, but they will display in English when missing. This is not a bug, it is normal behaviour. By the way, the previous file I uploaded was recoded into UTF-8/UNIX, but it should be UTF-8/DOS for it to be displayed. Apologies.
Marky Mark DE
QUOTE (markh @ Jul 5 2011, 23:03) *
Done. The missing help files are simply not there, but they will display in English when missing. This is not a bug, it is normal behaviour. By the way, the previous file I uploaded was recoded into UTF-8/UNIX, but it should be UTF-8/DOS for it to be displayed. Apologies.


thanks for your Assistance ;-)
Lakrits
Swedish locale (sv-SE) added and released.
markh
QUOTE (Newcomer01 @ Jun 29 2011, 20:23) *
Note: Some Phrases in Locales (smarttemplate.dtd) are unfortunly translated by google Translator by this reason it would be nice, if you can review and test your translation.
When you have reviewed/test you translation, please set the Status in WTS to released.
Thank you!

That makes the language used very ugly. You probably had your reasons for this, but please try not to do that again, as it will give a very bad user experience. Use of the original English strings would probably have been better dry.gif
Akilles
I can't test my translation atm because I get a XML parsing error in the options dialog. I'm using TB 10.0.2 with clean profile.
I've attached picture of the options dialog with error.

(language in the dialog is Finnish as you might have guessed but it says the error is on line 67, column 12 if that's helpful at all)
Lakrits
QUOTE (Akilles @ Feb 21 2012, 14:39) *
I can't test my translation atm because I get a XML parsing error in the options dialog. I'm using TB 10.0.2 with clean profile.
I've attached picture of the options dialog with error.

(language in the dialog is Finnish as you might have guessed but it says the error is on line 67, column 12 if that's helpful at all)

Moi, kaveri smile.gif

The only thing in the string pref_html.label (smartTemplate.dtd) that could cause that error is the < and > characters in the HTML coding tags. But I don't know if you can use the lt and gt entities for it and still get the result you want inside the program. Worst case: Just remove the HTML tags.

Otherwise it's a character encoding error (it should be UTF-8 without BOM and not ANSI, which sometimes is the standard encoding in external editors).

Micke
markh
QUOTE (Lakrits @ Feb 21 2012, 16:49) *
Moi, kaveri smile.gif

The only thing in the string pref_html.label (smartTemplate.dtd) that could cause that error is the < and > characters in the HTML coding tags. But I don't know if you can use the lt and gt entities for it and still get the result you want inside the program. Worst case: Just remove the HTML tags.

Otherwise it's a character encoding error (it should be UTF-8 without BOM and not ANSI, which sometimes is the standard encoding in external editors).

Micke

That’s exactly it. The < and > can be replaced by their HTML codes to get the desired result. This is the case for three strings, not only this one!
Marky Mark DE
QUOTE (markh @ Feb 21 2012, 16:40) *
That’s exactly it. The < and > can be replaced by their HTML codes to get the desired result. This is the case for three strings, not only this one!


Yes but unfortunly i need the code examples in the addon which are displayed as the encoded (to HTML) one.
Those Phrases inside the addon
<b>bold</b>
<br> or for this Phrase
The Phrase in cambered Brackets {Cc: %cc(name)%} will only displayed if the variable %(name)% can be replaced
and other ones

those signs must replaced inside the dtd files with their entities (without spaces)
% = & # 37;
{ = & # 123;
} = & # 125;
< = & lt;
> = & gt;
and insteat of quoting marks like " " or ` ´ it is better to use the apostrophe '
otherwise you get this parsing error...
If you type this it as entitie inside the WTS System, those signs will be paste encoded in the export file too, mybe an fix inside this system will be great, you type e.g < br > and other, the System paste by automatically such signs in the file with the right entities cool.gif

I don't have an other idea for an workarround only as to export and change this inside the dtd file direct.

To find an other formular for the Phrases can be an other idea but i don't know that the sense of this phrases is in every locale the self if i change the Phrase and set this problematic strings in the xul direct and build the pharses arround them (Phrase split)....
Example:
The Phrase in cambered Brackets (ENTITY String for locale)
{Cc: %cc(name)%} (inside the xul code)
will only displayed if the variable (ENTITY String for locale)
%(name)% (inside the xul code)
can be replaced (ENTITY String again for locale)

but this is an job for an guy who has slay down father and mother...german collucation and means horror job, punishment
- simpler is to change those sings in the file biggrin.gif

I change the codes byself and test byself no problem, i know about this problems but i can't change if i need the encoded results.
UTF-8 without BOM makes some trouble but this is the only format in which i can realize locale.
Sorry for the problems which i make.
Akilles
Now everything I translated is gone in WTS =\ Fortunately I have a local backup.

This might be some kind of bug in the WTS as it says in "My Translation" page that everything is translated (100%) but when I actually go to the locale files nothing is translated.
Lakrits
QUOTE (Akilles @ Feb 22 2012, 16:24) *
Now everything I translated is gone in WTS =\ Fortunately I have a local backup.

This might be some kind of bug in the WTS as it says in "My Translation" page that everything is translated (100%) but when I actually go to the locale files nothing is translated.

Yep, the progress bars are notoriously unreliable, and it's a bug we know of. Sometimes they are green because the developer adds English strings to all locale files.

But as you have experienced the progress bars can't be used alone, you have to check the files anyway. Paskatilapalkki. wink.gif
Akilles
Ok, thanks for the info. I was successful at the testing of the translation (thanks to the advice I got here) so I uploaded the locale files to the WTS and set the translation status to Released.

@Lakrits: Almost proper Finnish. It should be "paskat tilapalkit" =)
Lakrits
QUOTE (Akilles @ Feb 22 2012, 22:01) *
@Lakrits: Almost proper Finnish. It should be "paskat tilapalkit" =)

Fennoswede raised in Sweden. Haven't spoken Finnish since I was about 6 years old smile.gif
Marky Mark DE
QUOTE (Akilles @ Feb 22 2012, 22:01) *
Ok, thanks for the info. I was successful at the testing of the translation (thanks to the advice I got here) so I uploaded the locale files to the WTS and set the translation status to Released.

@Lakrits: Almost proper Finnish. It should be "paskat tilapalkit" =)


Thanks for, i have test too and added the new locale to SmartTemplate4.
Feel free to enjoy them if we publish the new Version on AMO ;-)
I think i will change a little more before publish ;-)
Now i will upload the current version in the WTS in all locale i have add an new "Additional"
and i hope that you can check your translation again, i'm not sure that you have see this before... yes this was really the last change for now ;-)
<!ENTITY specform_note.label "The Phrase inside the cambered Brackets & # 123;Cc: & # 37;cc(name)& # 37;& # 125; will only displayed if the variable & # 37;cc(name)& # 37; can be replaced!">
This The Phrase inside the cambered Brackets is new in all locale (Google Translator again), i don't know why i have oversee this in the english one but now the Phrase is complete ;-)
Sometimes i hate myself ;-)

By this reason i have set all finished/published locale to "needs review" again... sorry!
Akilles
Finnish translation is done. As markh mentioned a few posts back, please don't use Google translator as it is harder to spot untranslated (or rather google-translated) strings from already translated strings.
Marky Mark DE
QUOTE (Akilles @ Feb 23 2012, 15:35) *
Finnish translation is done. As markh mentioned a few posts back, please don't use Google translator as it is harder to spot untranslated (or rather google-translated) strings from already translated strings.


yes but the problem is, that many translators need to much time to check/review her translations and i have to publish new versions.... should i publish incomplete files?
Yes i know too that other addon developer do this like this, but i think thats bad for users of this locale
In this case i translate with Google that i have better wrong things as nothing...
Hope you understand my line of thought
Akilles
Actually I don't. Google's translation for English->Finnish is so crappy that it is actually much better if the missing strings were in English than in confusing or wrong Finnish. In this case in Google's translation had some of the words in wrong grammatical case and some weren't translated at all. When the words have typos or other mistakes in programs, it gives off a cheap impression and that is something not a dev wants..
Google's translation is OK if you roughly want to know what is said in the text that is in a foreign language that you can't understand but it's not good for a proper translation.
Marky Mark DE
QUOTE (Akilles @ Feb 23 2012, 22:58) *
Actually I don't. Google's translation for English->Finnish is so crappy that it is actually much better if the missing strings were in English than in confusing or wrong Finnish. In this case in Google's translation had some of the words in wrong grammatical case and some weren't translated at all. When the words have typos or other mistakes in programs, it gives off a cheap impression and that is something not a dev wants..
Google's translation is OK if you roughly want to know what is said in the text that is in a foreign language that you can't understand but it's not good for a proper translation.


yes i understand your problem, you think it's better to mix english with the included language e.g english and finnish (only in this example here)?
What is with the solution which i made here right now?
To say hey here in ENTITY .... in this Phrase .... i have made changes, can you check your translation? is this better and more easy to handle for translators?
I do copy the true Phrase from english that you can see what the true descrition of it is....to find it in the file was not the biggest problem i think
And if i paste new ENTITY's, it will be only in english included that an translator see which string is new to translate
markh
QUOTE (Marky Mark DE @ Feb 24 2012, 12:22) *
yes i understand your problem, you think it's better to mix english with the included language e.g english and finnish (only in this example here)?
What is with the solution which i made here right now?
To say hey here in ENTITY .... in this Phrase .... i have made changes, can you check your translation? is this better and more easy to handle for translators?
I do copy the true Phrase from english that you can see what the true descrition of it is....to find it in the file was not the biggest problem i think
And if i paste new ENTITY's, it will be only in english included that an translator see which string is new to translate

Any new strings do not need to be pre-filled with either English or (machine-)translated strings, as long as they are added to the en-US files. The WTS will recognize the newly added strings and display them to translators as untranslated. This helps translators identify new strings easily, whereas if they are already prefilled they will need to look for either English text where it shouldn’t be, or check the strings on grammatical correctness. Most translators do not like to do that, and only having to add the strings to en-US will save you a lot of effort trying to already come up with (mostly awkward) translations.
If you want to publish incomplete locales to AMO because you want to implement new features or so, it is up to you to decide what to do. The preferred way would be to upload a beta here, get your translations and THEN upload to AMO. You can set a deadline and ask translators to provide their work prior to that date. After that, any incomplete locales can either be left out of the published extension or completed with English strings (an option would be to download the locale files from the WTS with missing strings replaced).
Anyway, if you use machine translation in a public version, you may also be hurting the translators’ feelings. Since you are stating their nicks in the About window, they might publicly be (incorrectly) depicted as bad translators using machine translation wink.gif
Marky Mark DE
QUOTE (markh @ Feb 24 2012, 14:22) *
Any new strings do not need to be pre-filled with either English or (machine-)translated strings, as long as they are added to the en-US files. The WTS will recognize the newly added strings and display them to translators as untranslated. This helps translators identify new strings easily, whereas if they are already prefilled they will need to look for either English text where it shouldn’t be, or check the strings on grammatical correctness. Most translators do not like to do that, and only having to add the strings to en-US will save you a lot of effort trying to already come up with (mostly awkward) translations.
If you want to publish incomplete locales to AMO because you want to implement new features or so, it is up to you to decide what to do. The preferred way would be to upload a beta here, get your translations and THEN upload to AMO. You can set a deadline and ask translators to provide their work prior to that date. After that, any incomplete locales can either be left out of the published extension or completed with English strings (an option would be to download the locale files from the WTS with missing strings replaced).
Anyway, if you use machine translation in a public version, you may also be hurting the translators’ feelings. Since you are stating their nicks in the About window, they might publicly be (incorrectly) depicted as bad translators using machine translation wink.gif


okay hope i do it right in the future wink.gif
Can you check this ENTITY
specform_note.label and set it after to released?
This was the last time that i paste things from google translator - promised!
And this Phrase was the last in which i have made changes since the last review...

NOTE: right now i have upload an changed version again, in all locale in which i have made changes and paste things from google translator, which are NOT reviewed right now i have set in the localized area in install.rdf <em:translator>Google Translator</em:translator> insteat of the Translator's Nick of BabelZilla.
Hope that's in our sense.
If the locale reviewed/fixed can set this Translator his Nick in install.rdf again.
With this solution is it impossible that an Translator which have translated an previous Version, shame on with his translation and my additional things from google trans wink.gif
I'm so sorry, don't have think about before!
markh
QUOTE (Marky Mark DE @ Feb 24 2012, 14:51) *
okay hope i do it right in the future wink.gif
Can you check this ENTITY
specform_note.label and set it after to released?
This was the last time that i paste things from google translator - promised!
And this Phrase was the last in which i have made changes since the last review...

NOTE: right now i have upload an changed version again, in all locale in which i have made changes and paste things from google translator, which are NOT reviewed right now i have set in the localized area in install.rdf <em:translator>Google Translator</em:translator> insteat of the Translator's Nick of BabelZilla.
Hope that's in our sense.
If the locale reviewed/fixed can set this Translator his Nick in install.rdf again.
With this solution is it impossible that an Translator which have translated an previous Version, shame on with his translation and my additional things from google trans wink.gif
I'm so sorry, don't have think about before!

No worries. I case you are curious about the functionalities of the WTS, you may find our Wiki an informative place wink.gif
urko
I have tested OK and released Spanish locale replacing the < > characters in my local files (I used pspad - UTF8, the "without BOM" option is not available), but when uploading to Babelzilla and downloading the files again these characters seem to be wrong again.
¿Could you check manually the three entities when downolading the Spanish locale?:
pref_html.label
pref_rep_br.label
pref_rep_br.cap
Marky Mark DE
QUOTE (urko @ Feb 26 2012, 12:56) *
I have tested OK and released Spanish locale replacing the < > characters in my local files (I used pspad - UTF8, the "without BOM" option is not available), but when uploading to Babelzilla and downloading the files again these characters seem to be wrong again.
¿Could you check manually the three entities when downolading the Spanish locale?:
pref_html.label
pref_rep_br.label
pref_rep_br.cap

Done!
Thank you, i have changed this. wink.gif
Oh by the way:
I have upload today an BETA Version of my Addon with a new Abouttab and for this i need some small translations again - see topic -> page 1.
Thanks to all for your great work!
markh
QUOTE (Marky Mark DE @ Feb 26 2012, 14:39) *
Oh by the way:
I have upload today an BETA Version of my Addon with a new Abouttab and for this i need some small translations again - see topic -> page 1.
Thanks to all for your great work!

Thanks for the heads up. Again, you did not need to add them to every locale in English, just en-US is sufficient. With a next upload, please leave the type of update untouched when asked; the default will reset every translation status to ‘needs update’ and will send an automatic update notification to all translators. You can use this to inform your translators about a new version upload wink.gif
maurojs10
I noticed the following URL is being used as the SmartTemplate4 address for all locales.

CODE
https://addons.mozilla.org/en-US/thunderbird/addon/324497


This will present the user a page in English, even if the user language is set to other than English.

My suggestion is to replace that URL with this one:

CODE
https://addons.mozilla.org/thunderbird/addon/smarttemplate4/


This way, the user will be redirected to a proper localized version of SmartTemplate4 page on AMO.
Marky Mark DE
QUOTE (maurojs10 @ Feb 26 2012, 22:28) *
I noticed the following URL is being used as the SmartTemplate4 address for all locales.

CODE
https://addons.mozilla.org/en-US/thunderbird/addon/324497


This will present the user a page in English, even if the user language is set to other than English.

My suggestion is to replace that URL with this one:

CODE
https://addons.mozilla.org/thunderbird/addon/smarttemplate4/


This way, the user will be redirected to a proper localized version of SmartTemplate4 page on AMO.


Thank you good Idea but i have en-us and de only... in this case i have set all languages to en-us only the de directed to de...
What will happen if the use have e.g. es-ES? Will he directed to the en-US version as default?
This Info is new by this reason i ask for
but okay i have changed all URLs in my local file to
https://addons.mozilla.org/thunderbird/addon/324497/
Better now?
Marky Mark DE
QUOTE (markh @ Feb 26 2012, 20:16) *
Thanks for the heads up. Again, you did not need to add them to every locale in English, just en-US is sufficient. With a next upload, please leave the type of update untouched when asked; the default will reset every translation status to ‘needs update’ and will send an automatic update notification to all translators. You can use this to inform your translators about a new version upload wink.gif

Okay thanks for our contribution, i will hold on this instruction in the future!
markh
QUOTE (Marky Mark DE @ Feb 27 2012, 09:53) *
Thank you good Idea but i have en-us and de only... in this case i have set all languages to en-us only the de directed to de...
What will happen if the use have e.g. es-ES? Will he directed to the en-US version as default?
This Info is new by this reason i ask for
but okay i have changed all URLs in my local file to
https://addons.mozilla.org/thunderbird/addon/324497/
Better now?

Perfect. AMO will default to en-US if the page for the user’s locale is missing. When linking to en-US, the entire site will display in English, while leaving out the locale reference will look for the user’s locale (say es-ES), display the site in es-ES, but display the add-on details in en-US. It will then look like this:
Click to view attachment
Marky Mark DE
QUOTE (markh @ Feb 27 2012, 11:01) *
Perfect. AMO will default to en-US if the page for the user’s locale is missing. When linking to en-US, the entire site will display in English, while leaving out the locale reference will look for the user’s locale (say es-ES), display the site in es-ES, but display the add-on details in en-US. It will then look like this:
Click to view attachment

ah okay good to know biggrin.gif
Akilles
Finnish translation is released in WTS. I've corrected a little typo in errors.properties, so could you update that file as well.
Marky Mark DE
QUOTE (Akilles @ Feb 28 2012, 13:12) *
Finnish translation is released in WTS. I've corrected a little typo in errors.properties, so could you update that file as well.


okay thank you and especially for the note that you have checked/corrected other files too!
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2013 Invision Power Services, Inc.