JLReq TF meeting notes 9/28

[kidayasuo]

Attendee

bin-sensei, kobayashi-san, murakami-san, murata-san, setsu-san (xfq), shimono-san, tahara-san, tajima-san, Nat & kida

UAX#50 AJ1 harmonisation proposal

• Richard kindly reviewed the proposal to improve the language. Got feedbacks on GH.
• Taro-san @ Adobe analysed AJ1 font sources to confirm that the proposal makes AJ1 fonts UAX#50 compliant. It was confirmed according to the analysis. ^^/
• todo: Shimono-san to integrate feedbacks from Richard.
• todo: Kida to send a note to Richard to ask him if he could send it to UTC.

User requirements for TTS of ruby

Murata-san developed a document describing user requirements for TTS of ruby. It was originally a part of the simple ruby document. JLReq TF would like to make it an official W3C document like simple ruby.

• todo: Kida to send a note to Richard to get his OK to make a repository at W3C/ruby-t2s-user-requirements.

The next major revision of JLReq, the TOC

Following the previous meeting discussed the table of contents of the next major revision, the digital native version of JLReq.

Discussed on an early draft kida sent to the list on 9/28 9:38 JST.

top level

• murata-san: would like to add “universal design” as the top level themes → agreed

how

• nat: For most engineers Japanese line layout is very different → let’s add some basic introductions
• kobayashi-san: it might be a good idea to describe alternative methods for lower priority features → agreed
• bin-sensei: there aren’t much documents re: line progression. would like to strengthen jlreq on this point → agreed
• nat: should cover baseline and font metrics. there aren’t enough metrics in fonts for proper Japanese line layout → agreed. please write it up
• kida: current descriptions in JLReq have an implicit assumption on pages and books. would like to remove such an assumption, and move page and book making topics in separate sections → agreed
• murakami-san: (to the list of applications and features that I sent) EPUB supports page-spread → will correct
• nat: placement of contents and white spaces in Japanese layout has its own beauty and would like to maintain it → agreed to the concept, but would like to see a concrete write up.
• bin-sensei: the quality of text on screen is nearing the level of paper. getting better and better (comment)
• bin-sensei: the section 4 can be divided into three separate pieces. Titles, notes and non-textual objects like images or charts → ok!
• bin-sensei: for example title can be generalised even without the line-grid system.
• kobayashi-san: would like authors to read this also → as long as it fits within the scope
• kida: on the same context, would like to say no to fullwidth numbers → grin
• kida: should we describe how to deal with edge cases? → no. let’s leave such to implementations. Just mention that there will be edge cases. if there are complex issues it can be a separate document (shimono)

next steps

• Kida to develop an introduction like paragraph covering the top level theme. yes…
• Kida to update the TOC document and check it in under /docs/

TODOs

• Nat to write up something in regard to the beauty of the Japanese page layout, in a way people can apply them on digital media.
• Shimono-san to integrate feedbacks from Richard.
• Kida to send a note to Richard to ask him if he could send it to UTC.
• Kida to send a note to Richard to get his OK to make a repository at W3C/ruby-t2s-user-requirements.
• Kida to develop an introduction like paragraph covering the top level theme. yes…
• Kida to update the TOC document and check it in under /docs/

oh, my, god. I have four todos…

Next meeting

will be on 11/2 after TPAC.

raw transcript: https://www.w3.org/2021/09/28-jlreq-minutes.html

[r12a]

hi Kida-san, Yasuo Kida （木田泰夫） wrote on 28/09/2021 08:55:

todo: Kida to send a note to Richard to ask him if he could send it to UTC.

Was there a particular reason you wanted me to do this?  I think it would be much more impactful and appropriate for a Japanese person to submit this to the UTC, on behalf of the Japanese community. ri

[kidayasuo]

Was there a particular reason you wanted me to do this?

Just because it was developed at JLreq TF under W3C. Then probably Kobayashi-san or I will submit. Thank you for your advice!

[xfq]

FYI - although IIRC there is no public place to track the progress of a bug report to Unicode, this is the official way of providing feedback: https://www.unicode.org/reporting.html

(See also https://corp.unicode.org/pipermail/unicode/2020-March/008536.html)