Hi,
The debian-l10n-english team has reviewed the debconf templates for
resolvconf. This process has resulted in changes that may make your
existing translation incomplete.
A round of translation updates is being launched to synchronize all
translations.
Please send the updated file as a wishlist bug against the package.
The deadline for receiving the updated translation is Monday, February 25, 2008.
Thanks,
# translation of ru.po to Russian
#
#Translators, if you are not familiar with the PO format, gettext
#documentation is worth reading, especially sections dedicated to
#this format, e.g. by running:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
#Some information specific to po-debconf are available at
#/usr/share/doc/po-debconf/README-trans
# or http://www.debian.org/intl/l10n/po-debconf/README-trans#
#Developers do not need to manually edit POT or PO files.
# Yuri Kozlov [EMAIL PROTECTED], 2006.
#
msgid
msgstr
Project-Id-Version: resolvconf-1.34\n
Report-Msgid-Bugs-To: [EMAIL PROTECTED]
POT-Creation-Date: 2008-02-11 07:44+0100\n
PO-Revision-Date: 2006-01-29 11:28+0300\n
Last-Translator: Yuri Kozlov [EMAIL PROTECTED]\n
Language-Team: Russian debian-l10n-russian@lists.debian.org\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n
X-Generator: KBabel 1.9.1\n
#. Type: boolean
#. Description
#: ../templates:2001
msgid Prepare /etc/resolv.conf for dynamic updates?
msgstr Включить динамическое обновление /etc/resolv.conf?
#. Type: boolean
#. Description
#: ../templates:2001
#, fuzzy
#| msgid
#| This package contains the infrastructure required for dynamic updating of
#| the resolver configuration file. Part of the necessary infrastructure is
#| a symbolic link from /etc/resolv.conf to /etc/resolvconf/run/resolv.conf.
#| If you agree then this link will be created. The existing /etc/resolv.
#| conf file will be preserved as /etc/resolvconf/resolv.conf.d/original; it
#| will be restored if this package is removed.
msgid
The resolvconf package contains the infrastructure required for dynamic
updating of the resolver configuration file. Part of the necessary
infrastructure is a symbolic link from /etc/resolv.conf to /etc/resolvconf/
run/resolv.conf. If you choose this option then this link will be created;
the existing /etc/resolv.conf file will be preserved as /etc/resolvconf/
resolv.conf.d/original, and will be restored if this package is removed.
msgstr
Данный пакет содержит инфраструктуру динамического обновления файла
настройки определителя имён. Одной из необходимых частей инфраструктуры
является символическая ссылка /etc/resolv.conf на /etc/resolvconf/run/resolv.
conf. Если вы ответите утвердительно, то такая ссылка будет создана.
Существующий файл /etc/resolv.conf будет сохранён под именем /etc/resolvconf/
resolv.conf.d/original; он будет восстановлен при удалении пакета.
#. Type: boolean
#. Description
#: ../templates:2001
msgid
Declining this option will prevent future installations from recreating the
symbolic link and therefore the resolver configuration file will not be
dynamically updated. Dynamic updating can then be activated following
instructions in the README file.
msgstr
#. Type: boolean
#. Description
#: ../templates:2001
msgid
The presence of resolvconf can affect the behavior of other programs, so it
should not be left installed if unconfigured.
msgstr
#. Type: note
#. Description
#: ../templates:3001
msgid Network interfaces reconfiguration mandatory
msgstr
#. Type: note
#. Description
#: ../templates:3001
#, fuzzy
#| msgid
#| Once resolvconf is installed, interface configurers supply nameserver
#| information to it (which it then makes available to the C Library
#| resolver and to DNS caches). However, they do this only when they bring
#| up interfaces. Therefore for resolvconf's nameserver information to be up
#| to date after initial installation it is necessary to reconfigure
#| interfaces -- that is, to take them down and then to bring them up again
#| -- and to restart DNS caches.
msgid
Once resolvconf is installed, interface configurers supply name server
information to it (which it then makes available to the C library resolver
and to DNS caches). However, they do this only when they bring up
interfaces. Therefore for resolvconf's name server information to be up to
date after initial installation it is necessary to reconfigure interfaces
(that is, to take them down and then to bring them up again) and to restart
DNS caches.
msgstr
После установки resolvconf, настройщики интерфейсов предоставляют ему
информацию о серверах имён (которая затем становится доступна C библиотеке
resolver и кеширующим DNS). Однако, они делают это только при активации
интерфейсов. Поэтому, чтобы синхронизировать информацию о серверах имён для
resolvconf после начальной установки необходимо перенастроить интерфейсы, то
есть,
