summaryrefslogtreecommitdiffstats
path: root/libkcal/libical/TODO
diff options
context:
space:
mode:
authortoma <toma@283d02a7-25f6-0310-bc7c-ecb5cbfe19da>2009-11-25 17:56:58 +0000
committertoma <toma@283d02a7-25f6-0310-bc7c-ecb5cbfe19da>2009-11-25 17:56:58 +0000
commit460c52653ab0dcca6f19a4f492ed2c5e4e963ab0 (patch)
tree67208f7c145782a7e90b123b982ca78d88cc2c87 /libkcal/libical/TODO
downloadtdepim-460c52653ab0dcca6f19a4f492ed2c5e4e963ab0.tar.gz
tdepim-460c52653ab0dcca6f19a4f492ed2c5e4e963ab0.zip
Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features.
BUG:215923 git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/kdepim@1054174 283d02a7-25f6-0310-bc7c-ecb5cbfe19da
Diffstat (limited to 'libkcal/libical/TODO')
-rw-r--r--libkcal/libical/TODO39
1 files changed, 39 insertions, 0 deletions
diff --git a/libkcal/libical/TODO b/libkcal/libical/TODO
new file mode 100644
index 000000000..f707c2a52
--- /dev/null
+++ b/libkcal/libical/TODO
@@ -0,0 +1,39 @@
+
+TODOs for libical
+-----------------
+
+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.