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: methods for numbered paragraphs (ii)
Date: Mon, 7 Aug 2017 17:08:11 +0200	[thread overview]
Message-ID: <00773d66-b7ae-02f6-086e-b7c70b618327@gmx.es> (raw)
In-Reply-To: <op.y4kichviejo439@desktop-mt1m160>

On 08/06/2017 11:08 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:
> [...]
> Challenges:
> 
> 1. How can we get automatic indentation for all heads *except* the first  
> one that occurs after the \starttitle?

Hi Idris,

this should be the default (it is actually \setupheads[indentnext=no]).

I think there is a bug here, because \setuphead[alternative=margintext]
prevents "indentnext=no" from working.

You might use "insidesection=\noindenting", but this only works if you
don’t use \starpar...\stoppar. And this is only a workaround.

> 2. Look at the output of the adjusted version above - attached. Note that  
> a subsubsection after a section gives
> 
> 1.1
> 2.1
> 
> which are the same as those given by a subsection after a section. How can  
> we get a subsubsection after a section to produce the following?
> 
> 1.0.1
> 2.0.1

Again, I would say this is a bug in numbering:

    \starttext
    \section{A}
    %~ \subsection{B}
    \subsubsection{C}
    \stoptext

I mean, in a common sectioning structure a \subsubsection comes after a
\subsection. But I don’t think it must be mandatory.

Sorry for not being of much 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-08-07 15:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-05 20:08 Idris Samawi Hamid ادريس سماوي حامد
2017-08-06  3:28 ` Idris Samawi Hamid ادريس سماوي حامد
2017-08-06 13:54   ` Idris Samawi Hamid ادريس سماوي حامد
2017-08-06 19:39     ` Pablo Rodriguez
2017-08-06 21:08       ` Idris Samawi Hamid ادريس سماوي حامد
2017-08-07 15:08         ` Pablo Rodriguez [this message]
2017-08-07 18:57           ` Hans Hagen
2017-08-07 21:03             ` Pablo Rodriguez
2017-08-07 22:37               ` Idris Samawi Hamid ادريس سماوي حامد
2017-08-08  7:36               ` Hans Hagen
2017-08-08 12:42                 ` Idris Samawi Hamid ادريس سماوي حامد
2017-08-08 16:00                   ` Pablo Rodriguez
2017-08-08 20:43                 ` Pablo Rodriguez
2017-08-09  7:58                   ` Hans Hagen
2017-08-06 19:49     ` Pablo Rodriguez
2017-08-06 21:14       ` Idris Samawi Hamid ادريس سماوي حامد

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=00773d66-b7ae-02f6-086e-b7c70b618327@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).