| 1 | Data formats: |
1 | Data formats: |
| 2 | * Understand the password section |
2 | * Understand the password section |
| 3 | * Understand and document included objects |
|
|
| 4 | * Understand and document other file types (Data, Sheet, Agenda, etc) |
3 | * Understand and document 10000050 file types (Agenda, Data, etc) |
| 5 | |
4 | |
| 6 | Parser: |
5 | Parser: |
| 7 | * Incorporate the replacement section. Stubs are already in place. |
6 | * Incorporate the replacement section. Stubs are already in place. |
| 8 | * Add additional file types. |
7 | * Check image parsing works for other things than 2-bits greyscale. |
|
|
8 | * Complete Sheet |
|
|
9 | * Add more file formats |
| 9 | |
10 | |
| 10 | Generators: |
11 | Generator: |
|
|
12 | * Add audio file support. |
|
|
13 | * Check image file generation works for other things than 2 bits greyscale |
|
|
14 | * Add Sheet |
|
|
15 | * Add more file formats |
|
|
16 | |
|
|
17 | Psiconv program: |
| 11 | * HTML: Verify generated code, to see whether it is HTML-3.2 compatible |
18 | * HTML: Verify generated code, to see whether it is HTML-4.01 compatible |
| 12 | * HTML4: Fallback on normal HTML for TextEd files might be replaced with |
19 | * XHTML: Verify generated code, to see whether it is XHTML compatible |
| 13 | true code. But is it worth it? |
20 | * HTML,XHTML: Add support for images |
| 14 | * Add other targets (RTF would be very nice) |
21 | * RTF: Make it usable. Not nearly finished at the moment. Dead project. |
|
|
22 | * LATEX: re-enable or delete. Dead project. |
|
|
23 | * IMAGE: support for special things like clipping is still lacking at the |
|
|
24 | generator side. |
|
|
25 | |
|
|
26 | Config files: |
|
|
27 | * Add hex parsing |
| 15 | |
28 | |
| 16 | General: |
29 | General: |
| 17 | * Out-of-memory segfaults (malloc fails are not caught). Better handling? |
|
|
| 18 | * Many common values are returned as int. Perhaps change this to long, |
30 | * Many common values are returned as int. Perhaps change this to long, |
| 19 | for better behaviour on very large files on some architectures? |
31 | for better behaviour on very large files on some architectures? |
| 20 | * It should be possible for users to catch parse errors with their own |
32 | * Use libaudiofile for audio conversions? |
| 21 | routines. |
33 | * Look at portability (headers) |
|
|
34 | * Add more comments in data.h |
Parent Directory
| 
Revision Log
| 
Patch