ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Duncan Hothersall via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Duncan Hothersall <dh@capdm.com>
Subject: Re: numbering questions
Date: Sat, 31 Dec 2022 18:20:20 +0000	[thread overview]
Message-ID: <CAN8fp9We79cqdJoXAGcwHaazDOJBzHqYJfYgTe6y=dbAQVHksg@mail.gmail.com> (raw)
In-Reply-To: <18f2f823-ac76-e606-9f66-7990f586a966@fiee.net>


[-- Attachment #1.1: Type: text/plain, Size: 2338 bytes --]

I can't test right now but would something like

\setuphead[Day][sectionsegments=Day:Month:Year]

help?

Duncan


On Sat, 31 Dec 2022 at 17:24, Henning Hraban Ramm via ntg-context <
ntg-context@ntg.nl> wrote:

> A happy new year to everyone!
>
> I’m playing with some examples of section numbering.
>
> * Is there a setup to influence the order of number segments? I.e. can I
> have “section.chapter.part“ instead of “part.chapter.section”?
>
> * How can I format the segments, e.g. to get two or three digits each
> (leading zeros)?
>
> * I can force a section number with “ownnumber”, but the next one is
> back in the previous scheme. Itemize has “start”. How can I start
> section chapter numbering at 3 (or -1 or whatever; I know I can start at
> 0 with “zero”) and let ConTeXt continue from there?
>
>
> My example tries to (ab)use the section numbering for a date (e.g. for a
> diary):
>
> -----
> \definestructureconversionset[default][n,n,month,n][n]
> \definestructureseparatorset [default][-,-,-,-]
>
> \definehead[Year][chapter]
> \definehead[Month][section]
> \definehead[Day][subsection]
>
> \define[2]\TitleCmd{#1} % number only
>
> \setuphead[Year,Month,Day][number=yes,page=no,command=\TitleCmd]
> \setuphead[Year][page=yes]
> %\setuphead[Month][]
> \setuphead[Day][style={\ss\bf}]
>
> \def\Dummycontent{
>      \dorecurse{12}{
>      \startMonth
>      New Month.
>
>      \dorecurse{5}{
>      \startDay
>      Another day.
>
>      \stopDay
>      }
>
>      \stopMonth
> }}
>
> \starttext
>
> \startYear[ownnumber=2023,title=This]
> A new year begins.
>
> \Dummycontent
>
> \stopYear
>
> \startYear
> Next year.
>
> \Dummycontent
>
> \stopYear
>
> \stoptext
> -----
>
> Hraban
>
>
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to
> the Wiki!
>
> maillist : ntg-context@ntg.nl /
> https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki     : https://contextgarden.net
>
> ___________________________________________________________________________________
>

[-- Attachment #1.2: Type: text/html, Size: 3413 bytes --]

[-- Attachment #2: Type: text/plain, Size: 496 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2022-12-31 18:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-31 17:23 Henning Hraban Ramm via ntg-context
2022-12-31 18:20 ` Duncan Hothersall via ntg-context [this message]
2022-12-31 19:36   ` Henning Hraban Ramm via ntg-context
2022-12-31 19:41 ` Pablo Rodriguez via ntg-context
2022-12-31 21:07   ` Henning Hraban Ramm via ntg-context
2023-01-01 10:27 ` Wolfgang Schuster via ntg-context
2023-01-01 13:13   ` Henning Hraban Ramm via ntg-context

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='CAN8fp9We79cqdJoXAGcwHaazDOJBzHqYJfYgTe6y=dbAQVHksg@mail.gmail.com' \
    --to=ntg-context@ntg.nl \
    --cc=dh@capdm.com \
    /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).