November 2021 - ntg-context - NTG Mailing Lists

new upload
by Hans Hagen 16 Nov '21

16 Nov '21

Hi, I uploaded a new lmtx versions. It mostly concerns new math lfg file functionality (and control) that Mikael Sundqvist and I are currently working on so there might be subtle differences in math, which is, unless there are bugs, intentional and for the best. At some point there will be additional test files in the distribution and a chapter on fonts in the math manual (the deadline is next years ctx meeting). If you have wishes wrt fonts you can tell us and we'll take them into account (if possible) but we need proper (real) minimal examples, and not for only one font as we're looking at: cambria (the reference font, very little tweaking needed) modern (which has some properties different from other gyre fonts) modernlatin (the boldened aka bachotex version) dejavu (a gyre font but different from other gyre fonts) pagella (a gyre font, all have subtle differences) schola (a gyre font, all have subtle differences) termes (a gyre font, all have subtle differences) bonum (a gyre font, all have subtle differences) lucida (commercial but rather cheap from tug) xits (is that one still used?) libertinus (a mixed bag) stix-two (a mixed bag) asana (we might drop it because of quality reasons) ebgaramond (this one is quite cambria conforming) minion (tricky because commercial and not generally available) Maybe later the newlatin modern will get a lfg too but it's beta and we 'modernlatin' anyway which uses our normal lm lgf file as it's A runtime derived font and therefore fully compatible. The bold (heavy) math fonts also are dealt with automagically. For practical reasons we might freeze fonts in the distribution and only update when explicitly checked for changes (and/or I might cook up version support in the lfg file assuming version checking is doable as often version strings are somewhat messy). We're not that bound to conventions (in the perspective of tex usage) and can "fix" them once and for all (read: we can divert from how these fonts are currently tuned for usage and expectations in e.g. latex and plain tex) so feel free to suggest esthetical pleasing options. If needed we can add variants (for which we can extend the lfg format). We also have plenty of yet unused (detailed) control in the engine. We can for instance have specific parameter sets / finetuning defined in the lfg files too but I don't know how useful and in demand that is (Mikael is looking into that). (I'm sure Aditya has some wishes. We'll deal with Euler later as that's a virtual mix and virtual opentype might be redone later because we can simply matters a bit due to the fact that we have some more and better trickery wrt virtual fonts now.) More in due time (as it's a tedious and somewhat boring job that demands lots of testing and investigation), 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 -----------------------------------------------------------------

2 1

space handling in \type
by Henning Hraban Ramm 16 Nov '21

16 Nov '21

Hi, \starttext \quotation{\type{\CONTEXT\ }} \stoptext gives “\CONTEXT \” i.e. the space moved. Why? Bug? Hraban

2 1

Re: [NTG-context] directsetup vs setups
by Wolfgang Schuster 15 Nov '21

15 Nov '21

Rik Kabel schrieb am 15.11.2021 um 22:51: > > Wolfgang, > > Can you expand on the following statements from your reply? > > You can run Hans example with MkIV and the differences should be > even bigger because the check for [] is slower here while in LMTX > it's a engine feature. The main difference in LMTX is a extra > expansion for \setup compared to \directsetup. > > there is no difference between \setup and \directsetup > > Are you saying: > > 1. When [] are used with \setup, expansion of the contents is done > differently than when {} are used. It doesn't matter which form you use for \setup. What I'm trying to say is that \setup is slower (or better was slower in MkIV) than \directsetup because \setup has to check first if the name is passed within brackets or as normal argument in braces. The code in MkIV would look similar to this: \def\setup {\doifnextcharelse[ \setup_brackets \setup_braces} \def\setup_brackets[#1]% {\directsetup{#1}} \def\setup_braces#1% {\directsetup{#1}} > 2. There is no significant processing time difference between \setup > and \directsetup. > When I run the following example on my machine \starttext \startsetups [dummy] \stopsetups \testfeatureonce{100000}{\setup {test}} \elapsedtime \par \testfeatureonce{100000}{\directsetup{test}} \elapsedtime \par \stoptext I get these times. # MkIV \setup : 0.136s \directsetup : 0.079s # LMTX \setup : 0.083 seconds \directsetup : 0.071 seconds Add additional stuff in the setup environment and the difference between \setup and \directsetup doesn't matter anymore. > 3. There is additional expansion performed for \setup compared to > \directsetup. > Although this isn't completely true (but very close) the definition for \setup in LMTX is like this: \def\setup#1{\directsetup{#1}} > 4. Under LMTX, because {} and [] handling overhead is so similar, the > most visible processing time difference to users is from the > difference in expansion between \setup and \directsetup. > > I think you are saying that 2, 3, and 4 are true, but that 1 is not true. > > If that is the case, can you provide an example that demonstrates the > difference in expansion between \setup and \directsetup? > > Also, as far as expansion, is \fastsetup like \setup or like \directsetup? > \setup and \directsetup are similar. \fastsetup is like the name implies a faster version which ignores grid mode and doesn't care whether the requested environment even exists. > My simple testing shows no difference between setup, directsetup, and > fastsetup for namespace set and reset. Is it your understanding that > they all behave the same? > No, \fastsetup behaves different because it leaves \relax\empty in the input when you pass the name of a not existing environment. It shouldn't matter in normal usage but below are two examples. Example 1: \starttext \tex{directsetup} \scratchcounter 12\directsetup{unknown_a}34 \the\scratchcounter \tex{fastsetup} \scratchcounter 12\fastsetup{unknown_b}34 \the\scratchcounter \stoptext Example 2: \starttext \normalexpanded{\noexpand\firstoftwoarguments\directsetup{unknown_a}xy} \normalexpanded{\noexpand\firstoftwoarguments\fastsetup{unknown_b}xy} \stoptext Wolfgang

1 0

directsetup vs setups
by Rik Kabel 15 Nov '21

15 Nov '21

Hello list, Can anyone provide a description of, or a point to a description of, the differences between setups= and directsetup= for including setups? I searched the list archive and the documents and found nothing. (That may indicate my level of search foo, but nonetheless I am in need of help with this.) -- Rik

5 5

Can't replicate a simple example in the wikipage
by A A 15 Nov '21

15 Nov '21

Dear All, I'm trying to run one of the examples in the ConTeXt wiki page https://wiki.contextgarden.net/Titles Here's the code: *\setuppapersize[A5]\section[sec:old]{Old Section}This is an old-style \ConTeXt\ section.\startsection [ title={New Section} reference=sec:new, ]This is a new-style section.\stopsection* However, my compiled pdf looks nothing like the example on the wiki. What am I doing wrong? Is there anything wrong with my ConTeXt settings? Regards, Amine

2 1

\startbodymatter forcing new page in document
by A A 15 Nov '21

15 Nov '21

Dear All, The following code generates a title and some fake text: *\setuppagenumbering[location=right]\usemodule[visual]\usebtxdataset[bibliography.bib]\starttext\title{test}\fakewords{1000}{1200}\stoptext* The following code does the same, but wraps the fakewords in a *bodymatter * environment: *\setuppagenumbering[location=right]\usemodule[visual]\usebtxdataset[bibliography.bib]\starttext\title{test}* *\startbodymatter\fakewords{1000}{1200}\stopbodymatter* *\stoptext* In the first case, the title remains on the same page as the fake text. In the second case, a new page is forced after the title. Why does this occur? Regards, Amine

3 2

Paragraph break over pages with hanging float
by Adam Reviczky 15 Nov '21

15 Nov '21

Hi, Is there a way to allow a paragraph to break over two pages (between the paragraph start and the placement of the float) with a hanging float further down the paragraph? MWE: \starttext \input lorem \blank[20*line] % commenting out the hanging float allows paragraph break \startplacefigure[location={right,15*hang}] \framed[width=3cm,height=2cm]{graphic} \stopplacefigure \dorecurse{10}{\input lorem} \stoptext When I remove the hanging float, the paragraph is broken down at the first pagebreak. With the float, the paragraph starts always on the next page, regardless of the space left on the previous page. Adam

2 2

Emojis showing up in black instead of colours
by Vincent Hennebert 15 Nov '21

15 Nov '21

Hi there, freshly upgraded LMTX installation. TwemojiMozilla.ttf downloaded from GitHub [1]. The following: \usemodule[fonts-emoji] \definefontfeature [overlay] [default] [ccmp=yes, colr=yes, dist=yes] \starttext {\definedfont[name:twemojimozilla*overlay] \ShowEmoji} \stoptext gives me pages of emojis, all black. According to what is described on Stackexchange, I should be getting colours. Am I doing something wrong? Thanks, Vincent [1] https://github.com/mozilla/twemoji- colr/releases/download/v0.6.0/TwemojiMozilla.ttf [2] https://tex.stackexchange.com/questions/466442/context-using-emoji- fonts-without-color

3 3

Re: [NTG-context] mwe (font proble) SOLVED
by skyhorse＠gmx.us 15 Nov '21

15 Nov '21

Solved. Well almost. I do know that it's an access problem of some sort. I used 'font-manager' to look at fonts and it showed 'DejaVu Math Tex Gyre' as "disabled" For su is shows the font as usable. When context is run su, it compiles successfully. So the fonts are there. The example does work, but, not for me as user. I for some reason have the some fonts disabled. I'll figure out how to enable them. Thank you all for your time. I'll post back when I know what to do in case any future user has this problem. Thank you Hans Hagen via ntg-context <ntg-context(a)ntg.nl> wrote: > On 11/14/2021 12:26 AM, skyhorse--- via ntg-context wrote: > > Here is the minium not-working example which I took from the > > Wikigarden a few minutes ago. > > > > \def\T#1{% > > \startitemize[#1,joinedup] > > \item This is a bullet of type #1. > > \stopitemize > > } > > \starttext > > \dorecurse{9}{\T\recurselevel} > > \stoptext > > > > Compiling this into a pdf file with context produces an error. > > I've pasted the complete context typesetting run to show the error, in hopes that it will shed some light on what's wrong with my setup. I have a feeling that the stand along install is missing some vital part of the installation regarding fonts, and that it's not noticed by the majority of you since those items are still on your system from legacy versions. > nornally it means that you have no math font loaded (i.e. you do > something before \starttext > > 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 > ----------------------------------------------------------------- > ___________________________________________________________________________________ > If your question is of interest to others as well, please add an entry to the Wiki! > > maillist : ntg-context(a)ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context > webpage : http://www.pragma-ade.nl / http://context.aanhet.net > archive : https://bitbucket.org/phg/context-mirror/commits/ > wiki : http://contextgarden.net > ___________________________________________________________________________________

3 2

Re: [NTG-context] minimum working example plus (output)
by skyhorse＠gmx.us 14 Nov '21

14 Nov '21

Hans Hagen via ntg-context <ntg-context(a)ntg.nl> wrote: > On 11/14/2021 12:26 AM, skyhorse--- via ntg-context wrote: > > Here is the minium example which I took from the > > Wikigarden a few minutes ago. > > > > \def\T#1{% > > \startitemize[#1,joinedup] > > \item This is a bullet of type #1. > > \stopitemize > > } > > \starttext > > \dorecurse{9}{\T\recurselevel} > > \stoptext > > > > Compiling this into a pdf file with context produces an error. > > I've pasted the complete context typesetting run to show the error, in hopes that it will shed some light on what's wrong with my setup. I have a feeling that the stand along install is missing some vital part of the installation regarding fonts, and that it's not noticed by the majority of you since those items are still on your system from legacy versions. > > nornally it means that you have no math font loaded (i.e. you do > something before \starttext > > Hans Nothing is done before the sample shown above. That is all that is in the .lmtx source file. From looking at the errors, I agree, it looks like there are no math fonts or, they are not visiable to context. I need advice on how I can remedy that. What do I need and what do I need to do to install them if I don't have them already on disk. I assume that they are not distributed with the <install.sh> shelll script. Thanks

2 1