diff options
author | nobody <nobody@localhost> | 2003-06-29 00:20:00 +0800 |
---|---|---|
committer | nobody <nobody@localhost> | 2003-06-29 00:20:00 +0800 |
commit | 78df46c6a5f301ed1edcd6ea048d9b523938fc6e (patch) | |
tree | e521429188462e4446c632b5bd4b6f333e589995 /libical/TODO | |
parent | 5a8e20476b93515b8e69f7e1c8f659ab3dc55a8f (diff) | |
download | gsoc2013-evolution-78df46c6a5f301ed1edcd6ea048d9b523938fc6e.tar gsoc2013-evolution-78df46c6a5f301ed1edcd6ea048d9b523938fc6e.tar.gz gsoc2013-evolution-78df46c6a5f301ed1edcd6ea048d9b523938fc6e.tar.bz2 gsoc2013-evolution-78df46c6a5f301ed1edcd6ea048d9b523938fc6e.tar.lz gsoc2013-evolution-78df46c6a5f301ed1edcd6ea048d9b523938fc6e.tar.xz gsoc2013-evolution-78df46c6a5f301ed1edcd6ea048d9b523938fc6e.tar.zst gsoc2013-evolution-78df46c6a5f301ed1edcd6ea048d9b523938fc6e.zip |
This commit was manufactured by cvs2svn to create tagGNOME_VFS_2_5_1
'GNOME_VFS_2_5_1'.
svn path=/tags/GNOME_VFS_2_5_1/; revision=21653
Diffstat (limited to 'libical/TODO')
-rw-r--r-- | libical/TODO | 39 |
1 files changed, 0 insertions, 39 deletions
diff --git a/libical/TODO b/libical/TODO deleted file mode 100644 index eb52fb7a25..0000000000 --- a/libical/TODO +++ /dev/null @@ -1,39 +0,0 @@ - -TODOs for libical-0.16 ---------------------- - -libical treats properties with multiple values incorrecty -- it always -seperates multiple values into multiple properties. This is not -acceptable for CATEGORIES and RESOURCES. - -Some TEXT valued properties, like METHOD, have a limited set of valid -values. The code should check that the values of these properites are -valid. ( Although METHOD now uses enums, and is not really TEXT valued ) - -Finish implementing values - ATTACH/BINARY - content_type - language - -Check for buffer overflow on external input. - -Error Handling - - Dates and times: the parser will accept many illegal date time - values - -RECUR values ignore integers in BYDAY clauses, ie 'FREQ=MONTHLY;BYDAY=-1SU' - -Restrictions code does not catch lack of DTEND or DURATION - -For some value types, if there illegal characters in the value ( like -4.56 in an integer value), the parser will output the characters to -stdout. - -Check all uses of strcpy and sprinf for buffer overflows - -Make the mime parsing code in sspm grow the list of parts as needed, -rather than having a hard limit. - -in sspm.c, and unrecognized content-transfer-encoding values must -force a content type of application/octet-stream. |