Dr Notis Toufexis wrote:
> Dear all
>
> while transcribing a 16th c. Greek manuscript (the Early Modern Greek
> Grammar of Nicolaos Sophianos) I encountered a problem problem with a
> heading which is not laid out on the page in the usual way (with line
> breaks before and after). I have uploaded a picture on Flickr:
>
> http://www.flickr.com/photos/notix/3652899435/
>
> Marked with yellow are the two headings (the first reads "About the
> categories of the twenty four letters", the second "About consonants").
> The default for headings in the manuscript is the second one, the
> "inline" first one is just an exception.
>
> Have you had any similar cases in your manuscripts? My tentative
> solution would be to use <div>'s and @rend="inline" or something similar
> for the first type and manipulate accordingly my xsl stylesheets. Any
> better ideas?
I think it depends more on the nature of the material you are marking
up. Does the first heading introduce a new section? Is it just that it
doesn't have linebreaks? Since what you are (most likely) marking up
with elements like <div> is the intellectual structure, rather than
focussing on the original presentation I would mark it up just as you
suggest but with the @rend on the <head>. So something like:
<div>
<!-- previous div here -->
</div>
<div>
<head rend="inline">About the categories of...</head>
<!-- div content here -->
</div>
<div>
<head>About consonants</head>
<!-- div content here -->
</div>
In your XSLT matching a div with a child head who has a rend attribute
of 'inline' is fairly straightforward tei:div[tei:head/@rend='inline']
so if you are looking to reproduce this appearance in HTML/CSS it
wouldn't seem too difficult. I guess the real question you're asking is
whether the intellectual structure of the <div> is inline or the
slightly different formatting which lets you know this is a <head> is
what is inline. I don't think either is wrong, but I'd be tempted to
put the @rend on the element containing the text as that seems (for some
reason I'm not wholly willing to trust) as more accurate. Partly it is
because the next line (presumably containing some text that is part of
this <div> juts out further into the left-hand margin, making it look to
me like the <div> (or perhaps just its child <p>) isn't inline, just the
<head>.
My two pence for whatever that is worth these days,
-James
--
Dr James Cummings, Research Technologies Service, University of Oxford
James dot Cummings at oucs dot ox dot ac dot uk
|
