Allow pdf+latex export to make use of textext latex-sourcecode
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
In Progress
|
Wishlist
|
Håkon Marthinsen |
Bug Description
The textext inkscape extension makes it possible to create 'latex' objects, which appear as rendered paths, but also possess the original LaTeX source metadata (which can be re-edited). It would be beneficial, when this extension is used, for Inkscape's pdf+latex export option to be smart about the metadata stored in these textext objects, and only place the source in the text overlay file (instead of the textext-rendered SVG graphics). Perhaps better would be to provide an additional switch/option which allows one to choose whether or not the textext sourcecode gets used in the pdf+latex output overlay file.
This offers two advantages: (1) the LaTeX is rendered on the canvas, so you see what the end-product really looks like, and (2) it allows "Export bitmap" to end up generating something that is visually the same as "export pdf+latex".
Currently, in order to create "x-squared" in the exported pdf+latex file, one needs to use an SVG text object containing $x^2$. This LaTeX code renders correctly with pdf+latex export, but remains unrendered if you export to a bitmap or print the SVG.
'Tex Text' Inkscape extension:
<http://
tags: | added: exporting latex |
Changed in inkscape: | |
importance: | Undecided → Wishlist |
description: | updated |
Do you know if 'Tex Text' is still actively developed or maintained? (It's latest stable version (0.4.4) was based on Inkscape 0.46, and as far as I know (not using it myself), it doesn't work out-of-the-box with newer Python and/or Inkscape versions. The development repository hasn't seen recent activity either).