Publishing Assistant

You are here: Home / Archives for vvdovikov

Having double and single column books in a single PA job

Problem:

Can I have double column book (e.g. for narrative books) and a single column book (e.g. poetic books) in one PA job?

Solutions:

Yes. It is quite simple.

Design the page with desired number of columns and save your design to stylesheet (.isty) or  template bundle (.tb). To do this open PA job, go to Tools > Create Template from Current Configuration.

Then staring new book to typeset, choose the desired stylesheet. Here is double column Genesis

And one column Hosea. Both in one job.

And you can batch process all single column book in one go and all double column book in another one.

If for some reason you synchronize styles in InDesign, pay attention to the Style Source file. You might want not to apply styles from single column design to double column one.

Backing Up PA job

The problem:

For some reasons (freeing up HDD space, changing the computer or archiving) you might want to back up your PA job and use it sometime later.

Restoring PA job from backup is another story and described in another article.

Solution 1:

If you have running PA, then the best way to backup the job using PA:

  1. Run PA
  2. Open the project you’d like to backup
  3. Open any InDesign document of the job
  4. Go to Menu > Help > Create Debug Backup
  5. Add documents to your backup
  6. Use Ctrl or Shift to choose multiple files. Pressing Ctrl+A selects all files of the job.
  7. Make your choice about pictures included in the backup
  8. Add other files to the backup. It might be printed PDF, screenshots, instructions etc. You do not need to include fonts manually. PA takes care about fonts used in job. Just make sure that the fonts you used are not rented and the fonts files can be copied
  9. Select a folder and a name for the backup
  10. Press OK and wait (it might take some time) for confirmation message

Solution 2:

If for some reason you can not run PA on your computer then in order to backup the job you need to copy two things:

  1. Job folder. For PA5 and earlier versions you can find it  C:/My Paratext Projects/<Project Name>/InDesign/<Job Name>/
  2. Fonts used in the job. The best way to do this is to use Package Book for Print feature of InDesign. It will copy InDesign file, linked imaged and, most important, fonts to the selected folder.
    Open you job (.indb file) in InDesign, select all documents, go to book menu and select Package Book for Print

Restoring the job backed up this way is more tricky.

Solution 3:

PA 6.1 got a new helpful feature that allow typesetter to backup jobs easily — Copy Job… It will create full copy of the job and let one experiment with almost completed job without being afraid to break it and redo it from scratch if something goes wrong.

  1. Open you PA job.
  2. Go to Menu > File > Copy Job…
  3. Select the project, PA job and copied job name

Please backup your PA jobs regularly.

Use \h Content In Running Header

The problem:

BookNames table in Scripture Reference settings is usually a source of data for running header on the printed page. But for various reasons typesetter might be asked to place in running header something different from \toc1 (long name), \toc2 (short name) or \toc3 (abbreviation).

Solution:

Custom header content codes allows typesetter to use not only BookNames table but also content of the \h tag in USFM file. E.g., code <bc.r.s> will place book name and chapter range, and the short name from BookNames table will be used (“.s” means “use short names from BookNames.xml”). But code <bc.r.h> means “use \h content for the book name in the running header”. This flexibility allows more diversity for the printed books without changing the project settings. More details about custom header content codes are available in the PA User Manual.

Put Chapter Numbers in the Margin?

Since version 6.0 Publishing Assistant  has an opportunity of placing verse numbers on the margins.

Can this be done with chapter numbers? The answer is yes.

Look at this page. PA put verses in the outside margin. Chapter number aligned away from the gutter to be closer to verse numbers.

To do this one needs additional tool — the Javascript to pull out the chapter numbers.

Here is the solution:

Step 1

In PA set up a job with inline Chapter Numbers (Chapter/Verse tab) and enable Marginal verse number.

Step 2

Add following line to FinalChanges.txt file:

"<ParaStyle:cip><CharStyle:cnum>(\d+)<CharStyle:><CharStyle:cnumEndSpace> <CharStyle:>" > "<ParaStyle:mcnum>\1\r\n<ParaStyle:cip>"

This will create a custom paragraph style that is not defined in InDesign, so you will receive a prompt about that.

Step 3

Create two Object styles in InDesign with the names like “mChapterLeft” and “mChapterRight”.

Here are settings for  mChapterLeft

And for mChapterRight

Note that measurements will vary depending on the font size and margin size, etc.

Step 4

Create two Paragraph styles they have the same names as the object styles above. Make the settings so it would reflect the style of the chapter number.

Step 5

Create another Paragraph style named “mcnum” and set the leading to zero and the color to none.

Step 6

Adjust all pages using PA.

Step 7

Run the script.

If you are new to using scripts, read the article about installing and running scripts in InDesign.

Once you run the script, use the following settings.

For Frame height use two times leading value in mm. In this example leading is 11 pt, thus Frame height is to be set 22 pt equal 7.762 mm.

Step 8

Proceed to set up paragraph styles. You will need to manually change the object style from mChapterLeft to mChapterRight on all anchored chapter number frames in the right column.

Chapter Number in Running Head as Hebrew Characters

By default Publishing Assistant puts European (Western Arabic) digits in running headers for chapter and verse numbers. It looks like this.

European (Western Arabic) numbers in the running header

But you might want or be asked to put chapter numbers as Hebrew characters. This is how you can do this.

First have a look at this Wiki article about Hebrew numerals.

Then start to edit your headerChanges.txt

Each line finds an Arabic number followed by dot (full stop), i.e. it finds a chapter number. Then it replaces it with corresponding Hebrew letter/number.

Please pay attention to the order of lines. It is important to change three-digits numbers first (up to 150 or 151), then double-digits and finally single digit ones.

After editing and saving headerChanges.txt you proceed with creating document or updating header if you already created document and adjusted pages.

The result should look like that.

Hebrew chapter numbers in the running header

Here are the lines to add to headerChanges.txt
===================

# Let’s replace three-digits Arabic numerals with Hebrew ones

“100.” > “\u05E7 ” #qof
“101.” > “\u05E7\u05D0 ”
“102.” > “\u05E7\u05D1 ”
“103.” > “\u05E7\u05D2 ”
“104.” > “\u05E7\u05D3 ”
“105.” > “\u05E7\u05D4 ”
“106.” > “\u05E7\u05D5 ”
“107.” > “\u05E7\u05D6 ”
“108.” > “\u05E7\u05D7 ”
“109.” > “\u05E7\u05D8 ”

“110.” > “\u05E7\u05D9 ”
“111.” > “\u05E7\u05D9\u05D0 ”
“112.” > “\u05E7\u05D9\u05D1 ”
“113.” > “\u05E7\u05D9\u05D2 ”
“114.” > “\u05E7\u05D9\u05D3 ”
“115.” > “\u05E7\u05D9\u05D4 ”
“116.” > “\u05E7\u05D9\u05D5 ”
“117.” > “\u05E7\u05D9\u05D6 ”
“118.” > “\u05E7\u05D9\u05D7 ”
“119.” > “\u05E7\u05D9\u05D8 ”

“120.” > “\u05E7\u05DB ”
“121.” > “\u05E7\u05DB\u05D0 ”
“122.” > “\u05E7\u05DB\u05D1 ”
“123.” > “\u05E7\u05DB\u05D2 ”
“124.” > “\u05E7\u05DB\u05D3 ”
“125.” > “\u05E7\u05DB\u05D4 ”
“126.” > “\u05E7\u05DB\u05D5 ”
“127.” > “\u05E7\u05DB\u05D6 ”
“128.” > “\u05E7\u05DB\u05D7 ”
“129.” > “\u05E7\u05DB\u05D8 ”

“130.” > “\u05E7\u05DC ”
“131.” > “\u05E7\u05DC\u05D0 ”
“132.” > “\u05E7\u05DC\u05D1 ”
“133.” > “\u05E7\u05DC\u05D2 ”
“134.” > “\u05E7\u05DC\u05D3 ”
“135.” > “\u05E7\u05DC\u05D4 ”
“136.” > “\u05E7\u05DC\u05D5 ”
“137.” > “\u05E7\u05DC\u05D6 ”
“138.” > “\u05E7\u05DC\u05D7 ”
“139.” > “\u05E7\u05DC\u05D8 ”

“140.” > “\u05E7\u05DE ”
“141.” > “\u05E7\u05DE\u05D0 ”
“142.” > “\u05E7\u05DE\u05D1 ”
“143.” > “\u05E7\u05DE\u05D2 ”
“144.” > “\u05E7\u05DE\u05D3 ”
“145.” > “\u05E7\u05DE\u05D4 ”
“146.” > “\u05E7\u05DE\u05D5 ”
“147.” > “\u05E7\u05DE\u05D6 ”
“148.” > “\u05E7\u05DE\u05D7 ”
“149.” > “\u05E7\u05DE\u05D8 ”

“150.” > “\u05E7\u05E0 ”
“151.” > “\u05E7\u05E0\u05D0 ”

# Now let’s deal with double-digits numerals

“10.” > “\u05D9 ” #yod
“11.” > “\u05D9\u05D0 ”
“12.” > “\u05D9\u05D1 ”
“13.” > “\u05D9\u05D2 ”
“14.” > “\u05D9\u05D3 ”
“15.” > “\u05D9\u05D4 ”
“16.” > “\u05D9\u05D5 ”
“17.” > “\u05D9\u05D6 ”
“18.” > “\u05D9\u05D7 ”
“19.” > “\u05D9\u05D8 ”

“20.” > “\u05DB ” #kaf
“21.” > “\u05DB\u05D0 ”
“22.” > “\u05DB\u05D1 ”
“23.” > “\u05DB\u05D2 ”
“24.” > “\u05DB\u05D3 ”
“25.” > “\u05DB\u05D4 ”
“26.” > “\u05DB\u05D5 ”
“27.” > “\u05DB\u05D6 ”
“28.” > “\u05DB\u05D7 ”
“29.” > “\u05DB\u05D8 ”

“30.” > “\u05DC ” #lamed
“31.” > “\u05DC\u05D0 ”
“32.” > “\u05DC\u05D1 ”
“33.” > “\u05DC\u05D2 ”
“34.” > “\u05DC\u05D3 ”
“35.” > “\u05DC\u05D4 ”
“36.” > “\u05DC\u05D5 ”
“37.” > “\u05DC\u05D6 ”
“38.” > “\u05DC\u05D7 ”
“39.” > “\u05DC\u05D8 ”

“40.” > “\u05DE ” #mem
“41.” > “\u05DE\u05D0 ”
“42.” > “\u05DE\u05D1 ”
“43.” > “\u05DE\u05D2 ”
“44.” > “\u05DE\u05D3 ”
“45.” > “\u05DE\u05D4 ”
“46.” > “\u05DE\u05D5 ”
“47.” > “\u05DE\u05D6 ”
“48.” > “\u05DE\u05D7 ”
“49.” > “\u05DE\u05D8 ”

“50.” > “\u05E0 ” #nun
“51.” > “\u05E0\u05D0 ”
“52.” > “\u05E0\u05D1 ”
“53.” > “\u05E0\u05D2 ”
“54.” > “\u05E0\u05D3 ”
“55.” > “\u05E0\u05D4 ”
“56.” > “\u05E0\u05D5 ”
“57.” > “\u05E0\u05D6 ”
“58.” > “\u05E0\u05D7 ”
“59.” > “\u05E0\u05D8 ”

“60.” > “\u05E1 ” #samekh
“61.” > “\u05E1\u05D0 ”
“62.” > “\u05E1\u05D1 ”
“63.” > “\u05E1\u05D2 ”
“64.” > “\u05E1\u05D3 ”
“65.” > “\u05E1\u05D4 ”
“66.” > “\u05E1\u05D5 ”
“67.” > “\u05E1\u05D6 ”
“68.” > “\u05E1\u05D7 ”
“69.” > “\u05E1\u05D8 ”

“70.” > “\u05E2 ” #ayin
“71.” > “\u05E2\u05D0 ”
“72.” > “\u05E2\u05D1 ”
“73.” > “\u05E2\u05D2 ”
“74.” > “\u05E2\u05D3 ”
“75.” > “\u05E2\u05D4 ”
“76.” > “\u05E2\u05D5 ”
“77.” > “\u05E2\u05D6 ”
“78.” > “\u05E2\u05D7 ”
“79.” > “\u05E2\u05D8 ”

“80.” > “\u05E4 ” #pe
“81.” > “\u05E4\u05D0 ”
“82.” > “\u05E4\u05D1 ”
“83.” > “\u05E4\u05D2 ”
“84.” > “\u05E4\u05D3 ”
“85.” > “\u05E4\u05D4 ”
“86.” > “\u05E4\u05D5 ”
“87.” > “\u05E4\u05D6 ”
“88.” > “\u05E4\u05D7 ”
“89.” > “\u05E4\u05D8 ”

“90.” > “\u05E6 ” #tsade
“91.” > “\u05E6\u05D0 ”
“92.” > “\u05E6\u05D1 ”
“93.” > “\u05E6\u05D2 ”
“94.” > “\u05E6\u05D3 ”
“95.” > “\u05E6\u05D4 ”
“96.” > “\u05E6\u05D5 ”
“97.” > “\u05E6\u05D6 ”
“98.” > “\u05E6\u05D7 ”
“99.” > “\u05E6\u05D8 ”

# And finally we’ll change numbers from 1 to 9

“1.” > “\u05D0 ” #alef
“2.” > “\u05D1 ” #bet
“3.” > “\u05D2 ” #gimel
“4.” > “\u05D3 ” #dalet
“5.” > “\u05D4 ” #he
“6.” > “\u05D5 ” #waw
“7.” > “\u05D6 ” #zayin
“8.” > “\u05D7 ” #het
“9.” > “\u05D8 ” #tet
====================

 

Privacy/Terms

Development Partners

Scripture Ecosystem