From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: \setupalign (protrusion and expansion) in notes
Date: Sat, 30 Jul 2016 00:01:17 +0200 [thread overview]
Message-ID: <dbf9f373-93ec-25d5-3b3e-60b0ac9f19d7@wxs.nl> (raw)
In-Reply-To: <014ddb7a-db6c-8076-eb0d-761c7789d324@gmx.es>
On 7/29/2016 10:32 PM, Pablo Rodriguez wrote:
> Hans,
>
> I have the following sample:
>
> \definefontfeature
> [default]
> [default]
> [expansion=quality,
> protrusion=quality]
>
> \setupalign
> [hanging, hz]
>
> \starttext
> \input knuth\footnote{\input knuth}
> \stoptext
>
> Notes don’t inherit by default the \setupalign values.
>
> Wouldn’t it make sense that they share the same align values than the
> main text, unless other values are specified for notes?
notes really are a separate stream (and also kind of asynchronous ...
what if you change the alignment temporary and a page break occurs in
between
the same for headers and footers
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
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2016-07-29 22:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 20:32 Pablo Rodriguez
2016-07-29 22:01 ` Hans Hagen [this message]
2016-07-30 6:50 ` Pablo Rodriguez
[not found] ` <579c600a.915c1c0a.fee4a.34d9@mx.google.com>
2016-07-30 11:07 ` Pablo Rodriguez
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=dbf9f373-93ec-25d5-3b3e-60b0ac9f19d7@wxs.nl \
--to=pragma@wxs.nl \
--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).