| 
 | 
1 | NEXT RELEASE (0.9.2): | 
 | 
 | 
2 |   * Split Debian stuff from archive | 
 | 
 | 
3 |   | 
| 1 | Data formats: | 
4 | Data formats: | 
| 2 | * Understand the password section | 
5 | * Understand the password section | 
| 3 | * Understand and document 10000050 file types (Agenda, Data, etc) | 
6 | * Understand and document 10000050 file types (Agenda, Data, etc) | 
| 4 |  | 
7 |  | 
| 5 | Parser: | 
8 | Parser: | 
| … |  | 
… |  | 
| 13 | * Check image file generation works for other things than 2 bits greyscale | 
16 | * Check image file generation works for other things than 2 bits greyscale | 
| 14 | * Add Sheet | 
17 | * Add Sheet | 
| 15 | * Add more file formats | 
18 | * Add more file formats | 
| 16 |  | 
19 |  | 
| 17 | Psiconv program: | 
20 | Psiconv program: | 
| 18 | * HTML: Verify generated code, to see whether it is HTML-3.2 compatible | 
21 | * HTML: Verify generated code, to see whether it is HTML-4.01 compatible | 
| 19 | * HTML4: Fallback on normal HTML for TextEd files might be replaced with | 
22 | * XHTML: Verify generated code, to see whether it is XHTML compatible | 
| 20 |          true code. But is it worth it? | 
23 | * HTML,XHTML: Add support for images | 
| 21 | * RTF: Make it usable. Not nearly finished at the moment. Dead project. | 
24 | * RTF: Make it usable. Not nearly finished at the moment. Dead project. | 
 | 
 | 
25 | * LATEX: re-enable or delete. Dead project. | 
| 22 | * IMAGE: support for special things like clipping is still lacking at the | 
26 | * IMAGE: support for special things like clipping is still lacking at the | 
| 23 |          generator side.  | 
27 |          generator side.  | 
| 24 |  | 
28 |  | 
| 25 | Config files: | 
29 | Config files: | 
| 26 | * Add hex parsing | 
30 | * Add hex parsing | 
| 27 |  | 
31 |  | 
| 28 | General: | 
32 | General: | 
| 29 | * Many common values are returned as int. Perhaps change this to long, | 
33 | * Many common values are returned as int. Perhaps change this to long, | 
| 30 |   for better behaviour on very large files on some architectures? | 
34 |   for better behaviour on very large files on some architectures? | 
| 31 | * Use libaudiofile for audio conversions? | 
35 | * Use libaudiofile for audio conversions? | 
| 32 | * Go to Unicode for all stored strings. This will be somewhat hard, maybe. | 
36 | * Look at portability (headers) | 
| 33 |   Or maybe not, as most is contained in a few routines. | 
37 | * Add more comments in data.h |