Remove utf-8 todo; as each byte is unique we're fine (woo utf8)

1 files changed, 1 insertions, 11 deletions

diff --git a/TODO b/TODO
index 43c7b19..7addda7 100644
--- a/TODO
+++ b/TODO
@@ -1,4 +1,4 @@
-before 1.0: create bn tool, fix http bugs, be unicode safe, package for osx & windows
+before 1.0: create bn tool, fix http bugs, package for osx & windows
 
 # getbnbook
 
@@ -7,16 +7,6 @@ before 1.0: create bn tool, fix http bugs, be unicode safe, package for osx & wi
 use the correct file extension depending on the image type (for google and amazon
 the first page is a jpg, all the others are png)
 
-use wide string functions when dealing with stuff returned over http; it's known utf8
-	http://triptico.com/docs/unicode.html#utf-8
-	http://www.cl.cam.ac.uk/~mgk25/unicode.html#c
-	this means c99, rather than plain ansi c. worth it.
-	alternative is to just use our own bit of utf-8 handling; we only need to know to skip x number of bytes to get one char at a time, to find next char etc. whether this would get more tricky, being unable to use strcmp etc, to make it not worthwhile, is not yet certain. try it and see if it fits. note st has nice homemade utf8 support.
-OR
-use custom string functions where needed (prob only strstr needed), which work on utf8 specifically, and just skip the appropriate # of chars if it's not an ascii char
-BUT
-see how things are done in plan9, as they're good there
-
 bug in get() & post(): if the \r\n\r\n after http headers is cut off between recv buffers
 
 what happens if we receive not a http header? does recv loop forever, in a memory killing manner?