Conal-Tuohy
commented
5 years ago Thanks! I had noticed this myself and hadn't got around to raising it as an issue. It certainly looks ugly where it produces these sporadic extra-long lines.
This is slightly different in P5, since the @corr attribute is replaced with a <corr> element, which can itself contain a <lb/>; so it's possible to include the position of the line break in both the original and normalized form. It seems to me I should implement this in the P5 conversion step, so that (if I understand the convention correctly) it performs the following transformation:
<orig reg="ejusdem">ejus­<lb/>dem</orig>⇨
<choice><orig>ejus-<lb/>dem</orig><reg><lb/>ejusdem</reg></choice>Is that right?
We used orig-reg to handle words that Newton hyphenated.
See Keynes 12, ALCH00001, the line near the top that begins "7. Lapis componitur . . ." which is a good example. http://carbon.dlib.indiana.edu:8215/newton-dev/mss/dipl/ALCH00001/
In the diplomatic, we used a ­ entity to draw the hyphen and an
element to wrap the line. In the normalized, we wrapped the line then wrote the reg value as the first word. (I don't remember the details of the XSL I'm afraid.)
In 8220, the diplomatic version works like 8215, but in the normalized version the line isn't wrapping to match Newton's new line as we try to do.