PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US
  • Overview
  • How to proceed?
  • Checking out the project messages
  • Check-out parameters
  • Check-out parameters for a translation software
  • Notes
  • Format of text file of messages
  • Common 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 checked out:
  • 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 (list box, combo box, check box, radio button, Rich Text Area, ...)
  • Caption and help message associated with a menu option
  • Wait messages of 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?

Checking out the project messages

To check out the project messages:
  1. Open your project in WINDEV, WEBDEV or WINDEV Mobile ("File .. Open a project").Open your project in WINDEV, WEBDEV or WINDEV Mobile: on the "Home" pane, in the "General" group, expand "Open" and select "Open a project".
  2. Start WDMSG ("Tools .. WDMsg .. Check out the messages").Start WDMSG: on the "Project" pane, in the "Translate" group, expand "Translate" and select "Check out the messages".
  3. Select the language of messages to check out. This language corresponds to the language used for the development, to be translated into other languages.
    The available languages are the ones defined in the "Languages" tab of the project description ("Project .. Project description").
    Select the language of messages to check out. This language corresponds to the language used for the development, to be translated into other languages.Select the languages of messages to check out. These languages correspond to the languages already available in the project, to be translated into other languages.
    Choosing the extraction languages
    The available languages are the ones defined in the "Languages" tab of the project description.
    Notes:
    • Versions 21 and later
      The name of custom languages is also proposed.
      New in version 21
      The name of custom languages is also proposed.
      The name of custom languages is also proposed.
    • To display the project description, on the "Project" pane, in the "Project" group, click "Description".
    • Versions 22 and later
      To select multiple extraction languages, use the CTRL and/or SHIFT keys on the keyboard.
      New in version 22
      To select multiple extraction languages, use the CTRL and/or SHIFT keys on the keyboard.
      To select multiple extraction languages, use the CTRL and/or SHIFT keys on the keyboard.
  4. Go to the next wizard step.
  5. Versions 22 and later
    If you have selected several languages, specify the reference language, ie the language used during the development. Messages from this reference language must be translated into other languages.
    New in version 22
    If you have selected several languages, specify the reference language, ie the language used during the development. Messages from this reference language must be translated into other languages.
    If you have selected several languages, specify the reference language, ie the language used during the development. Messages from this reference language must be translated into other languages.
  6. Versions 22 and later
    Go to the next wizard step.
    New in version 22
    Go to the next wizard step.
    Go to the next wizard step.
  7. Select the different elements (windows, pages, reports, ...) whose messages (caption, code message, ...) must be checked out.
    Choosing the elements to extract
    Notes:
    • You have the ability to only select the elements not translated into the selected language.
    • Versions 20 and later
      If the elements of your project are grouped by custom-folders, the elements proposed by WDMSG will also be grouped by custom-folders.
      New in version 20
      If the elements of your project are grouped by custom-folders, the elements proposed by WDMSG will also be grouped by custom-folders.
      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. Versions 22 and later
    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.
    New in version 22
    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.
    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 check-out (see Details of parameters). Specify the name and directory of extraction file (the extraction file is created in the directory of current project by default).
  12. Go to the next step.
  13. When checking out the messages, you can check whether the messages that were previously checked out are identical to the messages found in the current project. See Checking out the 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 format of the extraction file (for example, if the keywords of this file are inadvertently changed).
  • compare the checked-out messages and the messages found in the current project (during the check-in).
The checked-out file can be translated:
  • by a specific translation software (extraction file in text format only).
  • or by WDTRAD, translation tool supplied with WDMSG.
Notes:
  • For a check-out in the format of a HFSQL data file, 3 files are created:
    • data file (.fic).
    • index file (.ndx).
    • memo file (.mmo).
  • Versions 22 and later
    Multilingual check-out: During a multilingual check-out:
    • in text format, a file is generated for each language.
    • in HFSQL or WDMSG format, a single file containing the different languages is generated.
    New in version 22
    Multilingual check-out: During a multilingual check-out:
    • in text format, a file is generated for each language.
    • in HFSQL or WDMSG format, a single file containing the different languages is generated.
    Multilingual check-out: During a multilingual check-out:
    • in text format, a file is generated for each language.
    • in HFSQL or WDMSG format, a single file containing the different languages is generated.

Check-out parameters

The check-out parameters are as follows:
  • Extract all the strings from the code: 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. These strings are enclosed in quotes.

      By default, only the multilingual character strings are extracted. To extract the non-multilingual character strings from the code, check "Extract all the strings from the code". These strings will automatically become multilingual strings when they are checked back in.
  • Generate the comments: if this option is checked, 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, ...).
  • Add the shortcuts: this parameter allows you to include the "&" character in the captions of controls to specify the control shortcut.
    Reminder: This shortcut gives direct access to the control by pressing [ALT]+[Letter]. In the caption of a control, any letter preceded by the "&" character automatically becomes the control "shortcut".
  • Convert to OEM format: if this option is checked, 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).
  • Name of generated extraction file: name and path of extraction file. This information can be modified with the browse button ("...").
    If the extension of this name is:
    • ".txt", the extraction file will be a file in text format.
    • ".fic", the extraction will be a HFSQL data file.
    • Versions 20 and later
      ".wdmsg", the extraction file will be a file in WDMSG format.
      Note: We recommend that you use files in WDMSG format.
      New in version 20
      ".wdmsg", the extraction file will be a file in WDMSG format.
      Note: We recommend that you use files in WDMSG format.
      ".wdmsg", the extraction file will be a file in WDMSG format.
      Note: We recommend that you use files in WDMSG format.
The extraction parameters common to all extraction file types are as follows:
  • Keep the shortcut indicator ("&") in the checked-out messages : this parameter allows you to include the "&" character in the captions of controls to specify the control shortcut.
    Reminder: This shortcut gives direct access to the control by pressing [ALT]+[Letter]. In the caption of a control, 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 the non-multilingual character strings from the code, check "Transform all the hard coded strings into multilingual string". These strings will automatically become multilingual strings when they are checked back in.
  • Convert to OEM format (ANSI by default): if this option is checked, 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 the next paragraph).

Check-out 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: 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 checked, 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 at the beginning of message: with some translation software, a space must be added before the delimiter.
    If this option is checked, a space character is added before the delimiter.
  • Add a space at the end of message: with some translation software, a space character must be added after the delimiter.
    If this option is checked, a space character is added after the delimiter.
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 checked, 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 checked, 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 checked, a space character is added after the delimiter.
  • Add additional information in comment: if this option is checked, 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 check-out file created by WDMSG is using a specific format. See the format of text files of messages for more details.

Common project

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