"International Domain Names" support in KDE

[Thiago Macieira]

Marc Mutz wrote:
>This doesn't make sense. They can just as well link against libidn.
>That's what LGPL is all about, isn't it? And they probably should,
>since it's hopefully going to be the std on Linux until gliibc supports
>it directly.

I wasn't planning to link against the library. I was planning on importing the 
code so that support is present everywhere, regardless of system libraries 
supporting it or not.

>They can't reuse the QString tables, since they are subject to updating
>to Unicode 4.0 eventually. IDNA (nameprep) instead directly references
>the Unicode 3.2 tables and _nothing_ else. Using 3.0 (as Qt currently
>seems to be doing) as well as 4.0 tables would result in
>non-compliance.

That much is true. But that doesn't mean some of the code or data can't be 
reused, if it helps reducing the memory footprint. There's also the 
converting side of the story: even though both sides are Unicode, Qt 
currently stores data as UTF-16 while libidn uses UCS-4, which means that we 
must do Unicode-to-Unicode conversion and then back.

Anyways, this won't be my call. The code I've written for Qt is currently 
using libidn, but it'll be up to TrollTech to decide if they will use it or 
if they'll integrate their own support -- to match their other platforms.

-- 
  Thiago Macieira  -  Registered Linux user #65028
   thiagom at mail.com           
    ICQ UIN: 1967141   PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: signature
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20030626/8f6cc235/attachment.sig>