Clreq Editors' Call -- 16 Nov 2017

huijing: It's related to the translation.
... The original text was not very understandable. Richard suggested some new text.
... Any opinion on this?
... The meaning of the proposed text seems to be differennt from the original text, which was translated from Chinese.

ryukeikun: It's a special case of vertical text that looks like horizontal text.

huijing: Do we need to rewrite the Chinese text?

xfq: https://github.com/w3c/type-samples/issues/35 seems to be RTL

ryukeikun: The newspaper looks strange to me. Is it common?

YJ: It used to be common, but much less now, I think.

ryukeikun: I propose that we accept the suggestion of Richard and rewrite that paragraph.

All: Agreed.

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

angel: We spent 30 minutes discussing 3 issues. Should we triage them first?

All: Agreed.

angel: I'll ping Bobby, and let him review the issue list first.

<angel> ACTION: angel to ping bobby about the issue deadline

Plan for a new released version by the end of 2017?

angel: WD update. Is it realistic to publish a new WD by the end of the year?

<angel> huijing++

YJ: We should merge https://github.com/w3c/clreq/pull/150 first.
... and complete the translation of the Glossary.

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

ryukeikun: There are 99 glossary items.

angel: I take the first 20. huijing takes 21-40. ryukeikun takes 41-60. xfq takes 61-80. YJ takes the rest.

All: Agreed.

angel: Proposed next meeting time: mid-December

huijing: I'll be in the US in mid-December.

Angel: December 14, 9pm Beijing, 10pm Tokyo, 7am US?

All: Agreed.

angel: Anything else before WD publication?

ryukeikun: Not that I can think of currently.

angel: Anyone going to the next in TPAC?
... We can meet Richard there.
... It will be held in Lyon, France.

ryukeikun: Great! I'll see if I have time next year.

<angel> thank you all!

angel: Talk with you in December!

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]

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/I think it may be: "xfq" and "xfq, angel", i.e., two actually//
Succeeded: s|https://www.w3.org/2017/09/20-clreq-minutes.html|Previous meeting minutes: https://www.w3.org/2017/09/20-clreq-minutes.html|
Succeeded: s/It used to be common,/It used to be common, but much less now,/
Present: Angel Fuqiao Huijing Xidorn Yijun
Found ScribeNick: xfq
WARNING: No scribe lines found matching ScribeNick pattern: <xfq> ...
Found ScribeNick: xfq, angel
WARNING: No scribe lines found matching ScribeNick pattern: <xfq\,\ angel> ...
Found ScribeNick: xfq
Found ScribeNick: xfq_
Inferring Scribes: xfq, xfq, angel, xfq_
Scribes: xfq, xfq, angel, xfq_
ScribeNicks: xfq, 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: angel

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.)

[End of scribe.perl diagnostic output]

- DRAFT -

Clreq Editors' Call

16 Nov 2017

Attendees

Contents

TPAC I18N Clreq related item briefing

Open actions review

Github issue (need to go through?)

Plan for a new released version by the end of 2017?

Summary of Action Items

Summary of Resolutions

Scribe.perl diagnostic output