- Inkscape Devel - Inkscape Mailman

Re: [Inkscape-devel] Doc scaling compatibility issue (Bug 1389723)
by Olof Bjarnason 06 Jun '16

06 Jun '16

Does the Inkscape 'extended' .svg file format not contain information on what version of Inkscape it was saved in? On 6 Jun 2016 00:47, "C R" <cajhne@...400...> wrote: Is this related to why flowed text line spacing sometimes freaks out when loaded? It's been really messing me up lately. For an example, load this file: https://www.dropbox.com/s/3f43lyrr494m8cm/testfile.svg?dl=0 and try to change the line spacing in the text box. Works okay in 0.91 stable and not at all in current trunk. -C On Sun, Jun 5, 2016 at 8:59 PM, Bryce Harrington <bryce@...961...> wrote: > What do you think we should do about the release-critical DPI bug? > We need a decision on a course of action. > > > One of the changes we're bringing in this release is changing the > definition of px from 90 dpi to 96 dpi, but a consequence of this is > that documents created in 0.91 or earlier will become mis-scaled if used > in 0.92. This is tracked in the following bug report: > > https://bugs.launchpad.net/inkscape/+bug/1389723 > > This is a release-critical bug, the sort that is likely to become a > thorn in our side in the near to mid term as users start running into > it more and more. Longer term it will diminish as our users move to > newer versions, but I imagine it'll take multiple years before it goes > away completely. > > I don't think we should consider reverting the change; it was introduced > pretty early on this development cycle so backing it out could cause > secondary bugs to crop up. Also, it's a change that has to be done, so > if we don't do it this release we'll have to go through all the trouble > again next release anyway. > > One proposed approach is to detect the affected files on load and > display a warning with a recommendation to convert the file manually. > Javier has posted a conversion tool that could be made use of; it's > received a fair bit of testing but there may be some remaining corner > cases to sort out; on the plus side with it being a discrete utility > fixes could be rolled out for it without needing full Inkscape releases. > > The other proposed approach would be for Inkscape to internally convert > files, so that no warning is needed. In theory this would provide a > better user experience, but is going to require a lot more developer > effort and thorough testing. I'm doubtful that all of this can be done > adequately within the timeframe we're looking at for the release. > > Both approaches also require a mechanism to detect affected files, which > sounds like it may be the tricky part here, as our SVG documents haven't > had versioning information we could rely on for this case. > > Do you have thoughts on other ways to address this issue? Do you have a > strong opinion on whether for this release we should use the expedient > approach or else postpone the release until the more user-friendly > approach can be developed? Or should we reconsider a revert of the DPI > switch so we can get the release out and re-enable it post-release in > hopes the issues can be worked out? > > Bryce > > > > ------------------------------------------------------------------------------ > What NetFlow Analyzer can do for you? Monitors network bandwidth and > traffic > patterns at an interface-level. Reveals which users, apps, and protocols > are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

2 1

Help Needed on Release Notes
by Bryce Harrington 05 Jun '16

05 Jun '16

Can you lend a hand in writing a section or two for the release notes? http://wiki.inkscape.org/wiki/index.php/Release_notes/0.92 1. Release highlights The write ups on the new features are spot on and look beautiful. We need to select a few of them deserving special mention - say 3-6 items - to make mention of in the 'Release Highlights' section. These should be like major changes, broadly useful enhancements that lots of people have been wanting, or specialized but powerful new capabilities. Stuff that can be described concisely but that will resonate with readers. 2. Notable Bug Fixes Could someone produce a dump or query of the bugs closed during this release period? Include a link to that listing here in this section. Then we need someone to look through those and pick out the (small?) proportion worth mentioning for the release - this will be pretty subjective but that's okay. We might want to categorize the list as platform-independent issues, Windows issues, OSX issues, and Linux issues. 3. Known Issues A link to current high/critical bug reports would be worth including here. >From that list we should pick out a subset worth mentioning in the release notes. This should be severe issues that will affect a broad number of users, or issues we're likely to get a lot of duplicate bug reports about. This should include our three release-critical bugs (we can move them to notables once they're resolved). Where possible, it would be useful to provide a sentence or two describing recommended workarounds, maybe with a link to the appropriate bug comment, forum topic, or mailing list email. 4. Anything missed? In general, review the release notes to see if there's any features that haven't gotten documented yet. Any new dependencies that should be mentioned? More translations? Thanks, Bryce

1 0

Inkscape 0.92pre0 Mac OSX 10.11.5 Compile Error
by Partha Bagchi 05 Jun '16

05 Jun '16

Tried compiling on the Mac. Get the following error: make[2]: *** No rule to make target `src/inkscape-version.cpp', needed by > `src/CMakeFiles/inkscape_base.dir/inkscape-version.cpp.o'. Stop. > make[1]: *** [src/CMakeFiles/inkscape_base.dir/all] Error 2 > make: *** [all] Error 2 My command line invocation: CXX="g++ -stdlib=libc++ " cmake -DCMAKE_CXX_FLAGS="-std=c++11 > -Wno-error=c++11-narrowing -Wc++11-extensions -O3 -ffast-math > -ftree-vectorize -mmacosx-version-min=10.8" > -DCMAKE_EXE_LINKER_FLAGS="-headerpad_max_install_names" > -DCMAKE_INSTALL_PREFIX=./Release -DWITH_GTK3_EXPERIMENTAL=YES > -DCMAKE_BUILD_TYPE=Release ..

2 2

INX Parameters
by ugajin 03 Jun '16

03 Jun '16

Hi, Is it possible to set the min/max param attribute values for an .inx file from within its associated Python scrip? E.g. when an int type param is not declared with min/max attribute values, the default values 0, and 10 are applied, and I would like to overwrite these, or whatever the values declared in the .inx file may be, from the associative Python script. I am guessing this may prove difficult, if the .inx file is parsed on loading Inkscape. Many thanks in anticipation. -u

4 9

CMake on win64
by Eduard Braun 29 May '16

29 May '16

Hi all, I just tried to do a cmake build on win64 and (what did I expect?) it didn't work... I followed the instructions at [1] but when linking libinkscape_base.dll I got the following errors: [ 99%] Linking CXX shared library ..\lib\libinkscape_base.dll CMakeFiles\inkscape_base.dir/objects.a(demangle.cpp.obj):demangle.cpp:(.text+0x278): undefined reference to `strdup' CMakeFiles\inkscape_base.dir/objects.a(xslt.cpp.obj):xslt.cpp:(.text+0x78b): undefined reference to `close' CMakeFiles\inkscape_base.dir/objects.a(script.cpp.obj):script.cpp:(.text+0x2a): undefined reference to `close' CMakeFiles\inkscape_base.dir/objects.a(script.cpp.obj):script.cpp:(.text+0x33): undefined reference to `unlink' CMakeFiles\inkscape_base.dir/objects.a(script.cpp.obj):script.cpp:(.text+0x166): undefined reference to `close' CMakeFiles\inkscape_base.dir/objects.a(script.cpp.obj):script.cpp:(.text+0x16f): undefined reference to `unlink' CMakeFiles\inkscape_base.dir/objects.a(script.cpp.obj):script.cpp:(.text+0x38e3): undefined reference to `close' CMakeFiles\inkscape_base.dir/objects.a(script.cpp.obj):script.cpp:(.text+0x38ed): undefined reference to `unlink' CMakeFiles\inkscape_base.dir/objects.a(script.cpp.obj):script.cpp:(.text+0x3d19): undefined reference to `close' CMakeFiles\inkscape_base.dir/objects.a(script.cpp.obj):script.cpp:(.text+0x3d23): undefined reference to `unlink' CMakeFiles\inkscape_base.dir/objects.a(script.cpp.obj):script.cpp:(.text+0x4998): undefined reference to `close' CMakeFiles\inkscape_base.dir/objects.a(emf-inout.cpp.obj):emf-inout.cpp:(.text+0xf21): undefined reference to `strdup' CMakeFiles\inkscape_base.dir/objects.a(emf-inout.cpp.obj):emf-inout.cpp:(.text+0xf82): undefined reference to `strdup' CMakeFiles\inkscape_base.dir/objects.a(emf-inout.cpp.obj):emf-inout.cpp:(.text+0x1356): undefined reference to `strdup' CMakeFiles\inkscape_base.dir/objects.a(emf-inout.cpp.obj):emf-inout.cpp:(.text+0x13e5): undefined reference to `strdup' CMakeFiles\inkscape_base.dir/objects.a(emf-inout.cpp.obj):emf-inout.cpp:(.text+0x18c3): undefined reference to `strdup' CMakeFiles\inkscape_base.dir/objects.a(emf-inout.cpp.obj):emf-inout.cpp:(.text+0x1c04): more undefined references to `strdup' follow CMakeFiles\inkscape_base.dir/objects.a(print.cpp.obj):print.cpp:(.text+0x296): undefined reference to `close' CMakeFiles\inkscape_base.dir/objects.a(print.cpp.obj):print.cpp:(.text+0x707): undefined reference to `unlink' CMakeFiles\inkscape_base.dir/objects.a(ink-comboboxentry-action.cpp.obj):ink-comboboxentry-action.cpp:(.text+0x17): undefined reference to `strdup' CMakeFiles\inkscape_base.dir/objects.a(color-profile.cpp.obj):color-profile.cpp:(.text+0x2193): undefined reference to `read' CMakeFiles\inkscape_base.dir/objects.a(color-profile.cpp.obj):color-profile.cpp:(.text+0x21d3): undefined reference to `close' CMakeFiles\inkscape_base.dir/objects.a(inkscape.cpp.obj):inkscape.cpp:(.text+0xcfa): undefined reference to `unlink' CMakeFiles\inkscape_base.dir/objects.a(prefix.cpp.obj):prefix.cpp:(.text+0x1b8): undefined reference to `strdup' CMakeFiles\inkscape_base.dir/objects.a(prefix.cpp.obj):prefix.cpp:(.text+0x348): undefined reference to `strdup' CMakeFiles\inkscape_base.dir/objects.a(prefix.cpp.obj):prefix.cpp:(.text+0x359): undefined reference to `strdup' CMakeFiles\inkscape_base.dir/objects.a(prefix.cpp.obj):prefix.cpp:(.text+0x4a2): undefined reference to `strdup' CMakeFiles\inkscape_base.dir/objects.a(prefix.cpp.obj):prefix.cpp:(.text+0x1a7): undefined reference to `strdup' CMakeFiles\inkscape_base.dir/objects.a(prefix.cpp.obj):prefix.cpp:(.text+0x328): more undefined references to `strdup' follow CMakeFiles\inkscape_base.dir/objects.a(winmain.cpp.obj):winmain.cpp:(.text+0x13): undefined reference to `fileno' CMakeFiles\inkscape_base.dir/objects.a(winmain.cpp.obj):winmain.cpp:(.text+0x23): undefined reference to `fileno' CMakeFiles\inkscape_base.dir/objects.a(winmain.cpp.obj):winmain.cpp:(.text+0xad): undefined reference to `fileno' CMakeFiles\inkscape_base.dir/objects.a(winmain.cpp.obj):winmain.cpp:(.text+0xb9): undefined reference to `dup2' CMakeFiles\inkscape_base.dir/objects.a(winmain.cpp.obj):winmain.cpp:(.text+0xdd): undefined reference to `fileno' CMakeFiles\inkscape_base.dir/objects.a(winmain.cpp.obj):winmain.cpp:(.text+0xe9): undefined reference to `dup2' CMakeFiles\inkscape_base.dir/objects.a(sp-filter.cpp.obj):sp-filter.cpp:(.text+0x42f): undefined reference to `strdup' CMakeFiles\inkscape_base.dir/objects.a(sp-filter.cpp.obj):sp-filter.cpp:(.text+0x4e2): undefined reference to `strdup' CMakeFiles\inkscape_base.dir/objects.a(sp-offset.cpp.obj):sp-offset.cpp:(.text+0x238a): undefined reference to `strdup' CMakeFiles\inkscape_base.dir/objects.a(sp-offset.cpp.obj):sp-offset.cpp:(.text+0x29d7): undefined reference to `strdup' ../lib/lib2geom_LIB.a(bezier-clipping.cpp.obj):bezier-clipping.cpp:(.text.startup+0x6f): undefined reference to `nextafter' E:/Temp/Inkscape/build/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/5.3.0/../../../../x86_64-w64-mingw32/lib/../lib/libmingwex.a(lib64_libmingwex_a-mingw_vfprintf.o):mingw_vfprintf.c:(.text+0x11): undefined reference to `_lock_file' E:/Temp/Inkscape/build/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/5.3.0/../../../../x86_64-w64-mingw32/lib/../lib/libmingwex.a(lib64_libmingwex_a-mingw_vfprintf.o):mingw_vfprintf.c:(.text+0x33): undefined reference to `_unlock_file' E:/Temp/Inkscape/build/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/5.3.0/../../../../x86_64-w64-mingw32/lib/../lib/libmingwex.a(lib64_libmingwex_a-mingw_vprintf.o):mingw_vprintf.c:(.text+0x16): undefined reference to `_lock_file' E:/Temp/Inkscape/build/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/5.3.0/../../../../x86_64-w64-mingw32/lib/../lib/libmingwex.a(lib64_libmingwex_a-mingw_vprintf.o):mingw_vprintf.c:(.text+0x44): undefined reference to `_unlock_file' collect2.exe: error: ld returned 1 exit status src\CMakeFiles\inkscape_base.dir\build.make:18858: recipe for target 'lib/libinkscape_base.dll' failed mingw32-make[2]: *** [lib/libinkscape_base.dll] Error 1 CMakeFiles\Makefile2:369: recipe for target 'src/CMakeFiles/inkscape_base.dir/all' failed mingw32-make[1]: *** [src/CMakeFiles/inkscape_base.dir/all] Error 2 Makefile:126: recipe for target 'all' failed mingw32-make: *** [all] Error 2 I assume there's an issue with linking to the standard library, but since I have no experience with CMake at all I don't have the slightest idea where to start... Anybody knows what might cause the issue and maybe even has a solution? Best Regards, Eduard [1] http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows_64-bi…

3 2

Releases Pages
by Martin Owens 26 May '16

26 May '16

Dear developers, I've released the next iteration of the website's "releases" app, this is the app that delivers each of our releases for different platforms. The releases app is still going through it's draft phase, but I hope to have the download pages replaced in time for 0.92. To do that I need your help to review the pages. If you can help with css patches, that would be great too. Currently available: https://inkscape.org/en/release/ Note: The releases will auto detect your os and give you the right download, but it's unconfigured on live and needs a bit of administrative help to get that all set up since the matching fields changed. I'd also like to draw your attention to the new request to donate after download: https://inkscape.org/en/release/0.91/windows/32-bit/ (click on one of the downloads to start) The text for these should be reviewed as well as the layout if you want to have a crack at the presentation. Thanks everyone for helping make 0.92 easier to deliver to our users. :-) Best Regards, Martin Owens

5 10

inkscape-0.92pre0 source tarball
by Bryce Harrington 26 May '16

26 May '16

Another pre-release is now available for testing from the source downloads page: https://inkscape.org/en/download/source/ The release is: 0.92pre1 Source Tarball Bzip https://inkscape.org/en/gallery/item/9633/inkscape-0.92pre1.tar.bz2 This is an early preview of our upcoming release and as such can be expected to have some stability issues or incomplete features. See Inkscape's bug tracker for a list of known issues. == Translation == We are now in String Freeze. All translators should strive to bring the language files up to date. Please aim to get all translation work committed by mid-June. == Packaging == Packagers for Linux, Windows, and OSX should use this source tarball for creating packages for their respective platforms. I strongly urge all packagers to test their packaging scripts at this time and generate packages for pre1. Please report to this thread with your status in getting the packages made, so I can identify where help is needed. Note that this was produced using the new cmake system, and the autoconfig build files are not included in this dist; if you require the autoconfig system for your platform you can still generate an autoconfig tarball from our VCS trunk, however you should prioritize shifting to cmake as we will be dropping autoconfig in the future 0.93 release. I plan to continue post further pre-releases on a roughly 1-2 week cadence until we feel the codebase is stable enough for the final release, which would be late June at the earliest. == About Screen == Hopefully a contest for the about screen should start up soonish? In the interim, and as a contingency in case it doesn't happen, could someone modify the 0.91 about screen to say 0.92pre? ------------------------------------------------------------------------ Thanks, Bryce

2 1

Inkscape todays Trunk refuses to launch on Kubuntu 14.04 and 16.04
by Ivan Louette 25 May '16

25 May '16

Inkscape todays Trunk refuses to launch on Kubuntu 14.04 and 16.04 After clicking on its icon it tries to launch but but after some seconds its icon disappears from Kubuntu's bar and nothing more happens on screen. ivan

5 9

New video three features.
by Jabiertxo Arraiza Cenoz 25 May '16

25 May '16

Hi, here are my last video. Is a kind of showcase of three features: * Eraser tool with no width now in trunk. * Randomize color extension now with a limit slider, also in trunk. * Optional auto fill Delaunay triangles with color and thin stroke in the same color. The code of this are in this bug:https://bugs.launchpad .net/inkscape/+bug/1553497 Anyway, there is better/faster ways to make Delaunay based in a image. So this is just a example. http://jabiertxof.marker.es/2016/03/no-width-eraser-mode-limit-random.h tml Cheers, Jabier.

3 2

0.92 release
by Alex Valavanis 24 May '16

24 May '16

Hi All, Just wondering if there are plans to freeze development yet? I think we're getting close to having a working CMake build... are there any "must have" features that are not yet fully implemented in 0.92, or can we push on with fixing-up the remaining bugs and releasing? I'm quite eager to make the switch to a hard C++11 requirement and default to Gtk+ 3, so the sooner we can get 0.92 out, the better :) Best wishes, Alex

11 21