June 2017 - Inkscape Devel - Inkscape Mailman

gcode tools support lacking
by brynn 06 Jun '17

06 Jun '17

Hi Friends, It's been well over a year since the team who created Inkscape's gcode tools, have answered requests for support in their forum, cnc-club (see link in Extensions menu > Gcodetools > About). There currently are not any users who participate in forums, who understand these tools who are apparently interested in helping. Is there anyone in the community who would be willing to be contacted (in lieu of regularly visiting forums) with questions about the gcode tools, when they come up (which is more and more lately)? Or does anyone know of any resources, such as tutorials? I only know of one...oh great, and I guess I've misplaced the link. But it's fairly limited. (I've even offered to write tutorials for the gcode tools, if the cnc-club forum would collaborate - no answer.) Personally, if the community can't provide support for our own tools, well.... I guess I'd have to start refering users elsewhere, for producing the gcode. Some have already started referring elsewhere (http://www.inkscapeforum.com/viewtopic.php?f=31&t=32491) Of course I don't want to do that. But this is a frustrating. Can the development community provide any guidance? Thank you very much, brynn

2 4

Fwd: Re: Fwd: Re: last used style #2
by C R 06 Jun '17

06 Jun '17

Sorry, sent this directly to brynn by mistake. Forwarding to the list, read below. ---------- Forwarded message ---------- From: "C R" <cajhne@...400...> Date: 6 Jun 2017 1:15 p.m. Subject: Re: [Inkscape-devel] Fwd: Re: last used style #2 To: "brynn" <brynn@...3133...> Cc: > The workflow is draw first, style second. (Personally I like that > routine much better than choosing the style first. So when you're making > changes, please make it optional, so that those who prefer the "old" way, > can continue without altering their personal routines.) The new way will not affect the old way of doing it if you like that better. The idea is that the user should be able, at any point to select a fill and stroke, and have the next thing drawn be that colour. This will not change if you want to select a different colour after you draw - newly drawn/selected items will still be filled with the colours chosen by the user for stroke and fill after they are drawn.selected in the same manner as it does now. The changes add the ability to use the Lower-Left stroke and fill widget as a master widget for colour, so you don't have to set the fill/stroke colour in the tool dialog (upper-left) - which most users seem to miss anyway. One colour widget to rule them all, one to find them, one to bring them all, and in the Inkscape bind them. -C > > So draw a rectangle. Yikes, nothing's there. I can see the dotted > lines and arrows (i.e. bounding box and selection handles), but my rectangle > isn't there. Yes, this is why it's nice to set the draw colour/fill before the rectangle is drawn. > Why isn't it there? Because the last time you drew a rectangle, > eventually you made it completely transparent. Now, every rectangle you > draw will be transparent, until you change it. Oh, you changed it to blue? > Now every rectangle will be blue, until you change one. If the user has chosen to draw blue rectangles, reverting to some other default colour doesn't make a lot of sense. In most drawing programs, the "current colour" (the one shown in the colour widget) is what the drawn shape will be. I draw a line - I make it red. I draw another line... but it's reverted back to the default line colour... I'm wanting to draw red lines, that's why I went through the trouble of changing the colour. I have to change it every single time = big big waste of time. To get around this, as others have noted, the workflow is draw a bunch of lines, select them all, then paste style. Yea... it's not great. It's what people are complaining about. This is why it's simpler to have one widget to control colour. Currently the user has to look all over to see where to change the default colour, and are baffled when the colour changes back to the default colour when they draw a new shape. > As I said before, it's easily the most asked question, both in forums > and LP Answers. And in my opinion, well, a ridiculous feature. Simplifying the interface into a single colour widget will help, also if the user changes things outside this colour widget, new objects should not retain the transparency settings. - This more than anything causes confusion. A distinction needs to be made between object transparency and fill alpha colour. Object transparency, controlled by the slider in the stroke/fill dialog should not affect the current colour (and thus not the affect the colour/transparency of newly drawn items). - This, more often than not is what causes completely invisible objects, and it's a pain for the user to try and figure out which settings are causing the object to be transparent. It's a difficult problem, but with your help, I'm sure we can come up with a solution that works better for everyone. > Most > newbies pick up Inkscape, and they're happily clicking away, not thinking > about anything, but marvelling over the awesome program. An hour later, or > a day, or a week, and they don't remember that they were playing with either > the alpha channel or Opacity slider. And also in my opinion, it's not > intuitive that whatever change I make is permanent for the tool. Yes exactly. This is part of what I'm working on remedying. We are on the same page here. > What's the solution? Explain to everyone how to change the style > settings for all their tools. This implies there is some means of forcing people to read tutorials. The "happily clicking away" thing is what needs to continue. The tool configuration landmines are what need to be replaced - an easy way to do that is to re-think how transparency and colour are applied, and provide a more intuitive and simpler interface that doesn't have vanishing bits. I believe we collectively can do this without adding a bottleneck to anyones workflow, and removing the substantial ones that we all have just gotten used to living with because that's how it's always been. :) > Anyway, I'm rather shocked that the mailing list crowd doesn't > understand what the problem is. I guess it underscores once again how far > removed many developers are, from the user community. Many people in this thread use Inkscape professionally, myself included (every working day, for a professional portfolio you wouldn't even believe was made in FLOSS). So let's not go the us vs. them route. There is no "them", only us. Let's try and find a solution that works for everyone. > Would it be such a hard thing to do, to make the default doc have all > the tools set for "own style"? I think for some tools this makes sense, but only if "own style" is replaced by "last used" style for that tool. If I am adding text to a doc, I don't want to have to change the colour from some default value every time I add more text. If I'm drawing shapes, I expect that Inkscape will preserve the colour I've chosen, not change it back to some default value until I tell it to change the colour. If I'm drawing lines, I'd like the same as for shapes, though often the fill gets in the way. It's not that big a deal to change the fill to transparent, but maybe a good solution is to change the fill to none by default, then add fill colour if the line becomes a closed shape. This is not a simple problem, and understanding all the implications is half the battle. Let's continue to work on it together. -C > Thanks again, > brynn > > -----Original Message----- From: C R > Sent: Sunday, June 04, 2017 2:12 PM > To: brynn > Cc: Inkscape-Devel ; J. F. Lemaire ; Martin Owens ; Olof Bjarnason > Subject: Re: [Inkscape-devel] Fwd: Re: last used style #2 > > > Hi brynn. I think maybe we were confused about what you wanted. Sorry > we guessed wrong. On the plus side, it opened up discussion of the > tools, and how styles are used/reused, and it seems no one likes how > it currently is very much - Which is why I'm making mockups of how it > could work. I'll try and do a video showing the steps for each option. > > It's taking a lot of thought, and consideration of different > workflows, because the tools and how they function differ, so coming > up with a unified solution that makes everyone happy will take a bit > of time. > > Can you advise in particular the workflow you are using - I think we > would benefit from an example or two. I'll try to get in touch with > you on irc this week to discuss it so we properly address your > problem. > > Thanks for your patience! > -C > > > On Sun, Jun 4, 2017 at 6:45 AM, brynn <brynn@...3133...> wrote: >> >> Hi Everyone, >> Sorry to have made that post just before I logged off for a day and >> a >> half. Aside from being a little afraid of what the response might be, I >> honestly didn't expect much response! >> >> Also honestly, I was totally lost with most of the discussion. And >> some of it, I can't even make a connection to what I asked. It's almost >> like my comment about holding onto something for 10 years, prompted >> everyone >> else to comment what they've been holding onto for years. But I don't >> think >> it ever came back around to my question. >> >> Moving the tool style indicator, or the selected object indicator, >> or >> when Fill and Stroke is called up, or setting style before/after, etc., >> (if >> I followed it all)..... Yikes, I'm totally lost! >> >> Changing whether we can set the style before or after drawing the >> object won't solve the problem I'm having. Not unless you somehow make it >> impossible to draw first and choose style second. And then you'll have >> complaints from all the "old" users who have it in their workflow to draw >> first, style second. >> >> I'll try to keep up with whatever mockups you come up with, and >> offer >> comments. >> >> But if I can just reiterate my original request (which doesn't >> require a ui change afaik). Please, can we make all the tools set for >> "This >> tool's own style" as the default? I don't mean take away "Last Used >> Style" >> as an option (well, I was joking when I mentioned it). I just mean, for >> the >> default document (which is what newbies use 99% of the time) can it start >> with everything set for "...Own Style"? >> >> It would not require current users, who might be using "last >> style", >> to go through and change everything, because their prefs file will keep >> them >> using whatever they already use. This would ONLY affect newbies, and make >> them less confused (and those of us who answer support requests, less >> bothered!) >> >> Not that I know much about programming. But what little I >> understand >> about how Inkscape works, it seems like it wouldn't take much time to make >> this change. Wouldn't it be just changing one thing, for each tool, in >> the >> default doc? Or maybe it's a change in the original prefs file? >> >> Since I didn't hear any objections - not to what I asked anyway, I >> guess I will make the feature request. >> >> Thanks again, >> brynn >> >> PS - (Re-titled this, in case of comments on my original request.) >> >> >> -----Original Message----- From: Martin Owens >> Sent: Friday, June 02, 2017 7:51 AM >> To: Olof Bjarnason ; C R >> Cc: J. F. Lemaire ; inkscape-devel >> Subject: Re: [Inkscape-devel] Fwd: Re: last used style >> >> On Fri, 2017-06-02 at 11:01 +0200, Olof Bjarnason wrote: >>> >>> >>> Just trying to make this happen, and it won't happen if you do not >>> get buy in from some developer that has the time and energy to make >>> this happen... >> >> >> >> This kind of UX is right in my wheelhouse. Please add me as principle >> developer to work on the design. To which we can then test functionally >> with users. >> >> Best regards, Martin Owens >> >> >> ------------------------------------------------------------ ------------------ >> 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 1

Alternative glyphs
by Tavmjong Bah 06 Jun '17

06 Jun '17

Hi, Many fonts have alternative glyphs for some unicode codepoints. These glyphs can be accessed by enabling OpenType tables such as 'salt', 'ss01', etc. Inkscape has supported using such alternative glyphs through the 'Variants' tab of the 'Text and Font' dialog (under the last section, 'Feature Settings'). But one problem that was pointed out is that it is difficult to know what alternative glyphs are available for a particular font. I've just added code in trunk that will display such alternative glyphs in the 'Feature Settings' section. The GUI leaves a bit to be desired and there is some more work to do to show all alternative glyphs properly (for example, font style is ignored) but it is a start. Please test it out and give me your feedback. Tav

3 7

chr[Hackfest]
by Christoph Rudorff 06 Jun '17

06 Jun '17

Hello Inkscape Community, I proposed at the irc board meeting my participation on the hack fest. I introduce myself as a dev and a user whose bug reports usually have a patch ready. I can do a talk "How we use inkscape to drive our CNC machine" and the gotchas that came up: http://chris.rudorff.com/Plotter/IMG_20170214_165918604.jpg This is a 1.4x10.5m vacuum desk with pen + laser tool. It cuts panels for sail making. It was build 1985 and survived more than computer system (WannaCry? WannaLaught!): http://chris.rudorff.com/Plotter/IMG_20170127_180750123.jpg So we hit the 1% zoom limit of inkscape ;) Beside the bugs I already fixed in inkscape I found more issues: memory leaks and performance eater. Top on my todo is the dxf importer. I hacked it for our needs but this extension can use a rewrite I can do. My travel is not that far but I can use some funding for staying/hotel/sofa. So I am looking forward meeting the people behind inkscape ;) chr[]

3 7

Re: [Inkscape-devel] [UX] A simple code that help
by Jabier Arraiza 06 Jun '17

06 Jun '17

Thanks Maren. I also add another feat at the same way: "hide selected objects" "unhide objects below" I hope i commit the code in half hour or less. Cheers, Jabier. On Tue, 2017-06-06 at 02:02 +0200, Maren Hachmann wrote: > Then for the strings I'd suggest: > - lock selected objects > - unlock objects below > > Maren > > Am 06.06.2017 um 01:51 schrieb Jabier Arraiza: > > Great!!! > > > > On Tue, 2017-06-06 at 01:47 +0200, Maren Hachmann wrote: > > > That sounds very useful to me, Jabier! > > > > > > Maren > > > > > > Am 06.06.2017 um 01:18 schrieb Jabier Arraiza: > > > > Yes. > > > > > > > > On Tue, 2017-06-06 at 00:34 +0200, Maren Hachmann wrote: > > > > > I still don't understand which items will be > > > > > unlocked+selected - > > > > > those > > > > > directly below the cursor, no matter how deep in the stack of > > > > > objects? > > > > > > > > > > Maren > > > > > > > > > > Am 05.06.2017 um 19:20 schrieb Jabier Arraiza: > > > > > > Seems a complex UI to me. To my workflow and easyest to > > > > > > undertand > > > > > > seems > > > > > > better unlook all selecting them in the same step, deselect > > > > > > the > > > > > > one > > > > > > you > > > > > > dont want locked and lock with right click all the others. > > > > > > Its > > > > > > like > > > > > > a > > > > > > natural action easy to remember, more than hidden feats. > > > > > > > > > > > > Cheers, Jabier. > > > > > > > > > > > > > > > > > > > > > > > > On Mon, 2017-06-05 at 17:40 +0100, C R wrote: > > > > > > > I see. Is it possible to just select all cursor locked > > > > > > > down > > > > > > > items, > > > > > > > and > > > > > > > then choose which ones to unlock? Or is that too much of > > > > > > > a > > > > > > > pain? > > > > > > > > > > > > > > -C > > > > > > > > > > > > > > On Mon, Jun 5, 2017 at 5:26 PM, Jabier Arraiza > > > > > > > <jabier.arraiz > > > > > > > a@...3326... > > > > > > > rker > > > > > > > .es> wrote: > > > > > > > > Cursor down locked items. > > > > > > > > > > > > > > > > On Mon, 2017-06-05 at 17:02 +0100, C R wrote: > > > > > > > > > Hey jabier. What are "down" items? > > > > > > > > > > > > > > > > > > Also, I just had an idea for unlocking: context > > > > > > > > > > Select > > > > > > > > > Locked, > > > > > > > > > which then > > > > > > > > > changes to context > Unlock Selected, which would let > > > > > > > > > users > > > > > > > > > deselect > > > > > > > > > items > > > > > > > > > they want to remain locked before unlocking. > > > > > > > > > > > > > > > > > > Thoughts? > > > > > > > > > > > > > > > > > > On 5 Jun 2017 4:56 p.m., "Jabier Arraiza" > > > > > > > > > <jabier.arraiza > > > > > > > > > @mar > > > > > > > > > ker. > > > > > > > > > es> > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > Realy the improvement is for unlock. Lock is by the > > > > > > > > > > way. > > > > > > > > > > > > > > > > > > > > Cheers, Jabier. > > > > > > > > > > > > > > > > > > > > On Mon, 2017-06-05 at 15:33 +0000, Miguel Lopez > > > > > > > > > > wrote: > > > > > > > > > > > I'll vote yes to the optional feature to come to > > > > > > > > > > > Inkscape! I > > > > > > > > > > > tend > > > > > > > > > > > to > > > > > > > > > > > manipulate objects within objects dialog (I don't > > > > > > > > > > > use > > > > > > > > > > > Layers > > > > > > > > > > > dialog > > > > > > > > > > > anymore because objects dialog, and I always > > > > > > > > > > > convert > > > > > > > > > > > group to > > > > > > > > > > > layers > > > > > > > > > > > in the final) for locking, but it wouldn't hurt > > > > > > > > > > > to > > > > > > > > > > > have a > > > > > > > > > > > extra > > > > > > > > > > > way > > > > > > > > > > > to lock. > > > > > > > > > > > > > > > > > > > > > > On 6/5/2017 11:13 AM, Jabier Arraiza wrote: > > > > > > > > > > > > > > > > > > > > > > Hi all. > > > > > > > > > > > > > > > > > > > > > > A thing easy to do: > > > > > > > > > > > Right click->context_menu:lock selected items. > > > > > > > > > > > Right click->context_menu:unlock down items. > > > > > > > > > > > > > > > > > > > > > > First one is optional. > > > > > > > > > > > > > > > > > > > > > > Want to add to Inkscape? Please let try to say > > > > > > > > > > > the > > > > > > > > > > > best 1 > > > > > > > > > > > or > > > > > > > > > > > 2 > > > > > > > > > > > strings > > > > > > > > > > > to the menu. > > > > > > > > > > > > > > > > > > > > > > Cheers, Jabier. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ----------------------------------------------- > > > > > > > > > > > ---- > > > > > > > > > > > ---- > > > > > > > > > > > ---- > > > > > > > > > > > ---- > > > > > > > > > > > ---- > > > > > > > > > > > ----------- > > > > > > > > > > > Check out the vibrant tech community on one of > > > > > > > > > > > the > > > > > > > > > > > world's > > > > > > > > > > > most > > > > > > > > > > > engaging tech sites, Slashdot.org! http://sdm.lin > > > > > > > > > > > k/sl > > > > > > > > > > > ashd > > > > > > > > > > > ot > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > > > > Inkscape-devel mailing list > > > > > > > > > > > Inkscape-devel(a)lists.sourceforge.net<mailto:Inksc > > > > > > > > > > > ape- > > > > > > > > > > > deve > > > > > > > > > > > l@...1721... > > > > > > > > > > > sts. > > > > > > > > > > > sour > > > > > > > > > > > ceforge.net> > > > > > > > > > > > https://lists.sourceforge.net/lists/listinfo/inks > > > > > > > > > > > cape > > > > > > > > > > > -dev > > > > > > > > > > > el > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------- > > > > > > > > > > ---- > > > > > > > > > > ---- > > > > > > > > > > --- > > > > > > > > > > ------------------ > > > > > > > > > > Check out the vibrant tech community on one of the > > > > > > > > > > world's > > > > > > > > > > most > > > > > > > > > > engaging tech sites, Slashdot.org! http://sdm.link/ > > > > > > > > > > slas > > > > > > > > > > hdot > > > > > > > > > > _______________________________________________ > > > > > > > > > > Inkscape-devel mailing list > > > > > > > > > > Inkscape-devel(a)lists.sourceforge.net > > > > > > > > > > https://lists.sourceforge.net/lists/listinfo/inksca > > > > > > > > > > pe-d > > > > > > > > > > evel > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------- > > > > > > > > > > ---- > > > > > > > > > > ---- > > > > > > > > > > --------------------- > > > > > > > > > > Check out the vibrant tech community on one of the > > > > > > > > > > world's > > > > > > > > > > most > > > > > > > > > > engaging tech sites, Slashdot.org! http://sdm.link/ > > > > > > > > > > slas > > > > > > > > > > hdot > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > > > Inkscape-devel mailing list > > > > > > > > > > Inkscape-devel(a)lists.sourceforge.net > > > > > > > > > > https://lists.sourceforge.net/lists/listinfo/inksca > > > > > > > > > > pe-d > > > > > > > > > > evel > > > > > > > > > > > > > > > ----------------------------------------------------------- > > > > > ---- > > > > > ---- > > > > > ----------- > > > > > 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 > >

1 0

[UX] A simple code that help
by Jabier Arraiza 05 Jun '17

05 Jun '17

Hi all. A thing easy to do: Right click->context_menu:lock selected items. Right click->context_menu:unlock down items. First one is optional. Want to add to Inkscape? Please let try to say the best 1 or 2 strings to the menu. Cheers, Jabier.

4 10

Gitlab Migration (for reals this time)
by Ted Gould 05 Jun '17

05 Jun '17

Howdy folks, (sorry about the accidental first send) As we've discussed more that once we're looking to move a Bazaar repositories on Launchpad over to Git repositories on GitLab. We're now closing in on the time for that migration. We've discussed a schedule in the board meeting this afternoon and I wanted to make sure everyone is aware of the plan. We're expecting 24-hours of "downtime" as part of this. ==== Step 1 ==== Wed, 7 Jun evening US time We're going to make the Bazaar repositories owned by the project owned by the board and then start migrating them to Git. This will hopefully mean that accidental commits won't happen. The migration to Git will take a few hours, giving it over night to complete (allow for some network hiccups). ==== Step 2 ==== Wed, 8 Jun morning US time Push the Git repo and branches to GitLab, this should take a little while, but will hopefully be done by the afternoon. We should be generally good to go after that, but will verify a couple of downloads. ==== Step 3 ==== Party! I'll send an e-mail to the mailing lists for each phase as we go through them with a status update. If you have an open branch on LP, it should be migrated. Please make sure to push before Wed. night the 7th. It would be even better if they could be merged but that shouldn't be required. You should be able to pick up your branch from Gitlab on the other side. Ted

3 4

Inkscape Phone
by Jabier Arraiza 05 Jun '17

05 Jun '17

Hi all. Is posible add a mobile phone for Inkscape proyect. The growing services based in mobile some of them mobile only, maybe require an oficial mobile phone. The goal is not use calls or data changes and use throught WIFI. Cheers, Jabier.

12 27

Re: [Inkscape-devel] [Inkscape-docs] News item about the new manual work?
by Maren Hachmann 04 Jun '17

04 Jun '17

Hi Carl (and Brynn, see bottom), Am 04.06.2017 um 15:55 schrieb Carl Symons: > > I have been holding off on any further editing and proofreading pending a > resolution of the following information for myself. > > There are places in the manual where additional information would be useful. > Information that is not in the original version. Should it be added? If yes, > to what extent should the content be tweaked? This depends on the amount of detail you want to add. It should fit into the book's concept of giving 'just the necessary basics'. Everything that is not strictly necessary, and does not *largely* improve the helpfulness of the book for someone who knows *nothing* about vector graphics, should be left to the detailed manual for advanced users. This is just an introduction, for people who want to learn by do(odl)ing, and who will pick up the concepts as they advance. It is meant to be easy - in writing style, with short sentences, as well as in contents. Would you like to pick up proofreading again where you left? You're welcome to make edits that fit the above description any time, without having to ask for permission. > Also ... there was some discussion about reorganizing the manual, changing > chapter order and the like. > > Apologies if this has been discussed previously. I've only recently joined the > manual effort. > > It would help to know if the project is mostly about translation or if it's > more extensive than that. Guidance please. @Brynn + Carl: I think we might postpone the changing of chapter order to a later point of time, so we will get a first, 'working' copy faster, and so people have a chance to gain insight into the conceptualization of the book. Also, that discussion got us sidetracked a bit, it seems, if it lead to Carl not knowing what to do next (and if). If anything, changing the order is a matter of drag and drop, and can be done any time, it shouldn't stop us from working. (I was thinking having a skeleton ready at Hackfest time might be useful, in case Elisa and Cédric would like to help work on this then - but of course, I don't know what their plans are for Paris). Kind Regards, Maren

1 0

Re: [Inkscape-devel] [Inkscape-docs] News item about the new manual work?
by Maren Hachmann 04 Jun '17

04 Jun '17

Thank you, Marietta, Carl, and Martin for pointing me into the right direction (hopefully) and for calling for help, and volunteering your time :) I'm glad to know that people are still interested in helping, but might just not have known how (or, in CR's case, are too busy with other stuff - believe me, I understand). Guess I got too used to the standard open source theme of 'grab a task and do it if you're up to it' - and I'm also kind of shy about telling others what to do. I'm sorry about not getting that I should take on a more active, guiding role, to make it easier for new members to join. @Marietta: What do you think about Martin's suggestion? Kind Regards, Maren Am 04.06.2017 um 22:52 schrieb Martin Owens: > On Sun, 2017-06-04 at 13:20 -0500, Marietta Walker wrote: >> If I can help, I will be glad to do so, but I do have limitations >> in knowing the software. > > You would make a good editor then, both in the generic sense for > English grammar and the functional sense in 'do you understand this' > > Is this something you'd be good at helping with? > > Best Regards, Martin Owens > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ Inkscape-docs mailing > list Inkscape-docs(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-docs >

1 0