internationalization: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
AndyMabbett (talk | contribs) (→Background: readability) |
||
| Line 7: | Line 7: | ||
* Internet and web standards in general use US English terms and spelling (ref: W3C, IETF) for elements, attributes, properties, values. | * Internet and web standards in general use US English terms and spelling (ref: W3C, IETF) for elements, attributes, properties, values. | ||
** e.g. (X)HTML is defined in US English (e.g "color", "center"). | ** e.g. (X)HTML is defined in US English (e.g "color", "center"). | ||
* However such standards also strongly advocate the support of character sets such as UTF-8 for broader/better support of | * However such standards also strongly advocate the support of character sets such as UTF-8 for broader/better support of internationalisation content. | ||
==Issues== | ==Issues== | ||
Revision as of 16:12, 22 March 2007
Internationalization
AKA internationalisation, i18n.
What can we do, to make micoroformats more easily usable, by people who are not publishing in (US) English?
Background
- Internet and web standards in general use US English terms and spelling (ref: W3C, IETF) for elements, attributes, properties, values.
- e.g. (X)HTML is defined in US English (e.g "color", "center").
- However such standards also strongly advocate the support of character sets such as UTF-8 for broader/better support of internationalisation content.
Issues
- March 2007 discussion (ongoing) of abbr title for non-English values. Is
<abbr class="type" title="fax">Téléc</abbr>acceptable? - Gender values in Genealogy