|
|||
|
Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > How to use translation memory with slmake
|
|
|||
|
Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > How to use translation memory with slmake
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| How to use translation memory with slmake - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... | ||||||||||||||
| Author | Post | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
bikemike Member
|
Say I have a range of generated context names, customStr1..customStr10 Say I remove a string after position 4 in my source, from which the names are generated. Now I have a range of generated context names, customStr1..customStr09. Now any translations I already have are out of alignment from customStr5 onwards. The original text in customStr09 should now appear in customStr08 When I rescan, Sisulizer picks up the fact that things have changed. Also, if my sequence had a hole in it previously, and I move an existing string to an empty slot, the translation engine can find the previous translation from the project and apply this. It cannot find the translation for a row that is already filled but for which the translation now applies to the wrong row. a) is there something wrong here b) I am assuming that if I use the translation memory and keep that up to date it will be able to translate these. If so, is there a way to get slmake to save the translation memory?
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
bikemike Member
|
It seems the use of an updated translation memory makes no difference. The key thing seems to be that I need to clear the cell, and then do the translate. (edit: but this only works if the correct text was at some point in the correct slot.... is the translation done exclusively on the context, not on string matching the original?) Thing is, I only want to do this for changed or new rows so i don't want to clear all rows for all resources for all languages and retranslate - and get potential duplicate problems and contextual errors in the reapplication of the translates. What should I do to reapply translations for changed items only - using slmake...? Last edited on Wed Oct 15th, 2008 11:14 pm by bikemike |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Jaakko.Salmenius Administrator 
|
What is your original file? Delphi EXE or .NET assembly? Sisulizer project always works by context. If a context changes but the original value remains same Sisulizer can keep the translation(s). If both changes at the same time Sisulizer looses the translations and creates a new row the the change context/orignal value. Translation memory always works by values. It does not know anything about conext but assing a translation for untranlsated cell if the original value of the row matches the value in the translation memory. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| Current time is 12:28 am | |
| Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > How to use translation memory with slmake | |
Sisulizer software localization tool - Three simple steps to localize
