diff options
| author | Bruno Haible <bruno@clisp.org> | 2002-07-17 16:35:30 +0000 |
|---|---|---|
| committer | Bruno Haible <bruno@clisp.org> | 2009-06-23 12:08:39 +0200 |
| commit | 02849a533b6a0490df05088c0b3ef5c24fc52ff5 (patch) | |
| tree | 39fc4b050d37aa328fbbcb7fb82cf622b6233dac /doc/gettext_10.html | |
| parent | 640b0799175f3e7f5d0f74d40763c44b2bb025aa (diff) | |
| download | external_gettext-02849a533b6a0490df05088c0b3ef5c24fc52ff5.zip external_gettext-02849a533b6a0490df05088c0b3ef5c24fc52ff5.tar.gz external_gettext-02849a533b6a0490df05088c0b3ef5c24fc52ff5.tar.bz2 | |
Update for 0.11.3.
Diffstat (limited to 'doc/gettext_10.html')
| -rw-r--r-- | doc/gettext_10.html | 64 |
1 files changed, 32 insertions, 32 deletions
diff --git a/doc/gettext_10.html b/doc/gettext_10.html index 09949bb..f0b8d92 100644 --- a/doc/gettext_10.html +++ b/doc/gettext_10.html @@ -1,7 +1,7 @@ <HTML> <HEAD> <!-- This HTML file has been created by texi2html 1.52a - from gettext.texi on 24 April 2002 --> + from gettext.texi on 16 July 2002 --> <TITLE>GNU gettext utilities - 10 The Programmer's View</TITLE> </HEAD> @@ -30,7 +30,7 @@ later explain our solution of this dilemma. <H2><A NAME="SEC142" HREF="gettext_toc.html#TOC142">10.1 About <CODE>catgets</CODE></A></H2> <P> -<A NAME="IDX820"></A> +<A NAME="IDX821"></A> </P> <P> @@ -65,7 +65,7 @@ therefore part of all Unix implementation (implementations, which are <H3><A NAME="SEC143" HREF="gettext_toc.html#TOC143">10.1.1 The Interface</A></H3> <P> -<A NAME="IDX821"></A> +<A NAME="IDX822"></A> </P> <P> @@ -78,7 +78,7 @@ for the functions and the needed definitions are in the </P> <P> -<A NAME="IDX822"></A> +<A NAME="IDX823"></A> <CODE>catopen</CODE> is used like in this: </P> @@ -97,7 +97,7 @@ message catalog, equivalent to handles to file returned by <CODE>open</CODE>. </P> <P> -<A NAME="IDX823"></A> +<A NAME="IDX824"></A> This handle is of course used in the <CODE>catgets</CODE> function which can be used like this: @@ -129,7 +129,7 @@ should better be <CODE>const char *</CODE>, but the standard is published in </P> <P> -<A NAME="IDX824"></A> +<A NAME="IDX825"></A> The last of these function functions is used and behaves as expected: </P> @@ -146,7 +146,7 @@ After this no <CODE>catgets</CODE> call using the descriptor is legal anymore. <H3><A NAME="SEC144" HREF="gettext_toc.html#TOC144">10.1.2 Problems with the <CODE>catgets</CODE> Interface?!</A></H3> <P> -<A NAME="IDX825"></A> +<A NAME="IDX826"></A> </P> <P> @@ -167,7 +167,7 @@ more easy to manage. <H2><A NAME="SEC145" HREF="gettext_toc.html#TOC145">10.2 About <CODE>gettext</CODE></A></H2> <P> -<A NAME="IDX826"></A> +<A NAME="IDX827"></A> </P> <P> @@ -198,7 +198,7 @@ in using this library will be interested in this description. <H3><A NAME="SEC146" HREF="gettext_toc.html#TOC146">10.2.1 The Interface</A></H3> <P> -<A NAME="IDX827"></A> +<A NAME="IDX828"></A> </P> <P> @@ -269,9 +269,9 @@ your language. <H3><A NAME="SEC147" HREF="gettext_toc.html#TOC147">10.2.2 Solving Ambiguities</A></H3> <P> -<A NAME="IDX828"></A> <A NAME="IDX829"></A> <A NAME="IDX830"></A> +<A NAME="IDX831"></A> </P> <P> @@ -347,7 +347,7 @@ unreliabilities. <H3><A NAME="SEC148" HREF="gettext_toc.html#TOC148">10.2.3 Locating Message Catalog Files</A></H3> <P> -<A NAME="IDX831"></A> +<A NAME="IDX832"></A> </P> <P> @@ -387,8 +387,8 @@ The value of the locale is determined through <H3><A NAME="SEC149" HREF="gettext_toc.html#TOC149">10.2.4 How to specify the output character set <CODE>gettext</CODE> uses</A></H3> <P> -<A NAME="IDX832"></A> <A NAME="IDX833"></A> +<A NAME="IDX834"></A> </P> <P> @@ -420,7 +420,7 @@ recommended that all <VAR>msgid</VAR>s be US-ASCII strings. <P> <DL> <DT><U>Function:</U> char * <B>bind_textdomain_codeset</B> <I>(const char *<VAR>domainname</VAR>, const char *<VAR>codeset</VAR>)</I> -<DD><A NAME="IDX834"></A> +<DD><A NAME="IDX835"></A> The <CODE>bind_textdomain_codeset</CODE> function can be used to specify the output character set for message catalogs for domain <VAR>domainname</VAR>. The <VAR>codeset</VAR> argument must be a valid codeset name which can be used @@ -454,7 +454,7 @@ global variable <VAR>errno</VAR> is set accordingly. <H3><A NAME="SEC150" HREF="gettext_toc.html#TOC150">10.2.5 Additional functions for plural forms</A></H3> <P> -<A NAME="IDX835"></A> +<A NAME="IDX836"></A> </P> <P> @@ -574,7 +574,7 @@ purpose. <P> <DL> <DT><U>Function:</U> char * <B>ngettext</B> <I>(const char *<VAR>msgid1</VAR>, const char *<VAR>msgid2</VAR>, unsigned long int <VAR>n</VAR>)</I> -<DD><A NAME="IDX836"></A> +<DD><A NAME="IDX837"></A> The <CODE>ngettext</CODE> function is similar to the <CODE>gettext</CODE> function as it finds the message catalogs in the same way. But it takes two extra arguments. The <VAR>msgid1</VAR> parameter must contain the singular @@ -604,7 +604,7 @@ Please note that the numeric value <VAR>n</VAR> has to be passed to the <P> <DL> <DT><U>Function:</U> char * <B>dngettext</B> <I>(const char *<VAR>domain</VAR>, const char *<VAR>msgid1</VAR>, const char *<VAR>msgid2</VAR>, unsigned long int <VAR>n</VAR>)</I> -<DD><A NAME="IDX837"></A> +<DD><A NAME="IDX838"></A> The <CODE>dngettext</CODE> is similar to the <CODE>dgettext</CODE> function in the way the message catalog is selected. The difference is that it takes two extra parameter to provide the correct plural form. These two @@ -615,7 +615,7 @@ parameters are handled in the same way <CODE>ngettext</CODE> handles them. <P> <DL> <DT><U>Function:</U> char * <B>dcngettext</B> <I>(const char *<VAR>domain</VAR>, const char *<VAR>msgid1</VAR>, const char *<VAR>msgid2</VAR>, unsigned long int <VAR>n</VAR>, int <VAR>category</VAR>)</I> -<DD><A NAME="IDX838"></A> +<DD><A NAME="IDX839"></A> The <CODE>dcngettext</CODE> is similar to the <CODE>dcgettext</CODE> function in the way the message catalog is selected. The difference is that it takes two extra parameter to provide the correct plural form. These two @@ -640,9 +640,9 @@ possibility of extensions to not prevent the use of new languages). </P> <P> -<A NAME="IDX839"></A> <A NAME="IDX840"></A> <A NAME="IDX841"></A> +<A NAME="IDX842"></A> The information about the plural form selection has to be stored in the header entry of the PO file (the one with the empty <CODE>msgid</CODE> string). The plural form information looks like this: @@ -668,7 +668,7 @@ value of <CODE>nplurals</CODE>. </P> <P> -<A NAME="IDX842"></A> +<A NAME="IDX843"></A> The following rules are known at this point. The language with families are listed. But this does not necessarily mean the information can be generalized for the whole family (as can be easily seen in the table @@ -878,9 +878,9 @@ Slovenian <H3><A NAME="SEC151" HREF="gettext_toc.html#TOC151">10.2.6 How to use <CODE>gettext</CODE> in GUI programs</A></H3> <P> -<A NAME="IDX843"></A> <A NAME="IDX844"></A> <A NAME="IDX845"></A> +<A NAME="IDX846"></A> </P> <P> @@ -957,7 +957,7 @@ fine: </P> <P> -<A NAME="IDX846"></A> +<A NAME="IDX847"></A> <PRE> char * @@ -1034,7 +1034,7 @@ quite some memory and disk space by doing this. <H3><A NAME="SEC152" HREF="gettext_toc.html#TOC152">10.2.7 Optimization of the *gettext functions</A></H3> <P> -<A NAME="IDX847"></A> +<A NAME="IDX848"></A> </P> <P> @@ -1089,8 +1089,8 @@ find the result through a single cache lookup. <H2><A NAME="SEC153" HREF="gettext_toc.html#TOC153">10.3 Comparing the Two Interfaces</A></H2> <P> -<A NAME="IDX848"></A> <A NAME="IDX849"></A> +<A NAME="IDX850"></A> </P> @@ -1140,7 +1140,7 @@ by </P> <P> -<A NAME="IDX850"></A> +<A NAME="IDX851"></A> <PRE> #include <libintl.h> @@ -1155,7 +1155,7 @@ can use any that becomes available. </P> <P> -<A NAME="IDX851"></A> +<A NAME="IDX852"></A> The same procedure can be done for the <CODE>gettext_noop</CODE> invocations (see section <A HREF="gettext_3.html#SEC19">3.6 Special Cases of Translatable Strings</A>). One usually defines <CODE>gettext_noop</CODE> as a no-op macro. So you should consider the following code for your project: @@ -1263,7 +1263,7 @@ is a list comments: <UL> <LI>Changing the language at runtime -<A NAME="IDX852"></A> +<A NAME="IDX853"></A> For interactive programs it might be useful to offer a selection of the used language at runtime. To understand how to do this one need to know @@ -1280,20 +1280,20 @@ priority: <OL> <LI><CODE>LANGUAGE</CODE> -<A NAME="IDX853"></A> - <A NAME="IDX854"></A> + +<A NAME="IDX855"></A> <LI><CODE>LC_ALL</CODE> -<A NAME="IDX855"></A> <A NAME="IDX856"></A> <A NAME="IDX857"></A> <A NAME="IDX858"></A> <A NAME="IDX859"></A> <A NAME="IDX860"></A> +<A NAME="IDX861"></A> <LI><CODE>LC_xxx</CODE>, according to selected locale -<A NAME="IDX861"></A> +<A NAME="IDX862"></A> <LI><CODE>LANG</CODE> </OL> @@ -1301,7 +1301,7 @@ priority: Afterwards the path is constructed using the found value and the translation file is loaded if available. -What is now when the value for, say, <CODE>LANGUAGE</CODE> changes. According +What happens now when the value for, say, <CODE>LANGUAGE</CODE> changes? According to the process explained above the new value of this variable is found as soon as the <CODE>dcgettext</CODE> function is called. But this also means the (perhaps) different message catalog file is loaded. In other @@ -1327,7 +1327,7 @@ language switching function. } </PRE> -<A NAME="IDX862"></A> +<A NAME="IDX863"></A> The variable <CODE>_nl_msg_cat_cntr</CODE> is defined in <TT>`loadmsgcat.c´</TT>. You don't need to know what this is for. But it can be used to detect whether a <CODE>gettext</CODE> implementation is GNU gettext and not non-GNU |