[jlreq] JLreq TF meeting notes 6/30 (#284)

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

== JLreq TF meeting notes 6/30 ==
JLreq TF meeting notes 6/30

Discussed re:magazine articles using topics gathered in #278
- The first topic will be about TWO EM DASH. A draft article was posted on #276
- Kobayashi-san will propose an article series (with irregular interval) to “印刷雑誌” magazine published by “The Japanese Society of Printing Science and Technology”. At the same time, we want to retain rights to publish it online. Possible venues are Kobayashi-san’s blog @ CITPC, Tajima-san’s blog or tech magazine sites.
- Will continue sharing and discussing on drafts on GH (unless the publisher did not like it)
- It will be in a dialog format as we do not have definite answers to many of the topics / issues. They are under ongoing discussions by JLReq and others. Now is an interesting time in a history where text layout and books on digital media is gradually taking a form (Kobayashi).
- Some terminologies will require explanations and these will be treated like side notes. Summaries and figures will also be treated as such.
- todo: Kida has comments and will post them on GH.

Other possible topics (added to #278)
- Issues with characters that are intended only in vertical writing such as KANA REPEAT MARKs and quotation marks.
- Issues with punctuations that share the same code point with European languages.
- Issues with punctuations that share the same code point with Chinese.
- Does it make sense to keep the concept of page spread, or left and right pages in digital books?

Digital Native JLReq (#281)
- We are developing the building blocks one by one, e.g. simple ruby, and expanding character class to unicode. We still do not know the timeline however.
- Let’s review the table of contents of the current JLReq, and see what needs to be changed #283. This will be a meeting topic after the next. (The next is to review the summary document of expanding character class to unicode)
- All topics that are covered by #278 are possible contents
- Can we touch on books with multiple threads like multilingual books?
- Referencing is one of the fundamental issue with ebooks
- Optimizing space between lines and line length (depending on the priority of the document)

The next meeting will be on 8/3 to discuss on the summary of expanding character class to Unicode. Kida is to finish the document by then.


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


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

Received on Tuesday, 29 June 2021 15:06:33 UTC