Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

runidn(1) [suse man page]

RUNIDN(1)						      General Commands Manual							 RUNIDN(1)

NAME
runidn - A script to allow applications to use internationalized domain names. SYNOPSIS
runidn [-e local-codeset] program-name [args..] DESCRIPTION
runidn enables applications to use internationalized domain names without recompilation. Just add ``runidn'' before the application-name, and the application can handle non-ASCII domain names. For example, you can do: % runidn telnet non-ASCII-hostname Before using runidn, you should set up properties related to internationalized DNS by configuring idnkit's configuration file idn.conf. See idn.conf(5) which describes the configuration. OPTION
The following option is available: -e local-codeset Specify the application's local codeset. If the option is not specified, runidn guesses the codeset from the current locale. See the ``NOTE'' section for more details about local codeset. IMPLEMENTATION
runidn is a small shell script that sets up an environment variable called ``LD_PRELOAD'', so that an application dynamically links a shared library ``libidnkitres'' before any other shared libraries. The library ``libidnkitres'' provides a special version of resolver functions which implement features for handling internationalized domain names. runidn replaces the following functions with the special version: gethostbyname gethostbyname2 gethostbyaddr gethostbyname_r gethostbyname2_r gethostbyaddr_r getipnodebyname getipnodebyaddr freehostent getaddrinfo freeaddrinfo getnameinfo By overriding them in the standard libraries with the special version provided by ``libidnkitres'', runidn enables applications to use internationalized domain names. o These API functions accept non-ASCII domain names encoded in the local codeset that the application is using. Also the result from these APIs may contain non-ASCII domain names. o The normalization and codeset conversion between application's local codeset and the codeset used in DNS protocol data are handled automatically, so users/applications need not worry about them. Properties of internationalized DNS (such as the normalization or the codeset used on DNS protocol data) can be configured with the idnkit's configuration file (idn.conf). See idn.conf(5) for details. NOTE
Unless -e option is specified, runidn tries to guess the application's local codeset from the application's current locale. However, some- times it cannot guess the codeset correctly, for example if the application does not set the locale appropriately by calling `setlocale()'. In that case, you can explicitly specify the local codeset by setting an environment variable ``IDN_LOCAL_CODESET''. See the section ``LOCAL CODESET'' in idn.conf(5) for details. The idea of using ``LD_PRELOAD'' to replace some functions in the standard library was taken from ``runsocks'' script distributed as part of SOCKS5 reference implementation. BUGS
There are many cases where runidn does not work. Your system must support ``LD_PRELOAD'' mechanism in the first place. Due to security reasons, ``LD_PRELOAD'' mechanism is disabled for setuid programs in any sane systems. So runidn does not work for setuid programs such as ping or rsh. If your application uses a function other than the ones runidn supports for name resolution, you lose. SEE ALSO
idn.conf(5), runsocks(1) April 6, 2001 RUNIDN(1)

Check Out this Related Man Page

BIND_TEXTDOMAIN_CODESET(3)				     Library Functions Manual					BIND_TEXTDOMAIN_CODESET(3)

NAME
bind_textdomain_codeset - set encoding of message translations SYNOPSIS
#include <libintl.h> char * bind_textdomain_codeset (const char * domainname, const char * codeset); DESCRIPTION
The bind_textdomain_codeset function sets the output codeset for message catalogs for domain domainname. A message domain is a set of translatable msgid messages. Usually, every software package has its own message domain. By default, the gettext family of functions returns translated messages in the locale's character encoding, which can be retrieved as nl_langinfo(CODESET). The need for calling bind_textdomain_codeset arises for programs which store strings in a locale independent way (e.g. UTF-8) and want to avoid an extra character set conversion on the returned translated messages. domainname must be a non-empty string. If codeset is not NULL, it must be a valid encoding name which can be used for the iconv_open function. The bind_textdomain_codeset func- tion sets the output codeset for message catalogs belonging to domain domainname to codeset. The function makes copies of the argument strings as needed. If codeset is NULL, the function returns the previously set codeset for domain domainname. The default is NULL, denoting the locale's char- acter encoding. RETURN VALUE
If successful, the bind_textdomain_codeset function returns the current codeset for domain domainname, after possibly changing it. The resulting string is valid until the next bind_textdomain_codeset call for the same domainname and must not be modified or freed. If a mem- ory allocation failure occurs, it sets errno to ENOMEM and returns NULL. If no codeset has been set for domain domainname, it returns NULL. ERRORS
The following error can occur, among others: ENOMEM Not enough memory available. BUGS
The return type ought to be const char *, but is char * to avoid warnings in C code predating ANSI C. SEE ALSO
gettext(3), dgettext(3), dcgettext(3), ngettext(3), dngettext(3), dcngettext(3), textdomain(3), nl_langinfo(3), iconv_open(3) GNU gettext 0.18.1 May 2001 BIND_TEXTDOMAIN_CODESET(3)
Man Page