Package: svgatextmode Version: 1.9-19 Severity: minor Tags: patch
Found some typos in '/usr/share/man/man8/grabmode.8.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
--- grabmode.8 2007-09-20 21:07:14.000000000 -0400 +++ /tmp/grabmode.8 2008-05-20 01:13:01.000000000 -0400 @@ -350,7 +350,7 @@ the mode grabber can then check if the current mode has exactly HALF the amount of lines of one of these modes: 240, 300, ..., 600 lines. If so, it ASSUMES (!) that this is an interlaced mode, and changes the timings -accoringly before displaying them. +accordingly before displaying them. This immediately shows that the mode grabber will not be able to detect non-standard interlaced modes. @@ -398,13 +398,13 @@ compiled using a commercial DOS C compiler, and required a lot of special code. The latest version was compiled using DJGPP version 2.0, the GNU C compiler for DOS. This required almost no special code, and thus it is a -cleaner port. BUT... It needs DPMI (DOS Proteced Mode Interface). A DMPI +cleaner port. BUT... It needs DPMI (DOS Protected Mode Interface). A DMPI environment can be found in MS-Windows (DOS boxes), OS/2, Windows-NT, qdpmi, 386max, etc. A free DMPI program is included in the distribution (The DJGPP DPMI program CWSDPMI). Scanmode.exe scans all VGA modes from the DOS BIOS, including the VESA -modes, and outputs two files in the currect directory: tconfig and xconfig. +modes, and outputs two files in the current directory: tconfig and xconfig. The text modes are stored in the tconfig file, and the graphics modes are stored in xconfig. @@ -419,7 +419,7 @@ .SH BUGS Is there an entry in the Guinness book of Records for amount-of-bugs/code-size ratio? This program would come in second (just -behind MicroSoft). +behind Microsoft). .SS clock probing accuracy The clock probe (used by clockprobe and grabmode) works best when the system @@ -458,7 +458,7 @@ multiplexing, ..., will cause grabmode to fail to detect the correct number of pixels per line. And because the horizontal sync and clock speed are all calculated from the H and V timings, they too are wrong. The vertical sync -speed is ALWAYS correct, since it is MEASURED, independantly from ANY timing +speed is ALWAYS correct, since it is MEASURED, independently from ANY timing register. .SS grabmode.exe limitations @@ -492,12 +492,12 @@ .SS grabmode caveats Too many to count. Or even more... -Most bugs not yet mentionned above result from the various assumptions the +Most bugs not yet mentioned above result from the various assumptions the mode grabber has to make along the way, which in turn is caused by the wealth of different methods VGA chip makers come up with to make special mode programming non-standard. -As mentionned above, the following special modes could cause grabmode and/or +As mentioned above, the following special modes could cause grabmode and/or clockprobe to get it all wrong: .IP @@ -519,13 +519,13 @@ Some IBM 8514 compatible cards (like ATI Mach) use a completely different set of registers than the normal VGA set when they are in graphics mode. -Because of the chipset-independance of grabmode, grabmode will not notice +Because of the chipset-independence of grabmode, grabmode will not notice this, and report the values which are in the now unused VGA register set. In most cases, this is the text mode from which the graphics program (XFree86, for example) was started. The main reason for all these problems are the author's stubbornness -(combined with a fair amount of lazyness) to keep grabmode +(combined with a fair amount of laziness) to keep grabmode chipset-independent. .SS Summary @@ -553,6 +553,6 @@ The `doc' directory in the SVGATextMode distribution contains a lot of miscellaneous documentation on a range of topics related to configuring and -using SVGATextMode. The monitor timing tuturial in the SVGATextMode +using SVGATextMode. The monitor timing tutorial in the SVGATextMode distribution could be a handy reference for understanding mode timings.
