<r12a> 3. plans for glossary development;

<r12a> 4. should we make zh into zh-hant;

<r12a> 5. review of issues list and discussion of issues that are stuck;

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

General status of the current CLreq document and plans for SC integration;

Richard: FPWD is released this week
... anther verison of the FPWD will be released today too
... we should actively go and look for people who want to review the document
... we want them to review the W3C site version, not the github version
... just not to get them sink in the github living version
... and github does not provide certain facility for comments

Eric: who is working on the SC version, Angel or Xiaoqian?

Angel: an editor from CHina Mobile, called Zhang Aijie

Eric: I will also check the SC version

Richard: Angel, you might want to piont the current github SC verison to Aijie

 review of issues list and discus

richard: we have some markup for diff verisons
... e.g.zh
... should we keep with these solution?

Eric: agree

Ethan: think we should stick with them

Richard: it might cause some translaiton problem for me and Angel, if we continue
... we will see how the translateme and checkme markup do

Ethan: I will look at the TC chinese translation in Aug

Eric: one table for SC and one table for TC?
... for the glossary
... we might need 2 tables for the glossary

richard: that is an issue we had

<r12a> https://github.com/w3c/clreq/issues/78

eric: I think it is necessary to put the TC version and SC version side by side

richard: a couple things to do
... one is to allow people to use JS
... another is the arbitrary order

Ethan: the JS solution might be too complicated

richard: we might do that later

Eric: is the Pinying necessary?

richard: it is very useful for me

Eric: TC and SC are different, but the pinyin is the same
... for some cases, we have to repeat the pinyin

Richard: we have the SC as the second

Angel: the tradition ones appeared first, I have not problem having them first

Ethan: dont have problem by far

Eric: maybe do not use /?

Richard: what we should do is to markup the @@
... we need to put markup to say this is the SC
... I was happy to have 2 columns

Ethan: will first merge them to CSV files then github files
... I might start to work on it next Sat, that is the earliest day I can start

Eric: it is great work, and takes time
... when people were working on the Jlreq, they spent lots lots time

richard: it seems Bobby has a diff idea of what line space than I do
... it affects what we do to solve the issue
... the Jlreq people started the work with glossary

no pressure Ethan

Eric: I can help too
... copy me in the process so that I can help to edit

Ethan: we are working on the CSV file, will put little comments on the repo
... if any problems, we can discuss it on github

Eric: or we can discuss it first

Ethan: sure

Richard: keep us informed please

Ethan: the fig I put in days ago, the tone mark of 2nd fig is wrong
... the one on the right
... the tone mark should be on the right side

richard: any other issues people want to discuss?

<r12a> https://github.com/w3c/clreq/issues/61

This is scribe.perl Revision: 1.140  of Date: 2014-11-06 18:16:30  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/call/called/
Succeeded: s/@@/translation/
Succeeded: s/arbitry/arbitrary/
Succeeded: s/appears/appeared/
Found Scribe: Angel
Inferring ScribeNick: Angel
Present: Richard Xiaoqian Ethan Lianghai Eric Liu
Got date from IRC log name: 30 Jul 2015
Guessing minutes URL: http://www.w3.org/2015/07/30-clreq-minutes.html
People with action items: