- Inkscape Docs - Inkscape Mailman

Re: [Inkscape-docs] [Inkscape-devel] should this remain in the gallery?
by brynn 20 Aug '17

20 Aug '17

Thanks C R! Off topic PS - I received the plaque. Thanks again :-) brynn -----Original Message----- From: C R Sent: Friday, August 18, 2017 2:41 AM To: brynn Cc: Inkscape-Docs ; Inkscape-Devel Subject: Re: [Inkscape-devel] should this remain in the gallery? My thought - If it mentions Inkscape, it's free advertising for the project. If it's spam, at least it's relevant spam. :D I vote to leave it up. imho we don't need to be ruthless unless there's some problem with too much of it. - It will make the project seem unfriendly to anything outside its own interests, and hostile to working with designers/developers who offer free editing with Inkscape as a benefit (I do this a lot with my own design work). They no-doubt post that pdf elsewhere with Inkscape compatibility listed as a benefit. I believe that's exactly the kind of thing we want. My 2p -C On Fri, Aug 18, 2017 at 5:17 AM, brynn <brynn@...78...> wrote: > 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 > > > > ------------------------------------------------------------------------------ > 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

Re: [Inkscape-docs] [Inkscape-devel] Not as awesome as....?
by brynn 20 Aug '17

20 Aug '17

Thanks Gord. But unfortunately, when I click Release, it turns blue, and that's all. There's no edit button. I'm not so much a website developer, as someone who watches out for the contents. (Originally I created a lot of the contents, but only the simple pages. There's a lot of the site I just don't have access to, because I don't understand it.) All best, brynn -----Original Message----- From: Gord Caswell Sent: Sunday, August 20, 2017 4:57 AM To: brynn Cc: Inkscape-Docs ; Inkscape-Devel Subject: Re: [Inkscape-devel] Not as awesome as....? On 20 August 2017 at 05:17, brynn <brynn@...78...> wrote: > > PS - I'd offer to delete them, except I don't appear to have access to those > pages. > Brynn, To edit the page, when you're on the page, click on "Release" in the header, then "Edit Release" Gord

1 0

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?

1 0

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

18 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

1 0

CSS class extension
by Mois 10 Aug '17

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