Dynamic toc that populates page numbers in word [creating question marks instead]

Check your compile format.

You’ll see something like
Chapter <$n> (Which gives Chapter 1)
And Chapter <$W> or <$w> (Which gives Chapter ONE or one)

Choose which one you want (ONE TWO THREE or 1 2 3) and replace the other with the chosen one.

1 Like

oooh this looks v promising – how do I access the screenshot you show above

Double click the compile format you compile with in the compile panel’s first column.

But in this case, you’ll most likely find not two, but one placeholder.
I guess you manually wrote a few numbers yourself in your documents’ titles.

Should you have been the one to use two different placeholders, you’d know how to access the compile format’s settings already. :wink:


so I’m still. getting this – trying to get a screen shot of the compiler options that populate for me they look different form yours

That’s Word. That’s why. (Else, if that’s not what you meant, I run the windows version. But nevermind the looks, it is the same.)
. . . . . . . . .

My screenshot is of Scrivener.

Chapter 15. Have a look at it (in Scrivener), see what you did different than with the other chapters.
(It is probably assigned to a different section TYPE in the metadata panel of your project – that’s in the inspector on the right).
My guess is that the “15” is from you, and the corresponding document is routed to a section type/layout that doesn’t overwrite it, unlike for the others.

Or you are set for section types to be automatic, and this document isn’t on the same level. Or is a file when it should be a folder. Or vice versa.
Find what is different.

1 Like

The way to tackle the number vs number as a word is to go back to Scrivener and check your Table of Contents document. It serves no purpose tacking it from Word if your source is incorrect.
It should consistently look like this (just with different listed items):

2 Likes

here’s how my metadata is set up – anything here explain things to you?


soil my toc in scrivener looks like this how do I tweak it to look like the example you sent


also – this is how I set up the metadata could it somehow be contributing to the Chapter One vs Chapter 1? I think I may have manually written in some chapter numbers?

A few observations first.

  1. Your focus is on Part number in the first of your latest slides. I can’t tell you what’s going on with your Chapters if your focus is not on Chapters.
  2. You have a “Chapter Title” Layout name with Title ticked. I assume you haven’t assigned this to a Section Type because it is not highlighted in bold text. Furthermore, I see your Chapters are called Chapter 1 to whatever, using a number. If this option were assigned to a Section Type, the placeholder “Section Title” would appear Compile Format Designer > Layout Name > Formatting tab and your Chapter Titles Chapter 1, etc. would appear as the title of each chapter and the TOC would read it as such too.
  3. The presumption is therefore that in the Layout name Chapter, you have the following placeholder in the Title Options tab: Chapter <$w>, which would render as Chapter One, etc.
  4. No problem with that. It’s one way of giving you what you prefer.

@liseygwrites

Read carefully.
You have typed the numbering of your chapters manually in the binder. I can see it in your screenshot.
Chapter 15 (and whichever others don’t compile right) is/are assigned the wrong section type in the metadata panel of the inspector.

image

Set it/them to route to the same one (section type) as the chapters that compile right.

And if you did so on purpose – which I doubt, given that yesterday you asked how to access this – because you want them chapters to compile the text with a different formatting, then leave it as it is, but set the Title Options of the corresponding layout to match the Title Options of the layout of your OK chapters, in your compile format.

Perhaps read this one post again, as a complement.

1 Like

A few comments about the second of your latest scans.

  1. Your Table of Contents document in Scrivener shows Chapter 1, etc. yet rendered as Chapter One in Word. Did you later change the number to words manually in Word, because compile wouldn’t do such a thing, unless Mac has a fangled setting that does such things.
  2. In your screen capture of your Word document, you have two errors. There’s a full-stop before Chapter Fourteen and Chapter 15 is a number, not a word. A placeholder can’t interchange itself, but a user can make an error - we all do.
  3. Check your Scrivener TOC for what’s going on around Chapter 14 and 15. Then Check the Word document for the same. If Scrivener is right, compile again and the errors would not be present in the new compile. If the error is in the Word document, then delete the errant full-stop there and the manual overtype of a number replacing a word.
  4. I work in centimetres, you probably work in inches.
  5. Turn on your ruler in Scrivener (in Windows it’s Alt+Shift+R; on Mac it’s probably Option+Shift+R, I don’t know for sure.)
  6. Still in the Scrivener TOC document with the Ruler on, drag your mouse over the TOC text and right click on the ruler and set a right tab at about 6.1 inches (that’s 15.6 cm for me). The page placeholder <$p> should now be on the same line as the Chapter Number and will render as such in Word or PDF reader. It may not in Scrivener, if you have not allocated sufficient editor width and your right indent marker is before the 6.1 inches mark. I note your Binder is particularly wide.
  7. I don’t know where to turn on the TOC grid lines. Maybe it has some other oblique name that eludes me at this time.
  8. You turn off the blue underline by selecting Scrivener Settings > Appearance > Textual Marks > Options and untick Underline Links. Click on the Colors tab next to Options and select Links and Change the colour to what you want it to be.

It sure can.
. . . . . . . .

You’re right. Because in this case a placeholder would have been used since the Chapter Layout was used, not Chapter Title. My bad.

2 Likes

More that the section layout that comes out right has the title box unchecked, and “Chapter” + the number – <$w> – comes from either the title’s prefix or suffix in the Title Options of the layout used by the majority of the chapters in this one case.

Which is why I am saying that Chapter 15 is assigned to the wrong section type. Ending up going through a section layout that doesn’t overwrite the document’s title.

thank you for all your help!


it looks to me like I have the same metadata in the inspector for chapters one and fifteen, yet chapter 15 populates with a number ( 15 vs fifteen) unless you’re seeing something I’m missing? so if this is not where the issue is, I suppose I should look at the compile settings?

I am baffled. I don’t know.
. . . . . . . . . .
Something is really off.

You should compile to RTF and reimport that compile in a blank dummy project. Rule out the compile process.
. . . . . .

You could also replace “Chapter 15” (the doc’s title) with “TEST” in the binder, and see if it’ll come out has TEST or Chapter 15.

We are currently in the realm of the supernatural.

Some other ideas:
– Run the Zap Gremlins function. (Somewhere under the Edit menu.)

– Uncheck Chapter one and two from compile, and see if it is chapter 17 that will come out wrong.

– Move Chapter 15 up or down the binder, see if it’ll still compile wrong.

. . . . . . . . . . .
Do not ignore @Kevitec57’s angle on the question.

I had a similar ‘bafflement’

Have you checked the tabs “suffix” and “prefix” in your compile menu? That’s where my errant code was hiding.

As seen in this screenshot, bottom right. This image has title options tab selected. The suffix & prefix tabs are to the right…

But how would it cause the OP’s chapter 14 and 15 listing to go Harry Bonkers?
I think befiddlement.

I don’t know, but in my case, the code that was in the prefix/suffix tabs overrode my other settings.

fwiw, I was trying to tweak a copy of a special template for numbering that had code in those tabs that I was unaware of. The end results was odd numbering until I deleted that code.