Exchange with XLIFF file format - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ...

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.

Not logged in - Login | Register

.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Exchange with XLIFF file format

Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius

New Topic

Printer Friendly

Exchange with XLIFF file format - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support

Author

Post

Posted: Fri Aug 20th, 2010 10:41 am

Private Upload

Quote

hokno2
Member

Joined:	Thu Jul 8th, 2010
Location:
Posts:	29
Status:	Offline

Hello,
it is the first time that we use Sisulizer for a translation with this big scale of operations. (8 Languages with more than 2000 words and sentences)
So i have some common question and some more detailed questions to make sure that everything is working well.
The translation will be done by a external company. The company are not able to use their translation memory (Trados, Transit) with Sisulizer so we want to do the exchange with XLIFF files. This is the most recommended when i look to the forum.
Question 1: XLIFF is still the format who is recommended for exchange with Sisulizer and third party tools?
When I look to the XLIFF documentation and make some test in Sizulizer I come to this working process

Export to as XLIFF.
Send to translation company
Translation company do the translation
import the file sent by the translator
everything is fine.

This is clear. It is just not clear in which way the translator have to edit the XLIFF file.
Or better, I think that I know it but hope that somebody approve that this is correct

The trans-unit node must be edit like this

Original

<trans-unit id="m_GroupBoxIdentification.m_LabelIdentification.Text">
<source>Hello Sisulzer support forum</source>
<target state="needs-translation"></target>
<sl:rowstatus>rsInUse</sl:rowstatus>
</trans-unit>

After tranlsation:

<trans-unit id="m_GroupBoxIdentification.m_LabelIdentification.Text">
<source>Hello Sisulzer support forum</source>
<target state="translated">Hei Sisulzer tukifoorumi</target>
<sl:rowstatus>rsInUse</sl:rowstatus>
</trans-unit>

TODO from the translator:

set state to “translated”
put the translation into between the target state

Question 2: Is this working sequence in common correct or did I forgot something who can break my neck later?

I decided that post my other questions about working with Sisulizer in a different post. So that all is separated.
Thank you for answering my questions.
Holger

Private Upload

Quote

Posted: Sun Aug 22nd, 2010 11:52 am

Private Upload

Quote

Janusz Grzybek
Super Moderator

Joined:	Fri Dec 1st, 2006
Location:	Zabrze, Poland
Posts:	2542
Status:	Offline

Hello Holger,

Question 1: XLIFF is still the format who is recommended for exchange with Sisulizer and third party tools?
Yes, XLIFF format is common standard for exchange localization resources between different localization/CAT tools and for this reason is supported by most of CAT and localization software. However, you can also use TMX (Translation Memory Exchange format) as export files. I'm not familiar with Trdos, but I think TMX format could be even better than XLIFF for exchange resources with this tool, because Trados is application based on translation memory.

The trans-unit node must be edit like this
Sisulizer has implemented extended support for export to XLIFF file, for example you can save translation status, context values, comments etc., but other localization tools doesn't support these items. These additional items are very useful, if you use XLIFF to exchange resources between two Sisulizer projects (Sisulizer -> XLIFF -> Sisulizer). So, if you use XLIFF format to exchange translations with other tools, you can ucheck these items in Export Wizard. It simplify and reduce size of exported file.

TODO from the translator:
1. set state to “translated”
2. put the translation into between the target state
As I mentioned above, Sisulizer's translation status saved to TMX may be invisible in other tools (apart text editors, but they aren't localization tools), so translator can't set it. However, during import (Import Wizard) you can set status for imported items.

Question 2: Is this working sequence in common correct or did I forgot something who can break my neck later?
Generally, I think this good solution, but the devil's in the detail

.

Best regards,
Janusz

____________________
http://www.sisulizer.com - Three simple steps to localize

Private Upload

Quote

Current time is 08:38 am
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Exchange with XLIFF file format

Sisulizer software localization tool - Three simple steps to localize