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]

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]

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

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]

Moi, kaveri

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]

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

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

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.