PietroLiuzzo
commented
4 years ago i understand that this sort of changes are a bit hard to understand out of practice. one first application is the ability to enter one reference to a range (you do not need two locus elements for example to refer to a passage defined also by lines), let me give you some application example. you use ref[@cRef] somewhere within a file, clicking there will take you to the passage referenced in the text view at that exact passage. you can refer to a precise passage in any text and transcription without need to point to an xmlid, which is only one option. most of this was implemented thanks to the existing of texts which you have encoded with multiple structures, which is great and can now be supported. so, any structure, but secure flexible referencing. another practical application is citation in publications. e.g. in f. 1ra line 4 to f 3vb line 3 could become a reference with a link to a betamasaheft entity which is unambiguous like MS.1ra4-3vb3 or we could theoretically map a reference to (making it up!) amda seyon e.g. a sentence numbered 45 in the transcription to 13[marrassini].3 (line 3 on page 13 of marrassini edition) and 46[krop].8 (line 8 on page 46 of krop edition). so that either .45, 13[marrassini].3 and 46[krop].8 point to the same section, and eventually you can jump from one to the other if they are encoded.
thea-m
This contains a lot of examples and prose about the new support for referencing parts of the text based on div, pb, cb, lb, l.