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 no
On 1/18/2022 2:16 PM, Joel via ntg-context wrote:
I am writing a secondary textbook to be used in public schools. In my
state, the textbooks must adhere to standards, such as the Common Core
State Standards (CCSS). It is typical for a textbook to contain an index
for teachers to check where in
On Sun, 16 Jan 2022 16:53:16 +0100
Marco Patzer via ntg-context wrote:
> Still an issue with 2022.01.15 17:29.
Fixed as of 2022.01.18 10:48. Thanks Hans.
Marco
___
If your question is of interest to others as well,
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 f
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 rea
I am writing a secondary textbook to be used in public schools. In my state,
the textbooks must adhere to standards, such as the Common Core State Standards
(CCSS). It is typical for a textbook to contain an index for teachers to check
where in the textbook which standards are used. I've used th
Hi Hans,
Some time ago I reported about an issue with \definemathcommand, and the issue
is still present, as one can see with following example.
Best regards: Otared
% begin liminf-Argmin.tex
\setupbodyfont[lucidaot]
%\setupbodyfont[termes]
\definemathcommand [Argmin] [limop] {\mfunctionlabel
Hi,
a new lmtx upload
- crash with bottom floats probably solved: had to do with tricky
interaction between engine insert handling and callback interference (as
well as some assumptions in the engine dating that relate to the fact
that tex was never written to be opened up this way)
- crash
Hi Hans and Aditya,
Thanks for the clarification. Since for some documents I still use mkiv, I
ended up using a definition which depends on whether one is using mkiv or lmtx,
as in the example below. I wonder if there is a better solution.
Best regards: Otared
% begin bug-aligned-solved.tex
\do