|
|||
|
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 > Can Sisulizer find strings that should not be translated?
|
|
|||
|
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 > Can Sisulizer find strings that should not be translated?
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Can Sisulizer find strings that should not be translated? - 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 | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
Ann-Christin Member
|
Hello, Is there a possiblility to detect strings that should not be translated, like e.g. internal software commands? Because in the wordpad sample i have localized for my thesis are the menu strings: TEXT_POPUP (containing a few regular strings like Cut, Copy, Paste,... but also the string <<OLE VERBS GO HERE>> which also shows up in a few other menus) MISC (containing the strings: Bold, Italic, Color,Underline, Left, Right, Center, Print Direct, Period, Space, Backspace, New Line, Pen, Lens) and COLOR_POPUP (containig different colors). Those strings in capital letters represent internal commands, don't they. How should they be delt with? Should they just be marked "Read only"?
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator 
|
Sisulizer localized resource data from Windows applications (.exe) and libraries (.dll). Typically all resource data is localizable and should be localized if the value in the target language is different than in the original language. If you have some string that should not be localized they should not be placed to resources at the first place but hard coded to the code. However if resources contains string that should not be localized then you have to use Sisulizer's Exclude feature to exclude those string from the project or mark them to Read only. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Ann-Christin Member
|
Good morning again, Ok, thank you and how do I recognize untranslatable strings?
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator
|
I think that you understod me wrong. All strings that are visible in Sisulizer are translatable. So you can enter translation for them. If you do not want to translate a string simple do not enter translation or make it read only or exclude it from the project. My oint was the the best solution would be that the developer would not put that string into resource data and then it would not appear in the Sisulizer projectat all. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| Current time is 09:22 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 > Can Sisulizer find strings that should not be translated? | |
Sisulizer software localization tool - Three simple steps to localize
