Package: installation-guide
Version:
Severity: minor
Tags: l10n, patch
boot-installer.po typos etc.
1.
po:8
auto: ⑤ Tag: para
Original: ⌘0 From the user's perspective, the most important
difference between SRM and ARC is that the choice of console
constrains the possible disk-partitioning scheme for the hard disk
which you wish to boot off of.
- for the hard disk which you wish to boot off of.
+ for the hard disk from which you wish to boot.
2.
po:12
auto: ⑤ Tag: para
Original: ⌘0 Because <command>MILO</command> is not available for
any of the Alpha systems currently in production (as of February
2000), and because it is no longer necessary to buy an OpenVMS or
Tru64 Unix license to have SRM firmware on your older Alpha, it is
recommended that you use SRM when possible.
- as of February 2000
Do we really not have any more recent information?
This also applies to this following string:
po:52
auto: ⑤ Tag: para
Original: ⌘0 Thus, three scenarios are generally possible, depending
on the system's console firmware and whether or not <command>MILO</
command> is available: <informalexample><screen>\n
SRM -> aboot\n
SRM -> MILO\n
ARC -> MILO\n
</screen></informalexample> Because <command>MILO</command> is not
available for any of the Alpha systems currently in production (as of
February 2000), and because it is no longer necessary to buy an
OpenVMS or Tru64 Unix license to have SRM firmware on your older
Alpha, it is recommended that you use SRM and <command>aboot</
command> on new installations of GNU/Linux, unless you wish to dual-
boot with Windows NT.
3.
.po:13
auto: ⑤ Tag: para
Original: ⌘0 The following table summarizes available and supported
system type/console combinations (see <xref linkend=\"alpha-cpus\"/>
for the system type names). The word <quote>ARC</quote> below denotes
any of the ARC-compliant consoles.
- The word <quote>ARC</quote> below
+ The acronym <quote>ARC</quote> below
4.
po:78
auto: ⑤ Tag: para
Original: ⌘0 Netwinders have two network interfaces: A 10Mbps NE2000-
compatible card (which is generally referred to as <literal>eth0</
literal>) and a 100Mbps Tulip card. There may be problems loading the
image via TFTP using the 100Mbps card so it is recommended that you
use the 10Mbps interface (the one labeled with <literal>10 Base-T</
literal>).
- interfaces: A
+ interfaces: a
5.
po:88
auto: ⑤ Tag: para
Original: ⌘0 To boot a CD-ROM from the Cyclone console prompt, use
the command <command>boot cd0:cats.bin</command>
- bin</command>
+ bin</command>.
6.
.po:101
auto: ⑤ Tag: title
Original: ⌘0 Booting from Linux Using <command>LILO</command> or
<command>GRUB</command>
- Linux Using
-Linux using
7.
.po:130
auto: ⑤ Tag: para
Original: ⌘0 When the installer boots, you should be presented with
a friendly graphical screen showing the Debian logo and the boot
prompt: <informalexample><screen>\n
Press F1 for help, or ENTER to boot:\n
</screen></informalexample> <snip>
I can't find anything like this in the D-I Level1 file. Where does it
occur? It's imperative that this core information be translated.
8. Use of entities
(a)
po:143
auto: ⑤ Tag: para
Original: ⌘0 Select <command>Boot Maintenance Menu</command> from
the menu with the arrow keys and press <command>ENTER</command>. This
will display a new menu.
- <command>ENTER</command>
+ &enterkey;
(b)
Several strings after this one also use <command>ENTER</command> or
simply "enter" instead of &enterkey;
(c)
po:167
auto: ⑤ Tag: para
Original: ⌘0 Press <command>ENTER</command>. This will load and
start the kernel. The kernel will display its usual initialization
messages followed by the first screen of the Debian Installer.
This string also doesn't use the &enterkey; entity, but shouldn't it
also use an entity for D-I ? &d-i;
- the Debian Installer.
+ &d-i;.
(d)
There are following strings which also are missing this entity.
(e)
Usage of CD-ROM is not consistent, either. In an early string in the
Manual, you state that "CD-ROM" can apply to any CD/DVD disc used,
thus establishing it as a defining class. Strings using "CD" or
"cdrom" instead of "CD-ROM" will thus confuse the reader. Use of
terms must be consistent.
9.
po:147
auto: ⑤ Tag: para
Original: ⌘0 These steps start the Debian boot loader which will
display a menu page for you to select a boot kernel and options.
Proceed to selecting the boot kernel and options.
This doesn't make sense: you're repeating yourself.
- Proceed to selecting the boot kernel and options.
+ Proceed to that menu page.
OR
+ Select the appropriate kernel and options for your system.
10.
po:151
auto: ⑤ Tag: para
Original: ⌘0 Select <command>EFI Shell</command> from the menu with
the arrow keys and press <command>ENTER</command>. The EFI Shell will
scan all of the bootable devices and display them to the console
before displaying its command prompt.<snip>
- and display them to the console
+ and display them via the console
11.
Different strings use "ia64" or "IA64". Shouldn't we choose one way
of writing it, and stick to that?
For example:
po:172
auto: ⑤ Tag: para
Original: ⌘0 A suitable TFTP entry for network booting an ia64
system looks something like this: <informalexample><screen>\n
host mcmuffin {\n
hardware ethernet 00:30:6e:1e:0e:83;\n
fixed-address 10.0.0.21;\n
filename \"debian-installer/ia64/elilo.efi\";\n
}\n
</screen></informalexample> Note that the goal is to get
<command>elilo.efi</command> running on the client.
and
Extract the <filename>netboot.tar.gz</filename> file into the
directory used as the root for your tftp server. Typical tftp root
directories include <filename>/var/lib/tftp</filename> and <filename>/
tftpboot</filename>. This will create a <filename>debian-installer</
filename> directory tree containing the boot files for an IA-64 system.
12.
po:209
auto: ⑤ Tag: para
Original: ⌘0 At the GEM desktop, start the Linux installation
process by double-clicking on the <guiicon>bootstra.prg</guiicon>
icon in the <filename>debian</filename> directory and clicking
<guibutton>Ok</guibutton> at the program options dialog box.
- At the GEM desktop
+ In the GEM desktop
- at the program options dialog box.
+ in the program options dialog box.
Neither of these are items local and individual enough to be "at".
You can be "at" a prompt or cursor position, but other items are too
large or diffuse to be "at". The preposition "at" implies a single
point or locus.
This also applies to the following strings:
.po:214
auto: ⑤ Tag: para
Original: ⌘0 At the MacOS desktop<snip>
po:232
auto: ⑤ Tag: para
Original: ⌘0 On the Broadcom BCM91250A <snip>
you can enter the following command on the CFE prompt:
<snip>
13.
This machine name is used in two forms:
po:246
auto: ⑤ Tag: title
Original: ⌘0 s390 Boot Parameters
po:247
auto: ⑤ Tag: para
Original: ⌘0 On S/390 you can append boot parameters<snip>
in several different strings. Surely we should use only one way of
writing this, to avoid confusion?
14.
po:269
auto: ⑤ Tag: para
Original: ⌘0 To boot from the <filename>boot-floppy-hfs.img</
filename> floppy, place it in floppy drive after shutting the system
down, and before pressing the power-on button.
- place it in floppy drive
+ place it in the floppy drive
15.
.po:276
auto: ⑤ Tag: para
Original: ⌘0 To boot from floppy on a Sparc, <snip>
- To boot from floppy
+ To boot from a floppy
16.
po:280
auto: ⑤ Tag: para
Original: ⌘0 If you cannot boot because you get messages about a
problem with <quote>IDPROM</quote>, then it's possible that your
NVRAM battery, which holds configuration information for you
firmware, has run out. See the <ulink url=\"&url-sun-nvram-faq;\">Sun
NVRAM FAQ</ulink> for more information.
- for you firmware
+ for your firmware
- has run out.
+ has died.
OR
+ is dead.
(This is the usual expression. Batteries don't "run out". They are
"empty" [if rechargeable], or "dead".)
17.
The installation report is difficult. I don't want to translate the
whole thing, because you won't be able to understand it when you
receive it. OTOH, it has to be translated. I've compromised by adding
translations to each part: this means the user can understand what s/
he has to do, and you can still make sense of the checkboxes and any
info in English.
I have added to the previous para. something like, "If you have
trouble writing English, please send your report to (our translation
mailing list), and we will translate for you. That way, you'll still
get reports, even if they can't write English, and we'll turn it into
English. This should make the difference between virtually no reports
from our community, and, this release being the first in our
language, at least some reports. Possibly quite a few. If I get
deluged in Vietnamese Installation Reports, I'll let you know. ;)
___________________________________
Clytie Siddall (vi-VN, Vietnamese free-software translation team /
nhóm Việt hóa phần mềm tự do)
