|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Exchange package options - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Eva Member
|
Hi I manage a Sisulizer project based on Qt .ts source files. When I make an Exchange package to send to the translators I want each of the translators to get a separate .sle with only the translators language included (besides the source language of course). Correct me if I am wrong, but I experience that if I want to send an Exchange package per language to the different translators, then I have to redo a process as many times as there are languages in my project. And there are 13 languages in my project. I believe the option is all in one package, or, to do the whole Exchange process from beginning to end for each desired language. I have heard of SlMake as a tool to automate several processes in Sisulizer. However, when single process is needed beside this tool, why not give the option to Exchange all languages - but in separate packages? Thanking you in advance for your kind reply Eva
____________________ Eva :O) |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello, SLMake doesn'ts allows on creation more than one exchange packages at once. One SLMake command can to create only one exchange package, but SLMake is command line tool, and for this reason you can use old DOS trick with batch file, that is, you should to type in batch file separated command lines for each exchange package, and next run batch file. However this is DOS feature, not internal SLMake feature. Your idea seem to me interest, but implementation could to provoke next issues, for example Exchange Wizard allows on type custom name for exchange package. If Exchange Wizard will create 15 separated exchange package. “Exchange Wizard – Information” step should contains 15 “Package name” fields! Additional number of these fields in Sisulizer UI should to depend on number of selected languages, so if you select only 9 languages instead all 15, this Wizard step should to have 9 fields. However I’ll forward your request to our R&D, maybe they will find some solution. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Eva Member
|
Thank you for replying so quickly. About solution, what if customer still is able to enter custom file name, but Sisulizer is the one to automatically add language abbreviation code according to selected language packages? E.g. I select German and Spanish languages and I am allowed to name the package MyProject. I am not allowed to add language abbreviations. Sisulizer automatically adds language abbreviations at runtime and thus makes these packages: MyProject_de.sle MyProject_es.sle Another solution is to name Exchange output files at the time of creating new projects? As a part of properties to be set along with project path, and source path, and such. Just an idea. Eva
____________________ Eva :O) |
||||||||||||||||
| |||||||||||||||||
| Current time is 08:38 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 > Exchange package options | |
Sisulizer software localization tool - Three simple steps to localize
