Very Computer

The help says to use a non-breaking space for a generated list so as not to
have a line number sitting on a line by itself.

But I'm using a tab for my TOC instead of a space. Is there a way?
--
Malcolm
in Toronto

If you have the problem of a long line forcing the page number to the left
side of the next line, place an extra tab between whatever is at the right
end of the heading and the left side of the page number.  So instead of

<$paratext> \t <$pagenum>

you use

<$paratext> \t \t <$pagenum>

Quote:>place an extra tab between whatever is at the right
>end of the heading and the left side of the page number

No change. Got another internal error though. Thanks, Tim.
--
Malcolm
in Toronto

At what point did you get the error?  Entering the tab? Doing the generate?
And if you got an error, how did you know there was no change?

Quote:>At what point did you get the error?  Entering the tab? Doing the generate?

Actually I got the error first.

Quote:>And if you got an error, how did you know there was no change?

With two tabs in place, after the generate, I had the text symbols showing
and it was as before, with the page number alone on the line but this time
with a tab marker in front of it.
--
Malcolm
in Toronto

Would your right tab just happen to be a hair to the right of the actual
right margin?

Quote:>Would your right tab just happen to be a hair to the right of the actual
>right margin?

Nope. I tend to do stuff by explicitly typing the numbers rather than
eyeballing. Both are 3.5"

I wound up with a total of 4 internal errors yesterday so I'm still
wondering if I have something conflicting.
--
Malcolm
in Toronto

In years of using Frame, and using Frame 6 since it shipped, I've only come
across maybe only one real "problem" document -- a book really -- that
actually crashed Frame over and over. I had to do a lot of clean up on it.

MIFing it didn't work; I had to take baby steps to fix it. Remove a few
unused para tags, save. Nudge a tab, save. Change a variable, save. Generate
after the tiniest change.  That kind of thing.  But finally, the book is
quite stable.

In your case the crash and the tab are (probably) unrelated, but I would
consider generating a fresh TOC before messing with the tabs any more ...
even seeing if generates without any TOC updates work okay.

Quote:>consider generating a fresh TOC before messing with the tabs any more ...

Actually, I've done a hundred or so over the past week. (At the beginning, I
told them, determine the structure of the book before you begin writing
anything. Of course, they got someone else to type 400+ pages that were
wildly inconsistent and almost completely without a sensible structure. Then
they gave it to me to do. In fact, the formats and their indents and
capitalization actually *reverse* about mid-book.)

I've been doing a new TOC every 10-20 minutes and thought the internal
errors might be related to that process. Oddly, though I had 4 such errors
on Wed., I had none yesterday. The only difference between those 2 days that
I can figure is that yesterday I was saving after EVERY change (as you
suggested above). This leads me to think that the program does memory
optimization/garbage collection at Save.
--
Malcolm
in Toronto