10:59 p.m.
Hello All,
as the problem is still there I would propose following intermediate solution:
currently in the codebasis there is also an pdf import via
poppler-cairo. This one is disabled.
I would like to enable this as an additional pdf import possibility.
We have to decide later when it comes to the release which one to
integrate into the release.
so we can test in parallel the two options.
we have a big tester basis (compared to separate launchpad branch)
we get the possibility to switch to an tested poppler-internals
independent solution (while using poppler)
I there is no big NONO I will go forward and enable this within the next days.
attached the patch that is needed for this (tested on windows, should
work on Linux)
regards,
Adib.
8:57 a.m.
New subject: pdf import again: poppler native vs. poppler cairo
I went a step forward and copied the preview dialogue from the poppler
import. So this dialogue is now available.
However the only functionality that is in use is the page selection
and page preview.
I do not know how to tune the parameters for pdf-cairo conversion.
i.e. when importing text all letters becomes single path elements. Not so nice.
Any suggestions.?
Adib.
--
On Thu, Jan 20, 2011 at 2:59 PM, the Adib <theadib@...1439...> wrote:
Hello All,
as the problem is still there I would propose following intermediate solution:
currently in the codebasis there is also an pdf import via
poppler-cairo. This one is disabled.
I would like to enable this as an additional pdf import possibility.
We have to decide later when it comes to the release which one to
integrate into the release.
so we can test in parallel the two options.
we have a big tester basis (compared to separate launchpad branch)
we get the possibility to switch to an tested poppler-internals
independent solution (while using poppler)
I there is no big NONO I will go forward and enable this within the next days.
attached the patch that is needed for this (tested on windows, should
work on Linux)
regards,
Adib.
2:39 a.m.
Can't compile anymore under Windows XP SP3 for this error:
Make error line 300: problem compiling: In file included from
src/extension/internal/pdf-input-cairo.cpp:21:
src/extension/internal/pdf-input-cairo.h:37:21: error: poppler.h: No such
file or directory
Regards.
Luca
--
View this message in context:
http://old.nabble.com/pdf-import-again%3A-poppler-native-vs.-poppler-cair...
Sent from the Inkscape - Dev mailing list archive at Nabble.com.
8:44 a.m.
New subject: pdf import again: poppler native vs. poppler cairo
THx for the message, fixed in bzr. Adib. (my btool still running...)
On Tue, Feb 15, 2011 at 6:39 PM, LucaDC <dicappello@...2144...> wrote:
Can't compile anymore under Windows XP SP3 for this error:
Make error line 300: problem compiling: In file included from
src/extension/internal/pdf-input-cairo.cpp:21:
src/extension/internal/pdf-input-cairo.h:37:21: error: poppler.h: No such
file or directory
Regards.
Luca
--
View this message in context:
http://old.nabble.com/pdf-import-again%3A-poppler-native-vs.-poppler-cair...
Sent from the Inkscape - Dev mailing list archive at Nabble.com.
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
4:59 p.m.
the Adib wrote:
THx for the message, fixed in bzr. Adib. (my btool still running...)
Everything fine now. Thanks.
Luca
--
View this message in context:
http://old.nabble.com/pdf-import-again%3A-poppler-native-vs.-poppler-cair...
Sent from the Inkscape - Dev mailing list archive at Nabble.com.
10:43 p.m.
On 15/2/11 00:57, the Adib wrote:
I went a step forward and copied the preview dialogue from the
poppler
import. So this dialogue is now available.
However the only functionality that is in use is the page selection
and page preview.
Tested with Inkscape 0.48+devel r10053 and r10067 on OS X 10.5.8 (i386):
the preview fails (empty) for PDF documents with just one page:
** Message: Attempting to open using PdfInputCairo
(inkscape:91466): Poppler-CRITICAL **: PopplerPage*
poppler_document_get_page(PopplerDocument*, int): assertion `0 <= index &&
index < poppler_document_get_n_pages (document)' failed
(inkscape:91466): Poppler-CRITICAL **: void poppler_page_get_size(PopplerPage*, double*,
double*): assertion `POPPLER_IS_PAGE (page)' failed
(inkscape:91466): GdkPixbuf-CRITICAL **: gdk_pixbuf_new: assertion `width > 0'
failed
On 15/2/11 00:57, the Adib wrote:
I do not know how to tune the parameters for pdf-cairo conversion.
i.e. when importing text all letters becomes single path elements. Not so nice.
<http://lists.freedesktop.org/archives/cairo/2011-February/021777.html> ?
~suv
9:01 p.m.
On 15/02/2011 00:57, the Adib wrote:
I went a step forward and copied the preview dialogue from the
poppler
import. So this dialogue is now available.
However the only functionality that is in use is the page selection
and page preview.
As mentioned earlier, the current dialog fails to show a preview for
single-page PDF documents.
I do not know how to tune the parameters for pdf-cairo conversion.
i.e. when importing text all letters becomes single path elements. Not so nice.
Text actually is outlined based on the embedded and subset fonts in the
PDF file which is a very useful feature for fonts not installed on the
current system (if the user does not intend to edit text as text).
The fonts remain kind of "embedded and subset" in the SVG file as well
(but not as SVG fonts which Inkscape couldn't render anyway): the
original paths for a glyph is stored as <symbol> in the <defs> section
and referenced as clone in the drawing.
Note: outlined texts (import text as path) is a frequently requested
feature direly lacking with Inkscape's default PDF import.
Apart from the text issues (btw - gradients and gradient meshes are also
imported differently than with Inkscape's own PDF import routines, often
with (visually) more precise results compared to how the PDF file
renders in a PDF viewer):
Could someone familiar with poppler and cairo please review the findings
reported in:
Bug #1017123 “'Adobe PDF via poppler-cairo' (trunk): imprecise and
incorrect stroke widths”
<https://bugs.launchpad.net/inkscape/+bug/1017123>
3992
days inactive
4513
days old
inkscape-devel@lists.inkscape.org
6 comments
3 participants
participants (3)
-
LucaDC -
the Adib -
~suv