- ntg-context - NTG Mailing Lists

ligature exceptions
by Thomas A. Schmitz 28 Jul '21

28 Jul '21

Hi all, just two quick questions: a couple of weeks ago, there was a long discussion on ligature exceptions in, e.g., German. Hans provided an elegant new mechanism (\startlanguageoptions). So my two questions: 1. Is the old mechanism (\replaceword[eg][Auflage][Au{fl}age]) now obsolete? I tried using it, but unwanted ligatures still occurred. If it is indeed deprecated, I'll add a note to the wiki (this would mean that the current texlive version does not have the new mechanism and the latest lmtx doesn't use the old one, so that's somewhat problematic). 2. Both mechanisms only work for complete words, is that right? So I can't just provide a pattern such as "uf|forder," I have to provide a full list with all inflected forms: auf|fordern auf|fordert auf|fordernd Auf|forderung Auf|forderungen and for 1-3 also the forms with a capital letter. Thank you! Thomas

2 1

Different Typing Styles
by Jeroen 28 Jul '21

28 Jul '21

Is there a way to have two different styles of typing. I tried the following, but it does not seem to work. \setuptyping[abc][style=\ttx] \setuptyping[def][style=\ttxx] \starttext \starttyping[abc] example example \stoptyping \starttyping[def] example example \stoptyping \stoptext Thanks Jeroen

2 1

A not so short introduction to ConTeXt Mark IV
by Joaquín Ataz López 28 Jul '21

28 Jul '21

Hello to all: Two months ago I informed to the list that I had written an introduction in Spanish to ConTeXt Mark IV. This interested several people, and in order to increase their potential audience, a member of this list (native English speaker) has proceeded to translate my text into English. It is precisely the members of this list who need no introduction at all, but it can sometimes be useful to help someone get started with the fascinating typesetting system that is ConTeXt. As for the English translation, I have made some small changes to the Spanish version, so anyone who understands Spanish and prefers to read it in its original language can download the new version: Both versions are available at the following links - Spanish: https://webs.um.es/jal/docs/introCTX_esp.pdf - Engilish: https://webs.um.es/jal/docs/introCTX_eng.pdf Soon I will send both texts, with their source files, to the documentation section of the CTAN repository. -- Joaquín Ataz López Derecho Civil Universidad de Murcia

17 35

Different Styles of Typing
by Jeroen 28 Jul '21

28 Jul '21

Is there a way to have two different types of typing. I tried the following, but it does not seem to work. \setuptyping[abc][style=\ttx] \setuptyping[def][style=\ttxx] \starttext \starttyping[abc] text text \stoptyping \starttyping[def] text text \stoptyping \stoptext

3 2

LMTX mtxrun --script fonts --reload --force isn't finding fonts in tex/texmf-fonts
by T. Kurt Bond 28 Jul '21

28 Jul '21

Hello. I'm trying to get LMTX to use my fonts on Fedora 33 Linux. I've got LMTX installed in the directory /sw/versions/context/lmtx and I've put copies of the fonts I'd like to use in /sw/versions/context/lmtx/tex/texmf-fonts. Some of them are truetype and some of them are opentype. When I run mtxrun --script fonts --reload --force it says fonts | names | scanning path '/sw/versions/context/lmtx/tex/texmf-fonts' for otf files fonts | names | 0 otf files checked, okay and later fonts | names | scanning path '/sw/versions/context/lmtx/tex/texmf-fonts' for ttf files fonts | names | 0 ttf files checked, okay Any ideas of what I'm doing wrong? -- T. Kurt Bond, tkurtbond(a)gmail.com, https://tkurtbond.github.io

3 5

Adobe Acrobat accessibility criteria
by Connor P. Jackson 28 Jul '21

28 Jul '21

Hello ConTeXt friends, I am newly exploring ConTeXt in search of a better way to produce PDF/UA-1 accessible and PDF/A compliant documents programmatically. From my early experiments, ConTeXt docs appear to fully satisfy the veraPDF validator, but Adobe Acrobat’s Accessibility Checker has three qualms with ConTeXt-produced documents: 1. The document is configured to display the file name rather than the title in the top of the window (DisplayDocTitle == True is what I think is required). See here <https://www.w3.org/TR/WCAG20-TECHS/PDF18.html>. 2. "Tagged Annotations" fails, suggesting that the document’s links are not properly tagged. I believe the issue is missing "Link - OBJR” (object reference) tags. See here <https://amp.levelaccess.net/public/standards/view_best_practice.php?violati…>, here <https://www.w3.org/TR/WCAG20-TECHS/PDF11.html>, and here <http://verapdf.org>. 3. "Tab Order" fails, I believe because ConTeXt does not specify that the tab order should follow the Document Structure, so Acrobat reads it as unspecified. See here <https://www.w3.org/TR/WCAG20-TECHS/PDF3.html>. Is there something I could be doing to correct these issues in my ConTeXt documents? Or is this a change that would have to be made within ConTeXt itself? I know that Adobe is not the definitive arbiter of what an “accessible” PDF looks like, but for many organizations, passing the Acrobat accessibility checker is a prerequisite, so it seems worthwhile to me to make ConTeXt capable of it. Many thanks! Connor Jackson

2 3

Using ConTeXt Lua libraries
by Jairo A. del Rio 28 Jul '21

28 Jul '21

Hi everyone! I want to know the proper way to load ConTeXt Lua modules/libraries *en masse*. such as those listed in cld-mkiv, without actual typesetting in order to write some scripts. I thought about creating a .cld file with no output, but I suspect there's a better way. Thanks in advance. Regards, Jairo

2 1

Question about \groupedcommand{}{}
by Fabrice Couvreur 28 Jul '21

28 Jul '21

Hi, The name of the environment must always end with a dot both with a title and without title. How to do ? Thanks Fabrice \setupenumerations [before={\blank}, after={\blank}, alternative=serried, title=yes, titleleft={(}, titleright={)}, titlestyle=normal, titlecommand=\groupedcommand{}{\bf.}, width=broad] \defineenumeration [definition] [text=Définition, number=no, headcommand=\groupedcommand{}{}, style=italic] \starttext \startdefinition{With a title} \samplefile{lorem} \stopdefinition Without title but no dot after the name of the environment. \startdefinition \samplefile{lorem} \stopdefinition \stoptext

2 2

new lmtx upload
by Hans Hagen 27 Jul '21

27 Jul '21

Hi, I uploaded a new version that mostly concerns documentation files (checking them for lmtx and so). I (partly) updated the primitives manual (for hans vd meer) and added followingup-expressions (for pablo). The expressions stuff (was already in previous uploads) is a side effect of finalizing some luametatex code. Part of it had been there in commented form as I had not yet made up my mind about how much is needed. In the end I decided to *not* integrate it in the \numexpr an d\dimexpr primitives because of potential compatibility issues (although that is unlikely given the way we use them in the core, I don't know to what extend users use these primitives). The long ago - one of the first things in luametatex - introtroduced integer division : probably went unnoticed (of course not by ws) which is an indication that this extension has been is rather safe. Anyway, more about expressions can be found in the mentioned documents. Think of (one can of course also use the usual tex variables): \starttext \the\dimexpression 2 * 10pt + 2pt \relax \the\dimexpression 2 * 10pt > 2pt \relax \number\dimexpression 2 * 10pt + 2pt \relax \number\dimexpression 2 * 10pt > 2pt \relax \ifboolean\dimexpression 2 * 10pt > 2pt \relax yes \else nop \fi \ifboolean\dimexpression 2 * 10sp > 2pt \relax yes \else nop \fi \ifdimexpression 2 * 10pt > 2pt \relax yes \else nop \fi \ifdimexpression 2 * 10sp > 2pt \relax yes \else nop \fi % alias \ifexpression : \ifnumexpression (2 * 10) + (3 << 4) > (4 & 5) \relax yes \else no \fi \stoptext Performance wise it is comparable to \dimexpr and \numexpr (these are a bit faster in luametatex than in luatex), the final \relax is mandate (so no lookahead side effects), and these don't suffer from some of the somewhat weird properties of their ancestors. The main difference is that they support comparison and bitwise operators. I can add more but it probably doesn't make sense. With \tracingexpressions1 \tracingonline1 you get info like this: 1:4: {dimenexpression rpn: 2 655360 * 131072 +} 1:4: {dimenexpression rpn: 2 655360 * 131072 >} 1:4: {dimenexpression rpn: 2 655360 * 131072 +} 1:4: {dimenexpression rpn: 2 655360 * 131072 >} 1:4: {dimenexpression rpn: 2 655360 * 131072 >} 1:4: {dimenexpression rpn: 2 2 * 131072 >} 1:4: {dimenexpression rpn: 2 655360 * 131072 >} 1:4: {dimenexpression rpn: 2 2 * 131072 >} 1:4: {numexpression rpn: 2 10 * 3 4 << + 4 5 band >} Of course (maybe for sure) there can be bugs but then, only a few will ever use this (I bet hvdm is one of them, as he also uses the other new \if* features). Other hidden 'pearls' (bachotex speak) will be revealed in due time, 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

Re: [NTG-context] Macro that does not work in an environment
by Wolfgang Schuster 27 Jul '21

27 Jul '21

Fabrice Couvreur schrieb am 27.07.2021 um 18:24: > Hi, > The macro \card must allow the word Card to be written in the normal style. > Hans' solution works well. To use \text with a certain style use a \mathtext.. command, e.g. \define[1]\card {\m{\mathtexttf{Card}\thinspace#1}} Wolfgang

1 0