The final step after translating and editing is to create the translated target files to your hard disk. This process is initialized with the menu item Create Target Files... in the menu File.
This step is optional. It creates the local language version of the application modules stored in the localization project (*.prj).
The translation is written into the target file(s) which are defined by the user. This is what to do:
Choose Create Target Files... from the menu File
The following dialog will appear:
Select the Target Language for your localization project:
Click on the Target Language combo box. All supported languages from your operating system (e.g. Windows 2000, Windows XP) are displayed. By default the target language which was used to create your localization project is selected. Usually there is no need to change it. However, if you wish to do so, select the language your translated target file(s) are in, i.e. the same language you selected for your target of translation when you created the localization project file (*.prj).
Insert the Target path for your localization project:
By default the target path will be the same path in which your source files are stored plus the subfolder "\target". To change this path, please click on the browse button to select a new target path for your localization project. The selected target path (i.e. "C:\test\Target\" see dialog above) will be used for ALL target modules listed in the column Target files. As result the target files (i.e. "notepad.exe", "TASKMAN.EXE", "twain.dll" and "VislocSample1.exe" see dialog above) will be stored into the same target folder "C:\test\Target".
In case that some target modules listed in the column Target files shall be stored into a subfolder from the Target path "C:\test\Target\", please insert the name of the subfolder directly in front of the target file name.
For example: "\subfolder\TASKMAN.EXE". Now the file "TASKMAN.EXE" will be stored into the folder "C:\test\Target\subfolder\"
In case that you want to store one or more target files on a completely different program folder or hard disk, please click on the small browse button in the column Target files and select the desired location on the dialog Specify target file name.
Select the creation of .NET Satellite Assemblies via the check box in column Sat.Assem.:
All .NET base assemblies (*.EXE or *.DLL) will be automatically recognized as developed on basis of a Microsoft™ .NET Framework. For these base assemblies you can instruct Visual Localize to create a corresponding .NET satellite assembly (*.resources.dll) by checking on the checkbox. (For WIN 32bit application modules this checkbox is disabled.) In case that the checkbox is checked on, Visual Localize will also modify the target path and file name in the column Target files.
For example:
The translated .NET base assembly "VislocSample1.exe" will be stored as satellite assembly in the target folder "C:\test\Target\" + "\de\VislocSample1.resources.dll" and "C:\test\Target\" + "\de-DE\VislocSample1.resources.dll"
Source files and Target files:
Source Files and Target Files are automatically displayed in the file list. The default target file names are copied from the source file names. The names of source files are not editable whereas the names and directories of target files can be changed by the user. To change the name of a target file, just click with your mouse into the cell with the file name. Then use your keyboard to edit the name of your target file or path.
If you do not want to create the target file for all modules stored in the localization project, you can remove the desired modules by selecting the row with your mouse. A black arrow in front of the row will display which row you have selected. Then please click on the delete button .
Confirm your settings and start the creation of the target files by clicking on the OK button. Visual Localize will write the translated target files into their target path(s).
All your settings (e.g path and file names for your target files) will be stored in your localization project each time the OK button was pressed.
In case that a source .NET base Assembly (EXE or DLL) was signed from the developer, Visual Localize will ask the user to specify the key file which shall be used to re-sign the translated files.
Further Information
Reload (Update) a Module with a New Version