Re: Base64 encoding on Leopard
Re: Base64 encoding on Leopard
- Subject: Re: Base64 encoding on Leopard
- From: Quinn <email@hidden>
- Date: Wed, 21 Nov 2007 17:22:11 +0000
At 11:51 -0500 21/11/07, Stephen Hoffman wrote:
Having an embedded conversion library would certainly be useful;
whether in CF or CD or otherwise. There are various other formats
where conversions could be useful. URL encoding, EBCDIC, Unicode,
accented Romance text to unaccented text, ROT13, etc. (Ok, ROT13
was a joke.) There are ways to perform these data conversions
scattered around, but AFAICT there's no central document nor central
reference for these existing conversion operations. And no
conversion library.
Actually, CF handles most of this stuff for you.
o URL encoding -- Courtesy of
CFURLCreateStringByReplacingPercentEscapes,
CFURLCreateStringByReplacingPercentEscapesUsingEncoding, and
CFURLCreateStringByAddingPercentEscapes.
o EBCDIC and other text encodings -- CFString handles pretty much any
text encoding that you can think of. While the list of encodings in
"CFString.h" is pretty short, CFString handles most (all?) of the
encodings listed in "TextCommon.h", which is vast.
o stripping diacriticals and other Unicode goodies --
CFStringNormalize, CFStringFold, and CFStringTransform take care of
most of these.
o ROT13 -- Don't think we support that.
Which what makes base64 such an outlier; we use it in multiple places
within CF, but we don't export the implementation.
S+E
--
Quinn "The Eskimo!" <http://www.apple.com/developer/>
Apple Developer Relations, Developer Technical Support, Core OS/Hardware
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden