Re: [dev-context] Typos in the LuaMetaTeX Manual
On 2/18/2020 3:04 AM, Sebastian Miele wrote: Some of these are up to two weeks old and may already have been fixed otherwise. thanks, applied - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ dev-context mailing list dev-context@ntg.nl https://mailman.ntg.nl/mailman/listinfo/dev-context
[dev-context] Typos in the LuaMetaTeX Manual
Some of these are up to two weeks old and may already have been fixed otherwise. "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 "whether". "Commands like (plain TEXs) \big need use this feature": "use" instead of "to use". "These commands are provides as convenience": "provides" instead of "provided". 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". "": Probably should be " 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( s, 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 deleted. "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) table. "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 context. "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
[dev-context] Typos in the LuaMetaTex Manual
"separation between font- and backend": "font" instead of "front". "(an UNICODE or index)": "an" instead of "a". (U is a vowel, but its pronounciation starts with a consonant sound. The pronounciation decides whether a(n).) "A node can have a subtype to that it": "to" instead of "so". "with an node": "an" instead of "a". "(here we do that with [a]": Missing closing parenthesis. "but if you need a dozen you might wonder what you’re doing. .": Two consecutive full stops. "and expands it content": "it" instead of "its". "But this kind of expansion it still": Superflous "it". "This primitives is like \ignorespaces": "primitives" instead of "primitive". "These commands are use as": "use" instead of "used". "There is an nice side effect": "an" instead of "a". "in several places where the engine to deal with the dimensions of nodes": Missing verb. "as mentioned ,their": Space and comma transposed. "reference to an image s specification": Space instead of "'". "An implementation probably should accepts": "accepts" instead of "accept". "when no proper nested grouping is used": "proper" instead of "properly". "This is conform the LuaTeX philosophy.": "is conform" instead of e.g. "is conform to" or "conforms to". "can be present in en entry": "en" instead of "an". In section 6.2 (Defining Fonts) the word 'hash' is used strangely. It seems like it is used to mean hash tables: "The parameters is a hash with mixed key types", "The characters table is a list of character hashes indexed by an integer number", "Each character hash itself is a hash", "The kerns table is a hash indexed by character index", "The ligatures table is a hash indexed by character index", "with the values being yet another small hash, with two fields". "They were mostly use for": "use" instead of "used". "At the font level there can be a fonts an (indexed) Lua table." ___ dev-context mailing list dev-context@ntg.nl https://mailman.ntg.nl/mailman/listinfo/dev-context
[dev-context] Typos in the LuaMetaTeX Manual
"The same is true fir"
"More fine-grained primitives control is possible and you can look up
the details in section 10.3.15. For simplicity’s sake, this manual
assumes that you have executed the \directlua command as given above.":
I think the second sentence was true in the LuaTeX manual, but is not
true in the LuaMetaTeX manual.
"Calling some form of tex.enableprimitives is highly important though,
because if you do not, you will end up with a TEX82-lookalike that can
run LUA code but not do much else.": Since LuaMetaTeX enables all
primitives by default, this is not true anymore.
"In the following syntax tables, such as the type of such a userdata
object is represented as ⟨node⟩.": Remove "such as".
'The return values of node.values("glue" are:': Missing closing
parenthesis. Ditto in the following 'The return values of ... are'
lines.
"when we issue this command, we get a table.": Lower case "w" at the
beginning of the sentence.
"where the number don’t relate to importance": "number" instead of
"numbers".
"This function that will append a node list to TEX’s ‘current list’.":
Remove "that".
"You mignt need"
"This helper makes sure that the node lists is double linked": "lists"
instead of "list"
"9.3.3.12 find_node": This section somehow has "node.traverse_list" in
it instead of "node.find_node".
"is a single tokens": "tokens" instead of "token".
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context
[dev-context] Typos in the LuaMetaTeX Manual
The following typos in the LuaMetaTeX Manual are from an about one week old ConTeXt LMTX (http://www.pragma-ade.nl/install.htm). In the future I will be more timely, as stated in the previous mail. A problem of not having an official repository for LMTX is: If I see a typo or problem in a section that I already read in the past, then, without further lookup, I do not know whether it already is reported or not. If I had a clone of an official repository and the manual were build from that, including the continually rebased and not-yet published fixes, that problem would not exist. I will try to deal gracefully with that problem. Depending on the problem, time, and mood, I will check for duplicates, completely ignore the typo/problem, or report the same issue more than once. "have are" in "All options are accepted but only some have are understood by" Missing closing parenthesis in "LUAs tostring function (and string.format may return values in scientific notation" "This mainly means that lpeg.S cannot be used with UTF 8 characters encoded in more than two bytes": I do not know any details of LPeg. But from a glance I suspect that "more than two bytes" should be something like "more than one byte" in that sentence. "There are all kind of subtle differences in the implementation": "kind" instead of "kinds". "Of course, of you use low level features": "of" instead of "if". "more of less long term stable": "of" instead of "or". "In chapter 5 we discussed some new primitives, here we will cover most of the adapted ones.": This sentence appears in chapter 3. So either "5" is wrong, or "discussed" should be "discuss". "The documentation, which is actually comes". "See chapter ?? for many small changes related to paragraph building". ___ dev-context mailing list dev-context@ntg.nl https://mailman.ntg.nl/mailman/listinfo/dev-context
