• Home
• Imprint/Impressum
• Localization Glossary
• Who we are

My Win32 file contains custom resource with strings, but Sisulizer can’t correctly recognize it. Could I fix it?

Sisulizer always correctly recognize standard resources, for example dialogs, menus, strings, versions resources (for Visual C++ binary file). Unfortunately, Sisulizer in some cases can’t correctly recognize custom resources with non standard contents. But don’t worry, if you right click on such a node you should see it in context menu “Properties” item. It opens “Custom Format” dialog. This item is not available for standard resource types (e.g. for dialogs or forms). However, you can find this item also for common in binary files XML and HTML resources. These resources often require customization, e.g. selection of tags and attributes to localization in XML resources. When you click on “Properties” item from context menu for XML node, you should to see “XML Tags” tab in “Custom Format” dialog, where you can check, uncheck or change kind of desired items. Below is example with customized tags for XML node from Delphi source file:

Resource nodes always contain at least one sub-item, but sometimes these nodes can contains more items, and some of these items can be different types. Below is example for node with mixed HTML and Text contents (some sub-items have HTML format, other have plain Text format). In “Format” tab of “Custom Format” dialog is displayed information about used formats in node. You can find here also tabs with settings specified for each detected or selected format. Of course, tabs aren’t displayed for not localizable resource types (plain binary data, pictures).

When Sisulizer can’t correctly recognize format of your resource, you should uncheck “Automatic Format” checkbox in “Format” tab of “Custom Format” dialog, and select appropriated format for your resource. Below is list of available formats:

• Plain binary
• User defined binary
• Plain text
• User defined text
• Picture
• XML
• HTML

Next you should adjust settings for selected format types. Plain binary, Plain text and Picture formats haven’t any settings, while User defined binary and User defined text require defining of format (format definition). User defined binary was implemented to build 292.

If you changed format on parent node level, new/edited format is applied to all sub-items of this node. When some sub-item use other format, simple navigate to this item, right click on it, select “Properties” from context menu, uncheck “Automatic Format”, and select desired format form list. In this way you can easy manage resource with mixed contents.

Of course, all format changes require re-scan of source.

Janusz

Did you enjoy this post? Why not leave a comment below and continue the conversation, or subscribe to my feed and get articles like this delivered automatically to your feed reader.