develooper Front page | perl.perl5.porters | Postings from February 2001

Re: The State of The Unicode

Jarkko Hietaniemi
February 19, 2001 17:14
Re: The State of The Unicode
Message ID:
> > My kingdom for one example.

Socket I/O?

Protocols: if all I know is that my output is 500 Unicode characters
long, how am I to print out Content-Length?

If I have a scalar which according to length() is 10E7 Unicode characters,
will it fit within my disk quota of which I have 20E7 bytes left?

> But you don't have to go that low level. uuencode & base64 work with 8-bit
> bytes. Taking your Unicode string, looking at it as bytes, uuencode it,
> send it, receive it, uudecode it and looking at it again as Unicode will
> work - as long as you can get to the bytes representation.

Any encoding which hasn't yet been encoded in Encode?

> A lot of existing compression and encryption software just look at the
> data to be compressed or encrypted as bit or byte streams. There is no
> reason to create Unicode aware versions of those tools before they can
> be used on Unicode data. But to create Perl programs that compresses or
> encrypts data that can be decompressed or decrypted with the existing
> tools, your Perl program needs to be able to look at the data as a
> sequence of bytes.
> When in Rome....
> Abigail

$jhi++; #
        # There is this special biologist word we use for 'stable'.
        # It is 'dead'. -- Jack Cohen Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About