On Thu, Apr 20, 2006 at 10:10:19PM +0300, Niko Tyni wrote: > > I guess a quick (and temporary solution) would be to upload the new > > revision of libi18n-charset-perl in order to get the new version in > > and close #329561. OTOH there's probably no hurry for the new version > > either ... > Yes, I think it's easiest to handle these concurrently. Thus one issue > is patching libi18n-charset-perl now and the other is trying to push the > libunicode-map8-perl patches upstream. Ok. > I just did the latter, it's CPAN #18802. Sorry for not doing it earlier. Thanks! > Gregor or eloy, will you take care of libi18n-charset-perl? AFAICT, > it's only missing a proper changelog entry Done. > (although patching DOS-style > newlines away in t/utf8.t seems a bit excessive). I think the bold ^M were too annoying for me ;-) Is this conversion doing any harm? > It might be nice to > have libapp-info-perl for the tests, though (ITP #362967). I have to admit that I'm not really sure how this module actually could be used in this context ... Cheers, gregor -- .''`. http://info.comodo.priv.at/ | gpg key ID: 0x00F3CFE4 : :' : infos zur usenet-hierarchie at.*: http://www.usenet.at/ `. `' member of https://www.vibe.at/ | how to reply: http://got.to/quote/ `-
Attachment:
signature.asc
Description: Digital signature