Same question, different problem. Our military contractor requires that the blank page be completely blank - no page number - nothing. However, the previous page must indicate that the next page is blank, as in 2-1 (2-2 blank) (in the footer/page number). I can't figure out how to advance the page number (2-2). We inherited this document, and the previous owner had a different master page for every page that required this notification (over 100 master pages!). There's got to be a better way, but I haven't been able to figure it out.
Thank you, Luca.
To Jive: Wow. That's a new one on me.
I guess you will need to create a master page with no headers or footers, but I don't know how you would program the page numbers into the last page of the document (for example, 2-2 blank). That wacky military. I just finished a military contract, which is why I needed to learn how to do the page intentionally blank in the first place.
I guess you could follow my directions for creating the TPILB, but leave the frame that contains the words "Page intentionally left blank" empty. That would solve your advancing the page issue and you could remove the headers and footers from the master page with the blank frame. But I'm stumped when it comes to adding the text to reflect what the next page number will be. Sorry. I'll think about this and try to find a solution...
By the way, if anyone knows of anyone hiring a very experienced writer in MD or VA, please let me know (how's that for a shameless plug??).
Oops, sorry oatsybob. My last post was to you. The address shown said to jive-xxx, so I addressed it to Jive.
Hi all! I am using FM 8 and I was able to apply this rule, but for some reason, it does not apply to my TOC file or to pages where I only have tables (even though I have included the formats used there in the mapping table). Does anybody know what I'm doing wrong??
This is how I've automatically applied the TPILB at the end of my even page chapters:
- Go to COVER file
- Create Reference mapping table: Format - Page Layout - Apply Master Pages
- Create LeftContent master page: Special - Add master page - copy from left - name "LeftContent"
- Go to Master page view and on the default LEFT page:
- Insert text box and write: This page is intentionally left blank.
- Go to Reference page view
- Book update: Yes
- Fill in Mapping table with conditions (the more the safer):
- Format - Page Layout - Apply Master Pages
- Leave COVER file open and select the rest of files in the book
- Import format:
- Page layout
- Reference pages
- Import format:
- Update book - select all, including Apply Master Pages
Thanks in advance for your help!
- Go to COVER file
Can we apply your suggested method to removing blank pages inserted by FraemMaker. I still can NOT remove blank pages even though I used all suggestiins in this forum.
If blank pages are being inserted, it's probably because the settings in the book template. You can make the book single page or double page. If it's double pages, it will insert the blank pages so that your chapters start on an odd page number for printing purposes. I don't have FrameMaker in front of me, so I can't tell you the exact steps, but if you click your book and click settings, you should be able to fix that issue.
Let me know if that solves your issue.
Many thanks Megan,
I tried all solutions,nothing worked. In a single chapter I can delete empty pages using pagination command in format. As soon as I update the book empty pages appear.
Sounds like there are elements being inherited from files somewhere.
Did you try this?
When you generate and update a book, the files in the book inherit structure information from the book file. A file’s Element Catalog may have inclusions and exclusions from the book, and other inherited information in the file may affect the formatting of its text elements.
If you delete a file from a book to use the file as a stand-alone document, reapply the file’s element definitions to remove any structure information that came from the book. If the file’s text formatting was affected by this structure information, reapplying the definitions also restores the file’s original formatting.
1. Make the appropriate document window or book window active. If a book window is active, select the documents you want to affect.
2. In the file, choose File > Import > Element Definitions.
3. Leave the Import from Document pop-up menu set to Current, select While Updating: Remove Information Inherited from Book, and click Import.
I had the same problem. The only solution I found was after generated my TOC, TOT, TOF, I would add an extra line below the table and tag it as "intentionally blank." It's not graceful, but it worked.
Let me know if that helps.
In addition to checking to see if book chapter pages have been set to
always be even in count, look to see if the chapters that follow are set
to begin specifically on a right or left hand page. For example, if
chapters are set to start on a right-hand page and is chapter 1 is three
pages long, it will also end on a right-hand page. Chapter 2 MUST then
insert an extra left-hand page in order to start on a right-hand page.
Thank you for replying! That worked indeed, but I still do not have a solution for the tables that run across several pages. My temporary solution is either to manually assign a different master page or split the tables and insert an extra line of each page, but I was hoping for something automatic
Great idea. Thanks for posting.
I'm testing it here. It works in most cases.
Anomalies that I see are:
- A table is the last content in a file and continues across a page boundary. The last page in the file, with the continued part of the table, is mapped to Left (not Left.Used). The table anchor paratag and table title paratag appear in the mapping table. This consistent with ana030's results.
- Generated files, such as a TOC. Same as before, the paratags for the (apparently) first paras in flow A on each page are in the mapping table, but no luck: Left (not Left.Used) and Right (not Right.Used) are being mapped.
Definitely worth more testing here. So far I'm stumped on these two anomalies.
I was going through some mail for my elderly mother and, in one of the renvelopes was a blank, white, plastic credit card with this printed on it.
This card intentionally left blank.
As Charlie Brown would say: Good Grief!
So, re: pages with table continuation, apparently none of the paratags of the table is the first paratag of flow A on the page.
I wonder how we could learn if FM believes a paratag is "on" that page at all? And if so, which one?
1 person found this helpful
Due to some more recent confusion about this, here's a step-by-step for the AMP hack:
- File > Open
some existing file with content & formats you use.
I selected the sample file:
This sample document defines paragraph tags: Author, Body, Bulleted, Callout, CellBody, Cellheading, Extract, Figure, Footnote, Heading1, Heading2, HeadingRunIn, Indented, Numbered, Numbered1, Subtitle, TableFootnote, TableTitle, Title, TitlePage, TitlePg-back
It also has a manually-applied Master Page usage of page "Plain" on the page 1 and 2. We'll fix that.
- Format > Page Layout > Apply Master Pages
[ OK ]
Master Page Mapping table does not exist.
A new table will be created in the reference pages.
[ OK ]
(In the unlikely event that your document already has a MasterPageMaps Reference Page, you won't see that dialog.)
- View > Master Pages
Special > Add Master Page
(•) Copy from Master Page [Left]
[ Add ]
- Special > Add Master Page
(•) Copy from Master Page [Right]
[ Add ]
- Navigate to Master Page Left
Use the graphics text tool to add, at page center:
"This page intentionally left blank" or as desired.
Set the color to Gray or as desired.
Select that text line as an object.
Graphics > Send to Back
and copy it to Master Page Right, sending to back there as well.
- View > Reference Pages
Navigate to Reference Page MasterPageMaps
Add as many rows to the UnstructMasterPageMaps table as needed for all the paragraph formats that need to be mapped to Left.Content and Right.Content pages. Typical rows look like:
Paragraph Tag Name Right-Handed Master Page (or Single-Sided Master Page) Left-Handed Master Page Range Indicator (Single, Span pages, Until changed) Comment TitlePage Plain Plain Single Body Right.Content Left.Content Single Bulleted Right.Content Left.Content Single
For this specific sample template, that first row converts the front page mapping from manual to automatic. The back-of-front page was also manual, but becomes automatic because we don't list it in the table. Add the same Right.Content/Left.Content to more rows, for each tag found on normal body pages.
- View > Body Pages
If there are no empty pages in your trial document, create some, typically by forcing some heading to start on the top of a right page.
In the case of the sample template used here, page 2 contains just an empty paragraph of format TitlePg-back, which is absent from the UnstructMasterPageMaps table.
- Format > Page Layout > Apply Master Pages
Check your empty pages. They should all have TPILB at center.
Note: Unless enhanced in later FMs, this hack doesn't work if the document contains tables that span more than two pages. FM7 ignores paragraphs in table cells for master page mapping. You need some non-table Flow A body content above or below the table to get proper mapping. Alternatively, if the table cells are all filled with a background color (including white), it might not matter if they get a TPILB page that is otherwise identical to our Left.Content and Right.Content, as the table will obscure the TPLIB text.
- File > Open
Multi-page tables work for me in FM11 and FM12 with the addition of two paratags, such as ta-TableAnchor and te-TableEnd.
On the body page, insert the table in a para styled with ta-TableAnchor. Also on the body page, append a te-TableEnd para immediately after the table. Negative space above and line height can make the ta- and te- paras be almost invisible. Because they have no text in them, I color them red for visibility while editing. I can image the color change might cause a problem with some publishing, but it hasn't caused a problem for me.
In the UnstructMasterPageMaps table, add rows for those to paratags as:
ta-TableAnchor Right.Content Left.Content Until changed te-TableEnd Right.Content Left.Content Single
Cool. That seems to solve the table span problem.
What's the reason for the TE tag?
And on the color, use Color Views to manage that. Define an enterprise-wide standard for which View number is what, and for the authoring view define a color named, say "Meta", which makes such meta text visible only during edit.
I've never used Color Views and wouldn't have thought of it. Schweet!
The te- tag switches AMP from "Until changed" mode back to "Single" mode. A bit like a bookend.
Top-of-mind, I'm not sure if it's needed. I don't recall noticing it as the first body para on any page, so maybe it's never really used.
A useful test case for a force-even pagination file would be to set the table length so that the table concludes its multi-page run on an odd page, with te- as (or not as) the final para in the file. How does FM set up the next (final, even) page? As Left or as Left.Content?
(I'm away from a machine with FM at the moment, so I can't test it.)