Re: [NTG-context] Automatic thousands separation in \unit

2019-02-09 Thread Marco Patzer
On Tue, 5 Feb 2019 12:22:29 +0100 Marco Patzer wrote: > Is there a way to hook the \spaceddigits into \unit somehow? I tried to add \spaceddigits to the \unit command, but it didn't work. If someone has an idea how to do that, I'd greatly appreciate. Marco

Re: [NTG-context] \date behaving strange

2019-02-09 Thread Hans Hagen
On 2/9/2019 2:39 PM, martin wrote: I'm getting a bit confused. The \date function doesn't result in a formatted date. That goes for some files that are a few weeks old. What am I missing? \starttext \date[d=2,m=3,y= 2018] \stoptext results in: d=2m=3y= 2018 An optional formatting

Re: [NTG-context] Bad names

2019-02-09 Thread Hans Hagen
On 2/9/2019 12:15 AM, Alan Braslau wrote: On Fri, 8 Feb 2019 23:26:21 +0100 Hans Hagen wrote: On 2/8/2019 10:22 PM, Marco Patzer wrote: What is a bad name for context? Does it have any consequences if badly named files are used? Just being curious. Bad names are names that can result i a

[NTG-context] \date behaving strange

2019-02-09 Thread martin
I'm getting a bit confused. The \date function doesn't result in a formatted date. That goes for some files that are a few weeks old. What am I missing? \starttext \date[d=2,m=3,y= 2018] \stoptext results in: d=2m=3y= 2018 An optional formatting parameter has no effect \date[d=1, m=4,

Re: [NTG-context] Bad names

2019-02-09 Thread Marco Patzer
On Fri, 8 Feb 2019 23:26:21 +0100 Hans Hagen wrote: > On 2/8/2019 10:22 PM, Marco Patzer wrote: > > > What is a bad name for context? Does it have any consequences if > > badly named files are used? Just being curious. > Bad names are names that can result i a miss when looked up on a case >