From owner-svn-doc-all@FreeBSD.ORG Wed Feb 12 16:48:57 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2EEE7456; Wed, 12 Feb 2014 16:48:57 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0CC8C1653; Wed, 12 Feb 2014 16:48:57 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s1CGmuaV081763; Wed, 12 Feb 2014 16:48:56 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s1CGmulB081762; Wed, 12 Feb 2014 16:48:56 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201402121648.s1CGmulB081762@svn.freebsd.org> From: Dru Lavigne Date: Wed, 12 Feb 2014 16:48:56 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43884 - head/en_US.ISO8859-1/books/handbook/l10n X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Feb 2014 16:48:57 -0000 Author: dru Date: Wed Feb 12 16:48:56 2014 New Revision: 43884 URL: http://svnweb.freebsd.org/changeset/doc/43884 Log: White space fix only. Translators can ignore. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/l10n/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/l10n/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/l10n/chapter.xml Wed Feb 12 16:37:35 2014 (r43883) +++ head/en_US.ISO8859-1/books/handbook/l10n/chapter.xml Wed Feb 12 16:48:56 2014 (r43884) @@ -27,11 +27,11 @@ &os; is a distributed project with users and contributors located all over the world. As such, &os; supports localization - into many languages, allowing users to view, input, or - process data in non-English languages. One can - choose from most of the major languages, including, but not - limited to: Chinese, German, Japanese, Korean, French, Russian, - and Vietnamese. + into many languages, allowing users to view, input, or process + data in non-English languages. One can choose from most of the + major languages, including, but not limited to: Chinese, + German, Japanese, Korean, French, Russian, and + Vietnamese. internationalization @@ -41,7 +41,8 @@ The term internationalization has been shortened to i18n, which represents the number of letters - between the first and the last letters of internationalization. + between the first and the last letters of + internationalization. L10n uses the same naming scheme, but from localization. The i18n/L10n methods, @@ -72,7 +73,8 @@ - How to find i18n-compliant applications. + How to find i18n-compliant + applications. @@ -148,34 +150,36 @@ To determine the current locale setting: &prompt.user; locale + encodings ASCII - Language specific character sets, such as - ISO8859-1, ISO8859-15, KOI8-R, and CP437, are - described in &man.multibyte.3;. The active list of character sets can be found at the IANA - Registry. + Language specific character sets, such as ISO8859-1, + ISO8859-15, KOI8-R, and CP437, are described in + &man.multibyte.3;. The active list of character sets can be + found at the IANA + Registry. Some languages, such as Chinese or Japanese, cannot be - represented using ASCII characters and require an extended - language encoding using either wide or multibyte characters. - Examples of wide or multibyte encodings include EUC and Big5. - Older applications may mistake these encodings for control - characters while newer applications usually recognize these - characters. Depending on the implementation, users may be - required to compile an application with wide or multibyte - character support, or to configure it correctly. - - - &os; uses Xorg-compatible locale encodings. - - - The rest of - this section describes the various methods for configuring the - locale on a &os; system. The next section will discuss the - considerations for finding and compiling applications with i18n - support. + represented using ASCII characters and + require an extended language encoding using either wide or + multibyte characters. Examples of wide or multibyte encodings + include EUC and Big5. Older applications may mistake these + encodings for control characters while newer applications + usually recognize these characters. Depending on the + implementation, users may be required to compile an + application with wide or multibyte character support, or to + configure it correctly. + + + &os; uses Xorg-compatible locale encodings. + + + The rest of this section describes the various methods for + configuring the locale on a &os; system. The next section + will discuss the considerations for finding and compiling + applications with i18n support. Setting Locale for Login Shell @@ -199,15 +203,16 @@ MIME - MM_CHARSET, which sets the MIME - character set used by applications + MM_CHARSET, which sets the + MIME character set used by + applications In addition to the user's shell configuration, these - variables should also be set for - specific application configuration and - Xorg configuration. + variables should also be set for specific application + configuration and Xorg + configuration. locale login class @@ -224,9 +229,10 @@ This first method is the recommended method as it assigns the required environment variables for locale name - and MIME character sets for every possible shell. This - setup can either be performed by each user or it can be - configured for all users by the superuser. + and MIME character sets for every + possible shell. This setup can either be performed by each + user or it can be configured for all users by the + superuser. This minimal example sets both variables for Latin-1 encoding in the .login_conf of an @@ -342,10 +348,10 @@ me:\ Shell Startup File Method - This second method is not recommended as each shell that is - used requires manual configuration, where each shell has a - different configuration file and differing syntax. As an - example, to set the German language for the + This second method is not recommended as each shell + that is used requires manual configuration, where each + shell has a different configuration file and differing + syntax. As an example, to set the German language for the sh shell, these lines could be added to ~/.profile to set the shell for that user only. These lines could also be added to @@ -789,22 +795,23 @@ Not sure where to put this section, perh i18n kits under libraries. These allow developers to write a simple file and translate displayed menus and texts to each language. + The &os; - Ports Collection contains many - applications with built-in support for wide or multibyte characters for several - languages. Such applications include i18n in their names for - easy identification. However, they do not always support the - language needed. + Ports Collection contains many applications with + built-in support for wide or multibyte characters for several + languages. Such applications include i18n in + their names for easy identification. However, they do not + always support the language needed. - Some applications can be compiled - with the specific + Some applications can be compiled with the specific charset. This is usually done in the port's Makefile or by passing a value to - configure. Refer to the i18n documentation - in the respective &os; port's source for more information on how to - determine the needed configure value - or the port's Makefile to determine which - compile options to use when building the port. + configure. Refer to the + i18n documentation in the respective &os; + port's source for more information on how to determine the + needed configure value or the port's + Makefile to determine which compile options + to use when building the port. @@ -831,8 +838,9 @@ Not sure where to put this section, perh This section shows the specific settings needed to localize a &os; system for the Russian language. Refer to - Using Localization for - a more complete description of each type of setting. + Using Localization + for a more complete description of each type of + setting. To set this locale for the login shell, add the following lines to each user's @@ -925,16 +933,18 @@ Option "XkbOptions" "grp:toggle" The Russian XKB keyboard may not work with - non-localized applications. Minimally localized applications should call a - XtSetLanguageProc (NULL, NULL, NULL); - function early in the program. + non-localized applications. Minimally localized + applications should call a XtSetLanguageProc + (NULL, NULL, NULL); function early in the + program. - See http://koi8.pp.ru/xwin.html - for more instructions on - localizing Xorg applications. For - more general information about KOI8-R encoding, refer to - http://koi8.pp.ru/. + See http://koi8.pp.ru/xwin.html + for more instructions on localizing + Xorg applications. For more + general information about KOI8-R encoding, refer to http://koi8.pp.ru/. @@ -1017,8 +1027,9 @@ Option "XkbOptions" "grp:toggle"Some &os; contributors have translated parts of the &os; documentation to other languages. They are available through links on the &os; web site or - in /usr/share/doc. + xlink:href="&url.base;/index.html">&os; web + site or in + /usr/share/doc.