|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Problems with XML Attribute - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
dke Member
|
Hello, I'm trying to translate an XML which corresponds roughly to a help page structure: <help-page> <contents> <p> <lnk target="dont_translate1">translate1</lnk> <br/> translate <u>underlined</u> <br/> translate <u>underlined</u> <br/> </p> </contents> </help-page> Within the Import Wizard, I check the whole <p>, but the 'target' attribute is omitted in the output. The only way I found to include 'target' in the output is to uncheck <p> and to check <lnk>, Text-Element and <u> instead. But this way I give up the flexibility regarding formatting tags like <u>, because they are translated separately in this case, which might not be wanted in a particular translation. Even if I check 'target' in addition to <p> (which should enable translation for 'target' in my opinion), neither 'target' is offered translation for, nor is it written to the output untranslated. What am I doing wrong? Kind regards, dke
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi dke, I ask our R&D what we can do. Probably we have to add the lnk tag to a list of tags having attributes. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello, You can't translate attribute value and tag value as one string for items like this: <p><tag attribute="text">text1</tag></p> so you can translate both items only, if you split it to separated rows by selecting appropriated sub-items in tags tree instead parent item (in our cases parent item is <p> tag). Of course, this solution split to separated rows also other sub-items. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
dke Member
|
Thanks for your fast answers. _(at)_Janusz: actually I don't want to translate tag- and attribute value. I want to translate the contents of <p> (including all the sub-tags that might be there) in one piece, AND I want the 'target' attribute of the <lnk> tag to be copied to the output untranslated. But unfortunately it is not copied, if I check <p>. When I played with the Wizard options, I just realized that I can also check both, <p> and additionally 'target', and I expected that Sisulizer would offer me a separate translation item for 'target', but it didn't (checking 'target' seems to have no effect in this case) - but that's maybe a different story. Thanks in advance, dke
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, Yes, you are right, Sisulizer doesn't copy "target" attribute if you select to localization parent item, that is, <p> tag. Markus already forwarded it to our developers. Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
dke Member
|
Thanks a lot, dke
|
||||||||||||||||
| |||||||||||||||||
| Current time is 06:05 am | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Problems with XML Attribute | |
Sisulizer software localization tool - Three simple steps to localize
