[Resolvconf-devel] Bug#625623: resolvconf: [INTL:ru] Russian debconf templates translation update

[Yuri Kozlov]

Package: resolvconf
Version: 1.52
Severity: wishlist
Tags: l10n patch


Russian debconf templates translation update is attached.

-- System Information:
Debian Release: 6.0.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.37-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
-------------- next part --------------
# 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 <kozlov.y at gmail.com>, 2006, 2008.
# Yuri Kozlov <yuray at komyakino.ru>, 2011.
msgid ""
msgstr ""
"Project-Id-Version: resolvconf 1.52\n"
"Report-Msgid-Bugs-To: resolvconf at packages.debian.org\n"
"POT-Creation-Date: 2011-05-04 14:46+0200\n"
"PO-Revision-Date: 2011-05-04 20:16+0400\n"
"Last-Translator: Yuri Kozlov <yuray at komyakino.ru>\n"
"Language-Team: Russian <debian-l10n-russian at lists.debian.org>\n"
"Language: ru\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Lokalize 1.0\n"
"Plural-Forms:  nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && "
"n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"

#. Type: boolean
#. Description
#: ../templates:2001
msgid "Prepare /etc/resolv.conf for dynamic updates?"
msgstr "???????? ???????????? ?????????? /etc/resolv.conf?"

#. Type: boolean
#. Description
#: ../templates:2001
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 ""
"????? resolvconf ???????? ?????????????? ??? ????????????? ?????????? ????? "
"????????? ???????????? ????. ????? ?? ??????????? ?????? ?????????????? "
"???????? ????????????? ?????? /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 ""
"? ?????? ?????????????? ?????? ????????????? ?????? ?? ????? ??????? ??? "
"??????? ?????????? ? ????????????? ???? ????????? ???????????? ???? ?? ????? "
"??????????? ???????????. ????? ???????? ???????????? ??????????, ????? "
"????????? resolvconf ??????? ?????? ??????? ??????????? ?? ????? README."

#. 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 ""
"??????????? ? ??????? ?????????????? ?????? resolvconf ????? ???????? ?? "
"?????? ?????????, ??????? ????? ??? ???????."

#. Type: note
#. Description
#: ../templates:3001
msgid "Reboot recommended"
msgstr "????????????? ????????????"

#. Type: note
#. Description
#: ../templates:3001
msgid ""
"Suppliers of name server information such as local caching name servers and "
"interface configurers are expected to supply name server information to the "
"resolvconf program. However, although installation of the resolvconf package "
"triggers them to supply their information, some of them fail to do so."
msgstr ""
"?????????, ??? ?????????? ? ??????? ???? ??? ????????? "
"resolvconf ????? ???????? ?? ?????? ????????, ????? ??? "
"????????? ????????? ??????? ???? ? "
"??????????? ???????????. "
"??????, ???? ????????? ????????? ?????? resolvconf "
"????????? ??? ??????????, ????????? ?? ??? ?? ????? "
"?? ??????."

#. Type: note
#. Description
#: ../templates:3001
msgid ""
"This bug would lead to loss of valid name server information on installation "
"of the resolvconf package if the following workaround were not adopted: "
"resolvconf includes the full contents of the pre-installation /etc/resolv."
"conf in its database until reboot. This has the drawback that name server "
"information is retained even if the associated interface is later "
"deconfigured. (This incorrect behavior is judged to be less harmful than the "
"alternative of losing valid information.)"
msgstr ""
"???? ?????? ?????? ?? ? ?????? ?????????? ? ??????? ???? ??? "
"????????? ?????? resolvconf, ???? ?? ???? ????????? "
"????????? ???????? ???????: "
"resolvconf ??????? ??? ?????????? /etc/resolv.conf, ??????? ???? "
"?? ?????????, ? ???? ???? ?????? ?? ????????????. "
"?? ? ???? ??????? ???? ??????????: ?????????? ? ??????? ???? "
"?????????, ???? ???? ?? ?????????? ? ??? ?????????? ??????? "
"????? ??????? ????????? (??? ???????????? ????????? "
"????????? ????? ???????????, ??? ?????? ??????????? ??????????)."

#. Type: note
#. Description
#: ../templates:3001
msgid ""
"Until the bug in question is fixed and the workaround removed, the only way "
"to ensure that resolvconf has fully correct name server information after "
"the resolvconf package has been installed on a running system is to reboot "
"the system."
msgstr ""
"???? ??????????????? ?????? ?? ??????????, ? ???????? ??????? "
"?? ???????, ???????????? ???? ?????????????, ??? ? resolvconf "
"???? ????????? ?????????? ?????????? ? ??????? ???? ????? "
"????????? ?????? resolvconf ????? ? ??????? ???????, "
"??? ???????????? ???????."

#. Type: boolean
#. Description
#: ../templates:4001
msgid "Append original file to dynamic file?"
msgstr "???????? ????????? ???? ? ??????????? ??????????? ?????"

#. Type: boolean
#. Description
#: ../templates:4001
msgid ""
"If the original static resolver configuration file (/etc/resolv.conf) "
"contains name server addresses, those addresses should be listed on \"dns-"
"nameservers\" lines in /etc/network/interfaces. For more information, please "
"consult the resolvconf(8) man page and the README file."
msgstr ""
"???? ??? ??????????? ???? ????????? ???????????? ???? (/etc/resolv.conf) "
"???????? ?????? ???????? ????, ?? ??? ?????? ?????? ???? ???????? ? ??????? "
"\"dns-nameservers\" ? ???? /etc/network/interfaces. ????????? ?? ???? "
"???????? ?? ???????? ??????????? resolvconf(8) ? ? ????? README."

#. Type: boolean
#. Description
#: ../templates:4001
msgid ""
"Until /etc/network/interfaces has been edited and the affected interfaces "
"brought down and up again, the name server addresses will not be included in "
"the dynamically generated resolver configuration file."
msgstr ""
"???? ???? /etc/network/interfaces ?? ????? ?????????????? ? ??????????????? "
"?????????? ?? ????? ????????????, ?????? ???????? ???? ?? ????? ??????????? "
"? ??????????? ??????????? ???? ????????? ????????????."

#. Type: boolean
#. Description
#: ../templates:4001
msgid ""
"If you choose this option, a temporary workaround will be put in place: a "
"symbolic link will be created (if it does not already exist) from /etc/"
"resolvconf/resolv.conf.d/tail to /etc/resolvconf/resolv.conf.d/original. "
"This will cause the whole of that original resolver configuration file to be "
"appended to the dynamically generated file."
msgstr ""
"???? ?? ???????? ?????????????, ?? ????? ???????????? ????????? ???????: "
"????? ??????? ????????????? ?????? (???? ?? ??? ?? ????) /etc/resolvconf/"
"resolv.conf.d/tail ?? ???? /etc/resolvconf/resolv.conf.d/original. ??? "
"???????? ? ?????????? ????? ??????????? ???????? ????? ????????? "
"???????????? ? ??????????? ??????????? ????."

#. Type: boolean
#. Description
#: ../templates:4001
msgid ""
"After the required \"dns-nameservers\" lines have been added to /etc/network/"
"interfaces, the /etc/resolvconf/resolv.conf.d/tail link should be replaced "
"by one to /dev/null."
msgstr ""
"????? ?????????? ? /etc/network/interfaces ??????????? ????? \"dns-"
"nameservers\", ????? ???????? ????????????? ?????? /etc/resolvconf/resolv."
"conf.d/tail, ????? ??? ????????? ?? /dev/null."

#~ msgid "Network interfaces reconfiguration mandatory"
#~ msgstr "???????????? ????????????? ??????? ???????????"

#~ 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 ????? ????????? ?????????, ?????????? "
#~ "????????????? ?????????? (?? ????, ?????????????? ?? ? ??? ?? "
#~ "???????????? ??????), ? ????? ????????????? ?????????? DNS."