Patch1 to fix typos, commas, fullstops ( Re: Work on debian-faq? )
Hi,
Holger Wansing <hwansing@mailbox.org> wrote:
> Holger Wansing <linux@wansing-online.de> wrote:
> > There is a bugreport, filed by myself :-)
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788361
> > with a patch.
> >
> > It contains many typo fixes, missing or unnecessary commas/dots etc.
> > These changings should be indisputable, nothing to discuss about, so
> > I think they should get committed. (The above bugreport also contains
> > some other changings, which might be worth to discuss about, but I would
> > leave such changings out for this first step.)
> > I could provide a patch, which contains only that indisputable fixes,
> > where the fixes do not affect the translations. So I would also unfuzzy
> > the po files, to not bother the respective translators with that
> > (all active translations are po-based; there is only zh_CN which is
> > sgml-based, but that's heavily outdated already, so no need to care about
> > that).
> > Po-based translations are in a very good shape, nearly all are 100% translated,
> > so unfuzzying is easy.
> >
> >
> > What do you think?
> > Any objections for this?
> > Should I prepare the above mentioned patch?
>
> I have prepared this patch some days ago, and now I saw it is corrupted
> due to this commit:
> http://anonscm.debian.org/viewvc/ddp/manuals/trunk/debian-faq/basic_defs.sgml?r1=10448&r2=11070
>
> So I will prepare a patch once more, will provide it here, and then commit
> it 2 days later, if noone objects.
Here is the proposed patch.
Holger
--
============================================================
Created with Sylpheed 3.5.0 under
D E B I A N L I N U X 8 . 0 " J E S S I E " .
Registered Linux User #311290 - https://linuxcounter.net/
============================================================
Index: choosing.sgml
===================================================================
--- choosing.sgml (Revision 11052)
+++ choosing.sgml (Arbeitskopie)
@@ -58,11 +58,11 @@
am not aware of any such website for desktops.</p>
<p>Another option would be to ask in the debian-user mailing list by sending
-an email to debian-user@lists.debian.org . Messages can be posted to the list
+an email to debian-user@lists.debian.org. Messages can be posted to the list
even without subscribing. The archives can be read
-through <url id="http://lists.debian.org/debian-user/";> Information regarding
+through <url id="http://lists.debian.org/debian-user/";>. Information regarding
subscribing to the list can be found at the location of archives. You are
-strongly encourage to post your questions on the mailing-list than on <url
+strongly encouraged to post your questions on the mailing-list than on <url
id="http://www.debian.org/support"; name="irc">. The mailing-list messages are
archived, so solution to your problem can
help others with the same issue. </p>
@@ -98,7 +98,7 @@
If stability is required: install stable distribution. If you want to work
with the latest packages, then install unstable.</p>
-<sect1>If I were to decide to change to another distribution, Can I do
+<sect1>If I were to decide to change to another distribution, can I do
that?
<p>Yes, but it is a one way process. You can go from stable --> testing
@@ -167,7 +167,7 @@
<p>The idea is that, if the package has any problems, it would be discovered by
people using unstable and will be fixed before it enters testing. This keeps
the testing in an usable state for most period of the time. Overall a
-brilliant concept, if you ask me. But things are alwasy not so simple. Consider
+brilliant concept, if you ask me. But things are always not so simple. Consider
the following situation:</p>
<p><list>
@@ -174,13 +174,13 @@
<item>Imagine you are interested in package XYZ.
<item>Let's assume that on June
-10, the version in testing is XYZ-3.6 and in unstable it is XYZ-3.7
+10, the version in testing is XYZ-3.6 and in unstable it is XYZ-3.7.
<item>After 10 days, XYZ-3.7 from unstable migrates into
testing.
<item>So on June 20, both testing and unstable have
XYZ-3.7 in their repositories.
- <item>Let's say, The user of testing distribution sees
-that a new XYZ package is available and updates his XYZ-3.6 to XYZ-3.7
+ <item>Let's say, the user of testing distribution sees
+that a new XYZ package is available and updates his XYZ-3.6 to XYZ-3.7.
<item>Now on June 25, someone
using testing or unstable discovers an RC bug in XYZ-3.7 and files it
in the BTS.
@@ -192,11 +192,11 @@
<item>This new version in unstable, XYZ-3.8 is scheduled
to enter testing on July 10th.
<item>But on July 5th some other
-person, discovers another RC-bug in XYZ-3.8
+person discovers another RC-bug in XYZ-3.8.
<item>Let's say the maintainer of XYZ fixes this new
RC-bug and uploads new version of XYZ after 5 days.
<item>So on July 10, testing has XYZ-3.7 while unstable
-has XYZ-3.9
+has XYZ-3.9.
<item>This new version XYZ-3.9 is now rescheduled to
enter testing on July 20th.
<item>Now since you are running
@@ -211,12 +211,12 @@
The above scenario which is artificially created by me, can occur in the real
life. But such occurrences are rare.
-<sect1>From an administrator's point of view, Which distribution
+<sect1>From an administrator's point of view, which distribution
requires more attention?
<p>One of the main reasons many people chose Debian over other Linux distributions is
that it requires very little administration. People want a system that just works.
-In general one can say that, stable requires very little maintenance while
+In general one can say, that stable requires very little maintenance, while
testing and unstable require constant maintenance from the administrator. If you are
running stable, all you need to worry about is, keeping track of security
updates. If you are running either testing or unstable it is a good idea to be
@@ -247,10 +247,10 @@
sid
<item>Unstable is always referred to as sid irrespective of whether a
release is made or not.
- <item>packages constantly migrate from sid to testing (i.e. &testingreleasename;). But
+ <item>Packages constantly migrate from sid to testing (i.e. &testingreleasename;). But
packages in stable (i.e. &releasename;) remain the same except for security
updates.
- <item>after sometime testing becomes frozen. But it will still be called
+ <item>After some time testing becomes frozen. But it will still be called
testing. At this point no new packages from unstable can migrate to testing
unless they include release-critical (RC) bug fixes.
<item>When testing is frozen, all the new bugfixes introduced, have to be
@@ -257,9 +257,9 @@
manualy checked by the members of the release team. This is done to ensure
that there wont be any unknown severe problems in the frozen
testing.
- <item> RC bugs in 'frozen testing' are reduced to either zero or, if
+ <item>RC bugs in 'frozen testing' are reduced to either zero or, if
greater than zero, the bugs are either marked as ignored for the release or
- are deferred for a point release
+ are deferred for a point release.
<item>The 'frozen testing' with no rc-bugs will be released as the new
stable version. In our example, this new stable release will be called as
&testingreleasename;.
@@ -296,7 +296,7 @@
Codename: sid
</example>
-<p>However, this is always not that easy. Some systems might have
+<p>However, this is not always that easy. Some systems might have
<file>sources.list</file> files with
multiple entries corresponding to different distributions. This could
happen if the administrator is tracking different packages from different
@@ -395,7 +395,7 @@
with one distribution you should use that and not mix packages from other
distributions. Many common breakages arise due to people running a distribution
and trying to install Debian packages from other distributions. The fact that
-they use the same formatting and name (.deb) does not make them inmediately
+they use the same formatting and name (.deb), does not make them immediately
compatible.
<p>For example, Knoppix is a Linux distribution designed to be booted as a live CD where as
Index: compat.sgml
===================================================================
--- compat.sgml (Revision 11052)
+++ compat.sgml (Arbeitskopie)
@@ -42,7 +42,7 @@
<item><em/s390x/: 64-bit port for IBM System z machines intended to replace s390.
<item><em/sparc/: this covers Sun's SPARC and most UltraSPARC systems, and
-some of their successors in the sun4 architectures
+some of their successors in the sun4 architectures.
</list>
@@ -65,7 +65,7 @@
<em/alpha/ (Compaq/Digital's Alpha systems) were dropped
in the Squeeze (Debian 6.0) release for similar reasons. The
<em/arm/ was dropped too in this release, as it was superseded by
-the <em/armel/ arquitecture.
+the <em/armel/ architecture.
<p>For more information on the available ports see the
<url id="http://www.debian.org/ports/"; name="ports pages at the website">.
@@ -95,7 +95,7 @@
<item><em/avr32/, port to Atmel's 32-bit RISC architecture,
-<item><em/hurd-i386/ a port for 32-bit PC. This port will use GNU Hurd, the new
+<item><em/hurd-i386/, a port for 32-bit PC. This port will use GNU Hurd, the new
operating system being put together by the GNU group,
<item><em/sh/, port to Hitachi SuperH processors.
@@ -126,7 +126,7 @@
<p>&debian; supports software developed for the <url
id="http://www.linuxbase.org/"; name="Linux Standard Base">. The LSB is a
specification for allowing the same binary package to be used on multiple
-distributions. The Debian Etch release is Certified for LSB Release 3.1, see
+distributions. The Debian Etch release is certified for LSB Release 3.1, see
the <url name="Linux Foundation Certification webpage"
id="https://www.linux-foundation.org/lsb-cert/productdir.php";>.
Discussion and
Index: contrib.sgml
===================================================================
--- contrib.sgml (Revision 11052)
+++ contrib.sgml (Arbeitskopie)
@@ -7,7 +7,7 @@
or provide user support), resources (to mirror the FTP and WWW archives),
and money (to pay for new testbeds as well as hardware for the archives)
can help the project. See also
-<url name="How can you help Debian?" id="debian-help;">.
+<url name="How can you help Debian?" id="&debian-help;">.
<sect id="contrib">How can I become a Debian software developer?
Index: pkg_basics.sgml
===================================================================
--- pkg_basics.sgml (Revision 11052)
+++ pkg_basics.sgml (Arbeitskopie)
@@ -27,7 +27,7 @@
<tt>.diff.gz</tt> file that contains the Debian-specific changes to the
original source. The utility <tt>dpkg-source</tt> packs and unpacks
Debian source archives; details are provided in its manual page. (The
- program <prgn/apt-get/ can get used a frontend for <tt>dpkg-source</tt>.)
+ program <prgn/apt-get/ can get used as a frontend for <tt>dpkg-source</tt>.)
</list>
<p>Installation of software by the package system uses "dependencies" which
@@ -365,8 +365,8 @@
<p>Their meanings are:
<list>
- <item>unknown - the user has never indicated whether he wants the package
- <item>install - the user wants the package installed or upgraded
+ <item>unknown - the user has never indicated whether he wants the package.
+ <item>install - the user wants the package installed or upgraded.
<item>remove - the user wants the package removed, but does not want to
remove any existing configuration files.
<item>purge - the user wants the package to be removed completely,
@@ -442,11 +442,11 @@
<example>sudo apt-get build-dep foo</example>
Then create a dedicated version of your own build (so that you won't get
-confused later when Debian itself releases a new version)
+confused later when Debian itself releases a new version):
<example>dch -l local 'Blah blah blah'</example>
-And finally build your package
+And finally build your package:
<example>debuild -us -uc</example>
Index: pkgtools.sgml
===================================================================
--- pkgtools.sgml (Revision 11052)
+++ pkgtools.sgml (Arbeitskopie)
@@ -34,7 +34,7 @@
<list>
<item>Find out all the options: <tt>dpkg --help</tt>.
<item>Print out the control file (and other information) for a specified
- package: <tt>dpkg --info foo_VVV-RRR.deb</tt>
+ package: <tt>dpkg --info foo_VVV-RRR.deb</tt>.
<item>Install a package (including unpacking and configuring) onto the
file system of the hard disk: <tt>dpkg --install foo_VVV-RRR.deb</tt>.
<item>Unpack (but do not configure) a Debian archive into the file system
@@ -52,8 +52,8 @@
package name (e.g., foo), <em/not/ the name of a Debian archive file
(e.g., foo_VVV-RRR.deb).
<item>Extract a single file named "blurf" (or a group of files
- named "blurf*" from a Debian archive:
- <tt>dpkg --fsys-tarfile foo_VVV-RRR.deb | tar -xf - 'blurf*'</tt>
+ named "blurf*") from a Debian archive:
+ <tt>dpkg --fsys-tarfile foo_VVV-RRR.deb | tar -xf - 'blurf*'</tt>.
<item>Remove a package (but not its configuration files):
<tt>dpkg --remove foo</tt>.
<item>Remove a package (including its configuration files):
Index: software.sgml
===================================================================
--- software.sgml (Revision 11052)
+++ software.sgml (Arbeitskopie)
@@ -15,7 +15,7 @@
<item>TeX (LaTeX) and Lyx, dvips, Ghostscript,
<item>the Xorg windowing system, which provides a networked graphical user
interface for Linux, and countless X applications including the GNOME,
- KDE and Xfce desktop environments.
+ KDE and Xfce desktop environments,
<item>a full suite of networking applications, including servers for
Internet protocols such as HTTP (WWW), FTP, NNTP (news), SMTP and POP
(mail) and DNS (name servers); relational databases like PostgreSQL, MySQL;
@@ -76,7 +76,7 @@
you are planning on rebuilding Debian packages. This last task is rather easy
to do, as official packages have to include a list of the additional software
(besides the packages in <package>build-essential</package>) needed to build
-the pacakge, this is known as <tt>Build-Dependencies</tt>. To install all the
+the package, this is known as <tt>Build-Dependencies</tt>. To install all the
packages needed to build a given source package and then build said source
package you can just run:
Index: support.sgml
===================================================================
--- support.sgml (Revision 11052)
+++ support.sgml (Arbeitskopie)
@@ -122,7 +122,7 @@
<item>Do not use foul language; besides, some people receive the lists
via packet radio, where swearing is illegal.
<item>Make sure that you are using the proper list. <em/Never/ post your
- (un)subscription requests to the mailing list itself<footnote>Use the
+ (un)subscription requests to the mailing list itself.<footnote>Use the
debian-<var>list-subject</var>-REQUEST@lists.debian.org address for that.</footnote>
<item>See section <ref id="bugreport"> for notes on reporting bugs.
</list>
Index: uptodate.sgml
===================================================================
--- uptodate.sgml (Revision 11052)
+++ uptodate.sgml (Arbeitskopie)
@@ -65,12 +65,12 @@
before upgrading.
<p>For details, see the manual page <manref name="aptitude" section="8">,
-and the file <file>/usr/share/aptitude/README</file>
+and the file <file>/usr/share/aptitude/README</file>.
<sect1 id="apt">apt-get, dselect and apt-cdrom
<p>An alternative to <prgn/aptitude/ is <prgn/apt-get/ which is
-APT-based command-line tool (described previously in <ref id="apt-get">)
+APT-based command-line tool (described previously in <ref id="apt-get">).
<p>Both <prgn/apt-get/, the APT-based command-line tool for handling packages, and
<prgn/dselect/, provide a simple, safe way to install and upgrade packages.
@@ -202,7 +202,7 @@
<p>Yes. You can use <prgn>cron-apt</prgn>, this tool updates the system at
regular interval by using a cron job. By default it just updates the package
-list and download new packages without installing.
+list and downloads new packages without installing.
<p>Note: Automatic upgrade of packages is <strong/NOT/ recommended
in <em>testing</em> or <em>unstable</em> systems as this might bring unexpected
@@ -217,7 +217,7 @@
<p><prgn>apt-proxy</prgn> reduces the bandwidth requirements of Debian mirrors
by restricting the frequency of Packages, Releases and Sources file updates
from the back end and only doing a single fetch for any file, independently
-of the actual request it from the proxy. <prgn>apt-proxy</prgn> automatically
+of the actual request from the proxy. <prgn>apt-proxy</prgn> automatically
builds a Debian HTTP mirror based on requests which pass through the proxy.
<p>For more details, see the apt-proxy homepage at <url
Reply to: