|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Translated texts AWOL - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
bikedude Member
|
My two colleagues who work with our translations reported last week that many of their translations has a tendancy to disappear. Case in point, we had the following in our repository:
...which was subsequently shortened to the much more efficent single line of this:
There were several of those. After upgrading to 305 we still see this happening. One colleague suspects the translation memory is a bit iffy. She says that it still remembers the disappearing translations, and when she re-translates some of the missing texts it will remember those as well. Any idea what we're doing wrong? (I'm not giving you much to go on, but not sure how to reliably reproduce this)
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Sisulizer use single line with following structure:
for not translated items, while after adding translation, this structure is changed, for example on:
So this is result, not reason. Let me know if you will find something about issue with missed translations. More information about SLP structure you can find in this http://www.sisulizer.net/forum2/1216.html thread on our forum. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator 
|
Sisulizer should not drop translations. Sometimes if the context of the original changes Sisulizer can not correctly copy existing translations from old row to the new row. Even on that case Sisulizer leaves the old translations on the old row and just marks the rows as unused. Can you tell me whart kind of file this row belongs to. Is it a .resx or .XAML file. Have you recently changed the original file? Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
bikedude Member
|
The quoted text belongs to a .resx file. The .resx file itself was last changed April 23rd. Our translators have been working steadily around that time, but the mishap did not occur until May 11th. But, further sampling seems to suggest that the affected texts have all been added within the past 7 months. It would not be impossible (I guess) that one of my translators could touch old source code while scanning for changes... Is that a plausible explanation for what we're seeing? (It seems strange, because the translator in question has the latest source -- I've checked this myself a couple of times) What does Sisulizer do when a text disappears from the source code? Is it all down to the translation memory to provide a guess the next time the text re-appear?
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
If text disappers or its context changes the row becomes unused. It is still in the project but it not bound to any item. It remains in the project as long as you remove unused items byt choosing Project | Remove Ununsed Items. When you do that Sisulizer removes the unused rows and translations they contains. Before removing Sisulizer adds the translations into translation memory (however you can turn this feature off). Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
bikedude Member
|
State=0, is that unbound? Because in my case, it not only became unbound (State=0), but the translation disappeared too... Are you sure the unbound element will retain its translation in all scenarios?
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
bikedude Member
|
Oh... sorry, Janusz already explained about the State value. 0 = New 1 = Unused 3 = Changed So... It went from "Unused" to "New". Neither was the case. ...And so the question become: Is the translation retained when changing from "Unused" to "New"? (I.e. when the text reappears?)
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Mike, If both the context and the value of an entry changes Sisulizer can not make a link. In this case for every new entry there is also one unused entry. The problem is, that even if the translations are saved to TM (which makes language pairs only by value) it will not help much since there is no clue how to glue the pairs together. Perhaps you changed the context of some strings and also changed the original text of the strings since you gave out the translation package? Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
bikedude wrote: ...And so the question become: Is the translation retained when changing from "Unused" to "New"? (I.e. when the text reappears?) When you change row status (via Sisulizer UI or manually editing of SLP file in text editor), Sisulizer should retain translations. However, if Sisulizer doesn't find these items in source after next scan, you get again "Unused" status for these items in project. Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Jaakko.Salmenius wrote: If text disappers or its context changes the row becomes unused. It is still in the project but it not bound to any item. It remains in the project as long as you remove unused items byt choosing Project | Remove Ununsed Items. When you do that Sisulizer removes the unused rows and translations they contains. Before removing Sisulizer adds the translations into translation memory (however you can turn this feature off). If you have checked "Tools" menu -> "General" -> "Translations" tab -> "Translate new rows automatically after scanning", Sisulizer should automatically use existing translations (also with "Unused" status) for new items. Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 08:41 pm | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Translated texts AWOL | |
Sisulizer software localization tool - Three simple steps to localize
