View | Details | Raw Unified | Return to bug 34966
Collapse All | Expand All

(-)doc/en_US.ISO8859-1/books/developers-handbook/l10n/chapter.sgml (-9 / +9 lines)
Lines 5-11 Link Here
5
-->
5
-->
6
6
7
  <chapter id="l10n">
7
  <chapter id="l10n">
8
    <title>Localization - I18N</title>
8
    <title>Localization and Internationalization - L10N and I18N</title>
9
9
10
    <sect1>
10
    <sect1>
11
      <title>Programming I18N Compliant Applications</title>
11
      <title>Programming I18N Compliant Applications</title>
Lines 13-28 Link Here
13
      <indexterm><primary>GTK</primary></indexterm>
13
      <indexterm><primary>GTK</primary></indexterm>
14
      <para>To make your application more useful for speakers of other
14
      <para>To make your application more useful for speakers of other
15
	languages, we hope that you will program I18N compliant.  The GNU
15
	languages, we hope that you will program I18N compliant.  The GNU
16
	gcc compiler, GUI Libraries like QT and GTK support I18N through
16
	gcc compiler and GUI libraries like QT and GTK support I18N through
17
	special handling of strings.  Making a program I18N compliant is
17
	special handling of strings.  Making a program I18N compliant is
18
	very easy.  It allows contributors to port your application to
18
	very easy.  It allows contributors to port your application to
19
	other languages quickly.  Refer to library specific I18N
19
	other languages quickly.  Refer to the library specific I18N
20
	documentation for more details.</para>
20
	documentation for more details.</para>
21
21
22
      <para>To the contrary of common perception, I18N compliant code is
22
      <para>In contrast with common perception, I18N compliant code is
23
	easy to write.  Usually, it only involves wrapping your strings
23
	easy to write.  Usually, it only involves wrapping your strings
24
	with library specific functions.  In addition, please be sure to
24
	with library specific functions.  In addition, please be sure to
25
	allow for wide or multibyte characters support.</para>
25
	allow for wide or multibyte character support.</para>
26
26
27
      <sect2>
27
      <sect2>
28
	<title>A Call to Unify the I18N Effort</title>
28
	<title>A Call to Unify the I18N Effort</title>
Lines 36-42 Link Here
36
36
37
	<para>Currently, we hope that, when you write or port I18N
37
	<para>Currently, we hope that, when you write or port I18N
38
	  programs, you would send it out to each country's related
38
	  programs, you would send it out to each country's related
39
	  FreeBSD mailing lists for testing.  In the future, we hope to
39
	  FreeBSD mailing list for testing.  In the future, we hope to
40
	  create applications that work in all the languages
40
	  create applications that work in all the languages
41
	  out-of-the-box without dirty hacks.</para>
41
	  out-of-the-box without dirty hacks.</para>
42
42
Lines 62-73 Link Here
62
          <primary>Python</primary>
62
          <primary>Python</primary>
63
        </indexterm>
63
        </indexterm>
64
64
65
	<para>Perl and Python have I18N and wide characters handling
65
	<para>Perl and Python have I18N and wide character handling
66
	  libraries.  Please use them for I18N compliance.</para>
66
	  libraries.  Please use them for I18N compliance.</para>
67
67
68
	<para>In older FreeBSD versions,
68
	<para>In older FreeBSD versions,
69
	  Perl may gives warning about not having a wide characters locale
69
	  Perl may give warnings about not having a wide character locale
70
	  that is already installed in your system.  You can set the
70
	  installed on your system.  You can set the
71
	  environmental variable <envar>LD_PRELOAD</envar> to
71
	  environmental variable <envar>LD_PRELOAD</envar> to
72
	  <filename>/usr/lib/libxpg4.so</filename> in your shell.</para>
72
	  <filename>/usr/lib/libxpg4.so</filename> in your shell.</para>

Return to bug 34966