Recommended Addon

[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

This post has been edited by RealRaven: Feb 3 2013, 13:19

[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]

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]

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

[Marky Mark DE]

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

okay hope i do it right in the future
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
I'm so sorry, don't have think about before!

[markh]

okay hope i do it right in the future
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
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

[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]

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.
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]

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