On 1/25/05 7:45 PM, "Martin Duerst" <[EMAIL PROTECTED]> wrote:
> > At 01:52 05/01/26, Paul Hoffman wrote: >> >> At 9:16 AM +0100 1/25/05, Julian Reschke wrote: >>> I saw some concerns (with which I agree) that requiring the presence of > an IDN library is problematic. As far as I can tell, it's likely to be > ignored by developers of clients that run on somwehat constrained devices. > > Just a correction to what Julian wrote: Stringprep may be ignored > or partially ignored, because it requires lots of data, but I don't > think the Unicode->punycode conversion will be ignored. > > >> I would like to hear more from developers whether or not they think this > is a problem. (I'm asking this wearing my co-chair-looking-for-consensus > hat, not my author-of-IDN-and-stringprep hat.) > > Although I don't have any experience with developing blogging tools, > I have some experience in integrating IDN support into a browser, and > I can report on some other browsers. I hope this breaks the ice for > others to chip in. > >From an SDK perspective, there are a number of libraries available to handle IDN support. As a Java person developing blogging tools, I've looked at the following. Hope this helps. Name: IDN SDK Vendor: Verisign URL: http://www.verisign.com/products-services/naming-and-directory-services/nami ng-services/internationalized-domain-names/idn-registrars/page_001408.html License: Apache/BSD Name: Java-IDNA (now part of GNU IDN Library) Vendor: GNU URL: http://www.gnu.org/software/libidn/ License: LGPL International Components for Unicode for Java (there are also C/C++ bindings which also have IDN support) Vendor: IBM URL: http://oss.software.ibm.com/icu4j/ License: IBM Open Source License ( http://oss.software.ibm.com/cvs/icu/~checkout~/icu/license.html) -David
