W3C mailing list search service
Search among 2,289,786 messages in the W3C mailing list archives:
Closed: [i18n-activity] i18n-ISSUE-484: Use BCP47 instead of ISO 639-1 for identifying languages (#87)
- Date
- Thu, 14 Nov 2019 16:04:06 +0000
- Author
- r12a via GitHub <sysbot+gh@w3.org>
Re: [i18n-activity] i18n-ISSUE-484: Use BCP47 instead of ISO 639-1 for identifying languages (#87)
- Date
- Thu, 14 Nov 2019 16:04:06 +0000
- Author
- r12a via GitHub <sysbot+gh@w3.org>
Re: i18n-ISSUE-484: Use BCP47 instead of ISO 639-1 for identifying languages
- Date
- Mon, 21 Sep 2015 14:50:07 +0900
- Author
- Martin J. Dürst <duerst@it.aoyama.ac.jp>
This is indeed very important. Chinese is only one example. For those who may not know, mainland China and Singapore use simplified, Hong Kong and Taiwan use traditional. This distinction is therefor
Re: i18n-ISSUE-484: Use BCP47 instead of ISO 639-1 for identifying languages
- Date
- Mon, 21 Sep 2015 14:50:07 +0900
- Author
- Martin J. Dürst <duerst@it.aoyama.ac.jp>
This is indeed very important. Chinese is only one example. For those who may not know, mainland China and Singapore use simplified, Hong Kong and Taiwan use traditional. This distinction is therefor
i18n-ISSUE-484: Use BCP47 instead of ISO 639-1 for identifying languages
- Date
- Thu, 17 Sep 2015 13:47:36 -0400
- Author
- "Steven Atkin" <atkin@us.ibm.com>
i18n-ISSUE-484: Use BCP47 instead of ISO 639-1 for identifying languages
- Date
- Thu, 17 Sep 2015 13:47:36 -0400
- Author
- "Steven Atkin" <atkin@us.ibm.com>
I18N-ISSUE-484: Use BCP47 instead of ISO 639-1 for identifying languages â [vehicle-information-access]
- List
- public-i18n-core
- Date
- Wed, 19 Aug 2015 16:05:58 +0000
- Author
- "Internationalization Working Group Issue Tracker" <sysbot+tracker@w3.org>
I18N-ISSUE-484: Use BCP47 instead of ISO 639-1 for identifying languages ⓟ [vehicle-information-access] http://www.w3.org/International/track/issues/484 Raised by: Steven Atkin On product: vehicle-
Help and hints for using this service
W3C Member? Check the Member-only interface. W3C staff? Use the Team-only interface.