Bug#516243: [INTL:be] Updated Belarusian debconf for exim4

[Pavel Piatruk]

Package: grub2
Version: 1.96+20080724-16
Severity: wishlist


Please update Belarusian debconf translation

-- System Information:
Debian Release: 5.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores)
Locale: LANG=be_BY.CP1251, LC_CTYPE=be_BY.CP1251 (charmap=CP1251)
Shell: /bin/sh linked to /bin/bash
-------------- next part --------------
# Belarusian translation of grub2 templates
# Copyright (C) 2009 respective translators (see below)
# This file is distributed under the same license as the grub2 package.
# Hleb Rubanau <g.rubanau at gmail.com>, 2009.
#
msgid ""
msgstr ""
"Project-Id-Version: be\n"
"Report-Msgid-Bugs-To: pkg-grub-devel at lists.alioth.debian.org\n"
"POT-Creation-Date: 2008-10-26 18:22+0100\n"
"PO-Revision-Date: 2009-02-19 09:19+0200\n"
"Last-Translator: Hleb Rubanau <g.rubanau at gmail.com>\n"
"Language-Team: Belarusian (Official spelling) <be at d-i.tanatos.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: note
#. Description
#: ../grub2.templates:1001
msgid "GRUB 1.95 numbering scheme transition"
msgstr "????? ????? ????????? GRUB 1.95"

#. Type: note
#. Description
#: ../grub2.templates:1001
msgid ""
"As of version 1.95, GRUB 2 has changed its numbering scheme.  Partitions are "
"now counted starting from 1 rather than 0.  This is to make it consistent "
"with device names of Linux and the other kernels used in Debian.  For "
"example, when using Linux as the kernel, \"(hd0,1)\" refers to the same "
"partition as the /dev/sda1 device node."
msgstr ""
"????? ????????? ? GRUB 2 ????????? ? ?????????? ? ??????? 1.95 . ????? "
"??????? ????? ??????????? ????????? ? 1 ?????? 0. ???? ????????, ??? "
"?????????? ?????? ???????? ? Linux ? ????? ?????, ???? ???????????????? "
"? Debian. ?????????, ???? ? ?????? ???? ???????????????? Linux, "
"????? \"(hd0,1)\" ????????? ???? ?????? ??????? ?????, ?? ? ???? ??????? "
"/dev/sda1."

#. Type: note
#. Description
#: ../grub2.templates:1001
msgid ""
"Because of this, there's a chance your system becomes unbootable if update-"
"grub(8) is run before GRUB is updated, generating a grub.cfg file that your "
"installed GRUB won't yet be able to parse correctly.  To ensure your system "
"will be able to boot, you have to:"
msgstr ""
"? ????? ??????? ???? ??????? ???? ????? ?????????? ?? ????????, ???? "
"???????? update-grub(8), ?????????? ?? ?????????? GRUB, ???????? ???? "
"grub.cfg, ??? ????????? ???????? ?????????? ??????????? GRUB. ??? "
"???????????, ??? ???? ??????? ???????? ?? ????????, ?????: "

#. Type: note
#. Description
#: ../grub2.templates:1001
msgid ""
" - Reinstall GRUB (typically, by running grub-install).\n"
" - Rerun update-grub to generate a new grub.cfg."
msgstr ""
" - ?????????????? GRUB (????????, ???? ?????? grub-install).\n"
" - ????????????? update-grub, ??? ???????? ???? grub.cfg."

#. Type: boolean
#. Description
#: ../grub-pc.templates:1001
msgid "Chainload from menu.lst?"
msgstr "?????????? ???????? ? menu.lst?"

#. Type: boolean
#. Description
#: ../grub-pc.templates:1001
msgid "GRUB upgrade scripts have detected a GRUB Legacy setup in /boot/grub."
msgstr "??????? ?????????? GRUB ??????? ?????????? ?????? GRUB, ??????????? ? /boot/grub."

#. Type: boolean
#. Description
#: ../grub-pc.templates:1001
msgid ""
"In order to replace the Legacy version of GRUB in your system, it is "
"recommended that /boot/grub/menu.lst is adjusted to chainload GRUB 2 from "
"your existing GRUB Legacy setup.  This step may be automaticaly performed "
"now."
msgstr ""
"??? ???????? ?????????? ?????? GRUB ? ????? ???????, ???? ????????? ???? "
"/boot/grub/menu.lst ????? ?????, ??? GRUB 2 ?????????? ???? ???????? "
"?????????? ???????? (chainload) ? ???????? ?????????? ?????? GRUB. ????? "
"????? ??????? ????? ??????? ???????????. "

#. Type: boolean
#. Description
#: ../grub-pc.templates:1001
msgid ""
"It's recommended that you accept chainloading GRUB 2 from menu.lst, and "
"verify that your new GRUB 2 setup is functional for you, before you install "
"it directly to your MBR (Master Boot Record)."
msgstr ""
"???? ?????? ????? ?????????? ???????? GRUB 2 ? menu.lst, ??? ?????????, ?? "
"???????? ??? ??? ?????? ?????????? GRUB 2, ????? ??? ?? ??????????? ??? "
"?????????? ? ??????? ?????????? ????? (MBR, Master Boot Record)."

#. Type: boolean
#. Description
#: ../grub-pc.templates:1001
msgid ""
"In either case, whenever you want GRUB 2 to be loaded directly from MBR, you "
"can do so by issuing (as root) the following command:"
msgstr ""
"???? ? ?? ??????, ??? GRUB 2 ?????????? ?????????? ? MBR, ?????????? ????????? "
"? ??????? ????????????? root ????????? ???????:"

#. Type: boolean
#. Description
#: ../grub-pc.templates:1001
msgid "upgrade-from-grub-legacy"
msgstr "update-from-grub-legacy"

#. Type: string
#. Description
#: ../grub-pc.templates:2001
msgid "Linux command line:"
msgstr "???????? ????? Linux:"

#. Type: string
#. Description
#: ../grub-pc.templates:2001
msgid ""
"The following Linux command line was extracted from the `kopt' parameter in "
"GRUB Legacy's menu.lst.  Please verify that it is correct, and modify it if "
"necessary."
msgstr ""
"????????? ??????? Linux ???? ???????? ? ????????? `kopt' ? ????? ??????? "
"(menu.lst) ?????????? ?????? GRUB. ???? ?????, ?????????????, ??? ??? "
"????????? ?????????, ?????, ???? ?????, ???????? ??. "