Re: correspondence encoding problems: letter headings
Conal Tuohy <[email protected]>
| Newsgroups | gmane.text.tei.general |
|---|---|
| Message-ID | <CAErBQuQykZagg0r-UT7sHFLwrd8W3T8Wzi6f6u7MyCbWHrnB2A@mail.gmail.com> |
Ron, your example of letters containing multiple letterheads reminded me to
suggest the use of <fw> ("forme work")
*http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-fw.html
<http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-fw.html>*
*Quoting
from http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHSK
<http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHSK>*
The fw <http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-fw.html>
element
> may be used to encode any of the unchanging portions of a page forme, such
> as:
>
> - running heads (whether repeated or changing on every page, or
> alternating pages)
>
>
> - running footers
>
>
> - page numbers
>
>
> - catch-words
>
>
> - other material repeated from page to page, which falls outside the
> stream of the text
>
> Because it's a member of the model.global class, you may deploy it freely!
Conal
On 23 February 2017 at 21:38, Ron Van den Branden <
[email protected]> wrote:
> Hi Paul and Peter,
>
> Many thanks for your replies, I'll comment on both here.
>
> Thanks, Paul, for correcting my limited assumptions about <head>, and
> pointing me to the corresponding <trailer> element. I agree they make an
> appealing pair for encoding letterheads occurring at the start and end of a
> letter.
>
> Peter, your proposal is elegant and tempting as well.
>
> Yet, what about letters written on multiple pages, each containing a
> letterhead (and not necessarily the same)? I think this would make both
> approaches less straightforward. For the sake of the argument, I'll assume
> the structure of a 2-page letter, both containing a leading and trailing
> letterhead.
>
> -<head> / <trailer>: since they can't be intermingled with <p>'s, each
> page would have to be transcribed in a separate <div>, instead of being
> marked with <pb/>:
>
> <div type="letter">
> <div type="page">
> <head type="letterHead">...</head>
> <opener>...</opener>
> <p>...</p>
> <trailer type="letterHead">...</trailer>
> </div>
> <div type="page">
> <head type="letterHead">...</head>
> <p>...</p>
> <closer>...</closer>
> <trailer type="letterHead">...</trailer>
> </div>
> </div>
>
> This wrapping of pages in <div>s seems to go against the logical content
> of the document, especially when a paragraph is split over a page boundary
> (which has been the motivation for <pb/>).
>
> -<div type="letterHead">: this would require the <div type="letterBody">
> to be split for each new page:
>
> <div type="letter">
> <div type="letterHead">...</div>
> <div type="letterBody">
> <opener>...</opener>
> <p>...</p>
> </div>
> <div type="letterHead">...</div>
> <pb/>
> <div type="letterHead">...</div>
> <div type="letterBody">
> <p>...</p>
> <closer>...</closer>
> </div>
> <div type="letterHead">...</div>
> </div>
>
> I can imagine that both could be linked with @next / @prev, but still it
> seems highly artificial.
>
> OTOH, and that's what I like about the flexibility of <figure>, this is
> perfectly valid:
>
> <div type="letter">
> <figure type="letterHead">...</figure>
> <opener>...</opener>
> <p>...</p>
> <figure type="letterHead">...</figure>
> <pb/>
> <figure type="letterHead">...</figure>
> <p>...</p>
> <closer>...</closer>
> <figure type="letterHead">...</figure>
> </div>
>
> I had to argue with myself about the <figure>-ness of letterheads, but the
> fact that they're typically the result of a lay-out process in the design
> of the letter paper seems to be an argument in favour.
>
> Best,
>
> Ron
>
>
> On 22/02/2017 16:52, Peter Stadler wrote:
>
>> Hi Ron,
>>
>> it would mean a little restructuring but what about
>> <div type="letter">
>> <div type="letterHead"/>
>> <div type="letterBody"/>
>> </div>
>>
>> Best
>> Peter
>>
>>
--
Conal Tuohy
http://conaltuohy.com/
@conal_tuohy
+61-466-324297