[dev-context] Typos in the LuaMetaTeX Manual

Sebastian Miele sebastian.miele at gmail.com
Tue Feb 18 03:04:03 CET 2020

Some of these are up to two weeks old and may already have been fixed

"has resulted in many more parameters than were not accessible before":
"than" instead of "that".

"in a \atop stack": "a" instead of "an".

"Method six omits the surround glue when there is (x)spacing glue
present while method seven does the opposite, the glue is only applied
when there is (x)space glue present too": The "too" at the end
superfluous. Apart from that, the sentence says the exact opposite of
what the preceding table says. At least one of them is wrong.

"Note 1: for ease of use": "for" instead of "For".

"so you you might encounter"

"a \hbox": "a" instead of "an".

The table for \mathscriptboxmode repeats 2 in the last two rows for the
value column. In the last row it should be 3.

"These primitives accepts an option width specification": "option"
instead of "optional".

"the fact if the used characters in the font have": "if" instead of

"Commands like (plain TEXs) \big need use this feature": "use" instead
of "to use".

"These commands are provides as convenience": "provides" instead of

The code example in 8.8.2 (Script commands \Unosuperscript and
\Unosubscript) uses the wrong buffer.

"and a character as nucleus. and which has the side effect that":
Superfluous ". and".

"(like kern and width, or data and value": Missing closing parenthesis.

"and and"

"A few more xperiments were done"

"two kind of callbacks": "kind" instead of "kinds".

"has to represent a hbox": "a" instead of "an".

"<number prevdepth>": Probably should be "<number> prevdepth".

"This callback replaces the code that prints LuaTeX’s when a file":
"prints LuaTeX's" instead of "LuaTeX prints". Two occurrences of this
typo (start_file, stop_file).

"The value is currently": Swap "is" and "currently".

"lua.setluaname(<string> s,<number> n])": A lone "]".

"If you pass true to get you get 5 values returned for a glue and when
you pass false you only get the width returned": This sentence only
repeats something already mentioned in the same paragraph and can be

"in which care only": "care" instead of "case".

"the space before in between will be gobbled": The example code before
that line actually uses "inbetween". "in between" probably is the
correct spelling.

"a callback that read numbers": "read" instead of "reads".

"The engine can in one of four modes": "can in" instead of "can be in".

"You can initialize with a new seed with init_rand (lua_math_randomseed
is equivalent to this one": Somewhere in this sentence a closing
parenthesis is missing.

"This function behaves like texio.write, but make sure": "make" instead
of "makes".

"This function that should be used with care": Superfluous "that".

"Normally a LUA will just collect prints": Something like "call" is
missing after "LUA".

"and as performance is quite ok. One can build additional parsers":
Probably "ok. One" instead of something like "ok(,) one".

"returns a number representing a dimension and or two numbers being the
filler and order": "and or" instead of probably just "or".

"The scan_code function takes an optional number, the keyword function":
The "scan_code" has the prefix "scan_" in this sentence, the "keyword"
does not, although it has in the preceding table.

"returns a table of tokens tokens"

"(for instance the catcode in case of a character or the classifier that
determines the internal treatment": Missing closing parenthesis.

In section 11.6.6 (Nota bene) the examples after "If we now say" do not
change anything and seem to be superfluous, as far as I can see.

"The argument hash can have a number of different fields": "hash" used
to mean (hash) table.

"Graphical objects come in various types that each has a different list
of accessible values": "has a different list" instead of "have different
lists". Or: "types that each" instead of "types. Each". Or: "types that
each has" instead of "types, each having".

"Each dash is two-item hash": Missing "a". Using "hash" to mean (hash)

"The first argument is to be a page dictionary": "is" followed "to be".
But more importantly: The sentence seems to make no sense in its

"13.1.7 get[from][dictionary|array|stream]": Contrary to the section
title, the section does not explain the getfrom.. stuff. That is handled
in a separate following section.

"The pdfe.new that takes three arguments:": "The pdfe.new that" instead
of e.g. just "pdfe.new".

"so that multiple doesn’t use more memory": Something is missing between
"multiple" and "doesn't". And probably "don't" (plural).

"an pdfe": "an" instead of "a". At least two occurrences of this.

"puspose": instead of "purpose".

The table explaining "readfixed2", "readfixed4", and "read2dot14"
contains e.g. "a 2 byte float" in the results column. However, as far as
I can see now, the functions probably read fixed point numbers of
specific formats and return them as ordinary Lua (floating point)
numbers. Similar considerations apply to other rows of the table. Maybe
the results column should be separated into two columns: One on what is
read from the stream, and one on how the result is represented and
returned in Lua.


"Keep in mind that there might be platforms where this function is
available": Probably a missing "not". Or "un" before "available".

"The lua library provide some general helpers": "provide" instead of

"Deep down some more has changes": Probably "changes" instead of

More information about the dev-context mailing list