Should be fixed now. Empty symbols (which pdf2svg creates, perhaps for a space?) returned an invalid bounding box. I also changed the default styling in the Symbol dialog preview. If there is no styling in the symbol and no default styling in the document, symbols will be displayed with a gray fill and dark-gray stroke. Previously the characters from pdf2svg were invisible.
Tav
On Sat, 2012-10-13 at 12:41 +0200, ~suv wrote:
On 11/10/2012 22:12, Tavmjong Bah wrote:
I've checked into trunk a Symbols dialog. A description of the dialog can be found on a Wiki page at:
http://wiki.inkscape.org/wiki/index.php/SymbolsDialog
There are still some issues that need to be resolved. They are listed in Wiki page.
AFAICT the 'Symbols' dialog loads and displays any kind of <symbol> objects found in the <defs> section of the current document.
SVG files created from PDF files via poppler-cairo (inkscape's own 'Adobe PDF via poppler-cairo' import extension, or e.g. with pdftocairo (from poppler), with pdf2svg or via printing to file (SVG) from Evince) have any text from the original PDF outlined, and the paths for the characters are stored as (AFAICT regular SVG) symbols inside a group in the <defs> section. Inkscape (stable and trunk) renders such files fine.
Opening the 'Symbols' dialog for such a document (to see the symbol preivews of the embedded outlined characters) however crashes Inkscape (backtrace from OS X attached, same crash happens on Ubuntu 12.10).
V