JLReq TF meeting notes 2019 August 8th

JLReq TF meeting notes 2019 August 8th
（日本語のアクションアイテムが後ろにあります）

Attendee
Kobayashi, Tatsuo
Kobayashi, Toshi (Bin-sensei)
McCully, Nat (online)
Murakami, Shinyu
Shimono, Atsushi
Tajima, Jun
Takase, Hiroshi
Kida, Yasuo
Notes

JLReq updates
The remaining task is translation check by Nat (Nat, what is the status? Are they #84 & #85?)
Agreed to create “future” label for issues that are not errata or usability improvements of the version 2 document (Shimono-san)
Agreed to create “wording” label to track wording issues both in Japanese and English (Shimono-san)
Gap Analysis: Progress on developing test cases
Tajima-san needs a list of detailed properties / values that correspond to each section of the document (Murakami-san to provide through slac)
Agreed to create a slac thread for online discussions (Tajima-san, done)
Tests that need to be newly developed will mainly on text-spacing and ruby
How we test font related features? Because glyph changes with some features are subtle ideally it is the best if there is a font with fake glyphs to clearly illustrate the change. Agreed developing such font is too much work, and will do with what are available.
There are features that works on paged documents and not really testable on web based test environment.
We did not discuss on this comment at the meeting but I realize that this might be an issue that is worth a discussion. Let’s discuss it at the next meeting.
Needs to translate test comments to English (Murakami-san)
Integration test
Each css implements specific feature described in JLReq. Do they then as a whole work together and can re-create documents that JLReq request?)
Need some rough ideas on risk areas so we can focus our efforts on (Nat to come up with a write up)
Agreed to create a sub-group discussing this specific matter (kida)
Development of such stylesheet will be mainly done as an activity in APL (agreement from a previous meeting)
TPAC breakout session (9/18)
Nat proposed a breakout session at TPAC. Are there discussions we would like to see?
An important goal would be to know who are our possible clients, who are interested in our activities 
Kyoto meeting (9/8)
Who are coming?  Richard, Erika, Nat, Shimono, Murata, Kobayashi, Murakami & Kida
Possible agenda
JLReq activity review (Kida)
Future talk (Kobayashi)
Ruby & Maze-gaki issue (Murata)
Wakachi-gaki, sharing the issue / discussion point (Murata)
How we treat Tate-chu-yoko in text-to-spech (Murata)
Murata-san will to send a list of agenda he would like to discuss (Murata)
Gap Analysis: Review of CSS definition status
Using a few meetings onward we will go through JLReq sections to review if CSS is defined for requested features

 Sections
3.1.1 Differences in Vertical and Horizontal Composition in Use of Punctuation Marks <https://www.w3.org/TR/2012/NOTE-jlreq-20120403/#differences_in_vertical_and_horizontal_composition_in_use_of_punctuation_marks>
Not a CSS issue.
This feature is to be achieved by using different characters depending on the direction of the text. It makes text data not interchangeable between vertical and horizontal. It poses an issue with accessibility. Should this feature be carried on to digital world? (Future issue)
3.1.2 Positioning of Punctuation Marks (Commas, Periods and Brackets) <https://www.w3.org/TR/2012/NOTE-jlreq-20120403/#positioning_of_punctuation_marks>
👍 CSS satisfies the requirements
3.1.3 Exceptional Positioning of Ideographic Comma and Katakana Middle Dot <https://www.w3.org/TR/2012/NOTE-jlreq-20120403/#exceptional_positioning_of_ideographic_comma_and_katakana_middle_dot>
Not currently possible
Priority: medium
3.1.4 Positioning of Consecutive Opening Brackets, Closing Brackets, Commas, Full Stops and Middle Dots <https://www.w3.org/TR/2012/NOTE-jlreq-20120403/#positioning_of_consecutive_opening_brackets_closing_brackets_comma_full_stops_and_middle_dots>
Not currently possible. Being proposed in text level 4 text-spacing
Issue with a case with different font size
Priority: high
3.1.5 Positioning of Opening Brackets at Line Head <https://www.w3.org/TR/2012/NOTE-jlreq-20120403/#positioning_of_opening_brackets_at_line_head>
Not currently possible. Being proposed in text level 4 text-spacing
Discussions on what should be the default / normal. JIS X 4051 defines a default and JLReq follows it. In the real world however a different method is being used for compatibility issue.
Possible agenda at the Kyoto meeting
Priority: high
3.1.6 Positioning of Dividing Punctuation Marks (Question Mark and Exclamation Mark) and Hyphens <https://www.w3.org/TR/2012/NOTE-jlreq-20120403/#positioning_of_dividing_punctuation_marks>
👍 CSS satisfies the requirements
3.1.7 Characters Not Starting a Line <https://www.w3.org/TR/2012/NOTE-jlreq-20120403/#characters_not_starting_a_line>
👍 CSS satisfies the requirements
3.1.8 Characters Not Ending a Line <https://www.w3.org/TR/2012/NOTE-jlreq-20120403/#characters_not_ending_a_line>
👍 CSS satisfies the requirements
Next meeting
Considering various events in September the next meeting will be after 23rd

4-7: A-Typ I
8: Kyoto meeting
9-13: CS34
16-20: TPAC

––––––––––––––––––––––––––––––––––––
Action items
Complete English translation (Nat, #84 #85, etc.)
Create “future” and “wording” labels in Github issues (Shimono-san)
Make progress on developing CSS tests. Can we start submitting? (Tajima-san, Murakami-san, Takase-san)
Nat to write up something describing the point he raised and risk areas (Nat)
Create a sub group to discuss integration test / style sheet issues (kida)
Murata-san to send a list of agenda items for Kyoto meeting (Murata-san)
––––––––––––––––––––––––––––––––––––
アクションアイテム
英訳を終わらせる（ナット, #84, #85 など）
Github issues に “future”, “wording" ラベルを作る（下農さん）
CSS test cases の開発を進める。次のミーティングまでにサブミットし始められる？（田嶋さん、村上さん、高瀬さん）
CSS 全体として JLReq の要求を満たせるのか、想定されるリスクエリアについて書く（ナット）
その問題を議論するためのサブグループを作る（木田）
京都ミーティングで話したいことのリストを出す（村田さん、他誰でも）
––––––––––––––––––––––––––––––––––––

木田