|
|||
|
.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
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| 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 | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Christine Member
|
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
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
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 |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Christine Member
|
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
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
OK, I got new files and I'll check this. Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
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:
and Sisulizer can't add localized entries in differnet languages to empty DisplayName attributes. However if you use this simple structure:
Sisulizer will build correct multilingual file matched with w3 Org specification:
Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Christine Member
|
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
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Could you also upload original PresetRepository XML file and SLP? Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Christine Member
|
sure, upload done
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
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:
but can correctly build multilingual output file for this source structure:
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 |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Christine Member
|
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
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Ilkka.Salmenius Administrator
|
I fixed this in 330. The new build will be available tomorrow. Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| 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 | |
Sisulizer software localization tool - Three simple steps to localize