On 14 April 2012 18:33, Connor Lane Smith wrote:
> I've written a UTF-8 library based on Plan 9's libutf API, with a
> bunch of improvements [1].
>
> I've tested it on various correct and incorrect inputs and it seems to
> be 100% Unicode compliant (unlike Plan 9), but if anyone finds any
> bugs p
On 14 April 2012 19:24, Nick wrote:
> Also, a bit of documentation would be nice, just a sentence saying
> what each function does, plus an example of its use. I know it isn't
> complicated to work out from the function names, but it's still nice
> to have around.
The functions have descriptive c
On 2012-04-14, Nick wrote:
> One question: is a rune the same as a glyph? Or a codepoint? Or
> what?
‘rune’ == ‘Unicode code point’
> Also, a bit of documentation would be nice, just a sentence saying
> what each function does, plus an example of its use. I know it isn't
> complicated to work o
Looks quite spiffy.
One question: is a rune the same as a glyph? Or a codepoint? Or
what?
Also, a bit of documentation would be nice, just a sentence saying
what each function does, plus an example of its use. I know it isn't
complicated to work out from the function names, but it's still nice
Hey all,
I've written a UTF-8 library based on Plan 9's libutf API, with a
bunch of improvements [1].
I've tested it on various correct and incorrect inputs and it seems to
be 100% Unicode compliant (unlike Plan 9), but if anyone finds any
bugs please tell me.
Might this be useful to have on hg.
