Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

ne_i18n_init(3) [suse man page]

NE_I18N_INIT(3) 						neon API reference						   NE_I18N_INIT(3)

NAME
ne_i18n_init - functions to initialize internationalization support SYNOPSIS
#include <ne_i18n.h> void ne_i18n_init(const char *encoding); DESCRIPTION
The ne_i18n_init function can be used to enable support for translated messages in the neon library. The encoding 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. This call is only strictly necessary if either: 1. neon has been installed into a different prefix than the gettext implementation on which it depends for i18n purposes, or 2. the caller requires that translated messages are in a particular character encoding. If ne_i18n_init 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. 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 ne_i18n_init with a different encoding parameter. SEE ALSO
ne_sock_init AUTHOR
Joe Orton <neon@lists.manyfish.co.uk> Author. COPYRIGHT
neon 0.28.4 25 February 2009 NE_I18N_INIT(3)

Check Out this Related Man Page

NE_I18N_INIT(3) 						neon API reference						   NE_I18N_INIT(3)

NAME
ne_i18n_init - functions to initialize internationalization support SYNOPSIS
#include <ne_i18n.h> void ne_i18n_init(const char *encoding); DESCRIPTION
The ne_i18n_init function can be used to enable support for translated messages in the neon library. The encoding 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. This call is only strictly necessary if either: 1. neon has been installed into a different prefix than the gettext implementation on which it depends for i18n purposes, or 2. the caller requires that translated messages are in a particular character encoding. If ne_i18n_init 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. 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 ne_i18n_init with a different encoding parameter. SEE ALSO
ne_sock_init AUTHOR
Joe Orton <neon@lists.manyfish.co.uk> Author. COPYRIGHT
neon 0.30.0 31 July 2013 NE_I18N_INIT(3)
Man Page

3 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Install neon-0.26.3. on a OpenBSD server

Hello, I'm a very basic beginning user of OpenBSD. I'd like to install neon-0.26.3. I placed it on our server but I don't know how to install it. The directory has the following contain: # ls .package AUTHORS ChangeLog.CVS NEWS TODO ... (1 Reply)
Discussion started by: syddy
1 Replies

2. UNIX for Dummies Questions & Answers

character encoding in Fedora6

Hello, After upgrading the OS from Fedora4 to Fedora6, the firefox view>character encoding doesn't work anymore. None of the foreign characters can be displayed, no matter what character encoding to select. Any suggestions? Thanks, bsky :confused (1 Reply)
Discussion started by: bsky
1 Replies

3. HP-UX

how to find the character encoding of a file in hp_ux

how to find the character encoding of a file in hp_ux (1 Reply)
Discussion started by: alokjyotibal
1 Replies