Re: PEAR Account Request: dr
| From: | Stefan Neufeind | Date: | Sat, 08 May 2004 16:46:02 +0000 |
| Subject: | Re: PEAR Account Request: dr | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-29029@lists.php.net to get a copy of this message | ||
On 8 May 2004 at 18:40, David Rech wrote:
> Stefan Neufeind wrote:
> > On the one hand I think that it might simply go into the current
> > package I18N as a separate class/file. Another solution I can think
> > of would be I18N_Punycode. But to my understanding it's more tied to
> > internationalisation (or charset-conversions) than real "Net", isn't
> > it?
> >
> > Stefan
> >
>
> I agree on I18N_Punycode. Maybe we should add the Stringprep stuff as
> I18N_Text, I18N_Characters or something like that to the existing I18N
> package?
>
> This would add character mapping to the I18N package.
>
> Stringprep with its character mapping could be usefull for I18N related
> things other than Punycode anytime later.
Well, you need quite large tables for complete Stringprep-conversions
strictly according to the RFCs. Currently I only have the Nameprep
profile implemented and the tables needed for this to implement it
fully. Even these are quite large. To make them smaller and faster to
load they are currently stored in serialized format in my package.
Since nameprep is afaik only used in conjunction with punycode I'd
propose to simply have them as private functions inside the class,
for now. If need arises we can at a later step simply separate it to
a separate package (because of the large tables). I'm against adding
that burden to the I18N-package.
Stefan