From: Scott Woods (scottw_at_[hidden])
Date: 2007-06-27 16:15:37
----- Original Message -----
From: "Scott Woods" <scottw_at_[hidden]>
Sent: Tuesday, June 26, 2007 2:57 PM
Subject: Re: [boost] [rfc] I/O Library Design
>>I don't think any of the transformation are accurately represented as
>> encoding a byte stream as text. I'll quickly address base-64 because it's
>> different from the others; this is a bitstream representation that
>> to tolerate being interpretted as character data in most scenarios
>> (base-32 also tolerates case conversion - so it's suitable for HTTP
> Sorry but not responding to your mail specifically but all of the recent
> postings on this topic.
> A need for the latter example might arise where the interpretation input
> only ever
> viewed by developers and support staff (all speaking English) while the
> stored content is
> being viewed and modified at many sites around Europe.
> There is a lot more that I can inject into this thread but before I make a
> tit of myself,
> is this making sense to anyone else?
I'll take that as a no :-) Maybe my concepts could do with a bit more work.
The detail on unicoding has been great. Thanks.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk