Re: [NTG-context] Itemization formatting

2019-05-29 Thread Wolfgang Schuster
Taco Hoekwater schrieb am 29.05.2019 um 16:15: Hi all, I must be getting old :( It used to be that I could get ConTeXt to do what I wanted, but that is increasingly getting harder. Current problem: I would like to have itemizations that behave like in this dummy ascii formatting: *

Re: [NTG-context] Itemization formatting (different question)

2019-05-29 Thread Hans Hagen
On 5/29/2019 5:20 PM, Taco Hoekwater wrote: Hi Wolfgang, So the answer is no right now, then? In that case, I would like to log a formal feature request ;) so a nested margin would be enough? -

Re: [NTG-context] Itemization formatting

2019-05-29 Thread Hans Hagen
Hi Taco, \start \definesymbol[mystar][\llap{\symbol{star}\hskip10mm}] \setupitemgroup[itemize][intext,mystar] \setupitemgroup[itemize][leftmargin=15mm,rightmargin=5mm] \setupitemgroup[itemize][width=2cm,distance=-25mm] \startitemize \startitem

Re: [NTG-context] Itemization formatting (different question)

2019-05-29 Thread Taco Hoekwater
Hi Wolfgang, So the answer is no right now, then? In that case, I would like to log a formal feature request ;) Taco > On 29 May 2019, at 17:14, Wolfgang Schuster > wrote: > > Taco Hoekwater schrieb am 29.05.2019 um 16:20: >> Hi again, >> >> Another question on nearly the same subject:

Re: [NTG-context] Itemization formatting (different question)

2019-05-29 Thread Wolfgang Schuster
Taco Hoekwater schrieb am 29.05.2019 um 16:20: Hi again, Another question on nearly the same subject: how can I get nested itemizations to listen to the before= and after= keys? AFAICT, they always use the inbetween= instead of above= and below= keys? ConTeXt supports before/after values for

Re: [NTG-context] Itemization formatting

2019-05-29 Thread Taco Hoekwater
Hans, You missed this bit: # > # \setupitemize[option=intext] # > # # > # is nearly right for this case (with indentation equal to the left margin), so I assumed I would # > # be able to tweak that. But the problem there is that while it does 2-4, it ignores the extra # > # indentation

Re: [NTG-context] Itemization formatting

2019-05-29 Thread Taco Hoekwater
Hi, > On 29 May 2019, at 16:53, Tomas Hala wrote: > > > You're right... And this? > > \setupitemize[1][option=intext][margin=1cm] > \setupitemize[2][option=intext][margin=2cm] Sorry, no go, intext is back, but the nested margin setting is ignored. I also tested with

Re: [NTG-context] Itemization formatting

2019-05-29 Thread Hans Hagen
On 5/29/2019 4:15 PM, Taco Hoekwater wrote: Hi all, I must be getting old :( It used to be that I could get ConTeXt to do what I wanted, but that is increasingly getting harder. Current problem: I would like to have itemizations that behave like in this dummy ascii formatting: * Lorem

Re: [NTG-context] Itemization formatting

2019-05-29 Thread Tomas Hala
You're right... And this? \setupitemize[1][option=intext][margin=1cm] \setupitemize[2][option=intext][margin=2cm] Best wishes, Tomáš Wed, May 29, 2019 ve 04:40:09PM +0200 Taco Hoekwater napsal(a): # Hi, # # Not here. The extra empty brackets seem to ‘destroy’ the option=intext # setting, and

Re: [NTG-context] Itemization formatting

2019-05-29 Thread Taco Hoekwater
Hi, Not here. The extra empty brackets seem to ‘destroy’ the option=intext setting, and I am left with a para going like this: • Lorem ipsum dolor sit amet, consectetur adipiscing elit. Donec dapibus turpis et nulla venenatis tincidunt. Curabitur sit amet vehicula nisi, sit amet instead of

Re: [NTG-context] Itemization formatting

2019-05-29 Thread Tomas Hala
Hi Taco, probably, there is missing one pair of []: \setupitemize[1][][margin=1cm] \setupitemize[2][][margin=2cm] I tried it with TL2018 and I guess it works. Best wishes, Tomáš Wed, May 29, 2019 ve 04:15:25PM +0200 Taco Hoekwater napsal(a): # Hi all, # # I must be getting old :( # #

Re: [NTG-context] Itemization formatting (different question)

2019-05-29 Thread Taco Hoekwater
Hi again, Another question on nearly the same subject: how can I get nested itemizations to listen to the before= and after= keys? AFAICT, they always use the inbetween= instead of above= and below= keys? Best wishes as always, Taco itemtest2.pdf Description: Adobe PDF document itemtest2.tex