Re: [NTG-context] Protect the lettrine

2023-06-13 Thread Otared Kavian via ntg-context
Hi, Adding \hfill\break to the short line solves the issue, but probably there is a better way to achieve the correct result. \setupinitial[n=2] \setuphead[chapter][ after={\placeinitial}, page=no, ] \starttext \chapter{one} Kermit Ruffins \hfill\break % <--- Meet me at the second line.

[NTG-context] xml nbsp?

2023-06-13 Thread Hans van der Meer via ntg-context
What happened to the non breaking space in XML? It has disappeared in a way. See the minimal example attached.dr. Hans van der Meer test-nbsp.pdf Description: Adobe PDF document ___ If your question is of interest to

Re: [NTG-context] letfrozen?

2023-06-13 Thread Hans van der Meer via ntg-context
Of course. But without that \enabledirective I can redefine the frozen macro at will, as a simple test did show. The crux, however, is that one wants to protect the frozen code always, irrespective of that directive setting. dr. Hans van der Meer > On 12 Jun 2023, at 19:47, Hans Hagen via

Re: [NTG-context] Protect the lettrine

2023-06-13 Thread Thangalin via ntg-context
Thanks Otared, Unfortunately, that's adding content between \starttext and \stoptext, which isn't tenable in my situation. The user is writing in Markdown, which is automatically converted to XHTML then passed to ConTeXt, and so the setups need to account for this scenario without modifying the

Re: [NTG-context] Protect the lettrine

2023-06-13 Thread Thangalin via ntg-context
Here's the output I'm looking to achieve: https://i.stack.imgur.com/XeZQS.png Note how the second line honours the lettrine's width and padding, in the same way that the second line of the first paragraph in Knuth's quote respects the width and padding. On Tue, Jun 13, 2023 at 2:01 PM Thangalin

Re: [NTG-context] xml nbsp?

2023-06-13 Thread Bruce Horrocks via ntg-context
is not a pre-defined named character in XML (but it is in HTML which lulls you into a false sense of security). See the link below for some more detail and a fix. > On 13 Jun 2023, at 11:01, Hans van der Meer via

Re: [NTG-context] letfrozen?

2023-06-13 Thread Hans Hagen via ntg-context
On 6/13/2023 12:43 PM, Hans van der Meer via ntg-context wrote: Of course. But without that \enabledirective I can redefine the frozen macro at will, as a simple test did show. The crux, however, is that one wants to protect the frozen code always, irrespective of that directive setting. there

Re: [NTG-context] Protect the lettrine

2023-06-13 Thread Thangalin via ntg-context
Thank you for taking the time to reply, linguafalsa, I appreciate it. The source document is written in Markdown using KeenWrite, my Markdown editor. Inserting typesetting instructions into the document would defeat the software's architecture, hence being untenable. After the Markdown is

Re: [NTG-context] Protect the lettrine

2023-06-13 Thread linguafalsa--- via ntg-context
On Tue, Jun 13, 2023 at 02:01:14PM -0700, Thangalin via ntg-context wrote: > Thanks Otared, > > Unfortunately, that's adding content between \starttext and \stoptext, > which isn't tenable in my situation. The user is writing in Markdown, which > is automatically converted to XHTML then passed to