- Inkscape Devel - Inkscape Mailman

SVG Working Group: Markers
by Tavmjong Bah 21 Jul '10

21 Jul '10

Hi, There was a lengthy discussion about markers at yesterday's SVG teleconference. At least one browser vendor would like to change the behavior of markers in the SVG1.1 spec. At the moment, markers inherit the style of their parent at the point they are defined: <g fill="black" stroke="red> <marker id="marker1"> <rect width="10" height="10"/> </marker> <path marker-start="url(#marker1)" d="M 30 60 L 80 60 L 80 110 Z"/> <g> would produce a marker on a path. Both the marker and path would have a black fill and a red stroke. On the other hand: <g fill="green" stroke="yellow> <marker id="marker2"> <rect width="10" height="10"/> </marker> <g> <g fill="black" stroke="red> <marker id="marker2"> <rect width="10" height="10"/> </marker> <path marker-start="url(#marker2)" d="M 30 60 L 80 60 L 80 110 Z"/> <g> would produce a marker on a path with the marker having a green fill and yellow stroke. The proposal is to change the behavior so that the marker fill and stroke are defined at the point they are referenced (like the <use> object). This would allow markers to take the color of the path they are attached to. It was claimed that a search of roughly 30,000 SVG's collected from the Web finds only one SVG that relies on the current spec's behavior... namely the SVG from the W3C test suite that specifically tests the behavior. I'm not sure if this is actually true as many Inkscape's markers don't include fill or stroke color. Since they are defined in the <defs> section, the fill defaults to black. If the marker fill were defined at the point of reference, I would think that it would take the object's fill... which is normally "none" for a path with an arrowhead. I pointed out that this does not solve the typical Inkscape user's problem since what most user's want is for the marker fill to be the same color as the object's stroke color, see: https://bugs.launchpad.net/inkscape/+bug/165865 The plan is to reevaluate the proper way to handle markers for SVG2 and then look at what changes to 1.1 can be made that will be compatible with SVG2. This could include changing the spec as described above. Tav BTW, why do some Inkscape markers include "font-size" in their style?

3 2

Updating our 2geom
by unknown＠example.com 21 Jul '10

21 Jul '10

Hi all, Now that 0.48 is branched off, we can work towards updating our 2geom copy. I think the most problematic 2geom change is the renaming of "Geom::Matrix" to "Geom::Affine". Nathan, I read in one of your mails that you already worked on renaming those in Inkscape? Ciao, Johan

2 1

Re: [Inkscape-devel] After the dbus api merge, trunk (9614) fails to build on osx
by Uwe Schöler - OSS-Marketplace.com 20 Jul '10

20 Jul '10

Hi, i get similar errors while building inkscape on windows7 with dbus-wrapper.c I'm not familiar with all that stuff, so i attached the log file ;) Sincerely, UweSch 1) make error due to hardcoded 'libtoolize' in autogen.sh > $ make > CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh /Volumes/blue/src/Inkscape/src/inkscape-repo/mp-x11/missing --run aclocal-1.11 > cd . && /bin/sh /Volumes/blue/src/Inkscape/src/inkscape-repo/mp-x11/missing --run automake-1.11 --foreign > configure.ac:33: required file `./ltmain.sh' not found > make: *** [Makefile.in] Error 1 On OS X libtool and libtoolize are installed as 'glibtool' and 'glibtoolize'. autogen.sh should either test for it or maybe use the environment variables ($LIBTOOL, $LIBTOOLIZE) which could be set in the packaging script (packaging/macosx/osx-build.sh). After editing autogen.sh (replace "libtoolize" with "glibtoolize") to test the fix, autogen.sh and configure ran through: > Configuration: > > Source code location: . > Destination path prefix: /Volumes/blue/src/Inkscape/src/inkscape-repo/mp-x11/packaging/macosx/../../Build > Compiler: ccache g++ > CPPFLAGS: -Wall -Wformat -Wformat-security -W -D_FORTIFY_SOURCE=2 -I/Volumes/blue/mp-inkscape/with-a-long-long-long-directory-name/include > CXXFLAGS: -Wpointer-arith -Wcast-align -Wsign-compare -Woverloaded-virtual -Wswitch -Wno-unused-parameter -O3 -Wall -Wno-strict-aliasing > CFLAGS: -Wno-pointer-sign -O3 -Wall > LDFLAGS: -L/Volumes/blue/mp-inkscape/with-a-long-long-long-directory-name/lib > > Use Xft font database: yes > Use gnome-vfs: yes > Use openoffice files: yes > Use relocation support: no > Internal Python: skipped > Internal Perl: skipped > Enable LittleCms: yes > Enable DBUS no > Enable Poppler-Cairo: yes > ImageMagick Magick++: yes > Libwpg: yes > Doing Local Install: no but make failed later on with: 2) link error for 'libinkdbus.la' > CCLD libinkdbus.la > Undefined symbols: ... > ld: symbol(s) not found > collect2: ld returned 1 exit status > make[3]: *** [libinkdbus.la] Error 1 > make[2]: *** [all] Error 2 > make[1]: *** [all-recursive] Error 1 > make: *** [all] Error 2 Any hints on how one can really disable DBUS in Inkscape for now or how to investigate if this is a problem with my local build environment (dbus, dbus-glib dependencies are installed [2]) or why this error happens on osx would be highly appreciated. ~suv [1] from the console log building bzr trunk 9614: > LeWitt:mp-x11 suv$ make > make all-recursive > Making all in src > dbus-binding-tool --mode=glib-server --output=extension/dbus/application-server-glue.h --prefix=application_interface extension/dbus/application-interface.xml > dbus-binding-tool --mode=glib-server --output=extension/dbus/document-server-glue.h --prefix=document_interface extension/dbus/document-interface.xml > dbus-binding-tool --mode=glib-client --output=extension/dbus/document-client-glue.h --prefix=document_interface extension/dbus/document-interface.xml > make all-am > CXX arc-context.o > ... > > CXX extension/print.o > CXX extension/dbus/dbus-init.o > extension/dbus/dbus-init.cpp:71: warning: unused parameter ‘proxy’ > extension/dbus/dbus-init.cpp: In function ‘void Inkscape::Extension::Dbus::init()’: > extension/dbus/dbus-init.cpp:87: warning: unused variable ‘obj’ > extension/dbus/dbus-init.cpp: In function ‘gchar* Inkscape::Extension::Dbus::init_document()’: > extension/dbus/dbus-init.cpp:103: warning: unused variable ‘result’ > extension/dbus/dbus-init.cpp:104: warning: unused variable ‘error’ > CXX extension/dbus/application-interface.o > extension/dbus/application-interface.cpp:40: warning: unused parameter ‘object’ > extension/dbus/application-interface.cpp:57: warning: unused parameter ‘object’ > extension/dbus/application-interface.cpp:57: warning: unused parameter ‘error’ > extension/dbus/application-interface.cpp:63: warning: unused parameter ‘object’ > extension/dbus/application-interface.cpp:70: warning: unused parameter ‘object’ > extension/dbus/application-interface.cpp:70: warning: unused parameter ‘error’ > extension/dbus/application-interface.cpp:78: warning: unused parameter ‘object’ > extension/dbus/application-interface.cpp:78: warning: unused parameter ‘document_name’ > extension/dbus/application-interface.cpp:78: warning: unused parameter ‘error’ > extension/dbus/application-interface.cpp:85: warning: unused parameter ‘object’ > extension/dbus/application-interface.cpp:85: warning: unused parameter ‘error’ > extension/dbus/application-interface.cpp:91: warning: unused parameter ‘object’ > extension/dbus/application-interface.cpp:91: warning: unused parameter ‘error’ > extension/dbus/application-interface.cpp:101: warning: unused parameter ‘object’ > extension/dbus/application-interface.cpp:101: warning: unused parameter ‘error’ > extension/dbus/application-interface.cpp:107: warning: unused parameter ‘object’ > extension/dbus/application-interface.cpp:114: warning: unused parameter ‘object’ > extension/dbus/application-interface.cpp:114: warning: unused parameter ‘error’ > CXX extension/dbus/document-interface.o > extension/dbus/document-interface.cpp:205: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:341: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:486: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:521: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:555: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:563: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:573: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:807: warning: unused parameter ‘object’ > extension/dbus/document-interface.cpp:807: warning: unused parameter ‘shape’ > extension/dbus/document-interface.cpp:841: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:853: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:877: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:933: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:944: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:958: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:975: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:1019: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:1040: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:1055: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:1079: warning: unused parameter ‘object’ > extension/dbus/document-interface.cpp:1079: warning: unused parameter ‘x’ > extension/dbus/document-interface.cpp:1079: warning: unused parameter ‘y’ > extension/dbus/document-interface.cpp:1079: warning: unused parameter ‘x2’ > extension/dbus/document-interface.cpp:1079: warning: unused parameter ‘y2’ > extension/dbus/document-interface.cpp:1079: warning: unused parameter ‘replace’ > extension/dbus/document-interface.cpp:1079: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:1141: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:1153: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:1160: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:1277: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:1299: warning: unused parameter ‘object’ > CXX extension/implementation/implementation.o > extension/implementation/implementation.cpp:100: warning: unused parameter ‘docCache’ > CXX extension/implementation/script.o > ... > > CXX inkscape-version.o > AR libinkversion.a > CC extension/dbus/wrapper/libinkdbus_la-inkscape-dbus-wrapper.lo > CCLD libinkdbus.la > Undefined symbols: > "_dbus_g_bus_get", referenced from: > _dbus_get_connection in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_desktop_init_dbus in libinkdbus_la-inkscape-dbus-wrapper.o > "_dbus_g_proxy_call", referenced from: > _inkscape_delete_all in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_call_verb in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_rectangle in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_ellipse in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_polygon in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_star in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_spiral in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_line in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_text in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_image in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_node in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_document_get_width in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_document_get_height in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_document_get_css in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_document_set_css in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_document_merge_css in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_document_resize_to_fit_selection in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_set_attribute in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_set_int_attribute in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_set_double_attribute in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_get_attribute in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_move in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_move_to in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_object_to_path in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_get_path in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_transform in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_get_css in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_modify_css in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_merge_css in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_set_color in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_move_to_layer in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_get_node_coordinates in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_save in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_save_as in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_load in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_mark_as_unmodified in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_close in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_inkscape_exit in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_undo in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_redo in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_pause_updates in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_resume_updates in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_update in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_get in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_add in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_add_list in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_set in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_set_list in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_rotate in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_delete in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_clear in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_select_all in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_select_all_in_all_layers in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_box in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_invert in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_group in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_ungroup in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_cut in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_copy in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_paste in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_scale in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_move in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_move_to in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_move_to_layer in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_get_center in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_to_path in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_combine in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_divide in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_change_level in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_layer_new in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_layer_set in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_layer_get_all in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_layer_change_level in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_layer_next in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_layer_previous in libinkdbus_la-inkscape-dbus-wrapper.o > "_dbus_g_proxy_new_for_name", referenced from: > _dbus_get_proxy in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_desktop_init_dbus in libinkdbus_la-inkscape-dbus-wrapper.o > "_dbus_g_type_get_collection", referenced from: > _inkscape_get_node_coordinates in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_get_center in libinkdbus_la-inkscape-dbus-wrapper.o > ld: symbol(s) not found > collect2: ld returned 1 exit status > make[3]: *** [libinkdbus.la] Error 1 > make[2]: *** [all] Error 2 > make[1]: *** [all-recursive] Error 1 > make: *** [all] Error 2 > LeWitt:mp-x11 suv$ [2] installed (dbus) dependencies (via MacPorts): dbus @1.2.24_0+no_root+no_startupitem dbus-glib @0.86_1 glib2 @2.24.1_0+darwin ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel -- Mit freundlichem Gruß, Uwe Schöler

4 8

inkscape@...2375... Open
by Alexandre Prokoudine 20 Jul '10

20 Jul '10

Hi, Is anybody planning to participate at SVG Open 2010? Alexandre Prokoudine http://libregraphicsworld.org

2 1

DXF import plugin (dxf_input.py) bugs, missing features and their solutions.
by dormouse 19 Jul '10

19 Jul '10

Hello! Let me introduce myself to group. My name is Vladimir Kalyaev (http://kalyaev.com) one of the "gcodetools" developers. gcodetools is the Inkscape extension to add CNC functionality. It generates G-Codes from SVG drawings and aimed to be a complete CAD/CAM freeware open-source workflow. DXF import bugs. I've discovered 2 major bugs in the latest dxf_import.py release. Both of them are incorrect last "bulget" (having curvature) segment import of LWPOLYLINE. This plugin simply throws away this segment and replaces it with a straight line. Incorrect import example (straight lines point to errorneus lines. Arcs should be there): http://kalyaev.com/2010/20100513/inkscape-direct.png The source code was modified by me to correct these errors. Now all closed polylines imports correctly to Inkscape. Also there is another missing feature: POINT primitive import due to SVG limitation (there is no POINT at all inside SVG specification). dxf_import.py imports POINTS as two circular segments and they are totally indistinguishable from the other objects. Point is very usefull for "drilling" and e.t.c so a simple solution: import them as any object (red arrow in my version) with the "d" outline "M x,y ..." (x,y)=(pointX, pointY) and special SVG-attribute "dxfpoint":"1" to distinguish from the other objects. This behaviour turns on when new "checkmark" is enabled (dxf_import.inx) All of these corrections and additions are tested and work fine. I offer to merge them into current Inkscape dev distribution. Everyone can take these files from launchpad.net "lp:gcodetools" branch or download today's version with the DXF,svg,png examples from the http://kalyaev.com/2010/20100601/gcodetools.v85.zip Have a nice day! --- Vladimir Kalyaev.

3 6

compile error in rev 9618
by bulia byak 18 Jul '10

18 Jul '10

I can probably fix it, but I wonder if it may be a sign of some other trouble. Anyone else seeing this? sp-gradient.h: In function ‘void sp_gradient_pattern_common_setup(cairo_pattern_t*, SPGradient*, const NRRect*)’: sp-gradient.h:81: error: ‘SPGradientUnits SPGradient::units’ is private sp-gradient.cpp:2057: error: within this context sp-gradient.cpp: In function ‘cairo_pattern_t* sp_radialgradient_create_pattern(SPPaintServer*, const NRRect*)’: sp-gradient.cpp:2071: error: ‘sp_gradient_ensure_colors’ was not declared in this scope sp-gradient.cpp: In function ‘cairo_pattern_t* sp_lineargradient_create_pattern(SPPaintServer*, const NRRect*)’: sp-gradient.cpp:2089: error: ‘sp_gradient_ensure_colors’ was not declared in this scope -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

6 6

What are Auto-Smooth Nodes?
by Dave Crossland 16 Jul '10

16 Jul '10

Hi, Over on the www-svg@...157... list, there has been some discussion about Catull-Rom splines, triggered by http://schepers.cc/?p=243 and http://schepers.cc/svg/path/dotty.svg :) These CR curves look exactly like Inkscape's "auto smooth" node type; could someone confirm this? :) CR curves as per dotty.svg change the 4 segments around the point, although since dotty.svg hasn't got moving points functionality yet, only placing new points, then only the 2 segments before the newly placed point are seen changing as a new point is laid down. The Inkscape "auto smooth" node type interaction is the opposite in the 0.47 release, where you can't lay down AS nodes but you can change points' type to AS and then move them around, which effects the 4 segments around the point. I haven't checked the trunk source version; does the latest node tool support this? Cheers Dave

2 5

linking on Fedora
by Jakub Steiner 15 Jul '10

15 Jul '10

Current trunk fails linking the final binaries on Fedora. I am absolutely clueless about the automake system, but adding -lX11 -ldl -ldbus-glib-1 to INKSCAPE_LIBS in src/Makefile does the trick for me in trunk. Can this be fixed upstream or is that a Fedora specific thing that needs to remain being handled downstream? Thank you https://bugs.launchpad.net/inkscape/+bug/595872 -- Jakub Steiner <jimmac@...400...> http://jimmac.musichall.cz

2 1

How to create a Windows Style file selection modally using GTK?
by Bruce 15 Jul '10

15 Jul '10

Dear All, I am writing a GTK application on Win32. I need to create a Windows style file selection dialog using GetOpenFileName function. I have referred to your source code to see how you did it (filedialogimpl-win32.cpp). I see you are calling GetOpenFileName in another thread, and in the main thread, you can g_main_loop_run to block the main window and make the file selection dialog modally. But when I write my code, I cannot block the main window. It seems that calling g_main_loop_run function would also accept and handle signals from the main window, making the main window still active. So can anyone tell me how you make your Windows style file selection dialog modally (preventing the main window from active) ? Bruce Cheng --

2 5

Upgrading Bazaar Repository Format
by Ted Gould 13 Jul '10

13 Jul '10

Hello again, miss me? We had talked about upgrading the Bazaar repository format as the 0.48 release went out the door, I'm thinking that branching is "good enough" for this. I'd like to upgrade to the '2a' format which requires everyone to be using Bazaar 1.16 or better (current is 2.1). I'll do this tomorrow night if there are no complaints. What does this mean to you? Smaller repositories and faster operations with Bazaar. What do you have to do? You can just grab an entirely new check out of the updated branch. Personally, I'd recommend just upgrading your local repos with the "bzr upgrade" command to save yourself some bandwidth. This does take a while, so I'd do it before bed. What about other branches in LP? You probably want to upgrade them as well. If you look at the branch page (something like https://code.edge.launchpad.net/~inkscape.dev/inkscape/trunk ) you'll notice a "Upgrade this branch" button at the very bottom of page. Click that. Any other questions or concerns? --Ted

1 2