AppSuite:I18n - Revision history

Khgras: Replaced content with "The content on this page has moved to https://documentation.open-xchange.com/latest/ui/how-to/i18n.html Note: Open-Xchange is in the process of migrating all its technica..."

2017-05-22T09:52:37Z

Replaced content with "The content on this page has moved to https://documentation.open-xchange.com/latest/ui/how-to/i18n.html Note: Open-Xchange is in the process of migrating all its technica..."

Show changes

Frank.paczynski at 12:39, 10 February 2016

2016-02-10T12:39:22Z

← Older revision		Revision as of 12:39, 10 February 2016
Line 1:		Line 1:
			<!-- !!! -->
			<!-- PLEASE APPLY CHANGES ONLY TO THE NEW TECHNICAL DOCUMENTATION: wd/frontend/web/documentation -->
			<!-- !!! -->

	{{Stability-experimental}}		{{Stability-experimental}}

J.ohny.b: /* Custom Translations */

2015-08-10T14:31:18Z

Custom Translations

← Older revision		Revision as of 14:31, 10 August 2015
Line 156:		Line 156:

	==Custom Translations==		==Custom Translations==
	App Suite has support for custom translations. ''gettext'' provides a function ''addTranslation(dictionary, key, value)'' that allows adding custom translation to a global dictionary ("*") as well as replacing translations in existing dictionaries. In order to use this, you have to create a plugin for the "core" namespace.		App Suite has support for custom translations. ''gettext'' provides a function ''addTranslation(dictionary, key, value)'' that allows adding custom translation to a global dictionary ("*") as well as replacing translations in existing dictionaries. In order to use this, you have to create a plugin for the "core" namespace. With release 7.8.0, there is a special namespace for exactly this use-case. It is now possible to define plugins to be loaded for the "i18n" namespace, which is loaded right before gettext is being enabled and after that the core plugins will be loaded.

	<pre class="language-javascript">		<pre class="language-javascript">

Viktor.Pracht: /* Custom Translations */ Use best practices for require calls

2015-06-22T12:56:56Z

Custom Translations: Use best practices for require calls

← Older revision		Revision as of 12:56, 22 June 2015
Line 159:		Line 159:

	<pre class="language-javascript">		<pre class="language-javascript">
	~~var gt =~~ require('io.ox/core/gettext');		require(['io.ox/core/gettext'], function (gt) {
	gt.addTranslation('*', 'Existing translation', 'My custom translation');		gt.addTranslation('*', 'Existing translation', 'My custom translation');
			});
	</pre>		</pre>

J.ohny.b: /* Translation */

2014-06-12T07:46:30Z

Translation

← Older revision		Revision as of 07:46, 12 June 2014
Line 29:		Line 29:
	$ build-appsuite ox.pot		$ build-appsuite ox.pot

	to create the file in the apps root directory ~~and~~ starting from 7.6.0:		to create the file in the apps root directory.

			Working with a version starting from 7.6.0, the command:

	$ grunt create_pot		$ grunt create_pot

J.ohny.b: /* Translation */

2014-06-11T15:39:30Z

Translation

← Older revision		Revision as of 15:39, 11 June 2014
Line 25:		Line 25:
	</pre>		</pre>

	~~After building~~ the ~~module,~~ the ~~file~~ ox.pot in the ~~project's~~ root directory will contain an entry for every call to one of <tt>gettext</tt> functions:		A file named ox.pot is created by the <tt>ox.pot</tt> (< 7.6.0) or <tt>create_pot</tt> (>= 7.6.0) tasks of the build system. So for versions < 7.6.0 you will need to run:

			$ build-appsuite ox.pot

			to create the file in the apps root directory and starting from 7.6.0:

			$ grunt create_pot

			will generate this file within the <tt>i18n/</tt> directory. It will contain an entry for every call to one of <tt>gettext</tt> functions:

	<pre class="language-gettext">		<pre class="language-gettext">
Line 33:		Line 41:
	</pre>		</pre>

	~~After~~ translation, ~~the~~ PO files in the directory <tt>i18n</tt> shoud contain the translated entry:		This file can be sent to the translators and during the translation process, one PO file for each language will be created. The PO files in the directory <tt>i18n</tt> shoud contain the translated entry:

	<pre class="language-gettext">		<pre class="language-gettext">

Viktor.Pracht: /* Custom Translations */

2014-03-03T11:47:26Z

Custom Translations

← Older revision		Revision as of 11:47, 3 March 2014
Line 194:		Line 194:
	returns translations for current language.		returns translations for current language.
	*/		*/
	gt('Tree');		if (false) {
	gt('House');		gt('Tree');
	gt('Dog');		gt('House');
			gt('Dog');
			}

	// get internal dictionary (for current language of course)		// get internal dictionary (for current language of course)

Tierlieb at 11:39, 27 September 2013

2013-09-27T11:39:33Z

← Older revision		Revision as of 11:39, 27 September 2013
Line 205:		Line 205:
	});		});
	</pre>		</pre>


			[[Category:AppSuite]]
			[[Category:UI]]
			[[Category:Developer]]

Mattes: /* Custom Translations */

2013-05-29T07:49:27Z

Custom Translations

← Older revision		Revision as of 07:49, 29 May 2013
Line 150:		Line 150:
	<pre class="language-javascript">		<pre class="language-javascript">
	var gt = require('io.ox/core/gettext');		var gt = require('io.ox/core/gettext');
	gt.addTranslation('*', '~~Address Book~~', 'My ~~Contacts App~~');		gt.addTranslation('*', 'Existing translation', 'My custom translation');
	</pre>		</pre>

Line 159:		Line 159:
	var gt = require('io.ox/core/gettext');		var gt = require('io.ox/core/gettext');

	// replace translation in dictionary 'io.ox/core'		// replace translation in dictionary 'io.ox/core'. Apps use context "app".
	gt.addTranslation('io.ox/core', '~~Address~~ Book', 'My Contacts~~');~~		gt.addTranslation('io.ox/core', 'app\x00Address Book', 'My Contacts');

	~~// replace translation in global dictionary~~
	~~gt.addTranslation('*', 'Files', 'My File Box~~');

	// replace translation - counterpart to ngettext		// replace translation - counterpart to ngettext
	gt.addTranslation('io.ox/mail', 'Copy\x01Copies', { 0: 'Kopie', 1: 'Kopien' });		gt.addTranslation('io.ox/mail', 'Copy\x01Copies', { 0: 'Kopie', 1: 'Kopien' });

	~~// replace translation - counterpart to pgettext~~
	~~gt.addTranslation('io.ox/mail', 'test\x00Files', 'Files');~~

	// replace translation - counterpart to npgettext		// replace translation - counterpart to npgettext

Mattes: /* Custom Translations */

2013-05-13T19:06:10Z

Custom Translations

@@ Line 191: / Line 191: @@
 <pre class="language-javascript">
-/* Just list all custom translations in your plugin by standalone gt() calls.
+define('plugins/example/register', ['io.ox/core/gettext', 'gettext!custom'], function (gettext, gt) {
-// get internal dictionary (for current language of course)
+    'use strict';
 var dictionary = gt.getDictionary();
-// add all translations to global dictionary. Done!
+    /* Just list all custom translations in your plugin by standalone gt() calls.
-gettext.addTranslation('*', dictionary);
+       The build system recognizes these strings and collects them in a POT file,
 </pre>