Setting Up Custom Script Format for Glossary/Index

Hey I thought I might set up a custom Script Format under Script Settings so that I could automatically format my Glossary and Index entries as I work in a Non-Fiction book project.

But I’ve opened a can of worms to say the least. I really am not getting consistent behavior from my settings no matter what I try.

Are there bugs and problems with this Scrivener Script format definition functionality?

Specifically I thought I would set up a Script Style that had the following elements:

  1. Type (Prefaced with "Type: " and with text completion menu for the following words: who, what, where, when, why, way)
  2. Title (prefaced with "Title: ")
  3. Place and Date (prefaced with "Place: , Date: ")
  4. Description (prefaced with “Description:”)
  5. See Also (prefaced with "See also: ")
  6. Index List (prefaced with "Index: ")

Each of these items would have specific font and formatting. Some would be automatically populated with a specific prefix text string ("See also: " for example). And all would have automatic responce to tab and or return key input that would go to and start the next element.

The format I am after looks like this:

PS: Any suggestions or video tutorial? I have read through all of the documentation on this topic and watched the short segment in the Script Writing vid on the L&L website.

What I’ve done so far is set up the elements, and set the options for the elements (best I know how), but I am experiencing strange and unpredictable behavior.

What I would like to do is have Scrivener respond to tab or return by bringing up the next element, and in some cases, I’d like that element to be prefixed by a string of predetermined text (like "Date: " or "See also: " or "Index: ". Any way to do this? Make it reliable? Any way to visually know what element I am currently typing within?

Thanks, Randall

I am a windows user, but if have special pages with special formatting like a glossary, the simplest way to maintain the appearance, is to put these documents in your back matter folder and create a section type called Front or Back Matter (or really any name) and assign to these files with special formatting.
When you compile, then in the use the Section Layout as-is on them which preserves the formatting and assign the Section Layout to the Front/Back Matter section type. If you do it correctly it will look something like this (again in Windows)

My interest is not about compiled output but customizing the writing environment, the place where I write and think and create.

Simple problem. I want to create a custom script format where there are just two “Elements” (Title and Content). The Title element I want to be in all caps and in a grey color, and to end in a colon follow by a space when the user presses the tab key. Pressing the tab key while in the Title element should then switch to the Content element (on same line) where the font should be standard text (not all caps), larger, and in black color.

I have set my two elements up in Script Settings. I have set everything up as described above. But even though I have set up the Title element to first insert a colon and space char and then to switch to the Content element after a tab key press, it never switches to the content element despite properly inserting the colon and space chars after a tab key.

Desired Finished Product Example:

What I get instead is text all in the Title element style I have defined, and never transitioning to the Content element style I have also defined. What am I doing wrong? Why doesn’t it work?

Settings for the Title element…

Merged with your existing thread on this topic.

Really? Nobody knows how to help me with this? I am doing it exactly as the user manual says to do it. Have I missed something?

If you’re in script mode, the current element is shown at the bottom right of the Editor pane. So that’s the first thing to check: is Scrivener switching between elements as you expect it to?

There’s also a menu to cycle between elements in the bottom right of the Editor. So even if Scrivener isn’t switching correctly, you can use that menu to determine whether the elements individually behave as desired.

2 Likes