Re: [NTG-context] Use \unit for value and uncertainty

2020-05-09 Thread Benjamin Buchmuller
I know this is quite an old thread, but here is a minimal parser (\units with an “s”) that wraps around \digits and \unit to produce an acceptable output. As I frequently need to write ranges (or measures of uncertainty), I find it convenient to able to type \units{4.0 to 5.0 centi meter}

Re: [NTG-context] mkiv digits/units zero padding not working

2020-05-07 Thread Benjamin Buchmuller
\stopxtablebody \stopxtable > On 7 May 2020, at 21:22, Benjamin Buchmuller > wrote: > > Hi Wolfgang, > > you are (of course) right again. I realised that I wouldn’t get the expected > behaviour after checking the snippet isolated from my documen

[NTG-context] mkiv \digits{2.0=} zero padding feature request

2020-05-07 Thread Benjamin Buchmuller
Hi, As Wolfgang has figured out, zero padding in \digits only works for trailing (and omitted) zeroes when immediately preceded by the decimal separator. It would be nice if this would work even if there is a number preceding, so that \digits{3.1=}x\crlf \digits{3.==}x\crlf \digits{3.14}x

Re: [NTG-context] mkiv digits/units zero padding not working

2020-05-07 Thread Benjamin Buchmuller
:00, Wolfgang Schuster > wrote: > > Benjamin Buchmuller schrieb am 07.05.2020 um 19:41: >> Hi Wolfang, >> Thank you for your reply. I have indeed not explained my intended result >> very clearly. >> 1. >> Primarily, I need to get the two values aligned at the d

Re: [NTG-context] mkiv digits/units zero padding not working

2020-05-07 Thread Benjamin Buchmuller
by . > On 7 May 2020, at 18:21, Wolfgang Schuster > wrote: > > Benjamin Buchmuller schrieb am 07.05.2020 um 17:31: >> Hi, >> I’m trying to get >> \digits{15.0=}±\digits{1.00} >> \digits{_8.12}±\digits{0.34} >> horizontally aligned as >> 15.0 ±1.00

[NTG-context] mkiv digits/units zero padding not working

2020-05-07 Thread Benjamin Buchmuller
Hi, I’m trying to get \digits{15.0=}±\digits{1.00} \digits{_8.12}±\digits{0.34} horizontally aligned as 15.0 ±1.00 8.12±0.34 But I get 15.0±1.00 8.12±0.34 instead. From the source (phys-dim.mkiv), I can see that “=“ should expand to \hphantom{0}. (I think \zeropoint in the table is

Re: [NTG-context] \placetable[location=split] reference ??

2020-05-07 Thread Benjamin Buchmuller
be different as soon as xtable tries to place them … Cheers \startplacetable[reference=tab1,title={A table},location=split] \startxtable[split=repeat] \startxrow \startxcell hi \stopxcell \stopxrow \stopxtable \stopplacetable > On 22 Apr 2020, at 21:10, Benjamin Buchmuller > wrote: > >

Re: [NTG-context] Basic font question (Optima, but no bold, no italics). Standalone ConTeXt does not work. TeX Live 2019 works

2020-04-26 Thread Benjamin Buchmuller
020, at 12:14, Benjamin Buchmuller > wrote: > > Hi Hraban, > > Thanks for the hint (and the proper fontfamily setup), I have forced reload > ten times now from various accounts; the issue persists unfortunately. > > This might confirm Taco‘s notion that there is some bug

Re: [NTG-context] Basic font question (Optima, but no bold, no italics). Standalone ConTeXt does not work. TeX Live 2019 works

2020-04-24 Thread Benjamin Buchmuller
of Dec/Jan three days ago, I suspect it is not because of a new feature in the OS, but rather an old feature in mtxrun or elsewhere having disappeared. > On 24. Apr 2020, at 11:35, Henning Hraban Ramm wrote: > > > >> Am 24.04.2020 um 11:13 schrieb Benjamin Buchmuller &g

Re: [NTG-context] Basic font question (Optima, but no bold, no italics). Standalone ConTeXt does not work. TeX Live 2019 works

2020-04-24 Thread Benjamin Buchmuller
Although this specific issue might have been solved meanwhile by the helpful suggestions of Wolfang, Thomas and others, I would like to point out that I have recently also encountered an odd behaviour of the mtxrun fontloader in the standalone, in which not all typefaces are available/properly

Re: [NTG-context] Hyphentation/Linebreak after x characters

2020-04-24 Thread Benjamin Buchmuller
4/23/2020 17:50, Wolfgang Schuster wrote: >> Benjamin Buchmuller schrieb am 23.04.2020 um 23:16: >>> Hi Rik, >>> >>> Thanks for the fast reply! Your example works indeed nicely. However, >>> within this solution my problem has shifted now (fully) towards

Re: [NTG-context] Hyphentation/Linebreak after x characters

2020-04-23 Thread Benjamin Buchmuller
Thanks Wolfgang, this works perfectly. I will add this hint tomorrow to the Wiki. > On 23 Apr 2020, at 23:50, Wolfgang Schuster > wrote: > > Benjamin Buchmuller schrieb am 23.04.2020 um 23:16: >> Hi Rik, >> Thanks for the fast reply! Your example works indeed

Re: [NTG-context] Hyphentation/Linebreak after x characters

2020-04-23 Thread Benjamin Buchmuller
pril 2020 at 21:46:59 CEST > To: ntg-context@ntg.nl, benjamin.buchmul...@gmail.com > > > > > On 4/23/2020 15:01, Benjamin Buchmuller wrote: >> Sorry, I have just realized that the problem might not be \WORD{} actually, >> so this one hyphenates: >> >> \define[2]\m

Re: [NTG-context] Hyphentation/Linebreak after x characters inside \WORD?

2020-04-23 Thread Benjamin Buchmuller
23 Apr 2020, at 20:46, Benjamin Buchmuller > wrote: > > Hi again, > > I am reading a CSV file into ConTeXt which contains long DNA sequences (>> 40 > characters) to place in xtables. So far, this works fine. However, I need to > uppercase the entries and need to \

[NTG-context] Hyphentation/Linebreak after x characters inside \WORD?

2020-04-23 Thread Benjamin Buchmuller
Hi again, I am reading a CSV file into ConTeXt which contains long DNA sequences (>> 40 characters) to place in xtables. So far, this works fine. However, I need to uppercase the entries and need to \tt them. When I do this inside \WORD however, they don’t hyphenate any more. I’m using:

[NTG-context] mtxrun fontloader in recent standalone

2020-04-22 Thread Benjamin Buchmuller
I’ve just updated to the most recent standalone ConTeXt ver: 2020.01.30 14:13 MKIV beta fmt: 2020.4.22 (LuaTeX 1.11.1) and I’m running now into troubles with system font indexing: mtxrun --script fonts --reload locates fonts in macOS directories appropriately (*.afm fonts placed in

[NTG-context] \placetable[location=split] reference ??

2020-04-22 Thread Benjamin Buchmuller
Hi, I would like to reference a table of the following structure. \starttext \startplacetable[reference=tab1,title={A table},location=split] \startxtable \startxrow \startxcell hi \stopxcell \stopxrow \stopxtable \stopplacetable In Table \in[tab1] \stoptext It has [location=split], which I

Re: [NTG-context] \placenamedfloat and \setuphead[aftersection=...] broken?

2020-04-03 Thread Benjamin Buchmuller
.) is simply not “converted" to \starthead ... \stophead before the next invocation of \head or the end of \stoptext? Cheers Benjamin > On 2 Apr 2020, at 19:51, Wolfgang Schuster > wrote: > > Benjamin Buchmuller schrieb am 02.04.2020 um 19:29: >> Potentially on the same

[NTG-context] \placenamedfloat and \setuphead[aftersection=...] broken?

2020-04-02 Thread Benjamin Buchmuller
Potentially on the same lines, placing delayed element seems currently not to work properly (or the syntax has changed?). I think these features of MkIV are very elegant and useful. I’m just wondering if they are/were temporarily not working (tried on 2019.12.27 16:34 MKIV beta and the Wiki’s

[NTG-context] \setupinteraction[style=...] supersedes manual text style for \note

2020-04-01 Thread Benjamin Buchmuller
For the following one, I’m not sure if this is the intended behaviour or not: I want to set up the “notation” and “note” style manually, which works great unless I also call \setupinteraction[state=start,style=normal] (or any other style), regardless of calling it before or after setting up

[NTG-context] placelistofsynonyms without tabulate

2020-03-30 Thread Benjamin Buchmuller
Following Aditya’s recommendation on making a glossary with ConTeXt (https://tex.stackexchange.com/questions/152248/make-a-glossary-with-context) and have looked through several older and newer manuals under “abbreviations” and into the source. However, I cannot figure out if there is a

[NTG-context] Changing default rule thickness (globally)

2020-03-25 Thread Benjamin Buchmuller
Hi! I would like to change the rule thickness that is used by default in ConTeXt. However, from the command documentation (http://www.pragma-ade.nl/general/qrcs/setup-en.pdf), I see that I would need to basically change this for \basegrid[rulethickness=...] \setupbar[rulethickness=...]

[NTG-context] \setupfooter[color=red]: red color spills with float over next page

2016-12-19 Thread Benjamin Buchmuller
Hi Hans, the patch solves the issue. Thank you for the fast reply. With regard to Pablo’s question: When I would not use crop in the MWE, apparently I would get the desired output indeed. However, in the situation I was using the command to produce a document, I would need to crop some parts

[NTG-context] \setupfooter[color=red]: red color spills with float over next page

2016-12-18 Thread Benjamin Buchmuller
Hi Hans, I finally managed to make a MWE. The issue is related to me using \clip{…} onto external figures I would like to crop in conjunction with a colored footer set-up: \starttext \setupfooter[color=red] \setupfootertexts [] [] [any

Re: [NTG-context] \setupfooter[color=red]: red color spills with float over next page

2016-12-04 Thread Benjamin Buchmuller
..@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. \setupfooter[color=red]: red color spills with float over > next page (Benjamin Buchmuller) &

[NTG-context] \setupfooter[color=red]: red color spills with float over next page

2016-12-03 Thread Benjamin Buchmuller
When I have \setupfooter[color=red, style=bold] (same goes with \setupfooter[style=red]) and a tex text text % page breaks here after typesetting \startplacefigure[ %location=force, % no matter what I do here title={Caption.} ] … something … \stopplacefigure other

[NTG-context] Another question about definerefereformat

2016-11-13 Thread Benjamin Buchmuller
Here is another question, I was wondering about. What is the ConTeXt’s way to provide the “right” (or “left”) argument when \definereferenceformat[text=…] is set? Starting from this example: \starttext \definereferenceformat[infig][text={Figure }] \startplacefigure[reference=fig:A] Some

[NTG-context] Setupreferencing[interaction=text] breaks referenceformat[text={…}]

2016-11-13 Thread Benjamin Buchmuller
Hi, I’m not sure if this is the intended behaviour of the system, but I want to typeset “This is Figure 1.1 in Chapter A Good Story” in the attached minimal example. However, setting up the referencing interaction to text, this typesets “This is 1.1 in Chapter A Good Story”. The same holds

[NTG-context] “Case-insensitive” sorting for \placelistofsynonyms?

2014-05-29 Thread Benjamin Buchmuller
Hi list, according to case-insensitive sorting for \placeregister[…][…, method=…], I tried to figure out how to achieve similar results for \placelistofsynonyms (has method-key too). I tried this modified minimal example (that originally was proposed by Hans here: