[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Followup on the ccharset idea



* Ian Kumlien <pomac@vapor.com> [031020 19:53]:
> On Tue, 2003-10-21 at 01:38, Michael Edenfield wrote:
> > * Rimas Kudelis <rq@akl.lt> [031020 18:09]:
> > > hostnames with national symbols? not bad, but not now.. not yet..
> > > Hey, are they standartized in any way? and if yes, then how? I *HOPE* they
> > > will use UTF-8, and not ISO-8859-1-15, etc for servernames, right?
> > > In that case, X-chat just needs a patch, which will always try to resolve
> > > hostnames in UTF-8. And it's rather a bug if it doesn't do that now.
> > 
> > Yes, they are standardized.  As of March this year, IETF finalized their
> > proposals and put some RFC's on the standards track.
> > 
> > Verisign has been testing internationalized domain names (IDN) for about
> > 2.5 years in a .com/.net IDN testbed.  Netscape 7.1 is, I beleive, the
> > only major application to support them.
> 
> And Moz 1.4 =)
> 
> > See RFC's http://www.ietf.org/rfc/rfc3490.txt, rfc3491.txt, rfc3492.txt.
> > 
> > But IDN support in XChat is a much different issue than changing the
> > default and/or current character set.  To that issue, I have two
> > contributions (if you consider them that!) to the discussion:
> 
> Well, no, not if you are forced to change the charset that the entire
> app uses.

IDN is independant of the current character set -- that's the point.
Implementing a default character set in X-Chat would have no effect on
implementing IDN, as the names would have to be converted into the IDN
format from whatever character set you're using.

--Mike

PGP signature