# Level 3

## Contents

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

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

- debconf

- newt

- win32-loader (&d-i; team)

## Debconf

### Package description

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

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.

However, as the package is a key Debian package, its translation is important for a properly localized system.

### Files location and access methods

The package uses a GIT 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.

- GIT access: `&git-debconf;`

  The debconf translation lies in the `debian/po` directory, while the programs translation is in `po/`.

- HTTP access:

  - &url-level3-pot;/debconf_debian_po.pot

  - &url-level3-po;/debconf_debian_po_&language;.po

### Updating/adding translations

Translations should be reported as bugs against the `debconf` package.

### Specific recommendations

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

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 `debconf` translations.

## Newt

### Package description

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 Yes or No widgets used by boolean templates, as well as the OK or Abort buttons text.

### Files location and access methods

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

- GIT access: `&git-newt;`

  ...

- HTTP access:

  - &url-level3-pot;/newt_po.pot

  - &url-level3-po;/newt_po_&language;.po

### Updating/adding translations

Translations should be reported as bugs against the `newt` package.

### Specific recommendations

none

## Win32-loader

### Package description

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.

This package is, technically speaking, a regular 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 `packages/arch/i386/win32-loader`.

### Files location and access methods

Using GIT is strongly encouraged as this is the only way for them to commit the translations.

This package's l10n material is included in one POT file:

- `l10n/po/messages.pot`

Access to these files:

- GIT clone commands:

  - `&git-win32-loader;`

  The `l10n/po` contains the translation material.

- HTTP access:

  - &url-level3-pot;/win32-loader_l10n_po.pot

  - &url-level3-po;/win32_loader_l10n_po_&language;.po

### Updating/adding translations

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

In case GIT commits are absolutely impossible, these updates can be sent as bug reports against the `win32-loader` package (see bug-reports for details).

### Specific recommendations

none