A Simple Guide to Use Internationalization Library - Revision history

Halw at 16:18, 27 February 2011

2011-02-27T16:18:10Z

Manus at 16:54, 24 February 2011

2011-02-24T16:54:11Z

Ted: New page: Category:Internationalization == Overview == This page focuses on very simple/general steps to bring i18n library up in your project. == Steps == # Choose and create a directory to p...

2010-11-05T04:29:05Z

New page: Category:Internationalization == Overview == This page focuses on very simple/general steps to bring i18n library up in your project. == Steps == # Choose and create a directory to p...

New page

[[Category:Internationalization]]

== Overview ==
This page focuses on very simple/general steps to bring i18n library up in your project.

== Steps ==
# Choose and create a directory to put exported translated files (*.mo).
# In your project, initialize a <e>{LOCALE_MANAGER}</e> using the dir created in step 1.
# Write normal code that uses <e>{I18N_LOCALE}.translation</e> or <e>{I18N_LOCALE}.plural_translation</e> to get translated texts. <e>{I18N_LOCALE}</e> instances can be queried from <e>{LOCALE_MANAGER}</e>.
# Run [[po_generation_tool]] to extract template file (.pot) to be translated.
# Copy the .pot file to .po files with the name of the language you need. For example, es_ES.po for Spanish, ko_KR.po for Korean.
# Translate .po files using external tools like poEdit for Windows and KBabel or gtranslator for KDE and Gnome.
# Export .mo files using the tools above. And copy them into the directory created in step 1.
# Run the executable, you get translated strings at run-time.

← Older revision		Revision as of 16:18, 27 February 2011
Line 13:		Line 13:
	# Export .mo files using the tools above. And copy them into the directory created in step 1.		# Export .mo files using the tools above. And copy them into the directory created in step 1.
	# Run the executable, you get translated strings at run-time.		# Run the executable, you get translated strings at run-time.
		+
		+
		+	==Process Diagram==
		+
		+	[[Image:I18n process diagram.png]]

@@ Line 6: / Line 6: @@
 == Steps ==
 # Choose and create a directory to put exported translated files (*.mo).
-# In your project, initialize a <e>{LOCALE_MANAGER}</e> using the dir created in step 1.
+# In your project, initialize a <e>{I18N_LOCALE_MANAGER}</e> using the dir created in step 1.
-# Write normal code that uses <e>{I18N_LOCALE}.translation</e> or <e>{I18N_LOCALE}.plural_translation</e> to get translated texts. <e>{I18N_LOCALE}</e> instances can be queried from <e>{LOCALE_MANAGER}</e>.
+# Write normal code that uses <e>{I18N_LOCALE}.translation</e> or <e>{I18N_LOCALE}.plural_translation</e> to get translated texts. <e>{I18N_LOCALE}</e> instances can be queried from <e>{I18N_LOCALE_MANAGER}</e>.
 # Run [[po_generation_tool]] to extract template file (.pot) to be translated.
 # Copy the .pot file to .po files with the name of the language you need. For example, es_ES.po for Spanish, ko_KR.po for Korean.