W3C home > Mailing lists > Public > public-payments-wg@w3.org > September 2016

Re: i18n-ISSUE-214: Improper use of languageCode

From: Andre Schappo <A.Schappo@lboro.ac.uk>
Date: Fri, 2 Sep 2016 08:36:54 -0500
Message-Id: <3DBF31FE-384E-4DDD-A040-9FF57311138C@lboro.ac.uk>
To: "www-international@w3.org" <www-international@w3.org>, "Web Payments Working Group" <public-payments-wg@w3.org>

> On 2 Sep 2016, at 10:35, Martin J. Dürst <duerst@it.aoyama.ac.jp <mailto:duerst@it.aoyama.ac.jp>> wrote:
> On 2016/09/02 01:58, Rouslan Solomakhin wrote:
>> On Thu, Sep 1, 2016 at 9:54 AM, John Cowan <cowan@ccil.org <mailto:cowan@ccil.org>> wrote:
>>> Some postal services, like Japan, have separate formats for national and
>>> international addressing, the former being big-endian and the latter
>>> little-endian
>> That's where the language code comes into play. Language codes like "ja-JP"
>> uses the national addressing format in Japan: big endian. Language codes
>> like "en" or "ja-Latn" use international addressing format in Japan: little
>> endian.
> This makes sense at first sight, but is quite ad-hoc. It's totally unclear what "language code" other conventions would use. Also, "ja-Latn" says "Japanese language, written with Latin script", but what you really want to identify is "Japanese (country!) format, when using Latin script". So you would need a country and a script, but not a language. That's not exactly what language codes provide.

The language tag mul-Latn-JP specifies the country and the script without specifying the language.

mul = multiple languages

The IANA language subtag registry contains the entry

Type: language
Subtag: mul
Description: Multiple languages
Added: 2005-10-16
Scope: special

André Schappo

http://twitter.com/andreschappo <http://twitter.com/andreschappo>

Received on Friday, 2 September 2016 13:37:00 UTC

This archive was generated by hypermail 2.3.1 : Friday, 2 September 2016 13:37:00 UTC