On Fri, Jul 17, 2009 at 7:41 PM, Daniel Paul
O'Donnell<[log in to unmask]> wrote:
> As I understand the layout, it doesn't look that much different from
> standard displays you see from print things on the web as well. So it looks
> like basic strikeout and square brackets would work.
Courtney's original question is whether there is "a standard or
generally accepted way to display the corrections" (i.e. in a web
browser view), and strikeout/square brackets (as you might find in a
print edition) are certainly one way of doing it. But I'd say there is
not one standard for display - although there are lots of options.
(Sorry I don't have time to find examples for all of these, but I've
certainly seen them, perhaps others on the list who recognize these
will provide links to projects?)
One way (also borrowed from print editing) would be to provide one
view in the "main text" with links to corrections (if you are looking
at the "original" view) or original/uncorrected readings (if you are
looking at the "editor's/corrected" view) - these readings might be in
some apparatus at the bottom of the web page, or in a margin, or in
another page viewed in a pop-up - there are lots of possibilities.
Another option (more hyper-texty than print-like) would be to view the
alternatives in mouseovers - say, in an "editor's/corrected" view any
word or phrase that has been corrected is underlined, and if you mouse
over you'll see the original/uncorrected version in a tooltip.
In any case imo it's nice to provide both alternatives as "main view",
and let the reader/user of your project decide which version they
prefer to use. And of course the underlying TEI markup would be the
same for all of these, the only difference is in the processing.
Hope this helps,
> Stuart, how did this approach lead to poorly formed XHTML? There's nothing
> inherent about the TEI that should, surely? In a P4 SGML document I used a
> syntax that anticipated choice in this context to a certain extent and even
> with the rudimentary pre XSLT tools available to me at the time had no
> trouble getting valid XHTML out of it. Or is just a bug still needing to be
> squashed in your sheets?
> Courtney Michael wrote:
>> Thank you Stuart! This is exactly what we’re looking for. Any more example
>> from the list greatly appreciated!
>> On 7/16/09 3:53 PM, "stuart yeates" <[log in to unmask]> wrote:
>> Courtney Michael wrote:
>> > We are looking for an answer to the former question – for examples or
>> > models actually.
>> > We are displaying transcripts on the web and want to see if there
>> is a
>> > standard or generally accepted way to display the corrections.
>> > Any examples appreciated.
>> We have a much annotated / corrected document at:
>> This is an newspaper cutting stuck in the front cover of a book
>> and then
>> Alas our approach has led us to badly-formed HTML, which we're now
>> paying for as we try to generate valid XHTML for inclusion in
>> ebooks and
>> learning objects.
>> Stuart Yeates
>> http://www.nzetc.org/ New Zealand Electronic Text Centre
>> http://researcharchive.vuw.ac.nz/ Institutional Repository
> Daniel Paul O'Donnell
> Associate Professor of English
> University of Lethbridge
> Chair and CEO, Text Encoding Initiative (http://www.tei-c.org/)
> Co-Chair, Digital Initiatives Advisory Board, Medieval Academy of America
> President-elect (English), Society for Digital Humanities/Société pour
> l'étude des médias interactifs (http://sdh-semi.org/)
> Founding Director (2003-2009), Digital Medievalist Project
> Vox: +1 403 329-2377
> Fax: +1 403 382-7191 (non-confidental)
> Home Page: http://people.uleth.ca/~daniel.odonnell/
Dot Porter (MA, MSLS) Metadata Manager
Digital Humanities Observatory (RIA), Regus House, 28-32 Upper
Pembroke Street, Dublin 2, Ireland
-- A Project of the Royal Irish Academy --
Phone: +353 1 234 2444 Fax: +353 1 234 2400
http://dho.ie Email: [log in to unmask]