|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Translate XML file problem - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
James Member
|
Hi all, I use an industrial supervision software called "Wonderware" which has some support for language switching. The language elements of the software are exported in XML format. There is an "original language" column and a "Translated" column. The suggested procedure is to translate via Excel. I would like to use sisulizer to translate these documents but it does not seem possible to get sisulizer to use the "Translated" column - it only wants to substitute the original language column (which is fine for most situations, but not in this case). Is there any way to use sisulizer to translate these xml documents? Thanks, James
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Can you send one sample file to me support (at) sisulizer.fi Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Hi James, Thank you for the file. Currently you can not use Sisulizer to tranlate this file. The problem is that it contains two languages where the source and target languages are not in the same XML level and do not use the same element name. I will study this more and it might be that we can get this working very soon (in few weeks). I need a little bit more time to test this. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
James Member
|
Thanks for the info! I'll check back on the product from time to time
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Edson Furmankiewicz Member
|
Jaakko.Salmenius wrote: Hi Jaakko I have this same question, but the original and translation fields are at the same level. How could I import, translate and export the translated file? Thanks Edson Hi James, Attachment: prowiz.gif (Downloaded 28 times)
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Nieminen Administrator
|
Thank you for the file. I got your point. The new feature is almost completed but it was never released. I will finish it. It won't take long. After that you can localize your XML file. Jaakko
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Nieminen Administrator
|
Now the new feature is completed. It will be in the next build (310). Open your project. Right click the XML file in the project tree and choose properties. Select Tags sheet. Select original node and right click. From popup choose Original value. Select value node and right click. From popup choose Translated value. Finally select key node and choose Context value in the popup. Your selections should look like in this screen shot. The above configuration makes Sisulizer to handle original node an XML tag that contains original value and value node contains translated value. Key node contains unique context value. Use this only if the value in the key node is really unique. Jaakko Attachment: Untitled.png (Downloaded 22 times)
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Edson Furmankiewicz Member
|
Hi Jaakko, I think I followed exactly the steps, but I did not get what I expected: • Translation was imported in the Original colum • Translation is not paired with Original I expected that Original field would be imported to Original column and Translation field would be imported to Translation column, and and that columns would be aligned. Did I miss something? Again, I'm capable of thinking in some workarounds to get what I want Sisulizer do, but I'm wondering why this option does appear to function as intuitively as it seems. Thanks Edson Furman Attachment: two_lang_xml.jpg (Downloaded 13 times)
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Nieminen Administrator
|
I tested your file in the current build (310) and it got it working. The reason that it does not work on your project is that you have selected resource-string element as context element. Remove the context flafg from the element. See the screenshot. After that SL correctly scan the orginal value instead of translation value. However I found one bug. SL bud 310 did not import the translated value (Portuguese) into SL project. I fixed this in 311. Jaakko Attachment: Untitled.png (Downloaded 13 times)
|
||||||||||||||||
| |||||||||||||||||
| Current time is 05:44 pm | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Translate XML file problem | |
Sisulizer software localization tool - Three simple steps to localize
