You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would we be able to use <div> (or something else) to thread the various interpolations back to their “parent” <div>, where appropriate? I like the idea of making explicit in the markup some of the internal connections and reiterations of the book.
I think marking this up would be a good idea--but I think it would require a different strategy. The divs are not granular enough (you want to be able to the interpolated/reiterated text, not just the section from which it came, right? Would something like this work, using and refs?
<lbn="100201"/>raised his cap abruptly: <spanxml:id="l100201">the young woman
abruptly bent and with slow care
<lbn="100202"/>detached from her light skirt a clinging twig.</span>
And, later in the same file:
<p><lbn="100440"/><reftarget="#l100201">The young woman with slow care detached from
her light skirt a
<lbn="100441"/>clinging twig.</ref>
There is, in "Wandering Rocks" a clear "original," and "reference" structure I think. It would be nice if were bidirectional (that the source pointed to where it was later interpolated), but off the top of my head I can't think of an obvious and semantic way of doing it. (Simply adding more ptrs/links--as folks do when they make HTML footnotes, with links back to the text seems wrong here.) I'd like to hear others thoughts on the best approach, but once there is consensus I'm happy to hop in and add the appropriate markup. (Note also, I've just created a rather weak id for the source span using the line number... I don't think that's a very good idea.)
The text was updated successfully, but these errors were encountered:
What about using a combination of <seg> and <span>?
The <seg> element may be used at the encoder's discretion to mark any segments of the text of interest for processing. <span> associates an interpretative annotation directly with a span of text.
For example:
<lbn="100314"/><saidwho="Blazes Boylan">―Can you send them by tram? Now?</said></p>
<p><segxml:id="100315"><lbn="100315"/>A darkbacked figure under Merchants' arch scanned books on the
<lbn="100316"/>hawker's cart.</seg>
<lbn="100317"/><saidwho="Thornton's girl">―Certainly, sir. Is it in the city?</said>
<p><lbn="100520"/>They went up the steps and under Merchants' arch. <segxml:id="100520">A darkbacked
<lbn="100521"/>figure scanned books on the hawker's cart.</seg>
<lbn="100522"/><saidwho="Lenehan">―There he is,</said> Lenehan said.
@yellwork asks:
@c-forster responds:
I think marking this up would be a good idea--but I think it would require a different strategy. The divs are not granular enough (you want to be able to the interpolated/reiterated text, not just the section from which it came, right? Would something like this work, using and refs?
And, later in the same file:
There is, in "Wandering Rocks" a clear "original," and "reference" structure I think. It would be nice if were bidirectional (that the source pointed to where it was later interpolated), but off the top of my head I can't think of an obvious and semantic way of doing it. (Simply adding more ptrs/links--as folks do when they make HTML footnotes, with links back to the text seems wrong here.) I'd like to hear others thoughts on the best approach, but once there is consensus I'm happy to hop in and add the appropriate markup. (Note also, I've just created a rather weak id for the source span using the line number... I don't think that's a very good idea.)
The text was updated successfully, but these errors were encountered: