Development/Tutorials/Localization/i18n - Revision history

AnneW at 12:47, 13 July 2012

2012-07-13T12:47:06Z

Peter: Adding qml information

2012-02-13T08:19:02Z

Adding qml information

Icwiener: Fix syntax highlighting.

2011-06-27T16:42:18Z

Fix syntax highlighting.

Show changes

Aspotashev at 09:47, 14 May 2011

2011-05-14T09:47:42Z

Djarvie: /* Adding Context with i18nc() */ Reference to semantic markup

2010-07-29T13:04:04Z

‎Adding Context with i18nc(): Reference to semantic markup

Odysseus: /* Calendaring */

2009-11-06T16:34:52Z

‎Calendaring

Tampakrap at 16:01, 3 May 2009

2009-05-03T16:01:16Z

Ilic: Change of context property name in Designer in Qt 4.5.

2009-04-21T18:16:35Z

Change of context property name in Designer in Qt 4.5.

DeKay: Corrected spelling mistakes: Refering -> Referring

2009-03-14T21:54:24Z

Corrected spelling mistakes: Refering -> Referring

Lazarus: Add border to table; minor grammar fix; abbreviation expansion.

2008-12-07T09:58:07Z

Add border to table; minor grammar fix; abbreviation expansion.

← Older revision		Revision as of 12:47, 13 July 2012
Line 1:		Line 1:
−	~~{{Template:I18n/Language Navigation Bar\|Development/Tutorials/Localization/i18n}}~~

	{{TutorialBrowser\|		{{TutorialBrowser\|

← Older revision		Revision as of 08:19, 13 February 2012
Line 253:		Line 253:

	{{improve\|provide more info on the different calendar systems}}		{{improve\|provide more info on the different calendar systems}}
		+
		+	== QML ==
		+
		+	To make QML code translatable, <tt>KDeclarative </tt> provides the same <tt>i18n()</tt> calls described above. To enable parsing at runtime, you need to install a <tt>KDeclarative</tt> object in the <tt>QDeclarativeEngine</tt>:
		+	<syntaxhighlight lang="cpp-qt">
		+	KDeclarative kdeclarative;
		+	//view refers to the QDeclarativeView
		+	kdeclarative.setDeclarativeEngine(view.engine());
		+	kdeclarative.initialize();
		+	//binds things like kconfig and icons
		+	kdeclarative.setupBindings();
		+	</syntaxhighlight>
		+
		+	The application also needs to link to <tt>libkdeclarative</tt>.

	== Avoiding Common Traps ==		== Avoiding Common Traps ==

@@ Line 148: / Line 148: @@
 | Yes || Availability of a thing|| <tt>i18nc("Availability", "Yes")</tt>
 |}
 === Plurals ===

← Older revision		Revision as of 13:04, 29 July 2010
Line 82:		Line 82:

	Contexts can also be added when building forms in Qt Designer. Each widget label, including tooltips and whatsthis texts, has a "disambiguation" attribute (named "comment" prior to Qt 4.5), which will serve the same purpose as first argument to <tt>i18nc()</tt> call.		Contexts can also be added when building forms in Qt Designer. Each widget label, including tooltips and whatsthis texts, has a "disambiguation" attribute (named "comment" prior to Qt 4.5), which will serve the same purpose as first argument to <tt>i18nc()</tt> call.
		+
		+	KDE provides a standard set of strings to identify the semantic context of translatable strings. These are defined in the [[Development/Tutorials/Localization/i18n_Semantics\|KUIT Semantic Markup scheme]].

	=== Standard Context For Common Phrases ===		=== Standard Context For Common Phrases ===

@@ Line 206: / Line 206: @@
 Developing applications dealing with dates and time, such as calendars, is a very complex area. Not only may the displayed string containing a date or time look different based on locale, but one also has to take care of other aspects such as:
 * which day in the week is the first one (cf int weekStartDay())
 * how many months in a year there are
 * "era"-based calendars
 * whether to use 24-hour time format (cf bool use12Clock())
 KLocale provides, among others, these methods:

@@ Line 151: / Line 151: @@
 Plurals are handled differently from language to language. Many languages have different plurals for 2, 10, 20, 100, etc. When the string you want translated refers to more than one item, you must use the third form of <tt>i18n</tt>,  the <tt>i18np()</tt>. It takes the singular and plural English forms as its first two arguments, followed by any substitution arguments as usual, but at least one of which should be integer-valued. For example:
-<code cppqt>msgStr = i18np("1 image in album %2", "%1 images in album %2", numImages, albumName);</code>
+<code cppqt>msgStr = i18np("1 image in album %2", "%1 images in album %2", numImages, albumName);
 <tt>i18np()</tt> gets expanded to as many cases as required by the user's language. In English, this is just two forms while in other languages it may be more, depending on the value of the first integer-valued argument.

@@ Line 81: / Line 81: @@
 {{note|There is also a ki18nc("context","text") method for providing context to strings which are constructed before the KInstance. It returns a KLocalizedString, so use the toString() method afterwards to convert it into a QString.}}
-Contexts can also be added when building forms in Qt Designer. Each widget label, including tooltips and whatsthis texts, has a "comment" attribute, which will serve the same purpose as first argument to <tt>i18nc()</tt> call.
+Contexts can also be added when building forms in Qt Designer. Each widget label, including tooltips and whatsthis texts, has a "disambiguation" attribute (named "comment" prior to Qt 4.5), which will serve the same purpose as first argument to <tt>i18nc()</tt> call.
 === Standard Context For Common Phrases ===

@@ Line 92: / Line 92: @@
 ! Phrase !! Context !! i18nc Call !! Example
 |-
-| Busy || Refering to a person || <tt>i18nc("A person is busy", "Busy")</tt>
+| Busy || Referring to a person || <tt>i18nc("A person is busy", "Busy")</tt>
 |-
-| Busy || Refering to a thing || <tt>i18nc("A thing is busy", "Busy")</tt>
+| Busy || Referring to a thing || <tt>i18nc("A thing is busy", "Busy")</tt>
 |-
 | Color || Color mode, as opposed to Grayscale || <tt>i18nc("Not Grayscale", "Color")</tt>
 |-
-| Creator || Refering to a person || <tt>i18nc("A person who creates", "Creator")</tt>
+| Creator || Referring to a person || <tt>i18nc("A person who creates", "Creator")</tt>
 |-
-| Creator || Refering to software || <tt>i18nc("Software", "Creator")</tt>
+| Creator || Referring to software || <tt>i18nc("Software", "Creator")</tt>
 |-
-| Display || Refering to hardware || <tt>i18nc("Hardware display", "Display")</tt>
+| Display || Referring to hardware || <tt>i18nc("Hardware display", "Display")</tt>
 |-
-| Editor || Refering to a person || <tt>i18nc("A person who edits", "Editor")</tt>
+| Editor || Referring to a person || <tt>i18nc("A person who edits", "Editor")</tt>
 |-
-| Editor || Refering to software || <tt>i18nc("Software", "Editor")</tt>
+| Editor || Referring to software || <tt>i18nc("Software", "Editor")</tt>
 |-
-| Line || Refering to drawing || <tt>i18nc("Draw a line", "Line")</tt>
+| Line || Referring to drawing || <tt>i18nc("Draw a line", "Line")</tt>
 |-
-| Line || Refering to text || <tt>i18nc("Line of text", "Line")</tt>
+| Line || Referring to text || <tt>i18nc("Line of text", "Line")</tt>
 |-
-| Name || Refering to a name of thing || <tt>i18nc("A thing's name", "Name") || In theme change dialog: i18nc("Theme name", "Name")</tt>
+| Name || Referring to a name of thing || <tt>i18nc("A thing's name", "Name") || In theme change dialog: i18nc("Theme name", "Name")</tt>
 |-
-| Name || Refering to first name and last name of person || <tt>i18nc("Person's first and last name", "Name") || In KAddessbook contact edit dialog: i18nc("Person's first and last name", "Name")</tt>
+| Name || Referring to first name and last name of person || <tt>i18nc("Person's first and last name", "Name") || In KAddessbook contact edit dialog: i18nc("Person's first and last name", "Name")</tt>
 |-
 | New || Create something || <tt>i18nc("Action", "New")</tt>
@@ Line 128: / Line 128: @@
 | (Re)load || (Re)start a program, daemon etc. || <tt>i18nc("(Re)start a program", "(Re)load")</tt>
 |-
-| Title || Refering to a person || <tt>i18nc("A person's title", "Title")</tt>
+| Title || Referring to a person || <tt>i18nc("A person's title", "Title")</tt>
 |-
-| Title || Refering to a thing || <tt>i18nc("A thing's title", "Title")</tt>
+| Title || Referring to a thing || <tt>i18nc("A thing's title", "Title")</tt>
 |-
-| Trash || Refering to the action of emptying || <tt>i18nc("The trash is not empty. Empty it", "Empty")</tt>
+| Trash || Referring to the action of emptying || <tt>i18nc("The trash is not empty. Empty it", "Empty")</tt>
 |-
-| Trash || Refering to the state of being empty || <tt>i18nc("The trash is empty. This is not an action, but a state", "Empty")</tt>
+| Trash || Referring to the state of being empty || <tt>i18nc("The trash is empty. This is not an action, but a state", "Empty")</tt>
 |-
-| Volume || Refering to sound || <tt>i18nc("Sound volume", "Volume")</tt>
+| Volume || Referring to sound || <tt>i18nc("Sound volume", "Volume")</tt>
 |-
-| Volume || Refering to a filesystem || <tt>i18nc("Filesystem volume", "Volume")</tt>
+| Volume || Referring to a filesystem || <tt>i18nc("Filesystem volume", "Volume")</tt>
 |-
-| Volume || Refering to books || <tt>i18nc("Book volume", "Volume")</tt>
+| Volume || Referring to books || <tt>i18nc("Book volume", "Volume")</tt>
 |-
 | Yes || Answer to a question || <tt>i18nc("Answer to a question", "Yes")</tt>

@@ Line 87: / Line 87: @@
 Below is a chart showing some common words and phrases in English and the context that must be used with them to ensure proper translation of them in other languages.
-{|
+{| border="1"
 |+ Standard Contexts
 |-
@@ Line 116: / Line 116: @@
 | Name || Refering to first name and last name of person || <tt>i18nc("Person's first and last name", "Name") || In KAddessbook contact edit dialog: i18nc("Person's first and last name", "Name")</tt>
 |-
-| New || Create smth || <tt>i18nc("Action", "New")</tt>
+| New || Create something || <tt>i18nc("Action", "New")</tt>
 |-
 | New || Status || <tt>i18nc("New mail message", "New")</tt>
@@ Line 204: / Line 204: @@
 == Calendaring ==
-Developing applications dealing with dates and time, such as calendars, is a very complex area. Not only may the displayed string containing a date or time may look different based on locale, but one also has to take care of other aspects such as:
+Developing applications dealing with dates and time, such as calendars, is a very complex area. Not only may the displayed string containing a date or time look different based on locale, but one also has to take care of other aspects such as:
 * which day in the week is the first one (cf int weekStartDay())
 * how many months in a year there are