Development/Architecture/KDE3/i18n and l10n - Revision history

AnneW at 15:39, 13 July 2012

2012-07-13T15:39:02Z

Neverendingo: Text replace - "" to ""

2011-06-29T19:15:56Z

Text replace - "</code>" to "</syntaxhighlight>"

Neverendingo: Text replace - "`" to ""`


2011-06-29T19:13:34Z
Text replace - "<code cppqt>" to "<syntaxhighlight lang="cpp-qt">"

				
				
				
				
			
			← Older revision
			Revision as of 19:13, 29 June 2011
			
Line 31:
Line 31:
  Translations are made possible by the <tt>QString i18n(const char*)</tt> method which must wrap all strings that should be displayed. The QString returned by <tt>i18n()</tt> is the translated (if necessary) string. This makes creating translatable widgets as simple as in this example:   Translations are made possible by the <tt>QString i18n(const char*)</tt> method which must wrap all strings that should be displayed. The QString returned by <tt>i18n()</tt> is the translated (if necessary) string. This makes creating translatable widgets as simple as in this example:
    
− <code cppqt> + <syntaxhighlight lang="cpp-qt">
  QPushButton* myButton = new QPushButton(i18n("Translate this!"), 0);</code>   QPushButton* myButton = new QPushButton(i18n("Translate this!"), 0);</code>
    
Line 52:
Line 52:
  Additionally, translators sometimes need extra help in understanding what the text is actually referring to during the translation purpose. Use this form of i18n whenever the string to translate is short or the meaning is hard to discern when the context is not exactly known. For example:   Additionally, translators sometimes need extra help in understanding what the text is actually referring to during the translation purpose. Use this form of i18n whenever the string to translate is short or the meaning is hard to discern when the context is not exactly known. For example:
    
− <code cppqt>QString up = i18n("Go one directory up in the hierarchy", "Up"); + <syntaxhighlight lang="cpp-qt">QString up = i18n("Go one directory up in the hierarchy", "Up");
  QString relation = i18n("A person's name and their familial relationship to you.", "%1 is your %2").arg(name, relationship);</code>   QString relation = i18n("A person's name and their familial relationship to you.", "%1 is your %2").arg(name, relationship);</code>
    
Line 61:
Line 61:
  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>: <tt>QString i18n(const char* singular, const char* plural, int number)</tt>. For example:   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>: <tt>QString i18n(const char* singular, const char* plural, int number)</tt>. For example:
    
− <code cppqt>msgStr = i18n("Creating index file: 1 message done",   + <syntaxhighlight lang="cpp-qt">msgStr = i18n("Creating index file: 1 message done",  
                 "Creating index file: %n messages done", num);</code>                  "Creating index file: %n messages done", num);</code>
    
Line 68:
Line 68:
  Note that this form should be used even if the string always refers to more than one item as languages use a singular form even when referring to a multiple (typically for 21, 31, etc.). This code:   Note that this form should be used even if the string always refers to more than one item as languages use a singular form even when referring to a multiple (typically for 21, 31, etc.). This code:
    
− <code cppqt>i18n("%1 files were deleted").arg(numFilesDeleted);</code> + <syntaxhighlight lang="cpp-qt">i18n("%1 files were deleted").arg(numFilesDeleted);</code>
    
  is therefore incorrect and should instead be:   is therefore incorrect and should instead be:
    
− <code cppqt>i18n("%1 files were deleted",   + <syntaxhighlight lang="cpp-qt">i18n("%1 files were deleted",  
        "%1 files were deleted",         "%1 files were deleted",
        numFilesDeleted).arg(numFilesDeleted);</code>         numFilesDeleted).arg(numFilesDeleted);</code>



Santa: Fixed programming lang. s/cppqt3/cppqt/
2009-11-02T13:55:13Z
Fixed programming lang. s/cppqt3/cppqt/

				
				
				
				
			
			← Older revision
			Revision as of 13:55, 2 November 2009
			
Line 31:
Line 31:
  Translations are made possible by the <tt>QString i18n(const char*)</tt> method which must wrap all strings that should be displayed. The QString returned by <tt>i18n()</tt> is the translated (if necessary) string. This makes creating translatable widgets as simple as in this example:   Translations are made possible by the <tt>QString i18n(const char*)</tt> method which must wrap all strings that should be displayed. The QString returned by <tt>i18n()</tt> is the translated (if necessary) string. This makes creating translatable widgets as simple as in this example:
    
− <code cppqt3> + <code cppqt>
  QPushButton* myButton = new QPushButton(i18n("Translate this!"), 0);</code>   QPushButton* myButton = new QPushButton(i18n("Translate this!"), 0);</code>
    
Line 52:
Line 52:
  Additionally, translators sometimes need extra help in understanding what the text is actually referring to during the translation purpose. Use this form of i18n whenever the string to translate is short or the meaning is hard to discern when the context is not exactly known. For example:   Additionally, translators sometimes need extra help in understanding what the text is actually referring to during the translation purpose. Use this form of i18n whenever the string to translate is short or the meaning is hard to discern when the context is not exactly known. For example:
    
− <code cppqt3>QString up = i18n("Go one directory up in the hierarchy", "Up"); + <code cppqt>QString up = i18n("Go one directory up in the hierarchy", "Up");
  QString relation = i18n("A person's name and their familial relationship to you.", "%1 is your %2").arg(name, relationship);</code>   QString relation = i18n("A person's name and their familial relationship to you.", "%1 is your %2").arg(name, relationship);</code>
    
Line 61:
Line 61:
  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>: <tt>QString i18n(const char* singular, const char* plural, int number)</tt>. For example:   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>: <tt>QString i18n(const char* singular, const char* plural, int number)</tt>. For example:
    
− <code cppqt3>msgStr = i18n("Creating index file: 1 message done",   + <code cppqt>msgStr = i18n("Creating index file: 1 message done",  
                 "Creating index file: %n messages done", num);</code>                  "Creating index file: %n messages done", num);</code>
    
Line 68:
Line 68:
  Note that this form should be used even if the string always refers to more than one item as languages use a singular form even when referring to a multiple (typically for 21, 31, etc.). This code:   Note that this form should be used even if the string always refers to more than one item as languages use a singular form even when referring to a multiple (typically for 21, 31, etc.). This code:
    
− <code cppqt3>i18n("%1 files were deleted").arg(numFilesDeleted);</code> + <code cppqt>i18n("%1 files were deleted").arg(numFilesDeleted);</code>
    
  is therefore incorrect and should instead be:   is therefore incorrect and should instead be:
    
− <code cppqt3>i18n("%1 files were deleted",   + <code cppqt>i18n("%1 files were deleted",  
        "%1 files were deleted",         "%1 files were deleted",
        numFilesDeleted).arg(numFilesDeleted);</code>         numFilesDeleted).arg(numFilesDeleted);</code>





Hualiang.miao at 15:58, 15 February 2009
2009-02-15T15:58:46Z


				
				
				
				
			
			← Older revision
			Revision as of 15:58, 15 February 2009
			
Line 1:
Line 1:
  + {{Template:I18n/Language Navigation Bar|Development/Architecture/KDE3/i18n and l10n}}
  + 
  + 
  Reaching a broad audience of users and developers requires that your software can be translated and otherwise shaped at runtime to be linguistically and culturally relevant to whomever is sitting in front of the computer. This is the realm of localization and this tutorial steps you through what is needed to make your application localizable.   Reaching a broad audience of users and developers requires that your software can be translated and otherwise shaped at runtime to be linguistically and culturally relevant to whomever is sitting in front of the computer. This is the realm of localization and this tutorial steps you through what is needed to make your application localizable.
    



Hualiang.miao: Undo revision 38620 by Hualiang.miao (Talk)
2009-02-15T15:58:01Z
Undo revision 38620 by Hualiang.miao (Talk)

				
				
				
				
			
			← Older revision
			Revision as of 15:58, 15 February 2009
			
Line 1:
Line 1:
− {{Template:I18n/Language Navigation Bar|Development/Architecture/KDE3/i18n and l10n}}  
−  
  Reaching a broad audience of users and developers requires that your software can be translated and otherwise shaped at runtime to be linguistically and culturally relevant to whomever is sitting in front of the computer. This is the realm of localization and this tutorial steps you through what is needed to make your application localizable.   Reaching a broad audience of users and developers requires that your software can be translated and otherwise shaped at runtime to be linguistically and culturally relevant to whomever is sitting in front of the computer. This is the realm of localization and this tutorial steps you through what is needed to make your application localizable.
    
− == 什么是国际化和本地化？ == + == What is Internationalization and Localization? ==
    
− 国际化,或i18n ('i', 紧跟着18个字母然后是个'n'), 开发你的程序，让他们可以在任意一种本地文化氛围中工作。 这意味下列因素要被考虑起来： + Internationalization, or i18n ('i', followed by 18 letters, then an 'n'), is the process of writing your application so that it can be run in any locale. This means taking into account such things as:
− * 给用户显示的文字消息 + * textual messages that are displayed to the user
− * 用户输入的数据，文件和其他资源 + * data input from the user, files and other sources
− * 日期，数字，货币等 + * format of dates, numbers, currency, dates, etc.
    
− 本地化,或l10n ('l',  紧跟着18个字母然后是个'n'), 把国际化开发的程序进行特定文化的本地化工作。 + Localization, or l10n ('l', followed by 10 characters, then an 'n'), is the process of taking an internationalized application and adapting it for a specific locale.
    
− 总得来说, 程序员开发国际化的程序而翻译团队作本地化工作。 + Generaly speaking, programmers internationalize their applications and translation teams localize them.
    
− == 为什么这很重要? == + == Why is This Important? ==
    
  KDE development happens primarily in English as this allows the broadest reach into the development and translation communities. However, English is not the primary language of most people on the planet. In fact, fewer than 8% of humanity speaks English and less than 5% speak it as their mother tongue. Even on the Internet, only 35% people who are online use English as their primary language and as more and more of the world gets wired this number is only decreasing. Additionally most languages, including 9 out of the 10 most common languages, use non-ASCII characters in their written form. It is easy to see, then, why it has become a necessity to provide localized software.     KDE development happens primarily in English as this allows the broadest reach into the development and translation communities. However, English is not the primary language of most people on the planet. In fact, fewer than 8% of humanity speaks English and less than 5% speak it as their mother tongue. Even on the Internet, only 35% people who are online use English as their primary language and as more and more of the world gets wired this number is only decreasing. Additionally most languages, including 9 out of the 10 most common languages, use non-ASCII characters in their written form. It is easy to see, then, why it has become a necessity to provide localized software.  
Line 20:
Line 18:
  As an international project that spans the globe such localization is a core value within the KDE culture. In fact, while many KDE developers write their software in English they use the desktop in their native locale.   As an international project that spans the globe such localization is a core value within the KDE culture. In fact, while many KDE developers write their software in English they use the desktop in their native locale.
    
− == 使用i18n()的可翻译代码 == + == Translatable Code Using i18n() ==
    
  To ensure applications are ready to be localized they have to follow a few simple rules. All user-visible strings in the application should be translated before they are displayed on the user's screen, exceptions to this being debugging messages, configuration keys and similar types of text data.   To ensure applications are ready to be localized they have to follow a few simple rules. All user-visible strings in the application should be translated before they are displayed on the user's screen, exceptions to this being debugging messages, configuration keys and similar types of text data.
Line 31:
Line 29:
    
  <code cppqt3>   <code cppqt3>
− QPushButton* myButton = new QPushButton(i18n("翻译我!"), 0);</code> + QPushButton* myButton = new QPushButton(i18n("Translate this!"), 0);</code>
    
  QString's native Unicode support ensures that all translations are represented correctly. All string handling done by your application should therefore use QString.   QString's native Unicode support ensures that all translations are represented correctly. All string handling done by your application should therefore use QString.
    
− {{tip|如果文字摇被翻译到包含非UTF8字符的字符串，用utf8()方法来获取char*。}} + {{tip|If the string to be translated contains any non-UTF8 characters, use the utf8() method to get a char*.}}
    
  === I18N_NOOP ===   === I18N_NOOP ===
Line 43:
Line 41:
  When you want to actually translate the string at runtime, you still have to use i18n() with exactly the same string. I18N_NOOP() is typically used for strings given to KAboutData, because it is constructed before the KApplication and you can use i18n() only after the construction of the KApplication. Other than these special cases, it is always safe to use i18n() if you are sure that the code will be executed after construction of KApplication or some other KInstance.     When you want to actually translate the string at runtime, you still have to use i18n() with exactly the same string. I18N_NOOP() is typically used for strings given to KAboutData, because it is constructed before the KApplication and you can use i18n() only after the construction of the KApplication. Other than these special cases, it is always safe to use i18n() if you are sure that the code will be executed after construction of KApplication or some other KInstance.  
    
− === 添加上下文=== + === Adding Context ===
    
  There is an extended version of <tt>i18n()</tt> which takes two <tt>const char*</tt> arguments. The first argument is an additional contextual description of the second, translated string. The first string is used to find the proper corresponding translation at run-time and is shown to translators to help them understand the meaning of the string.     There is an extended version of <tt>i18n()</tt> which takes two <tt>const char*</tt> arguments. The first argument is an additional contextual description of the second, translated string. The first string is used to find the proper corresponding translation at run-time and is shown to translators to help them understand the meaning of the string.  
Line 54:
Line 52:
  QString relation = i18n("A person's name and their familial relationship to you.", "%1 is your %2").arg(name, relationship);</code>   QString relation = i18n("A person's name and their familial relationship to you.", "%1 is your %2").arg(name, relationship);</code>
    
− {{note|有一个I18N_NOOP2("context","text")的宏，可以把未进行翻译的字符串加一个上下文环境 。}} + {{note|There is also a I18N_NOOP2("context","text") macro for providing untranslated strings with a context.}}
    
  === Plurals ===   === Plurals ===
Line 75:
Line 73:
        numFilesDeleted).arg(numFilesDeleted);</code>         numFilesDeleted).arg(numFilesDeleted);</code>
    
− == 日期和数字的格式化 == + == Formatting Dates and Numbers ==
    
  When displaying a number to the user, your program must take care of the decimal separator, thousand separator and currency symbol (if any) being used. These symbols differ from region to region. In English speaking countries a dot (.) is used to separate the fractional part of a number, while in some European countries a comma (,) is used instead. Below is a short summary of functions that will help you format the numbers correctly, taking the local conventions into account for you.   When displaying a number to the user, your program must take care of the decimal separator, thousand separator and currency symbol (if any) being used. These symbols differ from region to region. In English speaking countries a dot (.) is used to separate the fractional part of a number, while in some European countries a comma (,) is used instead. Below is a short summary of functions that will help you format the numbers correctly, taking the local conventions into account for you.
Line 108:
Line 106:
  Similar functions exist to read information provided by the user at runtime in their localized format, e.g. readNumber() or readMoney().   Similar functions exist to read information provided by the user at runtime in their localized format, e.g. readNumber() or readMoney().
    
− == 日历 == + == 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 may look different based on locale, but one also has to take care of other aspects such as:
Line 134:
Line 132:
  |}   |}
    
− == 更多信息 == + == Further Information ==
− 更多信息请参阅[http://i18n.kde.org i18n 网页]。 + For additional information have a look at the [http://i18n.kde.org i18n pages].
    
  [[Category:KDE3]]   [[Category:KDE3]]
  [[Category:Architecture]]   [[Category:Architecture]]



Hualiang.miao at 15:51, 15 February 2009
2009-02-15T15:51:48Z


				
				
				
				
			
			← Older revision
			Revision as of 15:51, 15 February 2009
			
Line 1:
Line 1:
  + {{Template:I18n/Language Navigation Bar|Development/Architecture/KDE3/i18n and l10n}}
  + 
  Reaching a broad audience of users and developers requires that your software can be translated and otherwise shaped at runtime to be linguistically and culturally relevant to whomever is sitting in front of the computer. This is the realm of localization and this tutorial steps you through what is needed to make your application localizable.   Reaching a broad audience of users and developers requires that your software can be translated and otherwise shaped at runtime to be linguistically and culturally relevant to whomever is sitting in front of the computer. This is the realm of localization and this tutorial steps you through what is needed to make your application localizable.
    
− == What is Internationalization and Localization? == + == 什么是国际化和本地化？ ==
    
− Internationalization, or i18n ('i', followed by 18 letters, then an 'n'), is the process of writing your application so that it can be run in any locale. This means taking into account such things as: + 国际化,或i18n ('i', 紧跟着18个字母然后是个'n'), 开发你的程序，让他们可以在任意一种本地文化氛围中工作。 这意味下列因素要被考虑起来：
− * textual messages that are displayed to the user + * 给用户显示的文字消息
− * data input from the user, files and other sources + * 用户输入的数据，文件和其他资源
− * format of dates, numbers, currency, dates, etc. + * 日期，数字，货币等
    
− Localization, or l10n ('l', followed by 10 characters, then an 'n'), is the process of taking an internationalized application and adapting it for a specific locale. + 本地化,或l10n ('l',  紧跟着18个字母然后是个'n'), 把国际化开发的程序进行特定文化的本地化工作。
    
− Generaly speaking, programmers internationalize their applications and translation teams localize them. + 总得来说, 程序员开发国际化的程序而翻译团队作本地化工作。
    
− == Why is This Important? == + == 为什么这很重要? ==
    
  KDE development happens primarily in English as this allows the broadest reach into the development and translation communities. However, English is not the primary language of most people on the planet. In fact, fewer than 8% of humanity speaks English and less than 5% speak it as their mother tongue. Even on the Internet, only 35% people who are online use English as their primary language and as more and more of the world gets wired this number is only decreasing. Additionally most languages, including 9 out of the 10 most common languages, use non-ASCII characters in their written form. It is easy to see, then, why it has become a necessity to provide localized software.     KDE development happens primarily in English as this allows the broadest reach into the development and translation communities. However, English is not the primary language of most people on the planet. In fact, fewer than 8% of humanity speaks English and less than 5% speak it as their mother tongue. Even on the Internet, only 35% people who are online use English as their primary language and as more and more of the world gets wired this number is only decreasing. Additionally most languages, including 9 out of the 10 most common languages, use non-ASCII characters in their written form. It is easy to see, then, why it has become a necessity to provide localized software.  
Line 18:
Line 20:
  As an international project that spans the globe such localization is a core value within the KDE culture. In fact, while many KDE developers write their software in English they use the desktop in their native locale.   As an international project that spans the globe such localization is a core value within the KDE culture. In fact, while many KDE developers write their software in English they use the desktop in their native locale.
    
− == Translatable Code Using i18n() == + == 使用i18n()的可翻译代码 ==
    
  To ensure applications are ready to be localized they have to follow a few simple rules. All user-visible strings in the application should be translated before they are displayed on the user's screen, exceptions to this being debugging messages, configuration keys and similar types of text data.   To ensure applications are ready to be localized they have to follow a few simple rules. All user-visible strings in the application should be translated before they are displayed on the user's screen, exceptions to this being debugging messages, configuration keys and similar types of text data.
Line 29:
Line 31:
    
  <code cppqt3>   <code cppqt3>
− QPushButton* myButton = new QPushButton(i18n("Translate this!"), 0);</code> + QPushButton* myButton = new QPushButton(i18n("翻译我!"), 0);</code>
    
  QString's native Unicode support ensures that all translations are represented correctly. All string handling done by your application should therefore use QString.   QString's native Unicode support ensures that all translations are represented correctly. All string handling done by your application should therefore use QString.
    
− {{tip|If the string to be translated contains any non-UTF8 characters, use the utf8() method to get a char*.}} + {{tip|如果文字摇被翻译到包含非UTF8字符的字符串，用utf8()方法来获取char*。}}
    
  === I18N_NOOP ===   === I18N_NOOP ===
Line 41:
Line 43:
  When you want to actually translate the string at runtime, you still have to use i18n() with exactly the same string. I18N_NOOP() is typically used for strings given to KAboutData, because it is constructed before the KApplication and you can use i18n() only after the construction of the KApplication. Other than these special cases, it is always safe to use i18n() if you are sure that the code will be executed after construction of KApplication or some other KInstance.     When you want to actually translate the string at runtime, you still have to use i18n() with exactly the same string. I18N_NOOP() is typically used for strings given to KAboutData, because it is constructed before the KApplication and you can use i18n() only after the construction of the KApplication. Other than these special cases, it is always safe to use i18n() if you are sure that the code will be executed after construction of KApplication or some other KInstance.  
    
− === Adding Context === + === 添加上下文===
    
  There is an extended version of <tt>i18n()</tt> which takes two <tt>const char*</tt> arguments. The first argument is an additional contextual description of the second, translated string. The first string is used to find the proper corresponding translation at run-time and is shown to translators to help them understand the meaning of the string.     There is an extended version of <tt>i18n()</tt> which takes two <tt>const char*</tt> arguments. The first argument is an additional contextual description of the second, translated string. The first string is used to find the proper corresponding translation at run-time and is shown to translators to help them understand the meaning of the string.  
Line 52:
Line 54:
  QString relation = i18n("A person's name and their familial relationship to you.", "%1 is your %2").arg(name, relationship);</code>   QString relation = i18n("A person's name and their familial relationship to you.", "%1 is your %2").arg(name, relationship);</code>
    
− {{note|There is also a I18N_NOOP2("context","text") macro for providing untranslated strings with a context.}} + {{note|有一个I18N_NOOP2("context","text")的宏，可以把未进行翻译的字符串加一个上下文环境 。}}
    
  === Plurals ===   === Plurals ===
Line 73:
Line 75:
        numFilesDeleted).arg(numFilesDeleted);</code>         numFilesDeleted).arg(numFilesDeleted);</code>
    
− == Formatting Dates and Numbers == + == 日期和数字的格式化 ==
    
  When displaying a number to the user, your program must take care of the decimal separator, thousand separator and currency symbol (if any) being used. These symbols differ from region to region. In English speaking countries a dot (.) is used to separate the fractional part of a number, while in some European countries a comma (,) is used instead. Below is a short summary of functions that will help you format the numbers correctly, taking the local conventions into account for you.   When displaying a number to the user, your program must take care of the decimal separator, thousand separator and currency symbol (if any) being used. These symbols differ from region to region. In English speaking countries a dot (.) is used to separate the fractional part of a number, while in some European countries a comma (,) is used instead. Below is a short summary of functions that will help you format the numbers correctly, taking the local conventions into account for you.
Line 106:
Line 108:
  Similar functions exist to read information provided by the user at runtime in their localized format, e.g. readNumber() or readMoney().   Similar functions exist to read information provided by the user at runtime in their localized format, e.g. readNumber() or readMoney().
    
− == 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 may look different based on locale, but one also has to take care of other aspects such as:
Line 132:
Line 134:
  |}   |}
    
− == Further Information == + == 更多信息 ==
− For additional information have a look at the [http://i18n.kde.org i18n pages]. + 更多信息请参阅[http://i18n.kde.org i18n 网页]。
    
  [[Category:KDE3]]   [[Category:KDE3]]
  [[Category:Architecture]]   [[Category:Architecture]]



Dhaumann: Development/Architecture/KDE 3 Architecture/i18n and l10n moved to Development/Architecture/KDE3/i18n and l10n
2007-03-11T21:37:04Z
Development/Architecture/KDE 3 Architecture/i18n and l10n moved to Development/Architecture/KDE3/i18n and l10n

			
			← Older revision
			Revision as of 21:37, 11 March 2007
			


Pino: link to the qt3 classes
2007-03-07T22:21:24Z
link to the qt3 classes

				
				
				
				
			
			← Older revision
			Revision as of 22:21, 7 March 2007
			
Line 28:
Line 28:
  Translations are made possible by the <tt>QString i18n(const char*)</tt> method which must wrap all strings that should be displayed. The QString returned by <tt>i18n()</tt> is the translated (if necessary) string. This makes creating translatable widgets as simple as in this example:   Translations are made possible by the <tt>QString i18n(const char*)</tt> method which must wrap all strings that should be displayed. The QString returned by <tt>i18n()</tt> is the translated (if necessary) string. This makes creating translatable widgets as simple as in this example:
    
− <code cppqt> + <code cppqt3>
  QPushButton* myButton = new QPushButton(i18n("Translate this!"), 0);</code>   QPushButton* myButton = new QPushButton(i18n("Translate this!"), 0);</code>
    
Line 49:
Line 49:
  Additionally, translators sometimes need extra help in understanding what the text is actually referring to during the translation purpose. Use this form of i18n whenever the string to translate is short or the meaning is hard to discern when the context is not exactly known. For example:   Additionally, translators sometimes need extra help in understanding what the text is actually referring to during the translation purpose. Use this form of i18n whenever the string to translate is short or the meaning is hard to discern when the context is not exactly known. For example:
    
− <code cppqt>QString up = i18n("Go one directory up in the hierarchy", "Up"); + <code cppqt3>QString up = i18n("Go one directory up in the hierarchy", "Up");
  QString relation = i18n("A person's name and their familial relationship to you.", "%1 is your %2").arg(name, relationship);</code>   QString relation = i18n("A person's name and their familial relationship to you.", "%1 is your %2").arg(name, relationship);</code>
    
Line 58:
Line 58:
  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>: <tt>QString i18n(const char* singular, const char* plural, int number)</tt>. For example:   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>: <tt>QString i18n(const char* singular, const char* plural, int number)</tt>. For example:
    
− <code cppqt>msgStr = i18n("Creating index file: 1 message done",   + <code cppqt3>msgStr = i18n("Creating index file: 1 message done",  
                 "Creating index file: %n messages done", num);</code>                  "Creating index file: %n messages done", num);</code>
    
Line 65:
Line 65:
  Note that this form should be used even if the string always refers to more than one item as languages use a singular form even when referring to a multiple (typically for 21, 31, etc.). This code:   Note that this form should be used even if the string always refers to more than one item as languages use a singular form even when referring to a multiple (typically for 21, 31, etc.). This code:
    
− <code cppqt>i18n("%1 files were deleted").arg(numFilesDeleted);</code> + <code cppqt3>i18n("%1 files were deleted").arg(numFilesDeleted);</code>
    
  is therefore incorrect and should instead be:   is therefore incorrect and should instead be:
    
− <code cppqt>i18n("%1 files were deleted",   + <code cppqt3>i18n("%1 files were deleted",  
        "%1 files were deleted",         "%1 files were deleted",
        numFilesDeleted).arg(numFilesDeleted);</code>         numFilesDeleted).arg(numFilesDeleted);</code>
Line 96:
Line 96:
               bool shortFormat=false )</pre>                bool shortFormat=false )</pre>
  |-   |-
− | Time || QTime || <pre>formatTime( const QTime & pTime,   + | Time || {{qt3|QTime}} || <pre>formatTime( const QTime & pTime,  
               bool includeSecs=false)</pre>                bool includeSecs=false)</pre>
  |-   |-
− | Date&nbsp;and&nbsp;time || QDateTime || <pre>formatDateTime( const QDateTime &pDateTime, + | Date&nbsp;and&nbsp;time || {{qt3|QDateTime}} || <pre>formatDateTime( const QDateTime &pDateTime,
                   bool shortFormat = true,                    bool shortFormat = true,
                   bool includeSecs = false )</pre>                    bool includeSecs = false )</pre>
Line 121:
Line 121:
  ! Formats&nbsp;a.. !! From&nbsp;a.. !! Function Prototype   ! Formats&nbsp;a.. !! From&nbsp;a.. !! Function Prototype
  |-   |-
− | Date || QDate || <pre>formatDate( const QDate & pDate, + | Date || /klocal/QDate || <pre>formatDate( const QDate & pDate,
               bool shortFormat=false )</pre>                bool shortFormat=false )</pre>
  |-   |-
− | Time || QTime || <pre>formatTime( const QTime & pTime, + | Time || {{qt3|QTime}} || <pre>formatTime( const QTime & pTime,
               bool includeSecs=false )</pre>                bool includeSecs=false )</pre>
  |-   |-
− | Date&nbsp;and&nbsp;time || QDateTime || <pre>formatDateTime( const QDateTime &pDateTime, + | Date&nbsp;and&nbsp;time || {{qt3|QDateTime}} || <pre>formatDateTime( const QDateTime &pDateTime,
                   bool shortFormat=true,                    bool shortFormat=true,
                   bool includeSecs=false )</pre>                    bool includeSecs=false )</pre>



Dhaumann: Category:KDE3 Category:Architecture
2007-01-23T09:38:42Z
Category:KDE3 Category:Architecture

				
				
				
				
			
			← Older revision
			Revision as of 09:38, 23 January 2007
			
Line 135:
Line 135:
  For additional information have a look at the [http://i18n.kde.org i18n pages].   For additional information have a look at the [http://i18n.kde.org i18n pages].
    
− [[Category:Programming]] + [[Category:KDE3]]
  + [[Category:Architecture]]

← Older revision		Revision as of 15:39, 13 July 2012
Line 1:		Line 1:
−	~~{{Template:I18n/Language Navigation Bar\|Development/Architecture/KDE3/i18n and l10n}}~~
−

	Reaching a broad audience of users and developers requires that your software can be translated and otherwise shaped at runtime to be linguistically and culturally relevant to whomever is sitting in front of the computer. This is the realm of localization and this tutorial steps you through what is needed to make your application localizable.		Reaching a broad audience of users and developers requires that your software can be translated and otherwise shaped at runtime to be linguistically and culturally relevant to whomever is sitting in front of the computer. This is the realm of localization and this tutorial steps you through what is needed to make your application localizable.

← Older revision		Revision as of 15:58, 15 February 2009
Line 1:		Line 1:
		+	{{Template:I18n/Language Navigation Bar\|Development/Architecture/KDE3/i18n and l10n}}
		+
		+
	Reaching a broad audience of users and developers requires that your software can be translated and otherwise shaped at runtime to be linguistically and culturally relevant to whomever is sitting in front of the computer. This is the realm of localization and this tutorial steps you through what is needed to make your application localizable.		Reaching a broad audience of users and developers requires that your software can be translated and otherwise shaped at runtime to be linguistically and culturally relevant to whomever is sitting in front of the computer. This is the realm of localization and this tutorial steps you through what is needed to make your application localizable.

← Older revision		Revision as of 09:38, 23 January 2007
Line 135:		Line 135:
	For additional information have a look at the [http://i18n.kde.org i18n pages].		For additional information have a look at the [http://i18n.kde.org i18n pages].

−	[[Category:~~Programming~~]]	+	[[Category:KDE3]]
		+	[[Category:Architecture]]