[LCFC] templates://grub2/{templates} (Was: Bug#605748: grub-pc: debconf questions should be translated)

Wed Dec 8 17:08:01 UTC 2010

On Tue, Dec 07, 2010 at 10:07:54AM -0400, David Prévot wrote:
> May I push this further: in order to hopefully get those reviewed
> templates and according translations in time for Squeeze, I'm afraid
> that we have to hurry a bit (and important untranslated templates like
> this ones is really a shame for Lenny to Squeeze upgrades).
> 
> Please find attached the last reviewed version of grub-pc.templates.in,
> with no other changes than s/Description/_Description/ (and relative
> comments deleted) from Justin's review. Justin following comments are
> copied verbatim for Colin and other grub2 maintainers benefits.
> 
> Justin, I also attached templates.in that may need some consistency
> review according to your previous comments (some easily fixable (1) and
> some (2) in the last template I haven't fixed yet).
> 
> If no one objects, I'd like to send a five day call for translation
> update tonight, hoping that further templates update will introduce no
> meaning change.

Here are the final templates.in and grub-pc.templates.in which I just
committed to our squeeze branch, along with the resulting templates.pot.

Should I manually unfuzzy the strings which only changed in terms of
double-spacing/single-spacing, or would the i18n task force like to take
care of that?

Thanks,

-- 
Colin Watson                                       [cjwatson at debian.org]
-------------- next part --------------
Template: grub2/linux_cmdline
Type: string
_Description: Linux command line:
 The following Linux command line was extracted from /etc/default/grub or the
 `kopt' parameter in GRUB Legacy's menu.lst. Please verify that it is correct,
 and modify it if necessary.

Template: grub2/linux_cmdline_default
Type: string
Default: quiet
_Description: Linux default command line:
 The following string will be used as Linux parameters for the default menu
 entry but not for the recovery mode.

# still unused
Template: grub2/kfreebsd_cmdline
Type: string
_Description: kFreeBSD command line:
 The following kFreeBSD command line was extracted from /etc/default/grub or the
 `kopt' parameter in GRUB Legacy's menu.lst. Please verify that it is correct,
 and modify it if necessary.

# still unused
Template: grub2/kfreebsd_cmdline_default
Type: string
Default: quiet
_Description: kFreeBSD default command line:
 The following string will be used as kFreeBSD parameters for the default menu
 entry but not for the recovery mode.

Template: grub2/device_map_regenerated
Type: note
_Description: /boot/grub/device.map has been regenerated
 The file /boot/grub/device.map has been rewritten to use stable device
 names. In most cases, this should significantly reduce the need to change
 it in future, and boot menu entries generated by GRUB should not be
 affected.
 .
 However, since more than one disk is present in the system, it is possible
 that the system is depending on the old device map. Please check whether
 there are any custom boot menu entries that rely on GRUB's (hdN) drive
 numbering, and update them if necessary.
 .
 If you do not understand this message, or if there are no custom
 boot menu entries, you can ignore this message.
-------------- next part --------------

# This file is concatenated.  Do not delete the newline above.

Template: grub-pc/chainload_from_menu.lst
Type: boolean
Default: true
#flag:translate!:6
_Description: Chainload from menu.lst?
 GRUB upgrade scripts have detected a GRUB Legacy setup in /boot/grub.
 .
 In order to replace the Legacy version of GRUB in your system, it is
 recommended that /boot/grub/menu.lst is adjusted to load a GRUB 2 boot
 image from your existing GRUB Legacy setup. This step can be automatically
 performed now.
 .
 It's recommended that you accept chainloading GRUB 2 from menu.lst, and
 verify that the new GRUB 2 setup works before it is written to the MBR
 (Master Boot Record).
 .
 Whatever your decision, you can replace the old MBR image with GRUB 2
 later by issuing the following command as root:
 .
 upgrade-from-grub-legacy

Template: grub-pc/install_devices
Type: multiselect
Choices-C: ${RAW_CHOICES}
Choices: ${CHOICES}
_Description: GRUB install devices:
 The grub-pc package is being upgraded. This menu allows you to select which
 devices you'd like grub-install to be automatically run for, if any.
 .
 Running grub-install automatically is recommended in most situations, to
 prevent the installed GRUB core image from getting out of sync with GRUB
 modules or grub.cfg.
 .
 If you're unsure which drive is designated as boot drive by your BIOS, it is
 often a good idea to install GRUB to all of them.
 .
 Note: it is possible to install GRUB to partition boot records as well, and
 some appropriate partitions are offered here. However, this forces GRUB to
 use the blocklist mechanism, which makes it less reliable, and therefore is
 not recommended.

Template: grub-pc/install_devices_disks_changed
Type: multiselect
Choices-C: ${RAW_CHOICES}
Choices: ${CHOICES}
_Description: GRUB install devices:
 The GRUB boot loader was previously installed to a disk that is no longer
 present, or whose unique identifier has changed for some reason. It is
 important to make sure that the installed GRUB core image stays in sync
 with GRUB modules and grub.cfg. Please check again to make sure that GRUB
 is written to the appropriate boot devices.
 .
 If you're unsure which drive is designated as boot drive by your BIOS, it is
 often a good idea to install GRUB to all of them.
 .
 Note: it is possible to install GRUB to partition boot records as well, and
 some appropriate partitions are offered here. However, this forces GRUB to
 use the blocklist mechanism, which makes it less reliable, and therefore is
 not recommended.

Template: grub-pc/disk_description
Type: text
# Disk sizes are in decimal megabytes, to match how disk manufacturers
# usually describe them.
_Description: ${DEVICE} (${SIZE} MB, ${MODEL})

Template: grub-pc/partition_description
Type: text
# The "-" is used to indicate indentation. Leading spaces may not work.
_Description: - ${DEVICE} (${SIZE} MB, ${PATH})

Template: grub-pc/install_devices_failed
Type: boolean
Default: false
#flag:translate!:3
_Description: Writing GRUB to boot device failed - continue?
 GRUB failed to install to the following devices:
 .
 ${FAILED_DEVICES}
 .
 Do you want to continue anyway?  If you do, your computer may not start up
 properly.

Template: grub-pc/install_devices_failed_upgrade
Type: boolean
Default: true
#flag:translate!:3
_Description: Writing GRUB to boot device failed - try again?
 GRUB failed to install to the following devices:
 .
 ${FAILED_DEVICES}
 .
 You may be able to install GRUB to some other device, although you should
 check that your system will boot from that device. Otherwise, the upgrade
 from GRUB Legacy will be canceled.

Template: grub-pc/install_devices_empty
Type: boolean
Default: false
_Description: Continue without installing GRUB?
 You chose not to install GRUB to any devices. If you continue, the boot
 loader may not be properly configured, and when this computer next starts
 up it will use whatever was previously in the boot sector. If there is an
 earlier version of GRUB 2 in the boot sector, it may be unable to load
 modules or handle the current configuration file.
 .
 If you are already using a different boot loader and want to carry on
 doing so, or if this is a special environment where you do not need a boot
 loader, then you should continue anyway. Otherwise, you should install
 GRUB somewhere.

Template: grub-pc/postrm_purge_boot_grub
Type: boolean
Default: false
_Description: Remove GRUB 2 from /boot/grub?
 Do you want to have all GRUB 2 files removed from /boot/grub?
 .
 This will make the system unbootable unless another boot loader is
 installed.

Template: grub-pc/mixed_legacy_and_grub2
Type: boolean
Default: true
#flag:translate!:3
_Description: Finish conversion to GRUB 2 now?
 This system still has files from the GRUB Legacy boot loader installed, but
 it now also has GRUB 2 boot records installed on these disks:
 .
 ${DISKS}
 .
 It seems likely that GRUB Legacy is no longer in use, and that you should
 instead upgrade the GRUB 2 images on these disks and finish the conversion
 to GRUB 2 by removing old GRUB Legacy files. If you do not upgrade these
 GRUB 2 images, then they may be incompatible with the new packages and
 cause your system to stop booting properly.
 .
 You should generally finish the conversion to GRUB 2 unless these boot
 records were created by a GRUB 2 installation on some other operating
 system.

Template: grub-pc/kopt_extracted
Type: boolean
Default: false
Description: for internal use
-------------- next part --------------
# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: grub2 at packages.debian.org\n"
"POT-Creation-Date: 2010-12-08 17:04+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <LL at li.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=CHARSET\n"
"Content-Transfer-Encoding: 8bit\n"

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

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

#. Type: boolean
#. Description
#: ../grub-pc.templates.in:2001
msgid ""
"In order to replace the Legacy version of GRUB in your system, it is "
"recommended that /boot/grub/menu.lst is adjusted to load a GRUB 2 boot image "
"from your existing GRUB Legacy setup. This step can be automatically "
"performed now."
msgstr ""

#. Type: boolean
#. Description
#: ../grub-pc.templates.in:2001
msgid ""
"It's recommended that you accept chainloading GRUB 2 from menu.lst, and "
"verify that the new GRUB 2 setup works before it is written to the MBR "
"(Master Boot Record)."
msgstr ""

#. Type: boolean
#. Description
#: ../grub-pc.templates.in:2001
msgid ""
"Whatever your decision, you can replace the old MBR image with GRUB 2 later "
"by issuing the following command as root:"
msgstr ""

#. Type: multiselect
#. Description
#. Type: multiselect
#. Description
#: ../grub-pc.templates.in:3001 ../grub-pc.templates.in:4001
msgid "GRUB install devices:"
msgstr ""

#. Type: multiselect
#. Description
#: ../grub-pc.templates.in:3001
msgid ""
"The grub-pc package is being upgraded. This menu allows you to select which "
"devices you'd like grub-install to be automatically run for, if any."
msgstr ""

#. Type: multiselect
#. Description
#: ../grub-pc.templates.in:3001
msgid ""
"Running grub-install automatically is recommended in most situations, to "
"prevent the installed GRUB core image from getting out of sync with GRUB "
"modules or grub.cfg."
msgstr ""

#. Type: multiselect
#. Description
#. Type: multiselect
#. Description
#: ../grub-pc.templates.in:3001 ../grub-pc.templates.in:4001
msgid ""
"If you're unsure which drive is designated as boot drive by your BIOS, it is "
"often a good idea to install GRUB to all of them."
msgstr ""

#. Type: multiselect
#. Description
#. Type: multiselect
#. Description
#: ../grub-pc.templates.in:3001 ../grub-pc.templates.in:4001
msgid ""
"Note: it is possible to install GRUB to partition boot records as well, and "
"some appropriate partitions are offered here. However, this forces GRUB to "
"use the blocklist mechanism, which makes it less reliable, and therefore is "
"not recommended."
msgstr ""

#. Type: multiselect
#. Description
#: ../grub-pc.templates.in:4001
msgid ""
"The GRUB boot loader was previously installed to a disk that is no longer "
"present, or whose unique identifier has changed for some reason. It is "
"important to make sure that the installed GRUB core image stays in sync with "
"GRUB modules and grub.cfg. Please check again to make sure that GRUB is "
"written to the appropriate boot devices."
msgstr ""

#. Type: text
#. Description
#. Disk sizes are in decimal megabytes, to match how disk manufacturers
#. usually describe them.
#: ../grub-pc.templates.in:5001
msgid "${DEVICE} (${SIZE} MB, ${MODEL})"
msgstr ""

#. Type: text
#. Description
#. The "-" is used to indicate indentation. Leading spaces may not work.
#: ../grub-pc.templates.in:6001
msgid "- ${DEVICE} (${SIZE} MB, ${PATH})"
msgstr ""

#. Type: boolean
#. Description
#: ../grub-pc.templates.in:7001
msgid "Writing GRUB to boot device failed - continue?"
msgstr ""

#. Type: boolean
#. Description
#. Type: boolean
#. Description
#: ../grub-pc.templates.in:7001 ../grub-pc.templates.in:8001
msgid "GRUB failed to install to the following devices:"
msgstr ""

#. Type: boolean
#. Description
#: ../grub-pc.templates.in:7001
msgid ""
"Do you want to continue anyway?  If you do, your computer may not start up "
"properly."
msgstr ""

#. Type: boolean
#. Description
#: ../grub-pc.templates.in:8001
msgid "Writing GRUB to boot device failed - try again?"
msgstr ""

#. Type: boolean
#. Description
#: ../grub-pc.templates.in:8001
msgid ""
"You may be able to install GRUB to some other device, although you should "
"check that your system will boot from that device. Otherwise, the upgrade "
"from GRUB Legacy will be canceled."
msgstr ""

#. Type: boolean
#. Description
#: ../grub-pc.templates.in:9001
msgid "Continue without installing GRUB?"
msgstr ""

#. Type: boolean
#. Description
#: ../grub-pc.templates.in:9001
msgid ""
"You chose not to install GRUB to any devices. If you continue, the boot "
"loader may not be properly configured, and when this computer next starts up "
"it will use whatever was previously in the boot sector. If there is an "
"earlier version of GRUB 2 in the boot sector, it may be unable to load "
"modules or handle the current configuration file."
msgstr ""

#. Type: boolean
#. Description
#: ../grub-pc.templates.in:9001
msgid ""
"If you are already using a different boot loader and want to carry on doing "
"so, or if this is a special environment where you do not need a boot loader, "
"then you should continue anyway. Otherwise, you should install GRUB "
"somewhere."
msgstr ""

#. Type: boolean
#. Description
#: ../grub-pc.templates.in:10001
msgid "Remove GRUB 2 from /boot/grub?"
msgstr ""

#. Type: boolean
#. Description
#: ../grub-pc.templates.in:10001
msgid "Do you want to have all GRUB 2 files removed from /boot/grub?"
msgstr ""

#. Type: boolean
#. Description
#: ../grub-pc.templates.in:10001
msgid ""
"This will make the system unbootable unless another boot loader is installed."
msgstr ""

#. Type: boolean
#. Description
#: ../grub-pc.templates.in:11001
msgid "Finish conversion to GRUB 2 now?"
msgstr ""

#. Type: boolean
#. Description
#: ../grub-pc.templates.in:11001
msgid ""
"This system still has files from the GRUB Legacy boot loader installed, but "
"it now also has GRUB 2 boot records installed on these disks:"
msgstr ""

#. Type: boolean
#. Description
#: ../grub-pc.templates.in:11001
msgid ""
"It seems likely that GRUB Legacy is no longer in use, and that you should "
"instead upgrade the GRUB 2 images on these disks and finish the conversion "
"to GRUB 2 by removing old GRUB Legacy files. If you do not upgrade these "
"GRUB 2 images, then they may be incompatible with the new packages and cause "
"your system to stop booting properly."
msgstr ""

#. Type: boolean
#. Description
#: ../grub-pc.templates.in:11001
msgid ""
"You should generally finish the conversion to GRUB 2 unless these boot "
"records were created by a GRUB 2 installation on some other operating system."
msgstr ""

#. Type: string
#. Description
#: ../templates.in:1001
msgid "Linux command line:"
msgstr ""

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

#. Type: string
#. Description
#: ../templates.in:2001
msgid "Linux default command line:"
msgstr ""

#. Type: string
#. Description
#: ../templates.in:2001
msgid ""
"The following string will be used as Linux parameters for the default menu "
"entry but not for the recovery mode."
msgstr ""

#. Type: string
#. Description
#: ../templates.in:3001
msgid "kFreeBSD command line:"
msgstr ""

#. Type: string
#. Description
#: ../templates.in:3001
msgid ""
"The following kFreeBSD command line was extracted from /etc/default/grub or "
"the `kopt' parameter in GRUB Legacy's menu.lst. Please verify that it is "
"correct, and modify it if necessary."
msgstr ""

#. Type: string
#. Description
#: ../templates.in:4001
msgid "kFreeBSD default command line:"
msgstr ""

#. Type: string
#. Description
#: ../templates.in:4001
msgid ""
"The following string will be used as kFreeBSD parameters for the default "
"menu entry but not for the recovery mode."
msgstr ""

#. Type: note
#. Description
#: ../templates.in:5001
msgid "/boot/grub/device.map has been regenerated"
msgstr ""

#. Type: note
#. Description
#: ../templates.in:5001
msgid ""
"The file /boot/grub/device.map has been rewritten to use stable device "
"names. In most cases, this should significantly reduce the need to change it "
"in future, and boot menu entries generated by GRUB should not be affected."
msgstr ""

#. Type: note
#. Description
#: ../templates.in:5001
msgid ""
"However, since more than one disk is present in the system, it is possible "
"that the system is depending on the old device map. Please check whether "
"there are any custom boot menu entries that rely on GRUB's (hdN) drive "
"numbering, and update them if necessary."
msgstr ""

#. Type: note
#. Description
#: ../templates.in:5001
msgid ""
"If you do not understand this message, or if there are no custom boot menu "
"entries, you can ignore this message."
msgstr ""