Re: PEAR Account Request: dr

Hi, I'm the lead developer of the PECL idn Extension. I think it wuld be good to have such a PHP based implementation inside PEAR since in future there will be quite a few "internationalized" domain names and note everybody can/want's to install an extension. But I think it would be good if the PHP code would try to use the extension if it's available on the host. Currently the stringprep things aren't available via the extension but I'm planning to implement these soon (like I do with the libidn TLD-Stuff) so I could do this with your requirements in mind. Through the Libidn documentation you can see what I can offer sooner or later with this extension http://www.gnu.org/software/libidn/manual/ If you leave me a note I can change my priorities accordingly. ;-) johannes David Rech wrote: > > Oh yes, these tables are *evil* large. I've divided mine into file/array > pieces. Serializing is quite a fine solution, I think I'd follow on that > and review my stringprep code again. > > Summarized we have two ways to take: > > a) I18N_Punycode for pure punycode en-/decoding, plus I18N_IDN for the > idn_to_*() functionality. > > or > > b) One single I18N_IDN package for all related things to that. > > I'd say b) would be more reasonable than a), because ATM there's no > really need for the mapping abilities build around the IDN. > > I'll hurry up to compare our two solutions ASAP. > > >