Reviews run for a minimum of one week. The outcome of the review is decided on this date. This is the last day to make comments or ask questions about this review.
LaTeX is a typesetting system that is widely used by the science community for document preparation and publications. Eclipse TeXlipse is a plugin to enable Eclipse support for LaTeX projects. TeXlipse was first introduced around 2005, but support has dwindled since then. Although TeXlipse is still available via the marketplace and from SourceForge, the last release was in 2011 and there is no longer any active development or bug fixing. With the creation of the Science TLP, now is a great opportunity to reconstitute TeXlipse as an Eclipse project, and to create a community that will continue to maintain and even enhance the plugin.
The Eclipse TeXlipse project provides an Eclipse extension to support LaTeX projects, so that document preparation can be incorporated into the normal Eclipse development activities.
Outside the scope of the project:
- LaTeX tools and environments
- PDF viewers
LaTeX is a typesetting system that is widely used by the science community for document preparation and publications. The TeXlipse project provides an Eclipse extension to support LaTex projects, so that document preparation can be incorporated into the normal Eclipse development activities. General LaTeX users will also find the advanced editing and automatic document generation features of TeXclipse provide a compelling alternative to other LaTeX environments. TeXclipse supports the following features:
- Syntax/semantic editing of LaTeX documents
- Code folding
- Error annotations
- Content assist
- Line wrapping
- Table editor
- BibTeX editing support
- F3 navigation
- File and document outline
- Build support (document typesetting)
- Spell checking
- Menu support for common LaTeX symbols
- BibTeX and BibLaTeX support
- Integration of PDF viewers
- Bibsonomy integration
Apart from providing support for a tool that is widely used by the science community, this is also a great opportunity to reinvigorate the project. By taking advantage of Eclipse's capabilities, it is possible that TeXclipse could become competitive with other open source LaTeX environments. For science, this could help create a motivating factor for developers to choose Eclipse as their preferred development environment.
Other Science WG projects may be interested to integrate TeXclipse features and services in scientific workbenches and workflows.
The initial contribution comprises a single plugin containing source code and documentation. The plugin provides a LaTeX parser and model, editor, and properties pages. It also includes a builder to support creating LaTeX documents from source, as well as menu integration. There are also wizards for project and file creation, template support, integration with spell checkers, and support for external document viewers. The documentation component provides user documentation and templates.
The copyright appears to be held by the "TeXlapse Team". A Google search turns up a reference to "TeXlapse-team, SoberIT lab of the Helsinki University of Technology, TeXlipse users, Antti Pirinen, Boris von Loesch, Esa Seuranen, Jani Laitinen, Kimmo Karlsson, Laura Takkinen, Oskar Ojala, Taavi Hupponen, Tor Arne Vestbø".
Eclipse TeXlipse is an existing SourceForge project that was originally developed at the Helsinki University of Technology. It is already EPL licensed so that does not present an issue, however it may be difficult to establish the provenance of the code given its age. The plugin also depends on Jazzy for spell checking which is LGPLv2 licensed. This support could be a works-with dependency or could be dropped altogether for the initial contribution.
- An initial contribution will be made immediately.
- Integration with CI by end Q4 2016
- Initial release to coincide with Oxygen
Other Science WG projects (e.g. Triquetrum) are interested to take advantage of LaTeX typesetting for document generation services. To that end the TeXlipse codebase must be refactored and corresponding service APIs and implementations must be added.