Scripture Print


This flavor is in beta and we are actively seeking feedback.


The Scripture Print flavor is based on the Digital Bible Library’s print entry type, which was initially developed as a way to archive projects generated by Publishing Assistant, and to make such projects available through industry standard print on demand vendors. The metadata has been through several iterations, in discussion with POD vendors.

POD assumes a fixed page layout that must conform to various printing requirements. PDFs are ideal for this, but do not allow text to be “reflowed” for novel publishing scenarios. Scripture Burrito therefore adds a variant, based on InDesign Tagged Text, that allows publishers to use fully marked-up text within containers of their choice.

The “source” section of print flavors requires more work. In DBL, print entries follow Paratext-created text entries, providing the entire source as a zip file. This is opaque, and should be replaced with a more transparent and intentional resource structure, as for Scripture Burrito’s scriptureText flavor.


PDF Variant

  • A PDF containing the body of the published work, with a scopeOrRole of “printBody”

  • A PDF containing the cover of the published work, with the scopeOrRole of “printCover”

  • optionally, a JPEG containing a thumbnail for online POD scenarios, with a scopeOrRole of “printThumbnail”

Tagged Text Variant

  • An InDesign Tagged Text (.indd) file with a scopeOrRole of “printFlowable”.

Metadata Flavor Details

PDF Variant

  • a contentType element with the value “pdf”

  • a pod element containing a boolean value

  • pageCount element containing an integer value

  • a width element containing a value such as “210mm”

  • a height element containing a value such as “297mm”

  • a scale element containing a value such as “100%”

  • an orientation element containing “portrait” or “landscape”

  • a color element containing “RGB” or “CMYK”

  • an edgeSpace element

  • optionally, a thumbnail element

  • optionally, a fonts element

The edgeSpace element, when present, contains top, bottom, left and right elements, each of which contains a value like “5mm”.

The thumbnail element, when present, contains width, height and color elements.

The fonts element, when present, contains one or more font element. The element encloses the name of the font, while the type attribute is one of

  • OpenType

  • Bitmap

  • TrueType

  • Type1

  • Other

Tagged Text Variant

  • a contentType element with the value “inDesignTaggedText”

  • a pod element with the value “false”

  • optionally, a fonts element as for the PDF variant


PDF Variant


The presence of this convention confirms that the ingredients are structured according to DBL’s legacy structure, ideal

  • the content in release/Inside.pdf

  • the printable cover in release/Cover.pdf

  • optionally, a thumbnail in release/CoverThumbnail.jpg

The absence of this convention means that nothing maybe assumed about the name or location of any resources. (This should not matter to Scripture Burrito tool chains which should use the scopeOrRole fields to determine semantics.)

Tagged Text Variant