[jlreq] todo: Update Ruby terminology wiki and solicit feedback from clreq (#385)

kidayasuo has just created a new issue for https://github.com/w3c/jlreq:

== todo: Update Ruby terminology wiki and solicit feedback from clreq ==
todo for @murata2makoto, from JLReq TF meeting on 2023-10-31.

- Update Ruby terminology [wiki](https://github.com/w3c/jlreq/wiki/English-ruby-terminology) based on the discussions at the meeting
- Clarify if there are semantic difference between “rb/rb/rt/rt”and “rb/rt/rb/rt”
- Solicit feedback from clreq folks.

Below is from meeting notes:
- data: a [presentation](https://docs.google.com/presentation/d/1x-cIsFinp4MKQkNve4UWAQ0_GTR22hX2PwIYc6MrOS4/edit#slide=id.g122e38f3b6d_0_50) and a [wiki](https://github.com/w3c/jlreq/wiki/English-ruby-terminology)
- We have decided not to use Mono, Group and Jukugo Ruby in ruby layout descriptions in jlreq-d because these terms have an assumption that the base text is a string of Kanji and the ruby annotation is a string of Kana. We want to generalise the ruby layout in jlreq-d so it does not have assumptions on the script used for the base or the ruby annotation. These terms will be touched on in side notes.
- Remaining issue regarding the terminology is if we define a name for the combination of the base text and ruby annotation. Kida: When I drafted a proposal of line-foldable ruby I often felt the need for the term. Bin-sensei: the term ‘Oyamoji-gun (base text group)’ was used in JIS X 4051. - no conclusion
- Murata: related to the topic do we need a term for “rb/rb/rt/rt”and “rb/rt/rb/rt” ? I do not know if they are differ in the resulting layout. todo: need to clarify.
- Murata: When we say “ruby” what does it mean? It was sometimes used to describe the annotation attached, and sometimes it means the feature as a whole. The annotation part should be called “ruby annotation” for clarify.
- For para-ruby and sou-ruby, JLReq TF folks thinks they can be used as-is.


Please view or discuss this issue at https://github.com/w3c/jlreq/issues/385 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Sunday, 19 November 2023 07:54:00 UTC