| 1 |
|
| 2 |
|
| 3 |
Put the contents of the README into the documentation. |
| 4 |
First, we need to distribute a pre-compiled documentation |
| 5 |
|
| 6 |
xml module: |
| 7 |
============ |
| 8 |
|
| 9 |
* DOM requires Utf16-encoding for strings. |
| 10 |
Can we make all the packages generic, so that the user can decide whether |
| 11 |
to use Utf16 or Utf8 ? |
| 12 |
|
| 13 |
* Unicode: Add conversion to Wide_Char and Wide_String |
| 14 |
|
| 15 |
* Support for xml:* attributes (space, ...) |
| 16 |
Note that xml:space means that we must use the Ignorable_Whitespace callback |
| 17 |
in SAX. |
| 18 |
|
| 19 |
* Should Encoding_Scheme include support for From_Utf32 and To_Utf32 |
| 20 |
|
| 21 |
* Unicode: http://www.unicode.org/unicode/standard/versions/Unicode3.0.html |
| 22 |
|
| 23 |
* DOM: Finish implementation for the few remaining cases |
| 24 |
|
| 25 |
* SAX: Should have a feature to specify whether entity refs in attribute |
| 26 |
values should be expanded or not |
| 27 |
|
| 28 |
* Parser: Checking of self-contained entities could be cleaner (ie done at |
| 29 |
a more general level). For instance, directly at the end of Next_Token, |
| 30 |
but we must exclude Text from the tests. |
| 31 |
|
| 32 |
* Can we implement the lexical parser as a state machine (Next_Char called |
| 33 |
at a single place). This might make it shorter (but probably not more |
| 34 |
efficient) |
| 35 |
|
| 36 |
Release 0.7 |
| 37 |
=========== |
| 38 |
* Parse_Element_Model_From_Entity should use Next_Token (for entitites) |
| 39 |
* File_Input shouldn't store the whole file in memory (have a buffer of 64k |
| 40 |
instead). |
| 41 |
* No need to return Id in Next_Token, should be stored directly in |
| 42 |
Parser.Id. This would be more efficient. This allows for a simplification |
| 43 |
in Parse_Element_Model. |
| 44 |
* For efficiency, Sax.Attributes should be an array |
| 45 |
* We must normalize PublicID (see 4.2.2) |
| 46 |
* Group all DTD-related field into a separate record (Entities, Default_Atts) |