1 | Data formats: |
1 | Data formats: |
2 | * Understand the password section |
2 | * Understand the password section |
3 | * Understand and document other file types (Data, Sheet, Agenda, etc) |
3 | * Understand and document 10000050 file types (Agenda, Data, etc) |
4 | |
4 | |
5 | Parser: |
5 | Parser: |
6 | * Incorporate the replacement section. Stubs are already in place. |
6 | * Incorporate the replacement section. Stubs are already in place. |
7 | * Add additional file types. |
7 | * Check and/or add image parsing for not 2-bits greyscale. |
8 | * Add included objects |
8 | * Complete Sheet |
|
|
9 | * Add more file formats |
9 | |
10 | |
10 | Psiconv Generators: |
11 | Generator: |
|
|
12 | * Add audio file support. |
|
|
13 | * Add image RLE support |
|
|
14 | * Check image file generation works for other things than 2 bits greyscale |
|
|
15 | * Add image 4-bit and 8-bit color palettes |
|
|
16 | * Add more file formats |
|
|
17 | |
|
|
18 | Psiconv program: |
11 | * HTML: Verify generated code, to see whether it is HTML-3.2 compatible |
19 | * HTML: Verify generated code, to see whether it is HTML-3.2 compatible |
12 | * HTML4: Fallback on normal HTML for TextEd files might be replaced with |
20 | * HTML4: Fallback on normal HTML for TextEd files might be replaced with |
13 | true code. But is it worth it? |
21 | true code. But is it worth it? |
14 | * Add other targets (RTF would be very nice) |
22 | * RTF: Make it usable. Not nearly finished at the moment. Dead project. |
|
|
23 | * IMAGE: support for special things like clipping is still lacking at the |
|
|
24 | generator side. |
15 | |
25 | |
16 | General: |
26 | General: |
17 | * Out-of-memory segfaults (malloc fails are not caught). Better handling? |
|
|
18 | * Make psiconv_debug and friends variables, that can be changed to |
|
|
19 | catch those errors and handle them in an application-specfic way. |
|
|
20 | * Many common values are returned as int. Perhaps change this to long, |
27 | * Many common values are returned as int. Perhaps change this to long, |
21 | for better behaviour on very large files on some architectures? |
28 | for better behaviour on very large files on some architectures? |
22 | * I suspect there are still some memory leaks. |
|
|
23 | * Use libaudiofile for audio conversions? |
29 | * Use libaudiofile for audio conversions? |
24 | * Add generation of audio files. |
30 | * Go to Unicode for all stored strings. This will be somewhat hard, maybe. |
|
|
31 | or maybe not, as most is contained in a few routines. |