- ntg-context - NTG Mailing Lists

Re: [NTG-context] Typesetting Markdown – Part 5: Interpolation
by Andres Conrado 09 Jul '19

09 Jul '19

Thank you. I still don't really understand why can't you have a "presentational" yaml file and a "content" yaml file (I do it like that... I have a "variables.yaml" file for content and a "settings.yaml" file for presentational stuff, and use a "template.context" file with all my mapped variables within the ConTeXt code, and compile everything using pandoc). But I guess you want to do it this way. Or maybe I'm not really understanding your process. It's quite interesting in any case, and I'm learning a lot. Thanks for sharing. Andrés Conrado Montoya http://chiquitico.org

1 0

Re: [NTG-context] Typesetting Markdown – Part 5: Interpolation
by Andres Conrado 09 Jul '19

09 Jul '19

You can do it on the template... you can use a yaml variable to determine if the toc should be printed or not. Like so: yaml file: --- toc: true ... template file: %%%%%%% $if(toc)$ \completecontent $endif$ %%%%%%% Andrés Conrado Montoya http://chiquitico.org El lun., 8 jul. 2019 a las 2:52, <ntg-context-request(a)ntg.nl> escribió: > Send ntg-context mailing list submissions to > ntg-context(a)ntg.nl > > To subscribe or unsubscribe via the World Wide Web, visit > https://mailman.ntg.nl/mailman/listinfo/ntg-context > or, via email, send a message with subject or body 'help' to > ntg-context-request(a)ntg.nl > > You can reach the person managing the list at > ntg-context-owner(a)ntg.nl > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of ntg-context digest..." > > > Today's Topics: > > 1. Re: Typesetting Markdown – Part 5: Interpolation > (Aditya Mahajan) > 2. Re: Typesetting Markdown – Part 5: Interpolation (Thangalin) > 3. Re: Typesetting Markdown – Part 5: Interpolation > (Aditya Mahajan) > 4. request for \definefontfamily and \definefallbackfamily > (Pablo Rodriguez) > 5. Re: crappy names in the fontloader (Hans Hagen) > 6. problems with images, layers and crop marks (Henning Hraban Ramm) > 7. Re: problems with images, layers and crop marks (Hans Hagen) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 7 Jul 2019 10:17:31 -0400 (EDT) > From: Aditya Mahajan <adityam(a)umich.edu> > To: mailing list for ConTeXt users <ntg-context(a)ntg.nl> > Subject: Re: [NTG-context] Typesetting Markdown – Part 5: > Interpolation > Message-ID: <nycvar.YAK.7.76.1907071012590.13567@nqv-guvaxcnq> > Content-Type: text/plain; charset=US-ASCII; format=flowed > > On Sat, 6 Jul 2019, Thangalin wrote: > > > Hello again! > > > > This part of the series describes how to reference *interpolated* strings > > inside Markdown documents. > > https://dave.autonoma.ca/blog/2019/07/06/typesetting-markdown-part-5/ > > > > There's a section at the end about eliminating the table of contents > from a > > reusable document template. I would have preferred using setups, rather > > than redefining the \completecontent macro, but didn't see an obvious way > > to do so. > > Why not simply omit \compltecontent from the pandoc template? > > Aditya > > > > ------------------------------ > > Message: 2 > Date: Sun, 7 Jul 2019 11:58:12 -0700 > From: Thangalin <thangalin(a)gmail.com> > To: mailing list for ConTeXt users <ntg-context(a)ntg.nl> > Subject: Re: [NTG-context] Typesetting Markdown – Part 5: > Interpolation > Message-ID: > <CAANrE7qd81BudwSHBWufu=MpDDUPn5fh8ZBM63qLVZ160gZH= > g(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Thank you Aditya. > > The main.tex file is meant to be reusable for different document styles. By > removing \completecontent altogether from the main template, it would > preclude a different document from reusing the main.tex template with a > table of contents. I'd like the template to be "reusable"; making > modifications to "main.tex" --- or creating a copy --- would subvert that > goal. > > On Sun, Jul 7, 2019 at 7:17 AM Aditya Mahajan <adityam(a)umich.edu> wrote: > > > On Sat, 6 Jul 2019, Thangalin wrote: > > > > > Hello again! > > > > > > This part of the series describes how to reference *interpolated* > strings > > > inside Markdown documents. > > > https://dave.autonoma.ca/blog/2019/07/06/typesetting-markdown-part-5/ > > > > > > There's a section at the end about eliminating the table of contents > > from a > > > reusable document template. I would have preferred using setups, rather > > > than redefining the \completecontent macro, but didn't see an obvious > way > > > to do so. > > > > Why not simply omit \compltecontent from the pandoc template? > > > > > > >

2 1

interfaces.definecommand fails with brackets inside string arguments
by mf 09 Jul '19

09 Jul '19

Hello list, i've played a bit with interfaces.definecommand, that lets you define TeX macros from lua (see the "ConTeXt Lua Documents", 7.3 User interfacing). I found that the commands defined by interfaces.definecommand fail when you pass string arguments that contain brackets. I think cldf-int.lua needs a patch to support those kind of arguments. In the meantime it's possible to bypass the problem passing arguments with brackets inside double braces, as in the MWE attached. Best wishes, Massimiliano

3 3

Typesetting Markdown – Part 5: Interpolation
by Thangalin 08 Jul '19

08 Jul '19

Hello again! This part of the series describes how to reference *interpolated* strings inside Markdown documents. https://dave.autonoma.ca/blog/2019/07/06/typesetting-markdown-part-5/ There's a section at the end about eliminating the table of contents from a reusable document template. I would have preferred using setups, rather than redefining the \completecontent macro, but didn't see an obvious way to do so. Thoughts?

2 4

From mkii to mkiv: MathML mtable alignment
by Duncan Hothersall 08 Jul '19

08 Jul '19

The command \setupMMLappearance[mtable][alternative=b] used to give me, in mkii, MathML layouts in which the first column was ragged left, the second column centred, and the third column ragged right. It now seems to be ignored, and the output has all three columns centred. Minimal working example showing the problem: \usemodule[mathml] \setupMMLappearance[mtable][alternative=c] \starttext Some text. \xmlprocessdata{}{<formula> <math xmlns='http://www.w3.org/1998/Math/MathML'> <mtable> <mtr> <mtd> <mi>x</mi> <mo>+</mo> <mi>y</mi> </mtd> <mtd> <mo>=</mo> </mtd> <mtd> <mn>2.56</mn> <mtext> million</mtext> </mtd> </mtr> <mtr> <mtd> <mi>x</mi> </mtd> <mtd> <mo>=</mo> </mtd> <mtd> <mn>2.56</mn> </mtd> </mtr> </mtable> </math> </formula>}{} Some more text. \stoptext What is the successor to \setupMMLappearance please? Thanks very much. Duncan

2 2

problems with images, layers and crop marks
by Henning Hraban Ramm 08 Jul '19

08 Jul '19

Hi all, I’m quite quiet at the moment, because I can access my mailing list address only via inconvenient webmail; since I updated MacOS, neither Apple Mail nor Thunderbird will take my password anymore... :-(( Besides, I’m currently well paid for working with LaTeX, and my other projects get less time. Anyway, one of our authors finally submitted her final corrections, and "of course" my ConTeXt setup that still worked well in May doesn’t behave any more: * stacked layers won’t work on the first page (there should be a title bar above an image; it works on the back cover, but not on the front; but I can enable one of both layers) That might be related to: * on some right pages, including p.1 (cover), crop marks are shifted one page width to the right. * on some pages, crop marks are shifted vertically; might be related to using \offset for image placement. I’m trying to cook up MWEs, but the behaviour is so strange and irregular, that I don’t know if I can reproduce it in a simpler environment... I suspect my combined use of postponing, makeups, layers and \offset might have grown side effects since May. Any ideas? Greetlings, Hraban Greetlings, Hraban Grüßlinge, Hraban --- https://www.fiee.net http://wiki.contextgarden.net https://www.dreiviertelhaus.de GPG Key ID 1C9B22FD

2 4

crappy names in the fontloader
by Marcel Fabian Krüger 08 Jul '19

08 Jul '19

Hi everyone, under default settings, the fontloaders discards all glyph names which are considered "crappy", meaning matching the "p_crappyname" pattern in "font-oup.lua". For some names this makes a lot of sense. For example the name "uni0303" is considered "crappy" and it really provides no useful information. Then there are other names like "t_uni0303" which are still considered "crappy" while they actually aren't completely useless. So I think there would be some value in preserving them. Of course, you can always enable "otf.keepnames" if you need names like this. But I actually want to talk about another class of names: Look at "Udotbelow". This is IMHO a perfectly normal and useful name, but the fontloader still considers it "crappy" because it starts with a "U" followed by a letter which could be a hexadecimal number. I think this is a bit over-agressive. Maybe the "p_crappyname" pattern could be changed to only look for "u<hexadecimal>" if followed by "p_done", marking the end of a component? Best regards, Marcel Krüger

2 2

request for \definefontfamily and \definefallbackfamily
by Pablo Rodriguez 07 Jul '19

07 Jul '19

Hi Wolfgang, I have two requests to be implemented in \definefontfamily. The first one is that is able to load fonts not defined as entries in the font database. Here you have a minimal sample: \definefont[Test][file:texgyrepagella-regular.otf at 10pt] \definefont[TestOne][file:texgyrepagella-regular-500.otf at 10pt] \definefontfamily [mainface] [rm] [Pagella] [tf={file:texgyrepagella-regular.otf}, bf={file:texgyrepagella-regular-500.otf}] \setupbodyfont[mainface] \starttext normal\\ \bf bold not working\\ \Test this works \TestOne this works \stoptext The second one would be to allow method=uppercase to \definefallbackfamily, so it could be used to fake small caps (such as in https://mailman.ntg.nl/pipermail/ntg-context/2018/092878.html. Many thanks for your help, Pablo -- http://www.ousia.tk

1 0

feature request
by Atsuhito Kohda 05 Jul '19

05 Jul '19

I've used LaTeX quite a long time but recently I begin to use ConTeXt too. So I'm very sorry if the following is well-known issue. I find an example of \pmatrix in p.21 of "ConTeXt Mark IV an excursion" (ma-cb-en.pdf). And I notice it is defined in /usr/share/texmf/tex/context/base/mkiv/math-pln.mkiv (in Debian). But it seems \bmatrix, \vmatrix are not defined yet. Is there any reason why they are not defined? Similar commands or environments \begin{bmatrix}...\end{bmatrix}, \begin{vmatrix}...\end{vmatrix} are very often used in mathematical LaTeX documents. It is very useful if we can use \bmatrix and \vmatrix in ConTeXt documents, so please add \unexpanded\def\bmatrix#1% {\left[\matrix{#1}\right]} \unexpanded\def\vmatrix#1% {\left|\matrix{#1}\right|} in math-pln.mkiv or somewhere. By the way, I think it is critical to set \setupmathematics[ampersand=normal] to use \matrix above but I can't find this setting in ma-cb-en.pdf It is great if this is added in ma-cb-en.pdf

4 9

I (metapost) can't handle numbers bigger than 32767.99998
by Zhichu 05 Jul '19

05 Jul '19

Hi everyone, I was using metapost to generate some symbols, as in "tex/texmf-context/metapost/context/fonts/mpiv/demo-symbols.tex" Occasionally, I want to customize a glyph whose charcode is a little large, say the character "院": ======================================== ~~~IPython In [1]: for c in u'院': print(ord(c)) 38498 ======================================== so I wrote: ======================================== beginglyph(38498,2,4,0) ; % high voltage interim ahlength := 1 ; drawarrow (1,4) -- (0,2) -- (2,3) -- (1,0) withcolor darkred ; endglyph ; ======================================== and I got: ======================================== ! Enormous number has been reduced. l.60 beginzhglyph(38498 ); I can't handle numbers bigger than 32767.99998; so I've changed your constant to that maximum amount. ======================================== So charcode is a 15-bit integer? Currently, I use `beginglyph(32767,2,4,0) ;` and call it with \char"7FFF. Not an elegant way I think. Is there a fix? I checked the metapost manual and found that charcode is only used to set the filename to something like %{jobname}.%{charcode} I can't see why there's a limit for charcode.

2 2