Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#25 Page on "diplomatic transcription" needed in GL

accepted
guidelines (51)
2
2014-09-18
2006-03-14
BODARD Gabriel
No

In noproblems.xml there is a note: The editor may
introduce modern spacing, punctuation, accents and
capitalization without comment unless the text is
contained within a <div type="diplomatic">.

We seriously need to think this issue though: do we
actually encode a separate diplomatic edition
(optionally), or do we want to offer this as a
stylesheet option to convert the tagged text to a
diplomatic rendition? (The latter ought to be possible,
but is there anything we could not do this way that we
*could* achieve with a separately marked up section?)

Discussion

  • Elli Mylonas
    Elli Mylonas
    2014-05-29

    • status: open --> accepted
    • assigned_to: BODARD Gabriel
    • Group: --> Next_Release_(example)
    • Priority: 5 --> 1(low)
     
  • Elli Mylonas
    Elli Mylonas
    2014-05-29

    decisions made, put them in guidelines

     
  • BODARD Gabriel
    BODARD Gabriel
    2014-05-29

    • summary: Think through "diplomatic transcription" --> Page on "diplomatic transcription" needed in GL
    • Priority: 1(low) --> 5(medium)
     
  • BODARD Gabriel
    BODARD Gabriel
    2014-07-24

    I've created a page at http://www.stoa.org/epidoc/gl/dev/trans-diplomatic.html ([r2220])

    This needs some more work, but I wanted to get a first draft in before the code freeze today. We also need to indicate in many more places in the Guidelines differences between diplomatic and interpretive rendering of markup features.

    It would also be useful to be able to produce a diplomatic rendering alongside the various leiden-styles in the GLs. Perhaps even everywhere? Discuss.

     

    Related

    Commit: [r2220]


    Last edit: BODARD Gabriel 2014-08-28
  • BODARD Gabriel
    BODARD Gabriel
    2014-09-18

    • Priority: 5(medium) --> 2