.\" -*- mode: troff; coding: utf-8 -*-
.\" Automatically generated by Pod::Man 5.01 (Pod::Simple 3.43)
.\"
.\" 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
..
.\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
.ie n \{\
.    ds C` ""
.    ds C' ""
'br\}
.el\{\
.    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 "DEBCONF-GETLANG 1"
.TH DEBCONF-GETLANG 1 2024-02-13 "" 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
debconf\-getlang \- extract a language from a templates file
.SH SYNOPSIS
.IX Header "SYNOPSIS"
.Vb 2
\& debconf\-getlang lang master [translation]
\& debconf\-getlang \-\-stats master translation [...]
.Ve
.SH DESCRIPTION
.IX Header "DESCRIPTION"
Note: This utility is deprecated; you should switch to using the po-debconf package.
.PP
This program helps make and manage translations of debconf templates.
There are basically three situations in which this program might be called:
.IP "A translation is just being started." 4
.IX Item "A translation is just being started."
You want to provide the translator with a file they can work on that has the
English fields from your templates file, plus blank Field-ll fields for the
target language that they can fill in.
.Sp
To do this, run the program with first parameter being the code for the
language that is being translated to, and the second parameter being the
filename of the English templates file.
.IP "A translation is well under way." 4
.IX Item "A translation is well under way."
You have changed some English text, or added more items to your templates
file, and you want to send the translators a file with the English text plus
their current translations (or you are the translator, and you want to
generate such a file for your own use).
.Sp
To accomplish this, run the program with the first parameter being the the
code for the language that is being translated to, the second parameter
being the filename of the master English templates file, and the third
parameter being the filename of the current translated file.
.Sp
When run this way, the program is smart enough to notice fuzzy
translations. For example a fuzzy Description will be output as
Description\-<lang>\-fuzzy, and a new, blank Description\-<lang> will be added.
Translators should remove the \-fuzzy fields as they correct the fuzzy
translations.
.IP "Checking the status of a translation" 4
.IX Item "Checking the status of a translation"
To check the status of a translation, use the \-\-status flag, and pass
the english template file as the first parameter, and all the other
translated templates after that. It will output statistics for each of
them. For example:
.Sp
.Vb 1
\&  debconf\-getlang \-\-stats debian/templates debian/templates.*
.Ve
.SH NOTE
.IX Header "NOTE"
Note that the text in the generated templates may be word-wrapped by
debconf.
.SH "SEE ALSO"
.IX Header "SEE ALSO"
\&\fBdebconf\-mergetemplate\fR\|(1)
.SH AUTHOR
.IX Header "AUTHOR"
Joey Hess <joeyh@debian.org>