updates.

[silc.git] / TODO

diff --git a/TODO b/TODO
index 56d4abfeba1e97f11eb83a3b378c717ba469ecf3..2f49dc644c2b308f7a8bbba1c9a30fe944d5083e 100644 (file)
--- a/TODO
+++ b/TODO
@@ -14,6 +14,8 @@ TODO/bugs In SILC Client Library
    set the key only if application wishes to set (accept the key) it
    (Do this to 1.0).
 
+ o Remove conn->current_channel.
+
  o Additions to do after protocol version 1.1:
 
        o Add support for list of errors in command replies.  Protocol
@@ -155,5 +157,16 @@ describe new stuff to be added to protocol versions 1.x.
  17. Cell wide channel founder support, and permanent channels when
      founder mode set.
 
- 18. UTF-8 requirement checkings for all specifications, when strings
-     are sent.
+ 18. Describe the SSH public key, X509, OpenPGP and SPKI certificates
+     encoding format in SKE (from their respective definitions).
+
+ o UTF-8 support/requirement for nicknames & channel names.  UTF-8 support
+   in terminals and OS's are so hazy that this matter is left for
+   consideration in next version of the protocol (1.2).  For good UTF-8
+   reference and tutorial see: http://www.cl.cam.ac.uk/~mgk25/unicode.html.
+   What should CLI application do if it receives nickname that it cannot
+   display without messing up the terminal?  If UTF-8 is mandatory in
+   SILC then SILC clients cannot be allowed to start on terminals that do
+   not support UTF-8 (which renders 98% of users unable to use CLI SILC
+   app without hacking their environment).  See also site
+   http://gratrix.net/unicode/