My project is structured as two levels. The folders represent chapters, and the sub-documents they contain are sections.
I use <$n> for the chapters and <$sn> for the sections.
Currently it looks like this which is fine:
I have tried the various compile formats, pored over the placeholder documentation and spend numerous hours trying to achieve the above format, but without success.
I am a software engineer by trade, have programmed using machine code, numerous compilers, C, C++, html, CSS, Javascript and many more… but I am defeated by this one.
I must be missing or overlooking something very simple
Rudi
Yeah, <$hn> is almost always what you want for a scenario like this, where you want clean and simple 1, 1.1, (and potentially 1.1.1, 1.1.1.1) hierarchical numbering. You only need one single token for every level.
In the case of using <$hn>, if the output doesn’t look quite as it should, it is the binder’s structure that needs to be better tuned. (Merge documents if needed.)
Does <$sn:chapter> reset on its own with each <$n:chapter> ?
If it doesn’t and you have to reset it yourself with the reset placeholder, then there is no real purpose to be using it as “sn”. Might as well create a new stream with a name that makes it easier to tell them apart.
Something like <$n:subchapter>.
You can create as many streams as you need, and the name doesn’t matter to the compiler. Could be <$n:scrivenerrocks>, and it would work just the same.
(I asked because some of the numbering placeholders don’t quite always do what is expected in the Windows version… I don’t remember exactly what, but I do recall there was an issue with resetting streams by use of the resetting prefix. <$rst_…>)
→ You have to use <$rst><$n:nameofthestreamthatyouwanttoreset>
Yeah. And some of the side experiments too, that ended up gravitating around it.
(And of which most is now comparable to a big mushy blur in my head, not having used any of it since.)