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: Sat, 29 Jul 2017 19:10:32 +0200	[thread overview]
Message-ID: <f6cf6104-e496-c94f-a755-356eb381cc54@gmx.es> (raw)
In-Reply-To: <dd5e8654-de68-ad81-2f57-41d0cbc69ec4@rik.users.panix.com>

On 07/23/2017 09:48 PM, Rik Kabel wrote:
> The following example demonstrates two problems with
> alternative=margintext in \setuphead:
> 
>  1. When used with start/stop sectioning, text following the title may
>     be set on the wrong line.

Hi Rik,

the issue comes with \startparagraph and sectioning commands (other
margindata are fine):

    \setuphead
        [chapter]
        [alternative=margintext]
    \starttext
    \chapter{Chapter}
    \startparagraph\input jojomayer\stopparagraph
    \blank
    \inleft{marg}\startparagraph\input jojomayer\stopparagraph
    \blank
    \inright{marg}\startparagraph\input jojomayer\stopparagraph
    \blank
    \inouter{marg}\startparagraph\input jojomayer\stopparagraph
    \ininner{marg}\startparagraph\input jojomayer\stopparagraph
    \blank
    \inmargin{marg}\startparagraph\input jojomayer\stopparagraph
    \blank
    \inother{marg}\startparagraph\input jojomayer\stopparagraph
    \stoptext

But \inmargin has no problem with margin
>  2. Without regard to the type of sectioning, margintext titles may
>     spill over the left edge of the margin and beyond the page frame.

I cannot align them either. I don’t know what we may be missing here.

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
___________________________________________________________________________________

  parent reply	other threads:[~2017-07-29 17:10 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 ` Pablo Rodriguez [this message]
2017-07-29 17:34   ` Problems with heads " 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
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=f6cf6104-e496-c94f-a755-356eb381cc54@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).