Support forum of the software localization tool Sisulizer


.NET, Delphi, ... - Sisulizer Localization Tool Support Home

Get in contact with the makers of Sisulizer.
Our forum is open for all questions around Sisulizer from customers and prospects.
Don't hesitate to register and ask. The Sisulizer team will answer ASAP.

Search     Help Home Sisulizer Website Download
Search by username
Not logged in - Login | Register 

 Moderated by: Sisusupport, Renate.Reinartz, Markus.Kreisel, Ilkka.Salmenius
New Topic Reply Printer Friendly
Xliff with tags generates HTML-encoded tags in the target - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Thu Jul 11th, 2019 04:05 pm
PM Private Upload Quote Reply
Olivier_ho
Member
 

Joined: Wed Jul 23rd, 2008
Location: Marseille, France
Posts: 160
Status: 
Offline
If you have an xliff file containing some supported tags (<ept>, <bpt>..), then the generated target contains "&lt;bpt some tag attributes... /&gt;" in the translation. Consequently, the translations are not correctly imported back into the original software.

The translation should keep the tags as valid HTML tags in the <target></target> values.

See the private upload project for an example.

Best regards,
Olivier

Last edited on Thu Jul 11th, 2019 04:07 pm by Olivier_ho

Back To Top PM Private Upload Quote Reply

 Posted: Thu Jul 11th, 2019 04:23 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3297
Status: 
Offline
Tags inside XML (and XLIFF is based on XML) must always be proteced by
<![CDATA

tags to be imported and exported correctly.

Markus

[code]



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Fri Jul 12th, 2019 03:15 pm
PM Private Upload Quote Reply
Olivier_ho
Member
 

Joined: Wed Jul 23rd, 2008
Location: Marseille, France
Posts: 160
Status: 
Offline
I'm afraid, but the XLIFF format documentation does not indicate that we should use <!CDATA tags for those tags:
http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.html
See: 2.4 inline elements.

Note that we don't master the production of the XLIFF, which is generated by the software we want to translate projects from (Walkme).

Back To Top PM Private Upload Quote Reply

 Posted: Fri Jul 12th, 2019 03:51 pm
PM Private Upload Quote Reply
Olivier_ho
Member
 

Joined: Wed Jul 23rd, 2008
Location: Marseille, France
Posts: 160
Status: 
Offline
Hi again,
I tried several other things, including using Sisulizer 3.0, and working with the target file (corrected with proper tags), and now I can't reproduce anymore.
There is something weird, I cannot dig deeper today, I will try again when I'm back from holidays.

Back To Top PM Private Upload Quote Reply

 Posted: Fri Jul 12th, 2019 04:34 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3297
Status: 
Offline
Hi,

Sisulizer uses its own XML routines to parse these XML files. And from my experience it always needs these tags even if the XLIFF documentation is not mentioning that.

Perhaps the makers of XLIFF didn't want to repeat the basic XML rules in teir documentation. By design XML was made to be very strict - in contrast to HTML.

Have nice holidays anyway.

Markus



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

Current time is 12:51 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Xliff with tags generates HTML-encoded tags in the target



WowUltra modified by Sisulizer Copyright © 2007-18 by Jim Hale - Based on WowBB Copyright © 2003-2006 Aycan Gulez

Impress - Privacy statement

Sisulizer software localization tool - Three simple steps to localize