Date: Thu, 30 Nov 2000 16:32:57 -0600 From: "Michael C . Wu" <keichii@iteration.net> To: doc@freebsd.org Subject: Handbook L10N chapter update Message-ID: <20001130163257.A20217@peorth.iteration.net>
next in thread | raw e-mail | index | archive | help
--wac7ysb48OaltWcw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hello, I have updated the l10n chapter of the handbook and attached a cvs diff. However, I have a few questions regarding this. Why did someone change the examples to European languages only when I originally had CJK *and* European examples? The current version only has German and Russian examples, which does not help the Asian users very much. There are many many problems with CJK support and we do not address any of those after the changes. Please, I ask you to not just assume that everybody living in the world speaks ISO8859-1/15 languages. And please notify me before you make *any* changes to that chapter for a small peer review like what should happen in the monolithic peer-reviewed FreeBSD development system. I have been fighting these secret changes several times since Rev. 1.16, and it is now Rev.1.40, still fighting. -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ --wac7ysb48OaltWcw Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="l10n.sgml.diff" Index: chapter.sgml =================================================================== RCS file: /home/ncvs/doc/en_US.ISO_8859-1/books/handbook/l10n/chapter.sgml,v retrieving revision 1.40 diff -u -r1.40 chapter.sgml --- chapter.sgml 2000/08/25 08:53:23 1.40 +++ chapter.sgml 2000/11/30 20:21:52 @@ -1,16 +1,16 @@ <!-- The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO_8859-1/books/handbook/l10n/chapter.sgml,v 1.40 2000/08/25 08:53:23 ache Exp $ + $FreeBSD: doc/en_US.ISO_8859-1/books/handbook/L10N/chapter.sgml,v 1.40 2000/08/25 08:53:23 ache Exp $ --> -<chapter id="l10n"> +<chapter id="L10N"> <title>Localization - I18N/L10N Usage and Setup</title> <para><emphasis>Contributed by &a.ache;</emphasis></para> - <para><emphasis>Rewritten by Michael Chin-Yuan Wu - <email>keichii@mail.utexas.edu</email>, 6 March 2000.</emphasis></para> + <para><emphasis>Rewritten by Michael C. Wu + <email>keichii@iteration.net</email>, 30 Nov 2000.</emphasis></para> <sect1> <title>Synopsis</title> @@ -24,8 +24,8 @@ that is responsible for each language.</para> <para>The author realizes that he may have been incomplete in the - description of the i18n process in FreeBSD. Due to the various - levels of i18n implementation in both the system and application + description of the I18N process in FreeBSD. Due to the various + levels of I18N implementation in both the system and application levels, we advise you to refer to individual documentation, man pages, READMEs, and so forth.</para> @@ -37,42 +37,42 @@ <title>The Basics</title> <sect2> - <title>What is i18n/l10n?</title> + <title>What is I18N/L10N?</title> - <para>Developers shortened internationalization into the term i18n, + <para>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 + letters of internationalization. L10N uses the same naming scheme, coming from "localization". Combined - together, i18n/l10n methods, protocols, and applications allow + together, I18N/L10N methods, protocols, and applications allow users to use languages of their choice.</para> - <para>I18n applications are programmed using i18n kits under + <para>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.</para> </sect2> <sect2> - <title>Why should I use i18n/l10n?</title> + <title>Why should I use I18N/L10N?</title> - <para>I18n/l10n is used whenever you wish to either view, input, or + <para>I18N/L10N is used whenever you wish to either view, input, or process data in non-English languages.</para> </sect2> <sect2> - <title>What languages are supported in the i18n effort?</title> + <title>What languages are supported in the I18N effort?</title> - <para>I18n and l10n are not FreeBSD specific. Currently, one can + <para>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, French, Russian, - and others.</para> + but not limited to: Chinese, German, Japanese, Korean, French, + Russian, Vietnamese and others.</para> </sect2> </sect1> <sect1 id="using-localization"> <title>Using Localization</title> - <para>In all its splendor, i18n is not FreeBSD-specific and is a + <para>In all its splendor, I18N is not FreeBSD-specific and is a convention. We encourage you to help FreeBSD in following this convention.</para> @@ -87,7 +87,7 @@ <title>Language and Country Codes</title> <para>In order to localize a FreeBSD system to a specific language - (or any other i18n-supporting UNIX's), the user needs to find out + (or any other I18N-supporting UNIX's), the user needs to find out the codes for the specify country and language (country codes tell applications what variation of given language to use). In addition, web @@ -134,9 +134,9 @@ 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 <ulink + To be able to input and process wide or multibyte characters, the <ulink url="../ports/">FreeBSD Ports collection</ulink> has provided - each language with different programs. Refer to the i18n + each language with different programs. Refer to the I18N documentation in the respective FreeBSD Port.</para> <para>Specifically, the user needs to look at the application @@ -149,7 +149,7 @@ <listitem> <para>Language specific single C chars character sets (see &man.multibyte.3;), i.e., - ISO_8859-1, KOI8-R, CP437.</para> + ISO_8859-1, ISO_8859-15, KOI8-R, CP437.</para> </listitem> <listitem> @@ -163,10 +163,10 @@ </sect2> <sect2> - <title>I18n applications</title> + <title>I18N applications</title> - <para>In the FreeBSD Ports and Package system, i18n applications - have been named with <literal>i18n</literal> in their names for + <para>In the FreeBSD Ports and Package system, I18N applications + have been named with <literal>I18N</literal> in their names for easy identification. However, they do not always support the language needed.</para> </sect2> @@ -233,10 +233,31 @@ encoding:</para> <programlisting> -me:My Account:\ +german:German User:\ :charset=ISO-8859-1:\ :lang=de_DE.ISO_8859-1:</programlisting> + <para>Here is an example of a + <filename>.login_conf</filename> 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.</para> + + <programlisting> +#Users who do not wish to use monetary units or time formats +#of Taiwan can manually change each variable +taiwan:Taiwanese User:\ + lang=zh_TW.Big5:\ + lc_all=zh_TW.Big:\ + lc_collate=zh_TW.Big5:\ + lc_ctype=zh_TW.Big5:\ + lc_messages=zh_TW.Big5:\ + lc_monetary=zh_TW.Big5:\ + lc_numeric=zh_TW.Big5:\ + lc_time=zh_TW.Big5:\ + charset=big5:\ + xmodifiers="@im=xcin": #Setting the XIM Input Server</programlisting> + <para>See <link linkend="adm-setup">Administrator Level Setup</link> and &man.login.conf.5; for more details.</para> </sect5> @@ -516,7 +537,7 @@ web site</ulink> or whichever X11 Server you use.</para> <para>In <filename>~/.Xresources</filename>, you can additionally - tune application specific i18n settings (e.g., fonts, menus, + tune application specific I18N settings (e.g., fonts, menus, etc.).</para> <sect3> @@ -574,15 +595,15 @@ <sect1> <title>Advanced Topics</title> - <para>If you wish to compile i18n applications or program i18n + <para>If you wish to compile I18N applications or program I18N compliant applications, please read this section.</para> <sect2> - <title>Compiling i18n Programs</title> + <title>Compiling I18N Programs</title> - <para>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 + <para>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.</para> <para>However, some applications such as MySQL need to be have the @@ -593,43 +614,55 @@ </sect2> <sect2> - <title>Programming i18n Compliant Applications</title> + <title>Programming I18N Compliant Applications</title> <para>To make your application more useful for speakers of other - languages, we hope that you will program i18n compliant. The GNU - gcc compiler, GUI Libraries like QT and GTK support i18n through - special handling of strings. Making a program i18n compliant is + languages, we hope that you will program I18N compliant. The GNU + gcc compiler, GUI Libraries like QT and GTK support I18N through + special handling of strings. Making a program I18N compliant is very easy. It allows contributors to port your application to - other languages quickly. Refer to library specific i18n + other languages quickly. Refer to library specific I18N documentation for more details.</para> - <para>To the contrary of common perception, i18n compliant code is + <para>To the contrary of common perception, I18N compliant code is easy to write. Usually, it only involves wrapping your strings with library specific functions. In addition, please be sure to allow for wide or multibyte characters support.</para> <sect3> - <title>A Call to Unify the i18n effort</title> + <title>A Call to Unify the I18N effort</title> - <para>It has come to our attention that the individual i18n/l10n + <para>It has come to our attention that the individual I18N/L10N efforts for each country has been repeating each others' efforts. Many of us have been reinventing the wheel repeatedly and inefficiently. We hope that the various major groups in - i18n could congregate into a group effort similar to the Core + I18N could congregate into a group effort similar to the Core Team's responsibility.</para> - <para>Currently, we hope that, when you write or port i18n + <para>Currently, we hope that, when you write or port I18N programs, you would send it out to each country's related FreeBSD mailing lists for testing. In the future, we hope to create applications that work in all the languages out-of-the-box without dirty hacks.</para> + + <para>The mailing list <email>FreeBSD-I18N@FreeBSD.org</email> + has been established. If you are an I18N/L10N developer, + please send your comments, ideas, questions, and anything + you deem related to it. </para> + + <para> Michael C. Wu will be maintaining an I18N works in progress + homepage at <ulink + url="http://www.iteration.net/~keichii/i18n/index.html">http://www.iteration.net/~keichii/i18n/index.html</ulink>; + Please also read the BSDCon2000 I18N paper and presentations + by Clive Lin, Chia-Liang Kao, and Michael C. Wu at <ulink + url="http://www.ece.utexas.edu/~mwu/">http://www.ece.utexas.edu/~mwu<ulink><para>; </sect3> <sect3> <title>Perl and Python</title> - <para>Perl and Python have i18n and wide characters handling - libraries. Please use them for i18n compliance.</para> + <para>Perl and Python have I18N and wide characters handling + libraries. Please use them for I18N compliance.</para> <para>In older FreeBSD versions, Perl may gives warning about not having a wide characters locale @@ -852,10 +885,10 @@ <sect2> <title>Traditional Chinese Localization for Taiwan</title> - <para>The FreeBSD-Taiwan Project has an i18n/l10n tutorial for - FreeBSD at <ulink url="http://freebsd.sinica.edu.tw/~ncvs/zh-l10n-tut/index.html">http://freebsd.sinica.edu.tw/~ncvs/zh-l10n-tut/index.html</ulink>; + <para>The FreeBSD-Taiwan Project has an I18N/L10N tutorial for + FreeBSD at <ulink url="http://freebsd.sinica.edu.tw/~ncvs/zh-L10N-tut/index.html">http://freebsd.sinica.edu.tw/~ncvs/zh-l10n-tut/index.html</ulink>; using many <filename>/usr/ports/chinese/*</filename> applications. - The editor for the <literal>zh-l10n-tut</literal> is Clive Lin + The editor for the <literal>zh-L10N-tut</literal> is Clive Lin <email>Clive@CirX.org</email>. You can also cvsup the following collections at <hostid role="fqdn">freebsd.sinica.edu.tw</hostid>:</para> @@ -876,7 +909,7 @@ </row> <row> - <entry>zh-l10n-tut tag=.</entry> + <entry>zh-L10N-tut tag=.</entry> <entry>Localizing FreeBSD Tutorial in BIG-5 Traditional Chinese</entry> </row> @@ -893,7 +926,7 @@ <para>Chuan-Hsing Shen <email>s874070@mail.yzu.edu.tw</email> has created the <ulink url="http://cnpa.yzu.edu.tw/~cfc/">Chinese FreeBSD Collection (CFC)</ulink> using FreeBSD-Taiwan's - <literal>zh-l10n-tut</literal>. The packages and the script files + <literal>zh-L10N-tut</literal>. The packages and the script files are available at <ulink url="ftp://ftp.csie.ncu.edu.tw/OS/FreeBSD/taiwan/CFC/">ftp://ftp.csie.ncu.edu.tw/OS/FreeBSD/taiwan/CFC/</ulink>.</para>; </sect2> --wac7ysb48OaltWcw-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001130163257.A20217>