<xfq_> scribenick: xfq_

2018 Plan

angel: What are we going to do in 2018?

bobby: ancient books, gap analysis
... Chinese version of the Current Status of Japanese Web Typography Submission?

ryukeikun: I think we need to finish the clreq document first.

https://www.w3.org/Submission/2017/SUBM-CSJTUWT-20170102/

ryukeikun: one big difference between clreq and jlreq is the compression of adjacent punctuation marks
... the jlreq version is clearer

angel: How should we define "finishing" this document?
... we also need to find out our high-level plans for 2018.

ryukeikun: 1) Finish "3.1.6.1 Compression of adjacent punctuation marks".
... 2) We need more images all over the document.
... 3) Some differences between TC and SC are actually regional differences, rather than differences between the layout of the two kinds of characters.
... we need to be more accurate on that.

angel: More info about ancient books, Eric?

ryukeikun: https://www.w3.org/TR/jlreq/#inline_cutting_note
... Inline Cutting Note (Warichu)
... we need to define this in clreq too.
... also @1 punctuations

bobby: 眉批 (notes and commentaries at the top of a page)

ryukeikun: Also the Chinese equivalence of Jidori

https://www.w3.org/TR/jlreq/#jidori_processing

<angel> scribenick: angel

<xfq_> https://www.w3.org/TR/css-rhythm-1/

ryukeikun: add the content of 4.1.6

Bobby: I will work on the class topic, update 3.1
... add the description, such as the regional diff
... add the illustrations too

ryukeikun: make sure the illustrations are simple

Bobby: also 占字和占行处理，same with Jidori and Gyou-dori in JP

ryukeikun: acient books?

Bobby: maybe for next year
... I would like to have a check list
... like Jlreq

Angel: more details of the check list?

ryukeikun: will FW the list from Jlreq community
... then you will get it

https://www.w3.org/Submission/CSJTUWT/

ryukeikun: plz read the end of this doc

<xfq_> https://www.w3.org/Submission/CSJTUWT/jlreq-analysis.html

ryukeikun: with the requirement ready, then see if the CSS is supportive enough
... requirements is important here

Bobby: we can provide some input each year for CSS people to work on

ryukeikun: this is easy to make
... hard part is the testing
... we can wait until later this year
... ask Yijun to work on a draft

<xfq_> scribenick: xfq

<xfq_> scribenick: xfq_

<ryukeikun> 占字 as jidori /// 占行 as Gyodori in Japanese

<ryukeikun> 割注 warichu

<angel> ryukeikun: and 中文排版需求分析表

Analysis of requirements in CLREQ 中文排版需求分析表

<ryukeikun> 双行夹住

<ryukeikun> 夹注

angel: we need to send this to Yijun too

GitHub issues

https://github.com/w3c/clreq/issues

https://github.com/w3c/clreq/issues/166

https://github.com/w3c/clreq/pull/167

xfq_: Can ellipsis appear at the line start?

ryukeikun: It depends.

bobby: https://github.com/w3c/clreq/issues/164
... Is Yuan considered a kind of Hei?

ryukeikun: You can see it in that way as well, yes.

bobby: Closing #164.
... https://github.com/w3c/clreq/issues/168 and https://github.com/w3c/clreq/issues/169?

ryukeikun: I'll handle these two issues.
... we also need to explain the frequency of these kind of situations
... they're rare.
... one solution is to change the side of pinyin.

https://github.com/w3c/clreq/issues/149

ryukeikun: I'll handle this as well.

Next Meeting

angel: When do we talk next time?

ryukeikun: April 19, Thu, 18:00-19:00 (UTC+8)

All: Agreed.

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/ lreq/Clreq/
Succeeded: s/of Current Status/of the Current Status/
Succeeded: s/2) We /... 2) We /
Succeeded: s/3) Some/... 3) Some/
Succeeded: s/clearer/more accurate/
Succeeded: s/gidori/jidori/
Succeeded: s/with jidori in JP/with Jidori and Gyou-dori in JP/
Succeeded: s/theClreq/the clreq/
Succeeded: s/differences in the two kinds of/differences between the layout of the two kinds of/
Succeeded: s/占字，/占字/
Succeeded: s/Github issue/GitHub issues/
Present: xfq angel eric huijing bobby
Found ScribeNick: xfq_
Found ScribeNick: angel
Found ScribeNick: xfq
WARNING: No scribe lines found matching ScribeNick pattern: <xfq> ...
Found ScribeNick: xfq_
Inferring Scribes: xfq_, angel, xfq
Scribes: xfq_, angel, xfq
ScribeNicks: xfq_, angel, xfq

WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)