Multilingual project

ONLINE HELP
WINDEV, WEBDEV AND WINDEV MOBILE

Version:

Home | Sign in | English

Help

WLanguage

WLanguage functions

Controls, pages and windows

Multilingual functions

Multilingual project

Special case: Translating the windows and pages proposed by default

Related examples

See also

Developing multilingual applications

Multilingual project

This table explains how to create and manage a multilingual project.

See Developing multilingual projects for more details.


Project elements	Project	Window, pages and controls (text, input masks and images)	Reports and controls (text, display mask and images)	Help system (hlp or chm)	Code messages (code, procedures, classes)	WINDEV messages
Action to perform	Project			Help system (hlp or chm)	Code messages (code, procedures, classes)	WINDEV messages
Choosing the different languages	The project languages are selected in the project description: On the "Project" pane, in the "Project" group, click "Description". Select the "Language" tab. The selected languages are taken into account for all the closed elements. The opened elements must be closed and re-opened.	Automatic if the language is managed in the project. Windows shared among several applications that do not use the same languages: Select the additional language in the window description ("Language" tab).	Automatic if the language is managed in the project. Reports shared between several applications that do not use the same languages: Select the additional language in the report description ("Language" tab).	Automatic if the language is managed in the project. Help system shared between several projects that do not use the same languages: Select the additional language in the description of the help system ("Language" tab).	Automatic if the language is managed in the project. Classes and procedures shared between several projects: Select the additional language in the language window (right click in the "Project explorer" pane, "Language" option).
Creating a new control		By default, only the caption of runtime language is specified. The caption of the control must be translated into the supported languages.	By default, only the caption of runtime language is specified. The caption of the control must be translated into the supported languages.	The title of the new pages and the keywords are automatically created in English.
Translation without specific tool (in WINDEV directly)		The translation must be performed in all description windows of windows and controls.	The translation must be performed in all description windows of reports and controls.	For the summary and the indexes: the translation must be performed in the description windows of the page. For the content of help page: the translation must be performed after the change of display language.	The translation must be performed in the message editor (Ctrl + T).
Translating messages with WDMSG/WDINT		Extract all messages to translate with WDMSG, translate the file generated by WDMSG and reintegrate the translated messages.				Extract and translate with WDINT. Generate a WDM file.
Display in the editor in a given language	Change the display language for all project elements: on the "Display" pane, in the "Options" group, expand "Language displayed" Caution: the default runtime language of project is not modified.	Automatic if the display language of project was modified. To modify the display language for all project elements: on the "Display" pane, in the "Options" group, expand "Language displayed" (*)	Automatic if the display language of project was modified. To modify the display language for all project elements: on the "Display" pane, in the "Options" group, expand "Language displayed" (*)	Automatic if the display language of project was modified To modify the display language for all project elements: on the "Display" pane, in the "Options" group, expand "Language displayed" (*)	Automatic if the display language of project was modified. To modify the display language for all project elements: on the "Display" pane, in the "Options" group, expand "Language displayed" (*)
Test	The project test is run in the default language of project.	The window test is run in the default language of project.	The report test is run in the default language of project.	Compilation and test run in the display language of help system. You must create as many help files as the number of languages.	During a test (window, project or report), message displayed in the default runtime language of project.	Define the WDM file associated with each language in the project description: On the "Project" pane, in the "Project" group, click "Description". Select the "Language" tab.
Executable	Created in the default project language. To change this language as soon as the executable is run, use Nation in the initialization code of the project. Caution: the language will be modified from the call to Nation and until the next call to Nation.	Windows displayed in the executable language. To change the display language of a window, use Nation before opening the window. Caution: the language will be modified from the call to Nation and until the next call to Nation.	Reports printed in the default executable language. To change the print language of a report, use: Nation before printing the report. Caution: the language will be modified from the call to Nation and until the next call to Nation. Versions 19 and later iPrintingNation. New in version 19 iPrintingNation. iPrintingNation.	Open the help file corresponding to the desired language (WHelp).	Messages displayed in the current runtime language. To change the language when displaying the message, use Nation. Caution: the language will be modified from the call to Nation and until the next call to Nation.
Deployed site	Created in the default project language. To change this language as soon as the deployed site is run, use Nation in the initialization code of the project. Caution: the language will be modified from the call to Nation and until the next call to Nation.	Pages displayed in the project language. To change the display language of a page, use Nation before opening the page. Caution: the language will be modified from the call to Nation and until the next call to Nation.	Reports printed by default in the project language. To change the print language of a report, use: Nation before printing the report. Caution: the language will be modified from the call to Nation and until the next call to Nation. Versions 19 and later iPrintingNation. New in version 19 iPrintingNation. iPrintingNation.		Messages displayed in the current runtime language. To change the language when displaying the message, use Nation. Caution: the language will be modified from the call to Nation and until the next call to Nation.

(*): if the control caption does not exist in the display language, the control is left empty in the editor.

Special case: Translating the windows and pages proposed by default

The following elements can be automatically included in your applications or sites:

HFSQL windows for automatic management of HFSQL programming errors.
windows or pages of user groupware. These elements are used to manage the connection of a user to an application and the different access levels for each user.
the setup program, allowing the user to install his application or his site.

Remark: From version 19, HFSQL is the new name of HyperFileSQL.

Including and translating the windows and pages proposed by default

These windows and pages are available in English and French by default. To support additional languages, the following operations must be performed:


		HFSQL windows and pages	User groupware	Setup program
Purpose	Display the report in "Preview" mode, and allow the user to print via the desired medium (printer, XML file, etc.).	Allow the user to manage duplicate errors, integrity errors, password errors, lock errors, etc.	Used to manage the connection of a user to an application as well as the different access levels for each user.	Allow the user to install the application on his computer.
Integration in the project	Request the integration of windows in your project: Open the project description: on the "Project" pane, in the "Project" group, click "Description". Display the "Style" tab. In "Report viewer", select "Custom (included in the project)". Select the type of customization to perform: <Standard report viewer (without skin template)>: this option imports the standard print windows into your project. <Standard report viewer with the skin template of the project>: this option imports the print windows corresponding to the skin template of your project.	On the "Project" pane, in the "Project" group, expand "Import" to import the files located in this directory: "\Programs\Data\Preset pages\HFSQL - Pages for automatic help".	Request the integration of pages in your project: on the "Project" pane, in the "Project" group, click "User groupware". Select "Enable the management of user groupware" and "Custom integration".	Open and translate the WDSETUP project supplied with WINDEV.
Translation without any specific tool or with WDMSG	See the above table
Use in the selected language	Automatic according to the default runtime language of project.	Automatic according to the default runtime language of project.	Automatic according to the default runtime language of project.	Automatic. All you have to do is configure the language used for the setup program: in the setup wizard: on the "Project" pane, in the "Generation" group, expand "Setup procedure" and select "Create setup procedure". in WDInst: on the "Tools" pane, in the "Utilities" group, click "WDInst". Caution: To use WDSetup in languages other than French or English, WDInst must be used to create the setup program.
Change the language with Nation	Automatic	Automatic	Cancel the automatic start of the first window or page from the groupware: On the "Project" pane, in the "Project" group, click "User groupware". In the "General" tab, select "Manual start". Change the language with Nation (e.g. project initialization code). Open the first window or page found in the groupware with gpwOpen.

Windows of AAF (Automatic Application Features)

Some AAFs (Automatic Application Features) use specific windows. These windows can be included in the application to be translated. List of main features that require a specific integration in order to be translated:

Scheduler control and Organizer control: Translating the window of appointments.
Versions 17 and later
Organization Chart control: Translating the window of elements.
New in version 17
Organization Chart control: Translating the window of elements.
Organization Chart control: Translating the window of elements.
Locking the application: Translating the lock window.
Managing the keyboard shortcuts: Translating the window for adding shortcuts.
Displaying a line of an edit control: Translating the window for line input.
Defining a timer: Translating the window for defining the timer.
Multi-control search: Translating the search window.
History of modifications: Translating the window for displaying the history.
Calendar: Translating the popup menu of calendar.
Versions 17 and later
Calculator: Translating the options.
New in version 17
Calculator: Translating the options.
Calculator: Translating the options.
Versions 17 and later
Automatic print of Scheduler controls: Translating the window for print configuration.
New in version 17
Automatic print of Scheduler controls: Translating the window for print configuration.
Automatic print of Scheduler controls: Translating the window for print configuration.
Versions 17 and later
Automatic print of Organizer controls: Translating the window for print configuration.
New in version 17
Automatic print of Organizer controls: Translating the window for print configuration.
Automatic print of Organizer controls: Translating the window for print configuration.

Related Examples:

Training (WINDEV): WD ChainedList

[ + ] This example supplies the tools required to build chained lists (simple sequencing). This type of list is used to store and browse a set of values in an organized way.

In the example, a chained list is used to store buttons.
- The list is then used to hide/move the buttons in the screen, creating a dynamic menu (Sidebar).
- The list is also used to translate the buttons without having to reload the window. To do so, the French caption and the English caption are stored for each button. The advantage of this method is to keep the status of the window, especially the menu in its drop-down aspect, the information text, and so on.

Specific feature of this example:
- this example is a multilingual example (French/English).