ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: two suggestions for \setuphead
Date: Thu, 23 Mar 2017 20:45:57 +0100	[thread overview]
Message-ID: <c81d1ac4-702b-d7c7-eda4-fe4f96b78187@gmx.es> (raw)
In-Reply-To: <fd0367aa-0572-dc9b-95b3-4d532a478e95@wxs.nl>

On 03/22/2017 10:13 PM, Hans Hagen wrote:
> On 3/15/2017 8:59 PM, Pablo Rodriguez wrote:
>> [...]
>> Would it be possible in this case to set both numberalign and textalign?
>> (If no margin or inmargin alternative is selected and both numberalign
>> and textalign are specified, textalign should have preference)
>>
>> I think those two suggestions would provide extra features for headings.
>>
>> How about implementing both in ConTeXt?
> 
> i have no clue what you mean

Sorry for not being clear, Hans. I have two different proposals.

The first one is about aligning titles and numbers (separately):

    \showframe
    %~ \setuphead[section][alternative=inmargin, align=center]
    \setuphead[section][alternative=inmargin]
    \setuphead[subsection][alternative=margin]
    \setuppagenumbering[alternative=doublesided]
    \starttext
        \dorecurse{5}{\section{Section title}
            \dorecurse{5}{\subsection{Subsection title}}}
    \stoptext

Using align, the margin or inmargin alternative doesn’t work. (And align
doesn’t work with the margintext alternative.)

Wouldn’t it be possible to set up both alignments, for numbers in margin
and for title inside margins?

My second proposal is to be able to specify which margin (inner, outer,
left or right) is used for both margin/inmargin and margintext
alternatives in \setuphead.

I mean, either I’m missing something, or the alternatives
margin/inmargin and margintext are set to the left margin. It seems to
be no other option.

Would it be possible to implement both proposals in ConTeXt?

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-03-23 19:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-15 19:59 Pablo Rodriguez
2017-03-22 21:13 ` Hans Hagen
2017-03-23 19:45   ` Pablo Rodriguez [this message]
2017-03-26 14:11     ` Hans Hagen
2017-03-26 20:09       ` Pablo Rodriguez
2017-03-26 20:20         ` Wolfgang Schuster
2017-03-26 20:41           ` Pablo Rodriguez
2017-03-27 13:57           ` Pablo Rodriguez
2017-03-27 15:22             ` Hans Hagen
2017-03-27 18:00               ` Pablo Rodriguez
2017-03-27 19:29                 ` Hans Hagen
2017-03-27 19:49                   ` Pablo Rodriguez
2017-03-27 20:15                     ` Hans Hagen
2017-03-28 17:14                       ` 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=c81d1ac4-702b-d7c7-eda4-fe4f96b78187@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).