Pure perl implementation of uniforum message translation
use Locale::gettext_pp (:locale_h :libintl_h); gettext $msgid; dgettext $domainname, $msgid; dcgettext $domainname, $msgid, LC_MESSAGES; ngettext $msgid, $msgid_plural, $count; dngettext $domainname, $msgid, $msgid_plural, $count; dcngettext $domainname, $msgid, $msgid_plural, $count, LC_MESSAGES; pgettext $msgctxt, $msgid; dpgettext $domainname, $msgctxt, $msgid; dcpgettext $domainname, $msgctxt, $msgid, LC_MESSAGES; npgettext $msgctxt, $msgid, $msgid_plural, $count; dnpgettext $domainname, $msgctxt, $msgid, $msgid_plural, $count; dcnpgettext $domainname, $msgctxt, $msgid, $msgid_plural, $count, LC_MESSAGES; textdomain $domainname; bindtextdomain $domainname, $directory; bind_textdomain_codeset $domainname, $encoding; my $category = LC_CTYPE; my $category = LC_NUMERIC; my $category = LC_TIME; my $category = LC_COLLATE; my $category = LC_MONETARY; my $category = LC_MESSAGES; my $category = LC_ALL;
The module Locale::gettext_pp is the low-level interface to message translation according to the Uniforum approach that is for example used in \s-1GNU\s0 gettext and Sun's Solaris.
Normally you should not use this module directly, but the high level interface Locale::TextDomain\|(3) that provides a much simpler interface. This description is therefore deliberately kept brief. Please refer to the \s-1GNU\s0 gettext documentation available at <http://www.gnu.org/manual/gettext/> for in-depth and background information on the topic.
The module exports by default nothing. Every function has to be imported explicitely or via an export tag (\*(L"\s-1EXPORT\s0 \s-1TAGS\s0\*(R").
See \*(L"\s-1FUNCTIONS\s0\*(R" in Locale::Messages.
See \*(L"\s-1FUNCTIONS\s0\*(R" in Locale::Messages.
See \*(L"\s-1FUNCTIONS\s0\*(R" in Locale::Messages.
See \*(L"\s-1FUNCTIONS\s0\*(R" in Locale::Messages.
See \*(L"\s-1FUNCTIONS\s0\*(R" in Locale::Messages.
See \*(L"\s-1FUNCTIONS\s0\*(R" in Locale::Messages.
See \*(L"\s-1FUNCTIONS\s0\*(R" in Locale::Messages.
See \*(L"\s-1FUNCTIONS\s0\*(R" in Locale::Messages.
See \*(L"\s-1FUNCTIONS\s0\*(R" in Locale::Messages.
See \*(L"\s-1FUNCTIONS\s0\*(R" in Locale::Messages.
See \*(L"\s-1FUNCTIONS\s0\*(R" in Locale::Messages.
See \*(L"\s-1FUNCTIONS\s0\*(R" in Locale::Messages.
See \*(L"\s-1FUNCTIONS\s0\*(R" in Locale::Messages.
See \*(L"\s-1FUNCTIONS\s0\*(R" in Locale::Messages.
See \*(L"\s-1FUNCTIONS\s0\*(R" in Locale::Messages.
You can (maybe) get the same constants from \s-1POSIX\s0\|(3); see there for a detailed description
See \*(L"\s-1CONSTANTS\s0\*(R" in Locale::Messages for more information.
This module does not export anything unless explicitely requested. You can import groups of functions via two tags:
Imports the functions that are normally defined in the C include file locale.h:
Introduced with libintl-perl 1.17.
Introduced with libintl-perl 1.17.
Introduced with libintl-perl 1.17.
Introduced with libintl-perl 1.17.
Introduced with libintl-perl 1.17.
Introduced with libintl-perl 1.17.
Imports the locale category constants:
Copyright (C) 2002-2013, Guido Flohr <[email protected]>, all rights reserved. See the source code for details.
This software is contributed to the Perl community by Imperia (<http://www.imperia.net/>).
Locale::TextDomain\|(3pm), Locale::Messages\|(3pm), Encode\|(3pm), perllocale\|(3pm), \s-1POSIX\s0\|(3pm), perl\|(1), gettext\|(1), gettext\|(3)
Hey! The above document had some coding errors, which are explained below:
=cut found outside a pod block. Skipping to next block.