1 | Data formats: |
1 | Data formats: |
2 | * Understand the password section |
2 | * Understand the password section |
3 | * Understand and document included objects |
3 | * Document included objects |
4 | * Understand and document other file types (Data, Sheet, Agenda, etc) |
4 | * Understand and document other file types (Data, Sheet, Agenda, etc) |
5 | |
5 | |
6 | Parser: |
6 | Parser: |
7 | * Incorporate the replacement section. Stubs are already in place. |
7 | * Incorporate the replacement section. Stubs are already in place. |
8 | * Add additional file types. |
8 | * Add additional file types. |
|
|
9 | * Add included objects |
9 | |
10 | |
10 | Generators: |
11 | Generators: |
11 | * HTML: Verify generated code, to see whether it is HTML-3.2 compatible |
12 | * 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 |
13 | * HTML4: Fallback on normal HTML for TextEd files might be replaced with |
13 | true code. But is it worth it? |
14 | true code. But is it worth it? |
14 | * Add other targets (RTF would be very nice) |
15 | * Add other targets (RTF would be very nice) |
15 | |
16 | |
16 | General: |
17 | General: |
17 | * Out-of-memory segfaults (malloc fails are not caught). Better handling? |
18 | * Out-of-memory segfaults (malloc fails are not caught). Better handling? |
|
|
19 | * Make psiconv_debug and friends variables, that can be changed to |
|
|
20 | catch those errors and handle them in an application-specfic way. |
18 | * Many common values are returned as int. Perhaps change this to long, |
21 | * Many common values are returned as int. Perhaps change this to long, |
19 | for better behaviour on very large files on some architectures? |
22 | for better behaviour on very large files on some architectures? |
20 | * It should be possible for users to catch parse errors with their own |
23 | * I suspect there are still some memory leaks. |
21 | routines. |
|
|