- Inkscape Devel - Inkscape Mailman

0.48.3.1 and 0.48.4 on Ubuntu 12.04 - Node Sculpting Problem
by clarkk 19 May '14

19 May '14

I hope someone can offer me some help. Please let me know if I haven't reported this in the right way or have omitted any info. Thanks in advance! My problem is that I am unable to sculpt text when using the node tool, as described at http://wiki.inkscape.org/wiki/index.php/Release_notes/0.44#Node_sculpting, and demonstrated in this video tutorial, http://youtu.be/_qqTAjBaeJ0?t=8m20s. These are the steps I take: 1) Create text with text tool 2) Node Tool 3) Select Text 4) Convert Object to Path 5) Select each path (each letter) - Note: the tutorial above shows that a selection box may be used to select all the paths at once, but this doesn't work for me. Hence, to work around this, I've selected each letter while the Shift key is held. Reasons for this would be welcome also! 6) CTRL+A (to select all nodes in selected path) 7) ALT+drag node - this MOVES all nodes together rather than sculpts them as described in the manual This is a video I made of the above process: https://dl.dropboxusercontent.com/u/14392713/temp/inkscape-sculpt-problem4.m kv I've also worked with a friend using Windows 7, where we have both done the same steps simultaneously. Hers works correctly (except the note mentioned in step 5) and mine does not. Any help would be very much appreciated! Environment: Ubuntu 12.04.4 (as per /etc/issue) Inkscape 0.48.4 (see my video below - installed from trunk ppa), but also tested in 0.48.3.1 (from Canonical repo) Default preferences (~/.config/inkscape deleted) System Alt key swapped with Win key (as per http://askubuntu.com/questions/118151/how-do-i-disable-window-move-with-alt- left-mouse-button-in-gnome-shell#272317)

2 1

Can't compile for Windows x64 (with btool)
by Liam White 18 May '14

18 May '14

Googled this issue, tried all the recommended solutions, and I found nothing helpful. When I run this command, btool -file build-x64.xml Everything compiles correctly, but the linker completely fails to find all external libraries: Make error line 459: LINK problem: c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lMagick++-6.Q16 c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lMagickCore-6.Q16 c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lMagickWand-6.Q16 c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -latk-1.0 c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -latkmm-1.6 c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lcairo c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lcairomm-1.0 c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lcdr-0.0 c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lexif c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lfontconfig c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lfreetype c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lgc c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lgdk-win32-2.0 c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lgdk_pixbuf-2.0 c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lgdkmm-2.4 c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lgio-2.0 c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lgiomm-2.4 c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lglib-2.0 c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lglibmm-2.4 c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lgobject-2.0 c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lgsl c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lgslcblas c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lgthread-2.0 c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lgtk-win32-2.0 c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lgtkmm-2.4 c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lintl c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -ljpeg c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -llcms2 c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lpango-1.0 c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lpangocairo-1.0 c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lpangoft2-1.0 c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lpangomm-1.4 c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lpangowin32-1.0 c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lpng c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lpoppler c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lpoppler-glib c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lpopt c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lsigc-2.0 c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -ltiff c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lvisio-0.0 c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lwpd-0.9 c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lwpd-stream-0.9 c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lwpg-0.2 The thought occurred to me that the issue might also affect the regular 32-bit builds as well. It didn't. They still compile fine. Johan, Partha, help!

3 4

Setting up a relative link
by john Culleton 18 May '14

18 May '14

I want to set up a relative link within a svg-based website. Here is the code I have now: <a xlink:href="http://../WEB00.svg" id="a3040"> <rect y="839.75012" x="257.37564" height="91.428574" width="282.85715" id="rect3009" style="fill:#ffff00;fill-opacity:1" /> </a> However my browsers (Seamonkey, Firefox, konqueror) can't follow the link. I could use a non-relative link of course but that would mean loading the pages to my website or else moving them to my /var/www/htdocs file. So a relative link would be a great convenience. Can anyone spot the error in my code above? -- John Culleton Wexford Press Free list of books for self-publishers: http://wexfordpress.net/shortlist.html PDF e-book: "Create Book Covers with Scribus" available at http://www.booklocker.com/books/4055.html

2 1

Idea: merge Inset, Outset, Dynamic Offset, Linked Offset
by Krzysztof Kosiński 18 May '14

18 May '14

Currently there are four offset-related items in the menu, but we actually need only one, Dynamic Offset. It could be renamed to Offset or Offset Path. The current Inset and Outset items are practically useless, because they use a fixed, non-configurable width (or it's hidden somewhere in the prefs). Linked Offset is redundant, because this action could be represented by using Dynamic Offset on a clone. What do you think? Regards, Krzysztof

6 8

Windows: why do we build with -O2?
by Johan Engelen 18 May '14

18 May '14

Hi all, Why do we build with -O2 instead of O3? We are missing out on: -O3: Optimize yet more. -O3 turns on all optimizations specified by -O2 and also turns on the -finline-functions, -funswitch-loops, -fpredictive-commoning, -fgcse-after-reload, -ftree-loop-vectorize, -ftree-slp-vectorize, -fvect-cost-model, -ftree-partial-pre and -fipa-cp-clone options. regards, Johan

6 8

Render Barcode extension problems
by Krzysztof Kosiński 18 May '14

18 May '14

The "Render Barcode" extension seems to have some problems: 1. The font for the numbers is specified as "sans-serif", rather than being a specific monospace font such as Courier. The extension should either check the system for a few fonts and use a suitable one, or use fixed paths. 2. The numbers are laid out using spaces instead of the "dx" attribute (kerning), so the spacing is more font-dependent than it should. 3. The layout of numbers looks nothing like the example in Wikipedia, and the quiet zone mark ">" on the right is missing. Regards, Krzysztof

5 9

Inkscape doesn't apply a changed display profile
by Tobias Ellinghaus 17 May '14

17 May '14

Hello, after annoying su_v with this for a while in IRC I'm taking this to the list now and hope that someone here can have a look -- otherwise I will try to file it in launchpad. The bug (?) I see is that Inkscape fails to apply a changed display color profile. More precisely, when I tick "Retrieve profile from display" in the settings Inkscape correctly gets whatever I set in the X atom. When I change the assigned profile while Inkscape is running it doesn't change the used profile though. After digging into the code a bit I found that src/ege-color-prof-tracker.cpp correctly notices that the profile was changed in handle_property_change(), it manages to extract the correct data and calls set_profile(). Afterwards fire() is called and the innermost if() is also reached, resulting in the g_signal_emit() being executed. This looks all fine and dandy. However, there is no further reaction I could see. I didn't try to understand what signal exactly was emitted there and what pieces of code connected to that, so I can't tell if the signal isn't caught by anyone, or if the subsequent code is buggy. All I could notice is that the newly found profile is not used. The easiest way to test this is using a regular sRGB profile and one of those profiles that swap color channels (BRG.icc or the like). I would expect that changing the display profile makes a noticeable difference then. I hope that it's just a small fix and that it can be taken care of for the upcoming release. Thanks for your attention, and thanks for Inkscape. Tobias

1 0

Re: [Inkscape-devel] Rejuvenated build system for Mac OS X
by su_v 16 May '14

16 May '14

On 2014-05-06 11:49 +0100, Partha Bagchi wrote: > Yes, my builds open PDF files and I saw this Debian bug report where > someone claimed that Inkscape uses gs instead of pstoedit: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=366797 That bug report was originally filed against older versions of inkscape (0.43-0.46). With the release of Inkscape 0.47 on 2009-11-24, PS/EPS import was switched from pstoedit to ps2pdf (from Ghostscript): <http://wiki.inkscape.org/wiki/index.php/Release_notes/0.47#PostScript_and_E…> <http://tavmjong.free.fr/INKSCAPE/MANUAL/html/File-Import.html> pstoedit [1] (used in older Inkscape versions for PS/EPS import) is a different application than ps2pdf [2] (used by current Inkscape stable and trunk [3]). 'ps2pdf' is part of Ghostscript i.e. it is one of the many separate command line tools installed by Ghostscript. [1] pstoedit: <http://www.pstoedit.net/> [2] ps2pdf (Ghostscript): <http://www.ghostscript.com/> <http://www.ghostscript.com/doc/9.10/Ps2pdf.htm> [3] (e)ps_input: <http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/view/head:/share/e…> <http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/view/head:/share/e…> <http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/view/head:/share/e…> > On Mon, May 5, 2014 at 10:01 PM, su_v <suv-sf@...58...> wrote: > >> On 2014-05-06 03:38 +0100, Partha Bagchi wrote: >>> On Mon, May 5, 2014 at 8:40 PM, su_v <suv-sf@...58...> >> wrote: >> >>>>> and I was not able to open EPS files (got a parsing error with >>>>> "expecting "<" ...). >>>> >>>> Since you don't share details about how your app was created (I assume >>>> you used custom packaging routines, too, besides your own build env for >>>> the dependencies), I can only guess what the underlying issue might be: >>>> >>>> I build all gtk/glib dependencies from scratch, everything I need for >> Gimp >>> (you can check out my Gimp builds on my website). >>> >>> I downloaded your branch and built the Inkscape App using the same >>> structure as my Gimp builds. The Inkscape App like my Gimp builds is self >>> contained and does not rely on the User for any dylibs. >>> >>>> 1) Is your Inkscape.app (Inkscape-0.48-dev) able to open PDF files? >>>> (these kind of parser errors are known from contexts where PDF >>>> support in Inkscape is broken - e.g. because poppler was configured >>>> without xpdf headers, or not built in at all). >>>> >>> See above. My builds have poppler configured with xpdf headers and >>> associated dependencies included. My Gimp builds open PDF/EPS/PS just >> fine. >>> :) I'll be happy to share my Inkscape build with you (or anyone) if >> needed. >> >> So your Inkscape.app build does open PDF files or not? Please note that >> GIMP's PostScript import feature is different from Inkscape. >> >>>> (If poppler support was not properly compiled in, >>>> 'org.inkscape.input.pdf' might be a logged missing dependency for input >>>> formats like PS and EPS (see 'extension-errors.log' in the inkscape user >>>> profile dir used by Inkscape.app - the exact location depends on whether >>>> you used the launcher script of the 'osxmenu' branch, or your own)). >>>> >>>> 2) Did you verify that the bundled ps2pdf and GhostScript (I assume you >>>> included it in the app bundle, since it is a required helper app for >>>> PostScript input in Inkscape) works as expected? >>>> >>> I was going to build ps2pdf till I saw the bugreport where you said that >>> one does not need it anymore. Gimp does not need ps2pdf to open EPS files >>> (or Ghostscript for that matter). Just the dylib. I'll build ps2pdf and >>> recheck this. >> >> Which bug report for inkscape - do you have a link? I can't imagine that >> I said that Inkscape no longer needs ps2pdf for EPS/PS import (it still >> does). >> >> In Inkscape, PS/EPS import works in two steps: >> 1) the PostScript file is converted to a PDF file with ps2pdf from >> Ghostscript (needs to be in $PATH). >> 2) the just created PDF file is imported in Inkscape using built-in >> (poppler-based) routines. >>

2 1

Windows devs: IMPORTANT, buildtool improvement
by Johan Engelen 15 May '14

15 May '14

Hi all, If you bzr up, you have to rebuild buildtool. I added a cxxflags attribute, so we no longer get warnings about C++ flags that are not applicable to C compilation. This is cmd you need: g++ buildtool.cpp -o btool.exe -O3 -fopenmp regards, Johan

1 0

Careful with merging!
by Johan Engelen 15 May '14

15 May '14

Hi all, Look here: http://bazaar.launchpad.net/~inkscape.dev/inkscape/experimental/changes rev 13365 <http://bazaar.launchpad.net/%7Einkscape.dev/inkscape/experimental/revision/…> managed to 'rename' my earlier commit to include poppler in win64 build. My recommendation to not waste too many brain cycles: don't merge. You can create you own branch, fine, just don't merge it in. Just create a separate trunk/experimental checkout and copy your changes in, then commit. Whatever you think about better workflows, it is paramount to maintain a clean version history. And again and again, we have proven that we are not capable of maintaining a clean history by using bzr merge. Thanks, Johan

4 5