Standardize:
FreeBSD ports collection -> FreeBSD Ports Collection Ports collection -> ports collection These changes look the most appropriate and appear in the handbook this way. Reviewed by: murray
This commit is contained in:
parent
d270c61df9
commit
91f3c93359
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=10053
6 changed files with 24 additions and 24 deletions
en_US.ISO8859-1/books/handbook
basics
l10n
mail
mirrors
ports
printing
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/basics/chapter.sgml,v 1.30 2001/07/19 01:11:44 chern Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/basics/chapter.sgml,v 1.31 2001/07/19 23:18:05 chern Exp $
|
||||
-->
|
||||
|
||||
<chapter id="basics">
|
||||
|
@ -450,7 +450,7 @@
|
|||
<para>FreeBSD also comes with more powerful text editors such as
|
||||
<command>vi</command> as part of the base system, and
|
||||
<command>emacs</command> and <command>vim</command>
|
||||
as part of the FreeBSD ports collection. These editors offer much
|
||||
as part of the FreeBSD Ports Collection. These editors offer much
|
||||
more functionality and power at the expense of being a little more
|
||||
complicated to learn. However if you plan on doing a lot of text
|
||||
editing, learning a more powerful editor such as
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/l10n/chapter.sgml,v 1.61 2001/07/24 10:09:10 ache Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/l10n/chapter.sgml,v 1.62 2001/07/25 06:00:15 ache Exp $
|
||||
-->
|
||||
|
||||
<chapter id="l10n">
|
||||
|
@ -956,7 +956,7 @@ Option "XkbOptions" "grp:caps_toggle"</programlisting>
|
|||
<tbody>
|
||||
<row>
|
||||
<entry>outta-port tag=.</entry>
|
||||
<entry>Beta-quality Ports Collection for Chinese</entry>
|
||||
<entry>Beta-quality ports collection for Chinese</entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/mail/chapter.sgml,v 1.23 2001/06/28 14:40:27 murray Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/mail/chapter.sgml,v 1.24 2001/07/20 23:24:54 chern Exp $
|
||||
-->
|
||||
|
||||
<chapter id="mail">
|
||||
|
@ -139,7 +139,7 @@
|
|||
<procedure>
|
||||
<step>
|
||||
<para>Get a POP or IMAP daemon from the <ulink
|
||||
url="/ports/mail.html">Ports Collection</ulink> and install
|
||||
url="/ports/mail.html">ports collection</ulink> and install
|
||||
it on your system.</para>
|
||||
</step>
|
||||
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml,v 1.136 2001/07/21 20:22:58 jesper Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml,v 1.137 2001/07/23 22:51:32 chern Exp $
|
||||
-->
|
||||
|
||||
<appendix id="mirrors">
|
||||
|
@ -2419,7 +2419,7 @@ src-all</programlisting>
|
|||
<term><literal>ports-all release=cvs</literal></term>
|
||||
|
||||
<listitem>
|
||||
<para>The FreeBSD ports collection.</para>
|
||||
<para>The FreeBSD Ports Collection.</para>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/ports/chapter.sgml,v 1.130 2001/07/21 19:26:13 jdp Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/ports/chapter.sgml,v 1.131 2001/07/25 20:12:59 chern Exp $
|
||||
-->
|
||||
|
||||
<chapter id="ports">
|
||||
|
@ -426,7 +426,7 @@ docbook =
|
|||
<secondary>installing</secondary>
|
||||
</indexterm>
|
||||
<para>The first thing that should be explained
|
||||
when it comes to the Ports collection is what is actually meant
|
||||
when it comes to the ports collection is what is actually meant
|
||||
by a <quote>skeleton</quote>. In a nutshell, a port skeleton is a
|
||||
minimal set of files that are needed for a program to compile and
|
||||
install cleanly on FreeBSD. Each port skeleton includes:</para>
|
||||
|
@ -478,7 +478,7 @@ docbook =
|
|||
</itemizedlist>
|
||||
|
||||
<para>Now that you have enough background information to know what
|
||||
the Ports collection is used for, you are ready to install your
|
||||
the ports collection is used for, you are ready to install your
|
||||
first port. There are two ways this can be done, and each is
|
||||
explained below.</para>
|
||||
|
||||
|
@ -505,7 +505,7 @@ lsof: /usr/ports/sysutils/lsof</screen>
|
|||
<filename>/usr/ports/sysutils/lsof</filename> directory.</para>
|
||||
|
||||
<para>Yet another way of finding a particular port is by using the
|
||||
Ports collection's built-in search mechanism. To use the search
|
||||
ports collection's built-in search mechanism. To use the search
|
||||
feature, you will need to be in the
|
||||
<filename>/usr/ports</filename> directory. Once in that
|
||||
directory, run <command>make search key=program-name</command>
|
||||
|
@ -724,7 +724,7 @@ Receiving lsof_4.57D.freebsd.tar.gz (439860 bytes): 100%
|
|||
<title>Troubleshooting</title>
|
||||
|
||||
<para>The following sections cover some of the more frequently asked
|
||||
questions about the Ports collection and some basic troubleshooting
|
||||
questions about the ports collection and some basic troubleshooting
|
||||
techniques, and what do to if a <link
|
||||
linkend="ports-broken">port is broken.</link></para>
|
||||
|
||||
|
@ -918,7 +918,7 @@ Receiving lsof_4.57D.freebsd.tar.gz (439860 bytes): 100%
|
|||
</question>
|
||||
|
||||
<answer>
|
||||
<para>To get every single tarball for the Ports collection,
|
||||
<para>To get every single tarball for the ports collection,
|
||||
do:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /usr/ports</userinput>
|
||||
|
@ -1212,7 +1212,7 @@ arcade game.</screen>
|
|||
<qandaentry>
|
||||
<question>
|
||||
<para>At work, we are using <literal>frobble</literal>, which
|
||||
is in your Ports collection, but we have altered it quite a
|
||||
is in your ports collection, but we have altered it quite a
|
||||
bit to get it to do what we need. Is there any way of making
|
||||
our own packages, so we can distribute it more easily around
|
||||
our sites?</para>
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/printing/chapter.sgml,v 1.40 2001/07/20 23:25:02 chern Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/printing/chapter.sgml,v 1.41 2001/07/21 09:13:55 murray Exp $
|
||||
-->
|
||||
|
||||
<chapter id="printing">
|
||||
|
@ -1351,7 +1351,7 @@ $%&'()*+,-./01234567
|
|||
printers that can print plain text. (It handles backspacing and tabs
|
||||
in the file, and does accounting, but that is about all it does.)
|
||||
There are also several filters and filter components in the FreeBSD
|
||||
ports collection.</para>
|
||||
Ports Collection.</para>
|
||||
|
||||
<para>Here is what you will find in this section:</para>
|
||||
|
||||
|
@ -1680,7 +1680,7 @@ $%&'()*+,-./01234567
|
|||
<command>lprps</command>) to convert it to PostScript. It then uses
|
||||
<command>lprps</command> to send the job to the printer.</para>
|
||||
|
||||
<para><command>lprps</command> is part of the FreeBSD ports collection
|
||||
<para><command>lprps</command> is part of the FreeBSD Ports Collection
|
||||
(see <link linkend="ports">The Ports Collection</link>). You can
|
||||
fetch, build and install it yourself, of course. After installing
|
||||
<command>lprps</command>, just specify the pathname to the
|
||||
|
@ -1726,8 +1726,8 @@ fi</programlisting>
|
|||
|
||||
<para>In the above script, <command>textps</command> is a program we
|
||||
installed separately to convert plain text to PostScript. You can
|
||||
use any text-to-PostScript program you wish. The FreeBSD ports
|
||||
collection (see <link linkend="ports">The Ports Collection</link>)
|
||||
use any text-to-PostScript program you wish. The FreeBSD Ports
|
||||
Collection (see <link linkend="ports">The Ports Collection</link>)
|
||||
includes a full featured text-to-PostScript program called
|
||||
<literal>a2ps</literal> that you might want to investigate.</para>
|
||||
</sect3>
|
||||
|
@ -1751,7 +1751,7 @@ fi</programlisting>
|
|||
special text filter for your printer, you can make your
|
||||
non-PostScript printer act like a real PostScript printer.</para>
|
||||
|
||||
<para>Ghostscript is in the FreeBSD ports collection, if you
|
||||
<para>Ghostscript is in the FreeBSD Ports Collection, if you
|
||||
would like to install it from there. You can fetch, build, and
|
||||
install it quite easily yourself, as well.</para>
|
||||
|
||||
|
@ -2116,8 +2116,8 @@ exit 2</programlisting>
|
|||
<programlisting>:df=/usr/local/libexec/hpdf:</programlisting>
|
||||
|
||||
<para>Now, for the hard part: making the filter. For that, we need
|
||||
a DVI-to-LaserJet/PCL conversion program. The FreeBSD ports
|
||||
collection (see <link linkend="ports">The Ports Collection</link>)
|
||||
a DVI-to-LaserJet/PCL conversion program. The FreeBSD Ports
|
||||
Collection (see <link linkend="ports">The Ports Collection</link>)
|
||||
has one: <command>dvi2xx</command> is the name of the package.
|
||||
Installing this package gives us the program we need,
|
||||
<command>dvilj2p</command>, which converts DVI into LaserJet IIp,
|
||||
|
@ -2242,7 +2242,7 @@ exit 0</programlisting>
|
|||
<secondary>filters</secondary>
|
||||
<tertiary>apsfilter</tertiary>
|
||||
</indexterm>
|
||||
<para>The FreeBSD ports collection has a text filter that performs
|
||||
<para>The FreeBSD Ports Collection has a text filter that performs
|
||||
automatic conversion called <command>apsfilter</command>. It can
|
||||
detect plain text, PostScript, and DVI files, run the proper
|
||||
conversions, and print.</para>
|
||||
|
|
Loading…
Reference in a new issue