- Inkscape Devel - Inkscape Mailman

Re: [Inkscape-devel] Embroidery extension
by Lex Neva 25 Aug '17

25 Aug '17

Hi! Sorry for going dark there -- everyday life intrudes fairly often. Neato, and thanks for the explanation! It does indeed look like your stuff follows a similar method to inkscape-embroidery. A few minor differences: * The extension handles creating a "grating" of lines automatically and intersects them with the fill region using Shapely (a Python extension). * The fill pattern is handled automatically through the insertion of extra nodes as you mentioned. Currently there's only one pattern: a sort of stair-step/staggered pattern that is visually pleasing. I cribbed it off of a pattern I bought online that was made using a commercial embroidery design program. I'd love to understand how to code more complex patterns, but I haven't given much thought to it yet. * The extension used to have a TSP solver of its own, but it really didn't do a particularly good job. I started off trying to fix bugs and ultimately just ripped it out. Instead, I carefully order paths in Inkscape. The new Objects panel is key for this, and it's a hugely awesome addition to Inkscape! The only part I struggle with is that Inkscape doesn't want to let you reorder objects relative to each other if they don't intersect (or nearly intersect). Ultimately, the problem I brought up for discussion boils down to the same problem you're solving with the your TSP algorithm. *Question: *what does your code do if it needs to get from one section to another that is distant? Does it just jump-stitch? Here's a brief description of how to use EmbroiderModder2's libembroidery to convert between formats: https://github.com/lexelby/inkscape-embroidery#optional-conversion-program I'd suggest that your code simply output a CSV in the format libembroidery understands, and then you can make use of its knowledge of pretty much every manufacturer format to convert it to a format compatible with your machine. --Lex On 7/30/2017 11:47 AM, Michael Soegtrop wrote: > Dear Lex, > > I guess we are trying to solve the same problem, but differently. I > wanted to have more control than semi automated fillers provide, so I > added 3 LPEs, which are in Inkscape 0.92.2: > > 1.) A bool LPE to do intersections / unions, ... of areas, so that one > can construct the areas to stitch from drawing areas. > > 2.) A path / path group trimmer LPE, which restricts a set of paths to > an area (or oustide of an area. There are already two path interpolation > LPEs which allow to create sets of paths with fine control over local > direction and density. > > 3.) An LPE to convert a set of paths into stitches. This includes an > almost reasonable traveling salesman problem (TSP) variant solver for > ordering groups of stitches to minimize the traveling in between. It can > still be improved. It is a bit more complicated than standard TSP > solvers, because it looks into groups of parallel stitches which have 4 > possible ends. > > > My approach is as follows > > 1.) Make a drawing > > 2.) Use the bool op LPE to create (in a new layer) the areas to fill > with each color / stitch style. > > 3.) Create a set of path to control density and direction using path > interpolation LPEs. This allows a great deal of control, e.g. for hair. > I don't think any commercial tool allows this amount of control. > > 4.) Use the path trim/cut LPE to trim the paths created in 3.) to the > areas created in 2.) > > 5.) Use the embroidery stitch LPE to convert the paths to stitches. > > Sometimes I use the cut / trim filter also to create intermediate nodes > in paths to create special stitching patterns. These nodes are not > visible in normal drawing, but after stitching they are visible. > > Of cause for simple cases, it would help to extend it with a more > automated approach, which is what you appear to be working at. > > I am very interested in the import/export library you mentioned. > > It would be great to work together on this. > > Best regards, > > Michael >

1 0

SVG in 92 and Phyisical Scale
by James Fritzler 25 Aug '17

25 Aug '17

Hi Inkscape Devs! I’ve used Inkscape for about five years now and have built up quite the library of svg files and have been using 91 since its release. My main creative effort is to build paper toys that I print and cut (in bulk) on a Silhouette Portrait cutting machine. (More info on my works at http://netroids.net ). I have a 100s of files and hoped to use them as my long term "masters” given that SVG is not proprietary and has had such great page layout fidelity for me. I’d love to update to v92 and future versions but, as is commonly known, the svg save logic has changed to support a new CSS standard of 96dpi and it is affecting my ability to import into my cutting software. It seems that perhaps the values written by Inkscape in 91 svg files are encoded using a 90dpi scale from their original design-time dimensions. In the past I’ve had much success importing SVGs from Inkscape 91 into Silhouette studio for years. (Granted, I do perform a little cleansing in a copy of the master svg before I go to Silhouette: I simplify the layers, ungroup, and flatten out clones into their own objects. Perhaps it is just serendipity that the Silhouette Studio imports SVGs at the 90dpi. (I tried asking them about dpi but I couldn’t "break through" their first-tier help desk support "fire wall".) I know there’s an import prompt and process for opening 91 files in 92 and I have participated in the launchpad forum and chat with Mc about this topic. (my user name is jimbox13). Unfortunate for me, none of the prompts give a workable solution. Here’s what happens to my files based on each option. (I used a diff tool in to investigate some of the changes.) * "Accuracy for sizes and position of paths" (Desired option) * Grid and guides appear to be changed – though I’m not sure to what extent. * Rectangles, paths and strokes are sized up by 6.667% * Inkscape Designer Outcome: shapes and sizes correct right based on the page. :) (bug #1712114 occurs.) * Cutter Software Outcome: File is too large (by 6.667%) for cutting area. :( * "Digital Art" * Grid and guides changed to some degree. * Rectangles and paths not changed. * Inkscape Designer Outcome: shapes and sizes are too small for the page :( * Cutter Software Outcome: shapes and sizes are correct :) * "Accuracy for masks and clips" * Grid and guides changed to some degree. * Rectangles, paths and strokes are changed to some degree, not the same as above. * Inkscape Designer Outcome: shapes and sizes correct right based on the page. :) (bug #1712114 does not occur.) * Cutter Software Outcome: File is significantly too small for cutting area. :( None of these options produce a svg that maintains its correct physical dimensions across both software packages. I tried experimenting by customizing the "units.xml" file in 92 without success. Here is my original v91 file zipped. (I added a background rectangle that is the size of the page to help troubleshooting.) https://www.dropbox.com/s/q6o17j5an2piiw3/acutra_TOCUTv91wBG.zip?dl=0 Is there anything that can be done? Thanks Jim

3 4

Changing width, triggers X axis movement
by Germano Massullo 24 Aug '17

24 Aug '17

I am sorry for not having opened a bugreport ticket in Launchpad, but actually Launcpad is experiencing malfunctions in logging process. At the following URL you can see a video example that shows the problem I am reporting: when trying to change width of selection, Inkscape instead changes X axis coordinates. https://youtu.be/Zcc4sq5U1gU inkscape-0.92.1-4.20170510bzr15686.fc26.x86_64 Best regards

2 4

Re: [Inkscape-devel] SVG in 92 and Phyisical Scale
by Jabier Arraiza 24 Aug '17

24 Aug '17

Hi James, Not only I program it but su_v and Tav do a great work on it. Just 96->90 if the document is converted at open. Cheers, Jabier. On Thu, 2017-08-24 at 15:19 +0000, James Fritzler wrote: > I have not tried it yet, but I see that you programmed it. It sounds > really useful! :) > > What steps should I use when I open the 91 file in 92 : Should I > first use the "digital art" option? and then use the 96 to 90 switch? > or should I try one of the other 2 options first (when opening the > old file)? > > > Thanks! > > > ________________________________ > From: jabier.arraiza@...2893... <javier.arraiza@...2893...> > Sent: Thursday, August 24, 2017 7:17:24 AM > To: Martin Owens; James Fritzler > Cc: Inkscape-Devel > Subject: Re: [Inkscape-devel] SVG in 92 and Phyisical Scale > > > Hi james, could you try the extension dpi switcher to convert to 90 > Dpi? > > > > Enviado desde mi móvil LG > > ------ Mensaje original ------ > De: Martin Owens > Fecha: 24/08/2017 15:10 > Para: James Fritzler; > CC: Inkscape-Devel; > Asunto:Re: [Inkscape-devel] SVG in 92 and Phyisical Scale > > > Hi James, > > It seems like the main issue is thrice fold: > > A) opening SVG 1.1 file means we have to convert it to SVG 2.0 dpi, > even though the spec isn't released, we've cut off the published spec > support too early. > B) We can't save physical units into the svg files themselves, > mitigating issues of external unit compatibility. > C) We don't have any capacity for users to change the way svg is > saved > to indicate which svg spec we should use. > > So we've got quite the compatibility problem. This isn't an issue if > one exports pdf files or printing to cut, but is a problem in this > case where the cutting software is consuming svg files directly. > > Tav and others: For 0.93, do we have a plan to try and help this > situation? > > If we can provide a way to save physical units and set svg 1.1 or svg > 2.0 outputs, we should be covering all bases. > > Best Regards, Martin Owens > > On 23 August 2017 at 11:10, James Fritzler wrote: > > Hi Inkscape Devs! > > > > > > I’ve used Inkscape for about five years now and have built up quite > > the > > library of svg files and have been using 91 since its release. My > > main > > creative effort is to build paper toys that I print and cut (in > > bulk) on a > > Silhouette Portrait cutting machine. (More info on my works at > > http://netroids.net ). I have a 100s of files and hoped to use > > them as my > > long term "masters” given that SVG is not proprietary and has had > > such great > > page layout fidelity for me. > > > > > > I’d love to update to v92 and future versions but, as is commonly > > known, the > > svg save logic has changed to support a new CSS standard of 96dpi > > and it is > > affecting my ability to import into my cutting software. > > > > > > It seems that perhaps the values written by Inkscape in 91 svg > > files are > > encoded using a 90dpi scale from their original design-time > > dimensions. In > > the past I’ve had much success importing SVGs from Inkscape 91 into > > Silhouette studio for years. (Granted, I do perform a little > > cleansing in a > > copy of the master svg before I go to Silhouette: I simplify the > > layers, > > ungroup, and flatten out clones into their own objects. Perhaps it > > is just > > serendipity that the Silhouette Studio imports SVGs at the > > 90dpi. (I tried > > asking them about dpi but I couldn’t "break through" their first- > > tier help > > desk support "fire wall".) > > > > > > I know there’s an import prompt and process for opening 91 files in > > 92 and I > > have participated in the launchpad forum and chat with Mc about > > this topic. > > (my user name is jimbox13). > > > > > > Unfortunate for me, none of the prompts give a workable > > solution. Here’s > > what happens to my files based on each option. (I used a diff tool > > in to > > investigate some of the changes.) > > > > "Accuracy for sizes and position of paths" (Desired option) > > > > Grid and guides appear to be changed – though I’m not sure to what > > extent. > > Rectangles, paths and strokes are sized up by 6.667% > > Inkscape Designer Outcome: shapes and sizes correct right based on > > the > > page. :) (bug #1712114 occurs.) > > Cutter Software Outcome: File is too large (by 6.667%) for cutting > > area. :( > > > > "Digital Art" > > > > Grid and guides changed to some degree. > > Rectangles and paths not changed. > > Inkscape Designer Outcome: shapes and sizes are too small for the > > page :( > > Cutter Software Outcome: shapes and sizes are correct :) > > > > "Accuracy for masks and clips" > > > > Grid and guides changed to some degree. > > Rectangles, paths and strokes are changed to some degree, not the > > same as > > above. > > Inkscape Designer Outcome: shapes and sizes correct right based on > > the > > page. :) (bug #1712114 does not occur.) > > Cutter Software Outcome: File is significantly too small for > > cutting area. > > :( > > > > None of these options produce a svg that maintains its correct > > physical > > dimensions across both software packages. I tried experimenting by > > customizing the "units.xml" file in 92 without success. > > > > > > Here is my original v91 file zipped. (I added a background > > rectangle that > > is the size of the page to help troubleshooting.) > > > > https://www.dropbox.com/s/q6o17j5an2piiw3/acutra_TOCUTv91wBG.zip?dl > > =0 > > > > > > Is there anything that can be done? > > > > Thanks > > > > > > > > Jim > > > > > > ----------------------------------------------------------------- > > ------------- > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Inkscape-devel mailing list > > Inkscape-devel(a)lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > > > > ------------------------------------------------------------------- > ----------- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel >

3 6

LXML & Windows
by Jabier Arraiza 23 Aug '17

23 Aug '17

Some users report me the complexity to install LXML on windows. Is posibol integrate it by default? Cheers, Jabier.

2 6

SMIL koi carp animation
by brynn 20 Aug '17

20 Aug '17

Hi Friends, I apologize, but I can't remember who made that SMIL koi carp animation image in the gallery. (User is shown as Unknown Author) I'm thinking Tav, but not positive. Anyway, note this recent comment: https://inkscape.org/en/comments/cr/621/5701/#c1569 I made reply comment that it has a copyright, but at last look, fish still swimming around on his website. I know we decided as a community not to bother with copyright issues in the gallery. But this time, it's one of us. So I just couldn't leave it alone. Although after this message, I am leaving it alone, and the artist can decide what to do :-) All best, brynn

3 2

should this remain in the gallery?
by brynn 20 Aug '17

20 Aug '17

Hi Friends, There's a recent new upload to the gallery, which appears to be instructions for using a website which helps people create their own logos, for a price. I can't see that it has anything to do with Inkscape (except in its PDF, it recommends using Inkscape to edit the logos). They could be considering the phrase in the CoC "made to be used with Inkscape" wrongly. But I'm not sure. (copying to the devel list, re CoC) I'm just looking for some other opinions about this, whether it should remain in the gallery at all, or remain under a different category. Personally, I think it's spam. But since I tend to be rather ruthless about spam, I thought I should ask for other opinions. Does anyone see any relationship to Inkscape here? Thanks, brynn

2 3

Not as awesome as....?
by brynn 20 Aug '17

20 Aug '17

Hi Friends, I happened to be looking through the Release Notes which now appear on the website, under each of the versions of Inkscape which are available for download. I noticed for some of the 0.48.x versions, under Known Issues, it says "Not as awesome as 0.91" For 0.48.3.1 it says "not as awesome as 0.49" which might be a clue these items were added around the time the decision was made to jump from 0.48 to 0.91. So apparently this was done on the wiki, and just made the transfer to the website recently. That doesn't sound especially professional to me. It sounds like a joke actually. Especially when there are no other known issues listed! (https://inkscape.org/en/release/0.48/?latest=1) If it's supposed to be some kind of motivation to upgrade, I think there probably is a more professional way to do it. I mean, it's not even a release note, since 0.91 was not made when 0.48.x was released. For goodness sakes! But I really think it should be removed. Or at the very least, re-worded. Is there some reason for that, which I haven't imagined yet? All best, brynn PS - I'd offer to delete them, except I don't appear to have access to those pages. Also, the about screen is not showing on the download pages for versions earlier than 0.48.5. Shall I make an Issue report? Or is someone currently working on it?

3 3

Download page inkscape, please sort by system
by the Adib 19 Aug '17

19 Aug '17

Hello web team, I wanted to update my system and was a bit confused which download to use. I propose to group alphabetically or by system instead of upload time. HTH, Adib. --

7 22

Measure line LPE improvemets
by Jabier Arraiza 19 Aug '17

19 Aug '17

Hi all. Following a CR conversation about "Measure Line LPE" and the unmanegable/slow to add a LPE for each segment. I do a mayor update to it. ALso rename it to "Measure Segments LPE" The previous LPE is not abailable now, so convert to paths previous works with it before update to trunk, sorry. Features: When apply to a path (can have subpaths) the full path is meassured. You can remove or add a partial segment measure by a blaclist/whitelist implemented. Before you can add another LPE to fill the removed segments with diferent params measuraments. By this way i do also a method to not cross measures with angle greater than "Fix Crossings º" parameter. I hope now is much more easy to use. Best regards, Jabier.

2 2

CMS on Windows, and a few more thing...
by Miguel Lopez 17 Aug '17

17 Aug '17

It doesn't seem to work, or I'm not sure how to get it right, but I'm sure you put .icc profile under new folder in Inkscape directory under share/color/icc, and Inkscape should be able to detect them, but from my end, it does not seem to work. Also, would it be possible to hide tabs in the color sections, and force Inkscape to stick with CMS? Is there some limitations to CMS that I'm not aware of? Does filters offset color informations? This is one feature I have never saw the use until recently. Thanks, Miguel Lopez

1 0

Inkscape Vectors Meeting - This Friday!
by Ryan Gorley 17 Aug '17

17 Aug '17

This month Vectors meeting will be hosting our first official meeting (see agenda <https://gitlab.com/inkscape/inkscape-vectors/admin/issues/1>)! There's a lot of need for diverse talents so please join us: * Friday, August 18, 18:00 GMT (14:00 EST) * https://teams.freecreatives.org/inkscape We look forward to meeting you and getting your input. :) Ryan @ Dijt <https://dijt.co>

1 0

What the hell happened to the git repo ?!?!?
by Felipe Sanches 16 Aug '17

16 Aug '17

https://gitlab.com/inkscape/inkscape

4 5

Fw: Version 0.92.2 seems infected by malware
by brynn 15 Aug '17

15 Aug '17

I received this below through Inkscape Community contact form (another person who could not figure out how to contact the website). I'll inform the sender of your reply (replies). All best, brynn -----Original Message----- From: johan_frederik@...1523... Sent: Tuesday, August 15, 2017 5:26 AM To: admin@...3472... Subject: Version 0.92.2 seems infected by malware Contact Page Form for Inkscape Community Name: Fred Schouten Email: johan_frederik@...1523... IP: 82.95.66.107 Message: Downloading en subsequently testing the download shows that libicudt58.dll is infected with malware. At least 10 engines at TotalVirus find a positive at the moment of testing (aug 15 2017). This is not the case with version 0.92.1.

2 2

inkscape root dir tidying thoughts
by Bryce Harrington 15 Aug '17

15 Aug '17

With the cmake and git conversions complete, and autotools and bzr bits removed, I am wondering if there's some additional cleanup of stuff accumulated in our repository's root directory. But much of this I'm not 100% sure about (and that maybe why others haven't already dealt with it). ------------------------------------------------------------------------ + distro + libgc.supp + tools-version.sh I think these may be obsolete. They've been in the codebase forever, but I don't know what they are used for anymore. I'm guessing they're autotools leftovers; can we drop them? ------------------------------------------------------------------------ + inkscape.ico + inkscape.png The share/icons/application/ directory is the formal place for our icons, with share/branding/ the official source for branding files. Only the windows packaging refers to inkscape.ico. So I think this could be moved to packaging/. Or perhaps windows could be changed to use the .png files like everything else? Doxyfile seems to reference inkscape.png but I believe it could as easily use one of the icons in share/icons/application/, but see below... ------------------------------------------------------------------------ + Doxyfile This doxygen config file works fine (just ran it). However according to http://wiki.inkscape.org/wiki/index.php/Doxygen_documentation we aren't posting doxygen pages online any more. In any case, doxygen lets you pass the config file name on its command line, so no reason this has to live in the root directory. Unless anyone has strong feelings otherwise I propose moving this file to doc/ with our other code/architecture docs. Or... other ideas? ------------------------------------------------------------------------ + inkscape.spec.in This is an old RPM build file I made way way back. I'm sure Fedora has something better, and besides this is _completely_ out of date. I will be deleting it. ------------------------------------------------------------------------ + inkscape.desktop.in + inkscape.desktop.template Is inkscape.desktop.in generated from inkscape.desktop.template? Do we need both files? ------------------------------------------------------------------------ + mingwenv.bat + mingwenv.cmake + msys2checkdeps.py + msys2installdeps.sh + msysenv.sh + inkscape.appdata.xml.in + Info.plist.in + appveyor.sh + appveyor.yml + .gitlab-ci.yml + .snapcraft.yaml + packaging/ I know a lot of tools expect config files in the project's root directory, but can any of these be moved to packaging/? (Or maybe a utils/ dir?) Several of these have description snippets that are essentially the first few paragraphs of the README. If the README is revised (see below), it may be worthwhile to resync the text in these from that. ------------------------------------------------------------------------ + download-gtest.sh This still seems necessary for setting up gtest (although current trunk breaks on configure due to lack of a "Findgtest.cmake"; but that seems unrelated). Having to use this script has always seemed a bit hacky to me. (and it's downloading gtest 1.7, but 1.8 is current). I know there's been some good work done on improving our testing cmake rules, I wonder if there is a way we can eliminate this script? ------------------------------------------------------------------------ + testfiles/ Speaking of tests... Is there a reason why we call this directory testfiles/ rather than a more traditional name like 'test/' or 'tests/'? ------------------------------------------------------------------------ + INSTALL The installation directions here are for autotools so the whole file is obsolete. I only hesistate to delete it because I believe `make distcheck` requires it. So question here is should we move the installation directions currently in the README.md file to INSTALL? ------------------------------------------------------------------------ + README.md + README.ca.txt + README.de.txt + README.es.txt + README.fr.txt + README.it.txt + README.pt_BR.txt + README.sk.txt + README.sr.txt Speaking of the README, we've had these translations of the README for a long, long time. Most have not been updated to reflect the autotools -> cmake move, some haven't been updated in a decade. None have followed the main README's reformatting to markdown. But I wonder if translations of the README are that necessary? If not, would anyone be troubled if we dropped them at this point? Aside from the installation directions (which are out of date anyway, and maybe should move to INSTALL), the information in the README is just introductory stuff that exists in translated form on our website and elsewhere so The first section of the README we have used far and wide all over the place. It's a stock text we cut and paste into anything that needs a description of our project. But it's been pointed out to me that this doesn't really reflect the current state of Inkscape and all the stuff that's been achieved since it was written. So, we may want to consider revising this. Does anyone know of a more current description of Inkscape that we could leverage for this? ------------------------------------------------------------------------ + inkscape.pod + inkscape.de.pod + inkscape.el.pod + inkscape.fr.pod + inkscape.ja.pod + inkscape.sk.pod + inkscape.zh_TW.pod + inkview.1.in + man/ Unlike the README's, the translated man pages have been getting updates. The --no-convert-text-baseline-spacing option is only documented in the English inkscape.pod, but the previously added option, --export-ps-level, (from 2013) is present in all. However, these should move down into the man directory. The CMake code is already in CMakeLists.txt to generate the .pod files from the man/ directory, so recent changes to the root *.pod's just need to be sync'd with the corresponding files in man/ and then removed. As an aside, I know we eliminated Perl from the build system, but it's still used for the man page generation (the 'p' in pod stands for perl). I like the POD format, but raw man page syntax (TROFF) isn't *that* complicated; if we wanted, we could just keep all the man pages as troff, eliminate pod usage, and simplify our build requirements. (Compare inkview.1.in with man/inkview.pod.in to see the difference). Would anyone be opposed (or favorable) to this change? ------------------------------------------------------------------------ + fix-roff-punct + utf8-to-roff These perl scripts were used to fix up punctuation goofs by pod2man. If we moved away from POD, then these are entirely superfluous and can be dropped. -------------- + COPYING + GPL2.txt + GPL3.txt + LGPL2.1.txt Next, licenses... As detailed in the COPYING file, the only reason we have GPL3.txt is because there's a few files in our tree copied from GIMP. Could someone please take the task of eliminating those files, so Inkscape can return to being pure GPL2? The LGPL2.1 isn't a problem, but according to COPYING it's only there due to some libs we copied into the tree (I see libavoid is LGPL, is there anything else?) If the LGPL libs were changed to be external dependencies instead of copied into src, we could eliminate the LGPL2.1.txt file too. ------------------------------------------------------------------------ + CMakeLists.txt + CMakeScripts/ + cmake_uninstall.cmake.in + config.h.cmake CMake is nice and concise compared to autotools. I do wonder if cmake_uninstall.cmake.in could perhaps be moved into CMakeScripts/. If anyone else wants to move it, please do, else I'll look into it some time. ------------------------------------------------------------------------ + astylerc This config file appears to be for a code formatting tool. I vaguely remember kk discussing it a while back. Is anyone still using it? The astyle man page indicates it supports using --options=FILENAME to specify a path to astylerc, so the file could be moved to utils/ or elsewhere. I see we already have the options documented at https://inkscape.org/en/develop/coding-style/ including directions for how to store the settings locally in ~/.astylerc. If no one is actively using this tool, that might be a better solution and remove astylerc from the codebase. ------------------------------------------------------------------------ + _clang-format I'm not sure why this is in the tree. Guessing it was a jenkins-related thing? I suspect we can drop this. ------------------------------------------------------------------------ + setup/ This appears to be current, but what is it? It has a single subdir with a single file, which looks like a copy of inkscape.desktop.in with translations embedded. Why is this in a directory called 'setup'? ------------------------------------------------------------------------ + ChangeLog With the newest entry in this file being from 2014, this looks vestigal. I think it used to be needed for packaging, and I think it dates to pre-bzr. Anyone know if there's a reason to keep it? ------------------------------------------------------------------------ + AUTHORS + TRANSLATORS + NEWS + doc/ + share/ + src/ + po/ This is all pretty stock, no comment here. Bryce P.S. if you've read to this far, thanks! This ended up way longer than I anticipated, sorry!

13 35

Correct download URL for source ?
by Ken Moffat 13 Aug '17

13 Aug '17

When I downloaded 0.92.2 using firefox, I thought that the link was to https://inkscape.org/en/release/0.92.2/source/archive/dl/bz2/ (but I might have misread the tiny text), and presumably it had inkscape-0.92.2.tar.bz2 on the end of it. But now that I try to go there directly I get inkscape's Page Not Found, and using that to search for inkscape-0.92.2.tar.bz2 fails. I see that Arch seem to be using https://media.inkscape.org/dl/resources/file/inkscape-0.92.2.tar.bz2 but that too fails for me with 404, or 403 for the directories above that. So, please, where should I point people to so that they can download it with a browser or wget ? ĸen -- I live in a city. I know sparrows from starlings. After that everything is a duck as far as I'm concerned. -- Monstrous Regiment

2 2

Rerun Cakke
by Jabier Arraiza 12 Aug '17

12 Aug '17

Hi all. Please I just push a minor improvement and if you have compiling isues with a icon, please re-run cmake. (not need to remove cache cmake file). Sorry for the inconveniences, Jabier.

1 0

Icon names
by Alex Valavanis 12 Aug '17

12 Aug '17

Hi Tav, Is there any chance you could use your icon-extracting Perl script to generate a list of Inkscape's icon-name strings? It would be good to put a table of names/descriptions on the Wiki to help people develop custom icon themes. AV

2 1

Download Page Redirect Issue?
by Ryan Gorley 11 Aug '17

11 Aug '17

Can someone confirm that they're having similar behaviors: When I visit inkscape.org I am properly assigned my language (/en/), when I hover over the download link it shows the proper URL (https://inkscape.org/en/release/), but when I click the link I am redirected to the French language version of the page (https://inkscape.org/fr/release/0.92.2/). I've tested in three browsers, it's not a local caching issue as far as I can tell. Seems like a serverside page caching issue to me, or maybe a simple redirect typo. Just want to see if I'm the only one.

6 7

Can not open .eps files
by Marc Alexander Gross 11 Aug '17

11 Aug '17

Hi, I installed today Inkscape. Unfortunately I could not open any .eps files. Neither if I open a jpg and translate it into EPS and safe it in EPS formate. Please could you help me out, to solve this problem? Regards Marc

3 5

Please update 0.93 release notes
by Bryce Harrington 11 Aug '17

11 Aug '17

Everyone working on trunk, please take a few minutes to jot down what you've been working on: http://wiki.inkscape.org/wiki/index.php/Release_notes/0.93 Also, if there's changes others have done that you're aware of, please add those too. Even placeholder text would help indicate where further fleshing out is needed. Thanks, Bryce

1 0

Fwd: Re: Debian 8 compatibility falling apart after one month of Debian 9
by Michael Soegtrop 11 Aug '17

11 Aug '17

Dear Eduard, dear Inkscape Team > If this version matches the actual requirement unexpected build failures > like Michael was experiencing should be impossible as cmake would > already warn at the configure stage. I would think that CMake allows newer versions than the specified one, unless explicitly told otherwise. The issue here is that some GTK 3.16 are actually used although only GTK 3.8 features should be used (as far as I understood). I have some experience with creating build systems which use specific package versions based on Cygwin. Since there is a working MSys build, it shouldn't be difficult to build with specific package versions - one just has to create a local cygwin or MSys package repository, which keeps these specific versions and tell the Cygwin/MSys installer to use that one. The Cygwin installer creates a suitable repository as a cache automatically. Not sure how this works with MSys, but I guess it has similar features. The main issue here might be to get the versions mentioned in the Wiki. One might have to build them from scratch. If someone has a years old cache folder of Cygwin or MSys with all the old package versions, please put is somewhere. It would make sense to run two builds, one with the latest packages and one with an archived set of packages. Best regards, Michael .

6 16

Organic Funding
by Martin Owens 10 Aug '17

10 Aug '17

Dear developers, We've just concluded our board meeting and one of the issues was funding. We're kicking around an idea of allowing some developers to use the service Patreon (http://patreon.com/) to collect subscriptions to fund their Inkscape development. This system of funding would be quite different from either a centralised funding model or the status quo of non-user involvement. These are some very raw thoughts for considering and I'd love to get more feedback from the wider developer community: * Developers would be allowed to create a Patreon page which describes their work on Inkscape. * Each developer would be shaping their focuses and would be responsible to keeping their Patreon pages up to date. * Developers may only define themselves as Inkscape developers on patreon if: . + They are Inkscape developers (in the list of devs) . + Are considered active in the project. . + Present Inkscape in a good light on their pages. . + Have asked for permission from the developers list. * Developers would be removed from the scheme by the developers if . + They are not active in the project for 2 months . + Are involved in an conduct infraction which gets them removed from the project. * People claiming to be Inkscape developers without permission will be considered to be using the Inkscape trademark inappropriately. (must check legal with Conservancy to make sure this is true) * The Inkscape general fund continues to be the donation headline, money going towards hackfests and other resources for the project. * The project would do periodic funding drives to improve donations and subscriptions to our patreon developers. Using social media and news announcements to improve funding. * Contributors to patreon developers would NOT receive sponsorship rewards from Inkscape (i.e. sponsorship levels on the website). * Patreon developers would continue to get sponsorship for hackfest expenses much like any other developer would. == Status == We have two developers who are prepared to trial such a system. Tav and Mc (Marc), both attended the hackfest, both have worked on Inkscape intensively for quite a while. I want to see if it's possible try and get a trial set up quickly. Mc will leave education in 2 months and must decide to continue developing Inkscape or move on to full time employment. Best Regards, Martin Owens

10 20

Thanks making 0.92.2 happen
by Ryan Gorley 10 Aug '17

10 Aug '17

The new release is available for download on the slick new release page <https://inkscape.org/en/release/0.92.2/>, the announcement <https://inkscape.org/en/news/2017/08/07/inkscape-0-92-2-release-announcemen…> is up, and we're in the midst of letting the world know <https://gitlab.com/inkscape/inkscape-vectors/press/issues/1>. From my vantage point it was really awesome to see /many/ of you step up to pull this all together--often during busy schedules and into the early mornings. I just wanted to say wow, and thank you! -- Ryan Gorley // Dijt <https://dijt.co> // Managing Partner

4 4

Inkscape .deb package
by Bryce Harrington 09 Aug '17

09 Aug '17

Our PPA to do autobuilds of releases broke with the switch from bzr to git; I tried coaxing it back to life but no go so far. Is anyone familiar with creating .deb packages, and available right now to help build a regular .deb package of Inkscape? If so, catch me on IRC. Bryce On Wed, Aug 02, 2017 at 08:08:35PM -0700, Bryce Harrington wrote: > == Release Meeting == > > Following the board meeting, 1pm Pacific time Friday, will be an > opportunity to review status ahead of the release this weekend. This > meeting will be held on #inkscape-devel. Everyone's welcome to attend, > but particularly people who have been testing or developing the release > candidate to gather feedback on any remaining issues. I'd also love to > see members of the new Vectors team to discuss announcement plans. > > Agenda: > * QA status / issues > * Translation team status > * Vector team status > * Web team status > * Release team status > * Final Go/No-go on release > * Other business > > There was also a question recently about policies for versions of > dependencies (i.e. what do we target for LTS). Time permitting we could > discuss this a bit as well. > > Thanks, > Bryce > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel

2 3