Hi all, A first draft of the reorganized version of the CO chapter incorporating the new Ruby section can now be seen here: https://teijenkins.hcmc.uvic.ca/job/TEIP5-issue-2054-ruby/lastSuccessfulBuil... Please take a look and let me know what you think. I haven't yet added links/refs from other chapters because I want to make sure the ids etc. are stable before I do that. Since Nagasaki-sensei has kindly provided translations of the glosses and descs on the Spec pages, the 日本語 links at the bottom of those pages will hopefully be useful. Cheers, Martin On 2021-02-03 7:58 a.m., Martin Holmes wrote:
Hi all,
Thanks for the feedback on the location for the Ruby prose. The consensus is clear -- it should be in core -- and the comments suggest that the most appropriate approach will be to integrated it with the content relating to glosses, which is currently in 3.3.4, "Terms, Glosses, Equivalents, and Descriptions". That sub-subsection is already quite long, so what I propose to attempt is this:
Take 3.3.4 "Terms, Glosses, Equivalents, and Descriptions" and 3.3.5 "Some Further Examples" and make them into a new subsection (i.e. one level higher), which will become 3.4.
Title the new section "Terms, Glosses, Equivalents, Descriptions, and Ruby". (JJ suggests that terms belongs elsewhere, but that would be a major reorg, and I don't think we have time for that right now.)
Create subsections:
3.4.1 "Terms and Glosses" covering the first part of what is now 3.3.4. This would also include the "Further Examples" bit, which is really an extension of this.
3.4.2 "Ruby Annotations" containing the new prose already proposed.
3.4.3 "Equivalents and Descriptions" containing the part of what is now 3.3.4 which discusses altIdent, desc, and equiv; I think this is a different topic, really, from glossing terms.
I'm doing this work in a separate branch:
https://github.com/TEIC/TEI/tree/issue-2054-ruby
which I'll merge dev into steadily as I go, to minimize later merge conflicts. I'll also set up a build job for this branch on my Jenkins when the initial work is done.
The time is relatively short, but I think we can get there before the freeze.
I'll post the meat of this on the ticket too, for the record.
Cheers, Martin
-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca