Your message dated Mon, 19 Mar 2007 00:57:26 +0100 with message-id <20070318235726.GA2943@javifsp.no-ip.org> and subject line Typos fixed 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 ---
- To: submit@bugs.debian.org
- Subject: release-notes
- From: Clytie Siddall <clytie@riverland.net.au>
- Date: Tue, 9 Jan 2007 17:43:27 +1030
- Message-id: <AA05E161-8CB4-4441-8702-4FDEA3AC1414@riverland.net.au>
Package: release-notes Version: Severity: wishlist Tags: l10n, patchWhile updating my translation of the release-notes, I have encountered the following typos, which I thought you might like to fix before the next release.___ 1. po:9 Translator: ③ type: <p></p>Original: ⌘0 The most recent version of this document is always available at <url id=\"&url-release-notes;\">. If your version is more than a month old, you might wish to download the latest version.] - version.] + version. 2. po:95 Translator: ③ type: <p></p>Original: ⌘0 You have to make sure before upgrading your system that you have sufficient hard disk space when you start the full system upgrade described in <ref id= \"upgrading_other\">. You will first need enough hard disk on the filesystem partition that holds <file>/var/</file> to temporarily download the packages that will be installed in your system. After the download, you will probablyneed more space in other filesystem partitions in order to both installupgraded packages (which might contain bigger binaries or more data) and newpackages that will be pulled in for the upgrade. If your system does nothave sufficient space you might end up with an incomplete upgrade that mightbe difficult to recover from. +Before upgrading your system, you have to make sure you have sufficient hard-disk space to start the full-system upgrade described in <ref id=\"upgrading_other\">. To start with, in the filesystem partition containing <file>/var/</file>, you need enough hard-disk space to download temporarily all the packages which will be installed on your system. After the download, in other filesystem partitions, you will probably need more space to install both the upgraded packages (which can contain larger binaries or more data) and the new packages required for the upgrade. If your system does not have enough space for these processes, you may end up with an incomplete upgrade, a difficult situation to fix.3. po:96 Translator: ③ type: <p></p>Original: ⌘0 Both <prgn>aptitude</prgn> and <prgn>apt</prgn> will show you detailed information of the disk space needed for the installation. You can see thisestimate before executing the actual upgrade running: - information of the disk space + information about the disk space - You can see this estimate before executing the actual upgrade running: + Before executing the upgrade, you can see this estimate by running: 4. po:100 Translator: ③ type: <p></p>Original: ⌘0 Remove old packages you no longer use. If you have <prgn>popularity-contest</ prgn> installed you can use <prgn>popcon-largest-unused</prgn> to list the packages you do not use in the system that occupy the most space. You can also use <prgn>deborphan</prgn> or <prgn>debfoster</prgn> to find obsoletepackages (see <ref id=\"obsolete\">) - installed you can use + installed, you can use - (see <ref id=\"obsolete\">) + (see <ref id=\"obsolete\">). 5. po:101 Translator: ③ type: <p></p>Original: ⌘0 Remove packages that take up too much space and you do not have an immediateneed for (you can always reinstall them after the upgrade). You can list packages that take up most of the disk space with <prgn>dpigs</prgn>(available in the <prgn>debian-goodies</prgn> package) or with <prgn>wajig</prgn> (running <prgn>wajig size</prgn>).- Remove packages that take up too much space and you do not have an immediateneed for+ Remove packages taking up too much space, which are not currently needed- You can list packages that take up most of the disk space with + You can list the packages taking up most of the disk space with 6. .po:104 Translator: ③ type: <p></p>Original: ⌘0 In case you run a kernel prior to 2.4.1, you need to upgrade to (at least) the 2.4-series before upgrading the <package>glibc</package>, which means: best before starting with the upgrade. It is recommended to upgrade to the2.6-kernel series. - which means: best before starting with the upgrade. + so preferably before starting the upgrade. 7. po:209 Translator: ③ type: <p></p>Original: ⌘0 If you are currently using a kernel from the 2.4 series, the older stable Linux kernel series, you should upgrade to a 2.6 series kernel, as 2.4 is no longer supported in &releasename;. If you are currently using a kernel from the 2.2 series, you must upgrade to (at least) the 2.4 series, better to a2.6 series kernel prior to upgrading your packages. Some general issuesassociated with an upgrade to 2.6 are documented in <ref id=\"upgrade- to-2.6\">. - better to a 2.6 series kernel prior to + preferably to a 2.6 series kernel, prior to 8. po:211 Translator: ③ type: <p></p>Original: ⌘0 <package>initrd-tools</package> is no longer supported and has beensuperseded by <package>initramfs-tools</package> and <package>yaird</package>. Upgrading to an &releasename; kernel will cause <package>initramfs- tools</package> to be installed by default. <![ %defaulted-2.4 [ If you are upgrading from a 2.4 kernel to a 2.6 kernel for the first time, you must use<package>initramfs-tools</package>. Using <package>yaird</package> willcause linux-image-2.6 installations to fail if you are running a 2.2 or 2.4kernel. ]]> - cause linux-image-2.6 installations + cause <package>linux-image-2.6</package> installations ? 9. .po:213 Translator: ③ type: <p></p>Original: ⌘0 &releasename; no longer provides support for <prgn>devfs</prgn>. It isrecommended that users switch to udev for dynamic <file>/dev</file>management. Debian kernels no longer include support for <prgn>devfs</ prgn>,so <prgn>devfs</prgn> users will need to manually convert their systems before upgrading to an &releasename; kernel. - switch to udev + switch to <prgn>udev </prgn> - to manually convert their systems + to convert their systems manually - Debian + &debian; (?) 10. po:214 Translator: ③ type: <p></p>Original: ⌘0 If you see the string 'devfs' in <file>/proc/mounts</ file>, you are likely using devfs. Any config files that reference devfs style names will need to be adjusted to use udev style names. Files that are most likely to refer to devfs style device names include <file>/etc/fstab</file>, <file>/etc/ lilo.conf</file>, <file>/boot/grub/menu.lst</file>, etc. - 'devfs' + <quote>devfs</quote> (correct tag?) - you are likely using devfs. + you are most likely using <prgn>devfs</prgn>. OR + you are probably using <prgn>devfs</prgn>. - Any config files that reference devfs style names will need tobe adjusted to use udev style names. Files that are most likely to refer to devfs style device names include <file>/etc/fstab</file>, <file>/etc/ lilo.conf</file>, <file>/boot/grub/menu.lst</file>, etc.+ Any config files that reference <prgn>devfs</prgn> style names will need to be adjusted to use <prgn>udev</prgn> style names. Files that are most likely to refer to <prgn>devfs</prgn> style device names include <file>/etc/fstab</file>, <file>/etc/lilo.conf</file> and <file>/boot/ grub/menu.lst</file>.(Note: you can use "include" or "etc." but not both, since "include" means "here are some specific examples", and "etc." means "and the rest". These two expressions are mutually exclusive. "e.g." is similar to "include", so "e.g." and "etc." are also mutually exclusive.)ppl11. po:216 Translator: ③ type: <heading></heading> Original: ⌘0 Standard kernels contain SMP abilities + Standard kernels have SMP capacity.(People have abilities. Non-living things have capacities, features, functions etc.)12. po:266 Translator: ③ type: <p></p>Original: ⌘0 Since 2.6.17, Linux uses TCP window scaling which is specified in RFC 1323in an aggressive way. Some servers have a broken behaviour, and announcewrong window sizes for themselves. Please see the bugs <url id= \"http://bugs.debian.org/381262\" name=\"#381262\"> and <url id=\"http://bugs.debian. org/395066\" name=\"#395066\"> for more information.- Since 2.6.17, Linux uses TCP window scaling which is specified in RFC 1323in an aggressive way.+ Since 2.6.17, Linux aggressively ,uses TCP window scaling which is specified in RFC 1323.(Otherwise, you're saying that it's mentioned aggressively in the RFC.) 13.There are quite a few terms which should have tags, e.g. program names without <prgn>, filenames without <file>, "Debian" instead of "&debian;", but I don't have time to document them all, sorry.14. po:302 Translator: ③ type: <p></p>Original: ⌘0 exim (version 3.xx) has been unmaintained upstream for years, and Debian has dropped support for that version as well. If you are still using exim 3.xx,please upgrade your exim installation to exim4 manually. Since exim4 isalready part of &oldreleasename, you can choose to do the upgrade on your &oldreleasename; system before the upgrade to &releasename;, or after the &releasename; upgrade at your convenience. Just remember that your old exim package is not going to be upgraded and that it won't get security supportafter support for &oldreleasename; will be discontinued. - exim + <prgn>exim</prgn> - exim4 + <prgn>exim4</prgn> - already part of &oldreleasename, + already part of &oldreleasename;, - after support for &oldreleasename; will be discontinued. + after support for &oldreleasename; is discontinued. OR + after support for &oldreleasename; has been discontinued. ___ 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)Attachment: PGP.sig
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
- To: 406161-close@bugs.debian.org
- Subject: Typos fixed
- From: Javier Fernández-Sanguino Peña <jfs@computer.org>
- Date: Mon, 19 Mar 2007 00:57:26 +0100
- Message-id: <20070318235726.GA2943@javifsp.no-ip.org>
- Mail-followup-to: 406161-close@bugs.debian.org
I've reviewed this bug report and fixed all the typos pointed out in it. Thanks for reviewing the Release Notes! JavierAttachment: signature.asc
Description: Digital signature
--- End Message ---