ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: Problems with heads using margintext alternative
Date: Sun, 30 Jul 2017 09:30:41 +0200	[thread overview]
Message-ID: <6a391611-8aae-aeea-8546-8cde34148f56@gmx.es> (raw)
In-Reply-To: <93d4b09d-a794-35f1-78c1-7df13471f52e@wxs.nl>

On 07/29/2017 11:44 PM, Hans Hagen wrote:
> On 7/29/2017 7:34 PM, Rik wrote:
>> Indeed, the extra line before the text occurs only when inter-paragraph 
>> whitespace is set and start/stop is used. This does indeed appear to be 
>> something that can be repaired.
> to some extend ... i added some hack in the upcoming beta btu keep in 
> mind that a section head carries some information so there's always 
> something (invisible) there that can generate whitespace

Many thanks for this fix and the one with itlc and ligatures, Hans.

I’m afraid I’m not able to align text in margin data:

    \setuphead
        [chapter]
        [style=\tfxx,
         number=no,
         alternative=margintext,
         align=middle]
    \setupmargindata
        [inmargin]
        [style=\tfxx,
         align=middle]
    \starttext
    \chapter{Chapter}
    \input jojomayer
    \blank
    \inmargin{marginal\\data\blank}\input jojomayer
    \stoptext

Is this a bug or am I missing something?

Many thanks for your help,

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
___________________________________________________________________________________

  reply	other threads:[~2017-07-30  7:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-23 19:48 Problems with headers " Rik Kabel
2017-07-29 14:52 ` Rik
2017-07-29 16:18   ` Willi Egger
2017-07-29 17:10 ` Problems with heads " Pablo Rodriguez
2017-07-29 17:34   ` Rik
2017-07-29 18:18     ` Pablo Rodriguez
2017-07-29 18:40       ` Rik Kabel
2017-07-29 21:44     ` Hans Hagen
2017-07-30  7:30       ` Pablo Rodriguez [this message]
2017-07-30 13:38         ` Hans Hagen

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=6a391611-8aae-aeea-8546-8cde34148f56@gmx.es \
    --to=oinos@gmx.es \
    --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).