display of <lb/> inside <lem>

[arlogriffiths]

I have the feeling that the display is not yet as foreseen in EGD 9.1.6, which I cite:

• empty elements representing transition points (<lb/>, <pb/> and <milestone/> of any kind) shall, however, be included in both lemmas and readings
• the purpose of this is primarily to show the fact that such a transition is present (or was indicated as present, not necessarily always in the right place, by a previous edition)
• any attributes of these elements present in the edition must mandatorily be retained in the lemma (contrary to the suggestion of the first release version of this EGD)
• we foresee that all of these elements will be displayed as a simple / character when they appear as a lemma (thus, since a pagelike partition will always be followed by a line beginning, these together will display as //)
• the / character will be displayed contiguously with the surrounding text if the element in question has @break="no", and with spaces on both sides if the element does not have @break="no"
• remember that when a lemma extends across such a boundary, the @loc of the apparatus entry must be the number of the line where the lemma begins
• in display, an indication that the lemma extends into the next line will probably be added automatically if an <lb/> element is present within the lemma

Example of code:

<app loc="A7"><lem>rājadhā<lb n="A8" break="no"/>ṇnī</lem><note>....</note></app>.

Example of current display:

[michaelnmmeyer]

OK for the first point you underline (use of /), but I am not sure what @danbalogh has in mind for the second one ("an indication that the lemma extends into the next line"). Should I add a tooltip on the lemma that says e.g. "Lemma that spans several pages/lines"?

[danbalogh]

I think a tooltip is unnecessary and what I or we meant by "indication" may have been simply the presence of the / sign(s). Though actually, I am not at all sure that displaying slashes in the lemmas would be better than the current display. But I also like Axelle's (?) display on github.io, which shows the next line number at the beginning of the lemma in addition to displaying a slash where the break is:

So the bottom line on my side is that the above would be best, since the fact that the lemma is over a break is evident right from the start, and since it is slightly more compact, because if the line break is displayed as a number, then that would be iterated in every reading, whereas here only a slash sign is iterated.

Anyway, in this matter too, whatever you two can agree on will be OK for me; just let me know what to put in the guide.

[arlogriffiths]

I think was was meant by "indication" is that the display would insert en-dash and number of the line where the <lem> ends, based on the last value of <lb n="..."> contained in it, exactly as in Axelle's set up. I agree with Dan's verdict that we need to reproduce the same on dharmalekha.info.

@Dan: as for the revision of EGD, I was actually wondering it might not be possible, or even desirable, to see less about presentational aspects in this context. Certainly nothing needs to be changed about how we encode.

[danbalogh]

I'm perfectly OK with saying less or nothing about display in the EGD, here and elsewhere. As you know, in my view display is an altogether separate matter from encoding. I think in many places, the first EGD only said things about display because you wanted the not-yet-implemented display ideas to be recorded somewhere.

[michaelnmmeyer]

OK for the handling of lb elements (line numbers ranges and use of /).

Now, we also have pagelike and gridlike milestones in the same context. Axelle's code does not display pagelike milestones at all, and represents gridlike milestones with ‡. Is this OK?

[danbalogh]

Pagelike milestones in lemmas should be displayed as a / just like page breaks, so that with the invariably following line break they become //. I like the idea of representing gridlike milestones with a ‡, but in that case I think that the regular display of those milestones should also include the same character, before the unit and number.

[arlogriffiths]

I agree with Dan's response.

@Dan: now that the presentation of files encoded as per our EGD is become more and more concrete, I think we can reduce or remove altogether what we say about presentational aspects in the next version. Feel free to propose the relevant cuts.

[danbalogh]

OK, noted.

[arlogriffiths]

@michaelnmmeyer — I think you can close this once the display has been modified as per instructions above.

[danbalogh]

I agree.

[danbalogh]

@michaelnmmeyer , please close this issue if the display has been implemented.