PC SOFT

WINDEVWEBDEV AND WINDEV MOBILE
ONLINE HELP

Home | Sign in | English UK
  • Overview
  • How to proceed?
  • Extracting project messages
  • Extraction parameters
  • Extraction parameters for a translation software
  • Notes
  • Format of text file of messages
  • Multi-product project
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Others
Stored procedures
Overview
The following messages are extracted:
  • Messages displayed by "MessTranslate":
    • Messages found in the project (".WDP", ".WWP" or ".WPP" file).
    • Messages found in the project classes (".WDC" file).
    • Messages found in the project reports (".WDE" file).
    • Messages found in the project windows (".WDW" or ".WPW" file).
    • Messages found in the project pages (".WWH" file).
    • Messages found in the project queries (".WDR" file).
    • Messages found in the sets of procedures (".WDG", ".WWN" or ".WWG" file).
  • Title of a window, page.
  • Caption of a control (found in a window, in a page or in a report).
  • Help message associated with a control.
  • Tooltip of a control.
  • Title and text of help window associated with a control.
  • Note associated with a control (found in a window, in a page or in a report).
  • Content of a control (e.g. List Box, Combo Box, Check Box, Radio Button, Rich Text Area, etc.).
  • Caption and help message associated with a menu option.
  • Temporization message for a report.
  • Characteristics of shared information typed in the analysis.
  • Title of help system.
  • Copyright of help system.
  • Index keywords of help system.
  • Title and content of help page.
  • Custom error message typed when creating the executable.
  • Name of window or internal page used.
  • ...
How to proceed?

Extracting project messages

To extract the project messages:
  1. Open your project in WINDEV, WEBDEV or WINDEV Mobile: on the "Home" pane, in the "General" group, expand "Open" and select "Open a project".
    Versions 25 and later
    Remark: To extract all resources from a multi-product project, open the project in WINDEV (in a configuration with WEBDEV and WINDEV Mobile integrated into WINDEV).
    New in version 25
    Remark: To extract all resources from a multi-product project, open the project in WINDEV (in a configuration with WEBDEV and WINDEV Mobile integrated into WINDEV).
    Remark: To extract all resources from a multi-product project, open the project in WINDEV (in a configuration with WEBDEV and WINDEV Mobile integrated into WINDEV).
  2. Start WDMSG: on the "Project" pane, in the "Translate" group, expand "Translate" and select "Extract messages".
  3. Select the languages of the messages to extract. These languages correspond to the languages already available in the project, to be translated into other languages.
    Choosing the extraction languages
    The languages proposed are those defined in the "Languages" tab of the project description.
    Remarks:
    • The name of custom languages is also proposed.
    • To display the project description, go to the "Project" pane, "Project" group, and click on "Description".
    • To select multiple extraction languages, use Ctrl and/or Shift.
  4. Go to the next step of the wizard.
  5. If you have selected several languages, specify the reference language, i.e. the language used during the development. Messages from this reference language must be translated into other languages.
  6. Go to the next step of the wizard.
  7. Select the different elements (windows, pages, reports...) whose messages (caption, code message...) must be extracted.
    Choosing elements to extract
    Notes:
    • You can select only non-translated or non-corrected elements in the selected language.
    • If the elements of your project are grouped by custom-folders, the elements proposed by WDMSG will also be grouped by custom-folders.
  8. Go to the next step.
  9. Choose the type of file to generate:
    Choosing the type of file
    • WDMSG archive. This type of file can only be used to perform a translation with WDTRAD.
    • HFSQL file. This type of file can only be used to perform a translation with WDTRAD.
    • Text file. This type of file can be used to perform a translation with WDTRAD or with another translation software.
  10. Go to the next step.
  11. Select the parameters of the result file created by the extraction (see Details of parameters). Specify the name and directory of the extraction file (by default, it is created in the directory of the current project).
  12. Go to the next step.
  13. When extracting messages, you can check whether the messages that were previously extracted are identical to the messages of the current project. See Extract modified messages for more details.
  14. Go to the next step.
  15. Validate.
The extraction file is created in the selected directory (project directory by default). We advise you to perform a backup copy of the extraction file. This backup copy will be used to:
  • retrieve the extraction file format (for example, if the keywords of this file are inadvertently changed).
  • compare the extracted messages and the messages of the current project (during reintegration).
The extracted file can be translated:
  • by a specific translation software (extraction file in text format only).
  • or by WDTRAD, translation tool supplied with WDMSG.
Remarks:
  • For extractions as HFSQL data file, 3 files are created:
    • data file (.fic).
    • index file (.ndx).
    • memo file (.mmo).
  • Multilingual extraction: During a multilingual extraction:
    • in text format, a file is generated for each language.
    • in HFSQL or WDMSG format, a single file containing the different languages is generated.

Extraction parameters

The extraction parameters common to all extraction file types are as follows:
  • Keep the shortcut indicator ("&") in the extracted messages : this parameter allows you to include the "&" character in the captions of controls to specify the control shortcut.
    Reminder: This shortcut is used to directly position on the control at run time by pressing Alt + Letter. In the control caption, any letter preceded by the "&" character automatically becomes the control "shortcut".
  • Transform the hard-coded strings into multilingual strings: Two types of character strings are found in the code:
    • the multilingual character strings. These strings are followed by a flag:
    • the non-multilingual character strings (also called "hard coded"). These strings are enclosed in quotes.
    By default, only the multilingual character strings are extracted. To extract non-multilingual character strings from the code, check "Transform all hard-coded strings into multilingual string". These strings will automatically become multilingual strings when they are reintegrated.
  • Convert to OEM format (ANSI by default): if this option is enabled, the text of the extraction file will be in OEM format (format of DOS characters, usable with a DOS software); otherwise, the text will be in ANSI format (format of Windows characters, usable with a Windows software.
You can also define parameters specific to your own translation software (see next paragraph).

Extraction parameters for a translation software

The following parameters are not required if you are using WDTRAD to translate the messages found in your project.
If you are using another translation software, specific parameters must be defined (these parameters may differ according to the software used). The parameters specific to the translation software used are as follows:
  • Add a delimiter for the text sections not to translate: with some translation software, sections of text can be ignored in the document to translate. 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 they will not be translated.
    See the documentation about the translation software for more details.
  • Add a space before the delimiter: with some translation software, a space must be added before the delimiter.
    If this option is enabled, a space character is added before the delimiter.
  • Add a space after the delimiter: with some translation software, a space character must be added after the delimiter.
    If this option is enabled, a space character is added after the delimiter.
  • Add additional information in comment: if this option is enabled, comment lines will be added into the created extraction file. These lines are used to find out the origin of messages (messages associated with a control, a window, ...).
Notes

Format of text file of messages

The extraction file created by WDMSG uses a specific format. See format of text files of messages for more details.

Multi-product project

If the current project is a multi-product project (WINDEV, WEBDEV and/or WINDEV Mobile):
  • during the extraction from WINDEV (with WEBDEV and WINDEV Mobile integrated into WINDEV), elements of different products are all taken into account.
    For example, windows and pages are extracted in a WINDEV and WEBDEV project.
  • during the reintegration from WINDEV (with WEBDEV and WINDEV Mobile integrated into WINDEV), elements of different products are all taken into account
Minimum version required
  • Version 9
This page is also available for…
Comments
Click [Add] to post a comment