TEIC
Minor error in rendering of DOI idno in biblStruct entry
Item 12 here:
http://www.tei-c.org/release/doc/tei-p5-doc/en/html/BIB.html#index-back.1_div.6_div.2
shows the problem: the idno containing a DOI URL runs into the following journal or monograph title.
Curiously, this doesn't seem to happen if the <idno type="DOI"> is followed by a <ptr>
We flip-flopped on whether it should be DOI or doi, so maybe the FO code got fossilized with the wrong case...
Stylesheets co-operative group worked on this today, and did not resolve the spacing issue -- it's complicated -- but other changes were made to the processing of DOI idnos which are good. See today's commits from @sydb for details. Basically we are now turning DOIs into links, but doing it in a Stylesheets step based on prefixing a $DOIResolver variable to them; this means that we were able to remove all the explicit protocol+resolver prefixes from the BIB chapter, because they should not be there (see https://github.com/TEIC/TEI/issues/1294), while actually creating clickable links in the output. The spacing issue remains to be figured out. It looks like the final element in a monogr or an analytic should have not only a space after it but a period followed by a space; otherwise, children of monogr or analytic should be followed by a space (or, to approach it another way, they should all be preceded by a space except for the first one).
First fix broke the build because of expected-results and a newly-triggered bug in anchor creation. Fix submitted in commit 59dda29.
On the BIB page, there are three distinct lists of bibliographic items. F1, the largest list, has been manually curated and is all <bibl>s; it looks good. F2 and F3, containing only 196 entries between them, are both <biblStruct>s, and they look ludicrous; they're alphabetized by surname but the surname does not come first, they have spacing issues, and there are punctuation problems throughout.
I think we should simply convert the remaining <biblStruct> to <bibl>s and have done with it. We can then curate them according to a specific style guide which we choose (assuming we haven't chosen one already -- not sure about that), and it will be WAY quicker (believe me) than trying to process <biblStructs>.
@laurentromary might have a view on this since I believe one of his students was responsible for providing the biblStructs concerned