locale::maketext::tpj13.3

视频监控网络部分的协议ddns,的模块的实现代码,请大家大胆指正.

.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
.de Sh \" Subsection heading
.br
.if t .Sp
.ne 5
.PP
\fB\\$1\fR
.PP
..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
..
.de Vb \" Begin verbatim text
.ft CW
.nf
.ne \\$1
..
.de Ve \" End verbatim text
.ft R
.fi
..
.\" Set up some character translations and predefined strings.  \*(-- will
.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
.\" double quote, and \*(R" will give a right double quote.  \*(C+ will
.\" give a nicer C++.  Capital omega is used to do unbreakable dashes and
.\" therefore won't be available.  \*(C` and \*(C' expand to `' in nroff,
.\" nothing in troff, for use with C<>.
.tr \(*W-
.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
.ie n \{\
.    ds -- \(*W-
.    ds PI pi
.    if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
.    if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\"  diablo 12 pitch
.    ds L" ""
.    ds R" ""
.    ds C` ""
.    ds C' ""
'br\}
.el\{\
.    ds -- \|\(em\|
.    ds PI \(*p
.    ds L" ``
.    ds R" ''
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD.  Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.ie \nF \{\
.    de IX
.    tm Index:\\$1\t\\n%\t"\\$2"
..
.    nr % 0
.    rr F
.\}
.el \{\
.    de IX
..
.\}
.\"
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear.  Run.  Save yourself.  No user-serviceable parts.
.    \" fudge factors for nroff and troff
.if n \{\
.    ds #H 0
.    ds #V .8m
.    ds #F .3m
.    ds #[ \f1
.    ds #] \fP
.\}
.if t \{\
.    ds #H ((1u-(\\\\n(.fu%2u))*.13m)
.    ds #V .6m
.    ds #F 0
.    ds #[ \&
.    ds #] \&
.\}
.    \" simple accents for nroff and troff
.if n \{\
.    ds ' \&
.    ds ` \&
.    ds ^ \&
.    ds , \&
.    ds ~ ~
.    ds /
.\}
.if t \{\
.    ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
.    ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
.    ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
.    ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
.    ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
.    ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
.\}
.    \" troff and (daisy-wheel) nroff accents
.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
.ds 8 \h'\*(#H'\(*b\h'-\*(#H'
.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
.ds ae a\h'-(\w'a'u*4/10)'e
.ds Ae A\h'-(\w'A'u*4/10)'E
.    \" corrections for vroff
.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
.    \" for low resolution devices (crt and lpr)
.if \n(.H>23 .if \n(.V>19 \
\{\
.    ds : e
.    ds 8 ss
.    ds o a
.    ds d- d\h'-1'\(ga
.    ds D- D\h'-1'\(hy
.    ds th \o'bp'
.    ds Th \o'LP'
.    ds ae ae
.    ds Ae AE
.\}
.rm #[ #] #H #V #F C
.\" ========================================================================
.\"
.IX Title "Locale::Maketext::TPJ13 3"
.TH Locale::Maketext::TPJ13 3 "2007-12-18" "perl v5.10.0" "Perl Programmers Reference Guide"
.\" For nroff, turn off justification.  Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.nh
.SH "NAME"
Locale::Maketext::TPJ13 \-\- article about software localization
.SH "SYNOPSIS"
.IX Header "SYNOPSIS"
.Vb 1
\&  # This an article, not a module.
.Ve
.SH "DESCRIPTION"
.IX Header "DESCRIPTION"
The following article by Sean M. Burke and Jordan Lachler
first appeared in \fIThe Perl Journal\fR #13
and is copyright 1999 The Perl Journal. It appears
courtesy of Jon Orwant and The Perl Journal.  This document may be
distributed under the same terms as Perl itself.
.SH "Localization and Perl: gettext breaks, Maketext fixes"
.IX Header "Localization and Perl: gettext breaks, Maketext fixes"
by Sean M. Burke and Jordan Lachler
.PP
This article points out cases where gettext (a common system for
localizing software interfaces \*(-- i.e., making them work in the user's
language of choice) fails because of basic differences between human
languages.  This article then describes Maketext, a new system capable
of correctly treating these differences.
.Sh "A Localization Horror Story: It Could Happen To You"
.IX Subsection "A Localization Horror Story: It Could Happen To You"
.RS 4
\&\*(L"There are a number of languages spoken by human beings in this
world.\*(R"
.Sp
\&\-\- Harald Tveit Alvestrand, in \s-1RFC\s0 1766, \*(L"Tags for the
Identification of Languages\*(R"
.RE
.PP
Imagine that your task for the day is to localize a piece of software
\&\*(-- and luckily for you, the only output the program emits is two
messages, like this:
.PP
.Vb 1
\&  I scanned 12 directories.
\&
\&  Your query matched 10 files in 4 directories.
.Ve
.PP
So how hard could that be?  You look at the code that
produces the first item, and it reads:
.PP
.Vb 2
\&  printf("I scanned %g directories.",
\&         $directory_count);
.Ve
.PP
You think about that, and realize that it doesn't even work right for
English, as it can produce this output:
.PP
.Vb 1
\&  I scanned 1 directories.
.Ve
.PP
So you rewrite it to read:
.PP
.Vb 5
\&  printf("I scanned %g %s.",
\&         $directory_count,
\&         $directory_count == 1 ?
\&           "directory" : "directories",
\&  );
.Ve
.PP
\&...which does the Right Thing.  (In case you don't recall, \*(L"%g\*(R" is for
locale-specific number interpolation, and \*(L"%s\*(R" is for string
interpolation.)
.PP
But you still have to localize it for all the languages you're
producing this software for, so you pull Locale::gettext off of \s-1CPAN\s0
so you can access the \f(CW\*(C`gettext\*(C'\fR C functions you've heard are standard
for localization tasks.
.PP
And you write:
.PP
.Vb 5
\&  printf(gettext("I scanned %g %s."),
\&         $dir_scan_count,
\&         $dir_scan_count == 1 ?
\&           gettext("directory") : gettext("directories"),
\&  );
.Ve
.PP
But you then read in the gettext manual (Drepper, Miller, and Pinard 1995)
that this is not a good idea, since how a single word like \*(L"directory\*(R"
or \*(L"directories\*(R" is translated may depend on context \*(-- and this is
true, since in a case language like German or Russian, you'd may need
these words with a different case ending in the first instance (where the
word is the object of a verb) than in the second instance, which you haven't even
gotten to yet (where the word is the object of a preposition, \*(L"in \f(CW%g\fR
directories\*(R") \*(-- assuming these keep the same syntax when translated
into those languages.
.PP
So, on the advice of the gettext manual, you rewrite:
.PP
.Vb 4
\&  printf( $dir_scan_count == 1 ?
\&           gettext("I scanned %g directory.") :
\&           gettext("I scanned %g directories."),
\&         $dir_scan_count );
.Ve
.PP
So, you email your various translators (the boss decides that the
languages du jour are Chinese, Arabic, Russian, and Italian, so you
have one translator for each), asking for translations for \*(L"I scanned
\&\f(CW%g\fR directory.\*(R" and \*(L"I scanned \f(CW%g\fR directories.\*(R".  When they reply,
you'll put that in the lexicons for gettext to use when it localizes
your software, so that when the user is running under the \*(L"zh\*(R"
(Chinese) locale, gettext(\*(L"I scanned \f(CW%g\fR directory.\*(R") will return the
appropriate Chinese text, with a \*(L"%g\*(R" in there where printf can then
interpolate \f(CW$dir_scan\fR.
.PP
Your Chinese translator emails right back \*(-- he says both of these
phrases translate to the same thing in Chinese, because, in linguistic
jargon, Chinese \*(L"doesn't have number as a grammatical category\*(R" \*(--
whereas English does.  That is, English has grammatical rules that
refer to \*(L"number\*(R", i.e., whether something is grammatically singular
or plural; and one of these rules is the one that forces nouns to take
a plural suffix (generally \*(L"s\*(R") when in a plural context, as they are when
they follow a number other than \*(L"one\*(R" (including, oddly enough, \*(L"zero\*(R").
Chinese has no such rules, and so has just the one phrase where English
has two.  But, no problem, you can have this one Chinese phrase appear
as the translation for the two English phrases in the \*(L"zh\*(R" gettext
lexicon for your program.
.PP
Emboldened by this, you dive into the second phrase that your software
needs to output: \*(L"Your query matched 10 files in 4 directories.\*(R".  You notice
that if you want to treat phrases as indivisible, as the gettext
manual wisely advises, you need four cases now, instead of two, to
cover the permutations of singular and plural on the two items,
\&\f(CW$dir_count\fR and \f(CW$file_count\fR.  So you try this:
.PP
.Vb 9
\&  printf( $file_count == 1 ?
\&    ( $directory_count == 1 ?
\&     gettext("Your query matched %g file in %g directory.") :
\&     gettext("Your query matched %g file in %g directories.") ) :
\&    ( $directory_count == 1 ?
\&     gettext("Your query matched %g files in %g directory.") :
\&     gettext("Your query matched %g files in %g directories.") ),
\&   $file_count, $directory_count,
\&  );
.Ve
.PP
(The case of \*(L"1 file in 2 [or more] directories\*(R" could, I suppose,
occur in the case of symlinking or something of the sort.)
.PP
It occurs to you that this is not the prettiest code you've ever
written, but this seems the way to go.  You mail off to the
translators asking for translations for these four cases.  The
Chinese guy replies with the one phrase that these all translate to in
Chinese, and that phrase has two \*(L"%g\*(R"s in it, as it should \*(-- but
there's a problem.  He translates it word-for-word back: \*(L"In \f(CW%g\fR
directories contains \f(CW%g\fR files match your query.\*(R"  The \f(CW%g\fR
slots are in an order reverse to what they are in English.  You wonder
how you'll get gettext to handle that.
.PP
But you put it aside for the moment, and optimistically hope that the
other translators won't have this problem, and that their languages
will be better behaved \*(-- i.e., that they will be just like English.
.PP
But the Arabic translator is the next to write back.  First off, your
code for \*(L"I scanned \f(CW%g\fR directory.\*(R" or \*(L"I scanned \f(CW%g\fR directories.\*(R"
assumes there's only singular or plural.  But, to use linguistic
jargon again, Arabic has grammatical number, like English (but unlike
Chinese), but it's a three-term category: singular, dual, and plural.
In other words, the way you say \*(L"directory\*(R" depends on whether there's
one directory, or \fItwo\fR of them, or \fImore than two\fR of them.  Your