Fix some typos

Most of them were found by codespell.

Signed-off-by: Stefan Weil <[email protected]>

ChangeLog

@@ -235,7 +235,7 @@
 	* zzip/file.c: errornous usage of currentfp before setting it to
 	   the new fp value in zzip_seek(). In the good case it would seek
 	   on the wrong file and in the bad case it goes off on sigbus/NPE.
-	   The problem occurs only if two+ zips are accessed simultanously.
+	   The problem occurs only if two+ zips are accessed simultaneously.
 	   (problem reported and patch kindly provided by Evgeniy Muhin)
 	* docs/Makefile.am: fixup for newer xmlto may be to generate
 	   a subdirectory "man3" inside of our output directory "man3"
@@ -442,7 +442,7 @@
  * fixing some compilation problems related to zip64 support in win32
 
 2005-12-08
- * cut acinclude.m4 into seperated aclocal macros in m4/ subdirectory
+ * cut acinclude.m4 into separated aclocal macros in m4/ subdirectory
 
 2005-10-14
  * testing on sourceforge compilefarm, cleaning away any compiler warnings
@@ -790,7 +790,7 @@
 	within plugin.h for io->read() calls. That makes for a little
 	bit of portability - it seems some platforms (dot-net f.e.)
 	do not `typedef unsigned int size_t;`, perhaps because int is 16bit
-	and a 32bit or even 64bit entitity is needed.
+	and a 32bit or even 64bit entity is needed.
  * now we do not need to AC_COMPILE_CHECK_SIZEOF(size_t) anymore, perhaps
 	even stand io-wrap is not needed anymore. Let's see.
  * both changes need update of zzip/conf.h for _zzip_size_t plus
@@ -861,7 +861,7 @@
 	a backslash as well. That should be handled better, we add some
 	alternative implementations for dirsep_strrchr and dirsep_casecmp
 	but the default is OFF!! even on WINDOWS !!
- * thereby seen another problem: we did deliberatly use strcasecmp but
+ * thereby seen another problem: we did deliberately use strcasecmp but
 	this symbol is not available on all unix systems - the manual
 	says its a BSD4.3 addition. Some other systems call it strcmpi
 	or stricmp instead, or they do not have it at all. Here we add
@@ -949,7 +949,7 @@
  * fix some problems of make-doc.pl with the current project
  * make a standard inlude info referring to zziplib.h as well
  * unpack htmpages.ar on SFNET and register it on the frontpage
- * dont forget to modify includes of internal headers
+ * don't forget to modify includes of internal headers
  * ...
  * fixed an annoying bug in make-doc.pl
  * include htmpages.ar into the tarball
@@ -958,7 +958,7 @@
  * completed new directory structure - the library is called 0.12.22 as
 	to match 0.10.72, it's the same C source in its content
  * install-headers modified - the new structure is now compatible both
-	as a shared libary (binary compatible) and for the include headers
+	as a shared library (binary compatible) and for the include headers
 	too - source compatible not only for function names but also for
 	the #include lines
  * 0.12.23 fixes a bug in make doc: the xmlto html was never done.
@@ -1103,7 +1103,7 @@
  * Michael-dot-Fink-at-asamnet-dot-de did some code review while
 	going after a specialty he wanted to do with the libs, and therefore..
  * PREFERZIP did never test real file - stupid bug, inverted logic....
- * add ZIPONLY zzipmode - we have plenty of options availabe... on 32bit
+ * add ZIPONLY zzipmode - we have plenty of options available... on 32bit
 	platforms however, since I want to keep with the access-bits in
 	the lower parts.
 
@@ -1162,7 +1162,7 @@
 	and two fixes
  * put the updated MSVC6 files into the project, again Mike Nordell
  * me, add new zzwrap.dsp to DIST in Makefile.am, following Mike's addition
- * me, modify some typecasts to use off_t/size_t where apropriate
+ * me, modify some typecasts to use off_t/size_t where appropriate
  * modified COPYING.ZZIP to be a bit more general than just for ZZIPLIB
 	as noted by Tomi Olilla
  * zzipwrap demo_callback, how can we do void* and char* at the same time...
@@ -1180,7 +1180,7 @@
  * add a new file COPYING for new less-strictly license
 	after Tomi Ollila has transferred full copyright to me
  * remove Tomi Ollila from all copyright entries in the sources
-	but honour his name where apropriate
+	but honour his name where appropriate
  * modify LGPL hints in sources and point to COPYING.ZZIP as well
         and change copyright year info
  * create COPYING.ZZIP with some general LGPL exceptions.
@@ -1402,7 +1402,7 @@
  * two new functions, zzip_dir_real and zzip_file_real
    to check if the ZZIP_XX structures are wrapping a
    real file or directory. Otherwise it is a zip-archive
-   or a zip-contained file respectivly.
+   or a zip-contained file respectively.
  * zzip_compr_str does now know about stat-types and
    will return names for S_ISTYPE bits.
  * remove zzip_fd. It was identical to zzip_dirfd
@@ -1510,7 +1510,7 @@
    Tomi did.
  * bugfixes for zzip_open, it did not always
    set errno(2) to the value of zzip_errno.
- * The zzip_read is now seperate from
+ * The zzip_read is now separate from
    zzip_fp_read, so that setting errno(2) is
    only done in zzip_read, not in the zzip-touching
    function.

README

@@ -39,7 +39,7 @@ INSTALLATION
   VisualC series of compilers. There should be no problem either
   when crosscompiling the zziplib for a third host platform.
 
-MAINTAINANCE
+MAINTENANCE
   The zziplib library is intentionally a lightweight interface to
   zip files. The author take patches but please consider to put 
   complex extensions into separate modules rather than implanting them

TODO

@@ -45,7 +45,7 @@ libtool package, the libtool 1.4 is dated 2001/04/24
 
 There are reports of misaligned access to some zip fields that
 I would guess to be on little-endian non-x86 platforms. The current
-bytewise access of multibyte fields is targetted towards the
+bytewise access of multibyte fields is targeted towards the
 bigendian unix machines. The fix would need to go to fetch.h but
 so far no response came about as that one could test a solution.
 

bins/zziplib.m4

@@ -7,7 +7,7 @@ dnl projects. In general, you can include in your configure.ac
 dnl some line like
 dnl PKG_CHECK_ZZIPLIB([ZZIP],[0.10.75])
 dnl in order to get the two autoconf/automake subst variables
-dnl named ZZIP_CFLAGS and ZZIP_LIBS respectivly.
+dnl named ZZIP_CFLAGS and ZZIP_LIBS respectively.
 
 dnl PKG_CHECK_ZZIPLIB(ZZIP, minversion, action-if, action-not)
 dnl defines ZZIP_LIBS, ZZIP_CFLAGS, see pkg-config man page

docs/Makefile.am

@@ -50,7 +50,7 @@ install-data-local : @MAINTAINER_MODE_FALSE@ install-mans
 
 # -------------------------------------------------------------------
 zziplib.spec : @top_srcdir@/$(PACKAGE).spec
-	@ cp $? $@ # the two zzip-doc.* will grep thru zziplib.spec
+	@ cp $? $@ # the two zzip-doc.* will grep through zziplib.spec
 doc  : $(doc_FILES) site.html
 docs : doc manpages.tar htmpages.tar
 # docu : docs

docs/Makefile.in

@@ -552,7 +552,7 @@ install-data-local : @MAINTAINER_MODE_FALSE@ install-mans
 
 # -------------------------------------------------------------------
 zziplib.spec : @top_srcdir@/$(PACKAGE).spec
-	@ cp $? $@ # the two zzip-doc.* will grep thru zziplib.spec
+	@ cp $? $@ # the two zzip-doc.* will grep through zziplib.spec
 doc  : $(doc_FILES) site.html
 docs : doc manpages.tar htmpages.tar
 # docu : docs

docs/README.MSVC6

@@ -85,7 +85,7 @@ Step 4: Customization
      or just ignore the value when no messages are there
   -> Project -> Settings -> Tab: Link
              -> Category: General -> "Output Filename"
-     e.g. "zzip-1.dll" intead of "zzip.dll" for this first generation
+     e.g. "zzip-1.dll" instead of "zzip.dll" for this first generation
      (needs also to rename dll dependencies from "zzip.lib" to "zzip-1.lib")
 - there are a few defines that trigger extra code in zziplib, e.g.
    ZZIP_HARDEN - extra sanity check for obfuscated zip files

docs/README.SDL

@@ -84,8 +84,8 @@ NOTE
   and zziplib will take one of them (depending on the modes when calling 
   zziplib).
 
-  But this didnt work for all of my original files, so I suggest using zipped
-  files only (and remove the original unzipped files, so zziplib doesnt try to
+  But this didn't work for all of my original files, so I suggest using zipped
+  files only (and remove the original unzipped files, so zziplib doesn't try to
   open the original version).
 
 

docs/configs.htm

@@ -83,7 +83,7 @@ <h3> pkg-config --libs </h3>
 </section><section>
 <h3> zzip-config </h3>
 <P>
-   The pkg-config ".pc" files are relativly young in the history of
+   The pkg-config ".pc" files are relatively young in the history of
    zziplib. A long time before that there was the `zzip-config`
    script installed in the system. These `*-config` were common
    before the pkg-config came about, and in fact the pkg-config
@@ -147,7 +147,7 @@ <h3> autoconf macro </h3>
 </P><P>
   which will provide you with two autoconf/automake variables
   named <b><code>ZZIP_CFLAGS</code></b> and <b><code>ZZIP_LIBS</code></b> 
-  respectivly.
+  respectively.
 </P>
 <P>
   Up to 2004, the macro in zziplib.m4 will be however carry

docs/developer.htm

@@ -20,7 +20,7 @@ <H2> Developer </H2> sourceforge SVN area
 </P>
 <P>
   I was using the sourceforge compilefarm to do remote testing of
-  releses for crossplatform compatibility. This included usually
+  releases for crossplatform compatibility. This included usually
   some unix compatible platforms such as Linux, Solaris,
   FreeBSD, Darwin/MacOSX including i386, amd64, sparc, sparc64,
   powerpc when available. Even the latest daytoday cvs snapshots

docs/download.htm

@@ -13,7 +13,7 @@ <H4>Sourceforge File Area</H4>
   All source releases and some binary releases are listed at the
   sourceforge download area under the link show above. The sourceforge
   file area is replicated all over the world and should be accessible
-  with highest bandwith in all corners of the world.
+  with highest bandwidth in all corners of the world.
 </P>
 
 </section><section>

docs/faq.htm

@@ -30,7 +30,7 @@ <H2> FAQ </H2> (non)frequently asked questions
   decades including the age when the ZIP file format was invented. The
   first instances of pkware's zip compressor were used on DOS with a 
   codepage 437 which has a way different encoding for the upper plane
-  than todays latin-1 encoding which in fact used in <em>all</em> 
+  than today's latin-1 encoding which in fact used in <em>all</em>
   modern operating systems. So what really see is a mismatch of 
   character encodings that you are used to.
 </P><P>

docs/functions.htm

@@ -15,7 +15,7 @@ <H2> Exported Functions </H2>
 </ul>
 
 <P>
-  Additonally, there is a complete set of unpacked documentation - the
+  Additionally, there is a complete set of unpacked documentation - the
   unix manual pages are translated to html manual pages.
 </P>
 

docs/make-doc.py

@@ -692,7 +692,7 @@ def copyright_text(page):
                 return copyright # !!!
         return ""
     def seealso_text(page):
-        """ the last section on a manpage is called 'SEE ALSO' usally and
+        """ the last section on a manpage is called 'SEE ALSO' usually and
             contains a comma-separated list of references. Some manpage
             viewers can parse these and convert them into hyperlinks """
         if page.seealso:

docs/zzip-api.htm

@@ -4,7 +4,7 @@ <h2> ZZIP Programmers Interface </h2>   The complete API description.
 <!--border-->
 
 <P>
-  The zzip library was orginally developped by Tomi Ollila as a
+  The zzip library was originally developed by Tomi Ollila as a
   set of zip decoder routines. Guido Draheim did pick it up and
   wrapped them under a call synopsis matching their posix
   api calls. Therefore <code>zzip_open()</code> has the same 

docs/zzip-basics.htm

@@ -58,7 +58,7 @@ <h3> Basics </h3>
   <tr><td width=50%> zzip_dir_close  </td>
       <td width=50%> close a zip-file and free the memory shadow</td></tr>
   <tr><td width=50%> zzip_dir_fdopen  </td>
-      <td width=50%> aquire the given posix-file and try to parse it 
+      <td width=50%> acquire the given posix-file and try to parse it
                                                   as a zip-file.</td></tr>
   <tr><td width=50%> zzip_dir_read  </td>
       <td width=50%> return the next info entry of a zip-file's central
@@ -119,7 +119,7 @@ <h3> Basics </h3>
 <table cellpadding=10 width=100%><tr><td><table border=1 width=100%>
   <tr><td width=50%> zzip_open  </td>
       <td width=50%> try the file-path as a real-file, and if not
-                     there, look for the existance of ZZIP_DIR by
+                     there, look for the existence of ZZIP_DIR by
                      applying extensions, and open the file 
                      contained within that one.</td></tr>
   <tr><td width=50%> zzip_close  </td>

docs/zzip-extio.htm

@@ -40,7 +40,7 @@ <h3> The EXT/IO calls </h3>
   Other wishes on <a href="zziplib.html">zziplib</a> circulated around
   <a href="zzip-xor.html">obfuscation</a> or access to zip-files wrapped 
   in other data areas including encrpyted resources from other applications. 
-  This has been adressed with the IO-handlers that you can explicitly 
+  This has been addressed with the IO-handlers that you can explicitly
   submit to the *_ext_io functions - the default will be posix-IO 
   open/read/write and seek/tell. An application using 
   <a href="zziplib.html">zziplib</a> can divert these to its own set of
@@ -81,7 +81,7 @@ <h3> The EXT stringlist </h3>
      static zzip_strings_t my_ext[] = { ".zip", ".ZIP", "", 0 };
   </pre>
 </P><P>
-  And last not least, people want to tell the libary to not try to
+  And last not least, people want to tell the library to not try to
   open a real file that lives side by side with the same path as the
   file path that can be matched by the zziplib. Actually, the magic
   wrappers were never meant to be used like - the developer should
@@ -90,7 +90,7 @@ <h3> The EXT stringlist </h3>
   the magic-wrappers look rather more familiar, and so you will find
   now a bit-option ZZIP_ONLYZIP that can be passed down to the _ext_io
   variants of the magic-wrapper calls, and a real-file will never get
-  tested for existance. Actually, I would rather recommend that for
+  tested for existence. Actually, I would rather recommend that for
   application data the option ZZIP_PREFERZIP, so that one can enter
   debugging mode by unpacking the zip-file as a real directory tree
   in the place of the original zip.
@@ -176,8 +176,8 @@ <h3> Finally </h3>
    structure for usage within the <code>zzip_read</code> calls.
 </P><P>
    This adds just a few bytes to the libs and just consumes additional 
-   cpu cycles that can be rightfully called to be negligable (unlike
-   most commerical vendors will tell you when they indeed want to
+   cpu cycles that can be rightfully called to be negligible (unlike
+   most commercial vendors will tell you when they indeed want to
    tell you that for soooo many new features you have to pay a price).
    It makes for greater variability without adding fatness to the
    core in the default case, this is truly efficient I'd say. Well,

docs/zzip-file.htm

@@ -113,7 +113,7 @@ <h3>Differences</h3>
 <P>
  What the current of version of the 
  <a href="zziplib.html">zziplib library</a>
- can definitly not do: calling zzip_opendir on a directory zippend
+ can definitely not do: calling zzip_opendir on a directory zippend
  <em>inside</em> a zip-file.
 </P>
 <P>

docs/zzip-index.htm

@@ -26,7 +26,7 @@ <h2> The Library </h2> Overview
 </dd>
 <dt>replacement mode:</dt>
 <dd>  Use ZZIP_FILE / ZZIP_DIR pointers provided by zziplib and
-      put them to work with routines originally developped to
+      put them to work with routines originally developed to
       work with real directories and file handles. The API calls
       do follow traditional synopsis from posix/stdio.
 </dd>

docs/zzip-sdl-rwops.htm

@@ -23,7 +23,7 @@ <h3> Source </h3>
  <a href="SDL_rwops_zzip.c">SDL_rwops_zzip.c</a>
  to the directory with your other project sources, and make sure
  to link it somehow to your programs. I did not make the effort to
- create a seperate library out of it - it would just export one
+ create a separate library out of it - it would just export one
  single function <tt>SDL_RWFromZZIP</tt> that has the same call-synopsis
  like <tt>SDL_RWFromFile</tt> (but it can not (yet) write a zip-file).
 </P>

docs/zzip-zip.htm

@@ -28,7 +28,7 @@ <h3> Using A Zip-File </h3>
 <P>
  Before a file in the zip-archive is accessed, the application
  must first get a handle to the central directory contained in the
- zip-file. This is achived by calling 
+ zip-file. This is achieved by calling
  <a href="zziplib.html#zzip_dir_open"> zzip_dir_open </a>
  or 
  <a href="zziplib.html#zzip_dir_fdopen"> zzip_dir_fdopen </a>.
@@ -84,7 +84,7 @@ <h3> Magic Zipped Files </h3>
  <a href="zziplib.html">zziplib library</a>.
 </P>
 <P>
- The magic functions are described in a seperated document on
+ The magic functions are described in a separated document on
  <a href="zzip-file.html"> Using Zipped Files </a>. In general,
  the functions have a prefix <tt>zzip_</tt> and their argument
  types have a prefix <tt>ZZIP_</tt> where appropriate. Calls
@@ -99,10 +99,10 @@ <h3> Magic Zipped Files </h3>
  <a href="zziplib.html#zzip_dir_real"> zzip_dir_real </a>
  can be used.
  If these return a true value, the standard posix functions
- are more apropriate. The posix handles can be obtained with
+ are more appropriate. The posix handles can be obtained with
  a call to
  <a href="zziplib.html#zzip_realdir"> zzip_realdir </a> and
- <a href="zziplib.html#zzip_realfd"> zzip_realfd </a> respectivly.
+ <a href="zziplib.html#zzip_realfd"> zzip_realfd </a> respectively.
 </P>
 
 </section><section>

docs/zzipdoc/functionlistreference.py

@@ -217,7 +217,7 @@ def copyright_text(self):
                 return copyright # !!!
         return ""
     def seealso_text(self):
-        """ the last section on a manpage is called 'SEE ALSO' usally and
+        """ the last section on a manpage is called 'SEE ALSO' usually and
             contains a comma-separated list of references. Some manpage
             viewers can parse these and convert them into hyperlinks """
         if self.seealso:

docs/zzipdoc/textfileheader.py

@@ -17,7 +17,7 @@ def parse(self, textfile = None):
         x = Match()
         text = self.textfile.get_src_text()
         if not text:
-            print "nonexistant file:", self.textfile.get_filename()
+            print "nonexistent file:", self.textfile.get_filename()
             return False
         if text & x(r"(?s)[/][*]+(\s(?:.(?!\*\/))*.)\*\/"
                     r"(?:\s*\#(?:define|ifdef|endif)[ ]*\S*[ ]*\S*)*"

docs/zziplib.html

@@ -21,7 +21,7 @@
        href="zzip-zip.html">ZIP Access</a>
 <br>-<a alt="zzip-file - Using Zipped Files Transparently"
        href="zzip-file.html">Transparently</a>
-<br>-<a alt="zzip-sdl-rwops - Example to make an SDL_rwops Inteface" 
+<br>-<a alt="zzip-sdl-rwops - Example to make an SDL_rwops Interface"
        href="zzip-sdl-rwops.html">SDLrwops Example</a>
 <br>-<a alt="zzip-extio - Customizing the file access" 
        href="zzip-extio.html">ext/io Customization</a>
@@ -1139,7 +1139,7 @@ <h3>Documentation</h3>
  <br />  are helper functions used implicitly in other zzipcalls 
  <br />  e.g. <a href="#zzip_dir_close"><code>zzip_dir_close</code></a> = zzip_close  
  <p> 
-   returns zero on sucess 
+   returns zero on success
  <br />  returns the refcount when files are attached. 
 
 <p align="right"><small>(../zzip/zip.c)</small></p></dd>

m4/ac_sys_largefile_sensitive.m4

@@ -8,7 +8,7 @@ dnl
 dnl This macro builds on top of AC_SYS_LARGEFILE to detect whether
 dnl special options are neede to make the code use 64bit off_t - in
 dnl many setups this will also make the code use 64bit off_t
-dnl immediatly.
+dnl immediately.
 dnl
 dnl The common use of a LARGEFILE_SENSITIVE config.h-define is to
 dnl rename exported functions, usually adding a 64 to the original