remote TABs in doc/ and test/

[cc65] / doc / apple2.sgml

diff --git a/doc/apple2.sgml b/doc/apple2.sgml
index ac5059902f7d5de8860d946656fdbb8fd0151e44..648ee56db7bb83bf85c91670103098e09d396757 100644 (file)
--- a/doc/apple2.sgml
+++ b/doc/apple2.sgml
@@ -32,7 +32,7 @@ more information.
 <sect>Binary format<p>
 
 The standard binary file format generated by the linker for the
-Apple&nbsp;&rsqb;&lsqb; target is an <url name="AppleSingle" 
+Apple&nbsp;&rsqb;&lsqb; target is an <url name="AppleSingle"
 url="http://kaiser-edv.de/documents/AppleSingle_AppleDouble.pdf"> file.
 The default load address is &dollar;803.
 
@@ -580,18 +580,18 @@ url="ca65.html" name="assembler manual">.
   ProDOS associates a file type and an auxiliary type with each file.
   These type specifications are separate from the file's name, unlike
   Windows which uses the file name's suffix (a.k.a.
-  extension) to specify the file type. For example, <tt/.exe/, 
+  extension) to specify the file type. For example, <tt/.exe/,
   <tt/.doc/, or <tt/.bat/.
-  The ProDOS low-level 
-  Machine-Language Interface (MLI) functions for creating and opening 
+  The ProDOS low-level
+  Machine-Language Interface (MLI) functions for creating and opening
   files require these types to be specified. And if they don't match
   with the file being opened, the operation may fail.
 
   In contrast, the ISO C function <tt/fopen()/ and the POSIX function
   <tt/open()/ have no parameter to specify either a file type or an
   auxiliary type. Therefore, some additional mechanism for specifying
-  the file types is needed. 
-  
+  the file types is needed.
+
   <tag>Specifying the File Type and Auxiliary Type</tag>
 
   There are two global variables provided that allow the file type
@@ -603,7 +603,7 @@ url="ca65.html" name="assembler manual">.
   extern unsigned char _filetype;  /* Default: PRODOS_T_BIN */
   extern unsigned int _auxtype;    /* Default: 0            */
   </verb>
-  </tscreen>  
+  </tscreen>
 
   The header file <tt/apple2_filetype.h/ also defines many values
   that can be used to set these variables. It is included in
@@ -614,26 +614,26 @@ url="ca65.html" name="assembler manual">.
   <tag>Example</tag>
 
   A text file cannot be created with just the
-  standard C functions because they default to the binary type 
+  standard C functions because they default to the binary type
   <tt/PRODOS_T_BIN/. The <tt/_filetype/ variable must be set to
-  <tt/PRODOS_T_TXT/ to create a text file. 
-  
-  For a text file, 
+  <tt/PRODOS_T_TXT/ to create a text file.
+
+  For a text file,
   <tt/_auxtype/ specifies the record length. A zero record
   length text file is referred to as a sequential text file.
-  This is equivalent to text files on 
+  This is equivalent to text files on
   other operating systems, except that the line terminator is a
-  carriage return instead of a line-feed (Linux/BSD/MacOS) or 
+  carriage return instead of a line-feed (Linux/BSD/MacOS) or
   carriage return, line-feed pair (Windows).
-  
-  The "sequential" text file terminology is in contrast to a 
+
+  The "sequential" text file terminology is in contrast to a
   "random-access" text file which would
-  have a fixed-length, non-zero record length, so that the 
+  have a fixed-length, non-zero record length, so that the
   file position of any individual record can be calculated.
-  
+
   For this example, the
   <tt/_auxtype/ does not need to be set because it defaults to
-  the desired value, which is zero. To be more explicit, 
+  the desired value, which is zero. To be more explicit,
   <tt/_auxtype/ can also be set to <tt/PRODOS_AUX_T_TXT_SEQ/
   which is defined as zero.
 
@@ -670,7 +670,7 @@ url="ca65.html" name="assembler manual">.
         }
     }
   </verb>
-  </tscreen>  
+  </tscreen>
 
 </descrip><p>
 
@@ -686,14 +686,14 @@ including commercial applications, and to alter it and redistribute it
 freely, subject to the following restrictions:
 
 <enum>
-<item> The origin of this software must not be misrepresented; you must not
-       claim that you wrote the original software. If you use this software
-       in a product, an acknowledgment in the product documentation would be
-       appreciated but is not required.
-<item> Altered source versions must be plainly marked as such, and must not
-       be misrepresented as being the original software.
-<item> This notice may not be removed or altered from any source
-       distribution.
+<item>  The origin of this software must not be misrepresented; you must not
+        claim that you wrote the original software. If you use this software
+        in a product, an acknowledgment in the product documentation would be
+        appreciated but is not required.
+<item>  Altered source versions must be plainly marked as such, and must not
+        be misrepresented as being the original software.
+<item>  This notice may not be removed or altered from any source
+        distribution.
 </enum>
 
 </article>