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
Trados XLIFF w/o line breaks crashes Sisulizer - 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: Wed Sep 27th, 2017 07:11 am
PM Private Upload Quote Reply
thbeckmann
Member


Joined: Thu May 28th, 2015
Location:  
Posts: 71
Status: 
Offline
Sisulizer crashes on importing the upper version of the same XLIFF file with "exception 2": "Invalid XML file" - which is incorrect, the XML is well formed, but the body tag is written in one line (of >21.000 characters).

Sisulizer should answer with a better error message, at least...

Thomas

Attachment: 201709270837_XLIFF.png (Downloaded 13 times)

Back To Top PM Private Upload Quote Reply

 Posted: Tue Oct 10th, 2017 03:32 am
PM Private Upload Quote Reply
Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 1977
Status: 
Offline
Hi Thomas,

Can you send us the XLIFF file that made Sisulizer to crash.

Ilkka



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

 Posted: Tue Oct 10th, 2017 07:51 am
PM Private Upload Quote Reply
thbeckmann
Member


Joined: Thu May 28th, 2015
Location:  
Posts: 71
Status: 
Offline
I have been sending the file(s)!

I don't mind a better error handling, but the support of Flare XLIFF files is way more important for us...

Thanks, Thomas

Back To Top PM Private Upload Quote Reply

 Posted: Tue Oct 10th, 2017 02:19 pm
PM Private Upload Quote Reply
Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 1977
Status: 
Offline
Hi Thomas,

Thank you for the files. unfortunately your XLIFF files use invalid XML. The first invalid part is this

<mrk mtype="protected" mid="2" MadCap:segmentStatus="Untranslated" MadCap:matchPercent="0"> < />


A valid XML would be

<mrk mtype="protected" mid="2" MadCap:segmentStatus="Untranslated" MadCap:matchPercent="0" />


or

<mrk mtype="protected" mid="2" MadCap:segmentStatus="Untranslated" MadCap:matchPercent="0"> </mrk>


XLIFF is based on XML and all XLIFF files must be valid XLM.

Ilkka



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

 Posted: Tue Oct 10th, 2017 02:30 pm
PM Private Upload Quote Reply
Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 1977
Status: 
Offline
What software did you use to create the XLIFF file?

Ilkka



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

 Posted: Tue Oct 10th, 2017 02:40 pm
PM Private Upload Quote Reply
Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 1977
Status: 
Offline
Another file you sent: "Anlegen von Probekarten.htm ms.xlf" uses valid XML.



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

 Posted: Tue Oct 10th, 2017 02:57 pm
PM Private Upload Quote Reply
thbeckmann
Member


Joined: Thu May 28th, 2015
Location:  
Posts: 71
Status: 
Offline
Hm, are you sure there's no </mrk> behind the statement? The empty XML-tags should be ok.
I checked the file with an XML-Editor and it seemed to be well formed.
I did not generate it on my own, but it has been written by Madcap Flare.

Last edited on Tue Oct 10th, 2017 03:00 pm by thbeckmann

Back To Top PM Private Upload Quote Reply

 Posted: Tue Oct 10th, 2017 04:44 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3757
Status: 
Offline
Hi Ilkka,

MadCap Flare is popular online help authoring tool: https://www.madcapsoftware.com/ . They also have own localization tool MadCap Lingo. MadCap tools use XLIFF format for exchange localization resources. Some company sent to me set of their XLIFF files generated by Flare in the past. Unfortunately, I couldn't find correct method of importing those resources to Sisulizer project. Ilkka, if you want, I'll sent those files to you for preview.

Janusz



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

 Posted: Tue Oct 10th, 2017 05:43 pm
PM Private Upload Quote Reply
thbeckmann
Member


Joined: Thu May 28th, 2015
Location:  
Posts: 71
Status: 
Offline
As Janusz reports, it seems to be a problem of Madcap - but I have no idea, how XLIFF files should look out. If any one of you could give me some hints, I'd address the Madcap team.

Thomas

Back To Top PM Private Upload Quote Reply

 Posted: Wed Oct 11th, 2017 02:15 am
PM Private Upload Quote Reply
Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 1977
Status: 
Offline
The problem is < /> element. In XML each element has to have a name. There cannot be empty or even single space named elements.

Even if they fix the XML format to be valid Sisulizer still cannot import that data. The data they have contains paragrahps with several segments and formatting information. This result to extremely complex XLIFF data. It cannot be importer to Sisulizer.

You can import translations from XLIFF if they are plain text without segmentation and formatting information.

Ilkka



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

 Posted: Wed Oct 11th, 2017 03:52 am
PM Private Upload Quote Reply
thbeckmann
Member


Joined: Thu May 28th, 2015
Location:  
Posts: 71
Status: 
Offline
Thank you for this information! I'm going to discuss this!

Back To Top PM Private Upload Quote Reply

Current time is 03:52 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Trados XLIFF w/o line breaks crashes Sisulizer



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

Sisulizer software localization tool - Three simple steps to localize