Footnotes still don’t work in columnsets (latest LMTX): - they stay in one column (I’d prefer them over the whole width of the text area) - they often get overwritten by main text Is there a workaround? Hraban

Am 06.03.2021 um 19:18 schrieb Jano Kula :

Hello Hans,

with fresh LMTX footnotes are still missing in \startcolumns as Clyde reported:

\starttext \startcolumns \input knuth\footnote{D. E. Knuth} \stopcolumns \stoptext

Tried columnsets. Footnotes are overlapping text and some text at the column break disappeared:

\starttext \startcolumnset \dorecurse{10}{\input knuth\footnote{D. E. Knuth}\ } \stopcolumnset \stoptext

We are running out of options :) Could you, please, have a look at it when your metafun mode is over?

Thanks, Jano ConTeXt ver: 2021.03.05 19:14 LMTX fmt: 2021.3.6

On Mon, Jan 25, 2021 at 10:05 PM Clyde Johnston wrote: I can no longer print the footnotes when I using columns in LTMX. If I remove the \{start|stop}columns, it works fine. This works on my old MKIV 2018.07.02 14:39 version.

\setupcolumns[n=2,rule=off,balance=no]

\starttext

\startcolumns

\input ward\footnote{A small footnote here}

\stopcolumns

\stoptext

Context Version: 2021.01.24 16:07

Clyde

On 8/12/2021 10:01 PM, Jano Kula via ntg-context wrote:

Hello Hraban!

On Thu, Aug 12, 2021, 15:24 Henning Hraban Ramm via ntg-context mailto:ntg-context@ntg.nl> wrote:

Footnotes still don’t work in columnsets (latest LMTX):

- they stay in one column (I’d prefer them over the whole width of the text area)

- they often get overwritten by main text

Is there a workaround?

I had to switch back to mkiv. It's on Hans' agenda, but with lots of interferencies there will be no quick fix.

good old mkiv ... so it serves a purpose! i would be more worried when you went back to mkii

Coffee break at the meeting will be the right place to ask for the higher priority. well, for sure, it helps to get my attention when i meet you over coffee (i know you look forward to real coffee)

i will pick up on footnotes once some other long pending priorities (annoyances actually) are met (which i will explain at the evening beer break next month) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------

On 8/13/2021 12:32 AM, Henning Hraban Ramm via ntg-context wrote:

...

Am 13.08.2021 um 00:03 schrieb Hans Hagen via ntg-context :

On 8/12/2021 10:01 PM, Jano Kula via ntg-context wrote:

...

Hello Hraban! On Thu, Aug 12, 2021, 15:24 Henning Hraban Ramm via ntg-context mailto:ntg-context@ntg.nl> wrote: Footnotes still don’t work in columnsets (latest LMTX): - they stay in one column (I’d prefer them over the whole width of the text area) - they often get overwritten by main text Is there a workaround? I had to switch back to mkiv. It's on Hans' agenda, but with lots of interferencies there will be no quick fix.

good old mkiv ... so it serves a purpose! i would be more worried when you went back to mkii

;D Unfortunately I can’t go back to MkIV with the CG journal since some articles use LMTX features.

I’ll probably find some ugly hack to work around the issues...

A lot has to do with defaults. We have several multicolumn mechanisms an cnotes themselves can also come in columns and it's nto easy to have a setup that suits them all, so each mechanism has additional settings. I'm still not sure how to deal with this because there are conflicting demands. So, one ends up in 'fix this setup' 'break that setup' situations (basically it means that we need to setup things on an extra axis: the kind of otr used). It's a bit the price we pay for configurability. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------

On 8/13/2021 8:54 AM, Henning Hraban Ramm via ntg-context wrote:

...

Am 13.08.2021 um 08:43 schrieb Hans Hagen :

On 8/13/2021 12:32 AM, Henning Hraban Ramm via ntg-context wrote:

...

...

Am 13.08.2021 um 00:03 schrieb Hans Hagen via ntg-context :

On 8/12/2021 10:01 PM, Jano Kula via ntg-context wrote:

...

Hello Hraban! On Thu, Aug 12, 2021, 15:24 Henning Hraban Ramm via ntg-context mailto:ntg-context@ntg.nl> wrote: Footnotes still don’t work in columnsets (latest LMTX): - they stay in one column (I’d prefer them over the whole width of the text area) - they often get overwritten by main text Is there a workaround? I had to switch back to mkiv. It's on Hans' agenda, but with lots of interferencies there will be no quick fix.

good old mkiv ... so it serves a purpose! i would be more worried when you went back to mkii ;D Unfortunately I can’t go back to MkIV with the CG journal since some articles use LMTX features. I’ll probably find some ugly hack to work around the issues... A lot has to do with defaults. We have several multicolumn mechanisms an cnotes themselves can also come in columns and it's nto easy to have a setup that suits them all, so each mechanism has additional settings. I'm still not sure how to deal with this because there are conflicting demands. So, one ends up in 'fix this setup' 'break that setup' situations (basically it means that we need to setup things on an extra axis: the kind of otr used). It's a bit the price we pay for configurability.

Would it be viable to use columnset areas for footnotes? Then the user could configure themselves where they should go, how many columns they should span etc.

the problem with notes is that the pagebreak depends on them so it is impossible to predict sizes .. it works with ratios and such in basically a one column operation mode (because that is what tex has) text text text text text text text text text text text text note note note tex has to split page and notes if needed and take optional distance into account the lua(meta)tex engine already privides a bit more control but solutions always have to operate with margins now, if users would accept limitations much is possible but in the end there always a 'i want this note to end up here' demand the same with figures: if they may float we can do a good job, but designers / publishers (unaware of reliable floating) nearly always demand 'it should end up here' which then conflicts with automated typesetting because 'here' means that one also manually messes with the rest Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------