Re: FPS/Data.ByteString candidate

ross:
> On Tue, Apr 25, 2006 at 12:08:45PM +0300, Einar Karttunen wrote:
> > The name Latin1 is particularly bad since there are many other
> > single byte encodings around.
> 
> The name is quite appropriate, since that is the particular encoding of
> Char that is exposed by the interface.  What's bad is that there's no
> choice.  Calling it Latin1 is just being honest about that, and leaving
> room for modules with other encodings or an interface parameterized
> by encoding.

Ok. Duncan, Ketil, Ross and Simon make good points here.
I'll move Data.ByteString.Char -> Data.ByteString.Latin1

-- Don