ONLINE HELP
 WINDEVWEBDEV AND WINDEV MOBILE

This content has been translated automatically.  Click here  to view the French version.
Help / Tools / Translation tools / WDMSG
  • Overview
  • How to?
  • Comparing the project messages
  • Comparison parameters
  • Comparison parameters for a translation software
WINDEV
WindowsLinuxJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac Catalyst
Others
Stored procedures
Overview
The comparison between source and target text helps you find translation errors:
  • same text in both languages.
  • messages not translated in one of the languages.
The comparison file is created in the reference language. The comparison file and the extraction file have the same format (WDMSG file, HFSQL data file or text file). For more details on the format of the comparison text file, see format of the content in the text file
If this file is in text format, it can be handled by WDTRAD or by another translation software like an extraction file. If this file is in HFSQL format or in WDMSG format, it can be handled by WDTRAD only.
This comparison file contains:
  • the messages identical in both languages.
  • the messages only displayed in the reference language.
The comparison file can be reintegrated once the modifications have been made. This reintegration is done in the same way as for the extraction file.
Note This file may be empty if no translation inconsistencies have been detected.
How to?

Comparing the project messages

To compare the messages of your project:
  1. Open your project in WINDEV, WEBDEV or WINDEV Mobile: in the "Home" pane, in the "General" group, pull down "Open" and select "Open a project".
  2. Launch WDMSG: under the "Project" pane, in the "Translate" group, scroll down to "Translate" and select "List of untranslated messages". The message comparison wizard opens.
  3. Choose the reference language. The different messages will be displayed in this reference language.
    Note: Customized language names are also available.
  4. Proceed to the next step of the wizard.
  5. Choose the language to compare.
    Note: Customized language names are also available.
    The comparison file will contain the messages:
    • that are identical in the reference language and in the language to compare.
    • that only exist in the language to compare.
  6. Go to the next step.
  7. Select the elements (windows, pages, reports, etc.) with text (captions, code comments, etc.) to be compared.
  8. Go to the next step.
  9. Choose the type of file to be generated:
    Choosing the type of file
    • WDMSG archive. This type of file can only be used to translate text with WDTRAD.
    • HFSQL data file. This type of file can only be used to translate text with WDTRAD.
    • Text file. This type of file can be used to translate with WDTRAD or with another translation software.
  10. Go to the next step.
  11. Select the different parameters of comparison file (these parameters are presented below). These parameters are the same as the ones used for a simple extraction. Your file can be checked back in after correction.
  12. Go to the next step.
  13. Validate. The comparison file is created in the selected directory (project directory by default). This file can be translated using specific translation software (text-only format) or using WDTRAD, the translation input tool supplied with WDMSG.
Remarks:
  • This comparison file may be empty if no messages correspond to the comparison.
  • For a comparison in the format of data files in HFSQL format, 3 files are included in the comparison file:
    • data file (.fic),
    • index file (.ndx),
    • memo file (.mmo).

Comparison parameters

The extraction options common to all file types are as follows:
  • Keep hotkey indicator ("&") in extracted messages Call letter: this parameter allows you to include the "&" character in field labels to indicate the field's call letter.
    Reminder: This hotkey allows you to position yourself directly on the field, using the Alt + Hotkey combination. In the control caption, any letter preceded by the "&" character automatically becomes the control "hotkey".
  • Convert to OEM format (ANSI by default) If this option is checked, the text in the extraction file will be in OEM format (DOS character format, usable with DOS software), otherwise the text will default to ANSI format (Windows character format, usable with Windows software).
You can also define options specific to the translation software used (see next paragraph).

Comparison parameters for a translation software

The following options are not required if you are using WDTRAD to translate the text of your project.
If you use another translation software, you need to define specific options (these options may vary depending on the software used). The options to be defined based on the translation software used are as follows:
  • Add a delimiter for parts of text not to be translated For some translation programs, it is possible to ignore parts of text in a document to be translated. For example, the comments generated by WDMSG can be ignored. To do so, the text sections to ignore must be enclosed in delimiters (specific to the software).
    If this option is enabled, all the sections of text specific to the format of the extraction file will be enclosed in delimiters (SSTRX by default) and will not be translated.
    For more details on delimiters, see the documentation of the translation software used.
  • Add a space before the delimiter For some translation programs, it is necessary to add a space before the delimiter.
    If this option is enabled, a space is added before the delimiter.
  • Add a space after the delimiter For some translation programs, it is necessary to add a space after the delimiter.
    If this option is enabled, a space is added after the delimiter.
  • Add additional information as comments If this option is checked, comment lines will be added to the extraction file created. These comments indicate the origin of the text (text from a control, window, etc.).
Minimum version required
  • Version 9
This page is also available for…
Comments
Click [Add] to post a comment

Last update: 06/26/2025

Send a report | Local help