- From: Chen Yijun via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Jul 2015 07:07:23 +0000
- To: public-i18n-archive@w3.org
> if we have answers to these questions, i can help, if you like, to reconfigure the table markup the next time i get some free time, because i think it is important to sort out the glossary asap. We are currently using the CSV file for sorting out the glossary, so that we can use tools like Excel to edit the content, automatically sort the order by Pinyin or English, and convert the format to HTML (in CLI tools or else). Can we please stay in using this procedures? **The CSV file:** <https://github.com/w3c/clreq/blob/gh-pages/glossary-pinyin.csv> > do we need the first two columns to be changed to TC term | TC pinyin | SC term | SC pinyin? Or should we add both TC and SC terms to one column, and pinyin to a second? I prefer TC/SC in one column and Pinyin in another. > If we do that, should we allow the SC vs TC terms/pinyin to be filtered out, or keep them always there? I think always there. Always there. > we also need to add ids to each row. I guess it wouldn't work to base the ids on the pinyin, since we'd ideally want to avoid tone marks so that people have less difficulty constructing links – if we avoid the tone marks, we'll presumably have clashes with some words. So maybe we should base them on the english? I’d say English IDs so that we can maintain the consistency with heading titles and avoid the conflicts of TC and SC. -- GitHub Notif of comment by ethantw See https://github.com/w3c/clreq/issues/78#issuecomment-126206046
Received on Thursday, 30 July 2015 07:07:26 UTC