ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Steffen Wolfrum <context@st.estfiles.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <pragma@wxs.nl>
Subject: Re: [***NOSPAM***] \setbreakpoints[compound] does not work
Date: Sun, 25 Mar 2012 18:49:36 +0200	[thread overview]
Message-ID: <0B7F6747-F456-494E-A440-61E6155E265D@st.estfiles.de> (raw)
In-Reply-To: <4F6F342A.9030005@wxs.nl>


Am 25.03.2012 um 17:05 schrieb Hans Hagen:

> On 25-3-2012 13:34, Steffen Wolfrum wrote:
>> \showframe
>> \mainlanguage[de]
>> \setbreakpoints[compound]
>> 
>> \setnumber[footnote][114]
>> 
>> \starttext
>> 
>> test
>> {\startfootnote[ftn115]
>> siehe Schlussbericht der zuständigen Bund-Länder-Arbeitsgruppe „Verkehrsverlagerungen info Lkw-Maut“, BT-Dr16/298 v.~13.\,12.\,2005, 2, 3.
>> \stopfootnote}.
>> 
>> \stoptext
> 
> It's something that is still not settled: what to reset when page building happens cq. we're in 'forget' mode. Anyhow, we can (stepwise) make some features global:
> 
> in typo-brk.mkiv:
> 
> \definesystemattribute[breakpoint][public,global]


thanks for this fast help!

st.
___________________________________________________________________________________
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
___________________________________________________________________________________


      reply	other threads:[~2012-03-25 16:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-25 11:34 [***SPAM***] " Steffen Wolfrum
2012-03-25 15:05 ` Hans Hagen
2012-03-25 16:49   ` Steffen Wolfrum [this message]

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=0B7F6747-F456-494E-A440-61E6155E265D@st.estfiles.de \
    --to=context@st.estfiles.de \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).