- Inkscape Docs - Inkscape Mailman

10 Aug '17

Hi, long-time Inkscape user here, looking to get into coding for it too. I created this really simple extension for setting CSS classes <https://github.com/monomon/inkscape-set-css-class> on elements. It has an option to clear inline styles of the elements, so that the css class would have an effect. It is useful when having numerous elements that repeat or have the same styles. First, select a correctly styled one, use "Merge styles into CSS". Then select the rest and use "Set CSS class" to apply the new style on them. I am aware of the extension posted on the forums that sets classes <http://www.inkscapeforum.com/viewtopic.php?f=5&t=18483&p=69760#p69752>, but having to manually clear styles after is a bit of a pain, so not completely usable for my case... and it's not in a code repository, so no way to contribute. I read that in GSoC CSS handling will be improved, which is awesome! Hope someone finds this useful. Regards, Mois

2 6

minor change of workflow for beginners guide?
by brynn 31 Jul '17

31 Jul '17

Hi Friends, I had initially started with proofreading for the new beginners guide, but quickly found it was very difficult to do, without taking the graphics into account. Without knowing where the images are going to be placed and whether they might have captions or not, it's hard to make the text fit well. Especially when the goal is to be brief and clear with the text, and not load it with a lot of technical details. One way to make it simple, is to use graphics wisely. But if the graphic for a particular item is far away from the text on the page, it could backfire, and make it more difficult to understand. I (or anyone) could proofread the text by itself. But after the layout and styling teams do their jobs, and place the images on the pages, the text and graphics may or may not work well together. Unless that's part of the style and layout teams' jobs? But it seems like that puts a lot of work on their plates? So I want to propose doing the proofreading as the final step. I'm not familiar with writing books or manuals. But for general text documents, like articles or theses, it seems like proofreading is usually the final step. So I thought it couldn't hurt to make the suggestion. I wasn't sure whether to make this an Issue in the gitlab. It seems like not very many of the Docs team or guide-writing team is looking there. So I wanted to at least start the discussion where the widest number of people can see it. If a formal Issue is needed, I'll be glad to make one. Anyway, just a thought. Thanks for listening, brynn

3 4

[Manual]: Beginners' Guide Status
by Maren Hachmann 28 Jun '17

28 Jun '17

Hi to all of you who are interested in the Beginners' Guide! I'd like to give you another status update about our progress on the book: What happened since the last status update? ------------------------------------------- - JP read over the first section, from a user perspective (and found no grave issues with it! :D) - Sergio joined the team, by commenting on an issue at gitlab. He will help in checking for hurdles for beginning Inkscape users, from a non-native speaker point-of-view, and (I hope) also with consistency checking. He has already made a good start, finding some inconsistencies and bugs within the second section of the book. - brynn proofread the largest part of the second section, to make sure it's using proper English! - Elisa, while in Paris at the Inkscape Hackfest that is currently going on (see also: https://inkscape.org/en/news/2017/06/06/hackfest-2017-paris/), had a go at separating single images and adding lots of new ones! - Jabier brushed up the CSS a bit, and tested export options :) See below for a link to the latest pdf, with some splashes of color! - I have updated screenshots and uploaded images with translated file names for section 1 and 2, and am currently working my way through the pictures in section 3 of the book. What can you help with at this stage? ------------------------------------- We need proof-readers, the more the merrier! The only requirements are that you need to be a native speaker of English and need to have a basic knowledge in Inkscape usage. We also need someone who can help with the book layouting, if possible with some experience in preparing books for print and/or screen and some knowledge of CSS. There's a lot of room for creativity here :) And last but not least, the book needs consistency checkers, who make sure that things fit together throughout the book, and that the terms used match those in the Inkscape glossary. This is really important, so the book will look like 'one piece', even though it's being worked on by different people. If you want to join the team, comment on the issue that you'd like to help with here: https://gitlab.com/inkscape/inkscape-docs/manuals/issues or just reply to this email. All book chapters are short, and work is shared - you can opt to take on just one or two chapters! If we have more people who can help with that, we'll have the book ready in a breeze! Alpha Version ------------- The current draft of the manual is available for reading at: http://write.flossmanuals.net/start-with-inkscape/_draft/ Jabier's latest pdf version of the manual is available for download at: http://objavi.booktype.pro/data/books/startwithinkscape-en-2017.06.27-23.32… See you on flossmanuals :), Kind Regards, Maren

1 0

[Manual] Updates and news
by Maren Hachmann 27 Jun '17

27 Jun '17

Hi everyone, after sending out the message about having felt a bit lonely while translating the manual, several people sent me some helpful tips on how to do it better :) (Thanks!) This update message is the incarnation of one of those. Also, I was very pleased to see that there are so many people still interested in helping, and to see some new people to join us on the Beginners' Guide project. Welcome again, Jabier, Jelle and Marietta! So, what happened this week? ----------------------------- - Brynn has worked on a friendly news item to get more contributors that will soon be published (find it here, if you're a website editor: https://inkscape.org/en/news/unpublished/812/) - CR posted a first draft (png) of a cover image, with a tasty Inkscape ice cream (find it here: https://www.dropbox.com/s/h4n88xpnc6declz/inkscape_cover_beginner_m) - Jabier has volunteered to work on the CSS a bit, and tested the pdf export, where he found an issue, which, fortunately, we were able to solve (see example pdf of draft from a couple of days ago: http://objavi.booktype.pro/data/books/startwithinkscape-en-2017.06.07 -01.46.42.pdf) - Jelle offered to help with proofreading, and possibly also with design - Marietta joined the team, and started out making a public task list (here: https://gitlab.com/inkscape/inkscape-docs/manuals/issues/, more on that further down) and committed to help keeping it updated. She also proofread one chapter for language inaccuracies, and offered to help with the glossary and testing of the manual's effectiveness. - Martin (doctormo) helped by giving me permissions to manage the manual task list and members on gitlab - I have learnt a bit about managing a project this size (at least, I hope I have... let me know when I'm stepping on your toes, please), did some investigation on export formats, helped set up the gitlab issues section, coordinated with members to get them set up, reviewed the news article and translated and technically reviewed 17 chapters, also feeding back to Elisa for the original French version. There are 14 chapters left to be translated, I expect to be done with that in a week, if nobody else joins me there. - Together we had some good discussions here on the list, that show that work on the manual is very much alive :) Hope I haven't forgotten anyone, and didn't get the facts wrong - if I have, please blame it on the lack of: The new task tracker -------------------- Marietta suggested that we have a task tracker to follow up on tasks and to keep an overview about responsibilities. This is a good idea (while currently, I'm still able to keep most of it in my head, that is not a good place to keep records, and to allow people to self-assign and update tasks, and to be responsible ;-) - it may also loose some info here and there), and after a bit of searching, we settled on the *Gitlab issue tracker* for the *Manuals project* as our base. As Inkscape's code is currently in the process of moving there, website translation files and website code already reside there, and most people who will stay with the project long-term will need an account there anyway, and as it offers some project management functions, this is a good place for keeping log of our progress. We are still thinking a bit about the most useful way to organize issues there (because of interdependencies). Everyone in the Beginners' Guide group is invited to create a gitlab account at https://gitlab.com/users/sign_in and to sign up for the tasks Marietta is currently working on adding at https://gitlab.com/inkscape/inkscape-docs/manuals/issues You can also add new tasks or request access to the team for helping to manage tasks. Please don't take on more tasks than you can work on in parallel. Only sign up for what you are really currently working on. If you want to work on a task in the future, but cannot yet, leave a comment there, so people know who to ask for help. Kind Regards, Maren

3 6

[Manual] Update
by Maren Hachmann 19 Jun '17

19 Jun '17

Hi Manual folks (and those who want to join us), we have reached a major milestone today: TRANSLATIONS ARE DONE :D 59 of 59 chapters translated! :) The only thing that is left to do for this step is to remove that task from the Community ToDo list on the Inkscape website ;-) (this one: https://inkscape.org/contribute/to-do-list/). I'm going to do that tomorrow. I'm so happy that we're now through with this, and now have a preliminary version available for people to look at. I also would like to thank Sylvain Chiron and Hinerangi Courtenay, who worked on the translations of the first section, for their help with this huge task. What else happened this week? ============================= - brynn's news item about the manual effort has been polished a bit further, reviewed by its author, and was published. You can read it all here now: https://inkscape.org/en/news/2017/06/06/new-inkscape-beginners-manual/ (it has also been translated to four other languages by our website translators' team). - JP, a new team member joined us as a test user on gitlab. JP wants to help by giving us feedback on how the book chapters work for new Inkscape users. - Jabier played a bit with setting up cover images on flossmanuals. - Brynn started proofreading, and has looked over the first three chapters in the second section already :) What's next? ============ The next tasks concern images and proofreading, and can be done in parallel. Images: ------- - pictures that we will keep will need English file names. These are (currently) all pictures that do not contain any (French) text. - pictures that need to be replaced or edited need to be re-made. This concerns all pictures with French text in them. For some, we may get away with just cutting off the French text, and putting its translation next to the image in the book. Others need to be shot again. If you can help with any of the image related tasks, please find more info at https://gitlab.com/inkscape/inkscape-docs/manuals/issues/16 and comment there, so we can organize who does what. Proofreading: ------------- - as you all know, the translator of most of the chapters (me) is not a native English speaker. Also, while I have fixed and updated a lot while translating already, there remain parts in the text that could be rephrased and polished a bit. We need your help with proofreading now. If you are a native English speaker, please comment at one of the section-related issues at gitlab: https://gitlab.com/inkscape/inkscape-docs/manuals/issues Current status for taking a peek ================================ The latest alpha version of our work is available for reading at http://write.flossmanuals.net/start-with-inkscape/_draft/_v/2.6/introductio… If you want to join the team, it's not too late - just send a message to the list here, or comment at gitlab, and we can get you set up. Due to the nature of the book, all chapters are very short, so work can be shared easily. Kind Regards, Maren

3 2

News item about the new manual work?
by brynn 12 Jun '17

12 Jun '17

Hi Friends, As I'm writing up a quick draft to announce the upcoming hackfest, I suddenly wondered if it might be a good idea to write a short item about the recent new work on the new manual? I could do that, after I finish the hackfest article. I'm thinking Maren might be able to get all the details correct, the first time around? Although I don't mean to volunteer her. As I said, I could do it myself, if we decide to do it. I think it would help in community-building, to keep the wider community up to date about these things. What do other manual workers and Docs list subscribers think? All best, brynn

3 11

update "Getting Started with Development"
by Maximilian Gaukler 11 Jun '17

11 Jun '17

Hi everyone, I would like to propose a change to this page: https://inkscape.org/en/develop/getting-started/#install-build-dependencies Currently, the section "Install build dependencies" doesn't constructively explain how to build the latest trunk without enabling some PPA. But, lucky enough, there is already a nice listing of apt-get commands in this file: https://gitlab.com/inkscape/inkscape/blob/master/.gitlab-ci.yml As it is used in the CI (automatic build), it is automatically checked that the commands there actually work for the current version. Therefore, I'd suggest the following change: (pseudo-patch-file, - = remove, + = insert) - Note: If you are using the PPA for the latest builds on Debian, you - can use this alternative command to get a more accurate set of build - dependencies: - - sudo apt-get build-dep inkscape-trunk Note that this will install the build dependencies of the Inkscape package available in your repositories. If the package is old, you might need to install some additional dependencies - ; + . + + A more accurate set of build dependencies + can be found in this file in the lines containing 'apt-get': + https://gitlab.com/inkscape/inkscape/blob/master/.gitlab-ci.yml + - the output of the configure script should give you hints on what - else is required. + In case of errors, the output of 'cmake' should give you hints on what + else is required. Also, the doc/HACKING.* files are really outdated (many technical details are wrong), I would suggest simply replacing them with a link to the develop/getting-started website. If it helps, I can hand in a merge request for that, or a launchpad bug report, or whatever is the right thing during the migration to GIT. Looking forward to your feedback, Max

2 1

Sourceforge confirmation email
by Maren Hachmann 10 Jun '17

10 Jun '17

Hi everyone, please actively look for an email from sourceforge that asks you to confirm your sourceforge mailing list membership(s). They have changed their mailing list policies to make indicating the country of residence of a subscriber mandatory. More info can be found at: https://sourceforge.net/blog/sourceforge-project-e-mail-policy-update/ (@doctormo: if you want to extract the things mentioned at https://sourceforge.net/blog/sourceforge-project-e-mail-policy-update/ , do it before June 29th - old, inactive mailing lists will be deleted, for example.) Kind Regards, Maren

3 2

Fwd: Re: [Inkscape-devel] News item about the new manual work?
by Marietta Walker 07 Jun '17

07 Jun '17

And I am the culprit on not getting sending back to the list. My email defaults to the sender not the list and I keep forgetting to change the email address and I just did it to Maren with the messages below! Shame on me Marietta -------- Forwarded Message -------- Subject: Re: [Inkscape-docs] [Inkscape-devel] News item about the new manual work? Date: Tue, 6 Jun 2017 16:36:12 -0500 From: Marietta Walker <marietta@...167...> To: Maren Hachmann <maren@...68...> No problem at all. I did take a look, and you will find I am pretty flexible, but is OK to use the English board? I am sure I will not learn French in time to help with anything! I will be happy to extract and help track task and mark them complete as we go. And as a new user of Inkscape, you can count on me to also test as we go. Regards Marietta On 6/6/2017 4:09 PM, Maren Hachmann wrote: > Hi Marietta, > > a kanban board is a good idea, but there are free alternatives which I > would prefer to see used, e.g. https://framaboard.org/. > > Perhaps you would be willing to extract the tasks from previous messages > (esp. the one about the news item to Brynn) and move the board over to > framaboard? Also, we would need someone to take care of marking tasks > that are done by people who are not registered there as done. > > We don't need everyone to have an account, I think - we could also just > add their names, when we know they want to work on it. > > What do you think, Marietta? > > Kind Regards, > Maren > > Am 06.06.2017 um 20:45 schrieb brynn: >> No thanks for me. (I've already got a whole notebook of login >> passwords.) But I think Martin has been looking for something like >> that. Especially if it would give automatic reminders (afaiu). >> >> All best, >> brynn >> >> -----Original Message----- From: Marietta Walker >> Sent: Monday, June 05, 2017 9:59 AM >> To: inkscape-docs(a)lists.sourceforge.net >> Subject: Re: [Inkscape-docs] [Inkscape-devel] News item about the new >> manual work? >> >> Hi all, >> >> I have set myself up with Trello in order to track notes and completion >> of Chapter review.. (Just to let everyone know I will not be actually >> editing chapters, only providing feedback to Maren on those things I >> need to. ) >> >> I digress. Trello is free and easy to use. It has taken me about ten >> minutes to figure it out and set my self up with a checklist, which I am >> now working on breaking into Sub-heading groups. >> >> With that said, if anyone would like to join me there to create >> checklists /progress tracking, If everyone jumped in to use, we could >> also let the group know where we are because I have made it public for >> viewing. >> >> So if you want to check it out-here is the link. >> https://trello.com/b/5MTvCikC/inkscape >> >> If you want to use it, then create an account and then send me your info. >> >> Regards >> Marietta >> >> On 6/4/2017 6:10 PM, Marietta Walker wrote: >>> I think it will suit me perfectly. >>> >>> Thanks--Marietta >>> >>> On 6/4/2017 5:55 PM, Maren Hachmann wrote: >>>> 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 >>>>> >>>> ------------------------------------------------------------------------------ >>>> >>>> >>>> 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 >>> >> >> ------------------------------------------------------------------------------ >> >> 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 >> >> ------------------------------------------------------------------------------ >> >> 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 >> > > ------------------------------------------------------------------------------ > 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

3 3

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

07 Jun '17

CR, I have been translating (and fixing contents as I go) 1-2 chapters each day for the last 2.5 weeks and am more than halfway through (35 chapters done, 24 left to do). There wasn't anyone else to be seen around, after the first week, when one person translated a chapter (unfortunately they picked the only one that needs to be rewritten from scratch, because Inkscape changed), and two people proofread a couple of chapters (thank you!!!). Well, and a couple of days ago, someone seems to have accidentally wiped all the notes on the book, that were supposed to help get people started (or maybe it was a platform bug). I'd be glad to see some proofreading and styling/screenshooting people get on board, so we can continue seamlessly after I'm through with translating. I'm a bit disappointed about everyone being so engaged and vocal about helping/liking the action, and now me working on it alone for > 2 weeks already. But that's normal, I guess - it was the reason why I haven't started this earlier, and I felt ready to take it on now, no matter what. Anyway, I'm going to continue to plow through, then translations will be ready before the hackfest. In parallel, I'm going to be plowing through my new garden, and to help fix up someone else's house, so I expect to not have time for much else. I'd be glad if someone could try and reengage people to help with the manual (preferably people who are able to work independently and know Inkscape inside out, or who concentrate on something they really do well, like fixing up language or styling). There are more than enough open tasks: from CSS to cover design, to screenshooting, to consistency checking and layouting, to improving on my more or less weird English, to adding missing content (or perhaps, translating, of course). And yet, when we do this, I think it's important to take care to honor the underlying 'Keep it simple and as short as possible' concept of the book, which would make it possible for young teenagers to use it to get started, without much theoretical ballast. Elisa seems to have invested a *lot* of thought into how she built up the chapters and when to start teaching which concept. I suspect her concept stems from experience in teaching live Inkscape courses. Maren Am 04.06.2017 um 13:32 schrieb C R: > I'd say let's wait and do a progress report, so we can say that we're > making progress on it, rather than just that we've decided to do it. I > plan on helping this area of the project much more after I handle the > hackfest swag. It would be better to have a more or less complete > manual before we announce it to the public, unless it's a call for > help with it. > > If it's a call for help with that area of the project, then go ahead, though. :) > > Thanks for the amazing amount of work you're doing for the project, > brynn. It's definitely helping drive my own motivation for Inkscape > project work. :) > > -C > > On Sun, Jun 4, 2017 at 12:17 PM, brynn <brynn@...78...> wrote: >> Hi Friends, >> As I'm writing up a quick draft to announce the upcoming hackfest, I >> suddenly wondered if it might be a good idea to write a short item about the >> recent new work on the new manual? >> >> I could do that, after I finish the hackfest article. I'm thinking >> Maren might be able to get all the details correct, the first time around? >> Although I don't mean to volunteer her. As I said, I could do it myself, if >> we decide to do it. >> >> I think it would help in community-building, to keep the wider >> community up to date about these things. What do other manual workers and >> Docs list subscribers think? >> >> All best, >> brynn >> >> >> >> ------------------------------------------------------------------------------ >> 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 >

5 19