only includes the used glyphs instead of the full character-set).Ī) The feature request to convert text to paths on import is known and tracked inīug #295564 “import PDF text also as path”ī) The feature request to support embedded fonts of imported PDF/PS/EPS files (converted to SVG fonts) is known, too, e.g.īug #293327 “Fonts not displayed correctly”īug #221405 “PDF import doesn't handle fonts” etc.īug #170963 “Support for SVG fonts (rendering, embedding.)” allow to edit the text content, within limits if the embedded fonts are subsetted (i.e. To me it is unclear what your blueprint is about: vectorized text (converted to path) is no longer editable as text (only as paths), whereas support for embedded fonts does (or should) retain an editability of text as text (i.e.
Inkscape currently does not support importing and rendering of embedded fonts (in SVG and other vector file formats) - it tries to find an installed font matching the font name stored on the PDF file, else falls back to generic font families. Embedded fonts per definition make a document independent from the installed fonts on the system a document is viewed. in my understanding the text is not vectorized into path outlines. Aren't you confusing the ability to use embedded fonts in PDF/PS/EPS files for rendering text content with converting text to paths (outlines)? Yes, Evince (like other SVG viewers) does support embedded fonts: the text can still be copied as text i.e. I found that Evince can vectorize PDF embedded fonts even if they aren't installed (one must do it through print to file and chose SVG output) Thus the code already exists !
0 kommentar(er)
