Internationalisation programmation - Revision history

Gastounet: /* How it works ? */

2015-11-18T12:04:09Z

How it works ?

2014-11-17T07:18:42Z

Simple controls

2014-11-05T12:55:08Z

GGrid and GDbGrid

2014-11-05T12:52:07Z

Other strings

2014-11-05T12:39:35Z

Why

2014-11-05T12:33:22Z

Why

2014-11-05T12:33:02Z

Language file

2014-11-05T12:27:32Z

Other strings

2014-11-05T12:25:12Z

Messages

2014-11-05T12:13:03Z

GGrid and GDbGrid

@@ Line 17: / Line 17: @@
 === Language file ===
-Translation are stored in text files, referred as '''language files'''. In Gestinux 1.1 there is only one language file for each language.
+Translation are stored in text files, referred as '''language files'''.
-In Gestinux 1.2 there are two language files for each language, and they are merged at startup in a single Inifile in memory.
+There are two language files for each language, and they are merged at startup in a single Inifile in memory.
 To locate, or create or improve a translation, see [[Translating#The_code_for_your_language|this page]].

@@ Line 27: / Line 27: @@
 For each control of [[Gestinux_util]], the translation is searched in the language file :
-The section is the Form name.
+The section is the Form name (the form class name in version under development).
 The parameter name is the component name, followed by a dot and the property name to translate.
 The parameter value is the translation

@@ Line 50: / Line 50: @@
 E.g :
-  Grid.Employees.Name.Title=Name
+  GridEmployees.Name.Title=Name
-  Grid.Employees.Address.Title=Address
+  GridEmployees.Address.Title=Address
-  Grid.Employees.City.Title=City
+  GridEmployees.City.Title=City
 === Messages ===

@@ Line 90: / Line 90: @@
   TranslateMessage ( Section, Key, [parameter_1, ... parameter_n] );
 == How to make a translation ==
 Use the [[Translating|translation utility]], available for Linux and for Windows, which can read a reference language file, and fill another language file, detecting missing translations.

@@ Line 1: / Line 1: @@
 == Why ==
-The common method using resource strings is a little tedious to implement.
+The common I18N method using resource strings requires a development environment and programming skills to make or improve translations.
-That's why I have used another system, with some success on a large application.
+For Gestinux, we have used another system.
-Translation are read by the software from mere inifiles and applied when forms are loaded. This is quick enough.
+Translation are read by the software from mere text files (inifile like) and read when forms are loaded. This is quick enough.
 This way, it is possible to define or modify translations directly when running the application, without developing tools and skills. There is no need to recompile anything to add a new language, or to modify an existing language.
 == How it works ? ==

@@ Line 79: / Line 79: @@
 === Other strings ===
-Other parameters can be present in the ini file, for special usages.
+Other parameters can be present in the language file, for special usages.
 Their translations can be queried at any time by :
-TranslateText( Section, Key, Default );
+ TranslateText( Section, Key, Default );
 == How to make a translation ==
 Use the [[Translating|translation utility]], available for Linux and for Windows, which can read a reference language file, and fill another language file, detecting missing translations.

@@ Line 52: / Line 52: @@
 === Messages ===
 Messages are identified by keywords not used for control's translations. They are stored in the form section, along with other control's translations.
-Parameters are allowed. Example :
+Parameters are allowed.
-UsernameConnectError=%1:s in not a valid username, retry.
+Example :
-MessageDlg and ShowMessage procedures must not be used, since they don't use the same translation system.
+ UsernameConnectError=%0:s in not a valid username, retry.
 To display a translated message, use only one of these functions member of TGForm :
-*ErrorMessage ( 'UsernameConnectError', [EditUsername.Text] );
+ AbortMessage ( 'UsernameConnectError', [EditUsername.Text] );
-*ConfirmationMessage ( 'UsernameConnectError', [EditUsername.Text] );
+ ErrorMessage ( 'UsernameConnectError', [EditUsername.Text] );
-*InformationMessage ( 'UsernameConnectError', [EditUsername.Text] );
+ ConfirmationMessage ( 'UsernameConnectError', [EditUsername.Text] );
-Or in  some special cases
+In some special cases, a more general procedure can be used :
-*DisplayMessage
+ DisplayMessage ( ParentForm, Section, MessageId, [parameter-1, ..., parameter_n], Severity, WikiPage );
 === Other strings ===