|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Selecting of XML tags - Wish list for software localization tool - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hi, Dialog Source XML (Properties…) > Tags allows to exclude selected tags from translation, but user needs to disable each unnecessary tag individually. To one of my project is attached simple but long XML file. This file contain software errors and messages list in following tags sequence (look on screenshot): <Sample> <name> … </name> <title> … </title> </reference> <description> … </description> </Sample> Above sequence is repeated around 300 times. I would like to exclude all tags <name> from project, but I need to click 300 times on <name> tag. Do you think about possibility excluding/including all identical tags (for example by context menu, new buttons on toolbar or by adding checkbox to Edit > XML item dialog)? Best, Janusz Attachment: screen.gif (Downloaded 28 times) Last edited on Sat Jan 5th, 2008 10:12 am by Janusz Grzybek ____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Janusz, have you tried to change the structure of the XML a bit. As it is now it does not seem to be very clever. Perhaps you could add another nesting level around all data entries of the same kind, like eg.: ... old xml header ... <extralevel> ... your old xml structure </extralevel> This could help Sisulizer to see that there are many entries of the same kind. In the moment it thinks it as one huge structure. While I have not seen your file I can only guess. Hope it helps nevertheless. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hi Markus, Thank you for interesting idea, I found out other solution before your post, that is, I used Text filter (look on screenshot), then I excluded from translation all contents of filtered sheet. Whole operation lasted below 1 minute, but I tested out of curiosity your idea, and it working with the Sisulizer just as you thought. However it seem to me that adding new option to XML properties > Tags could to be more comprehensive and “elegant” solution. Of course, this is not significant idea. Best, Janusz Attachment: screen1.gif (Downloaded 25 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Janusz, yes, the text filter with the regular expressions is a good idea for any non-standard XML. The problem with your XML is not Sisulizer but XML structure. It looks like XML but it is used more like a sequential text file. We have to decide how we can support such structures better. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
It looks like XML but it is used more like a sequential text file. Exactly. My file hasn’t typical for XML documents hierarchical tree structure, but XML is very flexible language, and people can defined in XML whatever wants. For this reason I frequently meet very “strange” XML files. Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Janusz, you are right. Everybody says "Off course we use XML" - but most use it just as a replacement for simple text file. They do not understand the beauty of the format and also do not meat some basics. You as a translator and we as localization tool vendor have to life with this weak structures coming with XML file extensions. Good luck that Sisulizer does not use any third party XML parser. So we can be more flexible while scanning XML files :-) Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 05:48 am | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Selecting of XML tags | |
Sisulizer software localization tool - Three simple steps to localize
