diff options
Diffstat (limited to 'etc/TODO')
| -rw-r--r-- | etc/TODO | 48 |
1 files changed, 38 insertions, 10 deletions
@@ -479,15 +479,6 @@ One way of doing this is to start with fx's dynamic loading, and use it to implement things like auto-loaded buffer parsers and database access in cases which need more than Lisp. -** Fix portable dumping so that you can redump without using -batch - -*** Redumps and native compiler "preloaded" sub-folder. -In order to depose new .eln files being compiled into the "preloaded" -sub-folder the native compiler needs to know in advance if this file -will be preloaded or not. As .eln files are not moved afterwards -subsequent redumps might refer to .eln file out of the "preloaded" -sub-folder. - ** Imenu could be extended into a file-structure browsing mechanism This could use code like that of customize-groups. @@ -904,6 +895,30 @@ It would make it easy to add (and remove) mappings like * Things to be done for specific packages or features +** Native compiler improvements + +*** Performance + +**** Intra compilation unit call optimization + +We could have a mechanism similar to what we use for optimizing calls +to primitive functions. IE using a link table for each compilation +unit (CU) such that calls from functions in a CU targeting functions +in the same CU don't have to go through funcall. If one of these +functions is redefined, a trampoline is compiled and installed to +restore the redirection through funcall. + +*** Features to be improved or missing + +**** Fix portable dumping so that you can redump without using -batch + +***** Redumps and native compiler "preloaded" sub-folder. +In order to depose new .eln files being compiled into the "preloaded" +sub-folder the native compiler needs to know in advance if this file +will be preloaded or not. As .eln files are not moved afterwards +subsequent redumps might refer to .eln file out of the "preloaded" +sub-folder. + ** NeXTstep port *** Missing features @@ -1245,7 +1260,7 @@ Necessary for indirect buffers to work? *** Locating schemas -**** Should 'rng-validate-mode' allow to specify a schema? +**** Should 'rng-validate-mode' allow specifying a schema? Give the user an opportunity to specify a schema if there is currently none? Or should it at least give a hint to the user how to specify a non-vacuous schema? @@ -1747,6 +1762,19 @@ The former is based on the GVFS archive backend, which makes it available on GNU/Linux only. That implementation has further drawbacks like it doesn't support to write into archives. +** Provide support for CFF outlines in the Android port. + +The file src/sfnt.c supplies the font backend for the Android port. +It is presently a self contained TrueType scaler, implementing both a +grayscale outline generator and an instruction code interpreter. + +Support for CFF (Compact Font Format) outlines will facilitate +utilizing fonts distributed as ".otf" files, a category that currently +encompasses all CJK and some Middle Eastern and Indic fonts +distributed with Android, obviating the present requirement for users +of such scripts to actively install TrueType versions of fonts +otherwise bundled with the system. + * Other known bugs ** 'make-frame' forgets unhandled parameters, at least for X11 frames |