|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Mark imported translations from "outside" engines
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Mark imported translations from "outside" engines
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Mark imported translations from "outside" engines - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
BStaack Member 
|
Hello again. When you have several activated translation engines it´s not possible to catch the source of the translation which belongs to it´s quality. I have activated our own directory (good quality of translations) and also Google and Microsoft (both should get checked). After the automatical translation / sync of databases I have no possibility to see where the text comes from. The automatic "outside" translation is a good help for missing translations but i about 80% you´ll have to correct them after importing. I need to see which translations I can ignore, because they were imported from our correct translation database, and which I have to check. Maybe you could give them a filer tag or a seperate color ? This would be great. Best regards Björn
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello, I'll ask about it our developers. With current build you can use following trick: First, use your internal TM with your verified translation resources. Next, go to "Tools" menu -> "General" -> "Translations" tab -> "Change translation status" -> "When importing" and change status e.g. from "Auto translated" to e.g. "Best guess". Then use Microsoft or/and Google engines. This solution allows you separate in easy way items translated by your internal Translation Memory ("Auto translated" status) and items translated by Google and Microsoft ("Best guess" status). Best regards, Janusz Attachment: screen.png (Downloaded 15 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
BStaack Member
|
Hi Janusz... thank you for this idea. This will be a good solution to mark those translations. It could be a nice possibility if it´s possible to do these settings combined with the translation engine !? Thank you
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Currently Sisulizer can't assign selected status to specified translation engine/memory, so Sisulizer use selected status for all translation engines and imported files. For this reason I recommend revert "When importing" setting to previous value after using Google or Microsoft, because when next time you use internal translation memory, Sisulizer assign to translated items status selected in "When importing" (in our example changed to "Best guess"). However, (as I mentioned above) I've some idea similar to your suggestion and I forward to our developers. Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 06:15 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 > Mark imported translations from "outside" engines | |
Sisulizer software localization tool - Three simple steps to localize
