1.1 --- a/configure.ac Thu May 30 19:26:24 2013 +0100
1.2 +++ b/configure.ac Thu May 30 20:27:45 2013 +0100
1.3 @@ -1,7 +1,7 @@
1.4 # -*- Autoconf -*-
1.5 # Process this file with autoconf to produce a configure script.
1.6
1.7 -AC_INIT([bookloupe],[1.52],[ali@juiblex.co.uk])
1.8 +AC_INIT([bookloupe],[1.90],[ali@juiblex.co.uk])
1.9 AC_PREREQ(2.59)
1.10 AC_CONFIG_AUX_DIR([config])
1.11 AC_CONFIG_SRCDIR([bookloupe/bookloupe.c])
2.1 --- a/doc/bookloupe.txt Thu May 30 19:26:24 2013 +0100
2.2 +++ b/doc/bookloupe.txt Thu May 30 20:27:45 2013 +0100
2.3 @@ -1,30 +1,26 @@
2.4
2.5
2.6 - Gutcheck documentation
2.7 + Bookloupe documentation
2.8
2.9
2.10 -gutcheck: lists possible common formatting errors in a Project
2.11 -Gutenberg candidate file. It is a command line program and can be used
2.12 -under Win32 or Unix (gutcheck.c should compile anywhere; if it doesn't,
2.13 -tell me). For Windows-only people, there is an appendix at the end
2.14 -with brief instructions for running it.
2.15 +bookloupe: lists possible common formatting errors in a Project
2.16 +Gutenberg candidate file. Bookloupe is based on gutcheck, written
2.17 +by Jim Tinsley. It is a command line program and can be used under
2.18 +Microsoft Windows, Mac or Unix. For Windows-only people, there is
2.19 +an appendix at the end with brief instructions for running it.
2.20
2.21 +Current version: 1.90, a beta version leading up to version 2.0
2.22
2.23 -Current version: 0.99. Users of 0.98 see end of file for changes.
2.24 +This software is Copyright Jim Tinsley 2000-2005 and
2.25 +J. Ali Harlow 2012 onwards.
2.26
2.27 -You should also have received the licence file COPYING, a README file,
2.28 -gutcheck.c, the source code, and gutcheck.exe, a DOS executable, with
2.29 -this file.
2.30 -
2.31 -This software is Copyright Jim Tinsley 2000-2005.
2.32 -
2.33 -Gutcheck comes wih ABSOLUTELY NO WARRANTY. For details, read the file COPYING.
2.34 +Bookloupe comes wih ABSOLUTELY NO WARRANTY. For details, read the file COPYING.
2.35 This is Free Software; you may redistribute it under certain conditions (GPL).
2.36
2.37 -See http://gutcheck.sourceforge.net for the latest version.
2.38 +See http://www.juiblex.co.uk/pgdp/bookloupe/ for the latest version.
2.39
2.40
2.41 -Usage is: gutcheck [-setopxlywm] filename
2.42 +Usage is: bookloupe [-setopxlywm] filename
2.43 where:
2.44 -s checks Single quotes
2.45 -e switches off Echoing of lines
2.46 @@ -40,36 +36,43 @@
2.47 -u warns about words in a user-defined typo file gutcheck.typ
2.48 -d ignores some DP-specific markup
2.49
2.50 -Running gutcheck without any parameters will display a brief help message.
2.51 +Running bookloupe without any parameters will display a brief help message.
2.52
2.53 Sample usage:
2.54
2.55 - gutcheck warpeace.txt
2.56 + bookloupe warpeace.txt
2.57
2.58
2.59 More detail:
2.60
2.61 + Character encoding
2.62 +
2.63 + Bookloupe will handle e-texts encoded in UTF-8 (preferred),
2.64 + ISO-8859-1 (also known as Latin-1), or WINDOWS-1252 (also known,
2.65 + incorrectly, as ansi). The output will be in the same encoding
2.66 + as the input e-text.
2.67 +
2.68 Echoing lines (-e to switch off)
2.69
2.70 - You may find it convenient, when reviewing Gutcheck's
2.71 - suggestions, to see the line that Gutcheck is questioning.
2.72 + You may find it convenient, when reviewing Bookloupe's
2.73 + suggestions, to see the line that Bookloupe is questioning.
2.74 That way, you can often see at a glance whether it is
2.75 a real error that needs to be fixed, or a false positive
2.76 - that should be in the text, but Gutcheck's limited
2.77 + that should be in the text, but Bookloupe's limited
2.78 programming doesn't understand.
2.79
2.80 - By default, gutcheck echoes these lines, but if you don't
2.81 + By default, bookloupe echoes these lines, but if you don't
2.82 want to see the lines referred to, -e will switch it OFF.
2.83
2.84
2.85 Quotes (-s and -p switches)
2.86
2.87 - Gutcheck always looks for unbalanced doublequotes in a
2.88 + Bookloupe always looks for unbalanced doublequotes in a
2.89 paragraph. It is a common convention for writers not to
2.90 close quotes in a paragraph if the next paragraph opens
2.91 with quotes and is a continuation by the same speaker.
2.92
2.93 - Gutcheck therefore does not normally report unclosed quotes
2.94 + Bookloupe therefore does not normally report unclosed quotes
2.95 if the next paragraph begins with a quote. If you need
2.96 to see all unclosed quotes, even where the next paragraph
2.97 begins with a quote, you should use the -p switch.
2.98 @@ -84,7 +87,7 @@
2.99 for contractions rather than quotes, but it isn't easy
2.100 to get a program to recognize that.
2.101
2.102 - Since Gutcheck makes too many mistakes when trying to match
2.103 + Since bookloupe makes too many mistakes when trying to match
2.104 singlequotes, it doesn't look for unbalanced singlequotes
2.105 unless you specify the -s switch.
2.106
2.107 @@ -102,7 +105,7 @@
2.108
2.109 Typos (-t switch)
2.110
2.111 - It's not Gutcheck's job to be a spelling checker, but it
2.112 + It's not bookoupe's job to be a spelling checker, but it
2.113 does check for a list of common typos and OCR errors if you
2.114 use the -t switch. (The -x switch also turns typo checking on.)
2.115
2.116 @@ -113,7 +116,7 @@
2.117 playing the odds - a few false positives for many errors found.
2.118 Similarly with "ii", which is a very common OCR error.
2.119
2.120 - Gutcheck suppresses multiple reporting of the first 40 "typos"
2.121 + Bookloupe suppresses multiple reporting of the first 40 "typos"
2.122 found. This is to remove the annoyance of seeing something like
2.123 "FN" (footnote) or "LK" (initials) flagged as a typo 147 times
2.124 in a text.
2.125 @@ -127,11 +130,11 @@
2.126 and Mac have different conventions, but the final text should
2.127 always use a CR/LF pair as its line terminator.
2.128
2.129 - By default, Gutcheck verifies that every line does have
2.130 + By default, bookloupe verifies that every line does have
2.131 the correct terminator, but if you're on a work-in-progress
2.132 in Linux, you might want to convert the line-ends as a final
2.133 step, and not want to see thousands of errors every time you
2.134 - run Gutcheck before that final step, so you can turn off
2.135 + run bookloupe before that final step, so you can turn off
2.136 this checking with the -l switch.
2.137
2.138
2.139 @@ -143,101 +146,103 @@
2.140
2.141 Overview mode (-o switch)
2.142
2.143 - This mode just gives a count of queries found
2.144 - instead of a detailed list.
2.145 + This mode just gives a count of queries found
2.146 + instead of a detailed list.
2.147
2.148
2.149 Header quote (-h switch)
2.150
2.151 - If you use the -h switch, gutcheck will also display
2.152 - the Title, Author, Release and Edition fields from the
2.153 - PG header. This is useful mostly for the automated
2.154 - checks we do on recently-posted texts.
2.155 + If you use the -h switch, bookloupe will also display
2.156 + the Title, Author, Release and Edition fields from the
2.157 + PG header. This is useful mostly for the automated
2.158 + checks we do on recently-posted texts.
2.159
2.160
2.161 Errors to stdout (-y switch)
2.162
2.163 - If you're just running gutcheck normally, you can ignore
2.164 - this. It's only there for programs that provide a front
2.165 - end to gutcheck. It makes error messages appear within
2.166 - the output of gutcheck so that the front end knows whether
2.167 - gutcheck ran OK.
2.168 + If you're just running bookloupe normally, you can ignore
2.169 + this. It's only there for programs that provide a front
2.170 + end to bookloupe. It makes error messages appear within
2.171 + the output of bookloupe so that the front end knows whether
2.172 + bookloupe ran OK.
2.173
2.174
2.175 Verbose reporting (-v switch)
2.176
2.177 - Normally, if gutcheck sees lots of long lines, short lines,
2.178 - spaced dashes, non-ASCII characters or dot-commas ".," it
2.179 - assumes these are features of the text, counts and summarizes
2.180 - them at the top of its report, but does not list them
2.181 - individually. If the -v switch is on, gutcheck will list them all.
2.182 + Normally, if bookloupe sees lots of long lines, short lines,
2.183 + spaced dashes, non-ASCII characters or dot-commas ".," it
2.184 + assumes these are features of the text, counts and summarizes
2.185 + them at the top of its report, but does not list them
2.186 + individually. If the -v switch is on, bookloupe will list them all.
2.187
2.188
2.189 Markup interpretation (-m switch)
2.190
2.191 - Normally, gutcheck flags anything it suspects of being HTML
2.192 - markup as a possible error. When you use the -m switch,
2.193 - however, it matches anything that looks like markup against
2.194 - a short list of common HTML tags and entities. If the markup
2.195 - is in that list, it either ignores the markup, in the case
2.196 - of a tag, or "interprets" the markup as its nearest ASCII
2.197 - equivalent, in the case of an entity. So, for example, using
2.198 - this switch, gutcheck will "see"
2.199 + Normally, bookloupe flags anything it suspects of being HTML
2.200 + markup as a possible error. When you use the -m switch,
2.201 + however, it matches anything that looks like markup against
2.202 + a short list of common HTML tags and entities. If the markup
2.203 + is in that list, it either ignores the markup, in the case
2.204 + of a tag, or "interprets" the markup as its nearest ASCII
2.205 + equivalent, in the case of an entity. So, for example, using
2.206 + this switch, bookloupe will "see"
2.207
2.208 - “He went <i>thataway!</i>”
2.209 + “He went <i>thataway!</i>”
2.210
2.211 - as
2.212 + as
2.213
2.214 - "He went thataway!"
2.215 + "He went thataway!"
2.216
2.217 - and report accordingly.
2.218 + and report accordingly.
2.219
2.220 - This switch does not, not, NOT check the validity of HTML;
2.221 - it exists so that you can run gutcheck on most HTML texts
2.222 - for PG, and get sane results. It does not support all tags.
2.223 - It does not support all entities. When it sees a tag or entity
2.224 - it does not recognize, it will query it as HTML just as if
2.225 - you hadn't specified the -m switch.
2.226 + This switch does not, not, NOT check the validity of HTML;
2.227 + it exists so that you can run bookloupe on most HTML texts
2.228 + for PG, and get sane results. It does not support all tags.
2.229 + It does not support all entities. When it sees a tag or entity
2.230 + it does not recognize, it will query it as HTML just as if
2.231 + you hadn't specified the -m switch.
2.232
2.233 - Gutcheck 0.99 will automatically switch on markup interpretation
2.234 - if it sees a lot of tags that appear to be markup, so mostly, you
2.235 - won't have to specify this.
2.236 + Bookloupe will automatically switch on markup interpretation
2.237 + if it sees a lot of tags that appear to be markup, so mostly, you
2.238 + won't have to specify this.
2.239
2.240 User-defined typos (-u switch)
2.241
2.242 - If you have a file named gutcheck.typ either in your current
2.243 - working directory or in the directory from which you explicitly
2.244 - invoked gutcheck, but not necessarily on your path, and if you
2.245 - specify the -u switch, gutcheck will query any word specified
2.246 - in that file. The file is simple: one word, in lower case, per
2.247 - line. 999 lines are allowed for. Be careful not to put multiple
2.248 - words onto a line, or leave any rubbish other than the word on
2.249 - the line. You should have received a sample file gutcheck.typ
2.250 - with this package.
2.251 + If you have a file named bookloupe.typ or gutcheck.typ either
2.252 + in your current working directory or in the directory from
2.253 + which you explicitly invoked bookoupe, but not necessarily on
2.254 + your path, and if you specify the -u switch, bookloupe will
2.255 + query any word specified in that file. The file is simple: one
2.256 + word, in lower case, per line. Be careful not to put multiple
2.257 + words onto a line, or leave any rubbish other than the word on
2.258 + the line. You should have received a sample file bookloupe.typ
2.259 + with this package. The file may be encoded in UTF-8 (preferred),
2.260 + ISO-8859-1 (also known as Latin-1), or WINDOWS-1252 (also known,
2.261 + incorrectly, as ansi).
2.262
2.263 Ignore DP markup (-d switch)
2.264
2.265 - Distributed Proofreaders (http://www.pgdp.net) is currently
2.266 - (2005) the main source of PG texts, and proofers there use
2.267 - special conventions. This switch understands those conventions,
2.268 - so that people can use gutcheck on files in process that still
2.269 - haven't had the special conventions removed yet. The special
2.270 - conventions supported in 0.99 are page-separators and
2.271 - "<sc>", "</sc>", "/*", "*/", "/#", "#/", "/$", "$/".
2.272 + Distributed Proofreaders (http://www.pgdp.net) has for some
2.273 + time been the main source of PG texts, and proofers there use
2.274 + special conventions. This switch understands those conventions,
2.275 + so that people can use bookloupe on files in process that still
2.276 + haven't had the special conventions removed yet. The special
2.277 + conventions supported are page-separators and
2.278 + "<sc>", "</sc>", "/*", "*/", "/#", "#/", "/$", "$/".
2.279
2.280
2.281 -You will probably only run gutcheck on a text once or maybe twice,
2.282 +You will probably only run bookloupe on a text once or maybe twice,
2.283 just prior to uploading; it usually finds a few formatting problems;
2.284 it also usually finds queries that aren't problems at all - it often
2.285 questions Tables of Contents for having short lines, for example.
2.286 -These are called "false positives", and need a human to decide on
2.287 +These are called "false positives," and need a human to decide on
2.288 them.
2.289
2.290 The text should be standard prose, and already close to PG normal
2.291 format (plain text, about 70 characters per line with blank lines
2.292 between paragraphs).
2.293
2.294 -Gutcheck merely draws your attention to things that might be errors.
2.295 +Bookloupe merely draws your attention to things that might be errors.
2.296 It is NOT a substitute for human judgement. Formatting choices like
2.297 short lines may be for a reason that this program can't understand.
2.298
2.299 @@ -246,8 +251,8 @@
2.300 them. Of these, spellchecking (with _very_ careful human judgement) is
2.301 the most important and most useful.
2.302
2.303 -Gutcheck does perform some basic typo-checking if you ask it to,
2.304 -but its focus is on formatting errors specific to PG texts -
2.305 +Bookloupe does perform some basic typo-checking if you ask it to,
2.306 +but its focus is on formatting errors specific to PG texts—
2.307 mismatched quotes, non-ASCII characters, bad spacing, bad line
2.308 length, HTML tags perhaps left from a conversion, unbalanced
2.309 brackets.
2.310 @@ -258,7 +263,7 @@
2.311
2.312
2.313
2.314 - How do _I_ use it?
2.315 + How does Jim Tinsley use gutcheck?
2.316
2.317 Practically everyone I give gutcheck to asks me how _I_ use it.
2.318 Well, when I get a text for posting, say filename.txt, I run
2.319 @@ -291,33 +296,23 @@
2.320
2.321
2.322
2.323 - Future development of gutcheck
2.324 + Future development of bookloupe
2.325
2.326 -Gutcheck has gone about as far as it can, given its current
2.327 -structure. In order to add better singlequotes checking,
2.328 -sentence checking, better he/be checking and other good stuff
2.329 -that I'd like to see, I'll have to rewrite it from a different
2.330 -angle - looking at the syntax instead of the lines. And I'll
2.331 -probably get around to that sooner or later.
2.332 +Bookloupe version 2.0 is intended to add UTF-8 support to
2.333 +gutcheck. All the functionality should already be implemented
2.334 +in the beta versions leading up to version 2.0, although
2.335 +some bugs may well remain.
2.336
2.337 -Meantime, I'm just trying to get this version stabilized, so
2.338 -please report any bugs you find. When it is stable, I'll run
2.339 -up a Windows port for those timid souls who can't look a
2.340 -command line in the eye. :-)
2.341 +Future versions will add support for UTF-8 characters that
2.342 +are not in ISO-8859-1 (eg., curled quotation marks);
2.343 +characters that do not have a composed form (version 2
2.344 +treats these as taking 2 or more columns); zero width and
2.345 +wide characters (version 2 treats these as taking 1 column).
2.346
2.347 -And I've started work on gutspell, a companion to gutcheck
2.348 -which will concentrate on spelling problems. PG spelling
2.349 -problems are unusual, since the range of texts we cover is
2.350 -so wide, and I'll be taking a somewhat unorthodox approach
2.351 -to writing this spelling-checker _specifically_ for texts
2.352 -containing a lot of dialect and uncommon words that have
2.353 -probably already been spell-checked against a standard
2.354 -modern dictionary.
2.355
2.356
2.357
2.358 -
2.359 -Explanations of common gutcheck messages:
2.360 +Explanations of common bookloupe messages:
2.361
2.362 --> 74 lines in this file have white space at end
2.363
2.364 @@ -330,7 +325,7 @@
2.365 --> 84 lines in this file are long. Not reporting long lines.
2.366 --> 8 lines in this file are VERY long!
2.367
2.368 - If there are a lot of long or short lines, Gutcheck won't list
2.369 + If there are a lot of long or short lines, bookloupe won't list
2.370 them individually. The short lines version of this message
2.371 is commonly seen when gutchecking poetry and some plays, where
2.372 the normal line length is shorter than the standard for prose.
2.373 @@ -345,7 +340,7 @@
2.374 The PG standard for an emdash--like these--is two minus signs
2.375 with no spaces before or after them. However, some older texts
2.376 used spaced dashes - like these -- and if there are very many
2.377 - such spaced dashes in the file, gutcheck just draws your
2.378 + such spaced dashes in the file, bookoupe just draws your
2.379 attention to it and doesn't list them individually.
2.380
2.381
2.382 @@ -357,12 +352,11 @@
2.383 represented according to several different non-ASCII encoding
2.384 schemes, using values over 127. If you have a plain English text
2.385 with a few accented characters in words like cafe or tete-a-tete,
2.386 - you should replace the accented characters with their unaccented
2.387 + you might replace the accented characters with their unaccented
2.388 versions. The English pound sign is another commonly-seen
2.389 non-ASCII character. If you have enough non-ASCII characters in
2.390 - your text that you feel removing them would degrade your text
2.391 - unacceptably, you should probably consider doing an 8-bit text
2.392 - as well as a plain-ASCII version.
2.393 + your text that you feel removing them would degrade your text,
2.394 + you should probably consider doing a UTF-8 text.
2.395
2.396
2.397
2.398 @@ -391,7 +385,7 @@
2.399
2.400 The tilde character (~) might be legitimately used, but it's the
2.401 character commonly used by OCR software to indicate a place where
2.402 - it couldn't make out the letter, so gutcheck flags it.
2.403 + it couldn't make out the letter, so bookloupe flags it.
2.404
2.405
2.406
2.407 @@ -407,7 +401,7 @@
2.408
2.409 PG texts should have lines shorter than 76. There may be occasions
2.410 where you decide that you really have to go out to 79 characters,
2.411 - but the sample above says that line 1451 is 129 characters long -
2.412 + but the sample above says that line 1451 is 129 characters long—
2.413 probably two lines run together.
2.414
2.415
2.416 @@ -416,12 +410,12 @@
2.417
2.418 PG texts should have lines longer than 54 characters. However,
2.419 there are special cases like poetry and tables of contents where
2.420 - the lines _should_ be shorter. So treat Gutcheck warnings about
2.421 + the lines _should_ be shorter. So treat bookloupe warnings about
2.422 short lines carefully. Sometimes it's a genuine formatting
2.423 problem; sometimes the line really needs to be short.
2.424
2.425 - Hint: gutcheck will not flag lines as short if they are indented
2.426 - - if they start with a space. I like to start inserted stanzas
2.427 + Hint: bookloupe will not flag lines as short if they are indented
2.428 + —if they start with a space. I like to start inserted stanzas
2.429 and other such items indented with a couple of spaces so that
2.430 they stand out from the main text anyway.
2.431
2.432 @@ -437,7 +431,7 @@
2.433 Line 1850 - Spaced em-dash?
2.434
2.435 The PG standard for an em-dash--like these--is two minus signs
2.436 - with no spaces before or after them. Gutcheck flags non-PG
2.437 + with no spaces before or after them. Bookloupe flags non-PG
2.438 em-dashes - like this one. Normally, you will replace it with a
2.439 PG-standard em-dash.
2.440
2.441 @@ -445,7 +439,7 @@
2.442
2.443 Line 1904 - Query he/be error?
2.444
2.445 - Gutcheck makes a very minor effort to look for that scourge of all
2.446 + Bookloupe makes a very minor effort to look for that scourge of all
2.447 proofreaders, "be" replacing "he" or vice-versa, and draws your
2.448 attention to it when it thinks it has found one.
2.449
2.450 @@ -454,7 +448,7 @@
2.451 Line 2017 - Query digit in a1most
2.452
2.453 The digit 1 is commonly OCRed for the letter l, the digit 0 for
2.454 - the letter O, and so on. When gutcheck sees a mix of digits and
2.455 + the letter O, and so on. When bookloupe sees a mix of digits and
2.456 letters, it warns you. It may generate a false positive for
2.457 something like 7am.
2.458
2.459 @@ -462,7 +456,7 @@
2.460
2.461 Line 2083 - Query standalone 0
2.462
2.463 - In paranoid mode (see -x) only, gutcheck warns about the digit 0
2.464 + In paranoid mode (see -x) only, bookloupe warns about the digit 0
2.465 and the number 1 standing alone as a word. This can happen if the
2.466 OCR misreads the words O or I.
2.467
2.468 @@ -470,7 +464,7 @@
2.469
2.470 Line 2115 - Query word whetber
2.471
2.472 - If you have switched typo-checking on, gutcheck looks for
2.473 + If you have switched typo-checking on, bookloupe looks for
2.474 potential typos, especially common h/b errors. It's not
2.475 infallible; it sometimes queries legit words, but it's
2.476 always worth taking a look.
2.477 @@ -504,10 +498,9 @@
2.478
2.479 Line 2385 column 27 - Wrongspaced quotes?
2.480
2.481 - As of version 0.98, gutcheck adds extra checks on whether a quote
2.482 - seems to be a start or end quote, and queries those that appear to
2.483 - be misplaced. This does give rise to false positives when quotes are
2.484 - nested, for example:
2.485 + Bookloupe checks whether a quote seems to be a start or end quote,
2.486 + and queries those that appear to be misplaced. This does give rise
2.487 + to false positives when quotes are nested, for example:
2.488
2.489 "And how," she asked, "will your "friends" help you now?"
2.490
2.491 @@ -540,14 +533,14 @@
2.492
2.493 Line 2540 - Mismatched quotes
2.494
2.495 - Another gutcheck mainstay - unclosed doublequotes in a paragraph.
2.496 + Another bookloupe mainstay—unclosed doublequotes in a paragraph.
2.497 See the discussion of quotes in the switches section near the
2.498 start of this file.
2.499
2.500 - Since the mismatch doesn't occur on any one line, gutcheck quotes
2.501 + Since the mismatch doesn't occur on any one line, bookloupe quotes
2.502 the line number of the first blank line following the paragraph,
2.503 since this is the point where it reconciles the count of quotes.
2.504 - However, if gutcheck is echoing lines, that is, you haven't used
2.505 + However, if bookloupe is echoing lines, that is, you haven't used
2.506 the -e switch, it will show the _first_ line of the paragraph,
2.507 to help you find the place without using line numbers. The
2.508 offending paragraph is therefore between the quoted line and
2.509 @@ -611,36 +604,36 @@
2.510 For Windows-only users who are unfamiliar with DOS:
2.511
2.512 If you're a Windows-only user, you need to save
2.513 - gutcheck.exe into the folder (directory) where the
2.514 + bookloupe.exe into the folder (directory) where the
2.515 text file you want to check is. Let's say your
2.516 - text file is in C:\GUT, then you should save
2.517 - GUTCHECK.EXE into C:\GUT.
2.518 + text file is in C:\gut, then you should save
2.519 + bookloupe.exe into C:\gut.
2.520
2.521 - Now get to a DOS prompt. You can do this by
2.522 + Now get to a console. You can do this by
2.523 selecting the "Command Prompt" or "MS-DOS Prompt"
2.524 option that will be somewhere on your
2.525 Start/Programs menu.
2.526
2.527 - Now get into the C:\GUT directory.
2.528 - You can do this using the CD (change directory)
2.529 + Now get into the C:\gut directory.
2.530 + You can do this using the cd (change directory)
2.531 command, like this:
2.532 - CD \GUT
2.533 + cd \gut
2.534 and your prompt will change to
2.535 - C:\GUT>
2.536 + C:\gut>
2.537 so you know you're in the right place.
2.538
2.539 Now type
2.540 - gutcheck yourfile.txt
2.541 - and you'll see gutcheck's report
2.542 + bookloupe yourfile.txt
2.543 + and you'll see bookloupe's report
2.544
2.545 - By default, gutcheck prints its queries to screen.
2.546 + By default, bookloupe prints its queries to screen.
2.547 If you want to create a file of them, to edit
2.548 against the text, you can use the greater-than
2.549 sign (>) to tell it to output the report to a
2.550 file. For example, if you want its report in a
2.551 - file called QUERIES.LST, you could type
2.552 -
2.553 - gutcheck yourfile.txt > queries.lst
2.554 + file called queries.lst, you could type
2.555 +
2.556 + bookloupe yourfile.txt > queries.lst
2.557
2.558 The queries.lst file will then contain the listing
2.559 of possible formatting errors, and you can
2.560 @@ -649,7 +642,7 @@
2.561 Whatever you do, DON'T make the filename after
2.562 the greater-than sign the name of a file already
2.563 on your disk that you want to keep, because
2.564 - the greater-than sign will cause gutcheck to
2.565 + the greater-than sign will cause bookloupe to
2.566 replace any existing file of that name.
2.567
2.568 So, for example, if you have two Tolstoy files
2.569 @@ -658,85 +651,11 @@
2.570 is ever used following the greater-than sign.
2.571 To check these correctly, you might do:
2.572
2.573 - gutcheck warpeace.txt >war.lst
2.574 + bookloupe warpeace.txt > war.lst
2.575
2.576 and
2.577
2.578 - gutcheck annak.txt > annak.lst
2.579 + bookloupe annak.txt > annak.lst
2.580
2.581 separately. Then you can look at war.lst and annak.lst
2.582 - to see the gutcheck reports.
2.583 -
2.584 - * * * *
2.585 -
2.586 -
2.587 -For existing 0.98 users upgrading to 0.99:
2.588 -
2.589 - If you run on old 16-bit DOS or Windows 3.x, I'm afraid
2.590 - you're out of luck. I'm not saying it _can't_ be compiled
2.591 - to run on 16-bit, but the executable with the package is
2.592 - for Win32 only. *nix users won't notice the change at all.
2.593 -
2.594 -
2.595 - There are two new switches: -u and -d.
2.596 - See above for full rundown.
2.597 -
2.598 -
2.599 -Here's a list of the new errors:
2.600 -
2.601 - Line 1456 - Carat character?
2.602 -
2.603 - I^ve found a few.
2.604 -
2.605 -
2.606 - Line 1821 - Forward slash?
2.607 -
2.608 - Common error for italicized "I", or so /'ve found.
2.609 -
2.610 -
2.611 - Line 2139 - Query missing paragraph break?
2.612 -
2.613 - "Come here, son." "Do I _have_ to go, dad?"
2.614 - Like that. False positives in some texts. Sorry 'bout that,
2.615 - but these are often errors.
2.616 -
2.617 -
2.618 - Line 2200 - Query had/bad error?
2.619 -
2.620 - Clear enough. Doesn't catch as many as I'd like it to,
2.621 - but rarely gives false alarms.
2.622 -
2.623 -
2.624 - Line 2268 - Query punctuation after the?
2.625 -
2.626 - Some words, like "the", very rarely have punctuation
2.627 - following them. Others, like "Mrs", usually have a
2.628 - period, but never a comma. Occasional false positives.
2.629 -
2.630 -
2.631 - Line 2380 - Query possible scanno arid
2.632 -
2.633 - It found one of your user-defined typos when you
2.634 - used the -u switch.
2.635 -
2.636 -
2.637 - Line 2511 - Capital "S"?
2.638 -
2.639 - Surprisingly common specific case, like: Jane'S
2.640 -
2.641 -
2.642 - Line 3469 - endquote missing punctuation?
2.643 -
2.644 - OK. This one can really cause a lot of false positives
2.645 - in some books, but it switches itself off if it finds
2.646 - more than 20 in a text, unless you force it to list them
2.647 - all with the -v switch.
2.648 - "Hey, dad" Johnny said, "can we go now?"
2.649 - is a common punctuation-missing error.
2.650 -
2.651 -
2.652 - Line 4266 - Mismatched underscores?
2.653 -
2.654 - Like mismatched anything else!
2.655 -
2.656 -
2.657 + to see the bookloupe reports.