Whitespace-only fixups for the committers and lists entities conversion.

This commit is contained in:
Peter Pentchev 2002-03-15 07:57:16 +00:00
parent eed41e97e6
commit 767c635e20
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=12472
7 changed files with 20 additions and 32 deletions

View file

@ -40,10 +40,9 @@
create applications that work in all the languages create applications that work in all the languages
out-of-the-box without dirty hacks.</para> out-of-the-box without dirty hacks.</para>
<para>The &a.i18n; <para>The &a.i18n; has been established. If you are an I18N/L10N
has been established. If you are an I18N/L10N developer, developer, please send your comments, ideas, questions, and
please send your comments, ideas, questions, and anything anything you deem related to it.</para>
you deem related to it. </para>
<para> Michael C. Wu will be maintaining an I18N works in progress <para> Michael C. Wu will be maintaining an I18N works in progress
homepage at <ulink homepage at <ulink

View file

@ -2215,16 +2215,11 @@ disk wd2 at wdc1 drive 1 # change from wd3 to wd2</programlisting
<para>Yes. FreeBSD currently runs on both Intel x86 and <para>Yes. FreeBSD currently runs on both Intel x86 and
DEC (now Compaq) Alpha architectures. Interest has also DEC (now Compaq) Alpha architectures. Interest has also
been expressed in a port of FreeBSD to the SPARC architecture, been expressed in a port of FreeBSD to the SPARC architecture,
join the &a.sparc; join the &a.sparc; if you are interested in joining that project.
if you are interested Most recent additions to the list of upcoming platforms are
in joining that project. Most recent additions to the list of IA-64 and PowerPC, join the &a.ia64; and/or the &a.ppc; for more
upcoming platforms are IA-64 and PowerPC, join the information. For general discussion on new architectures, join
&a.ia64; and/or the the &a.platforms;.</para>
&a.ppc;
for more information.
For general discussion on new architectures, join
the &a.platforms;.
</para>
<para>If your machine has a different architecture and you need <para>If your machine has a different architecture and you need
something right now, we suggest you look at <ulink something right now, we suggest you look at <ulink

View file

@ -47,8 +47,7 @@
that would just reiterate the documentation for each language. The aim of that would just reiterate the documentation for each language. The aim of
this section is to list those elements more likely to be useful to you. this section is to list those elements more likely to be useful to you.
If you have a question about how best to markup a particular piece of If you have a question about how best to markup a particular piece of
content, please post it to the content, please post it to the &a.doc;.</para>
&a.doc;.</para>
<note> <note>
<title>Inline vs. block</title> <title>Inline vs. block</title>

View file

@ -177,8 +177,7 @@
<para>The Handbook's organisation may change over time, and this <para>The Handbook's organisation may change over time, and this
document may lag in detailing the organisational changes. If you document may lag in detailing the organisational changes. If you
have any questions about how the Handbook is organised, please have any questions about how the Handbook is organised, please
contact the contact the &a.doc;.</para>
&a.doc;.</para>
</note> </note>
<sect4> <sect4>

View file

@ -266,9 +266,8 @@
</variablelist> </variablelist>
<para>If anyone has recommendations for other software that is useful <para>If anyone has recommendations for other software that is useful
when manipulating SGML documents, please let &a.nik; when manipulating SGML documents, please let &a.nik; know, so they
know, so they can be added to this can be added to this list.</para>
list.</para>
</sect2> </sect2>
</sect1> </sect1>
</chapter> </chapter>

View file

@ -178,9 +178,9 @@
help.</para> help.</para>
<para>If no one is listed on that page as translating for your <para>If no one is listed on that page as translating for your
language, then send a message to language, then send a message to the &a.doc; in case someone else
the &a.doc; in case someone else is is thinking of doing a translation, but has not announced it yet.
thinking of doing a translation, but has not announced it yet.</para> </para>
</answer> </answer>
</qandaentry> </qandaentry>
@ -290,9 +290,8 @@
<para>Put <filename>swedish-docs.tar.gz</filename> somewhere. If you <para>Put <filename>swedish-docs.tar.gz</filename> somewhere. If you
do not have access to your own webspace (perhaps your ISP does not do not have access to your own webspace (perhaps your ISP does not
let you have any) then you can e-mail let you have any) then you can e-mail &a.nik;, and arrange to e-mail
&a.nik;, and arrange to e-mail the files the files when it is convenient.</para>
when it is convenient.</para>
<para>Either way, you should use &man.send-pr.1; to submit a report <para>Either way, you should use &man.send-pr.1; to submit a report
indicating that you have submitted the documentation. It would be indicating that you have submitted the documentation. It would be
@ -301,9 +300,8 @@
person committing it will be fluent in the language.</para> person committing it will be fluent in the language.</para>
<para>Someone (probably the Documentation Project Manager, currently <para>Someone (probably the Documentation Project Manager, currently
&a.nik;) will then take your &a.nik;) will then take your translation and confirm that it builds.
translation and confirm that it builds. In particular, the In particular, the following things will be looked at:</para>
following things will be looked at:</para>
<orderedlist> <orderedlist>
<listitem> <listitem>

View file

@ -607,8 +607,7 @@ help
Ongoing irrelevant chatter or flaming only detracts from the value Ongoing irrelevant chatter or flaming only detracts from the value
of the mailing list for everyone on it and will not be tolerated. of the mailing list for everyone on it and will not be tolerated.
For free-form discussion on no particular topic, the &a.chat; For free-form discussion on no particular topic, the &a.chat;
is freely is freely available and should be used instead.</para>
available and should be used instead.</para>
</listitem> </listitem>
<listitem> <listitem>