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: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius
New Topic Reply Printer Friendly
SLMake xlf import incorrect - 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: Tue Jul 27th, 2010 10:56 am
PM Private Upload Quote Reply
ka_developer
Member
 

Joined: Tue Apr 20th, 2010
Location:  
Posts: 45
Status: 
Offline
Hallo,

we have some problems with slmake  xlf import in the verstion 307:

1) We have different translations of the same string in different contexts. Check of xlf file shows that all these translations are correctly exported. But  slmake import takes one translation for all occurrences, the other are lost.

2) slmake xlf import also "forgets" some translations seen in xlf file.

Could you please help us with these problems? I will do a private upload to this message.


Sincerely

Back To Top PM Private Upload Quote Reply

 Posted: Tue Jul 27th, 2010 12:00 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


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

Thank you for files and included description. I'll check this.

Best,
Janusz



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

 Posted: Wed Jul 28th, 2010 08:53 am
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


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

1) We have different translations of the same string in different contexts. Check of xlf file shows that all these translations are correctly exported. But slmake import takes one translation for all occurrences, the other are lost.
It occurs because Sisulizer always use "By value" method for import from XLIFF files, even, if to XLIFF file are included context values. In this case Sisulizer doesn't know where use different translation for this same original, and for this reason used is one translation for this same original. I already asked our R&D about improving import features for XLIFF files with saved contexts.

2) slmake xlf import also "forgets" some translations seen in xlf file.
I think some original values in both files (XLIFF and SLP) could be different and Sisulizer doesn't import these items. Unfortunately, confirmation of this suspicion requires comparing full contents of XLIFF and SLP file.
However, I performed my own test:
- I've exported German translations from your SLP to XLIFF file
- Next, I cleared all translations in SLP
- Then, I imported German translations from XLIFF file to SLP and all items were re-imported.

Best regards,
Janusz




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

 Posted: Wed Jul 28th, 2010 09:35 am
PM Private Upload Quote Reply
ka_developer
Member
 

Joined: Tue Apr 20th, 2010
Location:  
Posts: 45
Status: 
Offline
Thank you for your reply.

In the second case the problem is the same. In xlf we have some source string 2 times in different contexts and the first occurrence is not translated. So the translation of the second one is not imported properly because the first wins.


The fact that xlt import ignores context is quite an issue for us. Would you suggest to use tmx instead? We've choosen xlf because it looks compact. Could you tell us which format is better for which propose?


Sincerely


Back To Top PM Private Upload Quote Reply

 Posted: Wed Jul 28th, 2010 10:02 am
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 2542
Status: 
Offline
Yes, you can import TMX also with "By context" (recommended in your case) or "By context first then by value" methods, if contexts are saved to TMX file.

Janusz



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

 Posted: Wed Jul 28th, 2010 10:13 am
PM Private Upload Quote Reply
Jaakko.Nieminen
Administrator
 

Joined: Sat Mar 20th, 2010
Location:  
Posts: 657
Status: 
Offline
ka_developer wrote: The fact that xlt import ignores context is quite an issue for us. Would you suggest to use tmx instead? We've choosen xlf because it looks compact. Could you tell us which format is better for which propose?

Starting from build 308 you can import XLIFF using context senstive method. it works just like in TMX or SLP you can choose By value, By context or By context first then by value.

Of cource this can be done only if the XLIFF was originally export from Sisulizer and the XLIFF contains context-group / context elements.

Jaakko

Back To Top PM Private Upload Quote Reply

 Posted: Wed Jul 28th, 2010 10:26 am
PM Private Upload Quote Reply
ka_developer
Member
 

Joined: Tue Apr 20th, 2010
Location:  
Posts: 45
Status: 
Offline
>
> Starting from build 308 you can import XLIFF using context senstive method.
>

We will greatly appreciate that. We have already about 90 xlf files (all exported with context) in our build process and are to be sure that all these will be imported correctly with SLmake.

So we are looking forward for the next release.

Sincerely

Back To Top PM Private Upload Quote Reply

 Posted: Wed Jul 28th, 2010 10:47 am
PM Private Upload Quote Reply
Jaakko.Nieminen
Administrator
 

Joined: Sat Mar 20th, 2010
Location:  
Posts: 657
Status: 
Offline
One more thing. SL buidl before 308 did not incldue full context in the exported XLIFF files but partial context. To import them correct make sure you use the settings shown on the screen capture below.

If you import XLIFF file exported by SL 308 or later that options need not to be used.

Jaakko

Attachment: Untitled.png (Downloaded 18 times)

Back To Top PM Private Upload Quote Reply

 Posted: Wed Jul 28th, 2010 11:03 am
PM Private Upload Quote Reply
ka_developer
Member
 

Joined: Tue Apr 20th, 2010
Location:  
Posts: 45
Status: 
Offline
>
> SL buidl before 308 did not incldue full context in the exported XLIFF files but partial > context. To import them correct make sure you use the settings shown on the >screen capture below.
>

Thank you for the info.

What does it mean for SLMake command line options?


Sincerely

Back To Top PM Private Upload Quote Reply

 Posted: Wed Jul 28th, 2010 11:29 am
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 2542
Status: 
Offline
SlMake import task has already implemented attribute for selecting import method, but currently it doesn't work for import from XLIFF files. However, with next build you can use it. If you'll add "-method:0" attribute to your command line, Sisulizer use "By context" method for import.

One more thing. SL buidl before 308 did not incldue full context in the exported XLIFF files but partial context. To import them correct make sure you use the settings shown on the screen capture below.
Because, currently import from XLIFF file supports only "By value" method, you can't use "Use partial value in addition of full context".

Janusz



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

 Posted: Wed Jul 28th, 2010 12:07 pm
PM Private Upload Quote Reply
ka_developer
Member
 

Joined: Tue Apr 20th, 2010
Location:  
Posts: 45
Status: 
Offline
Thank you for your support.



Sincerely

Back To Top PM Private Upload Quote Reply

Current time is 08:48 pm  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > SLMake xlf import incorrect



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