|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > slmake support google translate machine translation?
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > slmake support google translate machine translation?
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| slmake support google translate machine translation? - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
jlsymantec Member
|
I wasn't able to figure it out, but... Does slmake.exe has a usage to do the following: 1) the changes will send to Google translate machine translation service - slmake translate -lang:ja Sample.slp? but how does it know i want to use Google translation service? 2) Fill the pseudo string if it contains the new entry. No need to re-fill the pseudo string to the language. - slmake fillpseudo Sample.slp? does this over written the ones that are already filled? or will it fill only the "Not translate" field? thanks Last edited on Fri Feb 27th, 2009 08:23 pm by jlsymantec |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello James, Yes, SLMake supports Google Translate feature. For fresh installation, latest build of Sisulizer automatically enable Google Translate engine, but if you updated your Sisulizer from older version, maybe you need manually enable Google Translate in Translation Engines dialog. For do it, you need to go to “Tools” menu > “Translation Engines” > click “+” button for adding new translation engine. After click “+” button, on your screen should appear “New Translation Engine” dialog. Next you should select “Google translate” item from “Translation engine type” list (look on screenshot). Currently Google Translate supports 34 languages. BTW: If you would like to test how Google Translate works with SLMake, you could to disable other active translation engines via Sisulizer UI and next run “slmake translate -lang:ja Sample.slp” command. Best regards, Janusz Attachment: screen.png (Downloaded 47 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
About your second question:2) Fill the pseudo string if it contains the new entry. No need to re-fill the pseudo string to the language. - slmake fillpseudo Sample.slp?If your Project contains new items, you should use “SLMmake fillpseudo” again, if you would like to fill new items with pseudo-translation. does this over written the ones that are already filled? or will it fill only the "Not translate" field?No, this command doesn’t replace exists pseudo-translations. Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
jlsymantec Member
|
thank you so much!!
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
jlsymantec Member
|
quick question, i receive daily compiled DLL binary files, updated versions, and update English strings. Command such as slmake fillpseudo and slmake translate only do it when there is a new translation, however, those comands don't re-fillpseudo or re-translate the existing old translation to the new strings. What is the workaround? Here is the breakdown: 1) once it scans, if there is a changed, remove the old translation in fr-FR and ja languages. 2) fillpseudo to update the new translation or translate the update translation 3) Only copy the original DLL versions to -lang:fr-FR and -lang:fr, do not fillpseudo or translate. thank you!
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hi James, You could use batch solution with following commands sequence for re-use pseudo-translation: - removepseudo - scan - fillpseudo It allows you refresh pseudo-translation for all strings in updated files. But this solution doesn’t works for already translated strings. Why? Here is answer: http://forum.sisulizer.com/forum3/1305.html Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
jlsymantec Member
|
thanks for your reply. I guess if i remove the whole translation, by using google, it will takes forever to fill in all the translation. Also, i noticed by using slmake command, "scan" option doesn't automatically save the file for you. It only tells you that ... file has been changed since the last scan. Is this a bug? Using Sizu UI, press F5 will scan and if you exit, it will ask you to save the file.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
jlsymantec Member
|
thanks for your reply. I guess if i remove the whole translation, by using google, it will takes forever to fill in all the translation. Also, i noticed by using slmake command, "scan" option doesn't automatically save the file for you. It only tells you that ... file has been changed since the last scan. Is this a bug? Using Sizu UI, press F5 will scan and if you exit, it will ask you to save the file.
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
jlsymantec Member
|
please ignored the previous comment. "Exclude" does update the version. thanks
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello James,Using Sizu UI, press F5 will scan and if you exit, it will ask you to save the file. SLMake automatically save project after scan. please ignored the previous comment. "Exclude" does update the version. Ok, thanks. However I’ve short comment to your posts. Changes could be invisible in project, for example in project tree or translation sheet, because changes are concerned to not localized resources (Resources tab in source properties), excluded data types from project (Excluded data types tab in source properties), excluded rows, originals and strings from project. Invisible changes could be also result of some filter usage. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
jlsymantec Member
|
thanks for your reply. I guess if i remove the whole translation, by using google, it will takes forever to fill in all the translation. Also, i noticed by using slmake command, "scan" option doesn't automatically save the file for you. It only tells you that ... file has been changed since the last scan. Is this a bug? Using Sizu UI, press F5 will scan and if you exit, it will ask you to save the file.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, jlsymantec wrote: thanks for your reply. I thought issue is solved, but you repeated your previous post. Could you tell me what happened? Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 05:26 pm | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > slmake support google translate machine translation? | |
Sisulizer software localization tool - Three simple steps to localize
