headers
Frank Bennett | 1 Sep 04:51
Picon

Variant request: Japanese modified Hepburn

Request for variant registration

   1. Name of requester: Frank Bennett
   2. E-mail address of requester: bennett <at> law.nagoya-u.ac.jp
   3. Record Requested:

      Type: variant
      Subtag: Hepburn
      Description: Revised Hepburn romanization
      Prefix: ja

   4. Intended meaning of the subtag:
       Indicates the target content is Japanese text, romanized
according to the rules by the modified Hepburn system of romanization.

   5. Reference to published description of the language (book or article):
       Unofficial reference with onward links:
http://en.wikipedia.org/wiki/Hepburn_romanization

   6. Any other relevant information:
       The immediate need for this is in the context of bibliography
management, where alternate representations of a title, name or other
field must be offered for sorting or display purposes.  Revised
Hepburn is the most common transliterated form used for Japanese
content where the native script (Han + kana) is not supported by the
publisher.
Permalink | Reply | 8 comments |
headers
Phillips, Addison | 1 Sep 05:28
Picon
Favicon

RE: Variant request: Japanese modified Hepburn

This probably should have the prefix "ja-Latn". Are you using Hepburn in contrast to some other scheme? As
the predominant romanization, it may not require its own subtag. The tag "ja-Latn" would presumably
imply Hepburn.

Please note that the subtag needs to be all lowercase (hepburn) if/when submitted to IANA.

Regards,

Addison

Addison Phillips
Globalization Architect -- Lab126

Internationalization is not a feature.
It is an architecture.

> -----Original Message-----
> From: ietf-languages-bounces <at> alvestrand.no [mailto:ietf-languages-
> bounces <at> alvestrand.no] On Behalf Of Frank Bennett
> Sent: Monday, August 31, 2009 7:51 PM
> To: ietf-languages <at> iana.org
> Subject: Variant request: Japanese modified Hepburn
> 
> Request for variant registration
> 
>    1. Name of requester: Frank Bennett
>    2. E-mail address of requester: bennett <at> law.nagoya-u.ac.jp
>    3. Record Requested:
> 
>       Type: variant
(Continue reading)

Permalink | Reply | 3 comments |
headers
John Cowan | 1 Sep 06:06

Re: Variant request: Japanese modified Hepburn

Phillips, Addison scripsit:

> This probably should have the prefix "ja-Latn". Are you using Hepburn
> in contrast to some other scheme? As the predominant romanization,
> it may not require its own subtag. The tag "ja-Latn" would presumably
> imply Hepburn.

There are at least two other major schemes, per Wikipedia (there are
others):

	nihon-shiki (ISO 3602 strict), which is a straight transliteration
	of kana

	kunrei-shiki (ISO 3602), which is a morphophonemic modification
	of the above adapted to modern pronunciation.

In any case, there's certainly no ban on registering just a single
variant subtag, anyway; the others can be registered later as needed.
I do think that the Prefix should be ja-Latn, though (remembering that
this is just a recommendation, not mandatory).

--

-- 
A witness cannot give evidence of his           John Cowan
age unless he can remember being born.          cowan <at> ccil.org
  --Judge Blagden                               http://www.ccil.org/~cowan
Permalink | Reply | 1 comment |
headers
Phillips, Addison | 1 Sep 06:34
Picon
Favicon

RE: Variant request: Japanese modified Hepburn

> 
> In any case, there's certainly no ban on registering just a single
> variant subtag, anyway; the others can be registered later as
> needed.

Nor would I imply that there is one. The question, left to the requester, is whether a variant is needed in
this case. Typically-but-not-exclusively a variant is in contrast to something (a predominant variety
or another variation). I don't oppose registering this value. I merely questioned whether it was
necessary given the use case cited.

Addison

Addison Phillips
Globalization Architect -- Lab126

Internationalization is not a feature.
It is an architecture.
Permalink | Reply | 0 comments |
headers
Michael Everson | 1 Sep 09:06
Favicon
Gravatar

Re: Variant request: Japanese modified Hepburn

Frank,

Since there are *three* flavours of Hepburn romanization, would it not  
be better to have subtags for all of them? Otherwise people wishing to  
tag something might mis-tag. Or?

Michael Everson * http://www.evertype.com/
Permalink | Reply | 2 comments |
headers
John Cowan | 1 Sep 09:19

Re: Variant request: Japanese modified Hepburn

Michael Everson scripsit:

> Since there are *three* flavours of Hepburn romanization, would it not
> be better to have subtags for all of them? Otherwise people wishing
> to tag something might mis-tag. Or?

There are three current and two obsolete flavors.  However, the
differences are trivial, in no way affect intelligibility, and no one
has asked to distinguish them.

--

-- 
John Cowan  cowan <at> ccil.org  http://ccil.org/~cowan
In computer science, we stand on each other's feet.
        --Brian K. Reid
Permalink | Reply | 1 comment |
headers
Michael Everson | 1 Sep 09:45
Favicon
Gravatar

Re: Variant request: Japanese modified Hepburn

On 1 Sep 2009, at 08:19, John Cowan wrote:

> Michael Everson scripsit:
>
>> Since there are *three* flavours of Hepburn romanization, would it  
>> not
>> be better to have subtags for all of them? Otherwise people wishing
>> to tag something might mis-tag. Or?
>
> There are three current and two obsolete flavors.  However, the
> differences are trivial, in no way affect intelligibility, and no one
> has asked to distinguish them.

John. Don't be so dismissive.

Intelligibility is an ingredient which we, who have minds, add to the  
soup. Language subtags can be used, for instance, to identify text and  
to perform operations on it, like conversion. We have three subtags  
for Cornish orthographies and will have two or three more.

My question to Frank stands, since his request was for only one  
flavour of Hepburn romanization (a specifically-named flavour).

Michael Everson * http://www.evertype.com/
Permalink | Reply | 0 comments |
headers
Håvard Hjulstad | 1 Sep 09:37
Picon
Favicon

ISO 639 JAC decision - Bihari languages

The ISO 639 Registration Authorities’ Joint Advisory Committee (JAC) has decided:

 

Identifiers: bh & bih (no change)

 

English name: Bihari languages (changed from Bihari)

 

French name: langues biharis (changed from bihari)

 

The item is now recognized as a “language collection” rather than an “individual language”.

 

Best regards,

Håvard Hjulstad

 

--------------------

Håvard Hjulstad

  (prosjektleder / Project Manager)

  Standard Norge / Standards Norway
  Postboks 242, NO-1326 Lysaker
  besøksadresse / visiting address: Strandveien 18
  tel: (+47) 67838600  |  faks / fax: (+47) 67838601
  direkte tel / direct tel: (+47) 67838645
  mobil / mobile (+47) 90145563
  hhj <at> standard.no
  http://www.standard.no/
--------------------

P Tenk på miljøet før du skriver ut denne e-posten. / Please consider the environment before printing this e-mail.

 

_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Permalink | Reply | 0 comments |
headers
Håvard Hjulstad | 1 Sep 09:42
Picon
Favicon

ISO 639 JAC decision - Himachali languages

The ISO 639 Registration Authorities’ Joint Advisory Committee (JAC) has decided:

 

Identifier: him (no change)

 

English name: Himachali languages; Western Pahari languages (changed from Himachali)

 

French name: langues himachalis; langues paharis occidentales (changed from himachali)

 

The item is now recognized as a “language collection” rather than an “individual language”.

 

Best regards,

Håvard Hjulstad

 

--------------------

Håvard Hjulstad

  (prosjektleder / Project Manager)

  Standard Norge / Standards Norway
  Postboks 242, NO-1326 Lysaker
  besøksadresse / visiting address: Strandveien 18
  tel: (+47) 67838600  |  faks / fax: (+47) 67838601
  direkte tel / direct tel: (+47) 67838645
  mobil / mobile (+47) 90145563
  hhj <at> standard.no
  http://www.standard.no/
--------------------

P Tenk på miljøet før du skriver ut denne e-posten. / Please consider the environment before printing this e-mail.

 

_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Permalink | Reply | 0 comments |
headers
Doug Ewell | 1 Sep 14:13
Favicon

Re: ISO 639 JAC decisions - Bihari languages and Himachali languages

Håvard Hjulstad <HHj at standard dot no> wrote:

> The ISO 639 Registration Authorities' Joint Advisory Committee (JAC) 
> has decided:
>
> Identifiers: bh & bih (no change)
>
> English name: Bihari languages (changed from Bihari)

and

> Identifier: him (no change)
>
> English name: Himachali languages; Western Pahari languages (changed 
> from Himachali)

I will post revised records and registration forms for changing the 
Description fields for these two subtags to match the new ISO 639 names. 
They are already referenced in the LSR as "Scope: collection", so no 
change is needed there.

--
Doug Ewell  *  Thornton, Colorado, USA  *  RFC 4645  *  UTN #14
http://www.ewellic.org
http://www1.ietf.org/html.charters/ltru-charter.html
http://www.alvestrand.no/mailman/listinfo/ietf-languages  ˆ

_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Permalink | Reply | 27 comments |

Gmane