RE: [i18n] education & outreach initiative

I have also long wanted to look at the validator, add some i18n checks
if/where needed, and provide useful hints and explanations for warnings
and errors.  Also HTML Tidy.  This will get a lot of visibility and help
us make a significant difference.

Adding a Q&A type area to the website also sounds like an interesting
approach.  For example, I'd like to provide some navigation into the
current hints & tips that started from some kind of Q&A type format.  (I
think Q&A is popular because when using it you are usually hoping to
find an answer to a very specific point that you need help with - which
fits very much into our philosophy so far of identifying and servicing
the needs of the community, rather than just producing untargeted
information blindly.)

RI

============
Richard Ishida
W3C

tel: +44 1753 480 292
http://www.w3.org/International/
http://www.w3.org/People/Ishida/



> -----Original Message-----
> From: public-i18n-geo-request@w3.org 
> [mailto:public-i18n-geo-request@w3.org] On Behalf Of Bjoern Hoehrmann
> Sent: 11 April 2003 04:41
> To: Arko, Phil
> Cc: public-i18n-geo@w3.org
> Subject: Re: [i18n] education & outreach initiative
> 
> 
> 
> * Arko, Phil wrote:
> >Many web designers (at least in the US) typically use a site such as 
> >WebMonkey.com or Builder.com instead of W3.org. Such sites offer a 
> >quick overview (although not always completely accurate) of the most 
> >important aspects of a topic. They typically (in my 
> experience) do not 
> >look to the entire guideline on the W3 site. Can we think 
> about methods 
> >of ensuring that our deliverables are more easily 
> approachable and more 
> >usable, so as to make sure that web designers come here first to get 
> >the most accurate set of guidelines?
> 
> That's exactly what I thought of when I first heard of I18N 
> GEO, make the authors and developers aware of issues, explain 
> them and provide hints how to deal with them. It would be 
> great to have Q&A documents to point at at w3.org. For 
> example, the W3C MarkUp Validator refuses to validate 
> documents which do not explicitly specify a character 
> encoding. Many authors don't understand why this is necessary 
> or how to setup the web server to specify the encoding, it'd 
> be great if I18N GEO would provide sole document dealing with 
> such issues.
>

Received on Friday, 11 April 2003 07:10:16 UTC