W3C

- DRAFT -

Clreq Editors' Call

14 Dec 2017

Attendees

Present
Huijing, Fuqiao, Yijun, angel, bobby
Regrets
Chair
fuqiao
Scribe
angel

Contents


<CYJ> ^_^

Plan for publishing a new working draft

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

glossary translation

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

Fuqiao: the translation of glossary is almost done
... some editors updated CSV and some worked on the index page
... not a big issue
... at least we have done the translation of the glosssary
... we have some translation from wikipedia, is that ok?
... wikipedia is CC BY-SA, so we can use the text with attribution

<scribe> scribenick: angel

Angel: I dont understand the Chinese of 标号

Huijing: should we put the ones that have not been translated into issue list?

Angel: good idea

<xfq> https://github.com/w3c/clreq/pull/159

<xfq> https://github.com/w3c/clreq/pull/160

Yijun: maybe we should use the wikipedia version

Fuqiao: will check the conflict

<xfq> https://github.com/w3c/clreq/pull/148

Fuqiao: Eric and I did some simple translation, issue 148
... can we merge them?
... the translation is smooth

All: ok to merge them

Fuqiao: other items/issues we should look at before we release the new version?

Huijing: last time we talked about the issue 151, but not solved

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

Bobby: I did look at the issues and closed the easy ones
... but some are hard to close

Fuqiao: maybe we can go through them today?

Yijun: are we done with glossary?
... Fuqiao will file an issue for the untranslated glossary items?

Fuqiao: I do have some questions
... e.g. 西文
... Angel asked about 标音

Yijun: we invented 标音,so it would not be confused with 注音
... way to indicate the pronunciation of Chinese characters

Fuqiao: ok, I will update it
... about 活字排版,the translation of 字块,what should it be

https://en.wikipedia.org/wiki/Movable_type

Huijing: sort or type

Fuqiao: I did not find the translation of 声调 平上去入

Yijun: four tones will do
... no need to be so detailed, the four tones should be good
... can Bobby help to explain the 天地? this is from GB?

Bobby: 天头?

<bobbytung> a) The top part of a book or a page.

<bobbytung> b) The top margin between the top edge of a trimmed page and the hanmen (text area)

<bobbytung> (JIS Z 8125)

Bobby: let's change text area into type area

Fuqiao: I will prepare the publishing
... any other issue we should look at?
... Richard pointed an issue, Huijing, any thoughts?

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

Huijing: would like to check with everyone, how should we move one with this?

<xfq> https://github.com/w3c/type-samples/issues/35

Fuqiao: I remember when we looked at the diagram, there are some untypical types

Yijun: we should ask Bobby
... personaly I think it should be vertical writing
... you can think of it as two columns

Huijing: this is a very rare case
... find any case in Chinese?

Fuqiao: we can stay with Richard's suggestion on this

Huijing: anyone can help with the Chinese translation?

Yijun: I will do it

All: thanks Yijun!

Huijing: since we are publishing a new version, what else?

Yijun: SC

Fuqiao: we can make it as the work for 2018

Yijun: we should give Huijing repo access

Fuqiao: let me check, I think she does

Huijing: could you please add my name into the editor's list?

Fuqiao: sure, will do

Yijun: bobby could you please check issue 151?

Bobby: a few questions, 1st is Columns. can we call the Columns in the news page columns?
... 2nd, can we call the example in https://github.com/w3c/type-samples/issues/35 vertical writing?
... which existed in the magazines in the old times

Yijun: so we dont know if it is vertical or horizontal?
... maybe we should call it @@3?

Fuqiao: bobby do you think we can try to avoid classify it into VW or HW?

Bobby: fine with Richard's update
... we should remove 2 things, one is IN THE PAST another one is NO COLUMNS ARE APPLIED
... will put it into the issue list

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

Fuqiao: a minor thing
... a new issue 158 about counter, to use 、 or .
... should we add it into Clreq?

Yijun: in CSS, it will be the latter, not the former

Fuqiao: should we mention it?

Huijing: should it is correct to use 、?

Fuqiao: at least that is what I have seen
... we don't have to sovle it in this version

Yijun: do we have this in the current content?

Fuqiao: I think so, in 3.1.1.1, there are some content about "、"

Yijun: this is only a brief mention
... there should be a paragraph about this
... a paragraph about LIST

<bobbytung> Chinese traditionally only uses vertical writing mode. Sometimes horizontal lines are used in content that is set vertically, such as on stone inscriptions or headings for newspapers and magazines. In such cases, characters should be ordered from right to left. but now this has largely been replaced by the horizontal lines that are read from left to right.

<bobbytung> 中文传统上仅使用直排,当横排文字使用于直排文字时,如匾额、报纸、杂志的标题,文字应为由右向左排列。但目前多为由左而右的横排书写方向取代。

<bobbytung> 中文傳統上僅使用直排,當橫排文字使用於直排文字時,如匾額、報紙、雜誌的標題,文字應為由右向左排列。但目前多為由左而右的橫排書寫方向取代。

Bobby: is it necessary to keep it into that level of details, if so, I will update it

Fuqiao: about the LIST, I can reply with what I got now, and mention the LIST paragraph work later

Next Meeting

Fuqiao: should we meet before or after Chinese spring festival?
... maybe a bit vacation? we meet after the spring festival?

Bobby: issue 130
... I noted that 儿话音 should be positioned above
... I need to check the version of the standard

Yijun: so when do we release the new version?

Fuqiao: I think we have finished the translation, not so much work left for releasing a new version
... this is a working draft, so we can publish it anytime
... I think we can publish it before the end of Dec
... I has not been involved into a multi-lingual draft. need to work with Richard
... for the next meeting, how about we meet in early March ?

Huijing: fine for me

Yijun: ok for me

Fuqiao: so Mar 1, a Thu
... and time?
... so we can switch back to old usual time?

Huijing: I will be back home, so the old time should be good for me

Bobby: some favor to ask Yijun
... e.g. underline
... issue 115
... Richard does not seem to agree

Yijun: I replied
... it does not have to be a Combination word
... how this line looks like depends on the designer or the browser?

Bobby: see no solution to this question
... can you make a pull request and change it?

Huijing: have to catch another meeting, will leave now, bye guys

[Huijing leaves]

Bobby: will solve it on gitbub
... no more questions

Fuqiao: another thing, W3C team in China has prepared a little gift for you
... pleaes send me the address and contact info so that we can send you the gift
... thanks very much for your hard on clreq!
... see you next year!

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2017/12/14 14:51:34 $

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/cna/can/
Succeeded: s/git/gift/
Succeeded: s/wikipedia is cc-by, we should refer to them/wikipedia is CC BY-SA, so we can use the text with attribution/
Succeeded: s/Fuqiao will setup issue list/Fuqiao will file an issue for the untranslated glossary items/
Succeeded: s/@@1 area/text area/
Succeeded: s|@@2 vertical writting|the example in https://github.com/w3c/type-samples/issues/35 vertical writing|
Succeeded: s/exits/existed/
Succeeded: s/horizental/horizontal/
Succeeded: s/INTO COLUMNS/NO COLUMNS ARE APPLIED/
Succeeded: s/to use , or ./to use 、 or ./
Succeeded: s/to use ,/to use 、/
Succeeded: s/dont/don't/
Succeeded: s/content about ,/content about "、"/
Succeeded: s/poll request/pull request/
Present: Huijing Fuqiao Yijun angel bobby
Found ScribeNick: angel
Inferring Scribes: angel

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


[End of scribe.perl diagnostic output]