Fix various typos in the codebase (#923)

* Fix various typos Found via `codespell -q 3 -S "*.po" -L clen,donn,informations,udo` * Fix typos in camlibs/ * Fix typos in ChangeLog
gphoto · Sep 3, 2023 · dfde313 · dfde313
1 parent 0b93f2d
commit dfde313
Show file tree

Hide file tree

Showing 80 changed files with 174 additions and 174 deletions.
diff --git a/ChangeLog b/ChangeLog
@@ -7,7 +7,7 @@
 2010-03-12  Hans de Goede <[email protected]>
 
 	* camlibs/st2205: New camera driver for ST2205 based picture frames.
-	* libgphoto2_port/usbdiskdirect: USB Disk direct acccess driver
+	* libgphoto2_port/usbdiskdirect: USB Disk direct access driver
 	  (for ST2205 based picture frames.)
 	* New dependency for "libgd" for image conversion for above driver.
 	* configure.ac, camlibs/Makefile.am: hooked up new camlib, new gd check.
@@ -71,7 +71,7 @@
 	* Adjusted to new GPPortInfo handling.
 
 	* Rewrote gphoto2-filesys.c to be directory based (in a tree
-	  structure). Change should not be visibile outside of gphoto2-filesys.c.
+	  structure). Change should not be visible outside of gphoto2-filesys.c.
 
 2008-05-18  Marcus Meissner   <[email protected]>
 
@@ -284,7 +284,7 @@
 	  Got rid of most LRU heuristics, simplified to just store
 	  the last <n> full datastreams.
 	  This should be fully sufficient for 99.9% of all usecases
-	  (download images lineary).
+	  (download images linearly).
 
 	  You can control this by the setting "libgphoto2" , "cached-images".
 
@@ -1028,7 +1028,7 @@
 
 2002-05-19  Christophe Barbe <[email protected]>
 
-	* frontends/command-line/main.c: replaced a missused #if with a #ifdef
+	* frontends/command-line/main.c: replaced a misused #if with a #ifdef
 	* frontends/command-line/gphoto2-cmd-capture.c: same 2 times.
 	   reported by Luciano Campal Vazquez <[email protected]>
 
@@ -2140,7 +2140,7 @@
 	that broke (at least) two of the supported 'libgphoto2' camera
 	libraries!!!" *sigh*. 
 
-	* conigure.in: Add a --with-multi option and a warning that people
+	* configure.in: Add a --with-multi option and a warning that people
 	  who use it will run into troubles with digita and dc240 and that
 	  people who don't use it will run into troubles when using Nautilus
 	  or Konqueror for browsing their camera.
@@ -2776,7 +2776,7 @@
 
 2001-10-26 Lutz Müller <[email protected]>
 
-	* frontends/command-line/gphoto2-cmd-capture.c: Adjust brighness
+	* frontends/command-line/gphoto2-cmd-capture.c: Adjust brightness
 	  and contrast with arrow keys
 
 2001-10-26 Dan Fandrich <[email protected]>
@@ -3192,7 +3192,7 @@
 
 2001-10-17  Lutz Müller <[email protected]>
 
-	* libgphoto2/gphoto2-debug.c: Make tranition to gp_log_*
+	* libgphoto2/gphoto2-debug.c: Make transition to gp_log_*
 	* camlibs/sierra: Adjust parameters of camera_capture
 
 2001-10-17  Lutz Müller <[email protected]>
@@ -3665,7 +3665,7 @@
 2001-10-04  Lutz Müller <[email protected]>
 
 	* camlibs/konica/library.c: const
-	* frontents/command-line/main.c: Print out last debugging messages
+	* frontends/command-line/main.c: Print out last debugging messages
 	on error
 	* include/gphoto2-debug.h:
 	* libgphoto2/debug.c: Remember history
@@ -4606,18 +4606,18 @@
 	* tests/*: New
 	* configure.in:
 	* Makefile.am: Add tests to SUBDIRS and generate the Makefile
-	* frontents/command-line/test.[c,h]: Removed
+	* frontends/command-line/test.[c,h]: Removed
 	* frontends/command-line/main.c:
-	* frontents/command-line/Makefile.am: Reflect changes
+	* frontends/command-line/Makefile.am: Reflect changes
 
 2001-08-17  Lutz Müller  <[email protected]>
 
-	* frontents/gtk/macros/*: Removed.
+	* frontends/gtk/macros/*: Removed.
 
 2001-08-17  Lutz Müller  <[email protected]>
 
-	* frontents/Makefile.am: Remove libpghoto2_frontend from SUBDIRS.
-	* frontents/gtk/*: Removed those ancient files. For GUI frontends, 
+	* frontends/Makefile.am: Remove libpghoto2_frontend from SUBDIRS.
+	* frontends/gtk/*: Removed those ancient files. For GUI frontends, 
 	refer to gtkam or GnoCam. They are distributed separately.
 
 2001-08-17  Lutz Müller  <[email protected]>
@@ -4627,7 +4627,7 @@
 
 2001-08-17  Lutz Müller  <[email protected]>
 
-	* frontents/libgphoto2_frontend/*: Removed. Those files were mainly
+	* frontends/libgphoto2_frontend/*: Removed. Those files were mainly
 	empty functions and nowhere needed.
 
 2001-08-17  Hubert Figuiere  <[email protected]>
@@ -5396,7 +5396,7 @@
 
 2000-07-29 04:14  simpson2
 
-	* camlibs/digita/digita.df: bvl: digita.df, module defenition file
+	* camlibs/digita/digita.df: bvl: digita.df, module definition file
 	to create DLL on OS/2
 
 2000-07-29 04:13  simpson2
@@ -5550,7 +5550,7 @@
 	po/POTFILES.in, po/cat-id-tbl.c, po/project5.pot, po/stamp-cat-id,
 	src/Makefile.am, src/callbacks.c, src/callbacks.h, src/interface.c,
 	src/interface.h, src/main.c, src/support.c, src/support.h: added
-	new gtk inteface beginning code
+	new gtk interface beginning code
 
 2000-07-26 14:25  scottf
 
@@ -5630,7 +5630,7 @@
 	camlibs/directory/directory.def, camlibs/directory/makefile.os2,
 	frontends/command-line/main.c, frontends/command-line/makefile.os2,
 	include/gphoto2.h, include/gphotoos2.h, libgphoto2/library.c,
-	libgphoto2/makefile.os2: bvl: Made some linebreak statments, and
+	libgphoto2/makefile.os2: bvl: Made some linebreak statements, and
 	ifdef correction on behalf of the      OS/2 port
 
 2000-07-22 14:47  scottf
@@ -5677,7 +5677,7 @@
 	camlibs/konica/Makefile.in, camlibs/panasonic/dc.c,
 	camlibs/panasonic/dc.h, camlibs/panasonic/dc1580.c,
 	camlibs/panasonic/dc1580.h, frontends/command-line/.cvsignore,
-	libgphoto2/file.c, libgphoto2/library.c: added a bunch of patchs
+	libgphoto2/file.c, libgphoto2/library.c: added a bunch of patches
 	from Johannes and Mariusz
 
 2000-07-21 14:15  scottf
@@ -6628,7 +6628,7 @@
 	* frontends/: Makefile.am, command-line/Makefile.am,
 	libgphoto2-util/Makefile.am, libgphoto2-util/cache.c,
 	libgphoto2-util/cache.h, libgphoto2-util/image.c,
-	libgphoto2-util/image.h: added beginining of gphoto2 utility
+	libgphoto2-util/image.h: added beginning of gphoto2 utility
 	library for frontends
 
 2000-06-16 14:48  scottf

diff --git a/NEWS b/NEWS
@@ -153,7 +153,7 @@ ptp2:
   * EOS M6 Mark 2 is actually more like a EOS DSLR and fully capable, added some work
   * Handle OLCINFO for M6 Mark 2 and EOS R5 and new cameras
   * added current list of autoexposuremode to expose also Fv and friends
-  * Canon Liveview size is encoded in "output" (PC / MOBILE / MOBILE2 variants are the different livesizes), try to expose seperately as "liveviewsize"
+  * Canon Liveview size is encoded in "output" (PC / MOBILE / MOBILE2 variants are the different livesizes), try to expose separately as "liveviewsize"
   * decode more options, nickname, eosmoviemode (color/bw), strobofiring, eventmode, flashcharged, oneshotrawon
   * bugfixes
 * Sony Alpha:
@@ -1077,7 +1077,7 @@ libgphoto2 API:
    * Adjusted to new GPPortInfo handling.
 
    * Rewrote gphoto2-filesys.c to be directory based (in a tree structure).
-     Change should not be visibile outside of gphoto2-filesys.c.
+     Change should not be visible outside of gphoto2-filesys.c.
 
 libgphoto2_port API:
    * GPPortInfo is now abstracted and internal.
@@ -1654,7 +1654,7 @@ libgphoto2:
    * gp-byteorder.m4 fixes for newer glibcs.
 
 Example programs:
-   * Addes some basic library usage example programs and helpers.
+   * Added some basic library usage example programs and helpers.
 
 PTP2 driver:
    * Merged camlib from TRUNK.
@@ -1846,7 +1846,7 @@ PTP2 driver:
 
  	Canon PowerShot SD1000, SD900, A450, A550, A560, A570, A420, SD40, SD750
  	Canon PowerShot S5 IS, SD1000
-	Canon Digitial IXUS 70, 75, 900Ti, iZ
+	Canon Digital IXUS 70, 75, 900Ti, iZ
 	Canon MV750i
 	Nikon CoolPix S4, S6, P4, L10
 	Nikon DSC D40, 
@@ -1942,7 +1942,7 @@ Ricoh G3:
    * Added Ricoh Caplio R4 id.
 
 Disk port:
-   * Addes Solaris filesystem table handling.
+   * Added Solaris filesystem table handling.
    * Fixed a crasher.
    * Skip "fuse" filesystem.
 

diff --git a/README.md b/README.md
@@ -46,7 +46,7 @@ Your operating system will tell you about that because it is likely to recognize
 the device as a SCSI disk that you can mount (for Linux 'dmesg' will tell you).
 Again, those cameras *cannot* be accessed through libgphoto2. Some of them can
 be switched to use a different communication protocol and might be in that case
-useable with libgphoto2.
+usable with libgphoto2.
 
 Other camera support a protocol called PTP or USB Imaging Devices that has
 been developed by Kodak and other. libgphoto2 does support PTP. Also working

diff --git a/SECURITY.md b/SECURITY.md
@@ -30,7 +30,7 @@ Attack impacts are achieving control over this computer, or blocking its use.
 
 ## Bugs considered security issues
 
-(Mostly for CVE assigments rules.)
+(Mostly for CVE assignments rules.)
 
 In scope of a security attack are the autodetecting protocols support,
 like USB.

diff --git a/camlibs/agfa-cl20/agfa_cl20.c b/camlibs/agfa-cl20/agfa_cl20.c
@@ -694,7 +694,7 @@ camera_init (Camera *camera, GPContext *context)
 	gp_port_set_settings(camera->port, settings );
 
 	/* Camera should return either 0x00 or 0x08, depending on
-	 * wether the PRINT button is depressed. Either way, it
+	 * whether the PRINT button is depressed. Either way, it
 	 * should NOT stay 'X'
 	 */
 

diff --git a/camlibs/agfa-cl20/commands.txt b/camlibs/agfa-cl20/commands.txt
@@ -3,9 +3,9 @@ I don't know what they do exactly.
 
 c1 00 00 00 21 05 01 00
 
-c1 00 00 00 20 05 01 00		This one appeares only right after issuing any delete command
+c1 00 00 00 20 05 01 00		This one appears only right after issuing any delete command
 				41 0a 01 00 0d 00 00 00 (for pic 01). It appears after every
-				 delete comand. I dont't know what
+				delete command. I don't know what
 				it does. The camera answers as usual with a "00" Byte.
 
 41 02 00 00 07 00 00 00		This appears after the

diff --git a/camlibs/agfa-cl20/protocol.txt b/camlibs/agfa-cl20/protocol.txt
@@ -1,4 +1,4 @@
-Okay, let's tell something about the protocoll:
+Okay, let's tell something about the protocol:
 
 Everything can be looked up in the USB 1.1 secification!
 http://www.usb.org/developers/data/usbspec.zip
@@ -14,7 +14,7 @@ I always confuse that. Well, If I have 0x0001 then it sends 01 00, so turned aro
 3. bulk transfers with direction "in"
 
 1. These control packages are always 8 Bytes long. The first
-   Byte is the reqest Type. this is always 0xc1 for direction "in".
+   Byte is the request Type. this is always 0xc1 for direction "in".
   The c1 is a Bitmap:
 7 1	means that the direction is device to host
 6 1	Bits 6 and 5 mean that the "Type" is "Vendor"
@@ -26,7 +26,7 @@ I always confuse that. Well, If I have 0x0001 then it sends 01 00, so turned aro
 0 1
 
 the last two Bytes are always 01 00 the length of the camera reply, so 0x0001 - one Byte.
-The camera always replys with 0x00.
+The camera always replies with 0x00.
 
 
 2. Similar to 1. just the direction is "out".
@@ -36,7 +36,7 @@ The camera always replys with 0x00.
 
 3. these semm to be standard bulk transfers. you just open one, and the camera sends data.
    The direction of this transfer is "in".
-   The trnsfer buffer length is always 0x100.
+   The transfer buffer length is always 0x100.
 
 
 
@@ -74,7 +74,7 @@ As answer we should get:
 07 05 84 03 01 00 08
 
 
-Now it's time to choose a configuration. I believe the camera just has one, but without setting it exlicitly, the camera does nothing!
+Now it's time to choose a configuration. I believe the camera just has one, but without setting it explicitly, the camera does nothing!
 
 So we choose configuration 0x01.
 

diff --git a/camlibs/agfa-cl20/protocol2.txt b/camlibs/agfa-cl20/protocol2.txt
@@ -19,7 +19,7 @@ The specs can be found here:
 http://www.pima.net/standards/it10/PIMA15740/Exif_2-1.PDF
 
 This is a special format which INCLUDES THUMBNAILS. This means, that the picture and the thmbnail are ONE file.
-So what basicallly happens in the windows driver:
+So what basically happens in the windows driver:
 
 It retrieves the EXIF File complete, for example 173kb. I calculated it. It fits. I had 685 Bulk Transfers, 256Bytes each, which makes a total of 175360 Bytes --> my picture (Exif=Thumbnail+picture).
 The Windows driver then extracts the Thumbnail out of the Exif, saves i as JFIF (JPEG) and displays it in the thumbnail overview.
@@ -29,21 +29,21 @@ So, if you have the Exif you automatically have the Thumbnail AND the picture. S
 Interesting is also, that the actual picture, the Exif File, comes in BIG ENDIAN Format. you can see this from the 4d 4d (MM) in the EXIF header.
 
 
-Okay, let's tell something about the protocoll:
+Okay, let's tell something about the protocol:
 
 Everything can be looked up in the USB 1.1 secification!
 That's where I have everything from.
 
 All the communication consists of three usb command types:
 It seems that all the packages have a little endian byte order (least significant byte first?)
-I always cofuse that. Well, If I have 0x0001 then it sends 01 00, so turned around.
+I always confuse that. Well, If I have 0x0001 then it sends 01 00, so turned around.
 
 1. control packages with direction "in"
 2. control packages with direction "out"
 3. bulk transfers with direction "in"
 
 1. These control packages are always 8 Bytes long. The first
-   Byte is the reqest Type. this is always 0xc1 for direction "in".
+   Byte is the request Type. this is always 0xc1 for direction "in".
   The c1 is a Bitmap:
 7 1     means that the direction is device to host
 6 1     Bits 6 and 5 mean that the "Type" is "Vendor"
@@ -55,7 +55,7 @@ I always cofuse that. Well, If I have 0x0001 then it sends 01 00, so turned arou
 0 1
 
 the last two Bytes are always 01 00 the length of the camera reply, so 0x0001 - one Byte.
-The camera always replys with 0x00.
+The camera always replies with 0x00.
 
 
 2. Similar to 1. just the direction is "out".
@@ -65,7 +65,7 @@ The camera always replys with 0x00.
 
 3. these semm to be standard bulk transfers. you just open one, and the camera sends data.
    The direction of this transfer is "in".
-   The trnsfer buffer length is always 0x100.
+   The transfer buffer length is always 0x100.
 
 
 
@@ -103,7 +103,7 @@ As answer we should get:
 07 05 84 03 01 00 08
 
 
-Now it's time to choose a configuration. I believe the camera just has one, but without setting it exlicitly, the camera does not
+Now it's time to choose a configuration. I believe the camera just has one, but without setting it explicitly, the camera does not
 hing!
 
 So we choose configuration 0x01.
@@ -149,7 +149,7 @@ These are the first rows without a flash card:
    0000:
 00 00 00 10 00 ff ff ff ff 31 2e 31 36 ff ff ff
    0010:
-ff ff ff ff 00 03 00 00 00 02 00 00 ff ff 05 09 Maybe the 03 is the nubmer of pictures, but I don't
+ff ff ff ff 00 03 00 00 00 02 00 00 ff ff 05 09 Maybe the 03 is the number of pictures, but I don't
    0020:                                        think so..
 1b 00 00 00 00 00 00 50 01 e0 00 60 00 17 0f 00
    0030:
@@ -181,7 +181,7 @@ Each time I get back a picture information package, looing like (for pic 4 for e
    0020:
 1b 74 01 62 02 11 06 50 01 e0 00 60 00 17 0f 01		ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    0030:
-19 01 1a 01 1b 01 1c 01 1d 01 1e 01 1f 01 20 01		and mor ffs...
+19 01 1a 01 1b 01 1c 01 1d 01 1e 01 1f 01 20 01		and more ffs...
    0040:
 21 01 22 01 23 01 24 01 25 01 26 01 27 01 28 01
    0050:

diff --git a/camlibs/ax203/README.ax203-compression b/camlibs/ax203/README.ax203-compression
@@ -244,13 +244,13 @@ bit weird, but it is how it is.
 ┌─────────┬───────────────────────────────────────────────────────────────────┐
 │ Offset  │                              Meaning                              │
 ├─────────┼───────────────────────────────────────────────────────────────────┤
-│0x00-0x01│Litte Endian 16 bit word storing last DC val for the Y channel     │
+│0x00-0x01│Little Endian 16 bit word storing last DC val for the Y channel    │
 ├─────────┼───────────────────────────────────────────────────────────────────┤
-│0x02-0x03│Litte Endian 16 bit word storing last DC val for the Cb channel    │
+│0x02-0x03│Little Endian 16 bit word storing last DC val for the Cb channel   │
 ├─────────┼───────────────────────────────────────────────────────────────────┤
-│0x04-0x05│Litte Endian 16 bit word storing last DC val for the Cr channel    │
+│0x04-0x05│Little Endian 16 bit word storing last DC val for the Cr channel   │
 ├─────────┼───────────────────────────────────────────────────────────────────┤
-│         │Litte Endian 16 bit word storing the offset into the image, from   │
+│         │Little Endian 16 bit word storing the offset into the image, from  │
 │0x06-0x07│the start of this info block! Where the huffman data for this MCU  │
 │         │starts                                                             │
 └─────────┴───────────────────────────────────────────────────────────────────┘

diff --git a/camlibs/ax203/ax203.c b/camlibs/ax203/ax203.c
@@ -1695,7 +1695,7 @@ ax203_commit(Camera *camera)
 	int dirty_sectors;
 
 	/* We first check each 64k block for dirty sectors. If the block
-	   contains dirty sectors, decide wether to use 4k sector erase
+	   contains dirty sectors, decide whether to use 4k sector erase
 	   commands (if the eeprom supports it), or to erase and reprogram
 	   the entire block */
 	for (i = 0; i < mem_sector_size; i += block_sector_size) {