PR: docs/149315
Fix a couple of typos/misspellings in: - doc/en_US.ISO8859-1/books/corp-net-guide/book.sgml - doc/en_US.ISO8859-1/books/dev-model/book.sgml - doc/en_US.ISO8859-1/books/developers-handbook/l10n/chapter.sgml - doc/en_US.ISO8859-1/books/fdp-primer/sgml-markup/chapter.sgml - doc/en_US.ISO8859-1/books/porters-handbook/book.sgml Contributed by: Jimmy Olgeni (olgeni@)
This commit is contained in:
Johann Kois
parent
62a39c73cd
commit
9024e5e4a5
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=36194
5 changed files with 15 additions and 15 deletions
en_US.ISO8859-1/books
corp-net-guide
dev-model
developers-handbook/l10n
fdp-primer/sgml-markup
porters-handbook
|
|
@ -1069,7 +1069,7 @@ Bind 3C5X9 #1 Ethernet_II LAN_NET</programlisting>
|
|||
systems will probably find it cheaper to simply upgrade to Windows
|
||||
NT Workstation or Win2K.</para>
|
||||
|
||||
<para>ACITS LPR and Win95 have a few printing idosyncracies. Most
|
||||
<para>ACITS LPR and Win95 have a few printing idiosyncrasies. Most
|
||||
Win95 programs, such as Microsoft Word, expect print output to be
|
||||
spooled on the local hard drive and then metered out to a printer
|
||||
that is plugged into the parallel port. Network printing, on the
|
||||
|
|
@ -1846,7 +1846,7 @@ NEC|NEC Silentwriter 95 PostScript printer:\
|
|||
<literal>nec</literal> in both the name of the printer and the name
|
||||
of the Spool directory. With the print spooler LPD, the Spool
|
||||
directories <emphasis>must</emphasis> be different from each other,
|
||||
or the spooler gets confused and doesen't print.</para>
|
||||
or the spooler gets confused and doesn't print.</para>
|
||||
|
||||
<para>After the <filename>/etc/printcap</filename> is modified, the
|
||||
root user must create the <filename>/var/spool/output/NEC</filename>
|
||||
|
|
|
|||
|
|
@ -2381,7 +2381,7 @@
|
|||
the FreeBSD web site</ulink>. It shows the number of ports
|
||||
available to FreeBSD in the period 1995 to 2005. It looks
|
||||
like the curve has first grown exponentionally, and then
|
||||
since the middle of 2001 grown linerly.
|
||||
since the middle of 2001 grown linearly.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
|
|
|
|||
|
|
@ -315,7 +315,7 @@ CFLAGS+= -DWITHOUT_NLS
|
|||
catalogs with the <makevar>NLSSRCDIR</makevar> &man.make.1;
|
||||
variable. The default name of the precompiled catalog files
|
||||
also follow the naming convention mentioned before. It can be
|
||||
overriden by setting the <makevar>NLSNAME</makevar> variable.
|
||||
overridden by setting the <makevar>NLSNAME</makevar> variable.
|
||||
There are other options to fine tune the processing of the catalog
|
||||
files but usually it is not needed, thus they are not described
|
||||
here. For further information on <filename>bsd.nls.mk</filename>,
|
||||
|
|
|
|||
|
|
@ -1708,7 +1708,7 @@ This is the file called 'foo2'</screen>
|
|||
<para>You will frequently want to refer to both applications and
|
||||
commands when writing documentation. The distinction between
|
||||
them is simple: an application is the name for a suite (or possibly
|
||||
just 1) of programs that fulfil a particular task. A command is the
|
||||
just 1) of programs that fulfill a particular task. A command is the
|
||||
name of a program that the user can run.</para>
|
||||
|
||||
<para>In addition, you will occasionally need to list one or more of
|
||||
|
|
|
|||
|
|
@ -962,7 +962,7 @@ DOS2UNIX_REGEX= .*\.(c|cpp|h)</programlisting>
|
|||
|
||||
<para>It is expected that <makevar>PORTEPOCH</makevar> will
|
||||
not be used for the majority of ports, and that sensible
|
||||
use of <makevar>PORTVERSION</makevar> can often pre-empt
|
||||
use of <makevar>PORTVERSION</makevar> can often preempt
|
||||
it becoming necessary if a future release of the software
|
||||
should change the version structure. However, care is
|
||||
needed by FreeBSD porters when a vendor release is made
|
||||
|
|
@ -1162,7 +1162,7 @@ PORTEPOCH= 1</programlisting>
|
|||
part of the directory name in a family of ports), the
|
||||
<replaceable>-compiled.specifics</replaceable> part should state
|
||||
the compiled-in defaults (the hyphen is optional). Examples are
|
||||
papersize and font units.</para>
|
||||
paper size and font units.</para>
|
||||
|
||||
<para>The <replaceable>-compiled.specifics</replaceable> part
|
||||
should be set in the <makevar>PKGNAMESUFFIX</makevar>
|
||||
|
|
@ -1315,7 +1315,7 @@ PORTEPOCH= 1</programlisting>
|
|||
<entry>psutils</entry>
|
||||
<entry>-letter</entry>
|
||||
<entry>1.13</entry>
|
||||
<entry>Papersize hardcoded at package build time</entry>
|
||||
<entry>Paper size hardcoded at package build time</entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
|
|
@ -3108,7 +3108,7 @@ ALWAYS_KEEP_DISTFILES= yes
|
|||
make sure you also add them to <filename>distinfo</filename>.
|
||||
Also, the additional files will normally be extracted into
|
||||
<makevar>WRKDIR</makevar> as well, which for some ports may
|
||||
lead to undesirable sideeffects and require special handling.</para>
|
||||
lead to undesirable side effects and require special handling.</para>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
|
|
@ -3885,7 +3885,7 @@ ${MANPREFIX}/man/de/man3/baz.3.gz</programlisting>
|
|||
check for
|
||||
<filename>/var/db/ports/<replaceable>portname</replaceable>/options</filename>.
|
||||
If that file does not exist, it will use the values of
|
||||
<makevar>OPTIONS</makevar> to create a dialogbox where the options
|
||||
<makevar>OPTIONS</makevar> to create a dialog box where the options
|
||||
can be enabled or disabled. Then the
|
||||
<filename>options</filename> file is saved and the selected
|
||||
variables will be used when building the port.</para>
|
||||
|
|
@ -5795,7 +5795,7 @@ do-configure:
|
|||
neglect to look for includes and/or libraries in the X11
|
||||
directories. You can tell <command>qmake</command> to
|
||||
add directories to the include and library searchpaths
|
||||
via the commandline, for example:</para>
|
||||
via the command line, for example:</para>
|
||||
|
||||
<programlisting>${QMAKE} -unix PREFIX=${PREFIX} INCLUDEPATH+=${LOCALBASE}/include \
|
||||
LIBS+=-L${LOCALBASE}/lib sillyapp.pro</programlisting>
|
||||
|
|
@ -7978,7 +7978,7 @@ WANT_LUA_VER= 5.0</programlisting>
|
|||
<row>
|
||||
<entry><literal>tolua</literal></entry>
|
||||
|
||||
<entry>Library for accesing C/C++ code</entry>
|
||||
<entry>Library for accessing C/C++ code</entry>
|
||||
|
||||
<entry><literal>4.0-5.0</literal></entry>
|
||||
</row>
|
||||
|
|
@ -12462,7 +12462,7 @@ Reference: <http://www.freebsd.org/ports/portaudit/74a9541d-5d6c-11d8-80e3-00
|
|||
<entry>700044</entry>
|
||||
<entry>June 7, 2007</entry>
|
||||
<entry>7.0-CURRENT after changing the argument for
|
||||
vn_open()/VOP_OPEN() from filedescriptor index to the
|
||||
vn_open()/VOP_OPEN() from file descriptor index to the
|
||||
struct file *.</entry>
|
||||
</row>
|
||||
|
||||
|
|
@ -14075,7 +14075,7 @@ exec %%LOCALBASE%%/bin/java -jar %%DATADIR%%/foo.jar "$@"</programlisting>
|
|||
<note>
|
||||
<para>If a port would conflict with a currently installed
|
||||
port (for example, if they install a file in the same
|
||||
place that perfoms a different function),
|
||||
place that performs a different function),
|
||||
<link linkend="conflicts">use
|
||||
<makevar>CONFLICTS</makevar> instead</link>.
|
||||
<makevar>CONFLICTS</makevar> will set
|
||||
|
|
@ -14173,7 +14173,7 @@ exec %%LOCALBASE%%/bin/java -jar %%DATADIR%%/foo.jar "$@"</programlisting>
|
|||
<para>The correct way for a <filename>Makefile</filename> to
|
||||
signal that the port can not be installed due to some external
|
||||
factor (for instance, the user has specified an illegal
|
||||
combination of build options) is to set a nonblank value to
|
||||
combination of build options) is to set a non-blank value to
|
||||
<makevar>IGNORE</makevar>. This value will be formatted and
|
||||
shown to the user by <command>make install</command>.</para>
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue