Clreq Editors Call -- 20 Sep 2017

Current Progress

Yijun: around Mar and April, did some proofreading
... went through chap 1 and 2
... until 2.3
... Huijing worked on the English proofreading
... I did not send a PR
... only on Master
... the PR in Mar is mainly about SC and TC, unifying the terms, until chap 3.1
... made some changes on font illustrations

Huijing: CN and TC need to be completely unified?

Yijun: let's try our best to unified them
... like a manual wikipedia

Huijing: SC and TC need to be completely unified?
... which is the standard version, SC or TC

Yijun: worked on a new version, published on Feb 20th

Angel: do we need to publish a new version?

Yijun: will publish a new version after the prove reading is done

Huijing: will move faster on the prove reading for clreq

Yijun: Bobby, anything to add?

Bobby: have not worked on this for sometime
... I care more about the Bopomofo

Yijun: Eric think @@ needs to be complete

Bobby: ruby for Pinyin?

Yijun: Yes

Angel: Yijun, anything we can help with?

Yijun: not that I can think of, simple work which just need time

Angel: any time table?

Yijun: later this year?
... will work on it on my Oct vacation

Bobby: I am working on bopomofo
... I planned to go to @@
... working on a proposal on Webfont

Angel: anyone plan to attend TPAC?

Bobby: maybe a bit late

current issues

Angel: can we close some issues?

Bobby: some are minor, we can close them

<xfq> https://github.com/w3c/clreq/issues

Angel: Bobby could you please help to close the minor ones?

Bobby: yes

Huijing: how do I add my correction in the prove reading

Yijun: which kind?

Huijing: typos

Yijing: go ahead with the typo corrections

Yijun: also I worked on the glossary

<xfq> Glossary: https://w3c.github.io/clreq/#glossary

Yijun: we need to translate the glossary

Eric: Yijun and I did some prove reading
... I used some Japanese definitions of the terms

Angel: I can help to translate some
... and referred from main land China definitions, ok with TC?

Bobby: think so, since there is no TC definitions

Angel: how many terms?

Yijun: about 100

<CYJ> 99 terms

<CYJ> https://github.com/w3c/clreq/blob/gh-pages/glossary-pinyin.csv

Bobby: if some of them are the same with Jlreq
... we can use them directly

Angel: I love it when we can use them directly :)

Bobby: careful that Jlreq has been being updated

Eric: Jlreq has some items to be added, e.g. 汉文
... I am working on some topics to be added to clreq, but needs more time to refine the thoughts
... some items, like @@, there are terms for them in main land china
... current this version contains the most basic requirements, but it needs more content

Bobby: for 注音，we used the 注音content from the Ministry of Education of the Republic of China
... for Bopomofo，let's find a more proper solution for it, not so old

Eric: better there is a reference than not
... for Pinyin, it is not mature yet, let's move it to next version

https://w3c.github.io/i18n-discuss/notes/language-matrix

<xfq> https://w3c.github.io/i18n-discuss/notes/language-matrix

Language matrix

Fuqiao: Richard recently developed a gap analysis

<xfq> https://w3c.github.io/typography/gap-analysis/arab-ar-fa

Fuqiao: Richard think it's better to include Chinese (SC and TC) in this table
... take Arabic as an example
... better if we can have a gap analysis for Chinese
... kind of roadmap for Clreq

Eric: can we just go through this list?

Fuqiao: sure
... better if we could come up with a document

Eric: if the framework is fixed
... filling in the content is easy
... Encoding, look no problem for me

<xfq> [Chinese, Japanese and Korean fonts almost always lack italic or oblique faces, because their characters are too complicated to support them well.]

all: disagree with the statement above

Fuqiao: let's correct it
... b/c it does not apply to Chinese

Bobby: it is another font, 楷体，in JP, it is 仿宋，rather than just 斜体
... better way to address is to make italic a different font

Eric: better to put it not applicable

Bobby: between light green and yellow

Eric: agree with light green

Fuqiao: any consensus?

Huijing: light green

Eric: Glyph control, not applicable

All: Glyph control, not applicable
... Cursive text, 楷体

<scribe> ACTION: Bobby to close the minor issues on github [recorded in http://www.w3.org/2017/09/20-clreq-minutes.html#action01]

<trackbot> Sorry, but no Tracker is associated with this channel.

<scribe> ACTION: Yijun to finish the prove reading before Dec [recorded in http://www.w3.org/2017/09/20-clreq-minutes.html#action02]

<trackbot> Sorry, but no Tracker is associated with this channel.

All: Boundaries & selection, need recovered

Eric: this feature is not for Chinese

All: Boundaries & selection, dark green
... Quotation, dark green

<xfq> https://drafts.csswg.org/css-counter-styles/

Bobby: Numbers & digits, basic needs covered

<xfq> https://drafts.csswg.org/css-counter-styles/#limited-chinese

Bobby: e.g. in vertical writing, 1903, we will not make it into one, but write it in full angle
... I think light green fits here

Eric: for order list, 1) and 2) can solve

Bobby: for list, there are some issues

Eric: order list is here or somewhere else?

Fuqiao: should be in list and counters

All: Numbers & digits, green is fine
... Char transforms, not applicable

Eric: Inter-char spacing, a bit topic!
... light green?

Bobby: agree

All: Inter-char spacing, light green
... ruby, light green
... Text decoration, light green
... Emphasis & highlight, dark green

Bobby: Inline notes, etc, 行内注，think it's yellow

Eric: something wrong with the link

All: Inline notes, etc, let's skip this one? dont know what it is, but the requirement applies for Chinese

Huijing: dont think this is supported for Chinese
... it should be a red

All: Inline notes, etc, RED

<ryukeikun> https://www.w3.org/TR/jlreq/ja/#inline_cutting_note

All: Bidi text, e.g. Chinese mixed with Arabic
... Bidi text, dark green is fine
... Line breaking, light green (DIFF)
... Hyphenation, at least issue with Pinyin, light green
... Justification & alignment, light green
... Lists, counters, light green
... Initial letter style, simple for Latin, not for Chinese
... broad use in magazines and books
... Initial letter style, Yellow
... Baselines, inline align, light green
... Other paragraph, light green
... Vertical text, light green

Bobby: Notes, footnotes,think should be yellow
... for Ancient Chinese, there is some head notes
... 头注

Eric: 眉批 by the author
... is it supported?

Bobby: think so

All: Notes, footnotes, light green
... Page numbers, running heads, 页眉，not on browsers, maybe on e-books, supported by reading system

Fuqiao: some browsers are working on it
... not aware of the progress

All: Page numbers, running heads, dark green??? need to check with CSS Working Group

Fuqiao: let's check with CSS WG

Bobby: and the new publishing WG

<scribe> ACTION: Fuqiao to check with CSS WG and Publishing WG [recorded in http://www.w3.org/2017/09/20-clreq-minutes.html#action03]

<trackbot> Sorry, but no Tracker is associated with this channel.

All: Other pagination, dark green??? need to check with CSS Working Group

Next Meeting

Angel: when should we meet again?
... let's target at Oct 25, Wed, 18:00-19:00

<xfq> UTC+8

<scribe> ACTION: Fuqiao to update matrix and talk to Richard [recorded in http://www.w3.org/2017/09/20-clreq-minutes.html#action04]

<trackbot> Sorry, but no Tracker is associated with this channel.

<scribe> ACTION: Huijing to continue the prove reading [recorded in http://www.w3.org/2017/09/20-clreq-minutes.html#action05]

<trackbot> Sorry, but no Tracker is associated with this channel.

<scribe> ACTION: Fuqiao to check with CSS WG and Publishing WG about the questions [recorded in http://www.w3.org/2017/09/20-clreq-minutes.html#action06]

<trackbot> Sorry, but no Tracker is associated with this channel.

<xfq> ACTION: xfq to do follow-up on the gap analysis [recorded in http://www.w3.org/2017/09/20-clreq-minutes.html#action07]

<trackbot> Sorry, but no Tracker is associated with this channel.

Yijun: we use CSV to update the version

Eric: Yijun please open a new @@ with time table

Yijun: let's publish PR and I will work on the conflict
... let's get a wechat group!
... let's stay with skype
... since everyone is here already

- DRAFT -

Clreq Editors Call

20 Sep 2017

Attendees

Contents

Current Progress

current issues

Language matrix

Next Meeting

Summary of Action Items

Summary of Resolutions

Scribe.perl diagnostic output