I agree that these "breaks" dividing chapters into smaller units can be
hard to divide into <div>-like divisions. What if a single work uses
both three-asterisks as a break and a blank line as a
slightly-less-significant break? Do we now have two levels of <div>
(even within a chapter)?
In a non-academic, HTML-ish context I have even marked up such breaks as
<lb rend="space"/> vel sim., although I concede that is a bit cludgey.
This sort of thinking has led me in my own writing to always flag "theme
breaks" with a new heading (making it unequivolcally a new <div>), but I
appreciate we can't rely upon our sources always to be so reasonable.
Joshua Hutchinson a écrit :
> I've always used <milestone> for these breaks.
> <div> didn't really seem appropriate. For instance, in a fiction
> work, I'd group the chapter as a whole in a <div>. But sometimes the
> author would mark a scene change or that some time passed "off-stage"
> by having a blank line or maybe a * * * between two paragraphs. This
> didn't seem to be a full change in <div>.
> In Project Gutenberg, we extended the <milestone> tag as:
> <milestone unit="tb" rend="<type of break>" />
> where the type of break defaults to blank line, but could be a
> horizontal line or a series of asterisks.
> On 10/19/07, M. Alan Thomas II <[log in to unmask]> wrote:
>> Jon Noring <[log in to unmask]> wrote:
>>> I'm curious to know how TEI markup people handle "theme breaks" or
>>> "scene breaks" in ordinary prose? I've looked around in the TEI
>>> documentation but did not yet find any mention.
>> The sections of text on delineated by the breaks seem like <div>s to me.
>> That is to say, from one break to the next constitutes a <div>. This may or
>> may not be an appropriate solution for any given vision of the structural
>> aspects of a text, and such structural analysis may or may not be
>> appropriate for any given project.
>> As for the break itself, if and how it is marked, outside of the fact that
>> one <div> ends and another begins, probably depends on whether the project
>> is more concerned with semantic content, physical structure, or what. If it
>> doesn't care about incidental physical aspects of a text, marking the
>> structure using <div>s is all of the semantic content you need, assuming
>> that the ornamentation does not convey anything other than "there is a break
>> here." If the project is more interested in marking up the physical object,
>> or if there is an image that conveys some further meaning, the relevant
>> element can appear between the <div>s. I can't recall what the tag for
>> "this space intentionally left blank" is, but for any sort of image it would
>> be <figure>.
>> I hope that helps.
>> In service,
>> M. Alan Thomas II
Dr Gabriel BODARD
(Epigrapher & Digital Classicist)
Centre for Computing in the Humanities
King's College London
7, Arundel Street
London WC2R 3DX
Email: [log in to unmask]
Tel: +44 (0)20 7848 1388
Fax: +44 (0)20 7848 2980