.\" Automatically generated by Pod::Man 4.10 (Pod::Simple 3.35)
.\"
.\" Standard preamble:
.\" ========================================================================
.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" ''
.    ds C`
.    ds C'
'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 >0, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
.\" entries marked with X<> in POD.  Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.\"
.\" Avoid warning from groff about undefined register 'F'.
.de IX
..
.nr rF 0
.if \n(.g .if rF .nr rF 1
.if (\n(rF:(\n(.g==0)) \{\
.    if \nF \{\
.        de IX
.        tm Index:\\$1\t\\n%\t"\\$2"
..
.        if !\nF==2 \{\
.            nr % 0
.            nr F 2
.        \}
.    \}
.\}
.rr rF
.\" ========================================================================
.\"
.IX Title "PODEBCONF-DISPLAY-PO 1"
.TH PODEBCONF-DISPLAY-PO 1 "2018-11-20" "" "po-debconf"
.\" 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"
podebconf\-display\-po \- display content of a PO file in a debconf interface
.SH "SYNOPSIS"
.IX Header "SYNOPSIS"
\&\fBpodebconf-display-po\fR
[\fB\-h\fR]
[\fB\-f\fR \fI\s-1FRONTEND\s0\fR]
\&\fIfile.po\fR
.SH "DESCRIPTION"
.IX Header "DESCRIPTION"
As with any other localization work, translators should test their
translations by running the program they are working on.  But this
is a very hard job with complicated configuration scripts because
there is no automatic way to have all messages displayed.
.PP
The \fBpodebconf-display-po\fR program could be called the
\&\fIPoor Man Localization Checker\fR for debconf.  It parses a \s-1PO\s0 file,
tries to guess what the original templates file did look like, and
displays messages in a debconf interface.
.PP
Of course being root is not mandatory, and there is no interaction
between \fBpodebconf-display-po\fR and system-wide debconf settings.
.SH "OPTIONS"
.IX Header "OPTIONS"
.IP "\fB\-h\fR, \fB\-\-help\fR" 4
.IX Item "-h, --help"
Display a usage summary and exit.
.IP "\fB\-f\fR, \fB\-\-frontend=\f(BI\s-1FRONTEND\s0\fB\fR" 4
.IX Item "-f, --frontend=FRONTEND"
Select an alternate debconf frontend.
.SH "CAVEATS"
.IX Header "CAVEATS"
.IP "\(bu" 4
As \fBpodebconf-display-po\fR relies on \f(CW\*(C`debconf\*(C'\fR to display questions,
your environment must be setup to display localized questions in the
language of the \s-1PO\s0 file.
If you want to check a translation in another language, you need to
temporarily change your settings, e.g.
.Sp
.Vb 1
\&  $ LANGUAGE=de podebconf\-display\-po de.po
.Ve
.Sp
If the \s-1PO\s0 file cannot be converted into your current encoding, English
strings are displayed instead of the localized ones.  You then have
to switch to a \s-1UTF\-8\s0 environment to prevent encoding mismatch.
.IP "\(bu" 4
Prior to 0.8.3, \f(CW\*(C`po\-debconf\*(C'\fR did only insert the field name in \s-1PO\s0
files.  But some discussions on mailing-lists showed that text
format does depend on template type, e.g. string and boolean types
are different because the former is an open question and user has
to enter some text input, whereas the latter is basically a Yes/No
question.  Authors have to think about it when writing their templates
files, but translators also have to be aware.
.Sp
This is achieved when \s-1PO\s0 files are generated by po-debconf >= 0.8.3,
template type is inserted in \s-1PO\s0 files.  With older versions,
\&\fBpodebconf-display-po\fR has a trivial algorithm to determine original
template type, and may sometimes be wrong.
.IP "\(bu" 4
The \f(CW\*(C`dialog\*(C'\fR frontend, when based upon \f(CW\*(C`whiptail\*(C'\fR, traps system
signals and thus \fBpodebconf-display-po\fR cannot be interrupted by \f(CW\*(C`Ctrl\-C\*(C'\fR
when using this frontend.
.SH "SEE ALSO"
.IX Header "SEE ALSO"
\&\fBdebconf\fR\|(1)
.SH "AUTHOR"
.IX Header "AUTHOR"
.Vb 1
\&  Denis Barbier <barbier@linuxfr.org>
.Ve