Difference between revisions of "internationalization"

From Microformats Wiki
internationalization
Jump to navigation Jump to search
(note all outstanding intl issues resolved)
m (Replace <entry-title> with {{DISPLAYTITLE:}})
 
Line 1: Line 1:
<entry-title>Internationalization</entry-title>
+
{{DISPLAYTITLE:Internationalization}}
 
(AKA '''internationalisation''', '''i18n'''.)
 
(AKA '''internationalisation''', '''i18n'''.)
  

Latest revision as of 16:28, 18 July 2020

(AKA internationalisation, i18n.)

What can we do, to make microformats more easily usable, by people who are not publishing in (US) English?

Background

  • To encourage broader/better support of international content, modern internet and web standards strongly advocate the support of character sets such as UTF-8.
  • The vocabularies used in such standards in general use US English terms and spelling (ref: W3C, IETF) for elements, attributes, properties and values. For example (X)HTML is defined in US English (e.g "color", "center"). See en-US FAQ for more on why this is actually good for internationalization.

The design of microformats follows both of these well-established practices of modern internet and web standards design.

Issues

  • ...

Resolved Issues

Solutions

<abbr class="tel" title="+44 1233 456 7890">01233 456 7890</abbr>
  • Use the Value Class Pattern for the type subproperty of the tel property when authoring in a language other than US English (which is used by the enumerated values of the type subproperty).

See also

Microformats wiki in other languages

See:

Internationalization and localization references