Re: one-language solution

[James Seng <jseng@pobox.org.sg>]

Dear all,

First of all, I agreed with Paul assesment of how different language/encodings
system will be horrible. It is the same reason why a MIME type approach is not
viable as I tried to explain again and again. But before we go into such
detail discussion of various possible implementation, lets stay on the
requirement doc.

I asked about one-language solutions because I know of many attempts to do a
localized DNS. Localized DNS in the sense that they make the DNS 8-bit cleans
and then used localized encoding in the zones. This is probably the simpliest
and most obvious solution but of course it has a *lot* of problems.

One of which is interoperability, ie how do we ensure a ISO-2022-JP DNS able
to interoperable with EUC-JP DNS, or GB DNS and BIG5 DNS. How do the zone file
match, how to get unified results etc.

-James Seng

"Martin J. Duerst" wrote:
> 
> At 14:39 00/01/23 +0800, James Seng wrote:
> 
> > One solution for all language is always an ideal. But do we want to set this
> > as an requirement? Why not be more flexible allowing different implementations
> > for different language/charset?
> 
> As I have said, it's unclear how to guess the language of a
> label printed on paper. Most scripts are used to write more
> than one language. I wouldn't want to have a German DNS,
> a French DNS, and a Japanese DNS. Which browser or resolver
> would I use in my daily work? Can you please explain how
> that could work?
> 
> Regards,   Martin.
> 
> #-#-#  Martin J. Du"rst, World Wide Web Consortium
> #-#-#  mailto:duerst@w3.org   http://www.w3.org