- ntg-context - Mailing Lists

Wiki New Extension: ConTeXtXML
by Taco Hoekwater 27 Aug '20

27 Aug '20

Hi, As announced last week, I have been working on a wiki extension to control the editing of /Command pages. That extension is now installed on the main wiki. In short, we will switch to XML as the page model for newly created /Command pages. This makes editing a bit harder, but it allows much better quality control and (fairly) easy export and import. The goal is to eventually be able to easily export all of the reference documentation in the wiki to a separate system (for instance, Paul Mazaitis plans to create a full-blown reference manual). In the current situation, this is nearly impossible because there is so much variation in the content and quality of the wiki /Command pages (not to mention that many are missing). We also want it to be possible to merge improvements to the interface xml definitions by Wolfgang without loosing any existing documentation work. The documentation pages are here: https://wiki.contextgarden.net/Command https://wiki.contextgarden.net/Help:Command https://wiki.contextgarden.net/Extension:ConTeXtXML After reading those, have a look at the three ‘work pages’: https://wiki.contextgarden.net/Document_level_commands_work_page https://wiki.contextgarden.net/Style_level_commands_work_page https://wiki.contextgarden.net/System_level_commands_work_page All the bright red links are currently undocumented commands. Clicking on one should bring you to the edit screen automatically, with a blob of XML preloaded, ready for you to start writing. All the dark red links are existing /Command pages. All of those are traditional wiki text pages. Following those links will bring you to a normal /Command page just like on the main wiki. If you want to see how one of those pages would look like in the new system, you’ll have to rename the existing page first (as explained in https://wiki.contextgarden.net/Command#Pre-existing_pages ) If you do some work, please update those work pages! Comments, suggestions and bug reports are more than welcome. Please direct those to me personally or (better) to the wiki mailing list: https://lists.contextgarden.net/mailman/listinfo/wiki Have fun! Taco

1 1

Index formatting difference LMTX and MkIV
by Rik Kabel 27 Aug '20

27 Aug '20

Hello list, I have an index which uses multilevel indexing (a+b+c) to insert entries which contain snips of text. LMTX behaves differently from MkIV when trimming that text, resulting in line wrapping which does not happen with MKiV. I am not sure when this began -- I just picked up work again on this project this week after a hiatus of a couple of months. This does not occur in every instance, but it happens often enough in this 20 page two-column index to add another full page, and it looks ugly in comparison (although perhaps no index looks good). The source is the same for both LMTX and MkIV. There is no explicitly conditional coding. With MkIV, I get: With LMTX, I get: I am struggling to prepare a MWE, but will try to do so if there is no obvious difference to those who ken the code. The problem may not be unique to register creation, but I have not noticed other appearances of the issue in the text. -- Rik

1 0

CFF2 based variable fonts with SubRS
by Marcel Fabian Krüger 26 Aug '20

26 Aug '20

Hi, I was playing with the variable font support of ConTeXt's font loader and noticed some issues. 1. While parsing the LocalSubRS and GlobalSubRS Indices, ConTeXt tries to use 16bit count fields as in CFF(1) instead of 32bit fields as in CFF2, reducing the number of found subroutines by a factor of 65536. Effectivly this suppressed all subroutines in the fonts I tested. 2. For fonts where the Top DICT does not contain an FDSelect entry, ConTeXt tries to read the Private dictionary offset from the Top dictionary as in name-keyed CFF1 fonts. This is not the expected behavior for CFF2, where the Top dictionary never contains the Privte offset. Instead, a missing FDSelect means that exactly one entry exists in FDArray which should be used for all CIDs. This caused problems when ConTeXt tried to find the Private directory in order to find local subroutines. A test font demonstrating both issues is "SourceCode Variable" https://github.com/adobe-fonts/source-code-pro/releases: The document \definefontfeature [light] [default] [axis={weight=200}] \definefont [sourcelight] [file:SourceCodeVariable-Roman.otf*light] \starttext \sourcelight Hallo \stoptext generates [...] otf reader > cff > unknown local call 14, case 2 : [] n=0 otf reader > cff > unknown local call 11, case 2 : [] n=0 otf reader > cff > unknown local call 138, case 2 : [] n=0 otf reader > cff > unknown local call 314, case 2 : [300 -12] n=2 otf reader > cff > unknown local call 607, case 2 : [-99 -66 99 174] n=4 otf reader > fatal error in file 'SourceCodeVariable-Roman.otf': ...e0dde776fb1556f32e/formats/luametatex/font-cff-macro.lua:1517: attempt to perform arithmetic on a nil value (local 'v') stack traceback: ...e0dde776fb1556f32e/formats/luametatex/font-otr-macro.lua:2339: in metamethod 'add' ...e0dde776fb1556f32e/formats/luametatex/font-cff-macro.lua:1517: in local 'a' ...e0dde776fb1556f32e/formats/luametatex/font-cff-macro.lua:1980: in upvalue 'process' [...] A possible fix for both issues would be diff --git a/tex/context/base/mkiv/font-cff.lua b/tex/context/base/mkiv/font-cff.lua index c2cf0e699..d00637b8e 100644 --- a/tex/context/base/mkiv/font-cff.lua +++ b/tex/context/base/mkiv/font-cff.lua @@ -2265,8 +2265,8 @@ do end -local function readglobals(f,data) - local routines = readlengths(f) +local function readglobals(f,data,version) + local routines = readlengths(f,version == "cff2") for i=1,#routines do routines[i] = readbytetable(f,routines[i]) end @@ -2324,14 +2324,14 @@ local function readprivates(f,data) end end -local function readlocals(f,data,dictionary) +local function readlocals(f,data,dictionary,version) local header = data.header local private = dictionary.private if private then local subroutineoffset = private.data.subroutines if subroutineoffset ~= 0 then setposition(f,header.offset+private.offset+subroutineoffset) - local subroutines = readlengths(f) + local subroutines = readlengths(f,version=="cff2") for i=1,#subroutines do subroutines[i] = readbytetable(f,subroutines[i]) end @@ -2394,7 +2394,7 @@ readers.parsecharstrings = parsecharstrings -- used in font-onr.lua (type 1) local function readnoselect(f,fontdata,data,glyphs,doshapes,version,streams) local dictionaries = data.dictionaries local dictionary = dictionaries[1] - readglobals(f,data) + readglobals(f,data,version) readcharstrings(f,data,version) if version == "cff2" then dictionary.charset = nil @@ -2402,9 +2402,19 @@ local function readnoselect(f,fontdata,data,glyphs,doshapes,version,streams) readencodings(f,data) readcharsets(f,data,dictionary) end + local cid = dictionary.cid + local fdarray = cid and cid.fdarray + if fdarray and not dictionary.private then + setposition(f,data.header.offset+fdarray) + local dictionaries = readlengths(f,version=="cff2") + assert(#dictionaries == 1) + dictionaries[1] = readstring(f,dictionaries[1]) + parsedictionaries(data,dictionaries) + dictionary.private = dictionaries[1].private + end readprivates(f,data) parseprivates(data,data.dictionaries) - readlocals(f,data,dictionary) + readlocals(f,data,dictionary,version) startparsing(fontdata,data,streams) parsecharstrings(fontdata,data,glyphs,doshapes,version,streams) stopparsing(fontdata,data) @@ -2416,7 +2426,7 @@ local function readfdselect(f,fontdata,data,glyphs,doshapes,version,streams) local dictionary = dictionaries[1] local cid = dictionary.cid local cidselect = cid and cid.fdselect - readglobals(f,data) + readglobals(f,data,version) readcharstrings(f,data,version) if version ~= "cff2" then readencodings(f,data) @@ -2462,7 +2472,7 @@ local function readfdselect(f,fontdata,data,glyphs,doshapes,version,streams) local cidarray = cid.fdarray if cidarray then setposition(f,header.offset+cidarray) - local dictionaries = readlengths(f) + local dictionaries = readlengths(f, version == "cff2") for i=1,#dictionaries do dictionaries[i] = readstring(f,dictionaries[i]) end @@ -2470,7 +2480,7 @@ local function readfdselect(f,fontdata,data,glyphs,doshapes,version,streams) cid.dictionaries = dictionaries readcidprivates(f,data) for i=1,#dictionaries do - readlocals(f,data,dictionaries[i]) + readlocals(f,data,dictionaries[i],version) end startparsing(fontdata,data,streams) for i=1,#charstrings do ---- Best regards, Marcel

2 1

odd behaviour with \definefontfamily
by jbf 26 Aug '20

26 Aug '20

Can someone tell me why, when I define my typefaces as follows below, I get: mkiv lua stats > loaded fonts: 2 files: baskervaldadfstd.otf, texgyrepagella-math.otf when in fact my font definitions are: \definefontfamily [mainface] [rm] [baskervaldadfstd] [tf=file:BaskervaldADFStd.otf] \definefontfamily [mainface] [ss] [librisadfstd] [tf=file:LibrisADFStd-Regular.otf] \definefontfamily [mainface] [mm] [TeX Gyre Pagella Math] \setupbodyfont[mainface] --------------------- ConTeXt loads the [rm] and the [mm] but not the [ss]. Be assured that the ss typeface is available. So if, for example, I comment out the first line ([rm]) and change the Libris to rm instead, I am told: mkiv lua stats > loaded fonts: 2 files: librisadfstd-regular.otf, texgyrepagella-math.otf In other words, only two, not three definitions are working at any one time. Or is it not accepting [ss] for some reason regardless? I have tried any number of existing sans serif fonts and none of them will load. I know the family names are correct, so that is not the problem. What could I be doing wrong? Julian

3 6

set_lua freezes control sequences
by Marcel Fabian Krüger 25 Aug '20

25 Aug '20

Hi, I noticed that recent LuaMetaTeX versions treats control sequences defined using token.set_lua with `value` or `condition` as frozen and does not allow redefining them. Given that these are not macros, we also can't "unfreeze" them using \unletfrozen. 1. Would it be possible to add a variant of Lua value and condition control sequences that are not frozen? 2. Also is there some way to disable the \frozen restrictions altogether? Maybe \suppressfrozenerror? 3. I also noticed that `token.set_lua` is not affected by control sequences being frozen. Therefore it allows redefining frozen control sequences which seems inconsistent. Best regards, Marcel

2 2

new version
by Hans Hagen 25 Aug '20

25 Aug '20

Hi, The current version of lmtx has some updated tracing of memory usage. This is irrelevant for most users but some of you generat elarge an complex files so ... (I'm talking about mf here). There is a command line option --usage that will make a run report some more statistics. The info shown might look somewhat cryptic but we basically have (per category) - max: the maximum allowed memory (for many categories we can make that larger, but I need proof that it's needed) - min: this is how we start out - stp: when more memory is needed, this is the step that we use to increase - set: this is the value that context configures by default, often larger than min, and less than max - mem: the memory usage (often in units) - all: the real usage (multiplied by the unit) - ini, ptr and top: are the startup values (when something is also stored in the format), the current usage and the max usage (all within the mentioned min-max range). The rest speaks for itself. Font usage reflects only the tex end, of course there is plenty usage at the lua end. The language info .... I might extend that with pattern and exception usage. Actually, tex memory usage is not that large in luametatex. When mem gets increased, there is a message. We can use that to eventually determine the best values. Actually we might even lower some initial values (not that it matters much, lua uses more). Of course there is also --timing but that one has been there from the start, although I did update it to reflect the more detailed tracing. The graphics are the same as always: red lines are usage, the blue line is the runtime. In general, memory management has been improved: all categories are now more dynamic, there is more checking for overflows, there is some recovery slack in allocation, etc. I will play a bit more some of it, for instance we might end up with more detailed configuration options, in addition the the already new ones. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------

1 0

Overriding the number on a float
by Duncan Hothersall 25 Aug '20

25 Aug '20

I think there was a question on this very recently but I don;t think it got an answer and I can't find it to reply to, so apologies for the extra noise. I have a large text with floats numbered sequentially by chapter and then figure/table number, but at the last minute I've had a request for two figures in a particular chapter to become 27.1a and 27.1b instead of 27.1 and 27.2. It's not a combination - they are separate figures on different pages. I've experimented with the options I can see, but it's not obvious if there is a facility to override the numbering of two figures in a stream of normally numbered figures like this. I was thinking of the equivalent of the old \sym{symbol} command that used to work as a way to override a single item in an otherwise sequential list. I guess there's a brute force method of setting up a new type of figure with the label "Figure 27.1" and having them numbered as lowercase alpha, but if there's an easier way that would be great. Thanks. Duncan

6 8

slight correction to 'short filler rule' question
by jbf 25 Aug '20

25 Aug '20

In the earlier post I mentioned the rules not balancing. That was my error. In experimenting with things I had made a minor error with one of the single \quad statements. Apologies. So, at this stage, replacing left=\zerowidthnobreakspace with left=\quads[3] on the ChapterLeftRule, and doing similarly with right= for the ChapterRightRule, I do achieve something of the kind I am after. I can even go as far as \quads[5] I can see. So maybe I have achieved the desired effect. But it may not be the best way to do it, since I can't control the length of those rules by exact dimensions using this approach. J.

1 0

short filler rule either side of a text
by jbf 25 Aug '20

25 Aug '20

I know it is possible to get a rule to act as a filler either side of, say, a chapter head text by using \definefiller with alternative=rule and, as explained in an earlier post <https://tex.stackexchange.com/questions/497352/context-heading-text-surroun…>, define a left and right version. So, for example, for the left version: \definefiller [ChapterLeftRule] [ChapterRule] [left=\zerowidthnobreakspace, right=\quad] This gives me a rule that extends to the margins. What if I want the rule to be, say, 2 cm either side of my centered header text? I tried experimenting by replacing left=\zerowidthnobreakspace with left=\quads[3] and that did shorten the rule somewhat, but when I did the same for the other side, it did not balance correctly. So maybe I need to deal with the 'left=' differently to achieve the desired result... or try an entirely different method! Of course, I don't want the rule at the baseline, but raised, as the original stackexchange <https://tex.stackexchange.com/questions/497352/context-heading-text-surroun…> example gives. Any clues? Julian

1 0

keeping content chunks on same page
by Mike Cooper 25 Aug '20

25 Aug '20

Just about to have these homework files finished! My final problem (I hope) is keeping question/answer blocks together. The questions are currently defined via \defineenumeration with a \testpage (see below). I fiddled with the \testpage and found that \testpage[6] gave me the best results but there are still some question/answer blocks that get split across pages. The content chunks can be as small as a single line question with T/F answer options, or as large as seven lines for the question and seven for the answer options (although I don't think both of these occur together). In my searching for solutions, I thought I'd found something helpful with \startframed but I can't figure any way to combine the framed and enumeration... Anyway, here's some code. It doesn't demonstrate the page-break problem but gives an idea of the different possible sizes of question/answer chunks. \defineenumeration[question] [text=, headstyle=normal, right=., alternative=left, distance=1em, width=fit, before={\testpage[6]\blank[2em]}, after={\blank} ] \defineitemgroup[achoices] [option={packed,a,broad}, left=(, right=), stopper=] \starttext \startquestion Before a joint of pipe is laid down, the thread protector should be installed. \startachoices \startitem True \stopitem \startitem False \stopitem \stopachoices \stopquestion \startquestion The hardest part of the drilling program for young drilling engineers to plan is the section on hole stability because they have not had much hole problem exposure and have not been told that this particular shale is a "twenty-day shale". The most likely reason for the breakdown in communications is: \startachoices \startitem Inadequate case history data and poorly completed field records and NO trend charts \stopitem \startitem Mud company representatives are only calling on drilling superintendents and managers \stopitem \startitem Drilling engineers cannot read "between the lines" on morning reports and therefore miss the point many times. \stopitem \startitem Too few hours to do adequate offset well record check \stopitem \stopachoices \stopquestion \startquestion If the toolpusher noted the following trend while RIH with drill pipe, what should he instruct the driller to do? \setuptabulate[header=none] \starttabulate[|c|c|c|] \NC Stands \NC Increments required vs. actual \NC Trend \NC \NR \NC 0-5 \NC 3.57 vs. 3.57 \NC ~0 \NC \NR \NC 6-10\NC 3.57 vs. 2.57 \NC -1 \NC \NR \NC 11-15\NC 3.57 vs. 1.57 \NC -2 \NC \NR \stoptabulate \startachoices \startitem Continue to RIH to the casing shoe and observe the well \stopitem \startitem Stop and break circulation every 12 stands \stopitem \startitem Slow down because it looks like we are losing mud to the formation \stopitem \startitem RIH quickly because it looks like the hole is trying to flow \stopitem \stopachoices \stopquestion \stoptext THANKS FOR YOUR HELP! Mike Cooper Technical Trainer Murchison Drilling Schools, Inc. 2501 Juan Tabo NE Albuquerque, NM 87112 Tel: (505) 293-6271 Fax: (505) 298-5294 Email: mike(a)murchisondrillingschools.com<mailto:mike@murchisondrillingschools.com> Website: www.murchisondrillingschools.com<http://www.murchisondrillingschools.com/> [cid:image007.jpg@01D03ADC.BD6E6850]<https://www.facebook.com/pages/Murchison-Drilling-Schools/158018484232622> [cid:image008.jpg@01D03ADC.BD6E6850] <http://www.linkedin.com/company/murchison-drilling-schools-inc-> [cid:image009.jpg@01D03ADC.BD6E6850] <https://twitter.com/trainingmds> Murchison Drilling Schools is now part of [cid:image001.png@01D63515.857FD120]

1 0