|
|
181.
|
|
|
pod2usage($exit_status); 
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../lib/Pod/UsageTrans.pm:50
|
|
|
182.
|
|
|
pod2usage( { -message => gettext( $message_text ) ,
-exitval => $exit_status ,
-verbose => $verbose_level,
-output => $filehandle,
-textdomain => $textdomain } );
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../lib/Pod/UsageTrans.pm:52
|
|
|
183.
|
|
|
pod2usage( -msg => $message_text ,
-exitval => $exit_status ,
-verbose => $verbose_level,
-output => $filehandle,
-textdomain => $textdomain );
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../lib/Pod/UsageTrans.pm:58
|
|
|
184.
|
|
|
Pod::UsageTrans works exactly like Pod::Usage but allows you to easily translate your messages. It was specifically written to be compatible with the F<.po> files produced by po4a(7). If you want to use any other method to produce your F<.po> files you should probably take a look at the source of code of this module to see which msgids you will need to use.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../lib/Pod/UsageTrans.pm:66
|
|
|
185.
|
|
|
For documentation on calling pod2usage from your program see Pod::Usage. Pod::UsageTrans additionally supports a C<-textdomain> option where you can specify the gettext domain to use. If C<-textdomain> isn't set, Pod::UsageTrans will behave exactly like Pod::Usage.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../lib/Pod/UsageTrans.pm:73
|
|
|
186.
|
|
|
BUGS
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../lib/Pod/UsageTrans.pm:79
|
|
|
187.
|
|
|
Pod::UsageTrans is currently in the state of a quickly hacked together solution that was tested with exactly one use case. Expect bugs in corner cases.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../lib/Pod/UsageTrans.pm:81
|
|
|
188.
|
|
|
It specifically doesn't support many of the po4a options like charset conversion between the POD input and the msgstr in the F<.pot> file.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../lib/Pod/UsageTrans.pm:85
|
|
|
189.
|
|
|
po4a(7), Pod::Usage, gettext info documentation
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../lib/Pod/UsageTrans.pm:90
|
|
|
190.
|
|
|
Based on Pod::Usage by Brad Appleton E<lt>bradapp@enteract.comE<gt> which is based on code for B<Pod::Text::pod2text()> written by Tom Christiansen E<lt>tchrist@mox.perl.comE<gt>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../lib/Pod/UsageTrans.pm:96
|
