|
|||
|
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 > Remove unused Items, Remove unnecessary Translations
|
|
|||
|
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 > Remove unused Items, Remove unnecessary Translations
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Remove unused Items, Remove unnecessary Translations - 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 | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
aschaepper Member
|
Hello Dear Im just using the new Sisu 2008 and i've some question about the two given features. (Even if they were in Sisu 1.5). "Remove Unnecessary Translation" From the Helpfile; Remove all unnecessary translations from the project. For example if you have moved a control (it's left property has been translated). Then you moved the control exactly to it's original place. Now the control have a translation that is identical with the original value. Those translations are unnecessary and can to removed. I just don't understand why a translation should become unused when i move a control? (But i have to say that i never used the integrated .NET Translations mechanism, all our "localizable" props are set to false and we do translations only via "Strongly Typed Resources". So maybe thats the reason why i don't understand this? "Remove Unused Items" Just to be sure. This means the original english string was deleted and therefore the translations can be removed because they are unused. Is that right? Thanks for your help Greetings Alex
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Alex, a control has more than just its text to localize. You can also "localize" its position. If you include all data types in your project you will see them. If the position is not changed then Sisulizer does not need to store it. The translation is displayed in grey text. To make it clearer. If you translated "OK" with "OK" then this translation was unnecessary because Sisulizer would have used the original "OK". If you move a control the translations gets a localized position (x/y). If you move it back to the original position the new X/Y position is the same as in the original and is redundant. Removing it reduces the size of the Sisulizer project. Unused items are marekd with a little blue dot at the beginning of the row. If you remove parts of your code and then use Scan for Changes Sisulizer will mark the strings from the removed parts as unused. These can be removed to shrink the project. Sisulizer stores translations made to these elements in the translation memory. If you later re-add the removed source parts to your product Sisulizer still knows the translations in its TM. No translation gets lost. Hope this helps Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
aschaepper Member
|
Hello Markus Thanks for your fast reply, it is now a lot cleaner. Greetings
|
|||||||||||||
| ||||||||||||||
| Current time is 08:01 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 > Remove unused Items, Remove unnecessary Translations | |
Sisulizer software localization tool - Three simple steps to localize
