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

[markh]

Dutch locale released 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

 nl.zip ( 2.85K ) Number of downloads: 2

[Marky Mark DE]

Dutch locale released 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

 nl.zip ( 2.85K ) Number of downloads: 2

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]

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]

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]

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
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!

Attached File(s)

 help.html ( 8.74K ) Number of downloads: 1

 

[markh]

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

Recoded version attached here:
 help.html ( 4.24K ) Number of downloads: 4

[Marky Mark DE]

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

Recoded version attached here:
 help.html ( 4.24K ) Number of downloads: 4

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]

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.