Book Chapters not renumbering

[_PamelaOwens_]

HELP...

FrameMaker (Structured v.7.2p158)

I copied some unstructured files to a new folder, used the conversion table to add structure...deleted and readded the files to the book file and it won't renumber. I even tried creating a whole new book file from scratch and it still will not renumber the files. So I have 7 chapter files all saying chapter 1.

I've tried using the document/chapter file numbering and set it there and then in the book file tell it to use the file...still didn't work.

Any ideas why it's being so stubborn? Is there a problem/BUG with unstructured having been structured that won't let it renumber?

Thanks.

[_Van_Kurtz_]

Pamela,

There is no bug/problem with numbering in files converted from unstructured to structure. I do it all the time.

Make sure the autonumbering format for the chapter title is correct, that is, make sure it is using the <$chapnum> building block. If the unstructured files are very old, they may be using another numbering system, one designed before the $chapnum building block became available.

Good luck,
Van

[Art Campbell]

In addition to making sure that the paragraph tag that displays the number uses <$chapnum>, you need to set the Chapter Numbering in the book file, not the component Document.

In the book file, highlight the chapters, right-click, then Numbering > Chapter > Increment...

Save the book and all files, and update.

A

[_PamelaOwens_]

The autonumbering is actually set the EDD. I've never had a problem with the numbering before. However this is the first time I've tried to update a converted unstructured document. That's why I was wondering if that might have been the problem.

I used the conversion tables, then I imported my structured EDD files and everything looked fine until I went to get them renumbered....

Like I said in my original post...I tried it both ways...setting the numbering in the book file, and when that didn't work I tried setting it in the document files...that didn't work either...no matter what I do, it seems they are just stubborn and won't change. arrrghh!

I know I've had some problems with them renumbering before, but it was always a matter of the order of the steps of saving the files in between...but I had made notes the last time I had a problem and I've always done it the same since...and never had a problem again until now.

Any other ideas on what to look at that might be the problem?

Thanks!

[_Van_Kurtz_]

Pamela,

I think you are misunderstanding something. You need to reread the posts by Art and me.

1. Open one of your documents that begins a chapter. Put the insertion point in the chapter title, where the chapter number is. Then open the paragraph designer and look at the autonumbering format. It needs to contains the building block <$chapnum>. If not, then your EDD and/or template is not creating the correct format for autonumbering to work.

2. Then in the book file, right-click each document file and select Numbering.

3. In the Numbering dialog box, click the Chapter tab and select Continue Numbering from Previous File in Book.

4. IF the chapter 1 file is not the first chapter in the book, then right-click the chapter 1 file and select Numbering. In the Chapter tab, select Chapter # and enter 1 in the text box.

5. Then update the book file. The numbering should be correct.

Chapter numbering is no different in structured files than it is in unstructured files.

Good luck,
Van

[_PamelaOwens_]

Hi Van,

The autonumbering is showing up in the paragraph designer.

There's definitely something strange going on here.

I tried adding 3 of the newly structured chapters to a book file that is working/updating the chapter files. Every one of these chapters would not renumber, and 2 of them had warnings for color definition inconsistancies. The 3 had no errors, but still did not change from chapter 1.

So the book looks like this now--first number is the number it was reassigned after updating: (I tried using a different order but still had the same results, all the restructured chapters stayed at #1 and everything renumbered after it).

1 original working book ch1
1 #3 restructured
1 #1 restructured
2 oriignal working book ch 2
1 #2 restructured
2 original working book ch.3

I tried importing formats: color definitions for ch.1&2 but it didn't work. Also there's an error on #2 where when the file is opened, it says "Document uses unavailable fonts. To reformat the document using available fonts, click OK." If I click OK, it opens the file, however, if I save it, you would think it would save it using the 'available fonts', but apparently it does not, because the next time I open the file, I get the same message again. There is no option to import fonts, so how do I fix this error?

Thanks.
Pam

[_Van_Kurtz_]

Pam,

I am not sure why the renumbering is not working, since you state that the correct chapnum building block is in the autonumbering format.

Anyway, in the preferences, there is an optional checkbox labeled Remember Missing Font Names, which I keep checked; however, you can uncheck it if you are sure about things. BUT you open a file that uses a font you do not have, FrameMaker displays the message about unavailable fonts. IF you have the option about remember missing fonts CHECKED, then FrameMaker allows you to edit the document, even though you do not have the font. When you save and close the document, the document still uses the missing font, even though the initial message states that it is reformatting with a different font. So, when you open the document again, the font is still missing. IF you UNcheck the preference, then FrameMaker WILL reformat with a different font and you will not get the message the next time you open the file. So, you can get rid of the message by unchecking this option, but it may not be what you want or should do...

In a structured document, your template and EDD control the formatting. So, your system should have all the fonts required by the template and EDD. If not, then I would think you should get them.

Now, when you convert an unstructured document to structure, sometimes a few "bits of fluff" remain in the file. So, there may be a font change in the file that does not have any text associated with it. If so, FrameMaker sees this as a missing font. Once I get a file converted to structure and fix everything so that the file validates and everything else looks good, I open a new, blank template file. Then switch to the structured file, open the structure window, select the root element (the one highest in the hierarchy), copy it, and paste it into the blank template. Then I save this file with the same name as the old one or with a new name. This file should have all the detritus in the old structured file removed. This is also a good way to standardize your color definitions.

The warnings about the inconsistencies in the color definitions should cause few problems, except in the display of color, but they certainly should not affect the numbering problem.

If you do the clean up I suggest above with all your newly structured files, maybe that will be enough to correct the numbering problem, but that is just a guess. If you have done all that I have presented in earlier posts, the numbering should work correctly.

Good luck,
Van

[_PamelaOwens_]

Hi Van,

well, still no luck. But I took your suggestion on moving the converted text to a template and that seemed to take care of the problem. So I guess there still must have been some "fluff" left over causing a problem.

But now I'm having troubles printing it to PDF:

%%[Page: 16]%%
%%[ Error: undefined; OffendingCommand: pdfmark; ErrorInfo: _objdef A286721.1 ]%%

Stack:
/ANN
/Custom
/Subtype
[0 0 0]
/Border
[1200 2529 9011 2058]
/Rect
{A286721.1}
/_objdef
-dict-

%%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
%%[ Warning: PostScript error. No PDF file produced. ] %%

I get this a lot. Ironically, if I print the chapters/file separately instead of as a book, I don't get this error. I vaguely remember seeing something in the notes for V8 stating something similar that was fixed. If I have V7.2, can I get the upgrade to the V8 or is there a charge for that? Maybe I'll have to look back at the notes...

Thanks for all of your help!
Pam

[Art Campbell]

In your Distiller Job Options, try toggling the Generate Tagged PDF setting.

Are you sure that you're up to date with Acrobat updates? An error like this was a bug that has been patched, but your particular error could be something else. Still, if you're not up to date...

Art

[_PamelaOwens_]

Art,

I don't have Version 8, I'm still on Version 7.2 using patch 158. Are there any other updates for V7.2?

Thanks.
Pam

[Art Campbell]

Pam,

Those settings are in the Adobe logical printer instance (Distiller), not in Frame itself.

Art

[_PamelaOwens_]

Well, I just upgraded to V.8 trial --had to open and resave everything to v8 format... tried printing...and I still get the same error...ugggh!!! So whatever bug they fixed, there's apparently another one...

[_Van_Kurtz_]

Pam,

Did you try Art's suggestion? When you print the book in FrameMaker, choose Adobe PDF as the printer. In the print dialog box, click PDF Setup. In the PDF Setup dialog box, select the Tags tab and CLEAR the Generate Tagged PDF. In the Links tab, select Create Named Destinations for Elements and Paragraphs. Click Set. Then click Print.

I am still using Frame v7.2 with Acrobat 8, and have no problems creating PDFs using the above procedure.

Van

[_PamelaOwens_]

Yes,

still no luck...

%%[ ProductName: Distiller ]%%
%%[Page: 1]%%
%%[Page: 2]%%
%%[Page: 3]%%
%%[Page: 4]%%
%%[Page: 5]%%
%%[Page: 6]%%
%%[Page: 7]%%
%%[Page: 8]%%
%%[ Error: undefined; OffendingCommand: pdfmark; ErrorInfo: Rect ]%%

Stack:
/ANN
/Link
/Subtype
/I9.5.1000124
/D
/GoToR
/S
/Action
/Type
-dict-
/Action
[0 0 0]
/Border
[1200 2885 9011 2068]
/Rect
-mark-

%%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
%%[ Warning: PostScript error. No PDF file produced. ] %%

[Arnis Gubins]

Pamela,

The error is saying that on page 9, there is a bad hypertext link area (that may be due to not setting the Generate Tagged PDF option, depending upon our exact version of FM8).

[jenniab2]

(Response to Pamela Owens)

I know this discussion is not about book chapter numbering anymore, but this was the only place I found the solution to my problem -- for one particular book I was getting the "Error: undefined; OffendingCommand: pdfmark; ErrorInfo: _objdef" error, even though my other Frame books print fine.

I checked the Tags and Links settings suggested above, that didn't work. Then I glanced at the Settings tab and saw that the PDF Job Options was not the one I usually use. Set that, and it worked! Phew. I think the error was about fonts not embedded in whichever job options setting was being used instead.

I'm on Frame 8.0p277