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
Problems with XML and multilingual file - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Mon Mar 5th, 2012 11:09 am
PM Private Upload Quote Reply
Christine
Member
 

Joined: Tue Nov 20th, 2007
Location:  
Posts: 191
Status: 
Offline
Hi all,

I have set up a new project, XML data and multilingual file build output.

The problem is that the build output does not contain the translations.

I have a similar project with multilingual file build output and that works fine.

I cannot find any problems with the settings, but maybe I am missing something.

Please find the project and original XML file attached.

Best regards, Christine

Back To Top PM Private Upload Quote Reply

 Posted: Mon Mar 5th, 2012 11:24 am
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


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

Thank you for files. I tested it and seems to me that multilingual output file is correct (look on attached screenshot). However, I found your SLP has unchecked "Multilingual file" option in source properties ("File" tab).  Please, check this option and build output file again.

Best regards,
Janusz

Attachment: screen.png (Downloaded 24 times)



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

 Posted: Mon Mar 5th, 2012 11:34 am
PM Private Upload Quote Reply
Christine
Member
 

Joined: Tue Nov 20th, 2007
Location:  
Posts: 191
Status: 
Offline
It seems something went wrong with the private Upload. The files you looked at are older files (from another support issue).

I try the upload again.

The file names are as follows:

PresetData.xml
PresetData.slp

Back To Top PM Private Upload Quote Reply

 Posted: Mon Mar 5th, 2012 11:42 am
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 2993
Status: 
Offline
OK, I got new files and I'll check this.

Janusz



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

 Posted: Mon Mar 5th, 2012 12:55 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 2993
Status: 
Offline
 Your file structure doesn't match with XML standard used by Sisulizer for multilanguage files. Here is w3.org specification for multilanguage entries in XML files: http://www.w3.org/TR/REC-xml/#sec-lang-tag
Here is thread about similar issue: http://www.sisulizer.net/view_topic.php?id=1299&forum_id=7&highlight=multilanguage+xml

You use following structure:

<TransText Description="" DisplayName="Text" DisplayName_de-DE="" DisplayName_fr-FR="" ID="Text"/>

and Sisulizer can't add localized entries in differnet languages to empty DisplayName attributes. However if you use this simple structure:

<TransText Description="" id="Text">Text</TransText>

Sisulizer will build correct multilingual file matched with w3 Org specification:

<TransText Description="" id="Text">Text</TransText>
<TransText xml:lang="de-DE" Description="" id="Text">Text</TransText>
<TransText xml:lang="fr-FR" Description="" id="Text">Text</TransText>

Best regards,
Janusz




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

 Posted: Mon Mar 5th, 2012 02:21 pm
PM Private Upload Quote Reply
Christine
Member
 

Joined: Tue Nov 20th, 2007
Location:  
Posts: 191
Status: 
Offline
Hi Janusz,

thank you for the prompt response. Can you please tell me why it works for another XML, which is quite similar to this one? Actually we used the other one as a template for the new one and are confused why it works in one case and not in the other.

I upload you the file that was created by a Sisulizer build.

Thanks in advance, Christine

Back To Top PM Private Upload Quote Reply

 Posted: Mon Mar 5th, 2012 02:33 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 2993
Status: 
Offline
Could you also upload original PresetRepository XML file and SLP?

Janusz



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

 Posted: Tue Mar 6th, 2012 08:20 am
PM Private Upload Quote Reply
Christine
Member
 

Joined: Tue Nov 20th, 2007
Location:  
Posts: 191
Status: 
Offline
sure, upload done

Back To Top PM Private Upload Quote Reply

 Posted: Tue Mar 6th, 2012 10:48 am
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


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

Thank you for files. Sorry, but I forgot our developers recently improved lang attributes support for XML files.
I compared both your source XML files and I found current build can't correctly build localized entries when tag hasn't separated closed tag and some contents (e.g. comment or sub-tag) between those tags, so Sisulizer can't correctly build item with following structure:

<TransText Description="" DisplayName="Paper1"/>


but can correctly build multilingual output file for this source structure:

<TransText Description="" DisplayName="Paper1"><!--comment--></TransText>


I think it should be changed, so I'll forward it to our R&D.

However if you change your source file like on above example (or similarly), probably you will get build error, because source already contains locale version of localized attributes (e.g. DisplayName_de-DE="" DisplayName_en-US="" DisplayName_es-ES="") and Sisulizer can't add localized attributes to output files. For fixing this, you need remove all "DisplayName" attributes with added lang abbreviations from source file. When you do it, Sisulizer automatically add these attributes to output files (with translations).

Best regards,
Janusz



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

 Posted: Tue Mar 6th, 2012 02:40 pm
PM Private Upload Quote Reply
Christine
Member
 

Joined: Tue Nov 20th, 2007
Location:  
Posts: 191
Status: 
Offline
Hi Janusz,

thank you for the information. After adjusting the XML as instructed, it works now as expected.

I agree that Sisulizer should support "empty" XML tags as they are quite common, even though this is no immediate problem for us.

Best regards, Christine

Back To Top PM Private Upload Quote Reply

 Posted: Fri Mar 9th, 2012 08:26 pm
PM Private Upload Quote Reply
Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 1321
Status: 
Offline
I fixed this in 330. The new build will be available tomorrow.

Ilkka



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

Current time is 09:04 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 > Problems with XML and multilingual file



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