After my discussion, I've included an annotated copy of the functions,
where I've added my comments after each function.
So, assuming (hah!) that I correctly understood everything in the draft,
It seems that I have several general concerns:
1. Why are lists of bits or bytes that are being inter
Hi Dan & Michael,
As a guy who speaks a strange language (multi byte chars, multi glyph
chars, caseless
text and half vowels) , I think you have made it too complicated than
it should be .
> charset end of things, offsets will be in graphemes (or Freds. I
> don't remember what we finally decided
At 2:19 PM +0530 8/11/04, Gopal V wrote:
Hi Dan & Michael,
As a guy who speaks a strange language (multi byte chars, multi glyph
chars, caseless
text and half vowels) , I think you have made it too complicated than
it should be .
This scared me some, as I've not gotten to the complicated part... :
At 11:29 PM -0400 8/9/04, Michael Stone wrote:
After my discussion, I've included an annotated copy of the
functions, where I've added my comments after each function.
So, assuming (hah!) that I correctly understood everything in the
draft, It seems that I have several general concerns:
1. Why
These are the details for the encoding API. This is the layer that
mediates between parrot, which sees strings as a sequence of
codepoints, and the low-level buffer, which is filled with bytes.
Note that the charset layer lives above this, but since I've not
finished that part yet I f
