|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| New item in Project Wizrd - Wish list for software localization tool - Technical Support (You need to be registered at the forum to write) - Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... | ||||||||||||||
| Author | Post | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, By default the Sisulizer after creation new project for INI files set option Quote as None (Source properties), but most applications use INI language files with double quote (“) or single quote (‘). For this reason translator immediately after creation new project should to change this option, but for applying this change necessary is using Project > Scan for changes feature and then Project > Clear Changed Status. Adding option for possibility of changing quote setting to Project Wizard probably improve working comfort. Do you think about adding following dialog window to Project Wizard for INI files? Best, Janusz Attachment: Snap1.gif (Downloaded 87 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator
|
Thank you for the good idea. I implemented this in 1.6.10 Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, Thank you for implementing it, but I've still two additional questions concerned to INI localization. Here short text from Wikipedia article abort INI format "Some implementations allow ":" in place of "=" and/or skipping the surrounding spaces." I found in some localization projects also , ; . tab and space characters as separators between contexts and values in INI keys. Do you think about adding possibility of choosing these characters in INI project wizard (similar option is available during opening text files in the MS Excel e.g. CSV). Below is second example text about INI files from Wikipedia: "Duplicate parameters: Most of the time, you can't have two parameters with the same name in one section. Therefore one can say that parameters are local to the section. Although this behavior can vary between implementations, it is advisable to stick with this rule." This is good idea, but unfortunately, software developers very often use keys duplicate in INI localization files. The Sisulizer consider it as error (List index out of bounds ) and abort scanning of INI file (content of INI file is incomplete). For successful scanning an adding all strings to Sisulizer project I open INI file in external text editor (any time ago I wrote about adding to Sisulizer option for opening source file in external editor directly from Sisulizer), then I search duplicate keys and temporary change context names of duplicate. After finish of localization process I revert to previous context name, and of course change it in translated file. Do you think about changing parsing mode for INI files to less restrictive or adding option to source properties or project wizard for ignore duplicate keys error? Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator
|
You can already skip the surrounding white spaces. See the screen shot. I will implement other in 1.6.15. Jaakko Attachment: untitled.PNG (Downloaded 69 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hi Jaakko, Thank you Jaakko. I use sometimes ignore white spaces feature, and my text about skipping white spaces is only quotation from Wikipedia. I quote this sentence from Wikipedia, because I wanted touch question about separator between name key and value. Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Janusz Grzybek Super Moderator
|
Jaakko, excuse me my importunity, but I’ve one idea for INI localization yet. Do you think about displaying INI sections in separated nodes in Tree pane? This solution give translator better preview of INI file content, and make work in sheet more comfortable. Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Jaakko.Salmenius Administrator
|
I will implement this too. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator
|
I implemented this in 1.6.15 Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Janusz Grzybek Super Moderator
|
Thank you for implementation all these features. Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, Current version of SL (1.6.15) enable preview of INI sections in separated nodes (Thanks!), but I can edit contents of INI file only after select root (main) node of INI file in tree pane, and after selecte any child node (section) I'm able only look on section contents, because sheet is empty. Do you think about implementation edit mode for separated nodes instead preview mode? Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, Thank you for improving INI files scan feature in SL 1.6.27. I tested today new version of SL behavior with INI files contains name duplicates in one section, and current SL version does not return “List index out of bounds” error during scan process, as results after scanning all string items has been added correctly to project. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Janusz Grzybek Super Moderator
|
Thank you for implementing in V2008 edit mode for separated nodes instead preview only (SL 1.6). It is really very comfortable solution for translators. Thanks again! Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| Current time is 03:24 am | |
| Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > New item in Project Wizrd | |
Sisulizer software localization tool - Three simple steps to localize