internationalization: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
m (Reverted edits by RicbaScace (Talk) to last version by AndyMabbett)
m (Replace <entry-title> with {{DISPLAYTITLE:}})
 
(5 intermediate revisions by 3 users not shown)
Line 1: Line 1:
=Internationalization=
{{DISPLAYTITLE:Internationalization}}
(AKA '''internationalisation''', '''i18n'''.)
(AKA '''internationalisation''', '''i18n'''.)


Line 5: Line 5:


==Background==
==Background==
* Internet and web standards in general use US English terms and spelling (ref: W3C, IETF) for elements, attributes, properties and values.
* To encourage broader/better support of international content, modern internet and web standards strongly advocate the support of character sets such as UTF-8.
** e.g. (X)HTML is defined in US English (e.g "color", "center").
* The vocabularies used in such standards in general use [[en-us|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.
* However such standards also strongly advocate the support of character sets such as UTF-8 for broader/better support of international content.
 
The design of microformats follows both of these well-established practices of modern internet and web standards design.


==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?
*** That code will work in [[hCard]], however, there is now a better solution described in the [[value-class-pattern]].
*[[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 has subsequently been resolved with a new [[gender]] property in vCard4/hCard1.1 ([[uf2|hCard2]] as well)


==Solutions==
==Solutions==
Line 18: 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).


==See also==
==See also==
*[[en-us]]
*[[en-us-faq]]
*[[naming-principles]]
*[[minimal-vocabulary]]
*[[value-class-pattern]]
*[[faq#Q: How do microformats breach language barriers?|FAQ: How do microformats breach language barriers?]]
*[[faq#Q: How do microformats breach language barriers?|FAQ: How do microformats breach language barriers?]]
*[[hcard-examples-in-wild#UTF8_Examples|hCards using UTF8]]
*[[hcard-examples-in-wild#UTF8_Examples|hCards using UTF8]]
Line 30: Line 43:
*[[how-to-start-new-translation|how to start a new translation]]
*[[how-to-start-new-translation|how to start a new translation]]


==Internationalization/localization references==
== Internationalization and localization references==
*[http://www.w3.org/International/  WC3 Internationalization and Localization] - Lots of information in all areas.
*[http://www.w3.org/International/  W3C Internationalization and Localization]
*[http://en.wikipedia.org/wiki/Internationalization_and_localization Wikipedia's definition] - As well as further links to related articles.
*[http://en.wikipedia.org/wiki/Internationalization_and_localization Wikipedia's definition of internationlization and localization]
*[http://www.lisa.org/ The Localization Industry Standards Association] - Some information requires site registration (like the primer), but not paid membership. Specific marketing details require paid membership.
*[http://www.lisa.org/ The Localization Industry Standards Association] - Some information requires site registration (like the primer), but not paid membership. Specific marketing details require paid membership.
*[http://www.useit.com/alertbox/9608.html Jakob Nielsen's Alertbox article on localization] - To remind this is actually for people first.
*[http://www.useit.com/alertbox/9608.html Jakob Nielsen's Alertbox article: International Web Usability] - which aligns with the microformats [[principle]] for humans first, machines second.

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