ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: jbf <roma83537@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: roman numerals frontpart
Date: Wed, 26 Jun 2024 11:43:31 +1000	[thread overview]
Message-ID: <227dd7db-d602-4f10-a736-40c8dce29847@gmail.com> (raw)
In-Reply-To: <17f8ff90-4cc6-492d-9e10-0cfddb733517@gmail.com>


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

I have found the problem, but am still seeking a little help:

I had created a setup to raise the page number in the footer. Calling 
this setup resulted in the frontpart pages reverting to arabic instead 
of roman:

\startsetups pnfooter

\setuppagenumbering[alternative=doublesided,location=]

\setupfooter

   [style=normal]

   \setupfootertexts

   [{\framed[width=max,frame=off,boffset=2mm]{\pagenumber}}]

\stopsetups

How can I continue to use the setup but still get my roman numerals in 
the frontpart?
Julian

On 26/6/24 10:52, jbf wrote:
>
> Something that has worked for me in the past is not working for me at 
> the moment, and I cannot figure out why:
>
> \startsectionblockenvironment [frontpart]
> \setupuserpagenumber [numberconversion=romannumerals]
> \setcounter [userpage] [5]
> \stopsectionblockenvironment
> \startsectionblockenvironment [bodypart]
> \setcounter [userpage] [1]
> \stopsectionblockenvironment
>
> gives me roman numerals in the TOC but not on the frontmatter pages, 
> which are arabic. Bodymatter is okay. What could I possibly be doing 
> wrong?
>
> Even with a different setup I get the same result:
>
> \definestructureconversionset [frontpart:pagenumber] [] [romannumerals]
> \setupheads[title][sectionconversionset=section]
> \startsectionblockenvironment[frontpart]
> \setupuserpagenumber[numberconversion=romannumerals]
> \setuppagenumber[number=1]
> \stopsectionblockenvironment
>
> Puzzling (for me at least).
>
> Julian
>

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

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

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

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2024-06-26  1:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26  0:52 [NTG-context] " jbf
2024-06-26  1:43 ` jbf [this message]

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=227dd7db-d602-4f10-a736-40c8dce29847@gmail.com \
    --to=roma83537@gmail.com \
    --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).