doc/ref/i18n.xml


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71

<refentry id="refi18n">

  <refmeta>
    <refentrytitle>ne_i18n_init</refentrytitle>
    <manvolnum>3</manvolnum>
  </refmeta>

  <refnamediv>
    <refname id="ne_i18n_init">ne_i18n_init</refname>
    <refpurpose>functions to initialize internationalization support</refpurpose>
  </refnamediv>
  
  <refsynopsisdiv>

    <funcsynopsis>

      <funcsynopsisinfo>#include &lt;ne_i18n.h&gt;</funcsynopsisinfo>

      <funcprototype>
        <funcdef>void <function>ne_i18n_init</function></funcdef>
        <paramdef>const char *<parameter>encoding</parameter></paramdef>
      </funcprototype>

    </funcsynopsis>

  </refsynopsisdiv>

  <refsect1>
    <title>Description</title>

    <para>The <function>ne_i18n_init</function> function can be used
    to enable support for translated messages in the &neon; library.
    The <parameter>encoding</parameter> parameter, if non-&null;,
    specifies the character encoding required for generated translated
    string.  If it is &null;, the appropriate character encoding for
    the process locale will be used.</para>

    <para>This call is only strictly necessary if either:

    <orderedlist numeration="loweralpha">
        
      <listitem><simpara>&neon; has been installed into a different
      prefix than the <literal>gettext</literal> implementation on
      which it depends for i18n purposes, or</simpara></listitem>

      <listitem><simpara>the caller requires that translated messages
      are in a particular character encoding.</simpara></listitem>

    </orderedlist></para>

    <para>If <function>ne_i18n_init</function> is never called, the
    message catalogs will not be found if case (a) applies (and so
    English error messages will be used), and will use the default
    character encoding specified by the process locale.  The library
    will otherwise operate correctly.</para>

    <para>Note that the encoding used is a process-global setting and
    so results may be unexpected if other users of &neon; within the
    process call <function>ne_i18n_init</function> with a different
    encoding parameter.</para>

  </refsect1>

  <refsect1>
    <title>See also</title>

    <para><xref linkend="ne_sock_init"/></para>
  </refsect1>

</refentry>