PDF import options always default to 'Poppler/Cairo import' (rev >= 14170)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
Fix Released
|
Low
|
jazzynico |
Bug Description
After the changes in Inkscape 0.91+devel rev 14170 (see also bug #1483701), PDF import options always default to import via poppler ("Poppler/Cairo import"). The last used setting is not remembered (neither in the current session, nor across sessions).
This is an unexpected change compared to current stable Inkscape 0.91 where the default is Inkscape's internal import (the user's choice is not remembered either): Apart from other differences in the resulting SVG structure, the major one is with text: import via 'Poppler/Cairo' produces outlined text ("converted to paths", reusing the glyphs of fonts embedded in the PDF file); implemented in SVG via symbols (per glyph) instanced as clones on-canvas (same as with the command line tool 'pdftocairo' from poppler). Without further changes, text from PDF files imported with default options will not editable as text in the next release (0.92).
Independent of whether or not the default import method is switched to external libraries (which might help resolving the build conflicts due to Inkscape requiring private poppler header files if Inkscape's internal import is dropped altogether), the last used choice of the user should be remembered (across sessions).
In case the setting ('Poppler/Cairo' or 'Internal') is restored from the preferences, the default used for command line operations, for example
$ inkscape -f file.pdf -l file.svg
likely needs to be reconsidered as well (currently, this PDF->SVG conversion via command line interface always uses Inkscape's internal import (no choice possible)).
Related branches
description: | updated |
Changed in inkscape: | |
importance: | Undecided → Low |
Changed in inkscape: | |
status: | Fix Committed → Fix Released |
Confirmed on Xubuntu 15.04, Inkscape trunk rev. 14419.
Restoring the original default is an easy fix, but the PDF import code has a specific preference handling (Inkscape: :XML::Node instead of Inkscape: :Preferences) that seems to be broken.