Documentation/Maemo 5 Developer Guide/Application Development/Maemo Localization - Revision history

amigadave: add example links

amigadave — Tue, 07 Sep 2010 10:30:53 GMT

add example links

← Older revision		Revision as of 10:30, 7 September 2010
Line 1:		Line 1:
-	This section describes how to localize ~~maemo~~ applications. Localization is needed to provide native translations of the software. The section contains information on how to localize an application, how to ease extraction of message strings, how to make the translations, and how to test the localization.	+	This section describes how to localize Maemo applications. Localization is needed to provide native translations of the software. The section contains information on how to localize an application, how to ease extraction of message strings, how to make the translations, and how to test the localization.

-	Changes are presented with code examples to help the localization process. MaemoPad is used as an example here.	+	Changes are presented with code examples to help the localization process. [[Documentation/Maemo 5 Developer Guide/Porting Software/Porting MaemoPad\|MaemoPad]] is used as an example here.

	== Localization ==		== Localization ==
Line 19:		Line 19:
	To localize an application, l10n needs to be set up before <code>gtk_init()</code> by including the following headers:		To localize an application, l10n needs to be set up before <code>gtk_init()</code> by including the following headers:

-	maemopad/src/main.c	+	[https://vcs.maemo.org/svn/maemoexamples/tags/maemo_5.0/maemopad/src/main.c maemopad/src/main.c]

	<source lang="c">		<source lang="c">
Line 28:		Line 28:
	To initialize the locale functions, the following lines need to be added:		To initialize the locale functions, the following lines need to be added:

-	maemopad/src/main.c	+	[https://vcs.maemo.org/svn/maemoexamples/tags/maemo_5.0/maemopad/src/main.c maemopad/src/main.c]

	<source lang="c">		<source lang="c">
Line 39:		Line 39:
	The most important of these are <code>GETTEXT_PACKAGE</code> and <code>localedir</code>, which come from <code>configure.ac</code>:		The most important of these are <code>GETTEXT_PACKAGE</code> and <code>localedir</code>, which come from <code>configure.ac</code>:

-	maemopad/configure.ac	+	[https://vcs.maemo.org/svn/maemoexamples/tags/maemo_5.0/maemopad/src/configure.ac maemopad/configure.ac]

	<source lang="autoconf">		<source lang="autoconf">
Line 71:		Line 71:
	Thus, the i18n version of the example would be:		Thus, the i18n version of the example would be:

-	maemopad/src/main.c	+	[https://vcs.maemo.org/svn/maemoexamples/tags/maemo_5.0/maemopad/src/main.c maemopad/src/main.c]

	<source lang="c">		<source lang="c">

amigadave: use and


amigadave — Tue, 20 Jul 2010 11:07:30 GMT
use <source> and <code>
Show changes



82.245.13.39: /* Testing */
82.245.13.39 — Mon, 15 Feb 2010 14:02:18 GMT
Testing

		
		
		
		
		
		
		← Older revision
		Revision as of 14:02, 15 February 2010
		
		Line 116:
Line 116:
 == Testing ==  == Testing ==
  
- Inside scratchbox, the translated application should be tested by setting LC_ALL environment variable to contain the newly created locale (in this example case for Finnish translation, "fi_FI"): + Inside scratchbox, the translated application should be tested by setting LANGUAGE environment variable to contain the newly created locale (in this example case for Finnish translation, "fi_FI"):
  
  




fredoll: /* Localizing Application */
fredoll — Mon, 15 Feb 2010 12:34:02 GMT
Localizing Application

		
		
		
		
		
		
		← Older revision
		Revision as of 12:34, 15 February 2010
		
		Line 51:
Line 51:
   AM_GLIB_GNU_GETTEXT    AM_GLIB_GNU_GETTEXT
   # Application locale install directory, /usr/share/locale by default    # Application locale install directory, /usr/share/locale by default
-   localedir=`$PKG_CONFIG osso-af-settings -variable=localedir` +   localedir=`$PKG_CONFIG osso-af-settings --variable=localedir`
  
 Of these, only GETTEXT_PACKAGE needs special attention, as it is the l10n domain that is to be used, and ALL_LINGUAS lists the available translations.  Of these, only GETTEXT_PACKAGE needs special attention, as it is the l10n domain that is to be used, and ALL_LINGUAS lists the available translations.




amigadave: categorise
amigadave — Fri, 12 Feb 2010 12:00:20 GMT
categorise

		
		
		
		
		
		
		← Older revision
		Revision as of 12:00, 12 February 2010
		
		Line 127:
Line 127:
  
 The example above assumes that the installation package installs the executable into /usr/bin. This script needs then to be configured to be run in the application's .desktop file, instead of the actual executable.  The example above assumes that the installation package installs the executable into /usr/bin. This script needs then to be configured to be run in the application's .desktop file, instead of the actual executable.
  + 
  + [[Category:Development]]
  + [[Category:Documentation]]
  + [[Category:Fremantle]]




esa: Created Maemo Localization page
esa — Thu, 01 Oct 2009 07:22:48 GMT
Created Maemo Localization page
New page
= Maemo Localization =



== Overview ==



This section describes how to localize maemo applications. Localization is needed to provide native translations of the software. The section contains information on how to localize an application, how to ease extraction of message strings, how to make the translations, and how to test the localization.



Changes are presented with code examples to help the localization process. MaemoPad is used as an example here.



== Localization ==



Localization means translating the application to different languages. Maemo localization is based on the standard gettext package, and all the necessary tools are included in Scratchbox. For applications, localization requires a couple of files in the po/ directory. The following files will be used for localization:



 Makefile.am

 en_GB.po

 fi_FI.po

 POTFILES.in





''POTFILES.in''  contains the list of source code files that will be localized. File ''en_GB.po''  includes translated text for target en_GB and file ''fi_FI.po''  for target fi_FI.



== Localizing Application ==



To localize an application, l10n needs to be set up before <code>gtk_init()</code> by including the following headers:



maemopad/src/main.c 



 #include <locale.h>

 #include <glib/gi18n.h>





To initialize the locale functions, the following lines need to be added:



maemopad/src/main.c 



 setlocale(LC_ALL, "");

 bindtextdomain(GETTEXT_PACKAGE, LOCALEDIR);

 bind_textdomain_codeset(GETTEXT_PACKAGE, "UTF-8");

 textdomain(GETTEXT_PACKAGE);





The most important of these are ''GETTEXT_PACKAGE''  and ''localedir'' , which come from configure.ac:



maemopad/configure.ac 



 AC_PROG_INTLTOOL([0.23])

 #PACKAGE=maemopad by default, defined by AM_INIT_AUTOMAKE

 GETTEXT_PACKAGE=$PACKAGE

 AC_SUBST(GETTEXT_PACKAGE)

 AC_DEFINE_UNQUOTED([GETTEXT_PACKAGE], "${GETTEXT_PACKAGE}", [gettext pakname])

 ALL_LINGUAS="en_GB fi_FI"

 AM_GLIB_GNU_GETTEXT

 # Application locale install directory, /usr/share/locale by default

 localedir=`$PKG_CONFIG osso-af-settings -variable=localedir`



Of these, only GETTEXT_PACKAGE needs special attention, as it is the l10n domain that is to be used, and ALL_LINGUAS lists the available translations.



=== Easing Extraction of Strings ===



In the source code, there are multiple strings that eventually get shown in the user interface. For example:



 maemopad_window_show_error ("maemopad_open_failed", self);





In order to make the strings localizable, they need to be wrapped in <code>gettext("String")</code> calls. In practice, writing <code>gettext()</code> for every string is tedious. The common practice is to set the following #define which is already done in included ''gi18n.h'':



 #define _(String) gettext (String)





Thus, the i18n version of the example would be:



maemopad/src/main.c



 maemopad_window_show_error (_("maemopad_open_failed"), self);





=== Creating Translation Files ===



Creating *.po files is quite straightforward. Maemopad has two localization files, ''en_GB.po'' and ''fi_FI.po''. Creating the Finnish translation is explained next. Localization .po files are filled with simple structures, defining the localization id and the actual text string, e.g.



 #: src/maemopad-window.c:573 src/maemopad-window.c:580

 msgid "maemopad_open_failed"

 msgstr "Open failed!"



"msgid" defines the original string (key) used in code, and "msgstr" defines the translated string for localization.



First, a template file is created with all strings from sources for translation. GNU xgettext command is used to extract the strings from sources:

 

 [sbox-FREMANTLE_X86: ~/maemopad] &gt; xgettext -f po/POTFILES.in -C -a -o po/template.po



Option "-f po/POTFILES.in" uses POTFILES.in to get the files to be localized, "-C" is for C-code type of strings, "-a" is for ensuring that all the strings are received from sources, and "-o template.po" defines the output filename.



This may output some warnings. Usually they are not serious, but it is better to check them anyway.



If the translation in question is into Finnish, the edited ''po/template.po''  needs to be copied to ''po/fi_FI.po'' , and ''fi_FI.po''  needs to be added to ALL_LINGUAS in ''configure.ac''.



Now ''po/fi_FI.po''  will include lines such as the following:



 #: src/maemopad-window.c:253

 msgid "maemopad_save_changes_made"

 msgstr "Save changes?"



All msgstrings should be translated into the desired language:



 #: src/maemopad-window.c:253

 msgid "maemopad_save_changes_made"

 msgstr "Tallenna muutokset?"



Autotools should now automatically convert the .po file to .mo file during the build process, and install it to the correct location.



To do it manually:

 

 [sbox-FREMANTLE_X86: ~/maemopad] > msgfmt po/fi_FI.po -o debian/maemopad/usr/share/locale/fi_FI/LC_MESSAGES/maemopad.mo



Where "debian/maemopad/usr/share/locale/fi_FI/LC_MESSAGES/" is the directory where the software should be installed to.



== Testing ==



Inside scratchbox, the translated application should be tested by setting LC_ALL environment variable to contain the newly created locale (in this example case for Finnish translation, "fi_FI"):





 [sbox-FREMANTLE_X86: ~] > LANGUAGE="fi_FI" run-standalone.sh maemopad



On the target device, a wrapper script is needed to accomplish this, if the device does not have a locale for the locale identifier used. The script can simply consist of:



 #!/bin/sh

 LANGUAGE="fi_FI" /usr/bin/maemopad



The example above assumes that the installation package installs the executable into /usr/bin. This script needs then to be configured to be run in the application's .desktop file, instead of the actual executable.

← Older revision		Revision as of 14:02, 15 February 2010
Line 116:		Line 116:
	== Testing ==		== Testing ==

-	Inside scratchbox, the translated application should be tested by setting ~~LC_ALL~~ environment variable to contain the newly created locale (in this example case for Finnish translation, "fi_FI"):	+	Inside scratchbox, the translated application should be tested by setting LANGUAGE environment variable to contain the newly created locale (in this example case for Finnish translation, "fi_FI"):

← Older revision		Revision as of 12:34, 15 February 2010
Line 51:		Line 51:
	AM_GLIB_GNU_GETTEXT		AM_GLIB_GNU_GETTEXT
	# Application locale install directory, /usr/share/locale by default		# Application locale install directory, /usr/share/locale by default
-	localedir=`$PKG_CONFIG osso-af-settings -variable=localedir`	+	localedir=`$PKG_CONFIG osso-af-settings --variable=localedir`

	Of these, only GETTEXT_PACKAGE needs special attention, as it is the l10n domain that is to be used, and ALL_LINGUAS lists the available translations.		Of these, only GETTEXT_PACKAGE needs special attention, as it is the l10n domain that is to be used, and ALL_LINGUAS lists the available translations.

← Older revision		Revision as of 12:00, 12 February 2010
Line 127:		Line 127:

	The example above assumes that the installation package installs the executable into /usr/bin. This script needs then to be configured to be run in the application's .desktop file, instead of the actual executable.		The example above assumes that the installation package installs the executable into /usr/bin. This script needs then to be configured to be run in the application's .desktop file, instead of the actual executable.
		+
		+	[[Category:Development]]
		+	[[Category:Documentation]]
		+	[[Category:Fremantle]]