diff --git a/README b/README index de1258b..ab6f9a7 100644 --- a/README +++ b/README @@ -12,7 +12,7 @@ directory, or unpack a created archive, cd into its top-level directory and follow the instructions provided in the INSTALL file found there. Alternatively, binary ready-to-install versions of the yodl program are -available in verious Linux distributions, in particular Debian. See, e.g., +available in various Linux distributions, in particular Debian. See, e.g., https://packages.debian.org/search?keywords=yodl&searchon=names&suite=all§ion=all Github's web-pages for yodl are here: diff --git a/yodl/CHANGES b/yodl/CHANGES index 36ad601..d874486 100644 --- a/yodl/CHANGES +++ b/yodl/CHANGES @@ -155,7 +155,7 @@ It differs from the previous (1.31) version in the following aspects: (texinfo), or because the format appears to be somewhat obsolete (sgml). - - Added a Yodl document type `letter', indended to be used with the + - Added a Yodl document type `letter', intended to be used with the `brief.cls' LaTeX documentclass - Yodl 2.00 converts documents much faster than earlier versions. @@ -179,7 +179,7 @@ It differs from the previous (1.31) version in the following aspects: - 2man: verb*() fixed - 2texinfo fixes: @top, Toplevel, \input texinfo - 2tely: mudela() -> @mudela - - 2texinfo: nicer handling of wierd nodenames ... NOT: + - 2texinfo: nicer handling of weird nodenames ... NOT: see comment in yodl2texinfo-post.py: urg @@ -324,7 +324,7 @@ It differs from the previous (1.31) version in the following aspects: - took debian/control,copyright changes to *.in source files 1.31.2.jbr2 - -src/yodl/message.c: va_end is doesn't do much on alot of platforms, + -src/yodl/message.c: va_end is doesn't do much on a lot of platforms, but it is proper. -src/yodl/grampipethrough.c: Major NT hack. The popen on NT seems to be leaking process slots. With this patch I can at least build diff --git a/yodl/PATCHES.txt b/yodl/PATCHES.txt index 1e3d714..ba0a141 100644 --- a/yodl/PATCHES.txt +++ b/yodl/PATCHES.txt @@ -131,7 +131,7 @@ SYNCHRONISE If you're not very quick with sending your patch, there's a good chance that an new release of Yodl comes available. In -such a case (and sometimes for other unkown reasons :-), the +such a case (and sometimes for other unknown reasons :-), the maintainer will probably ask you to make a new patch against the latest release. Your best bet is to download the latest release, and apply your patch against this new source tree: diff --git a/yodl/changelog b/yodl/changelog index 75dbd39..f2b8274 100644 --- a/yodl/changelog +++ b/yodl/changelog @@ -424,13 +424,13 @@ yodl (2.04) * The generic `yodl2whatever' has been given two more options to allow users to prevent file-collisions when the same user calls yodl to process a - document while another invokation of yodl by that user is still running: + document while another invocation of yodl by that user is still running: --tmp=: By default, the temporary file is written in the /tmp directory. Specify an alternate directory using --tmp = path-to-alternate-tmp-directory --unique-output: By default, yodl will use a temporary output file that - is rewritten at each new yodl-invokation. If that's not + is rewritten at each new yodl-invocation. If that's not what you want, specify the --unique-output flag, which will use the process-id as part of the temporary output file. This file is NOT removed when the yodl-conversion diff --git a/yodl/macros/rawmacros/xxmlatcontext.raw b/yodl/macros/rawmacros/xxmlatcontext.raw index 6f6b196..5b5cc1f 100644 --- a/yodl/macros/rawmacros/xxmlatcontext.raw +++ b/yodl/macros/rawmacros/xxmlatcontext.raw @@ -1,5 +1,5 @@ - Only avaiable in xml conversion mode. If at XML-context ARG it generates + Only available in xml conversion mode. If at XML-context ARG it generates ARG2 otherwise it generates ARG3 <> diff --git a/yodl/macros/rawmacros/xxsetxmldocumentheader.raw b/yodl/macros/rawmacros/xxsetxmldocumentheader.raw index a0955aa..00be0d3 100644 --- a/yodl/macros/rawmacros/xxsetxmldocumentheader.raw +++ b/yodl/macros/rawmacros/xxsetxmldocumentheader.raw @@ -1,7 +1,7 @@ Set doc header in xml: title, author, date. Call after XXstardocument(). - The title is generated as a separte heading, as the title is part of the + The title is generated as a separate heading, as the title is part of the preamble. The webplatform prints the title that is mentioned in the preamble in the displayed page. diff --git a/yodl/manual/yo/converters/intro.yo b/yodl/manual/yo/converters/intro.yo index cfb7990..84be7f0 100644 --- a/yodl/manual/yo/converters/intro.yo +++ b/yodl/manual/yo/converters/intro.yo @@ -1,5 +1,5 @@ Each macro package handling a conversion from Yodl to a given output format -has its pecularities. Although the various macro packages are very similar, +has its peculiarities. Although the various macro packages are very similar, they do show some differences, due to the unique characteristics of the output formats. Normally, these differences should not cause difficulties in performing the conversion(s). In this chapter the conversion of a Yodl diff --git a/yodl/manual/yo/macros/doctypes.yo b/yodl/manual/yo/macros/doctypes.yo index 7f553fd..953d5cf 100644 --- a/yodl/manual/yo/macros/doctypes.yo +++ b/yodl/manual/yo/macros/doctypes.yo @@ -2,7 +2,7 @@ book) and the em(manual) page. Note that document types have nothing in common with output formats; a book can be converted to each of the output formats, and a manual page can be converted to a tt(.dvi) file. Nevertheless, some -formats are particularly usefule for some document types. A book converted to +formats are particularly useful for some document types. A book converted to the tt(man) output format to be processed later with tt(groff) won't look too good. Its looks would greatly improve when the document would be converted to ASCII using the tt(ms) output format. diff --git a/yodl/manual/yo/userguide/chartables/pushingtables.yo b/yodl/manual/yo/userguide/chartables/pushingtables.yo index d167325..d6a1cf1 100644 --- a/yodl/manual/yo/userguide/chartables/pushingtables.yo +++ b/yodl/manual/yo/userguide/chartables/pushingtables.yo @@ -7,7 +7,7 @@ itemization( it() tt(PUSHCHARTABLE(name)) em(pushes) the currently active translation table onto a stack, and activates the table identified by tt(name). The - argument may be emtpy; in that case, the zero-translation table is + argument may be empty; in that case, the zero-translation table is activated (analogously to tt(USECHARTABLE())). it() tt(POPCHARTABLE()) activates the translation table that was last diff --git a/yodl/manual/yo/userguide/counters/creating.yo b/yodl/manual/yo/userguide/counters/creating.yo index 26a997c..a205967 100644 --- a/yodl/manual/yo/userguide/counters/creating.yo +++ b/yodl/manual/yo/userguide/counters/creating.yo @@ -5,7 +5,7 @@ lists: the name of the counter and an optional value. The counter's value, named tt(number) below, may be set as follows: itemization( it() If left unspecified, the counter is set to 0; - it() tt(number) may be a postive or negative integral value; + it() tt(number) may be a positive or negative integral value; it() tt(number) may be the name of an existing counter, in which case that counter's value is used. ) diff --git a/yodl/manual/yo/userguide/counters/using.yo b/yodl/manual/yo/userguide/counters/using.yo index 9fad202..096277b 100644 --- a/yodl/manual/yo/userguide/counters/using.yo +++ b/yodl/manual/yo/userguide/counters/using.yo @@ -7,7 +7,7 @@ Yodl has several functions to modify and/or to set the values of counters. The counter's value, named tt(number) below, may be set as follows: itemization( it() If left unspecified, the counter is set to 0; - it() tt(number) may be a postive or negative integral value; + it() tt(number) may be a positive or negative integral value; it() tt(number) may be the name of an existing counter, in which case that counter's value is used. ) diff --git a/yodl/src/HIERARCHY b/yodl/src/HIERARCHY index ca57e9f..04008df 100644 --- a/yodl/src/HIERARCHY +++ b/yodl/src/HIERARCHY @@ -553,7 +553,7 @@ The PUSHWSLEVEL() suppresses the consumption of ws at the end of lines by the lexer, so the \n argument of CHAR() is recognized (and stored) as part of the macro's definition. Then, the former ws level is restored again. The \ at eoln are used to force the lexer to consume the ws which are not part of the -macro's defintion, but were inserted to enhance the macro's legibility. +macro's definition, but were inserted to enhance the macro's legibility. The CHAR() is used to prevent character table redefinitions of \n. There's no cure against \n SUBST() definitions, as the lexer never sees the SUBST() diff --git a/yodl/src/media/media.h b/yodl/src/media/media.h index bea0edd..81bcb38 100644 --- a/yodl/src/media/media.h +++ b/yodl/src/media/media.h @@ -17,7 +17,7 @@ typedef struct Media char *d_filename; /* name of the file being processed */ Queue d_queue; /* queue of chars to process */ bool d_isfile; /* true if file media */ - bool d_fgetc; /* true if retreived char from file */ + bool d_fgetc; /* true if retrieved char from file */ } Media;