<\body> There are many things that we would like to integrate in . On |http://savannah.gnu.org/projects/texmacs/>, we maintain awish list with by users and other detailed wanted features. Here follows an incomplete list of more general directions for future development, as on september 2, 2011. The typesetter should be reorganized and improved as follows: <\itemize> Decouple the style-sheet language from the actual typesetter. Better support for agglomerated documents (from physically different documents). More types of dynamic objects, like animations, help balloons, Better line-breaking of large formulas. Although cursor movement, selections, etc. have already been implemented, some other standard editing facilities have not yet been completed. Let us mention a few of these: <\itemize> Better search and replace tool for structured texts, formulas, certain environments etc. and regular expressions. Mathematical facilities: simplification of a selected region, substitutions of formulas in other formulas, etc. Version control. Data compression and protection. Grammar checkers and automatic translation programs. Does someone know where to find detailed free dictionaries and stuff like that? Incorporation of a free speech recognition program. There is a constant need for good converters from and to other data formats: <\itemize> Of course, / cannot really be considered as a format (it is really a language with an ill defined grammar). Nevertheless it is important to have good heuristic converters in both directions. We still would appreciate help in this direction, in particular in order to support standard documents styles of various journals. is also compatible with , but some things such as forms have not been implemented yet. The importation of tables could also be further improved and it would be nice if the importer could support cascaded style sheets. It would be nice to have converters for the document formats used by , , and the internal formats used by important publishers such as . We would appreciate help for writing a converter from to the format, which is the standard documentation format for the GNU project. We would like to incorporate a ``universal spreadsheet'' facility into . The idea is that all dependencies between the cells in the sheet are analyzed by , but all actual computations are delegated to an extern system of your choice, like one of the currently supported computer algebra systems. Also, the data of the spreadsheet will not necessarily be formatted in a rectangular table; one can also imagine dependencies between nodes of a tree, elements of a graph, or anything else. We have started to include a facility for drawing technical pictures, but the responsable developer (Henri ) is currently no longer part of the team. It would be nice to rewrite parts of the tool and extend it further so as to allow for the definition of graphical macros. This would allow users to define new geometrical constructions. It would for instance be possible to write a style file for drawing electronic circuits or chemical components with a nice icon bar for selecting circuits or components, just as you select lines and circles in usual pictures. It would be nice to have a better integration of with the web. As a first step, we need a clean internal plug-in for or with support for cookies, security, etc. At a second stage, the Html converters should be improved to take advantage of this. After that, we may think about things like collaborative authoring via the web, integration with preprint servers, Another interesting thing would be to incorporate tools for live conferencing inside . We actually expect this to be quite easy and this would open a different road towards collaborative authoring, instant messenging, The following improvements should still be made in order to link to computer algebra systems: <\itemize> Improving the layout of computer algebra sessions. Add extra features to increase the interoperability between and computer algebra systems and to give additional control over the layout of big output. More semantics for the objects being communicated. This may either be high level information (like HTML 4.0 mathematical markup or Openmath) or low level information (including information about the representation of data), depending on the required speed. Further possibilities for evolution concern syntax highlighting, debugging facilities and so on. <\initial> <\collection>