Package: svgatextmode
Version: 1.9-19
Severity: minor
Tags: patch

Found some typos in '/usr/share/man/man5/TextConfig.5.gz', see attached '.diff'.

Hope this helps...

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/dash

Versions of packages svgatextmode depends on:
ii  kbd-compat [kbd]         1:0.2.3dbs-65.1 Wrappers around console-tools for 
ii  libc6                    2.7-11          GNU C Library: Shared libraries

svgatextmode recommends no packages.

-- no debconf information

--- TextConfig.5        2007-09-20 21:07:14.000000000 -0400
+++ /tmp/TextConfig.5   2008-05-20 01:03:44.000000000 -0400
@@ -31,7 +31,7 @@
 .SS Config file syntax rules
 Basically, the TextConfig file is scanned on a line-per-line basis, with no
 specific ordering whatsoever forced upon the user. A line can appear
-enywhere in the config file, and will have the same effect.
+anywhere in the config file, and will have the same effect.
 
 If the same definition (option, chipset, clockchips, mode lines, ...)
 appears twice in the config file, the LAST instance will be used, and all
@@ -54,10 +54,10 @@
 names, ClockChip names, Chipset names, etc.
 
 Configuration lines start with a \fBkeyword\fP, which tells SVGATextMode
-what this line is about. Modelines can have the prefix "modeline", but this
+what this line is about. Mode lines can have the prefix "modeline", but this
 is not a requirement.
 
-Mode description lines start with an opional \`modeline\', and then a mode
+Mode description lines start with an optional \`modeline\', and then a mode
 label, (any text enclosed in quotes), followed by at least 9 numbers
 describing the mode timings. A description of the meaning of these mode
 timings should be in the MODE TIMINGS section. Note that the mode label is
@@ -78,7 +78,7 @@
 
 .SS Safety tip
 When trying to create a new mode of your own, consider "testing" it first
-non-destuctively: use
+non-destructively: use
 
 .IP
 .B SVGATextMode -n <\fIMyNewMode\fP>
@@ -98,7 +98,7 @@
 
 .SS ChipSet \fI<some_chip>\fP
 This keyword tells SVGATextMode which SVGA chipset needs to be programmed.
-The syntax is straighforward:
+The syntax is straightforward:
 
 .IP
 \fBChipset "S3"\fP
@@ -151,13 +151,13 @@
 clock setting program, not the default or ClockChip method.
 
 This is especially useful for unsupported cards, or supported cards with
-unsupported clock chips, because the clock porgramming is about the only
+unsupported clock chips, because the clock programming is about the only
 thing that needs to know what chip we're talking about.
 
 It's also a useful stub for plugging in replacements for buggy or wrong
 SVGATextMode clock code.
 
-The syntax is rougly the same as the syntax for the XFree clock program, and
+The syntax is roughly the same as the syntax for the XFree clock program, and
 indeed any clock program written for XFree 3 should plug in without a
 glitch. In theory.
 
@@ -207,7 +207,7 @@
 in the range 1-254 otherwise.
 
 .B NOTE:
-as mentionned in the text above, you need to specify a clocks line, although
+as mentioned in the text above, you need to specify a clocks line, although
 the clock chip can (in most cases) make any clock within a certain range,
 and not just the ones in the clocks line. This requirement is necessary for
 external clock programs that program an "old-style" clock chip with just a
@@ -265,7 +265,7 @@
 Clocks line). See the Clockprog section for a full explanation of the use of
 the "ClockProg" keyword.
 
-All cases not mentionned above will need a "Clocks" line, or a set of clocks
+All cases not mentioned above will need a "Clocks" line, or a set of clocks
 lines.
 
 Any line in the TextConfig file that starts with "Clocks" will be used, and
@@ -326,7 +326,7 @@
 .SS Terminals <\fIterm_dev0\fP> [ \fI<term_dev1>...\fP ]
 The \`Terminals\' line tells SVGATextMode which terminal devices will be
 affected by a possible screen resize, and need to be resized. It will resize
-all mentionned terminals after switching to another mode. This "resizing"
+all mentioned terminals after switching to another mode. This "resizing"
 consists of sending a `SIGWINCH' to all specified virtual terminals.
 
 The usefulness of this option depends on the Linux kernel version you are
@@ -380,7 +380,7 @@
 
 .SS ResetProg <\fI/path/to/ResetProg\fP>
 The "reset program" is called when SVGATextMode has finished its job
-succesfully, but only when a ResetProg is defined.
+successfully, but only when a ResetProg is defined.
 .TP
 The path must be a fully specified path, as in
 ResetProg "/etc/resize_gpm"
@@ -443,7 +443,7 @@
 FontProg "/usr/bin/setfont -u def.uni"
 
 This would be required if you load a raw font file without a unicode map in
-it. Without that extra option, setfont would irradicate the original unicode
+it. Without that extra option, setfont would eradicate the original unicode
 mapping. If this sounds a bit cryptic: it means, amongst other things, that
 you will loose the "high-ascii" characters (aka box-characters) used by many
 text-based menuing systems (e.g. minicom).
@@ -509,7 +509,7 @@
 
 .SS Cursor <\fIstart\fP>-<\fIend\fP>
 Depending on personal preference, and on the type of screen you work on, the
-standard undercore cursor might be unsatisfactory. This type of cursor for
+standard underscore cursor might be unsatisfactory. This type of cursor for
 example is too small to be useful on laptop screens.
 
 This keyword allows a fully programmable cursor size. To avoid needing a
@@ -605,7 +605,7 @@
 .SS DacSpeed <\fIFrequency\fP>
 This line overrides the built-in maximum pixel clock speed for text mode for
 the specified chipset. Since most VGA card manufacturers don't bother
-mentionning this value in their data sheets, the defaults were "guessed"
+mentioning this value in their data sheets, the defaults were "guessed"
 from reports from users. The values are by no means "absolute", and they are
 no guarantee that staying below them will NOT cause trouble (although it's
 pretty sure), and also they are no guarantee that anything ABOVE that
@@ -682,7 +682,7 @@
 clocks. Read the file `doc/FAQ' in the SVGAtextMode distribution for a
 more in-depth discussion about this.
 
-The limits given above (and used as a default) are empyrical. This means
+The limits given above (and used as a default) are empirical. This means
 they resulted from experiments, and are thus not taken from the VGA chip
 maker's specifications. This is the correct place to introduce the
 expression "your mileage may vary": your card may be better, or worse. VGA
@@ -691,7 +691,7 @@
 
 If you see unstable characters, wrong characters (e.g. a "z" where you
 expect an "e"), character crawling, Mighty Morphing Power Characters (TM),
-colomns of characters from the left of the screen repeated towards the
+columns of characters from the left of the screen repeated towards the
 right, drop-outs (fixed positions on the screen where characters won't
 display) characters shifted down by one pixel line relative to the others,
 or something closer to noise than to text, you are most probably over the
@@ -911,7 +911,7 @@
 .TP
 .B MATROX
 Only the Millennium and the Mystique are supported (the older cards aren't).
-Clockchip "ti3026" (for the Millenium) and "mystique" (for the Mystique) are
+Clockchip "ti3026" (for the Millennium) and "mystique" (for the Mystique) are
 the clockchips for the respective cards.
 
 .TP
@@ -1157,14 +1157,14 @@
 
 This is especially probable (but still very rare) when overriding the
 default maximum DacSpeed, and severely overdriving the VGA card's text mode
-capabilities. As mentionned above, Cirrus Logic cards are dangerous
+capabilities. As mentioned above, Cirrus Logic cards are dangerous
 customers when you start tweaking the DRAM speed.
 
 So, just to be on the safe side, use this option when tweaking DRAM speed or
 RAMDAC speed, until you are confident that the system is stable enough.
 
 In this case, the SyncDisks option can at least avoid data loss when the
-system hangs, although it cannot avoid the filesystem check that will result
+system hangs, although it cannot avoid the file system check that will result
 from the reset.
 
 The sync option is enabled by default in the configuration file. It will
@@ -1446,7 +1446,7 @@
 SVGATextMode "100x37"
 
 .PP
-the program will try to program the mode descibed on this line.
+the program will try to program the mode described on this line.
 
 .TP
 \fBIMPORTANT NOTE\fP:
@@ -1483,7 +1483,7 @@
 blanked (unused) size.
 
 See the XFree documentation for a thorough understanding of these, or try
-the monitor timing tuturial in the distribution. See also below in the
+the monitor timing tutorial in the distribution. See also below in the
 section on 9-pixel fonts for some explanation on the effect of selecting an
 9-pixel font on these timings!
 
@@ -1524,8 +1524,8 @@
 .fi
 
 .SS 600 632 638 670
-Vertical Timings. Equivalent to the horizontal ones. The number of textlines
-(rows) in your textmode will depend on the font size selected:
+Vertical Timings. Equivalent to the horizontal ones. The number of text lines
+(rows) in your text mode will depend on the font size selected:
 
 .IP
 .nf
@@ -1534,7 +1534,7 @@
 
 .PP
 Here we have 600 active lines, and a font of 16 pixels high (see below), so
-there will be 600/16 = 37 textlines.
+there will be 600/16 = 37 text lines.
 
 Deriving the vertical refresh is even easier than horizontal: just do
 
@@ -1548,7 +1548,7 @@
 
 .SS Mode line attributes
 The following sections describe the possible attributes a mode line can
-have. They define the sync polariries, the font size to use, and DoubleScan
+have. They define the sync polarities, the font size to use, and DoubleScan
 operation.
 
 .SS -Hsync +Vsync
@@ -1582,7 +1582,7 @@
 for example have only 4 programmable modes, and when you've just tweaked
 X-windows into some weird modes, you might run out of user-settable modes.
 It might be a good idea to try to create standard SVGA timings for your
-textmodes (including the correct sync polarities), so your monitor
+text modes (including the correct sync polarities), so your monitor
 recognises them, without needing an extra entry in its screen parameter
 database.
 
@@ -1600,7 +1600,7 @@
 
 .SS font 8x16
 Font size: "font HxV" selects the horizontal size (character width = H) and
-vertical size (character heigth = V) of the textmode font. The possible
+vertical size (character height = V) of the text mode font. The possible
 ranges are:
 
 .IP
@@ -1722,7 +1722,7 @@
 shifts the screen to the left with an equal amount of character cells (i.e.
 "HShift 0" doesn't do anything).
 
-This parameter is useful for modelines where you can't get the display to
+This parameter is useful for mode lines where you can't get the display to
 move to the left side enough by changing the sync position. Take for example
 this modeline:
 

Reply via email to