Menu

#108 Guidelines for space avoiding hole in support, etc.

9.0
done
guidelines (82)
5(medium)
2019-10-15
2016-07-07
No

Add examples and suggested values for <space type="hole|damage|decoration|indent|centering|ditto|field"/> as discussed on the Markup list Re: encoding intentional hole in support of text (see e.g. http://lsv.uky.edu/scripts/wa.exe?A2=ind1607&L=markup&P=1277). To be discussed whether this belongs on the regular page for vacat, or a new page should be created.

Discussion

  • BODARD Gabriel

    BODARD Gabriel - 2016-07-19
    • status: unread --> pending
    • assigned_to: Scott DiGiulio
     
  • BODARD Gabriel

    BODARD Gabriel - 2016-07-19

    Scott will poke around and will then reply to Markup again.

     
  • BODARD Gabriel

    BODARD Gabriel - 2016-09-20
    • Group: future --> 8.23
     
  • Scott DiGiulio

    Scott DiGiulio - 2017-01-24

    As we discussed in the previous EDAG meeting, we're generally all in agreement that space with some kind of attribute seems to be the best way to do this; the important thing is to document if people know and want to mark the reason for the space, which would clarify the distinction between, e.g., a vacat and some formal feature of the support prior to the inscribing of the text. I'll email Markup in order to get some more examples and suggested vocabulary.

     
  • Scott DiGiulio

    Scott DiGiulio - 2017-03-20
    • Group: 8.23 --> future
     
  • Scott DiGiulio

    Scott DiGiulio - 2017-04-18
    • Group: future --> 8.24
     
  • BODARD Gabriel

    BODARD Gabriel - 2017-10-17
    • Group: 8.24 --> 9.0
     
  • Scott DiGiulio

    Scott DiGiulio - 2017-12-03

    (Very) short prose added to the Guidelines page for vacat (other), along with several suggested values there.

     
  • BODARD Gabriel

    BODARD Gabriel - 2017-12-04

    Should we also add some suggested values to the schema, or is that best left completely open, do we think?

     
  • Emmanuelle Morlock

    I wouldn't mind having these suggested values added to the schema, but on the other hand, I think it is ok to leave it open.

     
  • Scott DiGiulio

    Scott DiGiulio - 2018-02-20

    General consensus, at Feb. 20 EDAG, is that having at least some suggested values would be valuable. Addtionally these values would help to resolve questions raisedabout how to indicate indentation, etc., at FR79, since <space> allows for a number of attributes that cannot be placed on <lb>.

     
  • BODARD Gabriel

    BODARD Gabriel - 2018-04-17

    If we want to recommend a few values (and their definitions) to the ODD, I suggest values such as:

    • obstacle (a preexisting hole, blemish, protrusion, decoration, damage or other feature on the surface that the scribe avoids writing over)
    • indent (space at the beginning or end of a line to indent or centre a line of text)
    • break (a section or other unit break represented by whitespace on the original text)
    • others to be added only as concrete examples occur?
     

    Last edit: BODARD Gabriel 2018-04-17
  • Scott DiGiulio

    Scott DiGiulio - 2019-10-15
    • status: pending --> done
     
  • Scott DiGiulio

    Scott DiGiulio - 2019-10-15

    Will add a little more prose to make this clearer, re-paragraph a bit more to help clarify what we actually mean by <space> in EpiDoc

     

Log in to post a comment.