On Wed, 10 Apr 2002 02:01:34 -0600, [EMAIL PROTECTED] (Sean M. Burke)
wrote:
> Random question: Has anyone besides me had occasion to use Text::Unidecode?
I've played around with it once or twice (and sent you the occasional
patch, IIRC), but never used it in anger.
Cheers,
Philip
I've got a feeling 5.8.0 will be a reality, not something like a horizon
which is always there in front of you but you can never reach, when I
release ver. 1.33 of Encode. Available as follows;
Whole:
http://www.dan.co.jp/~dankogai/Encode-1.33.tar.gz
and CPAN
Diff against curre
On Thursday, April 11, 2002, at 04:30 , Philip Newton wrote:
> Can you please change my email address to '[EMAIL PROTECTED]', please?
> Thanks!
> (That's also what's in the main Perl AUTHORS file.)
Sure. Fixed.
Dan
On Sun, 31 Mar 2002, Dan Kogai wrote:
Hi Dan,
> >piconv -- iconv(1), reinvented in perl
> >
> >piconv is perl version of iconv, a character encoding con-
> >verter widely availabe for various unixen today. This
> >script was primarily a technology demostrator f
On Wed, 10 Apr 2002 05:30:29 +0900, [EMAIL PROTECTED] (Dan Kogai)
wrote:
> ! lib/Encode/Supported.pod
> ! lib/Encode/Unicode.pm
>POD revise by Philip Newton. This adds Philip to AUTHORS list.
>Thank you for the exact quote of Douglas Adams :)
>Message-Id: <[EMAIL PROTECTED]>
:) You'
> I was going to write "Why not define your own OO layer for Encode.pm,
> like Encode::Encoder?" But I noticed there *is* already a
> Encode::Encoder class.
>
> Encode::Encoder -- Object Oriented Encoder
>
> ;)
Ah, completely missed that. That works :)
thanks
--d
At Wed, 10 Apr 2002 09:05:55 -0700,
Daisuke Maki wrote:
> I do realize it's a style issue. I don't feel particularly strongly
> about this, but it just seems odd that a core module would do this.
I was going to write "Why not define your own OO layer for Encode.pm,
like Encode::Encoder?" But I
> What's wrong with
>
> use Encode ();
>
> ?
I do realize it's a style issue. I don't feel particularly strongly
about this, but it just seems odd that a core module would do this.
Anyway, my point is that I just shudder at the thought of modules
polluting my namespace by default in gener
On Wed 10-Apr-2002 at 02:01:34AM -0600, Sean M. Burke wrote:
> Random question: Has anyone besides me had occasion to use Text::Unidecode?
Yes I do. Our application uses Text::Unicode as a fallback when no
better transliterator is available to romanize content. This is used to
build human readabl
Anton,
> - several typos
> - excludes GBK from that section because
> it is discussed in Microsoft-related
>
> Just routine.
Thank you. Applied. Since this is purely of documentation, chances
are it will go with 5.8.0-RC2 at least and should there be any code
change BEFORE RC1, 5.8.0-RC1.
At Tue, 09 Apr 2002 13:03:17 -0700,
Daisuke Maki wrote:
> ( don't know if this is the correct mailing list to throw this to -- pls
> feel free to redirect me to the appropriate parties )
I think this list is the appropriate place.
> I suspect that there are a lot of us out there who don't nec
Hello, Dan!
- several typos
- excludes GBK from that section because
it is discussed in Microsoft-related
Just routine.
/Anton/
P.S. You've done a cozy text aligment-arrangement,
nice to look at! :-)
--- ext/Encode/lib/Encode/Supported.pod.origWed Apr 10 01:13:28 2002
> On Wed, 10 Apr 2002 02:01:34 -0600, "Sean M. Burke" <[EMAIL PROTECTED]> said:
> Random question: Has anyone besides me had occasion to use Text::Unidecode?
Sorry, no. I was interested, but my decoding needs are both so limited
and Text::Unidecode didn't meet my requirements, so I made up
> On Wed, 10 Apr 2002 04:04:42 +0900, Dan Kogai <[EMAIL PROTECTED]> said:
> On Wednesday, April 10, 2002, at 03:58 , Jarkko Hietaniemi wrote:
>>
>> Encode::Alias::resolve_alias(), to go with define_alias()?
> Well, be it resolve_alias().
Maybe it's nit-picking, but I find this one a
Random question: Has anyone besides me had occasion to use Text::Unidecode?
--
Sean M. Burkehttp://www.spinn.net/~sburke/
On Wed, Apr 10, 2002 at 06:38:00AM +0900, Dan Kogai wrote:
> On Wednesday, April 10, 2002, at 05:34 , Jarkko Hietaniemi wrote:
> >I'm afraid I've got one change at least coming up, I want to implement
> >the Configure -Uusecjk, so people with memory/disk footprint worries
> >can leave out the CJK
( don't know if this is the correct mailing list to throw this to -- pls
feel free to redirect me to the appropriate parties )
I just took a look at the latest Encode API, and I think it looks very
nice. One gripe I have is, though, that the API consists of such simple,
oft-used function names, w
17 matches
Mail list logo
