Localizing executable files |
SolutionLocalising executable files with Message Table resourcesIn Alchemy Catalyst the support for Message Tables is enabled through the use of the MessageTable.dll plug-in. This dll is by default enabled in Alchemy Catalyst via the Custom Editors dialog box. To add the Message Table plug-in navigate to: Tools > Options > Custom Editors. See the screen below. If missing, on the above screen select Add and then enter the details you see in the screenshot above into the form. Now you have added the MessageTable.dll custom editor you will be able to localize Message Tables in Alchemy Catalyst. Localizing 16 bit binariesAlchemy Catalyst does not provide direct support for inserting and localizing 16 bit binaries. The following is a work around for localizing these files in Alchemy Catalyst. Creating a 32 bit stem with the 16 bit resource: The recommended solution is to copy the resources from the 16 bit DLLs into an empty 32 bit stub file. This is a process that will need to be carried out in Visual Studio. Simply open both the 16 bit exe/dll and a 32 bit exe/dll in Visual Studio. Be sure to open As Resources. Select the resources to be localised from the 16 bit exe/dll and copy into the empty 32 bit file. Above you will see both a 16 bit executable and below a 32 bit executable open in Visual Studio. If you do not have an empty 32 bit file, you can create one by taking any 32 bit file, for example Notepad.exe, delete its resources and save as any filename. For example: Stub.exe. Localizing the created 32 bit file Once the 16 bit resources are copied into Stub.exe (see screenshot below), you have the full editing capabilities of Alchemy Catalyst available to your 16 bit resources. You should now insert your 16 bit executable into a TTK as if it is a 32 bit executable and localize the file. Returning to a 16 bit executable The reverse process is then required after editing has been completed. Extract the localized executable from the TTK in Alchemy Catalyst. Next open the 16 bit executable in Visual Studio and then copy the localized resources into the 16 bit file.
Related topicsProducts or Versions Affected
|