headers
Rick Wesson | 5 Feb 08:06

punnycode in java?


anyone know of a implementation of punny code in java? If I can't find a
LGPL'ed version I'll go off an write one, but I wanted to check if someone
else hand't done it first.

thanks,

-rick
Permalink | Reply | 0 comments |
headers
Hilde Margrethe Thunem | 6 Feb 09:04
Picon
Picon
Favicon

Using draft-jseng-idn-admin-01.txt


I've been looking at the "Internationalized Domain Names Registration 
and Administration Guideline for Chinese, Japanese and Korean" 
(draft-jseng-idn-admin-01.txt)

It looked rather interesting as a language to express a policy in if 
there is characters that could be seen as variants of each other. As I'm 
from a Norwegian background I've looked at using the guidelines in the 
draft to describe an administrative domain name policy for the Norwegian
language, with a language character variant table. In Norwegian there
are few (if any) characters that may be said to be variants of each 
others in all instances where they are used. The closest we get is 
perhaps by dropping the accents (using o as a predominant variant of ó 
and ò) but as e.g. "for", "fór" and "fòr" has three different meanings 
(for, travelled and furrow) it is not immideately given that they should 
be stuck together in one IDL package. There is also certain characters 
that is imported fom neighbouring languages and used in Norwegian names, 
that sound similar in speech to already existing Norwegian characters 
(e.g ø and ö). These may be considered variants of each others. (And even 
if in the end the administrative policy is that all characthers has no
variants, the draft does give a way of easily expressing both that fact, 
and expressing which characters are within the set of valid code points.)

Having tried to use it, I have a few questions concerning the interpretation 
of the different groups in the language character variant table. As far as I 
can see the recommended variants must also be valid codepoints, and result 
in domain names that are in the zonefile, while character variants are merely 
reserved when a valid combination is registered and are not in themselves 
added to the zonefile. In addition, character variants that aren't valid 
codepoints can't be the "starting point" for an IDL package.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Marcos Sanz/Denic | 6 Feb 11:21
Picon
Favicon

Re: punnycode in java?

On 05.02.2003 08:06 Rick Wesson <wessorh <at> ar.com> wrote:
>
> anyone know of a implementation of punny code in java? If I can't find a
> LGPL'ed version I'll go off an write one, but I wanted to check if someone
> else hand't done it first.

I haven't found any. If this is confirmed, I would contribute to write one.

Regards,
Marcos Sanz
DENIC eG
Permalink | Reply | 0 comments |
headers
Paul Hoffman / IMC | 6 Feb 19:23
Picon
Gravatar

New draft on internationalizing email addresses

Greetings. This message is Bcc'd to many IETF-related lists that are 
discussing internationalization, Internet mail and Usenet. With the 
imminent release of the RFCs for IDNA, Adam Costello and I have a 
proposal for allowing internationalized characters in email addresses 
(on both sides of the @). Instead of having it discussed on a bunch 
of different lists, there is a new list for discussing the draft and 
other ideas related to internationalizing email address.

If you are interested, please see <http://www.imc.org/ietf-imaa/> for 
information on the Internet Draft and the mailing list.

--Paul Hoffman, Director
--Internet Mail Consortium
Permalink | Reply | 0 comments |
headers
Roozbeh Pournader | 9 Feb 19:32

Re: Using draft-jseng-idn-admin-01.txt

On Thu, 6 Feb 2003, Hilde Margrethe Thunem wrote:

> And while I'm asking questions, has any of you in the WG used the draft for 
> creating a draft policy for a language?

I am writing an I-D based on draft-jseng-idn-admin for policies for
Arabic, Persian, Urdu, and Pashto. I will post it here when I finished it.

roozbeh
Permalink | Reply | 0 comments |
headers
James Seng | 10 Feb 02:44
Picon

Re: Using draft-jseng-idn-admin-01.txt

Hi Hilde,

> It looked rather interesting as a language to express a policy in if
> there is characters that could be seen as variants of each other. As I'm
> from a Norwegian background I've looked at using the guidelines in the
> draft to describe an administrative domain name policy for the Norwegian
> language, with a language character variant table.

To be exact, you can break the document into two sections:

a) How to generate variants of an IDN?
b) How do you handle all these variants?

For (a), the document describe a mechanism using language variants tables
and also an aglorithm to generate variants. This designed specifically for
CJK so I am not sure much Norwegian can use the same concept.

For (b), the document describe a mechanism of an IDN Package (IDL), how this
is registered, transferred, deleted, activiated, de-activated etc. I believe
this would be more or less consistent across different languages.

> Having tried to use it, I have a few questions concerning the
interpretation
> of the different groups in the language character variant table. As far as
I
> can see the recommended variants must also be valid codepoints, and result
> in domain names that are in the zonefile, while character variants are
merely > reserved when a valid combination is registered and are not in
themselves
> added to the zonefile. In addition, character variants that aren't valid
(Continue reading)

Permalink | Reply | 0 comments |
headers
IANA | 10 Feb 23:43
Favicon

FW: IANA Selection of IDNA Prefix

IDN Working Group--

This is the final version of the Protocol and Schedule for 
Selecting the IDNA Prefix.   	

Best regards,

Michelle S. Cotton
IANA Administrator

This document sets forth the protocol by which the IANA will select 
a two-character code to be used as the first two characters of
the ACE prefix referred to as "IESG--" in Section 5 of
draft-ietf-idn-idna-14.txt. It also specifies the schedule for
the selection.

This document is based on the IANA's proposed Protocol and Schedule
distributed on 30 January 2003 and reflects changes to address 
comments received by 6 February 2003.  The IANA thanks Adam Costello
and Simon Josefsson for their comments.

A. Protocol

The following steps will be used to select the two-character code:

1. The code will be selected from among a subset of the entries on
the ISO 3166-1:1997, clause 8.1.3 User-assigned alpha-2 code elements:
AA, QM to QZ, XA to XZ, and ZZ.  The selection is limited to these 
codes because of the following:
(Continue reading)

Permalink | Reply | 0 comments |
headers
IANA | 12 Feb 03:17
Favicon

Results of IANA Selection of IDNA Prefix


Results of IANA Selection of IDNA Prefix

As described in section B of the Protocol and Schedule
(see below), today 11 February 2003 (Tuesday), is the
Selection Day.

The IANA followed the steps described in section 4 (see
below).

The twelve stocks and their trading volumes (in 100s) were:

(NYSE) IMS Hlth RX            22157
(NYSE) IL Tool ITW            11795
(NYSE) IntRectifr IRF          5742
(NYSE) IBM IBM                78719
(NYSE) IntPaper IP            16609
(NYSE) Interpublic IPG        34961
(NASDAQ) Inamed IMDC           1567
(NASDAQ) Informatica INFA      4357
(NASDAQ) Inktomi INKT          6085
(NASDAQ) i2 Tch ITWO          37777
(NASDAQ) IDEC Pharm IDPH      18754
(NASDAQ) Intel INTC          524545

These trading volumes have been used to generate a key
string in the manner specified on page 5 of RFC 2777.

The key string is
(Continue reading)

Permalink | Reply | 0 comments |
headers
John Wall | 13 Feb 17:03

Punycode conversion tool

I am looking for an IDNA conversion tool using 
the ACE prefix available since yesterday.

Can anybody help me?

Thank you

J.W.

Sent by Go2net Mail!
Permalink | Reply | 4 comments |
headers
Yoshiro YONEYA | 13 Feb 17:39
Picon

Re: Punycode conversion tool

On Thu, 13 Feb 2003 11:03:18 -0500, "John Wall" <johwal <at> go2netmail.com> wrote:

> I am looking for an IDNA conversion tool using 
> the ACE prefix available since yesterday.
> 
> Can anybody help me?

Sure :-)

Try idnkit which is available from following URL:

    http://www.nic.ad.jp/ja/idn/mdnkit/download/#sources
    ==> idnkit-1.0pr2

By default, the idnkit-1.0pr2 uses 'zq--' as ACE prefix.
But it can be changed to 'xn--' by using '--with-punycode-prefix=xn--'
configure option.  Please read 'INSTALL' for more detail.

--

-- 
Yoshiro YONEYA <yone <at> po.ntts.co.jp>
           aka <yone <at> nic.ad.jp>
Permalink | Reply | 0 comments |

Gmane