internationalization: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
(entry-toc)
(note all outstanding intl issues resolved)
Line 11: Line 11:


==Issues==
==Issues==
* ...
=== Resolved Issues ===
*<code>type</code> attributes, such as those for <code>tel</code> in [[hcard|hCard]], require either English-language content on the page, or English-language <code>abbr</code> titles.
*<code>type</code> attributes, such as those for <code>tel</code> in [[hcard|hCard]], require either English-language content on the page, or English-language <code>abbr</code> titles.
**March 2007 discussion (ongoing) of [http://microformats.org/discuss/mail/microformats-discuss/2007-March/009000.html abbr title for non-English values]. Is <code><nowiki><abbr class="type" title="fax">Téléc</abbr></nowiki></code> acceptable?
**March 2007 discussion (ongoing) of [http://microformats.org/discuss/mail/microformats-discuss/2007-March/009000.html abbr title for non-English values]. Is <code><nowiki><abbr class="type" title="fax">Téléc</abbr></nowiki></code> acceptable?
Line 16: Line 19:
*[[genealogy-brainstorming#Gender|Gender values in Genealogy]]
*[[genealogy-brainstorming#Gender|Gender values in Genealogy]]
** This issue should be moved to [[gender-brainstorming]] (or perhaps [[gender-issues]]) until it actually presents a real issue in at least a draft microformat.
** This issue should be moved to [[gender-brainstorming]] (or perhaps [[gender-issues]]) until it actually presents a real issue in at least a draft microformat.
** This has subsequently been resolved with a new [[gender]] property in vCard4/hCard1.1 ([[uf2|hCard2]] as well)


==Solutions==
==Solutions==
Line 21: Line 25:
*For telephone numbers in hCard, use abbr and the [http://en.wikipedia.org/wiki/E.123 ITU E.123 standard] international format, for example:
*For telephone numbers in hCard, use abbr and the [http://en.wikipedia.org/wiki/E.123 ITU E.123 standard] international format, for example:
:<code><nowiki><abbr class="tel" title="+44 1233 456 7890">01233 456 7890</abbr></nowiki></code>
:<code><nowiki><abbr class="tel" title="+44 1233 456 7890">01233 456 7890</abbr></nowiki></code>
* Use the [[value-class-pattern]] for the <code>type</code> subproperty of the <code>tel</code> property when authoring in a language other than US English (which is used by the enumerated values of the <code>type</code> subproperty).  
* Use the [[value-class-pattern]] for the <code>type</code> subproperty of the <code>tel</code> property when authoring in a language other than US English (which is used by the enumerated values of the <code>type</code> subproperty).


==See also==
==See also==

Revision as of 00:25, 10 July 2012

<entry-title>Internationalization</entry-title> (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