Antw: Re: W3C WAI RDWG Symposium on Easy to Read on the Web

Thanks Shawn,
 
I don't care. I found it the right approach to use Easy to Read as a noun (a concept, a tool, an approach) and easy to read as an adjective.
 
It seems to be different in the US and in Europe: I checked with the Easy-to-Read network (http://www.easytoread-network.org; good part of our SC is included) and it seems that they capitalize when speacking about the concept/idea/... of Easy to Read, too.
US ressources do as you describe: capitalized only in headings.
But everywhere you find exceptions to the rules. 
 
I used hyphens at the beginning but deleted them (following a hint from an other colleague) and it seems that this is not used very often?
 
Will make a final check as soon as we have our final definition.
 
Klaus
 


>>> Shawn Henry <shawn@w3.org> 04.09.2012 18:35 >>>
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