|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > How to use SLMAKE Import with "Ignored Character: Character case" option
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > How to use SLMAKE Import with "Ignored Character: Character case" option
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| How to use SLMAKE Import with "Ignored Character: Character case" option - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
koela1 Member
|
Hi I use Sisulizer 2010 Build 321 and I need to import strings from an excel file using command shell (SLMAKE) and with the option "Ignored characters" -> "Character case" set on. This option appears in the Import wizard UI. what flag should I use for that? I couldn't find it in the manuals. Thanks Ela
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello Ela, Current version of SlMake doesn't support this parameter for import command and it is avilable only via Sisulizer GUI. I'll ask our R&D about adding ignored characters parameters. Here is article on our blog about import command: http://www.the-localization-tool.com/?p=936 BTW: Because thread is rather about improving of existing feature (not about bug), so I moved it to our wishes section. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
koela1 Member
|
Thanks Janusz, for your quick response. I understand you don't support this parameter but it causes me a lot of problems. I'll explain: Exporting to excel is done as case insensitive when I use "Only first instance" option checked. So if I had 2 strings: 1) User Preferences 2) user preferences The exported excel would contain only one of them - User Preferences On the other hand, importing strings is done as case sensitive. So importing the excel will update only "User Preferences" string and the other string is left not translated. Is it possible then, to have these 2 features aligned with each other? Can I export only first instance but treat the strings as case sensitive? Thanks Ela
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
I understand you, it could be annoying. I already forwarded it to our developers. Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Ilkka.Salmenius Administrator 
|
There were to issues in Sisulizer 1) When Only first instances on Sisulizer incorrectly ingore case. It should have exported items that used difference case. Now if project contained "One" and "one" only "One" or "one" was exported. I added also an option to turn on the old case insensitive export. The new features will be in the next build (330) 2) SlMake did not have any option to turn on case insensitive importing. I added this. The new feature will be in the next build (330). Use -ignorecase option. I also added some other missing options. 330 will be released next week. Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Ilkka.Salmenius Administrator
|
Ilkka.Salmenius wrote: 1) When Only first instances on Sisulizer incorrectly ingore case. It should have exported items that used difference case. Now if project contained "One" and "one" only "One" or "one" was exported. I added also an option to turn on the old case insensitive export. The new features will be in the next build (330) Here is some more information. Current Sisulizer handles duplicates in case insensitive way. This might be usefull in some purposes but the duplicate exclude feature was not indented to work like this. The purpose was to include every string at least onece and exclude only those string that are 100% the same. This is why I changed the logic such way. The new logic is effection starting from Sisulizer build 330. To make new build backward compatible I added a new option. if you check Ignore character case on duplicates check box Sisulizer works like it works now. Ilkka Attachment: Untitled.png (Downloaded 21 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Ilkka.Salmenius Administrator
|
Ilkka.Salmenius wrote: 2) SlMake did not have any option to turn on case insensitive importing. I added this. The new feature will be in the next build (330). Use -ignorecase option. I also added some other missing options. If you want to ignore case when importing use the following options SlMake.exe import MyFile.xls -columns:en;de -ignorecase MyFile.slp ignorecase is a new option for import task. Other new options are -onlystrings Import only strings values. -ignorecase Ignore character case of imported values. -ignorewhite Ignore white spaces of imported values. -ignorespe Ignore special characters such as period and hot key (&  .-usepartial Use partial context. Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
koela1 Member
|
Thank you all for the help I currently own the license for Sisulizer 2010 (and use version 321), so I'll probably update to Sisulizer 3 to get hold of version 330 Last question, Are there any breaking changes between versions 321 and 330 I should know of? Thanks Ela
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, Here are details about new and improved features in Sisulizer 3: http://www.sisulizer.com/localization/news/what-is-new-in-software-localization.shtml Here is our changelog, but not all changes are listed on this site: http://www.sisulizer.com/_inc/History.html I recommend you also read those articles on our blog about selected features implemented to Sisulizer 3: http://www.the-localization-tool.com/?p=2410 http://www.the-localization-tool.com/?p=2440 Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello,I'll probably update to Sisulizer 3 to get hold of version 330 Here are details about upgrade options (look on table in bottom part of site): http://www.sisulizer.com/support/upgrademe.shtml Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 07:55 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 > How to use SLMAKE Import with "Ignored Character: Character case" option | |
Sisulizer software localization tool - Three simple steps to localize
