Forme work: renditional issues

forme work rendition catchword
rend mw fw

Encoding renditional distinctions within mw

In cases where you want to record the rendition of some part of the forme work, we recommend using the rend attribute on fw wherever possible. Catchwords and titles are the only type of forme work likely to contain any renditional information. If only part of the catchword or title is renditionally distinct, use hi as necessary to indicate the renditional shifts within it. It is probably not useful to include any content-based encoding within catchwords (e.g. persName, etc.) since these terms do not function in forme work as they do in the main stream of the text. For instance, if the book title contains the name of the main character, and is repeated at the top of every other page, encoding the name with persName will overrepresent the use of that name in the text. You can compensate for this by excluding forme work from certain kinds of searches, but if in fact the name is never considered to function as a name, then it should not be encoded as one.

While in most cases we recommend encoding delimiters such as quotation marks, brackets, etc. using the rend attribute, in the case of forme work we recommend that they be encoded as #PCDATA, since they do not function as delimiters in any meaningful sense within the catchword.

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

Examples

Example 1.

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

    <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"/>
    <fw type="pageNum" rend="slant(upright)">3270</fw>
    <lb/>ultimate</term> word on the page. But it’s not.