🚀 go-pugleaf

The easiest way do to it would be to do a S&R or a short FrameScript that removes the soft returns from the TOC, I think.

But in general, the TOC pulls whatever the tag content is.

You could do a work-around with a set of two tags in the component file that replace the single tag w/ soft return, but that may create more problems later...

Katherine,

I think you can set your autonumber to <$chapnum>\r. The \r is a forced (soft) return. I think this will give you the line break in your Heading1.

In the reference page for the TOC, set the relevant line to be

<$chapnum> <$paratext>

The paratext building block copies the text of the paragraph without the autonumbering. Note that in the above for the TOC, you can put anything you want between chapnum and paratext, such as an en dash; I just put a space.

I have not tested this, so it may not work as I think it should.

Good luck,
Van

Thanks Art and Van.

The \r solutiuon would be best, as it is a template that I'm distibuting to other authors. I'd like to avoid the need for them to do anything manually if possible, such as a S&R.

Unfortunately though \r doesn't seem to work - it isn't forcing the new line in the chapter heading. Is that definitely the correct syntax for a soft return?

Thanks again,

Kat

Katherine,

FM does not allow any kind of return in the auto-number component.

You would need to set-up two paratags for this. The first one to do
the autonumber [h1_num] and the second one for the heading text [h1].
Have the first one for the autonumber set the Next Pgf Tag to the [h1]
heading one, so that all that is needed is to hit Enter after
inserting the h1 tag to start entering the heading text.

In the TOC, to get both on the same line, use this type of construct
for the h1 tag:

 <$paranumonly[h1_num]> - <$paratext> <$pagenum>

and do *not* include the h1_num tag in the TOC list of tags. 

The <$paranumonly[h1_num]> building block, in the h1 entry on the TOC
reference page, will tell FM to search backward for the first match in
the source document, which will be the correct autonumber value (one
paragraph prior).

Arnis is likely correct about not allowing returns in autonumbers. I was confused. I use structured Frame, which allow a soft return in the prefix of a paragraph. Prefixes are something that is in structured Frame but not unstructured, as far as I know.

Sorry for the confusion.

Van

Thanks Arnis, I will go with the two paragraph formats for the chapter headings.

Thanks for all the advice everyone and no problem at all Van, I just appreciate all the replies.

Kat

Hi again,

I don't know if anyone will read this now it's an old topic, but I've come across a problem with using the 2 paragraph formats for chapter headings. Ultimately I will be saving the book as a PDF, so I need to generate bookmarks from the paragraph tags. I need both the chapter name and number to be in the bookmarks, so does that mean I can't use two separate paragraph formats?

If I can't, is there another way to solve the original problem of wanting the chapter name on the line below the chapter number, but not using any formatting that would also be pulled through to the TOC.

Thanks,

Kat

Kat,

You can use Shlomo Perets' Timesavers to set up the PDF bookmarks any
way you want, see http://www.microtype.com/timesavers.html and
http://www.microtype.com/ImprovePDF.html This tool will allow you to
set things up at the FM end to  merge the two separate chapter
bookmarks onto a single line (see MergeBookmarks option).

However, do you really need to have the Chapter number in an
interactive document? With formatting (both font and colour) available
for the bookmarks (via Timesavers) the hierarchy can be made extremely
visible. Either way, it should work for you.

If you also are using chapter-page numbering on your pages, then Rick
Quatro's PageLabeler plug-in (see
http://www.frameexpert.com/plugins/pagelabeler/index.htm) can preserve
this numbering in the PDF pagenumbering display (i.e. the page numbers
match the displayed numbers, not the just absolute page sequence
numbers).

There's usually always a workaround, albeit you may need a third-party
tool for this. If you're creating lots of interactive PDFs, then I
highly recommend that you take a good serious look at Timesavers.