- ntg-context - NTG Mailing Lists

Display reference number as Roman number
by Rik Kabel 06 Jan '21

06 Jan '21

Hello all, What I thought should be a simple conversion escapes me. I have a reference (created originally via a label defined by \definelabel) that, when referenced as *\in[label]* or *\ref[number][label]* displays a number, and that is how I normally use it. However, I want to display it in one instance as a Roman numeral. *\**Romannumerals{\in[label]}* complains that it is not being fed a number. How can I display the label number in Roman number format in this one instance? -- Rik

2 1

Continued chapter numbers
by jbf 06 Jan '21

06 Jan '21

I need chapter numbers to continue sequentially across several parts. At the moment, when Part 2 begins, it begins with Chapter 1 once more, while it should be (in continued sequence) Chapter 4. I know that I can achieve the desired result by including ownnumber=4, so: \startchapter[title={My chapter title},ownnumber=4] will do that for me. But this means I have to do it for every chapter that follows (there are 11 more!). Perhaps there is a single way to get the result I want in the preamble with \setuphead[chapter] or similar. I have searched the wiki but it is not easy to find an answer to this. Can anyone point me to where, in the wiki, I can find a simple way to ensure sequential chapter numbers? Julian

3 3

\definefontfeature and script
by Pablo Rodriguez 06 Jan '21

06 Jan '21

Hans, this sample shows an issue with script: \definefontfeature [default] [default] [script=latn] \definefontfeature [onumsmcp] [onum=yes, smcp=yes, c2sc=yes] \setupbodyfont [pagella] \starttext \feature[+][onumsmcp]\tfb abc123ABC \stoptext If script=auto, current latest (2021.01.05 10:45) works fine. If it is set to Latin (as above), I don’t get small caps. Besides the potential issue in ConTeXt, I think that "script=auto" may be safer than "script=latn". Or am I taking too much for granted? Many thanks for your help, Pablo -- http://www.ousia.tk

2 4

lmtx upload
by Hans Hagen 05 Jan '21

05 Jan '21

Hi, A new version has been uploaded. This one has: \enableexperiments[fonts.compact] for the brave to test. As a reminder, as this has been around for a while now, if you really want to stress your test, run with (top of file): \overloadmode 4 % error \overloadmode 3 % warning in order to see if you (re)define primitives, core functionality, instances and whatever can lead to conflicts. There are still some commands to be tagged (and for some the category might change) but it's a bit of a tedious job. Btw, for metafun the warnings are enabled by default (for now), but users might have noticed that already. 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

dutch calendars 3 months
by luigi scarso 05 Jan '21

05 Jan '21

I guess this is a challenge for Willi : a module to typeset "dutch calendars" as in https://www.calendari.it/ (I am not involved at all with the site, it's the first I have found ) I like the slim version, with 3 months, the saint(s) of the day, the moon phases, the week number, the day from the beginning and to the end of the year .... -- luigi

4 5

ligature prevention
by Hans Hagen 05 Jan '21

05 Jan '21

Hi, I probably didn't mention this yet but the way to deal with ligature and kerning prevention in lmts is: whatever\par {\nokerning whatever}\par efficient ff fi\par {\noligaturing efficient ff fi}\par {\nokerning\noligaturing efficient ff fi}\par {e{\noligaturing ffi}cient}\par because this feature can be used local and because it actually has more granularity than advertised, I added this in the next version {ef{\noleftligaturing f}icient ff fi}\par {ef{\norightligaturing f}icient ff fi}\par (so, specific commands for left/right control). Or course one can wonder how useful it is, but because tex is all about control ... 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 2

Re: [NTG-context] Part label and chapter numbers
by Marco Patzer 04 Jan '21

04 Jan '21

On Tue, 5 Jan 2021 08:32:33 +1100 jbf <roma83537(a)gmail.com> wrote: > and apologies if you didn't think I provided an MWE. The idea is that people can just copy-paste the code into an editor and keep tweaking. It doesn't have to produce the correct output, but it should compile. If you add an MWE you're more likely to get a response. > Of the three issues below, only the first is not resolved, meaning > that part=Section\nobreakspace does not make any difference, or put > another way, at least it stops things from throwing an error, but the > result I get is not 'Section 1. My title' but simply '1. My title'. Here's what an MWE with the code I posted looks like: \setuphead [part] [placehead=yes, bodypartlabel=part] \setuplabeltext [part=Section\nobreakspace] \setuplabeltext [chapter=Chapter\nobreakspace] \setuphead [chapter] [conversion=Words] \setuphead [chapter] [sectionsegments=chapter] \setuphead [section] [sectionsegments=chapter:section] \starttext \startpart [title=Mypart] \startchapter [title=Some Chapter] \startsection [title=Some Section] \samplefile{knuth} \stopsection \stopchapter \stoppart \stoptext And the string “Section 1 Mypart” shows up there. > Below is exactly what I have in my preamble. Note that I have also > included \setuphead [section] which is the true 'section' level below > 'chapter'. Is it possible that this causes some confusion? > Unfortunately, the author still wants 'Part' to be actually named as > 'Section'! > > \setuphead > [part] > [ > placehead=yes, > page=no, > bodypartlabel=part > ] First, there a bunch of (U+00A0) NO-BREAK SPACEs in your code. I don't know if that's added by your mail client or if that's actually in your code. If it's also in the code: Context doesn't like it. The NO-BREAK SPACEs have to go. Second, you have a space (new line) after “bodypartlabel=part”. Add a comma, percent sign or move the closing bracket after the word “part”. Marco

2 1

Appearance of ticks and grids with ConTeXt metapost graph module
by Jean-Philippe Rey 04 Jan '21

04 Jan '21

Dear list, Thanks to Hans, I am now able to use the ConTeXt graph module with LMTX. However, I noticed that the tick/grid labels are drawn with the same parameters as the tick/grid marks. For example grid.bot("@d", 1) withcolor red; will draw the grid line AND "1" in red. The original metapost graph module doesn't apply drawing instructions to the label. That seems a better choice as you usually don't want to apply special effect on the labels. If you really want to draw the label with specific parameters you can write, for example, grid.bot(image(draw textext(1) withcolor blue;), 1) withcolor red; and get red lines and blue labels. With the ConTeXt version, both line and label would be red! What do you think about reverting to the original metapost behavior? If I am right, here is a patch to do it: --- mp-grap.mpiv 2021-01-04 18:29:15.000000000 +0100 +++ mp-grap-new.mpiv 2021-01-04 20:47:36.000000000 +0100 @@ -882,7 +882,7 @@ if c : graph_xyscale fi shifted (((.5 + mfun_laboff@# dotprod (.5,.5)) * mfun_laboff@#) graph_xyscale) ; image(draw p w ; - label@#(if string f : format(f,u) else : f fi, point 0 of p) w) + label@#(if string f : format(f,u) else : f fi, point 0 of p)) fi enddef ; Thanks for reading this far. -- Jean-Philippe Rey jean-philippe.rey(a)centralesupelec.fr 91192 Gif-sur-Yvette Cedex - France Empreinte PGP : 807A 5B2C 69E4 D4B5 783A 428A 1B5E E83E 261B BF51

1 0

Re: [NTG-context] MP reflectedabout broken?
by Damien Thiriet 04 Jan '21

04 Jan '21

> u is undefined. Ups, sorry for the noise. Too used to adding those u and didn't notice it when proofreading. So I shall now dig into a much complex file to understand why it compiled before updating and stop after… Once again sorry for wasting your time. Best regards, Damien Thiriet

1 0

MP reflectedabout broken?
by Damien Thiriet 04 Jan '21

04 Jan '21

Hi, I updated ConTeXt yesterday and went through troubles with reflectedabout. This snippet of code \starttext \startMPpage path p[]; p1:= unitcircle scaled 10; p2:= p1 reflectedabout ((15u,-15u),(15u,15)); draw p1; draw p2; \stopMPpage \stoptext doesn't compile with the following error message metafun > log > I'm unable to apply a partially specified transformation except to a fully known pair or transform. Proceed, and I'll omit the transformation. metafun > log > error: Transform components aren't all known metafun > log > metapost > log > metapost > log > <to be read again> metapost > log > = metapost > log > reflectedabout->transformed.begingroup.transform.temp_transform;(EXPR0)transformed.temp_transform= metapost > log > (EXPR0);(EXPR1)transformed.temp_transform=(EXPR1);xxpart.temp_transform=-yypart.temp_transform;xypa... metapost > log > <*> path p[]; p1:= unitcircle scaled 10; p2:= p1 reflectedabout ((15u,-15u),(15u,15)) metafun > log > metafun > log > I'm unable to apply a partially specified transformation except to a fully known pair or transform. Proceed, and I'll omit the transformation. My version: current version: 2020.12.30 16:45 Did I missused this function before? Best regards, Damien Thiriet

2 1