From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/106445 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Jean-Pierre Delange Newsgroups: gmane.comp.tex.context Subject: Re: body text invades space for notes Date: Wed, 4 Mar 2020 12:44:11 +0100 Message-ID: References: <7e17aaa4-e8c2-6e00-1798-b35baa0c2611@gmx.es> <556eea4f-ba2c-89ae-5454-fa49266e0758@gmx.es> Reply-To: mailing list for ConTeXt users Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5415904384554497463==" Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="119090"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 To: ntg-context@ntg.nl Original-X-From: ntg-context-bounces@ntg.nl Wed Mar 04 12:44:50 2020 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane-mx.org Original-Received: from zapf.boekplan.nl ([5.39.185.232] helo=zapf.ntg.nl) by ciao.gmane.io with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1j9SSG-000Urc-LE for gctc-ntg-context-518@m.gmane-mx.org; Wed, 04 Mar 2020 12:44:48 +0100 Original-Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id E3AB81826FA; Wed, 4 Mar 2020 12:44:15 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl Original-Received: from zapf.ntg.nl ([127.0.0.1]) by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e_5VaIpZnKgL; Wed, 4 Mar 2020 12:44:14 +0100 (CET) Original-Received: from zapf.ntg.nl (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 408DA1826E7; Wed, 4 Mar 2020 12:44:14 +0100 (CET) Original-Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 2D2991826CB for ; Wed, 4 Mar 2020 12:44:13 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl Original-Received: from zapf.ntg.nl ([127.0.0.1]) by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FEOUVQmLGsIs for ; Wed, 4 Mar 2020 12:44:11 +0100 (CET) Received-SPF: None (mailfrom) identity=mailfrom; client-ip=212.27.42.4; helo=smtp4-g21.free.fr; envelope-from=adeimantos@free.fr; receiver= Original-Received: from smtp4-g21.free.fr (smtp4-g21.free.fr [212.27.42.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by zapf.ntg.nl (Postfix) with ESMTPS id BA3C81824B9 for ; Wed, 4 Mar 2020 12:44:11 +0100 (CET) Original-Received: from [IPv6:2a01:e0a:20b:7080::5cd8:261f] (unknown [IPv6:2a01:e0a:20b:7080::5cd8:261f]) by smtp4-g21.free.fr (Postfix) with ESMTP id 6A0FC19F574 for ; Wed, 4 Mar 2020 12:44:11 +0100 (CET) In-Reply-To: Content-Language: fr X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.26 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ntg-context-bounces@ntg.nl Original-Sender: "ntg-context" Xref: news.gmane.io gmane.comp.tex.context:106445 Archived-At: This is a multi-part message in MIME format. --===============5415904384554497463== Content-Type: multipart/alternative; boundary="------------972D1F431E242A6A327112AD" Content-Language: fr This is a multi-part message in MIME format. --------------972D1F431E242A6A327112AD Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Dear Pablo, It seems that we never should say "never" about things which appear all over the real world. I just go back to a previous assertion you made here. I agree with you about footnotes which should be placed on the same page (I quote) : >    Bottom notes are somewhat tricky in ConTeXt. The user expects that these >     notes (either footnotes, or linenotes) aren’t moved to the next page. I >     mean, no reader expects to find a full footnote in the next page from >     the one that calls it. (At least, I have never seen that in any book >     read or paged through.) But, I am afraid to inform you that it is a kind of way of French printing, especially in Philosophy publishers (which are not known to be devoted to publish beautiful/strictly edited/... books). As a kind of sample, see the French translation of Nichomachean Ethics by Jean Tricot (1983 edition), Jean Vrin publisher, pages 201, 225-226, 245-246, etc.  One can notice an effort to reduce the body text in order to let some space to footnotes. But this effort flaws on several pages ... A way had have been chosen by publishers : "don't abuse about footnotes !", which is clearly impossible within academic books in Humanities ... JP Le 04/03/2020 à 12:07, Philipp A. a écrit : > Hi Pablo, > > Thank you for the help! > I’m not using lists on that page … what I do use is a figure with > location=left, which is probably the culprit, as it ends up pretty > close to the footnote. > Is there any interest in fixing this longstanding bug? It’s the only > feature that’s just consistently broken for me … > > Best, Phil > > Am Di., 25. Feb. 2020 um 22:15 Uhr schrieb Pablo Rodriguez > >: > > On 2/18/20 11:17 AM, Philipp A. wrote: > > For me it’s even worse (in mkiv), a paragraph of body text > completely > > overlaps my footnote. > > > > Where are the bottom notes placed? In the footer? Or how does it > work? > > How to debug it? > > Hi Philipp, > > I’m afraid that this misbehaviour is caused by the use of lists in the > same page. > > Even not using lists, the space before seems not to be honored when > using \setupnote[footnote]. > > Note handling seems to have been improved in both LMTX and MkIV. A > side-effect of this new handling is the random clash between body and > notes texts when using lists in the same page. > > BTW, foonotes cannot be placed in the footer. > >     \showframe\showgrid >     \setuppapersize[A9] >     \starttext >     \dorecurse{3}{% >         text\footnote{note}\\} >     \stoptext > > Sorry, but I’m afraid that I don’t know any way of debugging it. > > Pablo > > > > Am Sa., 14. Dez. 2019 um 19:41 Uhr schrieb Pablo Rodriguez: > > > >     Dear list, > > > >     I’m afraid to admit that ConTeXt notes are increasily > problematic for > >     me. I don’t think this is special to me and I hope we can > discuss the > >     general issue. > > > >     Bottom notes are somewhat tricky in ConTeXt. The user > expects that these > >     notes (either footnotes, or linenotes) aren’t moved to the > next page. I > >     mean, no reader expects to find a full footnote in the next > page from > >     the one that calls it. (At least, I have never seen that in > any book > >     read or paged through.) > > > >     There may be good reasons for that, but ConTeXt doesn’t > enable this by > >     default. Both options "split=verystrict" and "scope=text" > have to be > >     used in "\setupnote". > > > >     This translated in wrong space before notes when paragraph > form was > >     used. I was very interested to use these (line)notes for > critical > >     editions, but sometimes the text run into the notes. I’m > afraid that > >     left linenotes extremely problematic to be used. > > > >     With the arrival of LMTX, space before footnotes is more > problematic > >     than before. No paragraph notes, see the attached sample > (wrong-6.png). > >     In other cases, ConTeXt seems to ignore totally that the > page bottom > >     contains footnotes. > > > >     I cannot provide minimal samples. Consider that if it were > so easy to > >     reproduce, problably the issue would have been gone long ago. > > > >     Even when one avoids the problematic bottom partition (which > I did in > >     that case by removing the "before" option from > "\setupnote[footnote]"), > >     there is clearly an issue with the footnote having its space > before > >     remaining blank from the body text (wrong-2.png). > > > >     My first question is why the bottom notes have problems to > preserve the > >     space before them (and simultaneously remain in the same > page where they > >     come from). This applies also for paragraph notes. > > > >     My second question is what can be improved to achieve what > may be > >     considered as a basic typographic feature. > > > >     Sorry for not providing more than output samples. Bear with > me. I may > >     not be an expert user, but I think I’m a frequent ConTeXt > user. And I > >     don’t think it is totally wrong to consider this a basic > feature that > >     needs to be improved. > > > >     Many thanks for your help in advance, > > > >     Pablo > > > > -- > http://www.ousia.tk > ___________________________________________________________________________________ > If your question is of interest to others as well, please add an > entry to the Wiki! > > maillist : ntg-context@ntg.nl / > http://www.ntg.nl/mailman/listinfo/ntg-context > webpage  : http://www.pragma-ade.nl / http://context.aanhet.net > archive  : https://bitbucket.org/phg/context-mirror/commits/ > wiki     : http://contextgarden.net > ___________________________________________________________________________________ > > > ___________________________________________________________________________________ > If your question is of interest to others as well, please add an entry to the Wiki! > > maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context > webpage : http://www.pragma-ade.nl / http://context.aanhet.net > archive : https://bitbucket.org/phg/context-mirror/commits/ > wiki : http://contextgarden.net > ___________________________________________________________________________________ --------------972D1F431E242A6A327112AD Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

Dear Pablo,

It seems that we never should say "never" about things which appear all over the real world. I just go back to a previous assertion you made here.

I agree with you about footnotes which should be placed on the same page (I quote) :

>    Bottom notes are somewhat tricky in ConTeXt. The user expects that these
>     notes (either footnotes, or linenotes) aren’t moved to the next page. I
>     mean, no reader expects to find a full footnote in the next page from
>     the one that calls it. (At least, I have never seen that in any book
>     read or paged through.)

But, I am afraid to inform you that it is a kind of way of French printing, especially in Philosophy publishers (which are not known to be devoted to publish beautiful/strictly edited/... books).

As a kind of sample, see the French translation of Nichomachean Ethics by Jean Tricot (1983 edition), Jean Vrin publisher, pages 201, 225-226, 245-246, etc.  One can notice an effort to reduce the body text in order to let some space to footnotes. But this effort flaws on several pages ...

A way had have been chosen by publishers : "don't abuse about footnotes !", which is clearly impossible within academic books in Humanities ...

JP


Le 04/03/2020 à 12:07, Philipp A. a écrit :
Hi Pablo,

Thank you for the help!
I’m not using lists on that page … what I do use is a figure with location=left, which is probably the culprit, as it ends up pretty close to the footnote.
Is there any interest in fixing this longstanding bug? It’s the only feature that’s just consistently broken for me …

Best, Phil

Am Di., 25. Feb. 2020 um 22:15 Uhr schrieb Pablo Rodriguez <oinos@gmx.es>:
On 2/18/20 11:17 AM, Philipp A. wrote:
> For me it’s even worse (in mkiv), a paragraph of body text completely
> overlaps my footnote.
>
> Where are the bottom notes placed? In the footer? Or how does it work?
> How to debug it?

Hi Philipp,

I’m afraid that this misbehaviour is caused by the use of lists in the
same page.

Even not using lists, the space before seems not to be honored when
using \setupnote[footnote].

Note handling seems to have been improved in both LMTX and MkIV. A
side-effect of this new handling is the random clash between body and
notes texts when using lists in the same page.

BTW, foonotes cannot be placed in the footer.

    \showframe\showgrid
    \setuppapersize[A9]
    \starttext
    \dorecurse{3}{%
        text\footnote{note}\\}
    \stoptext

Sorry, but I’m afraid that I don’t know any way of debugging it.

Pablo


> Am Sa., 14. Dez. 2019 um 19:41 Uhr schrieb Pablo Rodriguez:
>
>     Dear list,
>
>     I’m afraid to admit that ConTeXt notes are increasily problematic for
>     me. I don’t think this is special to me and I hope we can discuss the
>     general issue.
>
>     Bottom notes are somewhat tricky in ConTeXt. The user expects that these
>     notes (either footnotes, or linenotes) aren’t moved to the next page. I
>     mean, no reader expects to find a full footnote in the next page from
>     the one that calls it. (At least, I have never seen that in any book
>     read or paged through.)
>
>     There may be good reasons for that, but ConTeXt doesn’t enable this by
>     default. Both options "split=verystrict" and "scope=text" have to be
>     used in "\setupnote".
>
>     This translated in wrong space before notes when paragraph form was
>     used. I was very interested to use these (line)notes for critical
>     editions, but sometimes the text run into the notes. I’m afraid that
>     left linenotes extremely problematic to be used.
>
>     With the arrival of LMTX, space before footnotes is more problematic
>     than before. No paragraph notes, see the attached sample (wrong-6.png).
>     In other cases, ConTeXt seems to ignore totally that the page bottom
>     contains footnotes.
>
>     I cannot provide minimal samples. Consider that if it were so easy to
>     reproduce, problably the issue would have been gone long ago.
>
>     Even when one avoids the problematic bottom partition (which I did in
>     that case by removing the "before" option from "\setupnote[footnote]"),
>     there is clearly an issue with the footnote having its space before
>     remaining blank from the body text (wrong-2.png).
>
>     My first question is why the bottom notes have problems to preserve the
>     space before them (and simultaneously remain in the same page where they
>     come from). This applies also for paragraph notes.
>
>     My second question is what can be improved to achieve what may be
>     considered as a basic typographic feature.
>
>     Sorry for not providing more than output samples. Bear with me. I may
>     not be an expert user, but I think I’m a frequent ConTeXt user. And I
>     don’t think it is totally wrong to consider this a basic feature that
>     needs to be improved.
>
>     Many thanks for your help in advance,
>
>     Pablo



--
http://www.ousia.tk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________
--------------972D1F431E242A6A327112AD-- --===============5415904384554497463== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX18KSWYgeW91ciBxdWVzdGlvbiBpcyBvZiBpbnRlcmVz dCB0byBvdGhlcnMgYXMgd2VsbCwgcGxlYXNlIGFkZCBhbiBlbnRyeSB0byB0aGUgV2lraSEKCm1h aWxsaXN0IDogbnRnLWNvbnRleHRAbnRnLm5sIC8gaHR0cDovL3d3dy5udGcubmwvbWFpbG1hbi9s aXN0aW5mby9udGctY29udGV4dAp3ZWJwYWdlICA6IGh0dHA6Ly93d3cucHJhZ21hLWFkZS5ubCAv IGh0dHA6Ly9jb250ZXh0LmFhbmhldC5uZXQKYXJjaGl2ZSAgOiBodHRwczovL2JpdGJ1Y2tldC5v cmcvcGhnL2NvbnRleHQtbWlycm9yL2NvbW1pdHMvCndpa2kgICAgIDogaHR0cDovL2NvbnRleHRn YXJkZW4ubmV0Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCg== --===============5415904384554497463==--