On Sat, Aug 14, 2004 at 12:26:23AM -0400, Michael Stone wrote:
: Finally, (and I'm just thinking about charset stuff here), exceptions
: frequently involve a bit of string processing. So if the
: charset/encoding code starts throwing exceptions, how do we write the
: string processing that thos
Larry Wall wrote:
On Wed, Aug 11, 2004 at 04:16:48PM -0400, Dan Sugalski wrote:
: If it's that handy then someone can write a library routine. This
: feels very much to be in the same category as running a
: speech-to-text algorithm if you send WAV data to a text filehandle.
Well, you can write
Aaron,
I happen to agree with Dan about the unwieldiness of replacing
characters with their full names during character translation, but your
idea of using Unicode equivalents seems more palatable. I'm going to
ignore the issue of how this method of handling errors fits into the
scheme o
On Wed, Aug 11, 2004 at 04:16:48PM -0400, Dan Sugalski wrote:
: If it's that handy then someone can write a library routine. This
: feels very much to be in the same category as running a
: speech-to-text algorithm if you send WAV data to a text filehandle.
Well, you can write a library routine,
At 7:37 PM +1000 8/10/04, Adam Richardson wrote:
I'm not sure how you plan to integrate the database level (or whether it
affects what you are doing at all), but presumably you know all about the
new encoding and collation sets in mySQL 4.1. Things have changed quite a
bit there from 4.0, and I've
At 10:48 AM -0400 8/11/04, Aaron Sherman wrote:
I don't want to argue per-se (that doesn't do anyone any good), so if
your mind is made up, that's cool... still, I think there's some value
in exploring the options, so read on if you're so inclined.
On Wed, 2004-08-11 at 04:40, Dan Sugalski wrote:
I don't want to argue per-se (that doesn't do anyone any good), so if
your mind is made up, that's cool... still, I think there's some value
in exploring the options, so read on if you're so inclined.
On Wed, 2004-08-11 at 04:40, Dan Sugalski wrote:
> > Converting Unicode to non-Unicode c
On Mon, 2004-08-09 at 14:14, Dan Sugalski wrote:
> Additionally if we have source text which is
> Latin-n, EBCDIC, ASCII, or whatever we must be
> able to convert it with no loss to Unicode.
> (Which I believe is now doable with Unicode 4.0)
> Losslessly converting Unicode to
> ASCII/EBCDIC/w
At 4:15 PM -0400 8/10/04, Aaron Sherman wrote:
On Mon, 2004-08-09 at 14:14, Dan Sugalski wrote:
Additionally if we have source text which is
Latin-n, EBCDIC, ASCII, or whatever we must be
able to convert it with no loss to Unicode.
(Which I believe is now doable with Unicode 4.0)
Losslessly co
On Monday, 9 August 2004 at 4:14 AM +1000, Dan Sugalski wrote:
>Since this has been a sore spot lately, and one
>we need to deal with. Might as well formally
>define what that is.
>
>We must be able to:
>
>*) Load in string data from an IO source,
>regardless of its encoding, and treat it as
>Unic
On Mon, Aug 09, 2004 at 02:14:46PM -0400, Dan Sugalski wrote:
> We don't care about on-screen rendering or date/time/money formatting.
And whilst every language out there might need these functions available
to its apps, this sounds like a module for the Comprehensive PIR Archive
Network. (ie I a
11 matches
Mail list logo
