Skip navigation
Currently Being Moderated

create variable for RunningH/F page no.

Jan 16, 2014 5:53 AM

can anyone help create variable for page number RunningH/F for every other page blank? I have created one but need a variable for the BLANK page number to be added automatically (like the current page number)!  I do not want to build a page number manually for each page simply because I can not get the blank page number to automatically be added incrementally.  They need to look like.......FO-1/(FO-2 blank), FO-3/(FO-4 blank), FO-5/(FO-6 blank), etc.

 
Replies
  • Currently Being Moderated
    Jan 16, 2014 6:53 AM   in reply to TruthRequired

    So you want odd-numbered pages (with content) to show a page number of:

    "FO-"<$curpagenum>

    and even numbered (blank) pages to to show a page number of:

    "(FO-"<$curpagenum>" blank)"

     

    if so, just format the Left and Right master page headers or footers as:

    FO-#

    and

    (FO-# blank)

    where "#" is the variable <$curpagenum>

     

    How are you creating the blank pages?

    A paragraph format named "Blank",

    font color: invisible named color (controlled by Color Views)

    pagination: top of left page

    usually does the trick.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 16, 2014 11:06 AM   in reply to TruthRequired

    > The page number will always be visible on the right hand page,
    > thus showing FO-1/(FO-2 blank).  The next page (being left hand

    > page) BLANK and will not have ANYTHING on it.

     

    Ah. The challenge there is getting page P to to pick up the page number from page P+1. Frame doesn't make that easy to do, as

    variable <$curpagenum> is only available for Master Pages, and not Body Pages, and

    you can't Cross-Ref to an MP and get the correct pagenum, and

    Running H/Fs only read from the current page, and not the next.

    FM also doesn't support any math ops on entity numbers, alas, other than simple paranum expressions.

     

    I'm not sure what Marker trick you had in mind, but it wouldn't be Frame if there were one way to solve a problem.

     

    Offhand, I can mostly visualize a complex Cross-Ref / Running_H/F hack for this, but won't post it until we first see if some other contributors have more elegant solutions.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 16, 2014 11:19 AM   in reply to TruthRequired

    Assumption:

    Each content page has something unique, that uses that same paragraph tag on each content page (my example assumes a Heading2).

     

    You can run this test on a new, empty duplex document.

     

    In your actual document, make your body text frames, at least for Right pages, one text line taller than they need to be. This holds an extra invisible bottom line on the content pages, used for Running H/F pickup.

     

    1. Format Setups

     

    View > Color > Definitions

    Name: Invisible Content

    Process

    RGB 75 50 75 (or whatever you like)

    Overprint

    [Add]

     

    View > Color > Views

    Move "Invisible Content" to to "Normal:" for whatever View# you use for authoring (we use#6). Move it to "Invisible:" for all other view numbers.

    [Set]

     

    Click in a normal Body para somewhere

     

    Format > Paragraph > Designer

    Tag: ForceBlank

    Commands: New Format

    [*] Store in Catalog [_] Apply to Selection

    Basic:

    [*] Next Pgf Tag:

    [Heading2]

    Default Font:

    Color: Invisible Content

    Pagination: Top of Left Page

    Numbering:

    [*] Autonumber Format:

    [FB after page: ]

    [Update All]

    Note: The autonum is not required, but if your ForceBlank paras don't have some unique content, they will be impossible to distinguish in the Xrefs dialog from NextPage paras.

     

    Format > Paragraph > Designer

    Tag: NextPage

    Commands: New Format

    [*] Store in Catalog [_] Apply to Selection

    Basic:

    [*] Next Pgf Tag:

    [ForceBlank]

    Default Font:

    Color: Invisible Content

    Pagination: Anywhere

     

    Special > Cross Reference > Edit Format

    Name: [<$pagenum> (only) ]

    Def: [<$pagenum> ]

    [Add]

     

    View > Master Pages

    Click in the header.

    Special > Variable:

    Running H/F 12

    [Edit Definition]

    change

    paratag

    to

    NextPage

    [Edit] [Done]

     

     

    Display Master Page Right.

    Click in header.

    Type in:

    This is page A. The next page is B.

    Set A to variable <$curpagenum>

    Set B to variable Running H/F 12

    View > Body Pages

     

    2. Create initial Body content instance

     

    Create a Heading2 with some xyzzy content.

    Start a new line.

    Apply tag NextPage

    Hit return, which will create a new page and an empty para of tag ForceBlank. This example assumes that NextPage will be the last para on every content page.

     

    With cursor in para ForceBlank,

    Special > Cross-Reference

    Source Type: Paragraphs

    [Heading2]

    Paragraphs:

    [ pick the xyzzy content ]

    Reference:

    [<$pagenum> (only)]

    [Insert]

    This makes this para unique in the Xref dialog's list, see we can Xref it by page#.

     

    Go back to the previous page.

    Click in the NextPage para.

    Special > Cross-Reference

    Source Type: Paragraphs

    [ForceBlank]

    Paragraphs: look for

    [FB after page: 1]

    Reference:

    [<$pagenum> (only)]

    [Insert]

    This puts page number P+1 on page P, in the Flow_A text.

     

    Edit > Update References

    [*] All Cross-References

     

    The header should now say:

    This page is 1. The next page is 2.

    QED

     

    If your content page don't have unique para formats that always appear, like the HEading2 in this example, the ForceBlank para could just Xref to the preceding NextPage para, idoes exist on each preceding content page.

     

    3. Create more instances.

     

    You can now copy that NextPage/ForceBlank para pair to every body page, and update the Xrefs to each other. They won't need edits after that, even when pagination changes, and you'll never need to type in actual page numbers.

     

    4. Rendering

     

    For a book, in the book menu, select all component files.

    View > Color > Views

    Select the view number you use for various editions which do not display color "Invisible Content".

    [Set]

    Render. (Save-as..., Print, etc.)

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 16, 2014 11:54 AM   in reply to TruthRequired

    Want to post pictures? Use the Camera icon in the Web interface version of the forum..

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 16, 2014 12:32 PM   in reply to TruthRequired

    Adobe doesn't provide much help on what you would use Color Views (CV) for, much less what each view number might mean. And no, you can't name them in the app (at least in the FM7.1 we use).

     

    CV is great for content that needs to (or at least can be) turned on and off without causing a reflow, such as the Invisible Content paras above. This is different than Condition Codes (CC), where reflow happens whether you want it or not, and Xrefs can easily get broken. We use CC where we want reflow when the content is switched on/off.

     

    We use CV for rendering editions. Our current convention (and it's just a convention) is:

    1. PDFs with visible navigation hypertext in the margins. Color "NavLink" on. Invisible, Masking and Reviewer off.
    2. Print editions with that Nav turned off. Invisible, Masking and Reviewer also off.
    3. {reserved, might be HTML5 or XML edition someday}
    4. {reserved, might be ebook edition someday}
    5. Reviewer edition, with NavLink and Reviewer on, Invisible & Masking off. Reviewer-on reveals draft state, timestamps, reviewer-only hints, etc.
    6. Authoring mode, with everything turned on.

     

    So you'd author in, say, CV#6, so you can see all the meta-text, then switch to one or another CV# for rendering with the meta turned off.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 16, 2014 12:33 PM   in reply to TruthRequired

    > I performed the “Pagination: Top of Left Page” step and then the following was generated…

     

    Link is circular.

     

    I didn't include all the [Apply] dialogs that pop up, and some ops probably do require that you be specifically in Body or Master Page mode.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 16, 2014 12:29 PM   in reply to TruthRequired

    FWIW, treat FM's Color Views as you would a layer in other applications (like Illustrator, Photoshop). The visibility of the objects is tied in to the color attribute applied to the object. The Color Views let you set up to six different ones where each color can be independently set to show (Normal), clip out underlying colored objects (Cutout) or Invisible (i.e. it can not be seen nor will it print, but FM knows that the content is still there and can reference or link to it).

     

    By default, most FM documents are set to be in Color View 1 and the View is a document level property (i.e. a template may set this to another View number).

     

    You can easily toggle between views using the shortcut <esc> v #, where #=1 to 6. [bonus: <esc> v v toggles all graphics on/off] The keyboard shortcut also works at the book level to change the View in all files of the book in one quick keyboard shortcut.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 16, 2014 1:04 PM   in reply to TruthRequired

    > ... see below in original message red text)!!!

     

    ??? I see no red text anywhere.

     

    > ... do I type all that in one line exactly as you have it?

     

    I did, into the default Header para type. it's just a demo, to show that the MP header can be made to show both the current page number, and any other arbitrary page number (in this case, the next page), by using a user-defined Running H/F variable to grab local page content that is actually an Xref to the away page ... with some tweaks to aid stewardship and presentation.

     

    > ... header you mentioned really supposed to be the footer where I want my page number to appear on the body page???

     

    Can be header or footer as long as it's a Background text frame on the Master Page: Right.

     

    > ... consider me your challenge for the day! ;0)

     

    Well, mine is winding down, so some of this may be left as homework for the student. It sounds like you have a bit to learn about paragraph formats, cross-references, cross-reference formats and variables.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 20, 2014 6:38 AM   in reply to TruthRequired

    You need to use the Camera icon in the Web interface if you want to show us screenshots or error logs – no attachments are permitted in the forum.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 20, 2014 6:38 AM   in reply to TruthRequired

    Search the forum for “unavailable fonts” – there’s a number of posts that have troubleshooting guidelines for eliminating where these pesky fonts can hide.

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points