January 2021 - ntg-context - NTG Mailing Lists

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

mathmatrix and tagging
by Christoph Reller 04 Jan '21

04 Jan '21

Hi, Unfortunately, the following MNWE results in an error when compiled with the latest version of ConTeXt LMTX: \setuptagging[state=start] \definemathmatrix[mymatrix][left={\left(},right={\right)}] \starttext \startformula \startmymatrix \NC A \NC B \NR \stopmymatrix \stopformula \stoptext Omitting "\setuptagging[state=start]" removes the error. A fix would be highly appreciated! Cheers, Christoph

1 1

Part label and chapter numbers
by jbf 04 Jan '21

04 Jan '21

This is a Mark IV issue rather than LMTX, and while it is almost certainly simple enough, I seem to have got myself confused and am not getting the results I need. essentially I am dealing with a book that is divided into parts and chapter, but the parts need to be called 'Section' not 'Part', and the Chapter numbers need to be words and sequential throughout the book, not restarting at each part/section. Issue 1: Parts need to be called 'Section' (Section 1, section 2 etc.). I thought I could achieve this with: \setuphead [part] [ placehead=yes, bodypartlabel=section, ] but then I just get the number 1, 2, not Section 1, Section 2 Of course, if I write bodypartlabel=part, then I do get Part 1, Part 2, etc. How do I achieve 'Section' rather than 'Part'? Issue 2: While the above 'sections' are numbered in arabic numbers, Chapters are meant to be in words. I thought I could do it with \setuphead [chapter] [deepnumbercommand=\convertnumber{words}] but this throws an error. How do I achieve this? I want Chapter One, not Chapter 1.1 Issue 3 might already be solved once I resolve Issue 2! But given that I have parts, the chapters at the moment come out as Chapter 1.1... Chapter 2.1 etc. and I simply want Chapter One, Chapter Two and so on, sequentially throughout the book. I thought I might be able to do it with something like \setuphead[section-2][bodypartconversion=Characters] |But that doesn't work. Any thoughts? Julian |

2 1

Re: [NTG-context] SILE typesetter and other projects
by Andres Conrado Montoya 03 Jan '21

03 Jan '21

Hi Denis. SILE seems interesting, aslo Patoline. However, I think both of these are very immature, and I feel somewhat puzzled by the authors of SILE when they say that you can't do grid typesetting on TeX without horrible hacks, blatantly ignoring ConTeXt's achievements on the matter. If you want to check an alternative typesetting system, I would tell you to not look forward but backwards: groff/troff are alive and well, are very mature, and you can find a lot of documentation and tutorials, even a subreddit: https://www.reddit.com/r/groff/. I would recommend trying the MOM macros for groff: http://www.schaffter.ca/mom/mom-01.html -- Andrés Conrado Montoya Andi Kú andresconrado(a)gmail.com http://sesentaycuatro.com http://messier87.com http://chiquitico.org ---------------------------------------- Los fines no justifican los medios, porque la medida verdadera de nuestro carácter está dada por los medios que estamos dispuestos a utilizar, no por los fines que proclamamos. ---------------------------------------- “You develop an instant global consciousness, a people orientation, an intense dissatisfaction with the state of the world, and a compulsion to do something about it. From out there on the moon, international politics look so petty. You want to grab a politician by the scruff of the neck and drag him a quarter of a million miles out and say, ‘Look at that, you son of a bitch.’” — Apollo 14 astronaut Edgar Mitchell

4 4

SILE typesetter and other projects
by denis.maier＠ub.unibe.ch 03 Jan '21

03 Jan '21

Hi I just came across the SILE typesetter (https://sile-typesetter.org) which looks quite interesting and somehow similar to ConTeXt in some ways (e.g. lua), apart from the fact that it does not use TeX at all. ;-) Another project seems to be Patoline. Just out of curiosity: Has anyone some experience with these tools? Best Denis

3 3