Dear Peter,

thanks for your comments.

I'm using <sourceDoc>, <surface>, <zone> and <line>, because it is precisely
our intention to record 'how exactly the text appears on the page'. The
output is a topographic, diplomatic transcription, which is correlated with
the facsimile - and the transcr module is (with some minor modifications)
exactly what we need in order to accomplish that.

Of course we were discussing extensively whether we should produce two
transcriptions, one for the diplomatic rendering (the topographic or
documentary transcript) and a linear one for better reading. And in the end
we will. But for pragmatic reasons we decided to produce only the
documentary one at this stage.

Kind regards


Von: TEI (Text Encoding Initiative) public discussion list
[mailto:[log in to unmask]] Im Auftrag von Peter Robinson
Gesendet: Dienstag, 26. November 2013 16:13
An: [log in to unmask]
Betreff: Re: [TEI-L] Using <rs> in documentary markup

Dear Oliver

Following up on Elena Piearazzo's comments, on the likely problems of using
<line> with other TEI mark-up -- you have a very simple solution. Use

Indeed, in general, unless you are working in the rather rarefied world of
genetic manuscript transcriptions, where indeed the precise and efficient
representation of how exactly the text appears on the page (and, in what
order it was written, etc) is all-important, you are generally better off
using <lb/> (and <pb/>, <cb/>, <milestone/> etc), used as defined in P5, and
giving you access to <rs> and loads else. Of course, using <lb/> to indicate
line breaks, as opposed to <line> to hold the content of the line, presents
other challenges: it makes the styling of each individual line of text
somewhat more difficult to achieve -- difficult, but not impossible.

One might comment, as I have elsewhere, that it was a mistake for the
editors of P5 to choose to include the system for encoding genetic editions
developed by Pierazzo and others under the rubric "Representation of Primary
Sources", with the clear implication that this should be used for
transcription of all manuscript materials.  If you need to use <rs> etc (not
to mention information on the intellectual structure -- the poems, verse
lines, chapters etc of what you are encoding), so that text disposition on
the page and writing acts are not all-important, then you should not use
this system.


On 22 Nov 2013, at 07:41, Oliver Gasperlin wrote:

Dear List,

I'm sure we are not the only ones doing manuscript transcriptions using
<line> for topographic lines.
But did anyone try to mark up persons or personal names within those kind of
And how would you do it, given that <rs> and <name> are not valid within

Would that be a case for a feature request? 

Kind regards
Oliver Gasperlin

-----Ursprüngliche Nachricht-----
Von: TEI (Text Encoding Initiative) public discussion list
[mailto:[log in to unmask]] Im Auftrag von Oliver Gasperlin
Gesendet: Donnerstag, 21. November 2013 12:33
An: [log in to unmask]
Betreff: [TEI-L] Using <rs> in documentary markup

Dear all,

I would like to distinguish persons within my documentary markup, using

<line>My personal life during the administration of <rs type="person">Col.

But I'm missing the core <rs> and <name> Elements in the declaration of

May there be an argument for integrating them within model.linePart? 

Or is it something one is not supposed to do on the documentary level?

I'm looking forward to all comments on this.

Kind regards
Oliver Gasperlin 


pagina GmbH - Publikationstechnologien

Oliver Gasperlin
- Digital Humanities -
Telefon: (07071) 9876-11
Telefax: (07071) 9876-22
E-Mail: oliver.gasperlin

Herrenberger Straße 51
D-72070 Tübingen

Handelsregister Stuttgart - HRB 380249
Geschäftsführer: Tobias Ott

Peter Robinson
Bateman Professor of English
#311, Arts Building, 9 Campus Drive, University of Saskatchewan
Saskatoon SK S7N 5A5, Canada
ph. (+1) 306 966 5491