Your message dated Mon, 01 May 2006 01:35:06 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#365319: installation-guide: install-methods.po
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: installation-guide
Version:
Severity: minor
Tags: l10n, patch
Here are some typos etc. from the file install-methods.po
___
1.
.po:29
reference: ⑤ install-methods.xml:263
flag: ⑤ no-c-format
auto: ⑤ Tag: para
Original: ⌘0 If you can't boot (IPL) from the CD-ROM and you are not
using VM you need to create an IPL tape first. This is described in
section 3.4.3 in the <ulink url=\"http://www.redbooks.ibm.com/pubs/
pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/
390: Distributions</ulink> Redbook. The files you need to write to
the tape are (in this order): <filename>kernel.debian</filename>,
<filename>parmfile.debian</filename> and <filename>initrd.debian</
filename>. The files can be downloaded from the <filename>tape</
filename> sub-directory, see <xref linkend=\"where-files\"/>,
This para. ends with a comma. Is that correct?
2.
po:32
reference: ⑤ install-methods.xml:293
flag: ⑤ no-c-format
auto: ⑤ Tag: para
Original: ⌘0 Floppy disk booting reportedly fails on Mac USB floppy
drives.
.po:33
reference: ⑤ install-methods.xml:297
flag: ⑤ no-c-format
auto: ⑤ Tag: para
Original: ⌘0 Floppy disk booting is not supported on Amigas or 68k
Macs.
In both these cases, I think you need to say:
- Floppy disk booting
+ Floppy-disk booting Debian
because other translators and users might read that, as I did, that
these machines don't support booting from floppy disks _at all_.
And I know that's not true, because I've had 68k Macs, and you can
boot the MacOS from floppies. In fact, in the early ones, you have
to! The earlier ones didn't come with a CD-drive.
If you're using nouns as adjectives, i.e. to describe other nouns,
it's best to use a hyphen to indicate that.
I have an orange juice-glass.
I have an orange-juice glass.
3.
po:35
reference: ⑤ install-methods.xml:313
flag: ⑤ no-c-format
auto: ⑤ Tag: para
Original: ⌘0 There are different techniques for creating floppies
from disk images, which depend on your platform. This section
describes how to create floppies from disk images on different
platforms.
You're saying the same thing twice, here.
- This section describes how to create floppies from disk images on
different platforms.
+ This section describes some of these platform-specific techniques.
4.
po:67
reference: ⑤ install-methods.xml:586
flag: ⑤ no-c-format
auto: ⑤ Tag: para
Original: ⌘0 For preparing the USB stick you will need a system
where GNU/Linux is already running and where USB is supported. You
should ensure that the usb-storage kernel module is loaded
(<userinput>modprobe usb-storage</userinput>) and try to find out
which SCSI device the USB stick has been mapped to (in this example
<filename>/dev/sda</filename> is used). To write to your stick, you
will probably have to turn off its write protection switch.
- For preparing the USB stick you
+ To prepare the USB stick, you
- turn off its write protection switch.
+ disable its write protection switch.
5.
po:68
reference: ⑤ install-methods.xml:596
flag: ⑤ no-c-format
auto: ⑤ Tag: para
Original: ⌘0 Note, that the USB stick should be at least 128 MB in
size (smaller setups are possible if you follow <xref linkend=\"usb-
copy-flexible\"/>).
- Note, that
+ Note that
6.
.po:80
reference: ⑤ install-methods.xml:667
flag: ⑤ no-c-format
auto: ⑤ Tag: para
Original: ⌘0 Since most USB sticks come pre-configured with a single
FAT16 partition, you probably won't have to repartition or reformat
the stick. If you have to do that anyway, use <command>cfdisk</
command> or any other partitioning tool for creating a FAT16
partition and then create the filesystem using:<snip>
- If you have to do that anyway, use <command>cfdisk</command> or
any other partitioning tool for creating a FAT16 partition and then
create the filesystem
+ If you have to do that anyway, use <command>cfdisk</command> or
any other partitioning tool for creating a FAT16 partition, and then
create the filesystem
OR
+ If you have to do that anyway, use <command>cfdisk</command> or
any other partitioning tool to create a FAT16 partition, and then
create the filesystem
These don't mean the same thing. The first + item means that the
partitioning tools are _for_ creating FAT16 partitions, not that you
are explictly supposed to do so. The second item says you are
explicitly supposed to create that partition, using one of those
tools. Currently, the meaning of the sentence is unclear.
7.
.po:96
reference: ⑤ install-methods.xml:844
flag: ⑤ no-c-format
auto: ⑤ Tag: para
Original: ⌘0 Now you should put any Debian ISO image (businesscard,
netinst or even a full one) onto your stick (if it fits). The file
name of such an image must end in <filename>.iso</filename>.
- Now you should put any Debian ISO image
+ Now, put a Debian ISO image
The article "a" indicates any image you choose.
- The file name of such an image
+ The filename of this image
8.
po:125
reference: ⑤ install-methods.xml:1046
flag: ⑤ no-c-format
auto: ⑤ Tag: para
Original: ⌘0 Make a note of the partition number of the MacOS
partition where you place these files. If you have the MacOS
<command>pdisk</command> program, you can use the L command to check
for the partition number. You will need this partition number for the
command you type at the Open Firmware prompt when you boot the
installer.
- you can use the L command
+ you can use the <command>L</command> command
9.
po:143
reference: ⑤ install-methods.xml:1218
flag: ⑤ no-c-format
auto: ⑤ Tag: para
Original: ⌘0 To use CMU <command>bootpd</command>, you must first
uncomment (or add) the relevant line in <filename>/etc/inetd.conf</
filename>. On &debian;, you can run <userinput>update-inetd --enable
bootps</userinput>, then <userinput>/etc/init.d/inetd reload</
userinput> to do so. Elsewhere, the line in question should look
like: <informalexample><screen>\n
What do you mean by "Elsewhere"? Another place? (What place?)
Or do you mean "Else" = "If not"?
Does it mean "under other operating systems"? If so, it would be
clearer to say so, since "elsewhere" is specific to location, not type.
- Elsewhere, the line in question should look like
+ Under other operating systems, the line in question should look like
Or do you mean something else? :S
10.
po:161
reference: ⑤ install-methods.xml:1409
flag: ⑤ no-c-format
auto: ⑤ Tag: para
Original: ⌘0 For DECstations, there are tftpimage files for each
subarchitecture, which contain both kernel and installer in one file.
The naming convention is <replaceable>subarchitecture</replaceable>/
netboot-boot.img. Copy the tftpimage file you would like to use to
<userinput>/tftpboot/tftpboot.img</userinput> if you work with the
example BOOTP/DHCP setups described above.
- <replaceable>subarchitecture</replaceable>/netboot-boot.img.
+ <filename><replaceable>subarchitecture</replaceable>/netboot-
boot.img</filename>.
11.
po:168
reference: ⑤ install-methods.xml:1487
flag: ⑤ no-c-format
auto: ⑤ Tag: para
Original: ⌘0 SPARC architectures for instance use the
subarchitecture names, such as <quote>SUN4M</quote> or <quote>SUN4C</
quote>; in some cases, the architecture is left blank, so the file
the client looks for is just <filename>client-ip-in-hex</filename>.
Thus, if your system subarchitecture is a SUN4C, and its IP is
192.168.1.3, the filename would be <filename>C0A80103.SUN4C</
filename>. An easy way to determine this is to enter the following
command in a shell (assuming the machine's intended IP is 10.0.0.4).
<informalexample><screen>\n
$ printf '%.2x%.2x%.2x%.2x\\n' 10 0 0 4\n
</screen></informalexample> This will spit out the IP in hexadecimal;
to get to the correct filename, you will need to change all letters
to uppercase and if necessary append the subarchitecture name.
- SPARC architectures for instance use the subarchitecture names,
such as <quote>SUN4M</quote> or <quote>SUN4C</quote>; in some cases,
the architecture is left blank
+ Some SPARC architectures use subarchitecture names like
<quote>SUN4M</quote> or <quote>SUN4C</quote>, while others leave the
architecture blank
12.
po:176
reference: ⑤ install-methods.xml:1547
flag: ⑤ no-c-format
auto: ⑤ Tag: para
Original: ⌘0 You don't have to configure DHCP in a special way
because you'll pass the full path of the file to the loaded to CFE.
- to the loaded
+ to be loaded
___
I hope this is useful. :)
Clytie Siddall (vi-VN, Vietnamese free-software translation team /
nhóm Việt hóa phần mềm tự do)
--- End Message ---
--- Begin Message ---
On Saturday 29 April 2006 09:39, Clytie Siddall wrote:
> Here are some typos etc. from the file install-methods.po
Most of them fixed, some rewritten. With one exception:
> - turn off its write protection switch.
> + disable its write protection switch.
Don't agree. "Disabling" a switch means that it no longer matters if it is
on or off.
Thanks again.
--- End Message ---
