|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| multi task with SLMake - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
bikemike Member
|
Whether I send
or
or
SLMake always does these tasks in the sequence LOAD, SCAN, FILLPSEUDO , REMOVESPEUDO , BUILD Per this post, http://forum.sisulizer.com/forum4/981.html I think I need the following sequence, and at the least FILL comes after REMOVE:-) LOAD, REMOVESPEUDO, SCAN, FILLPSEUDO, BUILDI only just realised I could send multiple tasks to the SLMAke, and this will improve build time as I have separate build steps for REMOVEPSEUDO, SCAN, FILLPSEUDO and BUILD and each task in isolation does it's own LOAD.... :-) I am nervous about ignoring the empty string problem and allowing the tasks to run in any sequence - unless that is surely fixed? Also, Can I handle PSEUDO translations for one language whilst building resources for them all in a single call - thereby keeping one LOAD? That will be very nice :-) If I have a single -lang specifier it seems to apply to all tasks. If I miss it out, there is a PSEUDO call for each language but I'm not sure what's happening under the covers there, is it safe...?
Last edited on Wed Dec 10th, 2008 11:43 pm by bikemike |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Mike, In the moment there is no way to change the order of the commands in the command line. I understand that it could be a timer safer in your situation to have everything in one run because of the load times. I move this thread to the wish list and hope R&D finds some easy way how to describe the order of the commands. They have to be careful in case some of our customers trusts in the current "internally fixed" order. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
bikemike Member
|
OK, but can someone tell me if it is safe to leave all the language specifiers in and let SLMake 'fail' for pseudo languages (except the one that does have pseudo) That will at least allow me to do the scan fill and create as one task, even if the remove has to be run on it's own - with the pseudo doing the one language, and the create doing them all.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Mike, what do you mean with "fail". If there are illegal commands in the command line Sisulizer should trow an warning. Does that not happen in your case? Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
bikemike Member
|
Only one of the languages in my example has pseudo filled. See the output sample I gave; it reports simply 'fillpseudo' and 'removepseudo' for each one. There's no meaningful output - nothing to report - for all languages, so whilst I might assume that it will fill the language that has been previously specified as having been filled with pseudo strings, and will not touch those that are properly filled, it might not behave like that. How does it know that one language is pseudo and one is not? I wanted to be certain how this worked. Thanks.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
bikemike Member
|
Only one of the languages in my example has pseudo filled. See the output sample I gave; it reports simply 'fillpseudo' and 'removepseudo' for each one. There's no meaningful output - nothing to report - for all languages, so whilst I might assume that it will fill the language that has been previously specified as having been filled with pseudo strings, and will not touch those that are properly filled, it might not behave like that. How does it know that one language is pseudo and one is not? I wanted to be certain how this worked. Thanks.
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Mike, here is how it looks inside the Sisulizer project file what is XML based: <row id="Caption"> <native>&Type:</native> <lang id="fi" savedtotm="1">&Tyyppi:</lang> <lang id="de" savedtotm="1">&Typ:</lang> <lang id="ja" savedtotm="1">タイプ(&T):</lang> <lang id="af" test="1"/> </row> As you can see does Pseudo Translate not add a string but writes test="1" into the field. This way Sisulizer can easily remove pseudo translated fields. It creates the pseudo string at display time from the actual rules. Hope this helps Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 08:13 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 > multi task with SLMake | |
Sisulizer software localization tool - Three simple steps to localize
