5 * Implement fribidi_wcwidth()?
7 * Port fribidi-main.c to new API.
11 Implementation issues:
13 * Add API to get and pass on TypeLink*, to not allocate bidi levels.
14 Something like that. Also the UTF-8 stuff from pango/mini-fribidi.
18 * Clean caprtl2utf8 to do arbitrary charset conversion?
20 * add --output-charset.
22 * Update README, etc...
24 * Mix __attr... with DLLIMPORT?
26 * Update all files headers/footers. For c/h files, lib/fribidi-mirroring.[ch]
27 is always the reference.
29 * In fribidi_main.c reorder after line break.
31 * Change fribidi-main cmd-line parameters: --mirror --no-mirror... change the
34 * Add an option to fribidi_main.c to assume two consecutive returns as
37 * Add more tests. For:
38 - Checking that not removing explicit marks in analyze is not changing the
40 - Tests with BN. Right now ^ is BN in CapRTL scheme.
43 * indent: support function attributes and _PARAMS like things. Also
44 FRIBIDI_BEGIN_DECLS, and LIKELY.
46 * Cleanup gen.tab/gen-*.c files.
48 * Override pkgincludedir and append interface version. Should we go the GNOME
51 * c2man: parse Author and Copyright from the whole file.
53 * Write texinfo documentation.
55 * Set up gnu.org web pages, and update the entry in Free Software Directory.
59 * Add FriBidiEnv functionality at compile time. Also, ifdef out the memory
60 cleanup stuff if asked to fail on memory allocation failure (xmalloc). When
61 this is done, FRIBIDI_GNUC_WARN_UNUSEDS can be turned off conditionally.
63 * Generate HTML and DVI documentation.
65 * Rewrite fribidi.spec.in
67 * Add make rules for lib/$(BUILT_SOURCES) to depend on gen.tab/ stuff?
69 * When called in interactive mode, fribidi cmd-line should greet, write
70 about copyrtight stuff, and shared-libs' version and Unicode version.
72 * Configure gen.tab/ with host=build to avoid cross-compiling table
75 * Replace test/run.tests with something better, Makefile foo, etc.
77 * Clean up README and NEWS, and check all files' headers. Write
78 gen.tab/README. Also add UniData license file.
80 From GNU Coding Standards:
82 * The distribution should contain a file named `README' which gives the name
83 of the package, and a general description of what it does. It is also good
84 to explain the purpose of each of the first-level subdirectories in the
85 package, if there are any. The `README' file should either state the version
86 number of the package, or refer to where in the package it can be found.
88 * Add ^L to all sources.