PPTools/Guiguts/Page Labels

From DPWiki
Jump to navigation Jump to search


It is up to the PPer's discretion if Page Labels should be included.

It is the general consensus that, if included, the page labels should match the page numbers in the original book. They should not be set to the page image numbers which are assigned by Project Managers to the scanned images in preparation for Post-processing. They frequently need adjustment as described below Setting Page Labels.

Page Markers and Page Labels

Refer to the Guiguts manual for up to date information on how to handle Page Markers and Page Labels


Information for older versions of Guiguts follows

All of the information below is for, as of 2021, older versions of Guiguts up through 1.0.x.

Warning for Large Projects

Warning: For large projects (over 1400 pngs or so) Guiguts versions prior to 1.3.0 may have problems maintaining page numbers and labels correctly. This page provides one possible work-around for this problem if it affects you. A simpler solution is to upgrade to the latest Guiguts version.

Adjust Page Markers

Guiguts pl palette.png

After you remove the page separators the page-image boundaries remain in the file as invisible markers. You can see and edit these markers using the Adjust Page Markers palette. To open it, right-click (Mac: control-click) in the Img: field of the status bar.

As the palette opens, the invisible page markers are revealed as bright-yellow insertions in the text. To close the palette and hide the markers, right-click in the Img: field again.

The number of the page marker next after the insertion point is shown. Use the Previous Marker and Next Marker buttons to step through the page markers in sequence. To jump to a particular marker, edit the yellow field at the top to show a page number one higher or lower than the marker you want. Then click Previous Marker or Next Marker. The document scrolls to the center the line containing the marker you want.

Managing Page Markers

The page markers represent the points where Guiguts will insert visible or invisible page anchors when you generate the HTML for the book. Normally you would not want to move, delete, or add to these markers because doing so makes the "pagination" of the HTML version different from that of the original book.

One possible reason to insert a marker: sometimes the people who scan a book scan the blank pages and sometimes they do not; and sometimes they scan some blank pages and not others. You may want to insert a marker to account for an unscanned page, so that the number of markers agrees exactly with the number of surfaces in the actual book.

You might receive a book that has no page markers. (Perhaps the book has been partly processed, and the .bin file, where the marker information is kept, has been lost.) In that case you could install page markers. The command File> Guess Page Markers will create markers evenly spaced through the document. Then you can use this dialog to insert, delete, and move the markers to match the page images.

To move the current marker in the text, click the four move buttons. The marker slides one character left or right, or one line up or down.

To add a new page marker at the end of the book, set the insertion point in the text somewhere after the last existing marker. Then click Add. To insert a new page marker between existing ones, set the insertion point where the marker is to go, and click Insert. A new marker is inserted and following markers are incremented by 1 if necessary to prevent duplicates.

To remove a marker, use the palette to navigate to the marker you want to remove, and click Remove. The marker is taken out of the book and no other changes are made.

If you click Insert Page Markers, Guiguts inserts a text string of the form [Pg 003] into the text following every (invisible) page marker. You can apply a regex replacement to style these as you want, for example as visible page numbers in an HTML or an ASCII text.

The Renumber button and page offset field are made obsolete by the Page Label dialog discussed below.

Page Numbers vs. Folios

The scanned pages we receive are numbered sequentially from 1 and we casually refer to these as "page numbers." Confusion arises because these numbers often are not the same as the numbers printed on the pages of the book. The technical term for the number that is printed on a book page is folio. If we use these terms separately, we can avoid some confusion:

  • page number: the sequence number of a scanned page image.
  • folio: the number printed on the page of a book.

The distinction is important because the numbers in a table of contents, an index, or a cross-reference ("see p.196") are folios—not page numbers.

Page numbers are a simple count of every scanned surface. Folios are assigned using complex and not terribly consistent rules that reflect the logistics of printing technology. For example, the "front matter" (comprising title pages, preface, contents, etc.) was usually the last part of the book finished, after the body had been set up in type. That meant body folios had to be assigned before the quantity of front-matter pages was known. Sometimes the front matter was left un-folio'd; sometimes it got its own series of folios, often lowercase roman numerals; then the body started over again with folio "1." When one or more glossy "plates" were inserted in the book, they might be numbered sequentially with the pages, or they might be referenced as "facing page nn." If a plate had a blank reverse, the blank face might count in the folio sequence or not—and it might have been scanned, giving it a page number, or not.

In summary: page numbers rarely match folios and the numerical relationship between the two can change as you go through the book. However, when Guiguts auto-generates HTML it inserts an anchor at each page boundary with the number of the page. It is important that these anchors reflect the folios, not the page numbers. Then it is easy to link the page references in the contents, the index, and in cross-references to the correct page.

Setting Page Labels

Guiguts associates a numeric label with each page marker. Initially, the labels are the same as the image numbers: image 001 has label Pg001. It is these labels that are used when creating HTML page-anchors. You use the Configure Page Labels dialog to change the labels so that they properly reflect the folios throughout the book.

To open the Configure Page Labels dialog, right-click (ctrl-click may work on earlier versions of Mac OS, but does not work in 10.5 and 10.6) in the Lbl: field in the status bar (the field just to the right of the See Image button). If you have not yet set the page labels, it reads No Labels.

Guiguts pl label1.png

Note in OS X and Linux you may need to drag the window wider in order to expose all the columns.

This dialog contains a table with one row for every page image in the book. The five columns of this table are:

  1. The image file numbers in sequence, e.g. Image# 089.
  2. The page numbers assigned to each image, initially the same as the image file number, e.g., Pg 89.
  3. A choice of one of three formats for the page number: Arabic, Roman, or "ditto" meaning "same as preceding page."
  4. A choice of three actions to take as Guiguts recalculates the page numbers in sequence: Start@, +1, and No Count.
  5. A numeric field used to specify a starting number when the action is Start@.

Using these fields you can specify almost any treatment of pages (excepting hyphenated numbers, chap-nn or vol-nn, which are not yet supported).

Dealing with Front Matter

For one common case, suppose that your book begins with:

  • A title sheet (two image files) that has no numbers, just a title recto and a blank verso.
  • Eight pages of front matter numbered iii to x.
  • A sheet blank on both sides, only one side of which seems to have been scanned.
  • Text that begins with Chapter I bearing the folio 3.

You would use the Page Labels dialog to set up this numbering as follows:

Guiguts pl label2.png

The first two pages are set to No Count so no page number anchors will be generated for the title sheet, which has no folios.

The first eleven images have been set for Roman format. The roman-numbered front matter pages begin with Image 003; it has been set to Start@ the number 3 (it will display as iii). The next seven pages are set to be numbered +1 and ditto format.

The text begins on Image 012 which bears the folio 3. The preceding (blank) image is set to No Count. (The even-numbered image 012 ought not carry an odd, i.e. right-handed, folio. What probably happened is that only one side was scanned of a sheet blank on both sides; in other words, page image #11 should have been two blank images. No matter; as these images had no text or folios, there will be no reference to them elsewhere in the book.) Image 012 is set to Start@ 3, in Arabic format, and all succeeding pages are left at ditto and +1.

Click Recalculate at the top of the dialog to get the page numbers refreshed in the window. Click Use These Values to apply the changes to the book and close the dialog.

Dealing with Plates

Further on in the same book there is a full-page illustration, or "plate" which has no folios. It is mentioned in the List of Illustrations as facing page 48. You page through the book and find that the image sequence runs:

  • Image 057 bears folio 48.
  • Image 058 has the illustration
  • Image 059 is blank—so they did scan the blank reverse of the picture.
  • Image 060 bears folio 49.

You open the Configure Page Labels dialog, scroll down to the right vicinity, and set No Count on the two images of the plate. After you click Recalculate, the dialog shows:

Guiguts pl label3.png

In the same way you deal with several other plates. When the numbers shown in yellow in the dialog all match correctly to the folios in the page images, you click "Use These Values" to assign the labels and close the dialog. Then you save the file.

Dealing with Skipped Blank Faces

Near the end of the book you find that the text terminates on a right page, folio 295. The next page image file contains the start of an Appendix having folio 297. Clearly the blank verso of page 295, logically page 296, was not scanned. There are two ways to bring the page labels back in sync with the book when blank faces are not scanned.

You can close the Configure Page Labels dialog and open the Adjust Page Markers dialog. Use it to insert a page marker to represent the unscanned blank face, in this case, just ahead of the one for the first page of the Appendix. When you reopen the Configure Page Labels dialog it will show an image and a label at this point.

Alternatively you can just use the Configure Page Labels dialog to set the first page of the Appendix to Start@ 297.