Fix: use better style in debconf translations

[rrq/maintain_lilo.git] / debian / lilo.templates

diff --git a/debian/lilo.templates b/debian/lilo.templates
index cb6ed22f1adf916fa0c8b87047131f07debb4c92..87bda43d196530958bea173b59af8abc97c240fe 100644 (file)
--- a/debian/lilo.templates
+++ b/debian/lilo.templates
@@ -2,7 +2,7 @@ Template: lilo/new-config
 Type: note
 _Description: LILO configuration
  It seems to be your first LILO installation. It is absolutely necessary to
 Type: note
 _Description: LILO configuration
  It seems to be your first LILO installation. It is absolutely necessary to

- run liloconfig(8) when you complete this process and execute /sbin/lilo 
+ run liloconfig(8) when you complete this process and execute /sbin/lilo

  after this.
  .
  LILO won't work if you don't do this. 
  after this.
  .
  LILO won't work if you don't do this. 


@@ -46,12 +46,12 @@ Template: lilo/runme
 Type: boolean
 Default: false
 _Description: Do you want to run /sbin/lilo now?
 Type: boolean
 Default: false
 _Description: Do you want to run /sbin/lilo now?

- It was detected that it's necessary to run /sbin/lilo in order to update
+ It was detected that it's necessary to run /sbin/lilo in order to activate

  the new LILO configuration.
  .
  WARNING: This procedure will write data in your MBR and may overwrite
  the new LILO configuration.
  .
  WARNING: This procedure will write data in your MBR and may overwrite

- some things in that place. If you skip this step, you must run /sbin/lilo
- before reboot your computer or your system may not boot again.
+ some data there. If you skip this step, you must run /sbin/lilo before
+ rebooting your computer, or your system may not boot again.

 
 Template: lilo/diskid_uuid
 Type: boolean
 
 Template: lilo/diskid_uuid
 Type: boolean


@@ -94,12 +94,12 @@ Template: liloconfig/lilo_warning
 Type: error
 _Description: WARNING!
  Even if lilo runs successfully, see /usr/share/doc/lilo/INCOMPAT.gz for
 Type: error
 _Description: WARNING!
  Even if lilo runs successfully, see /usr/share/doc/lilo/INCOMPAT.gz for

- changes in the usage of the ${liloconf} file.  If needed: edit ${liloconf} and
+ changes in the usage of the ${liloconf} file. If needed: edit ${liloconf} and

  rerun '/sbin/lilo -v'
 
 Template: liloconfig/select_bitmap
 Type: select
  rerun '/sbin/lilo -v'
 
 Template: liloconfig/select_bitmap
 Type: select

-Choices: /boot/tuxlogo.bmp, /boot/inside.bmp, /boot/debianlilo.bmp, /boot/coffee.bmp, /boot/onlyblue.bmp
+Choices: /boot/tuxlogo.bmp, /boot/inside.bmp, /boot/debian.bmp, /boot/debian-de.bmp, /boot/debianlilo.bmp, /boot/coffee.bmp, /boot/onlyblue.bmp

 Default: /boot/debian.bmp
 _Description: The following is the list of the available bitmaps
 
 Default: /boot/debian.bmp
 _Description: The following is the list of the available bitmaps
 


@@ -147,7 +147,7 @@ _Description: Booting from hard disk.
  partition active. You'll be asked to perform each of these tasks. You may skip
  any or all of them, and perform them manually later on.
  .
  partition active. You'll be asked to perform each of these tasks. You may skip
  any or all of them, and perform them manually later on.
  .

- This will result in Linux being booted by default from the hard disk.  If your
+ This will result in Linux being booted by default from the hard disk. If your

  setup is complicated or unusual you should consider writing your own
  customised ${liloconf}. To do this you should exit this configuration program
  and refer to the comprehensive lilo documentation, which can be found in
  setup is complicated or unusual you should consider writing your own
  customised ${liloconf}. To do this you should exit this configuration program
  and refer to the comprehensive lilo documentation, which can be found in