- From: <w3t-archive+esw-wiki@w3.org>
- Date: Mon, 21 Nov 2005 22:29:22 -0000
- To: w3t-archive+esw-wiki@w3.org
Dear Wiki user, You have subscribed to a wiki page or wiki category on "ESW Wiki" for change notification. The following page has been changed by RichardIshida: http://esw.w3.org/topic/geoQuickTips ------------------------------------------------------------------------------ Authors: Andrew Cunningham, Richard Ishida + The first section is an attempt to make the text more concise to fit on the cards. The second section is our original agreed text and is slightly lengthier - maybe the longer version could go on the Web site, or maybe we should just use the short one ?? + + + == Quick Internationalization Tips for the Web == + + Shortened version for the cards. + + 1. Encoding: Use Unicode wherever possible for content, databases, etc. Always declare the encoding of content. + + 2. Escapes: Only use escapes for characters in exceptional circumstances. + + 3. Language declaration: Declare the text-processing language of the document and any internal language changes. + + 4. Presentation vs. content: Use stylesheets for presentational information, and restrict markup to semantics. + + 5. Images, animations & examples: Check for inappropriate cultural bias and translatability. + + 6. Forms: Use appropriate encodings on both form and server. Support local formats of names/addresses, times/dates, etc. + + 7. Text authoring: Use simple, concise text. Do not compose sentences from multiple strings using scripting. + + 8. Navigation: On each page include clearly visible navigation to any localized pages or sites, using the target language. + + 9. Right-to-left text: For XHTML, add dir="rtl" to the html tag. Only re-use it to change directionality. + + 10. Check your work: Validate! Use techniques, tutorials, and articles at [[http://www.w3.org/International/ http://www.w3.org/International/]] + + + + == Quick Internationalization Tips for the Web == + + Original longer version: 1. Encoding: Use Unicode wherever possible for content, forms, scripts, databases, etc.; always declare the encoding in the page, and, where appropriate, using the HTTP header.
Received on Tuesday, 22 November 2005 12:33:34 UTC