ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Joel via ntg-context <ntg-context@ntg.nl>
To: Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>
Cc: Joel <uaru99@yahoo.com>
Subject: Re: How to create an index that refers to multiple other books?
Date: Wed, 19 Jan 2022 02:17:55 +0000 (UTC)	[thread overview]
Message-ID: <224865198.941964.1642558675055@mail.yahoo.com> (raw)
In-Reply-To: <d0983bdf-108e-cb35-6895-3fb90acc98f6@fiee.net>


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

 I tried adding 'pageprefixsegments' to setupregister, but cannot find any value that adds anything, ex. pageprefixsegments={WB1}
pageprefixsegments=part:number

How does it work? I'd be fine if the index listed pages like "WB1 3" meaning "Workbook 1, page 3", it isn't ideal but is better than not having the index showing anything.

--Joel


    On Tuesday, January 18, 2022, 07:41:15 AM MST, Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl> wrote:  
 
 Am 18.01.22 um 14:27 schrieb Joel via ntg-context:
> One possible solution I see, since the textbooks and workbooks share the 
> same macros, formatting, fonts, etc. is to just render them as a single 
> file, resetting the page number at the start of each new book, then 
> later use pdfjam to split the files, but I'm not sure how the index 
> could tell readers which of the five "page 5's" (for example) the index 
> is referring to. --Joel

In this case, you could use \part per workbook and use 
pageprefixsegments in \setupregister to add the part number in front of 
the page number.

Otherwise, I guess it would be possible to read the .tuc files of the 
other products to create index entries. (Some Lua programming; shouldn’t 
bee too hard, but still way over my head.)

Hraban
___________________________________________________________________________________
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
___________________________________________________________________________________
  

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

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

___________________________________________________________________________________
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:[~2022-01-19  2:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <83836089.771099.1642511796159.ref@mail.yahoo.com>
2022-01-18 13:16 ` Joel via ntg-context
2022-01-18 13:27   ` Joel via ntg-context
2022-01-18 14:39     ` Henning Hraban Ramm via ntg-context
2022-01-19  2:17       ` Joel via ntg-context [this message]
2022-01-18 18:26   ` Hans Hagen 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=224865198.941964.1642558675055@mail.yahoo.com \
    --to=ntg-context@ntg.nl \
    --cc=uaru99@yahoo.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).