From owner-svn-doc-all@FreeBSD.ORG Thu Jan 24 14:57:43 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1C8EDDE0; Thu, 24 Jan 2013 14:57:43 +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 025CFD34; Thu, 24 Jan 2013 14:57:43 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0OEvgd8074490; Thu, 24 Jan 2013 14:57:42 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0OEvgjp074489; Thu, 24 Jan 2013 14:57:42 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201301241457.r0OEvgjp074489@svn.freebsd.org> From: Dru Lavigne Date: Thu, 24 Jan 2013 14:57:42 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40734 - 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: Thu, 24 Jan 2013 14:57:43 -0000 Author: dru Date: Thu Jan 24 14:57:42 2013 New Revision: 40734 URL: http://svnweb.freebsd.org/changeset/doc/40734 Log: White space only fix. Translators can ignore. 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 Thu Jan 24 14:33:33 2013 (r40733) +++ head/en_US.ISO8859-1/books/handbook/l10n/chapter.xml Thu Jan 24 14:57:42 2013 (r40734) @@ -33,29 +33,29 @@ 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. + 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. After reading this chapter, you will know: How different languages and locales are encoded - on modern operating systems. + on modern operating systems. How to set the locale for your login - shell. + shell. How to configure your console for non-English - languages. - How to use X Window System effectively with different - languages. + languages. + How to use X Window System effectively with + different languages. Where to find more information about writing - i18n-compliant applications. - + i18n-compliant applications. + Before reading this chapter, you should: Know how to install additional third-party - applications (). + applications (). @@ -64,48 +64,51 @@ What Is I18N/L10N? - - internationalization - localization - - 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 same naming - scheme, coming from localization. Combined - together, I18N/L10N methods, protocols, and applications allow - users to use languages of their choice. + + internationalization + localization + + 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 + same naming scheme, coming from localization. + 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. + 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. Why Should I Use I18N/L10N? - I18N/L10N is used whenever you wish to either view, input, or - process data in non-English languages. + I18N/L10N is used whenever you wish to either view, + input, or process data in non-English languages. What Languages Are Supported in the I18N Effort? - 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 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. 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. + 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: @@ -116,16 +119,18 @@ Language and Country Codes + 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 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: @@ -164,32 +169,36 @@ Encodings + encodings 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. + 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. 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 on how to configure it correctly or + to pass correct values into the + configure/Makefile/compiler. 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. + (see &man.multibyte.3;), e.g. ISO8859-1, ISO8859-15, + KOI8-R, CP437. @@ -199,10 +208,11 @@ You can check the active list of character sets at the IANA Registry. + url="http://www.iana.org/assignments/character-sets">IANA Registry. - &os; uses X11-compatible locale encodings instead. + &os; uses X11-compatible locale encodings + instead. @@ -211,67 +221,71 @@ I18N Applications In the FreeBSD Ports and Package system, I18N applications - have been named with I18N in their names for - easy identification. However, they do not always support the - language needed. + have been named with I18N in their names + for easy identification. However, they do not always support + the language needed. Setting Locale - 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 (~/.profile, - ~/.bashrc, ~/.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. + 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 + (~/.profile, + ~/.bashrc, + ~/.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. - You should set the following two environment variables in your configuration - files: + You should set the following two environment variables + in your configuration files: - POSIX - - LANG for &posix; &man.setlocale.3; family - functions + POSIX + + LANG for &posix; &man.setlocale.3; + family functions MIME - MM_CHARSET for applications' MIME character - set + MM_CHARSET for applications' MIME + character set - This includes the user shell configuration, the specific application - configuration, and the X11 configuration. + This includes the user shell configuration, the specific + application configuration, and the X11 configuration. Setting Locale Methods - locale - login class + + 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. + 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. Login Classes Method - 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. + 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. User Level Setup @@ -285,12 +299,14 @@ :charset=ISO-8859-1:\ :lang=de_DE.ISO8859-1: - Traditional ChineseBIG-5 encoding + Traditional Chinese + BIG-5 encoding Here is an example of a - .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, Japanese, and Korean. + .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, + Japanese, and Korean. #Users who do not wish to use monetary units or time formats #of Taiwan can manually change each variable @@ -307,7 +323,8 @@ me:\ :xmodifiers="@im=gcin": #Set gcin as the XIM Input Server See Administrator Level - Setup and &man.login.conf.5; for more details. + Setup and &man.login.conf.5; for more + details. @@ -323,8 +340,8 @@ me:\ :lang=locale_name:\ :tc=default: - So sticking with our previous example using Latin-1, it - would look like this: + So sticking with our previous example using Latin-1, + it would look like this: german|German Users Accounts:\ :charset=ISO-8859-1:\ @@ -337,58 +354,65 @@ me:\ &prompt.root; cap_mkdb /etc/login.conf to make new configuration in - /etc/login.conf visible to the system. + /etc/login.conf visible to the + system. - Changing Login Classes with &man.vipw.8; + Changing Login Classes with + &man.vipw.8; - vipw - - Use vipw to add new users, and make - the entry look like this: + vipw + + Use vipw to add new users, and + make the entry look like this: user:password:1111:11:language:0:0:User Name:/home/user:/bin/sh - Changing Login Classes with &man.adduser.8; + Changing Login Classes with + &man.adduser.8; - adduser - + adduser + login class - Use adduser to add new users, and do - the following: + Use adduser to add new users, + and do the following: 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. + language in + /etc/adduser.conf. Keep in + mind you must enter a default + class for all users of other languages in this + case. - An alternative variant is answering the specified - language each time that -Enter login class: default []: + An alternative variant is answering the + specified language each time that + + Enter login class: default []: + appears from &man.adduser.8;. - Another alternative is to use the following for each - user of a different language that you wish to + Another alternative is to use the following for + each user of a different language that you wish to add: &prompt.root; adduser -class language - Changing Login Classes with &man.pw.8; + Changing Login Classes with + &man.pw.8; - pw - - If you use &man.pw.8; for adding new users, call it in - this form: + pw + + If you use &man.pw.8; for adding new users, call + it in this form: &prompt.root; pw useradd user_name -L language @@ -398,19 +422,20 @@ me:\ Shell Startup File Method - This method is not recommended because it requires a - different setup for each possible shell program chosen. Use - the Login Class Method - instead. + This method is not recommended because it requires + a different setup for each possible shell program + chosen. 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 + To add the locale name and MIME character set, just + set the two environment variables shown below in the /etc/profile and/or - /etc/csh.login shell startup files. We - will use the German language as an example below: + /etc/csh.login shell startup files. + We will use the German language as an example + below: In /etc/profile: @@ -423,11 +448,11 @@ me:\ 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). + /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: @@ -456,33 +481,37 @@ 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 here is taken + from the /usr/share/syscons/fonts + directory, without the .fnt + suffix. - sysinstall + sysinstall keymap screenmap If required, set the keymap and screenmap for your single C chars character set through sysinstall. - Once inside sysinstall, choose Configure, then - Console. Alternatively, you can add the - following to /etc/rc.conf: + Once inside sysinstall, choose + Configure, then + Console. Alternatively, you can + 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, 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 column. + The screenmap_name here is + taken from the + /usr/share/syscons/scrnmaps directory, + 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 + column. If you have the moused daemon enabled by setting the following @@ -494,29 +523,31 @@ keychange="fkey_number sequ paragraph. - moused + 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 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: 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 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: + 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 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: @@ -566,13 +597,14 @@ keychange="fkey_number sequ - For wide or multibyte characters languages, use the correct - FreeBSD port in your + 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: + 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: @@ -586,18 +618,22 @@ keychange="fkey_number sequ Traditional Chinese (BIG-5) - chinese/big5con + chinese/big5con Japanese - japanese/kon2-16dot or - japanese/mule-freewnn + japanese/kon2-16dot or + japanese/mule-freewnn Korean - korean/han + korean/han @@ -610,30 +646,36 @@ keychange="fkey_number sequ 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; + url="http://www.x.org/">&xorg; web site or whichever X11 Server you use. - In ~/.Xresources, you can additionally - tune application specific I18N settings (e.g., fonts, menus, - etc.). + In ~/.Xresources, you can + additionally tune application specific I18N settings (e.g., + fonts, menus, etc.). Displaying Fonts - X11 True Type font server + + X11 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. + (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. Inputting Non-English Characters - X11 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. + + X11 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. @@ -641,44 +683,45 @@ keychange="fkey_number sequ 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 specific - converters. + 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 + 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 respective languages' web sites for more - information and the patch files. + 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 + 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. + 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. Compiling I18N 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 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. MySQL @@ -705,14 +748,15 @@ keychange="fkey_number sequ Russian Language (KOI8-R Encoding) + localization Russian - For more information about KOI8-R encoding, see the KOI8-R References - (Russian Net Character Set). + For more information about KOI8-R encoding, see the + KOI8-R References + (Russian Net Character Set). Locale Setup @@ -724,8 +768,8 @@ keychange="fkey_number sequ :charset=KOI8-R:\ :lang=ru_RU.KOI8-R: - See earlier in this chapter for examples of setting up the - locale. + See earlier in this chapter for examples of setting + up the locale. @@ -758,18 +802,20 @@ font8x8="cp866-8x8" - See earlier in this chapter for examples of setting up the - console. + See earlier in this chapter for examples of setting up + the console. Printer Setup + 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. Such a filter is installed + by default as + /usr/libexec/lpr/ru/koi2alt. A + Russian printer /etc/printcap entry should look like: lp|Russian local line printer:\ @@ -782,16 +828,17 @@ font8x8="cp866-8x8" &ms-dos; FS and Russian Filenames - The following example &man.fstab.5; entry enables support - for Russian filenames in mounted &ms-dos; filesystems: + 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 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 + 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. @@ -803,30 +850,30 @@ font8x8="cp866-8x8" Do non-X locale - setup first as described. + setup first as described. If you use &xorg;, - install - x11-fonts/xorg-fonts-cyrillic - package. - - Check the "Files" section - in your /etc/X11/xorg.conf file. - The following - line must be added before any other - FontPath entries: + install x11-fonts/xorg-fonts-cyrillic + package. + + Check the "Files" section in + your /etc/X11/xorg.conf file. The + following line must be added before + any other FontPath entries: FontPath "/usr/local/lib/X11/fonts/cyrillic" - See ports for more cyrillic fonts. + See ports for more cyrillic fonts. + - To activate a Russian keyboard, add the following to the - "Keyboard" section of your + To activate a Russian keyboard, add the following + to the "Keyboard" section of your xorg.conf file: Option "XkbLayout" "us,ru" @@ -837,36 +884,38 @@ Option "XkbOptions" "grp:toggle"For grp:toggle the RUS/LAT switch will be Right Alt, - for grp:ctrl_shift_toggle switch will be - CtrlShift. - For grp:caps_toggle - the RUS/LAT switch will be CapsLock. - The old CapsLock function is still - available via ShiftCapsLock (in LAT mode - only). - grp:caps_toggle does not work in - &xorg; for 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: + for grp:ctrl_shift_toggle switch + will be CtrlShift. + For grp:caps_toggle the RUS/LAT + switch will be CapsLock. The old + CapsLock function is still available + via ShiftCapsLock + (in LAT mode only). grp:caps_toggle + does not work in &xorg; for + 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: Option "XkbVariant" ",winkeys" - The Russian XKB keyboard may not work with non-localized - applications. + 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. - See - KOI8-R for X Window for more instructions on + NULL); function early in the program. + + See + KOI8-R for X Window for more instructions on localizing X11 applications. @@ -874,27 +923,31 @@ Option "XkbOptions" "grp:toggle" Traditional Chinese Localization for Taiwan + localization Traditional Chinese The FreeBSD-Taiwan Project has an Chinese HOWTO for - FreeBSD at - using many Chinese ports. - Current editor for the FreeBSD Chinese HOWTO is - Shen Chuan-Hsing statue@freebsd.sinica.edu.tw. - - - Chuan-Hsing Shen statue@freebsd.sinica.edu.tw has - created the - Chinese FreeBSD Collection (CFC) using FreeBSD-Taiwan's - zh-L10N-tut. The packages and the script files - are available at . + FreeBSD at + using many Chinese ports. Current editor for the + FreeBSD Chinese HOWTO is Shen Chuan-Hsing + statue@freebsd.sinica.edu.tw. + + Chuan-Hsing Shen + statue@freebsd.sinica.edu.tw has created the + + Chinese FreeBSD Collection (CFC) using + FreeBSD-Taiwan's zh-L10N-tut. The packages + and the script files are available at . German Language Localization (for All ISO 8859-1 Languages) + localization German @@ -902,8 +955,8 @@ Option "XkbOptions" "grp:toggle"Slaven Rezic eserte@cs.tu-berlin.de wrote a tutorial on using umlauts on a FreeBSD machine. The tutorial - is written in German and is available at - . + is written in German and is available at . *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***