ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: methods for numbered paragraphs (ii)
Date: Tue, 8 Aug 2017 09:36:00 +0200	[thread overview]
Message-ID: <020f4ea1-087d-7ded-153c-45b03b9fec11@wxs.nl> (raw)
In-Reply-To: <c2f88251-1547-7fd0-295d-ff2ec8634c64@gmx.es>

On 8/7/2017 11:03 PM, Pablo Rodriguez wrote:
> On 08/07/2017 08:57 PM, Hans Hagen wrote:
>> On 8/7/2017 5:08 PM, Pablo Rodriguez wrote:
>>> [...]
>>> I mean, in a common sectioning structure a \subsubsection comes after a
>>> \subsection. But I don’t think it must be mandatory.
>>
>> Well, it's all on purpose ... no excuse for bad structuring
> 
> But even in that case, numbering from:
> 
>    \section{A}
>    \subsubsection{B}
> 
> gives:
> 
>    1 A
>    1 B
> 
> Should it be the following?
> 
>    1 A
>    1.1 B

no it would be 1 and 1.0.1 then

>> anyway, i'll support the criterium flag in sections too:
>>
>> \setuphead[subsection][criterium=all]
>>
>> and for sure i'll forget about it so I wonder who will document it ...
> 
> I have done it
> (http://wiki.contextgarden.net/Titles#Complete_Section_Numbering).
> 
> But Idris should review and improve it ;-).
> 
> Many thanks for the improvoement,
> 
> Pablo
> 


-- 

-----------------------------------------------------------------
                                           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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2017-08-08  7:36 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
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 [this message]
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=020f4ea1-087d-7ded-153c-45b03b9fec11@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).