- From: via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Jul 2015 08:59:56 +0000
- To: public-i18n-archive@w3.org
r12a has just created a new issue for https://github.com/w3c/clreq: == Adding definitions to the glossary == @ethantw some points for discussion about converting the glossary to hold linkable definitions, like jlreq: the glossary currently has the following columns term | pinyin | english if we are to add definitions, like for jlreq, we need to add a 'definition' column i assume that the definition column cells will contain three versions of each definition, en, zh-hans, zh. Each of which can be filtered out. 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? If we do that, should we allow the SC vs TC terms/pinyin to be filtered out, or keep them 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? 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. See https://github.com/w3c/clreq/issues/78
Received on Wednesday, 29 July 2015 08:59:57 UTC