May 2017 - Inkscape Devel - Inkscape Mailman

Re: [Inkscape-devel] Update to window rotation.
by Jean-François Lemaire 23 May '17

23 May '17

I too use an Intuos tablet but I disabled the touch feature because I hate it. I hope modest stylus users like myself won't be forgotten. Cheers, JFL

9 16

telegram inkscape
by Jabier Arraiza 22 May '17

22 May '17

Hi all anyone has get the t.me/inkscape from telegram direction. Its cool if can delete the acount and the url reserved and send to inkscape board to manage it. Whith this inkscape community has the best link to telegram services we want to add in the future. Thanks so much in advance.

3 6

Devanagari font rendering not correct
by Raghavendra Kamath 18 May '17

18 May '17

Hi, I noticed that the Devanagari (https://en.wikipedia.org/wiki/Devanagari) font and possibly other indic scripts with overlapping ligatures and diacritics, Don't render correctly in inkscape. The part where the elements overlap leave a hole, and there is a gap in horrizontal bar at the top. If I remember correctly this is recent problem after .92 (I will try to get older inkscape version and test this). I have also filed a bug report here -> https://bugs.launchpad.net/inkscape/+bug/1691631 You can see a screenshot where the same word is written in same font in inkscape and libreoffice here -> https://launchpadlibrarian.net/320136836/inkscapevslibreoffice-devanagari.p… Notice the gap in the top horizontal line and also the holes where the top diacritics intersect with the horizontal lines. I kindly request others to test and check if this problem is present in other scripts where there are overlapping elements, and if they encounter same problem please add comment to the bug report. This gives a problem for people using inkscape for lettering comics or typesetting using these scripts. Thank you -- Raghavendra Kamath Illustrator raghukamath.com

1 1

Stable 0.92.1 and gcc-7
by Ken Moffat 17 May '17

17 May '17

I know that trunk has been cleaned up for gcc-7, but some of us prefer to build rleases. The following patch (backported from trunk, boy, do I hate bazaar ;) fixed the errors I was getting. Now, I don't have all the possible deps, so it might be that there are other problems I haven't seen, but maybe this will help someone. ĸ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

1 0

Re: [Inkscape-devel] Any chance we can make some docs material? (targeting the moon)
by Maren Hachmann 17 May '17

17 May '17

Hi, sorry for the delay. I've been trying things out a bit, and I feel I haven't seen enough yet, but I won't have time tomorrow, so posting anyway now. So, it seems that what we still need for a manual (any kind) is a platform to create it (not only write, but also output to different formats). I have had a chance to look at 3 different platforms on my list, and I'm trying to outline the pros and cons, as I perceive them, please add yours to the list. There are many more platforms in existance (see also: https://github.com/PharkMillups/beautiful-docs#generating-docs), and if anyone here has some experience with them, please add. ************* - Gitlab Wiki + X, as suggested by Martin. WHAT: An online Wiki on gitlab with a source code editor, associated with a gitlab project. PROS: - custom-made to suit the project's individual needs (no specifics yet) - Preview functionality CONS: - only (limited set of) Markdown, RDoc or AsciiDoc - limited formatting options, formatting not so much about 'roles' of formatted text, but more about 'looks' - the backend isn't written yet - no option for branches via interface (so we could start writing for trunk, and continue fixing for stable) - no direct translation support - support for the backend depends upon a single individual, no user community - no WYSIWYG editor - no GUI access to git repo, for managing where to put uploaded files etc. - no GUI for undoing a change (like in a 'normal' Wiki), or looking at a diff EXAMPLE (frontend): https://gitlab.com/inkscape/inkscape-web/wikis/home ************* - Gitlab Editor + Sphinx / readthedocs: WHAT: A git repository with an online source code editor and documentation update on readthedocs.org on save (i.e. commit). PROS: - available quickly (didn't know how it works exactly, but got it all up and running with test content within an evening) - uses git and reStructured Text - allows to have branches, so devel version features can be documented when they are coded - supports translations (not entirely sure how, though, haven't tested it yet, wanted to send this email instead. E.g. Django docs are translated. Fallback to English if no translation of a document. I think they use different branches.) - free theming, separately for each output format - free hosting, can also use our own domain name with readthedocs.org, e.g. docs.inkscape.org - after installing some programs, tool chain runs locally - preview via gitlab editor or local editor - same toolchain can be used for developer documentation (includes code documentation from docstrings) - extensible via plugins (haven't had a chance to take a closer look yet or test any) - I think it's possible to add a 'edit this page on gitlab' link to each page, to get new contributors, even when using readthedocs.org (not tested, but read that others did similar things) - extremely wide range of export formats via plugins - infinite hierarchy nesting - syntax highlighting (e.g. for command line usage instructions, or extension writers) - video embedding (not tested) CONS: - learning curve for admin (theming, plugins,...) - learning curve for editors (syntax, workflow) - no WYSIWYG editor, only preview (incomplete, because doesn't support all sphinx stuff) EXAMPLE: - repository: https://gitlab.com/Moini/inkscape-extensions-multi-bool/tree/master/docs - rendered documentation: http://inkscape-multi-bool-extension.readthedocs.io/en/latest/index.html ************* - Booktype: WHAT: A web portal for creating books, hosted by friends of the Inkscape project. PROS: - available right now, no further setup required - best interface by far, easy and intuitive to use - team functions, user roles, chat - prevents concurrent editing - wide range of export and import formats - support for themes/settings for specific export formats (e.g. different font sizes etc.) - free hosting and maintenance via flossmanuals(fr) - community of experienced documentors CONS: - confinement to django database for version control, more difficult to get data out of it again for editing - no direct translation support (make a copy of the book, copy changes over after doing a comparison in the history) - limited versioning support (only the latest one can be edited) - we'd need to ask someone to add CC-By-SA licence (currently, the options I got were CC-By, GPL. I guess this would be quick and easy to solve.) EXAMPLE (rendered documentation): https://www.flossmanualsfr.net/initiation-inkscape/ ************* All of them would be FLOSS, have support for internal linking, allow to insert images and allow editing via browser. ************* I wish it were possible to combine the ease of use of the booktype frontend with the portability, branch support, sustainability and versatility of the gitlab/sphinx/readthedocs backend... (In German that's called the 'eierlegende Wollmilchsau' - egg-laying wool- and milk-giving pig...) For the sphinx option, I believe I'd be able to take on the first setup and some of the tasks that come with customization and extending, as well as basic maintenance. For Booktype, anyone of the documentation writers could do that easily. Regards, Maren

4 16

Offer to help put inkscape on windows store
by Marc Jeanmougin 12 May '17

12 May '17

Hi all, I recently discussed on IRC with dwcares from Miscrosoft who wants to help us simplify precesses on windows. Here is his email: === David Washington from Microsoft here. Earlier this afternoon I had conversation with Marc about potentially publishing the Inkscape app to the Windows Store, the app store for Windows 10 PCs. The Windows Store now supports publishing Win32 Desktop apps with little or no code change using the Windows Desktop Bridge. Taking advantage of the Windows Desktop Bridge and Distributing through the Windows Store also provides simplified options for automated updates, easy install and uninstall, and provides a new distribution path for folks who may have not found Inkscape before. Our team has identified Inkscape as a top desktop app that we’d love to see in the Windows Store. Given this we have some resources to help with the process of getting this ported using the Windows Desktop Bridge and published to the Windows Store. The process itself is lightweight, and our team is equipped help walk you through getting it ported and published. We’ve done some early investigation on the Inkscape binaries and we haven’t identified any issues getting it published. If this is something that seems interesting to you, we can get together on the phone and talk through the details for the next steps of getting this published. If you’d rather make progress in email/IRC, we’re happy to accommodate what works for your team. We’re prepared to work with you on getting this published as early as next week. I look forward to working together. I’ve included some folks from my team who will be helping you. Thanks much, David Washington Microsoft | Developer Experience | 206-605-2062 === Eduard, Nicolas or Partha, iirc you're the ones doing stuff on windows, could you take it from here if it seems interesting ? Thanks, -- Mc

13 31

Hackfest lodging
by C R 12 May '17

12 May '17

So, now that we have some solid dates, I can help whoever needs it to get lodging. There are several reasonably priced locations that are just a few steps from the venue. Please send me an email if you want help getting a room. Please include your budget, what days you're attending, whether you require a single room, or whether you'd like to save more money and share. I'll do my best to reserve the space we need in the same part of the hotel. Thanks! -C

1 0

moderators needed for the website
by brynn 12 May '17

12 May '17

Hi Friends, Thanks to Martin for creating the most amazing moderation system I've ever seen, for the website. Now that it's ready, volunteers are invited to join the website Moderation Team. Moderators work together to make decisions about each reported item (image, comment or member). No particular skills are needed. The biggest qualification is to care about maintaining the website as a beautiful and safe place for members to show their Inkscape work and interact. Most days you would only need to spend 15 to 20 minutes or less, although in the beginning, a little more time will probably be needed to become familiar with the system. And visit as many days as you can. The more moderators we have, the less time we each have to spend moderating. If you're interested in helping, please go to Community tab > Teams page (https://inkscape.org/en/teams/) and click on "Moderation Team". On the next page, click to request to join the team. (Sorry, I don't know exactly what the text is, for that link, but it will be regular size text, and orange color). After that, we'll contact you, and get you started. Thanks for your interest in contributing to the Inkscape Project :-) All best, brynn

1 0

website moderation policy final
by brynn 12 May '17

12 May '17

Hi Friends, It seems like this last message about moderation policy got buried in all the recent important chatter. So I'm re-sending the most vital parts of it, so we can finish this up. For convenience, https://inkscape.org/community/coc/ And here's the suggested change: In the Guidelines for User-Submitted Content section, replace "Art and other content submitted to the Inkscape website should adhere to the following rules:" with "Content uploaded to the gallery should be related to Inkscape (e.g. created with Inkscape, created for use with Inkscape, showing how to work with Inkscape, etc.). We reserve the right to remove any content that does not seem appropriate or does not adhere to the following obligatory rules:" C R said > Little thing, but "created for use with Inkscape" could cover things like just regular images... in fact it could cover just about anything, even things made with Adobe Illustrator. I'd simply cut that bit out. Hhmm.....yes, I see what you mean. My interpretation of that, is for things like extensions or filters. But maybe there's a better way to say it? What about "created to be installed in Inkscape"? Or maybe just "to be installed in Inkscape"? That would eliminate any kind of image. Any other suggestions out there? Eduard? I wonder about adding "Inkscape Project"? Such as: "Content uploaded to the gallery should be related to Inkscape or the Inkscape Project (e.g. created...." That would cover things like a website graphics or page mockup, board meeting transcript, etc. C R said > If there's a significant amount of undesirable content currently, it's probably best to make it retroactive. If it's just a few things, then we should approach the owners about it. Not to be pushy, but to inform them of the new policy. To me, it's a significant amount. By my estimate, probably 1 or 2 thumbnails per page of the gallery are random photos! So that's way too many to consider trying to contact them. Personally, I would love to delete them without notice. But since the policy was not available at the time they uploaded, technically I think it's not fair to delete them. But they'll soon be shuffled further and further back, as the gallery grows. I'm happy just to get the policy settled and put it into effect. Thanks everyone for taking the time, and helping to finalize this issue. As far as I know, this will be the last step before we can start recruiting moderators, and using the system officially. All best, brynn

4 9

Re: [Inkscape-devel] Any chance we can make some docs material? (targeting the moon)
by Maren Hachmann 12 May '17

12 May '17

Would it make sense to use gitlab's new subgroups feature for this? The inkscape-docs team could be a sub-team of Inkscape, that way. There are only 4 members as of now, so changing wouldn't be so difficult as it might be later on. Maren > Am 28.04.2017 um 16:14 schrieb Martin Owens: >> On Fri, 2017-04-28 at 12:39 +0100, C R wrote: >>> I'd love to quit my job and just do docs. :) Unfortunately, that's >>> what it would probably take to get docs going to the extent we'd >>> like. >>> It's been discussed before, but never gone anywhere because of lack >>> of time/hands involved. >>> >>> Yes, we should use Scribus to do it. In fact, it should probably be a >>> github project to attract contributors. This way we can patch what >>> needs to be patched when stuff changes in subsequent releases. >> >> Sounds like you have a solid step one Chris. >> >> Here's the inkscape-docs group on gitlab, EVERYONE should join, there >> should be a button to join: >> >> https://gitlab.com/inkscape-docs >> >> And here's the new book/manual/docs project where files can be put: >> >> https://gitlab.com/inkscape/manuals >> >> I recommend using the wiki attached to the project to plan the >> adventure slowly. Add a bit at a time and don't rush to have something >> "complete" but have something small produced. >> >> 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 >> >

12 86