- dev-context - NTG Mailing Lists

Typos in the LuaMetaTeX Manual
by Sebastian Miele 18 Feb '20

18 Feb '20

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". "<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 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 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. "string.cWharacters" "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 "provides". "Deep down some more has changes": Probably "changes" instead of "changed".

2 1

Minor Problems in the LuaMetaTeX Manual
by Sebastian Miele 16 Feb '20

16 Feb '20

"When you are processing a snippet of text starting with btex and ending with either etex or verbatimtex": According the MetaPost manual there are only "verbatimtex .. etex" blocks, but no "btex .. verbatimtex" blocks. "There is one special case: pens that are (possibly transformed) ellipses have an extra string-valued": In the current PDF, the "string-valued" gets hyphenated as "stringA" at the end of a line and "Bvalued" at the beginning of the following line.

1 0

time in downloaded attachments
by Pablo Rodriguez 13 Feb '20

13 Feb '20

Hans, would it be possible that "--remote-time" could be added to curl, so that attachments that are downloaded display when they were uploaded and not when they were downloaded? For some reason unknown to me, this seems to have no effect with http://lmtx.pragma-ade.nl/install-lmtx/installation.pdf (among many other ones). Timestamps work right when I download "curl -R -O http://lmtx.pragma-ade.nl/install-lmtx/installation.pdf" from the shell. Many thanks for your help, Pablo -- http://www.ousia.tk

1 0

Bug: Inline Math Surrounding Spacing
by Sebastian Miele 05 Feb '20

05 Feb '20

In the table on \mathsurroundmode in the LuaMetaTeX manual every example row has the same spacing, although there should be noticable differences. After trying to find the root of problem, I came to the conclusion that currently ConTeXt LMTX obeys neither \mathsurround nor \mathsurroundskip at all.

2 1

Minor Problems in the LuaMetaTeX Manual
by Sebastian Miele 05 Feb '20

05 Feb '20

"The characters table is a list of character hashes indexed by an integer number": The sentence says that the table is a list. According to 'Programming in Lua' that indeed is the case. But the term 'list' conveys that the order of the items is something that matters, which (most probably) is not the case here. As far as I see, the intent of the table is to just map character codes to character information. Using the term 'list' in that context is a bit misleading. "and tell the engine that œ counts as one character": I think it should be "two characters". "In figure ?? and 7.7 we show what happens with three samples" "(the ones resulting from an \exhyphenchar": Missing closing parentheses. "the case relate codes": "relate" instead of "related". "This word separation is worth mentioning because": Should be "separation of stages" or just "separation" instead of "word separation". Maybe "work separation" was intended. In the table at the top of page 80, the "sub 1" probably should go directly below "POST", and the "sub 2" directly below "REPLACE". Now they occur aligned to the numbering of the terminal nodes of the structure presented in the table. "it does not expect there to be discretionaries inside of discretionaries": As far as I understood the previous text, what is really meant here is "it does expect there not to be discretionaries inside of discretionaries". The Lua(Meta)TeX manuals talk about ghost nodes. I did not find any information on what that is. Up to now, for all other stuff encountered in the LuaMetaTeX manual that I did not know and wanted to have a rough idea of what it is about, I found the relevant information either in the LuaMetaTeX manual itself, in TeX by Topic, or in the ε-TeX manual. I.e. I found it using the LuaMetaTeX manual itself, or the manuals that were referenced at the beginning of chapter 1 of the LuaMetaTeX manual as important additional material. The Lua(Meta)TeX manual mentiones that \leftghost and \rightghost come from Aleph. I searched the web quite a bit about Omega and Aleph on that issue, and tried other things, but found nothing of relevance. There is a manual for Omega, but, after conversion from ps to pdf, and opening the pdf with Evince, the search function did not find the phrase 'ghost' in it, either.

2 3

Example on \mathstyle + \mathchoice + grouping in the LuaMetaTeX Manual
by Sebastian Miele 04 Feb '20

04 Feb '20

It took me longer than I want to admit here to mentally parse the example at the end of section 8.3.1 on \mathstyle, \mathchoice, and grouping. In particular it took a while until I noticed that the b case has no \bgroup ... \egroup. This may very well be because of temporary stupidity on my side. But nonetheless I recommend changing the example either so that the mathchoices between \bgroup ... \egroup receive one more level of indentation, or, even better, to change the example into something like: \def\a#1{ \mathchoice {\bf \scriptstyle (#1:d :\mathstyle)} {\bf \scriptscriptstyle (#1:t :\mathstyle)} {\bf \scriptscriptstyle (#1:s :\mathstyle)} {\bf \scriptscriptstyle (#1:ss:\mathstyle)}} [a:\mathstyle]\quad \bgroup\a x\egroup \quad [b:\mathstyle]\quad \a y \quad [c:\mathstyle]\quad \bgroup\a z\egroup \quad [d:\mathstyle] Apart from being shorter, that totally minimizes the effort required by the reader to mentally parse and compare what is equal and what is different in the example.

1 0

Typos in the LuaMetaTex Manual
by Sebastian Miele 01 Feb '20

01 Feb '20

"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."

1 0

sortedkeys and compare in LMTX l-table.lua
by Sebastian Miele 28 Jan '20

28 Jan '20

On table.sortedkeys the page https://www.contextgarden.net/Table_manipulation says: "Returns a sorted array of all the keys in table t. The comparer used for sorting will treat everything as a string iff the compared values are of mixed type." According to l-table.lua, sortedkeys first checks whether the keys in the given table are (1) all strings, (2) all numbers, or (3): neither (1) or (2). In cases (1) and (2) table.sort is used with the default comparer (Lua's '<'). In case (3) table.sort is used with a custom compare function named 'compare' and defined in l-table.lua. According to the sentence from the garden cited above, 'compare' should return (something equivalent) to tostring(a) < tostring(b). However, it does something more complex that, e.g., makes 10 < "2" < 3 < 10 ('<' meaning infix 'compare' here). I.e. there are strict circles in the strict order. https://www.contextgarden.net/Table_manipulation goes on explaining that, "In general this means that you will be fine as long as you avoid stuffing indices along with number hashes together in t, lest the order will end up confused depending on what type an element is compared with in what order (cf. example [2])." This reflects the way 'compare' actually is at the moment. But it contradicts the previous sentence "The comparer used for sorting will treat everything as a string iff the compared values are of mixed type." If everything is treated as a string when neither (1) nor (2), then everything is well-defined and there is no confusion. Why is 'compare' not just (something equivalent to) tostring(a) < tostring(b), violating the sentence cited above? Are there any meaningful uses of the way 'compare' is now? I suspect that the intent was to create an order that is lexicographic and numeric at the same time. As far as I see it, it just is not possible the way it was tried: Lexicographically, 11<2. Numerically, 2<11. I see three ways out: (1) Disallow mixed types of keys in tables given to sortedkeys. (2) Always use lexicographic order in the case of mixed key types. (3) Combine the orders by an order-theoretic sum. One possiblity: Every value that is neither a number nor a string is smaller than every number. Every number is smaller than every string. Otherwise elements are compared as they are now. Another possiblity: Define an order over all types, define an order for every type. Then sort by type first, and in type second. (1) may not possible without breaking a lot. (2) has sort of a discontinuity: E.g., add one numeric key to a table with only strings, and the order changes globally. (3) contains well defined, very predictable solutions without discontinuities.

2 4

Typos in the LuaMetaTeX Manual
by Sebastian Miele 28 Jan '20

28 Jan '20

"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".

1 0

No Official ConTeXt LMTX Repository
by Sebastian Miele 27 Jan '20

27 Jan '20

In the past months I worked through The TeXbook and The METAFONTbook. About a week ago I started to work through the LuaMetaTeX manual. For several reasons I want to learn ConTeXt from bottom to top. The main page of the ConTeXt Garden says "There is no offical repository there the development is going." ("there" in that sentence probably should be "where". I seem to not be allowed to edit the garden main page.) The LuaMetaTeX manual contains typos and other issues. In such cases I usually checkout the most recent development branch of the official repository and create continually rebased commits on top of it, that finally find their way into patches send over a mailing list, or pull requests on e.g. GitHub. This works really well. It would be really cool if ConTeXt LMTX had a/the official repository. For now, I will just somehow post the typos to dev-context(a)ntg.nl. I will use ConTeXt LMTX (from http://www.pragma-ade.nl/install.htm) as a reference point. I will update the installation it at least daily.

6 8