W3C home > Mailing lists > Public > public-i18n-geo@w3.org > January 2006

[ESW Wiki] Update of "geoQuickTips" by RichardIshida

From: <w3t-archive+esw-wiki@w3.org>
Date: Thu, 05 Jan 2006 16:59:53 -0000
To: w3t-archive+esw-wiki@w3.org
Message-ID: <20060105165953.9994.81297@localhost.localdomain>
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


------------------------------------------------------------------------------
  
    Unless you appropriately declare which character encoding you are using your users may be unable to read your content.  This is because incorrect assumptions will be made by the application interpreting your text about how the bytes map to characters.
  
-   The W3C internationalization site provides [http://www.w3.org/International/tutorials/tutorial-char-enc/ guidance on how to declare the character encoding] of (X)HTML and CSS content.  Note that this is not always so straightforward as it may appear.
+   The [http://www.w3.org/International/ W3C internationalization resources] provide [http://www.w3.org/International/tutorials/tutorial-char-enc/ guidance on how to declare the character encoding] of (X)HTML and CSS content.  Note that this is not always so straightforward as it may appear.
  
   2. '''Escapes.''' Only use escapes (numeric character references and entities) in specific circumstances.
  
@@ -59, +59 @@

  
    Such escapes are useful for clearly representing ambiguous or invisible characters, and to prevent problems with syntax characters such as ampersands and angle brackets.  They may also be useful on occasion to represent characters not supported by your character encoding or unavailable from your keyboard. Otherwise you should always use characters rather than escapes.
  
-   The W3C internationalization site provides [http://www.w3.org/International/questions/qa-escapes additional information about the use of escapes] in markup languages. In particular, entities (such as &aacute) should be used with caution.
+   The [http://www.w3.org/International/ W3C internationalization resources] provide [http://www.w3.org/International/questions/qa-escapes additional information about the use of escapes] in markup languages. In particular, entities (such as &aacute;) should be used with caution.
  
   3. '''Language declaration.''' Declare the text-processing language of documents and indicate any internal language changes.
+ 
+   Information about the natural language of text is important for accessibility, styling, searching, editing, and other reasons.  The more content is tagged and tagged correctly, the more applications that can detect language information will become useful and pervasive.
+ 
+   The [http://www.w3.org/International/ W3C internationalization resources] provide information about [http://www.w3.org/International/questions/qa-escapes how to declare the language] of a document as a whole, or fragments of content in a different language. In this regard, it is essential to understand the difference between the concepts of [http://www.w3.org/International/tutorials/language-decl/en/all.html#Slide0060 text-processing language vs. primary language metadata].
  
   4. '''Presentation vs. content.''' Use stylesheets for presentational information, and restrict markup to semantics.
  
Received on Thursday, 5 January 2006 19:46:58 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:28:03 UTC