From owner-svn-doc-all@FreeBSD.ORG Sun Feb 17 17:49:08 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A4D5EB17; Sun, 17 Feb 2013 17:49:08 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 9596FFB; Sun, 17 Feb 2013 17:49:08 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1HHn8GP015058; Sun, 17 Feb 2013 17:49:08 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1HHn8YI015057; Sun, 17 Feb 2013 17:49:08 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201302171749.r1HHn8YI015057@svn.freebsd.org> From: Dru Lavigne Date: Sun, 17 Feb 2013 17:49:08 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r41000 - 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.14 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: Sun, 17 Feb 2013 17:49:08 -0000 Author: dru Date: Sun Feb 17 17:49:08 2013 New Revision: 41000 URL: http://svnweb.freebsd.org/changeset/doc/41000 Log: Initial content fix. This patch addresses the following: - &os;, etc. i.e., e.g., you - xref and directory tags - fixes acronym tags and i18n/L10n - fixes grammos and clarifies some areas - removes -W as this is deprecated - removes CFC which no longer exists Approved by: gjb (mentor) 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 Sun Feb 17 17:41:05 2013 (r40999) +++ head/en_US.ISO8859-1/books/handbook/l10n/chapter.xml Sun Feb 17 17:49:08 2013 (r41000) @@ -24,38 +24,51 @@ - Localization - I18N/L10N Usage and Setup + Localization - + <acronym>i18n</acronym>/<acronym>L10n</acronym> Usage and + Setup Synopsis - FreeBSD is a very distributed project with users and - contributors located all over the world. This chapter discusses - the internationalization and localization features of FreeBSD - that allow non-English speaking users to get real work done. - There are many aspects of the i18n implementation in both the - system and application levels, so where applicable we refer - the reader to more specific sources of documentation. + &os; is a distributed project with users and contributors + located all over the world. This chapter discusses the + internationalization and localization features of &os; that + allow non-English speaking users to get real work done. Since + there are many aspects of the i18n + implementation in both the system and application levels, more + specific sources of documentation are referred to, where + applicable. After reading this chapter, you will know: - How different languages and locales are encoded - on modern operating systems. - How to set the locale for your login - shell. - How to configure your console for non-English - languages. - How to use X Window System effectively with - different languages. - Where to find more information about writing - i18n-compliant applications. + + How different languages and locales are encoded on + modern operating systems. + + + How to set the locale for a login shell. + + + How to configure the console for non-English + languages. + + + How to use Xorgeffectively + with different languages. + + + Where to find more information about writing + i18n-compliant applications. + Before reading this chapter, you should: - Know how to install additional third-party - applications (). + Know how to install + additional third-party + applications. @@ -63,7 +76,8 @@ The Basics - What Is I18N/L10N? + What Is + <acronym>i18n</acronym>/<acronym>L10n</acronym>? internationalization @@ -71,44 +85,45 @@ localization - Developers shortened internationalization into the term - I18N, counting the number of letters between the first and - the last letters of internationalization. L10N uses the + The term internationalization has been shortened to + i18n, which represents the number of + letters between the first and the last letters of + internationalization. L10n uses the same naming scheme, coming from localization. - Combined together, I18N/L10N methods, protocols, and - applications allow users to use languages of their - choice. + Combined together, + i18n/L10n methods, + protocols, and applications allow users to use languages of + their choice. - I18N applications are programmed using I18N kits under - libraries. It allows for developers to write a simple file - and translate displayed menus and texts to each language. - We strongly encourage programmers to follow this - convention. + i18n applications are programmed using + i18n kits under libraries. These allow + developers to write a simple file and translate displayed + menus and texts to each language. - Why Should I Use I18N/L10N? + Why Use + <acronym>i18n</acronym>/<acronym>L10n</acronym>? - I18N/L10N is used whenever you wish to either view, - input, or process data in non-English languages. + Using i18n/L10n + allows a user to view, input, or process data in non-English + languages. - What Languages Are Supported in the I18N Effort? + Which Languages Are Supported? - I18N and L10N are not FreeBSD specific. Currently, one - can choose from most of the major languages of the World, - including but not limited to: Chinese, German, Japanese, - Korean, French, Russian, Vietnamese and others. + i18n and L10n are + not &os; specific. Currently, one can choose from most of the + major languages, including but not limited to: Chinese, + German, Japanese, Korean, French, Russian, and + Vietnamese. Using Localization - In all its splendor, I18N is not FreeBSD-specific and is - a convention. We encourage you to help FreeBSD in following - this convention. locale Localization settings are based on three main terms: @@ -123,14 +138,11 @@ language codes country codes - In order to localize a FreeBSD system to a specific - language (or any other I18N-supporting &unix; like systems), - the user needs to find out the codes for the specific country - and language (country codes tell applications what variation - of given language to use). In addition, web browsers, - SMTP/POP servers, web servers, etc. make decisions based on - them. The following are examples of language/country - codes: + In order to localize a &os; system to a specific language, + the user needs to determine the codes for the specific country + and language as the country code tells applications which + variation of the given language to use. The following are + examples of language/country codes: @@ -174,54 +186,51 @@ ASCII Some languages use non-ASCII encodings that are 8-bit, - wide or multibyte characters, see &man.multibyte.3; for more - details. Older applications do not recognize them and mistake - them for control characters. Newer applications usually do - recognize 8-bit characters. Depending on the implementation, - users may be required to compile an application with wide or - multibyte characters support, or configure it correctly. - To be able to input and process wide or multibyte characters, - the FreeBSD Ports - Collection has provided each language with different - programs. Refer to the I18N documentation in the respective - FreeBSD Port. + wide, or multibyte characters. For more information on these + encodings, refer to &man.multibyte.3;. Older applications do + not recognize these encodings and mistake them for control + characters. Newer applications usually recognize 8-bit + characters. Depending on the implementation, users may be + required to compile an application with wide or multibyte + character support, or configure it correctly. To provide + application support for wide or multibyte characters, the + &os; Ports + Collection contains programs for several languages. + Refer to the i18n documentation in the + respective &os; port. Specifically, the user needs to look at the application - documentation to decide on how to configure it correctly or - to pass correct values into the - configure/Makefile/compiler. + documentation to decide how to configure it correctly or to + determine which compile options to use when building the + port. Some things to keep in mind are: Language specific single C chars character sets - (see &man.multibyte.3;), e.g. ISO8859-1, ISO8859-15, - KOI8-R, CP437. + such as ISO8859-1, ISO8859-15, KOI8-R, and CP437. These + are described in &man.multibyte.3;. - Wide or multibyte encodings, e.g., EUC, Big5. + Wide or multibyte encodings such as EUC and + Big5. - You can check the active list of character sets at the + The active list of character sets can be found at the IANA Registry. + url="http://www.iana.org/assignments/character-sets">IANA + Registry. - &os; uses X11-compatible locale encodings + &os; uses Xorg-compatible locale encodings instead. - - - - I18N Applications - - In the FreeBSD Ports and Package system, I18N applications - have been named with I18N in their names + In the &os; Ports Collection, i18n + applications include i18n in their names for easy identification. However, they do not always support the language needed. @@ -232,16 +241,16 @@ Usually it is sufficient to export the value of the locale name as LANG in the login shell. This could be done in the user's ~/.login_conf - file or in the startup file of the user's shell + or in the startup file of the user's shell: (~/.profile, - ~/.bashrc, + ~/.bashrc, or ~/.cshrc). There is no need to set the - locale subsets such as LC_CTYPE, - LC_CTIME. Please refer to language-specific - FreeBSD documentation for more information. + locale subsets such as LC_CTYPE or + LC_CTIME. Refer to language-specific &os; + documentation for more information. - You should set the following two environment variables - in your configuration files: + Each user should set the following two environment + variables in their configuration files: POSIX @@ -258,8 +267,9 @@ - This includes the user shell configuration, the specific - application configuration, and the X11 configuration. + These should be set in the user's shell configuration, the + specific application configuration, and the + Xorg configuration. Setting Locale Methods @@ -267,13 +277,13 @@ locale login class - There are two methods for setting locale, and both are - described below. The first (recommended one) is by - assigning the environment variables in - login class, and the - second is by adding the environment variable assignments - to the system's shell - startup file. + This section describes the two methods for setting + locale. The first is recommended and assigns the + environment variables in the login class. The second + method adds the environment variable assignments to the + system's shell startup + file. Login Classes Method @@ -281,19 +291,19 @@ This method allows environment variables needed for locale name and MIME character sets to be assigned once for every possible shell instead of adding specific shell - assignments to each shell's startup file. - User Level Setup can be - done by an user himself and - Administrator Level Setup - require superuser privileges. + assignments to each shell's startup file. User Level Setup can be + performed by each user while Administrator Level Setup + requires superuser privileges. User Level Setup - Here is a minimal example of a - .login_conf file in user's home - directory which has both variables set for Latin-1 - encoding: + This provides a minimal example of a + .login_conf located in a user's + home directory which has both variables set for the + Latin-1 encoding: me:\ :charset=ISO-8859-1:\ @@ -301,11 +311,11 @@ Traditional Chinese BIG-5 encoding - Here is an example of a + Here is an example of a user's .login_conf that sets the variables - for Traditional Chinese in BIG-5 encoding. Notice the - many more variables set because some software does not - respect locale variables correctly for Chinese, + for Traditional Chinese in BIG-5 encoding. More + variables are set because some applications do not + correctly respect locale variables for Chinese, Japanese, and Korean. #Users who do not wish to use monetary units or time formats @@ -332,39 +342,35 @@ me:\ Verify that the user's login class in /etc/login.conf sets the correct - language. Make sure these settings - appear in /etc/login.conf: + language: language_name|Account Type Description:\ :charset=MIME_charset:\ :lang=locale_name:\ :tc=default: - So sticking with our previous example using Latin-1, - it would look like this: + The previous Latin-1 example would look like + this: german|German Users Accounts:\ :charset=ISO-8859-1:\ :lang=de_DE.ISO8859-1:\ :tc=default: - Before changing users Login Classes execute - the following command: + Whenever this file is edited, execute the following + command to update the capability database: &prompt.root; cap_mkdb /etc/login.conf - to make new configuration in - /etc/login.conf visible to the - system. - Changing Login Classes with &man.vipw.8; vipw - Use vipw to add new users, and - make the entry look like this: + When using vipw to add new users, + use language to set the + language: user:password:1111:11:language:0:0:User Name:/home/user:/bin/sh @@ -375,32 +381,32 @@ me:\ adduser login class - Use adduser to add new users, - and do the following: + When using adduser to add new + users, configure the language as follows: - Set defaultclass = + If all new users use the same language, set + defaultclass = language in - /etc/adduser.conf. Keep in - mind you must enter a default - class for all users of other languages in this - case. + /etc/adduser.conf. - An alternative variant is answering the - specified language each time that + Alternatively, input the specified language at + this prompt: Enter login class: default []: - appears from &man.adduser.8;. + when creating a new user using + &man.adduser.8;. - Another alternative is to use the following for - each user of a different language that you wish to - add: + Another alternative is to use the following + when creating a user that uses a different language + than the one set in + /etc/adduser.conf: &prompt.root; adduser -class language @@ -411,7 +417,7 @@ me:\ pw - If you use &man.pw.8; for adding new users, call + If &man.pw.8; is used to add new users, call it in this form: &prompt.root; pw useradd user_name -L language @@ -423,19 +429,18 @@ me:\ This method is not recommended because it requires - a different setup for each possible shell program - chosen. Use the Login Class - Method instead. + a different setup for each shell. Use the Login Class Method + instead. MIME locale - To add the locale name and MIME character set, just - set the two environment variables shown below in the - /etc/profile and/or + To add the locale name and MIME character set, set + the two environment variables shown below in the + /etc/profile or /etc/csh.login shell startup files. - We will use the German language as an example - below: + This example sets the German language: In /etc/profile: @@ -447,25 +452,19 @@ me:\ setenv LANG de_DE.ISO8859-1 setenv MM_CHARSET ISO-8859-1 - Alternatively, you can add the above instructions to - /usr/share/skel/dot.profile (similar - to what was used in /etc/profile - above), or /usr/share/skel/dot.login - (similar to what was used in - /etc/csh.login above). - - For X11: - - In $HOME/.xinitrc: + Alternatively, add the above settings to + /usr/share/skel/dot.profile or + /usr/share/skel/dot.login. + + To configure Xorg, add + one of the following to + ~/.xinitrc, depending upon the + shell: LANG=de_DE.ISO8859-1; export LANG - Or: - setenv LANG de_DE.ISO8859-1 - Depending on your shell (see above). - @@ -481,73 +480,67 @@ me:\ font8x14=font_name font8x8=font_name - The font_name here is taken - from the /usr/share/syscons/fonts - directory, without the .fnt - suffix. + The font_name is taken from + /usr/share/syscons/fonts, + without the .fnt suffix. sysinstall keymap screenmap - If required, set the keymap and screenmap for your - single C chars character set through - sysinstall. - Once inside sysinstall, choose + The keymap and screenmap for the single C chars character + set can be set using sysinstall. Once + inside sysinstall, choose Configure, then - Console. Alternatively, you can + Console. Alternatively, add the following to /etc/rc.conf: scrnmap=screenmap_name keymap=keymap_name keychange="fkey_number sequence" - The screenmap_name here is - taken from the - /usr/share/syscons/scrnmaps directory, + The screenmap_name is taken + from /usr/share/syscons/scrnmaps, without the .scm suffix. A screenmap with a corresponding mapped font is usually needed as a workaround for expanding bit 8 to bit 9 on a VGA adapter's - font character matrix in pseudographics area, i.e., to move - letters out of that area if screen font uses a bit 8 + font character matrix. This will move letters out of the + pseudographics area if the screen font uses a bit 8 column. - If you have the moused daemon - enabled by setting the following - in your /etc/rc.conf: - -moused_enable="YES" - - then examine the mouse cursor information in the next - paragraph. + If moused is enabled in + /etc/rc.conf, review the mouse cursor + information in the next paragraph. moused - By default the mouse cursor of the &man.syscons.4; driver - occupies the 0xd0-0xd3 range in the character set. If your - language uses this range, you need to move the cursor's range - outside of it. To enable the workaround for &os;, add the - following line to /etc/rc.conf: + By default, the mouse cursor of the &man.syscons.4; driver + occupies the 0xd0-0xd3 range in the character set. If the + language uses this range, move the cursor's range. To enable + this workaround for &os;, add the following line to + /etc/rc.conf: mousechar_start=3 - The keymap_name here is taken - from the /usr/share/syscons/keymaps - directory, without the .kbd suffix. If - you are uncertain which keymap to use, you use can - &man.kbdmap.1; to test keymaps without rebooting. + The keymap_name in the above + example is taken from /usr/share/syscons/keymaps, + without the .kbd suffix. When uncertain + as to which keymap to use, &man.kbdmap.1; can be used to test + keymaps without rebooting. The keychange is usually needed to program function keys to match the selected terminal type because function key sequences cannot be defined in the key map. - Also be sure to set the correct console terminal type - in /etc/ttys for all - ttyv* entries. Current pre-defined - correspondences are: + Be sure to set the correct console terminal type in + /etc/ttys for all virtual terminal + entries. Current pre-defined correspondences are: @@ -597,14 +590,14 @@ keychange="fkey_number sequ - For wide or multibyte characters languages, use the - correct FreeBSD port in your - /usr/ports/language - directory. Some ports appear as console while the system - sees it as serial vtty's, hence you must reserve enough vtty's - for both X11 and the pseudo-serial console. Here is a partial - list of applications for using other languages in - console: + For languages with wide or multibyte characters, use the + correct &os; port in /usr/ports/language. + Some applications appear as serial terminals to the system. + Reserve enough terminals in /etc/ttys + for both Xorg and the pseudo-serial + console. Here is a partial list of applications for using + other languages in the console: @@ -641,87 +634,88 @@ keychange="fkey_number sequ - X11 Setup + Xorg Setup - Although X11 is not part of the FreeBSD Project, we have - included some information here for FreeBSD users. For more - details, refer to the &xorg; - web site or whichever X11 Server you use. - - In ~/.Xresources, you can - additionally tune application specific I18N settings (e.g., - fonts, menus, etc.). + Although Xorg is not installed + with &os;, it can be installed from the Ports Collection. + Refer to for more information on + how to do this. This section discusses how to localize + Xorg once it is installed. + + Application specific i18n settings such + as fonts and menus can be tuned in + ~/.Xresources. Displaying Fonts - X11 True Type font + Xorg True Type font server - Install &xorg; server - (x11-servers/xorg-server), - then install the language &truetype; fonts. Setting the - correct locale should allow you to view your selected - language in menus and such. + After installing x11-servers/xorg-server, install + the language's &truetype; fonts. Setting the correct locale + should allow users to view their selected language in + graphical application menus. Inputting Non-English Characters - X11 Input Method + X Input Method (XIM) - The X11 Input Method (XIM) Protocol is a new standard - for all X11 clients. All X11 applications should be written - as XIM clients that take input from XIM Input servers. - There are several XIM servers available for different - languages. + + The X Input Method (XIM) protocol + is an input standard for Xorg + clients. All Xorg applications + should be written as XIM clients that take input from XIM + input servers. There are several XIM servers available for + different languages. Printer Setup - Some single C chars character sets are usually hardware - coded into printers. Wide or multibyte character sets require - special setup and we recommend using - apsfilter. You may also convert - the document to &postscript; or PDF formats using language + Some single C chars character sets are hardware coded + into printers. Wide or multibyte character sets require + special setup using a utility such as + apsfilter. Documents can be + converted to &postscript; or PDF formats using language specific converters. Kernel and File Systems - The FreeBSD fast filesystem (FFS) is 8-bit clean, so it - can be used with any single C chars character set (see - &man.multibyte.3;), but there is no character set name stored - in the filesystem; i.e., it is raw 8-bit and does not know - anything about encoding order. Officially, FFS does not - support any form of wide or multibyte character sets yet. - However, some wide or multibyte character sets have - independent patches for FFS enabling such support. They are - only temporary unportable solutions or hacks and we have - decided to not include them in the source tree. Refer to + The &os; fast filesystem (FFS) is 8-bit + clean, so it can be used with any single C chars character + set. However, character set names are not stored in the + filesystem as it is raw 8-bit and does not understand encoding + order. Officially, FFS does not support + any form of wide or multibyte character sets. However, some + wide or multibyte character sets have independent patches for + enabling support on FFS. Refer to the respective languages' web sites for more information and the patch files. DOS Unicode - The FreeBSD &ms-dos; filesystem has the configurable - ability to convert between &ms-dos;, Unicode character sets - and chosen FreeBSD filesystem character sets. See - &man.mount.msdosfs.8; for details. + &os;'s support for the &ms-dos; filesystem has the + configurable ability to convert between &ms-dos;, Unicode + character sets, and chosen &os; filesystem character sets. + Refer to &man.mount.msdosfs.8; for details. - Compiling I18N Programs + Compiling <acronym>i18n</acronym> Programs - Many FreeBSD Ports have been ported with I18N support. - Some of them are marked with -I18N in the port name. These - and many other programs have built in support for I18N and - need no special consideration. + Many applications in the &os; Ports Collection have been + ported with i18n support. Some of these + include -i18n in the port name. These + and many other programs have built in support for + i18n and need no special + consideration. MySQL @@ -729,13 +723,13 @@ keychange="fkey_number sequ However, some applications such as MySQL need to have their Makefile configured with the specific - charset. This is usually done in the - Makefile or done by passing a value to + charset. This is usually done in the port's + Makefile or by passing a value to configure in the source. - Localizing FreeBSD to Specific Languages + Localizing &os; to Specific Languages @@ -754,22 +748,20 @@ keychange="fkey_number sequ Russian - For more information about KOI8-R encoding, see the + For more information about KOI8-R encoding, refer to KOI8-R References (Russian Net Character Set). Locale Setup - Put the following lines into your - ~/.login_conf file: + To set this locale, put the following lines into each + user's ~/.login_conf: me:My Account:\ :charset=KOI8-R:\ :lang=ru_RU.KOI8-R: - See earlier in this chapter for examples of setting - up the locale. @@ -777,33 +769,24 @@ keychange="fkey_number sequ - Add the following line - to your /etc/rc.conf file: - - mousechar_start=3 - - - - Also, use following settings in + Add the following lines to /etc/rc.conf: keymap="ru.koi8-r" scrnmap="koi8-r2cp866" font8x16="cp866b-8x16" font8x14="cp866-8x14" -font8x8="cp866-8x8" +font8x8="cp866-8x8" +mousechar_start=3 - For each ttyv* entry in + For each ttyv entry in /etc/ttys, use cons25r as the terminal type. - - See earlier in this chapter for examples of setting up - the console. @@ -812,94 +795,89 @@ font8x8="cp866-8x8" printers Since most printers with Russian characters come with hardware code page CP866, a special output filter is needed - to convert from KOI8-R to CP866. Such a filter is installed - by default as - /usr/libexec/lpr/ru/koi2alt. A - Russian printer /etc/printcap entry + to convert from KOI8-R to CP866. &os; installs a default + filter as /usr/libexec/lpr/ru/koi2alt. + A Russian printer /etc/printcap entry should look like: lp|Russian local line printer:\ :sh:of=/usr/libexec/lpr/ru/koi2alt:\ :lp=/dev/lpt0:sd=/var/spool/output/lpd:lf=/var/log/lpd-errs: - See &man.printcap.5; for a detailed description. + Refer to &man.printcap.5; for a more detailed + description. - &ms-dos; FS and Russian Filenames + &ms-dos; and Russian Filenames The following example &man.fstab.5; entry enables support for Russian filenames in mounted &ms-dos; filesystems: - /dev/ad0s2 /dos/c msdos rw,-Wkoi2dos,-Lru_RU.KOI8-R 0 0 + /dev/ad0s2 /dos/c msdos rw,-Lru_RU.KOI8-R 0 0 - The option selects the locale name - used, and sets the character conversion - table. To use the option, be sure to - mount /usr before the &ms-dos; - partition because the conversion tables are located in - /usr/libdata/msdosfs. For more - information, see the &man.mount.msdosfs.8; manual - page. + selects the locale name. Refer to + &man.mount.msdosfs.8; for more details. - X11 Setup + <application>Xorg</application> Setup - Do non-X locale - setup first as described. + First, configure the non-X locale + setup. - If you use &xorg;, - install When using &xorg;, + install the x11-fonts/xorg-fonts-cyrillic package. Check the "Files" section in - your /etc/X11/xorg.conf file. The + /etc/X11/xorg.conf. The following line must be added before any other FontPath entries: FontPath "/usr/local/lib/X11/fonts/cyrillic" - See ports for more cyrillic fonts. + Search the Ports Collection for more Cyrillic + fonts. To activate a Russian keyboard, add the following - to the "Keyboard" section of your - xorg.conf file: + to the "Keyboard" section of + /etc/xorg.conf: Option "XkbLayout" "us,ru" Option "XkbOptions" "grp:toggle" - Also make sure that XkbDisable is - turned off (commented out) there. + Make sure that XkbDisable is + commented out in that file. - For grp:toggle - the RUS/LAT switch will be Right Alt, - for grp:ctrl_shift_toggle switch - will be For grp:toggle use Right + Alt, for + grp:ctrl_shift_toggle use CtrlShift. - For grp:caps_toggle the RUS/LAT - switch will be CapsLock. The old + For grp:caps_toggle use + CapsLock. The old CapsLock function is still available - via ShiftCapsLock - (in LAT mode only). grp:caps_toggle + in LAT mode only using ShiftCapsLock. + grp:caps_toggle does not work in &xorg; for - unknown reason. + some unknown reason. - If you have &windows; keys on your - keyboard, and notice that some non-alphabetical keys - are mapped incorrectly in RUS mode, add the following - line in your xorg.conf file: + If the keyboard has &windows; keys, + and some non-alphabetical keys are mapped incorrectly, + add the following line to + /etc/xorg.conf: Option "XkbVariant" ",winkeys" @@ -910,13 +888,14 @@ Option "XkbOptions" "grp:toggle" - Minimally localized applications - should call a XtSetLanguageProc (NULL, NULL, - NULL); function early in the program. + Minimally localized applications should call a *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***