<!-- <chapter id="translators-level3"><title>Translating &d-i; - Level 3</title> -->

<sect1 id="translators-level3">
<title>
Level 3
</title>

<sect2>
<title>
Contents
</title>

<para>
The level 3 of translations contains packages which provide general infrastructure for
dialogs or for starting the installer from Windows systems.
</para>

<para>This includes one package maintained by the &d-i; team (win32-loader) as well as a few
other Debian packages:
</para>

	    <itemizedlist>
	      <listitem>
		<para>
		  debconf
		</para>
	      </listitem>
	    <listitem>
	      <para>
		newt
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		win32-loader (&d-i; team)
	      </para>
	    </listitem>
	    </itemizedlist>

</sect2>

<sect2 id="level3_debconf">
<title>
Debconf
</title>

<sect3 id="level3_debconf_description">
<title>
Package description
</title>

<para>
The <classname>debconf</classname> Debian package is the program which
handles all configuration steps of other packages when these packages
need some user interaction while they are configured.
</para>

<para>
This package is installed on all Debian systems. Its installation
process usually inputs the user about the default priority of
questions. However, when installed in a normal &d-i; installation
process, these answers are pre-filled with the priority settings of
the installation process. As a consequence, the questions are usually
hidden from users.
</para>

<para>
However, as the package is a <quote>key</quote> Debian package, its
translation is important for a properly localized system.
</para>

</sect3>

<sect3 id="level3_debconf_files">
<title>
Files location and access methods
</title>

<para>
The package uses a <acronym>GIT</acronym> repository. Commit access may be requested to
the &i18n-coords;. However, as the translatable parts do not change
very often, getting commit access is not highly useful.
</para>

<itemizedlist>
<listitem>
<acronym>GIT</acronym> access: <command>&git-debconf;</command>
<para>
The debconf translation lies in the <filename>debian/po</filename> directory, while
the programs translation is in <filename>po/</filename>.
</para>
</listitem>
<listitem>
<para>
<acronym>HTTP</acronym> access: 
</para>
<itemizedlist>
<listitem>
<para>
          <ulink url="&url-level3-pot;/debconf_debian_po.pot">&url-level3-pot;/debconf_debian_po.pot</ulink>
</para>
</listitem>
<listitem>
<para>
&url-level3-po;/debconf_debian_po_&language;.po
</para>
</listitem>
</itemizedlist>
</listitem>
</itemizedlist>

</sect3>


<sect3 id="level3_debconf_updates">
<title>
Updating/adding translations
</title>

<para>
Translations should be reported as bugs against the
<classname>debconf</classname> package.
</para>

</sect3>

<sect3 id="level3_debconf_recommendations">
<title>
Specific recommendations
</title>

<para>
The translations are very similar to the questions asked by the
<classname>cdebconf</classname> package, which is part of the level1
of &d-i; translations.
</para>

<para>
Translators should then be careful about using the same terminology in
both packages, especially for questions priorities. This can be done
by merging the translations from &d-i; level1 into
<classname>debconf</classname> translations.
</para>

</sect3>

</sect2>

<sect2 id="level3_newt">
<title>
Newt
</title>

<sect3 id="level3_newt_description">
<title>
Package description
</title>

<para>
The newt package is a library (whiptail) which includes widgets used by
the most popular interface to the debconf software, the software
involved in packages configuration steps. These widgets include the
<guibutton>Yes</guibutton> or  <guibutton>No</guibutton> widgets used by
boolean templates, as well as the  <guibutton>OK</guibutton> or
<guibutton>Abort</guibutton> buttons text.
</para>

</sect3>

<sect3 id="level3_newt_files">
<title>
Files location and access methods
</title>

<para>
The package uses a <acronym>GIT</acronym> repository.
As the translatable parts do not change very often, getting commit access is not
highly useful.
</para>

<itemizedlist>
  <listitem>
      <acronym>GIT</acronym> access: <command>&git-newt;</command>
         <para>
            ...
         </para>
  </listitem>
  <listitem>
    <para>
      <acronym>HTTP</acronym> access: 
    </para>
    <itemizedlist>
      <listitem>
        <para>
          <ulink url="&url-level3-pot;/newt_po.pot">&url-level3-pot;/newt_po.pot</ulink>
        </para>
      </listitem>
      <listitem>
        <para>
          &url-level3-po;/newt_po_&language;.po
        </para>
      </listitem>
    </itemizedlist>
  </listitem>
</itemizedlist>

</sect3>

<sect3 id="level3_newt_updates">
<title>
Updating/adding translations
</title>

<para>
Translations should be reported as bugs against the <classname>newt</classname> package.
</para>

</sect3>

<sect3 id="level3_newt_recommendations">
<title>
Specific recommendations
</title>

<para>
none
</para>

</sect3>

</sect2>

<sect2>
<title>
Win32-loader
</title>

<sect3>
<title>
Package description
</title>

<para>
The &win32-loader; package contains is a utility that can be run from the Windows
environment and which, with a few questions, prepares a system for booting a &d-i;
installation process. This utility is included on Debian installation media to
allow an easier startup of a Debian installation.
</para>

<para>
This package is, technically speaking, a <quote>regular</quote>
Debian package. However, the package maintainer is the &d-i; team and
the package is managed and developed the same way core &d-i; packages
are managed. The package is part of the core &d-i; development repository under
<filename>packages/arch/i386/win32-loader</filename>.
</para>

</sect3>

<sect3>
<title>
Files location and access methods
</title>

<para>
Using <acronym>GIT</acronym> is strongly encouraged as
this is the only way for them to commit the translations.
</para>

<para>This package's l10n material is included in one POT file:
</para>

<itemizedlist>
<listitem>
<para>
<filename>l10n/po/messages.pot</filename></para>
</listitem>
</itemizedlist>

<para>
Access to these files:
</para>

<itemizedlist>
  <listitem>
<para>
GIT clone commands:
</para>
<itemizedlist>
<listitem>
<command>&git-win32-loader;</command>
</listitem>
</itemizedlist>
    <para>
      The  <filename>l10n/po</filename> contains the translation material.
    </para>

  </listitem>
  <listitem>
    <para>
      <acronym>HTTP</acronym> access: 
    </para>
    <itemizedlist>
      <listitem>
        <para>
          <ulink url="&url-level3-pot;/win32-loader_l10n_po.pot">&url-level3-pot;/win32-loader_l10n_po.pot</ulink>
        </para>
      </listitem>
      <listitem>
        <para>
          &url-level3-po;/win32_loader_l10n_po_&language;.po
        </para>
      </listitem>
    </itemizedlist>
  </listitem>
</itemizedlist>


</sect3>

<sect3>
<title>
Updating/adding translations
</title>

<para>
Translators should
copy the <filename>messages.pot</filename> file in <filename>l10n/po</filename> as
<filename>&language;.po</filename> and work on this file, then add it to the
repository and later commit the needed updates.
</para>


<para>
In case <acronym>GIT</acronym> commits are
absolutely impossible, these updates can be sent as bug reports
against the <classname>win32-loader</classname> package (see <xref
linkend="bug-reports"/> for details).
</para>

</sect3>

<sect3>
<title>
Specific recommendations
</title>

<para>
none
</para>

</sect3>

</sect2>


</sect1>


<!-- </chapter> -->
