*.sgml:

- Use trademark entities.
 - Add trademark attributions.
 - Don't join trademarks with other words, e.g. using hyphens.

trademark.ent:
 - Add trademark entity for Sun.

en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml

@@ -27,7 +27,7 @@
 
     <para>This chapter is an introduction to using some of the
       programming tools supplied with FreeBSD, although much of it
-      will be applicable to many other versions of Unix.  It does
+      will be applicable to many other versions of &unix;.  It does
       <emphasis>not</emphasis> attempt to describe coding in any
       detail.  Most of the chapter assumes little or no previous
       programming knowledge, although it is hoped that most
@@ -39,18 +39,18 @@
 
     <para>FreeBSD offers an excellent development environment.
       Compilers for C, C++, and Fortran and an assembler come with the
-      basic system, not to mention a Perl interpreter and classic Unix
+      basic system, not to mention a Perl interpreter and classic &unix;
       tools such as <command>sed</command> and <command>awk</command>.
       If that is not enough, there are many more compilers and
       interpreters in the Ports collection.  FreeBSD is very
-      compatible with standards such as <acronym>POSIX</acronym> and
+      compatible with standards such as <acronym>&posix;</acronym> and
       <acronym>ANSI</acronym> C, as well with its own BSD heritage, so
       it is possible to write applications that will compile and run
       with little or no modification on a wide range of
       platforms.</para>
 
     <para>However, all this power can be rather overwhelming at first
-      if you have never written programs on a Unix platform before.
+      if you have never written programs on a &unix; platform before.
       This document aims to help you get up and running, without
       getting too deeply into more advanced topics.  The intention is
       that this document should give you enough of the basics to be
@@ -58,7 +58,7 @@
 
     <para>Most of the document requires little or no knowledge of
       programming, although it does assume a basic competence with
-      using Unix and a willingness to learn!</para>
+      using &unix; and a willingness to learn!</para>
 
   </sect1>
 
@@ -103,11 +103,11 @@
 	start if you have not done any programming before.  This kind
 	of environment is typically found with languages like Lisp,
 	Smalltalk, Perl and Basic.  It could also be argued that the
-	Unix shell (<command>sh</command>, <command>csh</command>) is itself an
+	&unix; shell (<command>sh</command>, <command>csh</command>) is itself an
 	interpreter, and many people do in fact write shell
 	<quote>scripts</quote> to help with various
 	<quote>housekeeping</quote> tasks on their machine.  Indeed, part
-	of the original Unix philosophy was to provide lots of small
+	of the original &unix; philosophy was to provide lots of small
 	utility programs that could be linked together in shell
 	scripts to perform useful tasks.</para>
     </sect2>
@@ -170,7 +170,7 @@
 	    <para>Lisp is an extremely powerful and sophisticated
 	      language, but can be rather large and unwieldy.</para>
 
-	    <para>Various implementations of Lisp that can run on UNIX
+	    <para>Various implementations of Lisp that can run on &unix;
 	      systems are available as packages for FreeBSD.
 	      <ulink URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/Latest/gcl.tgz">GNU Common Lisp</ulink>,
 	      <ulink URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/Latest/clisp.tgz">CLISP</ulink>
@@ -665,11 +665,11 @@
 
 	  <para>Each of these will both produce an executable
 	    <filename>foobar</filename> from the C++ source file
-	    <filename>foobar.cc</filename>.  Note that, on Unix
+	    <filename>foobar.cc</filename>.  Note that, on &unix;
 	    systems, C++ source files traditionally end in
 	    <filename>.C</filename>, <filename>.cxx</filename> or
 	    <filename>.cc</filename>, rather than the
-	    MS-DOS style
+	    &ms-dos; style
 	    <filename>.cpp</filename> (which was already used for
 	    something else).  <command>gcc</command> used to rely on
 	    this to work out what kind of compiler to use on the
@@ -827,7 +827,7 @@ int main() {
 	  </question>
 
 	  <answer>
-	    <para>Unlike MS-DOS, Unix does not
+	    <para>Unlike &ms-dos;, &unix; does not
 	      look in the current directory when it is trying to find
 	      out which executable you want it to run, unless you tell
 	      it to.  Either type <command>./foobar</command>, which
@@ -856,7 +856,7 @@ int main() {
 	  </question>
 
 	  <answer>
-	    <para>Most Unix systems have a program called
+	    <para>Most &unix; systems have a program called
 	      <command>test</command> in <filename>/usr/bin</filename>
 	      and the shell is picking that one up before it gets to
 	      checking the current directory.  Either type:</para>
@@ -880,7 +880,7 @@ int main() {
 
 	  <answer>
 	    <para>The name <firstterm>core dump</firstterm> dates back
-	      to the very early days of Unix, when the machines used
+	      to the very early days of &unix;, when the machines used
 	      core memory for storing data.  Basically, if the program
 	      failed under certain conditions, the system would write
 	      the contents of core memory to disk in a file called
@@ -910,7 +910,7 @@ int main() {
 
 	  <answer>
 	    <para>This basically means that your program tried to
-	      perform some sort of illegal operation on memory; Unix
+	      perform some sort of illegal operation on memory; &unix;
 	      is designed to protect the operating system and other
 	      programs from rogue programs.</para>
 
@@ -960,7 +960,7 @@ bar[27] = 6;
 strcpy(foo, "bang!");
 		</programlisting>
 
-		<para>Unix compilers often put string literals like
+		<para>&unix; compilers often put string literals like
 		  <literal>"My string"</literal> into read-only areas
 		  of memory.</para>
 	      </listitem>
@@ -994,7 +994,7 @@ free(foo);
 	<qandaentry>
 	  <question>
 	    <para>Sometimes when I get a core dump it says
-	      <errorname>bus error</errorname>.  It says in my Unix
+	      <errorname>bus error</errorname>.  It says in my &unix;
 	      book that this means a hardware problem, but the
 	      computer still seems to be working.  Is this
 	      true?</para>
@@ -1304,9 +1304,9 @@ DISTFILES=      scheme-microcode+dist-7.3-freebsd.tgz
 
 	<step>
 	  <para>Any special configuration needed for the source is
-	    done.  (Many Unix program distributions try to work out
-	    which version of Unix they are being compiled on and which
-	    optional Unix features are present&mdash;this is where
+	    done.  (Many &unix; program distributions try to work out
+	    which version of &unix; they are being compiled on and which
+	    optional &unix; features are present&mdash;this is where
 	    they are given the information in the FreeBSD ports
 	    scenario).</para>
 	</step>
@@ -1671,7 +1671,7 @@ else if (pid == 0) {		/* child */
     <sect2>
       <title>Emacs</title>
 
-      <para>Unfortunately, Unix systems do not come with the kind of
+      <para>Unfortunately, &unix; systems do not come with the kind of
 	everything-you-ever-wanted-and-lots-more-you-did-not-in-one-gigantic-package
 	integrated development environments that other systems
 	have.
@@ -1808,7 +1808,7 @@ else if (pid == 0) {		/* child */
 
       <para>If you are wondering what on earth the
 	<keysym>Meta</keysym> key is, it is a special key that many
-	Unix workstations have.  Unfortunately, PC's do not have one,
+	&unix; workstations have.  Unfortunately, PC's do not have one,
 	so it is usually the <keycap>alt</keycap> key (or if you are
 	unlucky, the <keysym>escape</keysym> key).</para>