Whitespace-only fixups for the committers and lists entities conversion.
This commit is contained in:
Peter Pentchev
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
|
|
@ -40,10 +40,9 @@
|
|||
create applications that work in all the languages
|
||||
out-of-the-box without dirty hacks.</para>
|
||||
|
||||
<para>The &a.i18n;
|
||||
has been established. If you are an I18N/L10N developer,
|
||||
please send your comments, ideas, questions, and anything
|
||||
you deem related to it. </para>
|
||||
<para>The &a.i18n; has been established. If you are an I18N/L10N
|
||||
developer, please send your comments, ideas, questions, and
|
||||
anything you deem related to it.</para>
|
||||
|
||||
<para> Michael C. Wu will be maintaining an I18N works in progress
|
||||
homepage at <ulink
|
||||
|
|
|
|||
|
|
@ -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
|
||||
DEC (now Compaq) Alpha architectures. Interest has also
|
||||
been expressed in a port of FreeBSD to the SPARC architecture,
|
||||
join the &a.sparc;
|
||||
if you are interested
|
||||
in joining that project. Most recent additions to the list of
|
||||
upcoming platforms are IA-64 and PowerPC, join the
|
||||
&a.ia64; and/or the
|
||||
&a.ppc;
|
||||
for more information.
|
||||
For general discussion on new architectures, join
|
||||
the &a.platforms;.
|
||||
</para>
|
||||
join the &a.sparc; if you are interested in joining that project.
|
||||
Most recent additions to the list of upcoming platforms are
|
||||
IA-64 and PowerPC, join the &a.ia64; and/or the &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
|
||||
something right now, we suggest you look at <ulink
|
||||
|
|
|
|||
|
|
@ -47,8 +47,7 @@
|
|||
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.
|
||||
If you have a question about how best to markup a particular piece of
|
||||
content, please post it to the
|
||||
&a.doc;.</para>
|
||||
content, please post it to the &a.doc;.</para>
|
||||
|
||||
<note>
|
||||
<title>Inline vs. block</title>
|
||||
|
|
|
|||
|
|
@ -177,8 +177,7 @@
|
|||
<para>The Handbook's organisation may change over time, and this
|
||||
document may lag in detailing the organisational changes. If you
|
||||
have any questions about how the Handbook is organised, please
|
||||
contact the
|
||||
&a.doc;.</para>
|
||||
contact the &a.doc;.</para>
|
||||
</note>
|
||||
|
||||
<sect4>
|
||||
|
|
|
|||
|
|
@ -266,9 +266,8 @@
|
|||
</variablelist>
|
||||
|
||||
<para>If anyone has recommendations for other software that is useful
|
||||
when manipulating SGML documents, please let &a.nik;
|
||||
know, so they can be added to this
|
||||
list.</para>
|
||||
when manipulating SGML documents, please let &a.nik; know, so they
|
||||
can be added to this list.</para>
|
||||
</sect2>
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
|
|
|||
|
|
@ -178,9 +178,9 @@
|
|||
help.</para>
|
||||
|
||||
<para>If no one is listed on that page as translating for your
|
||||
language, then send a message to
|
||||
the &a.doc; in case someone else is
|
||||
thinking of doing a translation, but has not announced it yet.</para>
|
||||
language, then send a message to the &a.doc; in case someone else
|
||||
is thinking of doing a translation, but has not announced it yet.
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
|
|
@ -290,9 +290,8 @@
|
|||
|
||||
<para>Put <filename>swedish-docs.tar.gz</filename> somewhere. If you
|
||||
do not have access to your own webspace (perhaps your ISP does not
|
||||
let you have any) then you can e-mail
|
||||
&a.nik;, and arrange to e-mail the files
|
||||
when it is convenient.</para>
|
||||
let you have any) then you can e-mail &a.nik;, and arrange to e-mail
|
||||
the files when it is convenient.</para>
|
||||
|
||||
<para>Either way, you should use &man.send-pr.1; to submit a report
|
||||
indicating that you have submitted the documentation. It would be
|
||||
|
|
@ -301,9 +300,8 @@
|
|||
person committing it will be fluent in the language.</para>
|
||||
|
||||
<para>Someone (probably the Documentation Project Manager, currently
|
||||
&a.nik;) will then take your
|
||||
translation and confirm that it builds. In particular, the
|
||||
following things will be looked at:</para>
|
||||
&a.nik;) will then take your translation and confirm that it builds.
|
||||
In particular, the following things will be looked at:</para>
|
||||
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
|
|
|
|||
|
|
@ -607,8 +607,7 @@ help
|
|||
Ongoing irrelevant chatter or flaming only detracts from the value
|
||||
of the mailing list for everyone on it and will not be tolerated.
|
||||
For free-form discussion on no particular topic, the &a.chat;
|
||||
is freely
|
||||
available and should be used instead.</para>
|
||||
is freely available and should be used instead.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
|
|
|||
Loading…
Reference in a new issue