[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: General internationalization
At 16:20 00/01/17 +0800, James Seng wrote:
> Paul Hoffman / IMC wrote:
> > Implementation must specify what character
> > sets are used and how these characters are encoded in the DNS names
> > and records.
> > This is bad. I strongly disagree that there is a *requirement* for
> > multiple character sets or encodings. Those who feel that this is a
> > requirement should say why it is so. I believe that adding "All" to the
> > beginning of the first sentence is sufficient.
>
> Ok, i think it is bad phrasing. I do not mean there is a requirement for
> multiple character sets or encodings. What I intent to mean is there should
> not be a requirement to reject multiple character sets. However, each
> character sets are defined properly if multiple are used.
Whether to use a single or multiple encodings is a decision that
will have to be taken at a later stage. I read the above as
trying to say: Whatever character sets/encodings (one or many)
we are going to use, it must always be cristal clear which one
is in use, for each data item.
> > Must allow I18C in DNS RR response.
> > I don't know what an "RR response" is.
>
> Resource Record. e.g A, CNAME, MX etc.
I don't know much about that either, but I leave that to
the DNS experts.
> > Must allow I18C in DNS TXT records.
> > I don't think I agree with this since it has nothing to do with domain names.
> >
> > I18N of domain names should be able to handle mix language characters
> > and script, within the same label and/or within the same FQDN.
> > [JS: I hear at least one strong objections to this]
> > Yes, you hear right. I do not see a requirement for language tagging
> > in internationalized names. Can you say why this is required?
>
> Mix language need not be handled by language tagging. There are other ways to
> do it, for example, if you are using Unicode, then it comes very naturely you
> can mix European languages and East Asia language within the same label
> without any tagging.
Questions of language tagging correctly put aside, I think there have
been clear objections to require that there is a need to mix scripts
in labels. In the discussion, we have found a few cases where we
know we want to allow them (numerals and everything else; mixed
Kana/Kanji for Japanese), but the general case is not at all clear;
just saying 'why not' doesn't make this a requirement.
Regards, Martin.
#-#-# Martin J. Du"rst, World Wide Web Consortium
#-#-# mailto:duerst@w3.org http://www.w3.org