Karma/i18n - Revision history

Km0r3: /* JavaScript Strings */

2010-06-14T00:24:17Z

JavaScript Strings

← Older revision		Revision as of 20:24, 13 June 2010
Line 25:		Line 25:
	* the arguments to the different calls should be string literals. Otherwise xgettext will not be able to extract the messages to be translated.		* the arguments to the different calls should be string literals. Otherwise xgettext will not be able to extract the messages to be translated.

	More ~~information~~: http://forum.jquery.com/topic/locale-information-should-be-separated-from-plugins		More resources:
			http://forum.jquery.com/topic/locale-information-should-be-separated-from-plugins
			http://wiki.jqueryui.com/i18n

	====HTML Strings====		====HTML Strings====

Km0r3: /* JavaScript Strings */

2010-06-14T00:13:14Z

JavaScript Strings

← Older revision		Revision as of 20:13, 13 June 2010
Line 25:		Line 25:
	* the arguments to the different calls should be string literals. Otherwise xgettext will not be able to extract the messages to be translated.		* the arguments to the different calls should be string literals. Otherwise xgettext will not be able to extract the messages to be translated.

	~~The lesson examples~~/~~6_Maths_matchingAnglesAndShapes~~/ ~~contains an example~~.		More information: http://forum.jquery.com/topic/locale-information-should-be-separated-from-plugins

	====HTML Strings====		====HTML Strings====

Km0r3: /* HTML Strings */

2010-06-05T04:49:26Z

HTML Strings

← Older revision		Revision as of 00:49, 5 June 2010
Line 34:		Line 34:
	* Dynamically change out strings per locale on page load (HIGH PRIORITY)		* Dynamically change out strings per locale on page load (HIGH PRIORITY)
	* A well-defined workflow		* A well-defined workflow
	* integrate the JavaScript i18n within the workflow.		** integrate the JavaScript i18n within the workflow.
	* Documentation.		* Documentation.

	I'm still actively working on it. Questions, comments, suggestions > km0r3 AT sugarlabs DOT org .		I'm still actively working on it. Questions, comments, suggestions > km0r3 AT sugarlabs DOT org .

Km0r3: /* HTML Strings */

2010-06-05T04:48:42Z

HTML Strings

← Older revision		Revision as of 00:48, 5 June 2010
Line 28:		Line 28:

	====HTML Strings====		====HTML Strings====
	We will try to use the [http://en.wikipedia.org/wiki/Internationalization_Tag_Set Internationalization Tag Set] for handling strings inline with html. The [http://okapi.sourceforge.net/ Okapi] tool may be able to parse out strings marked with ITS.

	~~There is first attempt at internationalizing html without using ITS~~. ~~It will be in git under karma~~/~~i18n.~~		The Python library [http://www.hforge.org/itools itools] automates the job of parsing the HTML and creating the PO files. There are already concrete experiments, which you can find [http://git.olenepal.org/~km0r3/karma/km0r3-karma/commits/experimental here].
	* You annotate the ~~tags~~ of ~~elements that need translation with a class attribute~~: ~~class="translate".~~
	* i18n/~~html2po~~.~~py is the equivalent of xgettext for html~~.
	* i18n/~~translate~~-~~html.py translates an html page~~.

	~~Have a look at karma/~~i18n~~/example for an example~~.		Things which still need to be done:
			* Dynamically change out strings per locale on page load (HIGH PRIORITY)
			* A well-defined workflow
			* integrate the JavaScript i18n within the workflow.
			* Documentation.

	~~The following is no longer true (translate-html~~.~~py generates a static translated html page)~~, ~~but can be implemented if needed:~~		I'm still actively working on it. Questions, comments, suggestions > km0r3 AT sugarlabs DOT org .
	* For the immediate future we will dynamically change out strings per locale on page load

Petergijsels: /* General Strategy */

2010-03-07T16:16:14Z

General Strategy

@@ Line 15: / Line 15: @@
 === General Strategy ===
-* Use a modified version of gettext, where the key for getting translations, we will use an arbitrary message identifier. This will remove the need for managing translation contexts.
+====JavaScript Strings====
-* We will try to use the [http://en.wikipedia.org/wiki/Internationalization_Tag_Set Internationalization Tag Set] for handling strings inline with html. The [http://okapi.sourceforge.net/ Okapi] tool may be able to parse out strings marked with ITS.
+We try to follow a subset of the [http://www.gnu.org/software/gettext/manual/gettext.html#gettext gettext api] quite closely. After including jquery.i18n.js you can use the following gettext functions in your javascript scripts:
-* We will use this lesson for prototyping examples/6_Maths_matchingAnglesAndShapes/
+* $.i18n.gettext('text to be translated') or $. _('text to be translated'): to translate a simple string
 * For the immediate future we will dynamically change out strings per locale on page load

BryanWB at 14:32, 24 February 2010

2010-02-24T14:32:50Z

← Older revision		Revision as of 10:32, 24 February 2010
Line 6:		Line 6:
	Examples		Examples
	$("#someDiv").text(gettext("Hello World"));		$("#someDiv").text(gettext("Hello World"));
			<nowiki>
	<div>Hello <strong>W</strong>orld</div>		<div>Hello <strong>W</strong>orld</div>
			</nowiki>

	* All strings stored in one file per locale, messages.json		* All strings stored in one file per locale, messages.json

BryanWB at 14:32, 24 February 2010

2010-02-24T14:32:09Z

← Older revision		Revision as of 10:32, 24 February 2010
Line 5:		Line 5:
	* Handle strings inside code and html markup		* Handle strings inside code and html markup
	Examples		Examples

	$("#someDiv").text(gettext("Hello World"));		$("#someDiv").text(gettext("Hello World"));

	<div>Hello <strong>W</strong>orld</div>		<div>Hello <strong>W</strong>orld</div>

BryanWB at 14:31, 24 February 2010

2010-02-24T14:31:46Z

← Older revision		Revision as of 10:31, 24 February 2010
Line 4:		Line 4:
	* Integrate with pootle		* Integrate with pootle
	* Handle strings inside code and html markup		* Handle strings inside code and html markup
			Examples

	~~=== Technical Requirements ===~~		$("#someDiv").text(gettext("Hello World"));
	* All strings stored in one file, messages.json
	*		<div>Hello <strong>W</strong>orld</div>

			* All strings stored in one file per locale, messages.json
			* All message identifiers must be unique within an a lesson
			* Accommodating numeric, currency, and date formatting is not an immediate requirement

	=== General Strategy ===		=== General Strategy ===
			* Use a modified version of gettext, where the key for getting translations, we will use an arbitrary message identifier. This will remove the need for managing translation contexts.
	~~Lesson~~ to use for prototyping		* We will try to use the [http://en.wikipedia.org/wiki/Internationalization_Tag_Set Internationalization Tag Set] for handling strings inline with html. The [http://okapi.sourceforge.net/ Okapi] tool may be able to parse out strings marked with ITS.
	examples/6_Maths_matchingAnglesAndShapes/		* We will use this lesson for prototyping examples/6_Maths_matchingAnglesAndShapes/
			* For the immediate future we will dynamically change out strings per locale on page load

BryanWB at 14:16, 24 February 2010

2010-02-24T14:16:57Z

← Older revision		Revision as of 10:16, 24 February 2010
Line 1:		Line 1:
	Rough plan for implementing i18n for Karma		Rough plan for implementing i18n for Karma

	== Requirements ==		=== Requirements ===
			* Integrate with pootle
			* Handle strings inside code and html markup

			=== Technical Requirements ===
	* All strings stored in one file, messages.json		* All strings stored in one file, messages.json
	*		*

			=== General Strategy ===

	Lesson to use for prototyping		Lesson to use for prototyping
	examples/6_Maths_matchingAnglesAndShapes/		examples/6_Maths_matchingAnglesAndShapes/

BryanWB at 14:07, 24 February 2010

2010-02-24T14:07:08Z

← Older revision		Revision as of 10:07, 24 February 2010
Line 1:		Line 1:
	~~Stub~~ for i18n ~~in the~~ Karma ~~framework~~		Rough plan for implementing i18n for Karma

	~~Trac bug {{Trac\|1039\|Pls add karma~~.~~pot~~ to ~~pootle}} has been filed.~~		== Requirements ==
			* All strings stored in one file, messages.json
			*


			Lesson to use for prototyping
			examples/6_Maths_matchingAnglesAndShapes/