ntg-context April 2018

ntg-context@ntg.nl

43 participants
81 discussions

Questions about \starttext
by Tomas Hala 15 Apr '18

15 Apr '18

Hi all, doing some tests I discovered two interesting facts. The first is that commands \starttext and \stoptext do not behave as a group. Minimal example (tested on TL2015, TL2016, TL2017, current CTX from the Garden): \starttext text \starttext \bf text \stoptext text % this text is in bold, too. \stoptext Is this the expected behaviour, or not? The second interesting thing is that the unbalanced document is compiled without protests: Minimal example #1 (tested on TL2015, TL2016, TL2017, current CTX from the Garden): \starttext text % in this case, the "text" is shipped out Minimal example #2 (tested on TL2015, TL2016, TL2017, current CTX from the Garden): text % in this case, the "text" is not shipped out \stoptext If this is ok, it does not correspond to our garden wiki (http://wiki.contextgarden.net/Command/starttext): "The first command takes care of a number of initializations, and the last command tells TEX that processing can stop. When this command is left out TEX will display a * (a star) on the command line at the end of the job. TEX will expect a command, for example \end." Wishes, Tomáš Tomáš Hála ------------------------------------------------------------------------ Mendel's University of Agriculture and Forestry, Faculty of Business and Economics, Department of Informatics ------------------------------------------------------------------------ Mendelova zemědělská a lesnická univerzita, Provozně ekonomická fakulta, Ústav informatiky, Zemědělská 5, CZ-613 00 Brno, tel. +420 545 13 22 28 ------------------------------------------------------------------------ http://www.mendelu.cz/~thala

4 5

newcolumnsets: Why are settings only applied on left pages?
by Henri Menke 14 Apr '18

14 Apr '18

Dear list, I want to have columns of different widths in my document. Therefore I'm using the newcolumnsets (aka pagegrids). However, it seems as if my settings are only applied on right pages. Why is that? I tried adding page=left and page=right but that doesn't do anything. MWE is below. Cheers, Henri --- \usemodule[newcolumnsets,visual] \definepagegrid[example][n=3,distance=.05\makeupwidth] \setuppagegrid[example:1][width=.4\makeupwidth] \setuppagegrid[example:2][width=.25\makeupwidth] \setuppagegrid[example:3][width=.25\makeupwidth] \starttext \startpagegrid[example] \dorecurse{6}{\fakewords{50}{75}\column} \stoppagegrid \stoptext

2 1

Re: [NTG-context] Font fallback scaling
by Magnus J 13 Apr '18

13 Apr '18

Well that's even more odd. Is it visible in the attachment? Tested with updated Acrobat Reader and Sumatra pdf viewer without any visible \prime or \doubleprime, except in the footnote (where there is no \wedge on the other hand)... Note that \prime is visible as a footnote symbol, which is also in math mode. If I comment *all* of the \definefallbackfamily rows, it shows in the math example (but then it's Termes of course). With any of the \definefallbackfamily uncommented, it won't show. Should I disable the fallback for a specific character, i.e., remove the characters from one of the fallback ranges? And how is that done? I don't care if Termes is used for most of the symbols, but I want to keep as much Garamond as possible in math mode, especially for letters and number. /MJO > On 4/13/2018 12:34 PM, Magnus J wrote: > > > $D\prime = 0.98$ % <-- no \prime in output > > > > $D\doubleprime = 0.98$ % <-- no \doubleprime in output > hm, i see primes here > > > ----------------------------------------------------------------- > 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 3

Re: [NTG-context] Font fallback scaling
by Magnus J 13 Apr '18

13 Apr '18

Thanks, I could have sworn I had tested that. With my new setup, I still have trouble with some characters in math mode. Specifically, I don't see the \prime and \doubleprime characters in math mode, and I can't use \wedge as a footnote symbol. Consider this commented example, pdf result attached. /MJO % define the characters to use for Garamond in math mode \definefontfamilypreset [math:somesymbols] [range={0x0002A-0x0002E,0x000A7,0x000B6,0x000D7,0x000F7,0x02020-0x02021,0x02212,0x02219-0x02226,0x02228-0x02265,0x02012,0x0003C-0x0003E,0x0007C}, tf=style:regular, offset=lowercasenormal, ] \definefallbackfamily[mainface][math][Adobe Garamond Pro][rscale=1.05,range=digitsnormal] \definefallbackfamily[mainface][math][Adobe Garamond Pro][rscale=1.05,range=lowercasenormal] \definefallbackfamily[mainface][math][Adobe Garamond Pro][rscale=1.05,range=lowercaseitalic] \definefallbackfamily[mainface][math][Adobe Garamond Pro][rscale=1.05,range=uppercasenormal] \definefallbackfamily[mainface][math][Adobe Garamond Pro][rscale=1.05,range=uppercaseitalic] \definefallbackfamily[mainface][math][Adobe Garamond Pro][rscale=1.05,range=math:somesymbols] \definefontfamily[mainface][serif][Adobe Garamond Pro] \definefontfamily[mainface][math][TeX Gyre Termes Math][scale=0.9] \setupbodyfont[mainface,11pt] % footnotes \defineconversion[avhset][\m{\wedge},\m{\prime}] \setupnotation[footnote][way=bypage,numberconversion=avhset] \enabletrackers[fonts.missing] \starttext $D\prime = 0.98$ % <-- no \prime in output $D\doubleprime = 0.98$ % <-- no \doubleprime in output wedge\wedge\footnote{wedge} % <-- lua stats > unknown math characters: ∧ (U+02227) (n=2) prime\prime\footnote{prime} % <-- \stoptext > On 4/12/2018 6:17 PM, Magnus J wrote: > > I use Adobe Garamond Pro in combination with Termes Math for math (the > > latter for missing glyphs, Garamond is not very complete). How can I > > scale size of Termes Math without decreasing the size of the Garamond > > glyphs in math mode? > > > > /MJO > > > > > > % define the characters to use for Garamond in math mode > > \definefontfamilypreset > > [math:somesymbols] > > > > [range={0x0002A-0x0002E,0x000A7,0x000B6,0x000D7,0x000F7,0x02020-0x02021,0= x02212,0x02219-0x02226,0x02228-0x02265,0x02012,0x0003C-0x0003E,0x0007C}, > > tf=style:regular, > > offset=lowercasenormal, > > ] > > > > \definefallbackfamily[mainface][mm][Adobe Garamond > > Pro][math:digitsnormal] > > \definefallbackfamily[mainface][mm][Adobe Garamond > > Pro][math:lowercasenormal] > > \definefallbackfamily[mainface][mm][Adobe Garamond > > Pro][math:lowercaseitalic] > > \definefallbackfamily[mainface][mm][Adobe Garamond > > Pro][math:uppercasenormal] > > \definefallbackfamily[mainface][mm][Adobe Garamond > > Pro][math:uppercaseitalic] > > \definefallbackfamily[mainface][mm][Adobe Garamond > > Pro][math:somesymbols] > > > > \definefontfamily[mainface][rm][Adobe Garamond Pro] > > \definefontfamily[mainface][mm][TeX Gyre Termes Math][scale=0.9] % > > <-- scaling here... > > > > \setupbodyfont[mainface,11pt] > > > > \starttext > > 100 > > > > $100$ % <-- leads to math mode that is smaller than text, even for > > Garamond glyphs > > \stoptext > \definefallbackfamily[mainface][math][Adobe Garamond > Pro][rscale=1.05,range=digitsnormal] > \definefallbackfamily[mainface][math][Adobe Garamond > Pro][rscale=1.05,range=lowercasenormal] > \definefallbackfamily[mainface][math][Adobe Garamond > Pro][rscale=1.05,range=lowercaseitalic] > \definefallbackfamily[mainface][math][Adobe Garamond > Pro][rscale=1.05,range=uppercasenormal] > \definefallbackfamily[mainface][math][Adobe Garamond > Pro][rscale=1.05,range=uppercaseitalic] > \definefallbackfamily[mainface][math][Adobe Garamond > Pro][rscale=1.05,range=math:somesymbols] > > \definefontfamily [mainface] [serif] [Adobe Garamond Pro] > \definefontfamily [mainface] [math] [TeX Gyre Termes Math] > > \setupbodyfont[mainface] > > > ----------------------------------------------------------------- > 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

Reference links with focus=standard
by Christoph Reller 13 Apr '18

13 Apr '18

On Fri, 13 Apr 2018 10:45:39 +0100, Lawrence Bell <lawrence.matthew.bell(a)gmail.com> wrote: > On 13/04/18 07:31, Henri Menke wrote: >> >> On Fri, 2018-04-13 at 08:13 +0200, Christoph Reller wrote: >>> >>> Please, Hans, I kindly ask you to reconsider. I am aware of your >>> opinion and reasoning about this issue. But I believe that for many of >>> us users, today's PDFs need to be both, interactive *and* printable. >>> >>> If there is any way I can help or motivate you, then please tell me ;-) >>> >> The best way to motivate Hans to implement something you need, is by >> implementing it yourself and sending him updated core files. >> Works for me every time ;-) >> Well, thank you for this hint Henry, but that works only for those who can afford the time :-/ > > Dear Christoph, > > I take it from your reply that fixing this problem with interactivity > would likely cause some trouble with the printability? And therefore, > it's staying as it is to prioritize printability? That's understandable, > but a bit frustrating, since I still don't have any clue what the actual > problem is. Could you possibly explain in some more detail or point me > to a relevant thread? > > Kind regards, > > Lawrence > Dear Lawrence, (Sorry for changing to bottom posting style.) This issue is not about a trade-off between print-ability and inter-activeness. If I understand Hans' position correctly, then at least part of his reasoning is the following (please correct me if I'm wrong): It is easy to produce two versions of a document from one common source, one version for print and one for the screen. The former needs no interactive links and the latter should best be viewed fullscreen, i.e., without scrolling, in which case focus=standard is unnecessary. While I largely agree with this approach, many of the ConTeXt users (including myself) are not in a position to decide how their documents should be published. I believe that many of today's PDF documents still are meant to be both, viewed on screen and printed. And it's only for this scenario that focus=standard makes sense. Kind regards, Christoph

1 0

Re: [NTG-context] Reference links with focus=standard option
by Christoph Reller 13 Apr '18

13 Apr '18

Fri, 13 Apr 2018 11:48:28 +0200, Hans Hagen <j.hagen(a)xs4all.nl> wrote: > On 4/13/2018 8:13 AM, Christoph Reller wrote: >> >> This is a long standing feature request reported multiple times by >> myself and others with MWEs in >> https://www.mail-archive.com/ntg-context@ntg.nl/msg79620.html and >> https://www.mail-archive.com/ntg-context@ntg.nl/msg79727.html. >> >> Another MWE in which the link is non-functional: >> > fixed in next beta (i'm not sure when i will upload that one as i need > to test some new features first) > Thank you Hans! This is good news. Your work is very much appreciated. I am looking forward to the next beta. Regards, Christoph

1 0

Installing fonts in a ConTeXt Docker (texfont tool missing?)
by Rodzis, Michelle 13 Apr '18

13 Apr '18

Dear list, currently I work on a customized Docker container based on Ubuntu 16.04 where I run ConTeXt standalone. To install ConTeXt, I use the approach described in the wiki: RUN wget http://minimals.contextgarden.net/setup/first-setup.sh &&\ sh ./first-setup.sh --modules=all After setting ConTeXt root everything works fine and as expected. However, the texfont tool seems to be missing which means I cannot install new fonts in my container. This seems kind of odd to me since I thought texfont is available automatically after ConTeXt is installed. I also tried Henri's Debian-based Dockerfile, but texfont seems to be missing there, too. Any ideas on this? Have I missed something? Many thanks in advance and best wishes, Michelle

5 10

Re: [NTG-context] Reference links with focus=standard option
by Christoph Reller 13 Apr '18

13 Apr '18

> On Wed, 11 Apr 2018 20:27:15 +0100, Lawrence Bell <lawrence.matthew.bell(a)gmail.com> wrote: > > Thanks very much for your replies. It's reassuring to see (it seems) > that I've not overlooked some extra option that magically does the job > :) Worst case scenario I'll hack something together, or just settle for > the default focus functionality, which is not the end of the world. Just > feel like there should be a better/more elegant way. > > On 11/04/18 19:36, Pablo Rodriguez wrote: >> On 04/11/2018 07:14 PM, Pablo Rodriguez wrote: >>> On 04/11/2018 04:35 PM, Lawrence Bell wrote: >>>> [...] >>>> What's going on here? >>> I generated an uncompressed PDF document from your source: >>> http://pdf.ousia.tk/focus-standard.pdf. >>> [...] >>> (eq:ref) seems to be missing there. But I have to investigate the issue >>> further to get a more accurate report. >> [...] >> Sorry, but I’m afraid that I don’t know exactly what misbehaves here. I >> hope Hans can fix it. Dear all, This is a long standing feature request reported multiple times by myself and others with MWEs in https://www.mail-archive.com/ntg-context@ntg.nl/msg79620.html and https://www.mail-archive.com/ntg-context@ntg.nl/msg79727.html. Another MWE in which the link is non-functional: \setupexternalfigures[location={local,global,default}] \setupinteraction[state=start, focus=standard] \starttext \about[figure]. \page \placefigure[][figure]{Figure}{\externalfigure[cow.pdf]} \stoptext Please, Hans, I kindly ask you to reconsider. I am aware of your opinion and reasoning about this issue. But I believe that for many of us users, today's PDFs need to be both, interactive *and* printable. If there is any way I can help or motivate you, then please tell me ;-) Kind regards, Christoph

4 3

\setupfloatcaption align=
by Alan Braslau 12 Apr '18

12 Apr '18

Hello list, According to the interface files (texmf-context/tex/context/interface/mkiv) \setupfloatcaption takes an align= parameter (inherits from \setupalign). Additionally, it suggests that the location= parameter can take the keywords tolerant, verytolerant and stretch. None of this appears to work. \setupcaption [figure] [align=verytolerant] is ignored, and \setupcaption [figure] [location={bottom,verytolerant}] gives unexpected and surprising results. I cheat, and use \setupcaption [figure] [style={\setupalign[verytolerant]}] but this is hardly a proper solution. Question: Why do figure captions NOT inherit from \setupalign, i.e. \setupalign[verytolerant] in a preamble does not have an effect on float captions? Question2: What is going on with \setupfloatcaption ? Thanks Alan

2 7

Font fallback scaling
by Magnus J 12 Apr '18

12 Apr '18

I use Adobe Garamond Pro in combination with Termes Math for math (the latter for missing glyphs, Garamond is not very complete). How can I scale size of Termes Math without decreasing the size of the Garamond glyphs in math mode? /MJO % define the characters to use for Garamond in math mode \definefontfamilypreset [math:somesymbols] [range={0x0002A-0x0002E,0x000A7,0x000B6,0x000D7,0x000F7,0x02020-0x02021,0x02212,0x02219-0x02226,0x02228-0x02265,0x02012,0x0003C-0x0003E,0x0007C}, tf=style:regular, offset=lowercasenormal, ] \definefallbackfamily[mainface][mm][Adobe Garamond Pro][math:digitsnormal] \definefallbackfamily[mainface][mm][Adobe Garamond Pro][math:lowercasenormal] \definefallbackfamily[mainface][mm][Adobe Garamond Pro][math:lowercaseitalic] \definefallbackfamily[mainface][mm][Adobe Garamond Pro][math:uppercasenormal] \definefallbackfamily[mainface][mm][Adobe Garamond Pro][math:uppercaseitalic] \definefallbackfamily[mainface][mm][Adobe Garamond Pro][math:somesymbols] \definefontfamily[mainface][rm][Adobe Garamond Pro] \definefontfamily[mainface][mm][TeX Gyre Termes Math][scale=0.9] % <-- scaling here... \setupbodyfont[mainface,11pt] \starttext 100 $100$ % <-- leads to math mode that is smaller than text, even for Garamond glyphs \stoptext

2 1

← Newer
1
2
3
4
5
6
7
8
9
Older →

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

ntg-context April 2018