From: Hans Hagen <pragma@wxs.nl>
To: massifr@fastwebnet.it,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: line break between number and footnote text in paragraph footnotes
Date: Fri, 03 Apr 2015 00:36:03 +0200 [thread overview]
Message-ID: <551DC453.9050407@wxs.nl> (raw)
In-Reply-To: <1428013899.10381.11.camel@fastwebnet.it>
On 4/3/2015 12:31 AM, mf wrote:
>> Hello,
>> I have a problem with paragraph footnotes. I don't know how to prevent a
>> line break occurring between the footnote number and the footnote text.
>> Sometimes a thing like this happens:
>>
>> ... [main text] ...
>>
>> --------------
>> 1. text of the first footnote --- 2. text of the second one --- 3.
>> text of the third one
>>
>> Is there a way to force ConTeXt to keep the "3." with "text of the third
>> one"?
>>
>> Thanks in advance,
>> Massi
> ...
>
>> \definenote[footnote]
>> \setupnotation[footnote][
>> alternative=serried,
>> numberstopper=,
>> numbercommand={\high},
>> numberconversion=a,
>> way=bypage,
>> width=0.5pt,
>> location=page]
>>
>> \setupnote[footnote][
>> alternative=serried,
>> paragraph=yes,
>> inbetween= \emdash{} ,
>> location=page,
>> before={\blank[2*line]}]
>>
>> \starttext
>> First footnote\footnote{this is the text of the first footnote}.
>> Another
>> one\footnote{the second one, longer to get to the right margin}.
>> And the third one,\footnote{third footnote} with the “c” letter
>> separated by a line break from the footnote text.
>> \stoptext
>
> I found a solution: adding a negative penalty at the end of the
> inbetween parameter:
>
> \setupnote[footnote][
> alternative=serried,
> paragraph=yes,
> inbetween= \emdash{} \penalty-1000,
> location=page,
> before={\blank[2*line]}]
>
> The footnotes' area was like this:
> ---------
> ^a this is the text of the first footnote --- ^b the second... --- ^c
> third footnote
>
> Now it is like this:
> ---------
> ^a this is the text of the first footnote --- ^b the second... ---
> ^c third footnote
>
> The first line ends with an em dash: it's not so fine, but it's better
> than a letter (footnote number) split from the text of the footnote by a
> line break.
it is already handled in the beta
--
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2015-04-02 22:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 22:15 mf
2015-04-01 0:06 ` Hans Hagen
2015-04-01 8:56 ` massifr
2015-04-02 22:31 ` mf
2015-04-02 22:36 ` Hans Hagen [this message]
2015-04-02 23:36 ` mf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=551DC453.9050407@wxs.nl \
--to=pragma@wxs.nl \
--cc=massifr@fastwebnet.it \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).