Home | Sign in | English UK
This content comes from an automatic translation.
  • Overview
  • How to proceed?
  • Translating a component used in an application
  • Translating and updating the component
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WindowsLinuxPHPWEBDEV - Browser code
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Stored procedures
Translating the external components
An external component is a set of WINDEV, WEBDEV or WINDEV Mobile elements that perform a specific feature (sending faxes, emails, ...). The external components can be redistributed to the other WINDEV, WEBDEV or WINDEV Mobile developers.
These developers will be able to easily include the feature proposed by the component in their application. The component will be included in the application and distributed with the application.
For the multilingual applications, it may be useful to translate the external component used. Indeed, let's imagine a component that supports French and English included in a project that supports French and Spanish.
By default, the mechanism for preferred languages proposes English instead of Spanish.
In order for the external component to use the application language, the different elements of the components must be translated. This technique requires the use of WDMSG. WDMSG is an optional tool of WINDEV, WEBDEV or WINDEV Mobile used to check out and to check back in all the messages to translate.
How to proceed?

Translating a component used in an application

To translate a component used in an application:
  1. Install (if necessary) WDMSG on the development computer.
  2. The component used by the project must be defined as translatable: the translation of the component must have been allowed by the author of the component.
    To do so, check "Allow the component to be translated" when generating the component. See Generating a component for more details.
    To find out whether the components used can be translated, display the description of the component ("General" tab).
  3. Use WDMSG to check out the elements from the component (and from your project if necessary): under the "Project" section, in the "Translate" group, scroll down "Translate" and select "Message retrieval".. A wdmsg file containing the messages to translate is created.
  4. Translate the messages (or contact a translator). See Using WDMSG for more details.
  5. Check in the translated messages: under the "Project" pane, in the "Translate" group, scroll down "Translate" and select "Message Reintegration".. Several files are automatically created during the check-in operation:
    • <ComponentName>.WDIT: This file contains the different messages of the component in the source language as well as their translation. This file is found on the development computer only.
    • <ComponentName>.WDKT: This file contains the different translations of the component in the requested language. This file will be used at run time to display the translated messages in the requested language.
  6. The application can be deployed.

Translating and updating the component

The version of the component changes when the component is updated in the project.
When updating the component, the WDKT file is automatically re-created from the existing translations found in the WDIT file. Indeed, the version of the component must be synchronized with the version of the WDKT file. To do so, WDMSG must be installed on the computer.
The component is ready to be used.
  • If all the resources of the component have been translated, the component elements will be displayed in the requested language.
  • If some resources have not been translated, the untranslated resources will be displayed in the source language of the component. In this case, a new check-out must be performed by WDMSG in order to translate the missing resources.
Minimum version required
  • Version 12
This page is also available for…
Click [Add] to post a comment