- Inkscape Devel - Inkscape Mailman

Re: [Inkscape-devel] RFC: stroke-alignment property for SVG and Inkscape
by Alexey Murz Korepov 21 Sep '18

21 Sep '18

2015-08-26 12:16 GMT+02:00 Tavmjong Bah <tavmjong@...360...>: > Just to bring others up-to-date. We discussed 'stroke-alignment' > yesterday at the SVG WG meeting (conveniently located in Paris). The > feeling was that the initial allowed values should be 'left' and > 'right' as it is easy to define how these values work for paths that > contain overlapping loops. The values 'inset' and 'outset' are more > complicated and require finding path intersections, something that the > browsers don't need to do (yet) for any other purpose. In https://www.w3.org/TR/svg-strokes/#issue5 described an issue: > How does this apply to open path segments? How are end caps handled? Adobe Illustrator applies stroke alignment property only for closed paths, if path becomes open - Illustrator immediately removes this property and applying center alignment. Can we standardize same behavior in Inkscape for solve this issue? -- Best regards, Alexey Murz Korepov. Email, Jabber: murznn@...400...

1 0

Inkscape Hackfest Summary - How do I make a new article on the Inkscape website?
by C R 20 Sep '18

20 Sep '18

Never done this before... Is there a way to publish markdown and pictures to a news story on the website? I can then link to it in a G+ press release. Thanks. :) -C

6 7

One of the moderators on our Inkscape G+ feed is blocking comments and slinging insults
by C R 20 Sep '18

20 Sep '18

imho, they should not be in charge of moderating the Inkscape's g+ feed. The name of this moderator is Grady Broyles. They have: 1. Falsely asserted that pngs are lossy. (not good for the project) 2. Falsely asserted that pngs are locked at 96dpi (just plain wrong, esp for those wanting to print their pngs) 3. Abused their moderator status by blocking arguments proving his statements incorrect. 4. Engaged in personal attacks. imho, this person is not fit to moderate the Inkscape G+ feed. Thanks for your attention to this matter. :) Here is a screenshot of the above: https://imgur.com/a/2ToD1VT This was in response to my comment (which did not fit in the screencapture): +Grady Broyles <https://plus.google.com/117132892207917418648> I've been exporting pngs from Inkscape at 600dpi A4 for the last 7 years... what on earth makes you think it is locked at 96 dpi? -C

9 24

Re: [Inkscape-devel] One of the moderators on our Inkscape G+ feed is blocking comments and slinging insults
by Ryan Gorley 19 Sep '18

19 Sep '18

Thanks, Josh! I can't give you great details because I don't have access to the tools, but this article seems to detail it alright: https://support.google.com/plus/answer/6320413?co=GENIE.Platform%3DDesktop&… Ryan On 9/19/18 12:52 PM, Josh Andler wrote: > Wow G+ is super confusing these days. Yeah, I see I'm an Owner as with > C R and Ryan, but I literally don't see that I really have permissions > for anything. I'm happy to help if someone can help point me > further... btw, thanks for mentioning the separation of brand account > stuff Ryan. > > On Wed, Sep 19, 2018 at 11:46 AM C R <cajhne@...400... > <mailto:cajhne@...400...>> wrote: > > I did kinda stick it to him in an indirect way... It gets under my > skin when people proclaim things like "I've been doing this for XX > years, so do your homework before questioning mah authoritah!" > For reference, I sent him this as a reply (600pdi A4 png): > https://imgur.com/a/yVMsuJE > > And suggested he could print it and put it on his wall to keep him > from holding the same misconceptions about png for another 30 years. > > IMHO, moderators should be engaging in useful and helpful > conversation, not waving around their years of experience and > proclaiming lordship of all things graphics (and calling people > who disagree less intelligent). > https://imgur.com/a/yVMsuJE > > Yes, I probably could have been nicer, but, well, this is why I'm > not a moderator. ;) > > Our mods should be nicer than me. :) > -C > > > > > On Wed, Sep 19, 2018 at 7:32 PM C R <cajhne@...400... > <mailto:cajhne@...400...>> wrote: > > Awesome, thanks. > -C > > On Wed, Sep 19, 2018 at 6:39 PM Ryan Gorley <ryan@...3676... > <mailto:ryan@...3676...>> wrote: > > So you should have ownership of the Inkscape Brand > Account, but this exists separately from the Inkscape > Community page (thank Google for making this confusing). > When you get on G+ you can change your account at the very > top right to use G+ as Inkscape. You can then post on the > community page as Inkscape (the brand). > > I don't actually have any permissions on the community. > Josh Andler (ScislaC) does. Josh, you able to help out > with that? > > I'll engage with Grady about this now too. > > > Ryan > > On 9/19/18 11:26 AM, C R wrote: >> Can you unblock me in the meantime? Also, how do I get >> access to the G+ feed? >> I need to post the hackfest summary tonight. >> >> Thanks. >> -C >> >> On Wed, Sep 19, 2018 at 6:09 PM Ryan Gorley via >> Inkscape-devel <inkscape-devel(a)lists.sourceforge.net >> <mailto:inkscape-devel@lists.sourceforge.net>> wrote: >> >> I agree that it's not appropriate for him to block >> you from posting, and some of these other items need >> to be addressed. Grady is a passionate man, like all >> of us he can get defensive about items, but his >> intentions are good. I think we should let this cool >> down for a couple days and I'm willing to discuss >> this matter with him directly. >> >> >> Ryan >> >> On 9/19/18 10:45 AM, C R wrote: >>> Seems they have blocked me entirely from posting. >>> Yea, that's not cool. :) >>> >>> -C >>> >>> On Wed, Sep 19, 2018 at 5:31 PM C R >>> <cajhne@...400... <mailto:cajhne@...400...>> wrote: >>> >>> imho, they should not be in charge of moderating >>> the Inkscape's g+ feed. >>> >>> The name of this moderator is Grady Broyles. >>> >>> They have: >>> >>> 1. Falsely asserted that pngs are lossy. (not >>> good for the project) >>> 2. Falsely asserted that pngs are locked at >>> 96dpi (just plain wrong, esp for those wanting >>> to print their pngs) >>> 3. Abused their moderator status by blocking >>> arguments proving his statements incorrect. >>> 4. Engaged in personal attacks. >>> >>> imho, this person is not fit to moderate the >>> Inkscape G+ feed. >>> >>> Thanks for your attention to this matter. :) >>> >>> Here is a screenshot of the above: >>> https://imgur.com/a/2ToD1VT >>> >>> This was in response to my comment (which did >>> not fit in the screencapture): >>> +Grady Broyles >>> <https://plus.google.com/117132892207917418648>I've >>> been exporting pngs from Inkscape at 600dpi A4 >>> for the last 7 years... what on earth makes you >>> think it is locked at 96 dpi? >>> >>> -C >>> >>> >>> >>> _______________________________________________ >>> Inkscape-devel mailing list >>> Inkscape-devel(a)lists.sourceforge.net <mailto:Inkscape-devel@lists.sourceforge.net> >>> https://lists.sourceforge.net/lists/listinfo/inkscape-devel >> _______________________________________________ >> Inkscape-devel mailing list >> Inkscape-devel(a)lists.sourceforge.net >> <mailto:Inkscape-devel@lists.sourceforge.net> >> https://lists.sourceforge.net/lists/listinfo/inkscape-devel >> > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net > <mailto:Inkscape-devel@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/inkscape-devel >

1 0

Regressions Tracker
by unknown＠example.com 19 Sep '18

19 Sep '18

Dear developers, One of the discussions we had in Kiel was the potential to host a tracker to document some of the regressions that we have on GitLab. While we're keeping the inkscape issues tracker closed for now, I've created a project to hold the regressions for 1.0. These are mostly for programmers to document errors and talk between ourselves about possible solutions, rather than end user issues. https://gitlab.com/inkscape/regressions I don't think this'll interfere with anything, but let me know if it opens too many problems and I'll close it down. Best Regards, Martin Owens

3 9

Rocket.Chat / chat.inkscape.org
by Bryce Harrington 19 Sep '18

19 Sep '18

Hi all, The Vectors team, after experimenting with a number of different online discussion tools, has selected Rocket.Chat as the best option for their team's discussions. Thanks to hard work by new Inkscaper Manuel Recena, this is up and running in Inkscape's official hosting, and is just about ready for use. While this is specifically set up at the request of the Vectors team, other teams are welcome to use it too if they wish. The #inkscape and #inkscape-devel freenode IRC channels will continue to be our primary discussion channels, no changes are planned for that. There are a few decisions that still need to be made on how Rocket.Chat is configured and used. We figured these questions deserve broader discussion, so are bringing them here. Ryan, could you reply on this thread with what decisions need to be made? Bryce

4 5

PIGLATIN
by Jabier Arraiza 19 Sep '18

19 Sep '18

Why this name in source code :((( /inkscape/po/en_US@...2278... This bring me very sad. Think about no more commits with this welcome.

4 4

Cusp corner cap even with rounded corners active (stroke)
by Maren Hachmann 12 Sep '18

12 Sep '18

Jabier asked me to share this file via mailing list. The shape in it has a stroke with round caps. Only one corner looks as if it has another type of cap. The cap type depends upon the size of the path. When you make it larger, it starts to look as expected. In Firefox it looks as expected at any size. (Hackfest bug reported by Robert who is visiting us and uses Inkscape for teaching students about building technology) Maren

2 2

License header cleanup: Need feedback
by Maximilian Gaukler 11 Sep '18

11 Sep '18

Hi everyone, I spent the last two days cleaning up license headers. If someone has the time, I would be happy to hear feedback about this merge request: https://gitlab.com/inkscape/inkscape/merge_requests/327 Regards, Max

1 0

Inkscape source license clarification
by Maximilian Gaukler 10 Sep '18

10 Sep '18

Dear Dmitry, ./src/main-cmdlinexact.cpp and ./src/main-cmdlinexact.h are licensed as GPL-v2.x-only. This is a problem because inkscape has implicitly switched to GPLv3 by including widget code from GIMP. Is it okay to relicense your code to "GPLv2 or any later version"? Otherwise I fear that someone would have to rewrite or remove it. Greetings from the Kiel Hackfest, Max

1 0