Forme work: renditional issues

Encoding Instructions (new P5 version)

The WWP records the renditional distinction of forme work components using the rend attribute on mw. Catchwords are the only type of forme work which is likely to contain any renditional information. If only part of the catchword is renditionally distinct, we will use hi as necessary to indicate the renditional shifts within it. We do not do any content-based encoding within catchwords (e.g. persName, etc.). We do not encode delimiters using the catchword’s rend attribute; quotation marks, brackets, etc. should be encoded as #PCDATA (using entity references) since they do not function as delimiters in any meaningful sense within the catchword.

Note that where an mw element occurs within a renditionally distinct element, the rendition of the mw (if different) will need to be specified.

Examples

	        <lb/>If there were fewer words in this sentence in this
                   <lb/>non-italicized page, then this could be the <term rend="slant(italic)">pen&shy;
                   <pb n="3270">
                   <milestone type="sig" n="Uu2v"/>
                   <mw type="pageNum" rend="slant(upright)">3270</mw>
                   <lb/>ultimate</term> word on the page. But it’s not.

The term element here is italicized, and hence the rend of mw needs to indicate that its content is not italicized.

Another example, more commonly encountered. Note in this case that the encoder has implemented a renditional default, such that mw is always right justified in order to match the catchwords at the bottom of each page:

          
          <l>I never had cause to love him more than<l>
          <mw type="sig" rend="align(center)">A1</mw>
          <mw type="catch">All</mw>
          <pb n="4">
          <milestone type="sig" n="A1v">
          <mw type="pageNum" rend="align(left)">4</mw>
          <l>All the butterflies above the flowers.<l>

Forme work: renditional issues

Abstract

Encoding Instructions (new P5 version)

Examples