|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Marking resource items as 'not to be included in the generated dll'
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Marking resource items as 'not to be included in the generated dll'
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Marking resource items as 'not to be included in the generated dll' - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
MikeBz Member
|
I would like to be able to mark some of my resource items (some dialog boxes, maybe some strings as well) as 'unused' and then remove them so that they don't get written to the generated dll. The reason is: I have code which hooks FindResource(), my hook function first looks for the resource in the current language dll and if it can't find it in there it loads it from the app's exe. The app's .exe contains English translations of all resource items. Some resource items are not and never will be translated, so I want to completely exclude those items from the generated language dlls so they always get loaded from the .exe. Then if during development I modify those never-to-be-translated resource I don't have to update & reissue all the language dlls because those resources are not loaded from them. Maybe there is a way of doing this which I haven't found? Mike
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Mike, The default behavior of Sisulizer is, that if you do enter a translation to a target language a fallback to the original string is automatically used. Delphi and .NET do it that way. I'm not sure about MFC, but it should be the same as well. To prevent these entries from being translated you should mark them as "Do Not Translate". You can do that for complete dialogs in the translation tree on the left side (use right click...). Hope this helps Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
MikeBz Member
|
Hi Markus, I have them marked as 'Excluded' and 'Do not translate' but they still get written out to the dlls. I want them to not be written to the dlls. Regards, Mike
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator 
|
Sisulizer writes them even if you have marked them Excluded. The only way you can optimize it is to exclude the resource type and then uncheck Copy all resource check box. However it still writes excluded items. This is incorrect and it should be just liek you told. This is why I fixed this in buuld 289. You have to wait for build 289 and then uncheck Copy all resources. Then you get what you expect. Jaakko Attachment: Untitled.png (Downloaded 17 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
MikeBz Member
|
Thanks Jaakko. I already have 'Copy all resources' unchecked, and as you say it still writes the excluded items to the dll. I'll wait for 289. Mike
|
||||||||||||||||
| |||||||||||||||||
| Current time is 08:27 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 > Marking resource items as 'not to be included in the generated dll' | |
Sisulizer software localization tool - Three simple steps to localize
