- From: Shadi Abou-Zahra <shadi@w3.org>
- Date: Wed, 05 Sep 2012 00:40:14 +0200
- To: Shawn Henry <shawn@w3.org>
- CC: Klaus Miesenberger <Klaus.Miesenberger@jku.at>, RDWG <public-wai-rd@w3.org>
Thanks for this feedback, Shawn! We were using capitals to indicate "easy to read" topic rather than the phrase something is easy to read. I will use hyphenation rather than capitals to indicate this. Thanks, Shadi On 4.9.2012 18:35, Shawn Henry wrote: > On 9/4/2012 7:59 AM, Klaus Miesenberger wrote: >> Please make a final check at >> http://www.w3.org/WAI/RD/wiki/Topic_4_pre-call > > > Hi Klaus & Shadi, > > Suggestion: hyphenate easy-to-read in lowercase, except for the title of > the symposium Easy-to-Read on the Web Symposium. > > Discussion: Judy brought up the issue of capitalization of Easy to Read. > It should be capitalized when used in the title of the symposium, "Easy > to Read on the Web". However, I think in other uses, it should be > lowercase and hyphenated. When you use "easy to read" is it really > shorthand for "easy-to-read language/format/etc."? Thus easy-to-read is > an adjective. > (fyi, https://www.google.com/search?q=esay+to+read ) > > I'm happy to discuss this as needed. > > ~Shawn > > -- Shadi Abou-Zahra - http://www.w3.org/People/shadi/ Activity Lead, W3C/WAI International Program Office Evaluation and Repair Tools Working Group (ERT WG) Research and Development Working Group (RDWG)
Received on Tuesday, 4 September 2012 22:40:51 UTC