We are still using the internal Poppler API to import PDFs. This is
very bad, since the internal Poppler API is not stable, and will keep
breaking. (We already don't build with poppler > 0.12.1)
How about using the public Glib API to render to a Cairo SVG surface
instead? This is how pdf2svg works, and to be honest I had to use that
utility several times to augment Inkscape, because it handles text
much better. What are the advantages to using internal Poppler API
Chris Lilley wrote:
> On Saturday, January 16, 2010, 10:32:16 PM, knowone wrote:
> k> How can I save the file as PNG with the drop shadow intact?
> Make sure you are exporting as PNG. Do not 'Save As' Cairo PNG.
> (I came across this a couple of days ago, and the symptom was that blur filters were not being applied. Also, the pixel dimensions of the two methods differ, if the graphic bleeds over the edge of the 'page').
Can someone tell me why we have a non-vector format in the save as list?
One that seems redundant and apparently with less functionality than the
normal export. Is this for testing purposes?
Selector tool has a new mouse cursor (arrow with an open hand) for
when your mouse is over a selectable object, and another (arrow with
clinched hand) for when you're dragging an object. This improves
precision of selection and UI consistency (previously, the mouse
cursor over a selectable object was different across platforms, e.g.
hand icon on Linux or four-way arrow on Windows).
Inkscape. Draw Freely.
I just built the inkscape trunk from bzr and ran this script
bus = dbus.SessionBus()
inkdoc1 = bus.get_object('org.inkscape', '/org/inkscape/desktop_0')
doc1 = dbus.Interface(inkdoc1, dbus_interface="org.inkscape.document")
im = doc1.image(100 ,100, '/home/ktenney/Firefox_wallpaper.png')
Which worked on a dbus branch a while back.
Now it starts inkscape, but does not place the image
- was the dbus code merged?
- if so, how do I enable/use it?
- if not, where is dbus capable code?
The input devices settings (for extended input, e.g. tablet) have
changed some time ago to a different format. Now, I can set the stylus
device to Screen to have it pressure sensitive as expected, and it is
also stored as this in the preferences.xml, but on reload if forgets
My stylus device is called Stylus0, the eraser Eraser0. Setting the
eraser to screen mode, in the preferences.xml I see something like
but no such entry for stylus or Stylus0 exists and is created...
Is the number of times an spobject is cloned (svg "use") counted?
It would be a really great help in fixing a bug.
So what I'd like to have is: SPObject obj; obj->clone_count
or something similar.
As I am sitting on the train returning from LGM 2010, I thought I
would give you all a summary of the conference. There where many nice
talks and it was great to finally meet many Inkscapers who I only knew
by name. There were also very nice endorsements of Inkscape. The
Fedora design team made a big point of expressing how much they LOVE
Inkscape. Inkscape appeared all over the place at the conference, from
designing icons to designing fonts. I am sure I have forgotten
somethings as my memory needs a serious upgrade... so other Inkscape
attendees, don't hesitate to correct me.
Here is a summary of talks by Inkscapers about Inkscape or other
Jasper van de Gronde: Diffusion curves (gradients defined
by values specified along the defining paths).
Felipe Sanches (JucaBlues): GNU LibreDWG to read DWG files
Jakub Steiner: Icon Workflows with Inkscape.
Alexandre Prokoudine: Digital photography workflow on Linux
Andy Fitzsimons: Inkscape for everybody.
Elisa de Castro Guerra: Workshop for Inkscape beginners
(in French and English).
John Phillips: Aiki framework. As a side note, he used Inkscape
for his presentation, putting all his slides on one page and then
zooming in and out on individual ones.
Other Inkscapers present included Ivan Louette, Gemy Cedric, and
My only critique is that it would have been nice to have had a
demonstration of some of the new features of the upcoming Inkscape
The list of other interesting talks is long. You can look at the
website for a list of talks and the videos of all the talks should be
online soon if not already. Some of the crowd favorites were the talk
by the NodeBox2 group and the talk by Tom Lechner who showed a very
impressive demonstration of putting images on a sphere and then
During the talks and at informal gatherings, there was quite a bit
of discussion about what users need from Inkscape. Here is a list of
1. Hyphenation support in the text tool.
2. Faster loading/displaying fonts in the menu.
3. Command line interface without opening the GUI.
4. Trapping for commercial work.
5. Fixes for bugs #167809 (Linked offset performance issues)
and #270983 (Terrible performance node editing even in
outline mode). In general there is a desire for more SPEED!
6. Shortcuts in tooltips (especially for tools).
7. Don't muck up imported SVG, e.g. turning ellipses into
paths. This is important when planning to animate things.
Many people design with Inkscape and then use Scribus for preparing
files for commercial printing.
Members of the SVG working group were present which lead to a number
of useful discussions. They will hold a working group meeting tomorrow.
Here are a number of topics that were covered:
1. Support for multipage documents. The proposal for multipage
documents has been dropped from SVG 1.2 due to many negative comments.
The proposal was too complicated for simple uses and not sophisticated
enough for advance uses. If we push, a simplified version could be
added to SVG 2.0.
2. Support for patterns along paths. Coming out of the discussion
on Power Strokes lead by Johan Engelen, Doug Schepers of the SVG
standards group expressed a great interest in pursuing this as it
would allow some LPE like effects to be animated. Doug, in general,
would like to see greater ability to edit/animate SVG.
3. Support for diffusion curves.
4. SVG Fonts: Firefox and IE at the moment don't have any interest
in supporting, preferring to focus on WOFF implementation. It was
pointed out by several people that SVG Fonts are much more useful for
artistic purposes as one can imagine animating the glyphs or adding
special effects to them.
5. Increasing the bit depth for some of the filters to avoid
artifacts (e.g. the displacement filter or lighting filters). There is
a need to balance requirements for small devices (small memory) with
the need for large ones (smooth/accurate displays) but perhaps a
compromise could be made (I've suggested adding an optional second
byte to the bump maps).
6. Standardizing layers (Inkscape currently uses tagged groups
Other SVG news is that Adobe is again interested in supporting the
standard and that IE9 will support all of SVG except SVG fonts and
filters. Finally, the SVG working group really stressed the need for
community participation, especially from Inkscape. I have volunteered
to help represent Inkscape in the group. So let me know on this list
or off of any thing you want raised with the group. You can also join
the SVG mailing list (www-svg@...157...). Jasper is already a member and
I just joined.
One of the more interesting talks was about trying to develop Open
Source tools for fashion design. It seems that there is a need to
develop adjustable patterns for those who don't have the petite bodies
the industry designs towards. The industry just scales up the patterns
for bigger women, leading to poor fit. After hearing the talk, someone
has already created an Inkscape extension to help with the work. See:
Finally, several venues for LGM 2011 have been proposed. The
leading candidate seems to be Ho Chi Min City, Viet Nam. Montreal is
also a possibility. Felipe was encouraged to think about Brazil
PS. Thanks to Jasper for reading a draft of this summary and making many
> From: Krzysztof Kosiński [mailto:tweenk.pl@...400...]
> W dniu 30 maja 2010 14:33 użytkownik Preben Soeberg <prsodk@...400...>
> > Now at devlibs rev. 17, still having the same problem:
> > Make error line 452: <msgfmt> problem: po/fr.po:18690: keyword "msgctxt"
> > unknown
> > po/fr.po:18690:8: parse error
> > po/fr.po:18695: keyword "msgctxt" unknown
> > po/fr.po:18695:8: parse error
> > ...
> > I'm not near a computer for the next week or so.
> I think you have an obsolete version of gettext tools installed in
> your MinGW directory, or somewhere in your PATH before the devlibs
> bin/ directory. Make sure that the msgfmt.exe from devlibs is first in
> your PATH.
Thanks, that solved my problem.
I just managed to test it, before I leave for the train.
if i try to update the de.po with "msgmerge -Uv de.po inkscape.pot" on Windows, i get a different error message:
inkscape.pot:18745: Schlüsselwort »msgctxt« ist unbekannt
inkscape.pot:18745:8: parse error
Keyword »msgctxt« is unknown
So i get at least 104 Error messages.
Can someone fix this problem?
> De : Peter Moulder <Peter.Moulder@...2349...>
> À : Nicolas Dufour <nicoduf@...48...>
>> Another check-markup related issue: [it doesn't support msgctxt
> It's past my bedtime, so I haven't tested interesting cases
> yet, but try the attached patch.
Thanks for the patch. Unfortunately, it still doesn't work. But the error
message is different now:
fr.po: parse error; may be a bug in po/check-markup:
And the fuzzy lines are now correctly ignored.
Inkscape-devel mailing list
Mit freundlichem Gruß,