- Inkscape Devel - Inkscape Mailman

New Das Stroke LPE
by Jabier Arraiza 01 Apr '18

01 Apr '18

Hey folks, Whit the help of Lazur and the thread: http://www.inkscapeforum.com/viewtopic.php?f=22&t=24175&p=83448&hilit=s troke+dash#p83448 just do a tiny LPE to fix it. Here are the new video showing it (no audio): https://archive.org/details/dash-stroke-lpe Hope is useful since is not included in the SVG spec. With love, Jabiertxo.

1 1

Hackfest 2018: Variable fonts, refactoring, etc.
by Bryce Harrington 01 Apr '18

01 Apr '18

----- Forwarded message from Tavmjong Bah <tavmjong@...8...> ----- Date: Sun, 01 Apr 2018 03:31:32 +0200 From: Tavmjong Bah <tavmjong@...8...> To: Bryce Harrington <bryce@...961...> Subject: Hackfest 2018: Variable fonts, refactoring, etc. Bryce, can you forward this to the inkscape-devel list? SourceForge is blocking my Internet provider's mail server. Thanks. Hi, Before I start my report on the Boston Hackfest, I would like to thank Martin Owens, our Inkscape host, and Máirín Duffy, our Red Hat host. Martin did a great job of showing us around Boston and making sure we were properly fed (even cooking us a lunch!). Máirín, a designer at Red Hat, gave us great feedback on Inkscape in its current form and on our plans for future Inkscape versions. I would also like to thank the other Red Hatters, especially Matthias Clasen, who helped make this hackfest a success! And I would like to thank the many donors to the Inkscape hackfest fund that make these hackfests possible. I'll start with the item that will most excite Inkscape users: Variable Font Support in Inkscape. Variable fonts are fonts that contain "axes" that can be tweaked by the user. The simplest example would be a font that contains an axis for weight. Instead of being limited to a few discrete font weights, each requiring its own font file, a user of variable fonts can with just one file select weights with any values continuously between a minimum and maximum value. Prior to the hackfest I got rendering of variable fonts working in Inkscape. This required handling the CSS property used to set the axes and modifying the rendering code to use the axes. (I should mention that this only works with very new versions of the libraries we use to handle fonts and text.) At the hackfest I worked with Felipe on adding support to the user interface. Felipe got a prototype version working during the hackfest. Felipe and I also had discussion with Matthias, a Red Hat employee who works on GTK about Matthias' improved GTK Font Selection widget to which he has added variable font support. I spent some time experimenting with replacing the font selection in the Text and Font dialog with the native GTK widget (after getting positive feedback from the designers in the room). Speaking of Matthias. We spent time with him discussing some of the problems we have with GTK. This was very productive, both in validating our move to GActions (discussed already by Alex) as well as getting feed back on a number of other issues. Maybe the biggest blocker in getting to 1.0 is how broken floating dialogs are under the Wayland compositor, a replacement for the X11 window server. The library we use to handle floating dialogs, GDL, is not used by many projects (maybe only two). The code is complex and fixing it to work with Wayland may be too difficult. After feedback from Máirín it appears our best way forward is to replace GDL with use of the GtkNoteBook widget which handles dragging and dropping tabs. (Máirín also finds Gimp's use of tabs to dock dialogs much easier to use than our current system.) One of my biggest beefs about working on Inkscape code is how poorly documented it is. Part of the problem is that code is strewn throughout the repository so it is often hard to find the code that handles a particular thing. This also leads to code duplication as its hard to see that we already have solution to a particular problem. I've proposed a directory reorganization that better sort the code by its purpose. This, and having README files in each directory should help new developers find their way through our code base. After several round of discussion and feedback we've come up with a solid plan which I'll be implementing in the next few weeks. Part of the directory reorganization is to get all the graphical interface code into one place so we can work on isolating the GUI components from other parts. This should allow us to more easily create an efficient command-line version of Inkscape. (Alex's work on GActions should also help us give more power to the command line.) There were quite a few other very useful discussions we had: the road map, documentation, increasing diversity, our website, etc. I personally find that I am not very efficient at actual hacking during hackfests (I work best when I am in the peace and quiet of my own home) but the discussions we have during hackfests leads to great productivity afterwards. Tav ----- End forwarded message -----

1 0

Re: [Inkscape-devel] [Inkscape-user] New Das Stroke LPE
by Jabier Arraiza 01 Apr '18

01 Apr '18

I just see the spec. I hope I can improve the LPE with it. Regards, Jabier On Sun, 2018-04-01 at 14:16 +0200, Tavmjong Bah wrote: > On Sun, 2018-04-01 at 12:51 +0200, Jabier Arraiza wrote: > > Hey folks, > > > > Whit the help of Lazur and the thread: > > http://www.inkscapeforum.com/viewtopic.php?f=22&t=24175&p=83448&hil > > it > > =s > > troke+dash#p83448 just do a tiny LPE to fix it. > > > > Here are the new video showing it (no audio): > > > > https://archive.org/details/dash-stroke-lpe > > Nice! > > > Hope is useful since is not included in the SVG spec. > > If it's an LPE it doesn't need to be in the SVG spec. Have a look at > this to see what the SVG group was thinking about before it was > removed > from the SVG 2 spec: > > https://svgwg.org/specs/strokes/#StrokeDashing > > > With love, Jabiertxo. > > ------------------------------------------------------------------- > > ----------- > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Inkscape-user mailing list > > Inkscape-user(a)lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/inkscape-user

1 0

Re: [Inkscape-devel] [Inkscape-user] New Das Stroke LPE
by Jabier Arraiza 01 Apr '18

01 Apr '18

Thanks Tav for the feedback. Im working in a feature to allow use min lenght of a segment to define the aproximate lenght of the hole/dash, this allow corner perfect dashes in a rectangle with diferent ammount of dashes. I go to the link you send to catch more ideas... I realy like more a SVG spec than a LPE, mainly because Im not recreating the stroke but subdividing the segment, so we cannot handle fills without fill between many LPE. Regards. On Sun, 2018-04-01 at 14:16 +0200, Tavmjong Bah wrote: > On Sun, 2018-04-01 at 12:51 +0200, Jabier Arraiza wrote: > > Hey folks, > > > > Whit the help of Lazur and the thread: > > http://www.inkscapeforum.com/viewtopic.php?f=22&t=24175&p=83448&hil > > it > > =s > > troke+dash#p83448 just do a tiny LPE to fix it. > > > > Here are the new video showing it (no audio): > > > > https://archive.org/details/dash-stroke-lpe > > Nice! > > > Hope is useful since is not included in the SVG spec. > > If it's an LPE it doesn't need to be in the SVG spec. Have a look at > this to see what the SVG group was thinking about before it was > removed > from the SVG 2 spec: > > https://svgwg.org/specs/strokes/#StrokeDashing > > > With love, Jabiertxo. > > ------------------------------------------------------------------- > > ----------- > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Inkscape-user mailing list > > Inkscape-user(a)lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/inkscape-user

1 0

Upcoming directory restructuring
by Tavmjong Bah 29 Mar '18

29 Mar '18

Hi all, At the hackfest we discussed a revised directory structure to better organize our code, This is a heads up that we plan on doing this reorganization in a couple of week (to give time for existing patches, etc. to land). The purpose of the reorganization is to make it more obvious where to find different pieces of code. At the moment our code tends to be distributed over lots of different directories (especially the code that manipulates SVG and the code for our 100+(!) GUI elements). The proposed directory structure can be found at: http://wiki.inkscape.org/wiki/index.php/Source_Directory_Structure You can comment on the proposed change here or on the wiki page. We also discussed a requirement that all files should have at least one or two sentences to document what their contents does. This should really help new developers (and prevent code duplication). Tav

8 14

Hackfest 2018 Boston - day 1 update
by Bryce Harrington 28 Mar '18

28 Mar '18

A recap of some discussions that have been under way... 0. On the first day I gave a presentation on modularity, and identified areas in both Inkscape the codebase and Inkscape the project, to encapsulate complexity into more easily understood chunks, with well defined and simple interfaces between them. 1. Gtk3 (and Gtk4) issues were brainstormed. We use several Gtk2 functionalities which are deprecated in Gtk3, and may be removed in Gtk4. We scoped out ideas for transitioning, such as migrating from GtkAction to GAction, and GtkMain to GtkApplication. The discussions helped clear some blockers, and Alex is now digging into the code and working out how we can do the change with minimum impact on UI appearance or behavior. Longer term, once these transitions are made, there are a number of more impactful changes that could be attempted. One scheme we scoped out was to separate the frontend and backend of Inkscape, using GActions as the interface. The backend would present a lengthy list of all of its internal operations (Actions). There would be separate sets of Document Actions (like moving a node on a Bézier curve) and Window Actions (like resizing the window). The frontend UI would translate its widget clicks and menu picks into the corresponding actions and pass them down. Apart from giving us better organized code, this could also make it easier to have multiple kinds of UI's (e.g. a simplified "kidscape" interface) or even no-UI (e.g. a headless version that processes commands through command line args or a batch language). 2. Website strategy is under heavy discussion. It's been a while since the website has had a design refresh, and whiteboard markers are flowing. Improving mobile friendliness seems important, also better use of graphics and videos is being explored, and better emphasis on using some of the great user stories out there. There's also a recognition that we have needs for something more user-facing (e.g. something "brochure-like") and something more back-office-y (the contributor community, aka "contributy"). A lot of this will need a lot more hashing out and collecting wider ideas, but I'm looking forward to seeing how this work proceeds in coming weeks and months. 3. Variable fonts. This new type of font permits e.g. sliding scale of style aspects like bold between letter forms. Some implementation work has already been done, but the hackfest has been used to hash out some remaining questions and implementation details. There's still some UX/UI questions on how it should be implemented in the interface. 4. Improved gradients using random dithering in pixman. Lots of discussions in both IRL and IRC around Mc's code to add better gradient rendering to pixman, that avoids banding by randomly dithering the colors. The patch has been proposed to pixman and some feedback's been received, but still mulling over how to actually get this feature into use. 5. Color management / CMYK. We had an in-depth discussion between coders and designers to hash out what we ought to be shooting for in terms of requirements. We discussed a "print pre-flight dialog" concept that had come up in some of the Vectors team discussions. What's needed as a next step is to flesh out the concept - workflow use cases, a mockup UI, and analysis of how data in/out flows need to work. There are a lot of ideas and user stories, that need gelled into something coherent that people can start throwing darts at. 6. SVG 2 working group, and future directions. A number of features we wanted to see included in the SVG 2 spec sound like they will get dropped. Further, this change of direction by the WG suggests it may get tougher to include artistic-oriented features in future revisions of the spec. We discussed some of the problems, but the path forward for us is unclear. --- I'm certain I've missed a number of the discussions here, and am not capturing all the work under way. Hopefully other attendees can fill in what I've missed or gotten wrong, and provide more details from my above summary. Please ask questions, too. Bryce

5 6

Future 0.92.x bugfix releases
by Bryce Harrington 26 Mar '18

26 Mar '18

Let's plan on a 0.92.4 in a few months, maybe in the May/June timeframe. As we've talked about in the past, we'll be continuing to do bugfix releases on the 0.92.x branch for the foreseeable future, and we'll be treating it as an equivalent of a 'long term stable' series for Inkscape in case changes. Some aggressive changes in 0.93 may lead to bad breakages for some users, so we want to give them a reliable fallback. So, please continue backporting good fixes from master into the 0.92.x branch, and record the changes in release notes: http://wiki.inkscape.org/wiki/index.php/Release_notes/0.92.4 If you don't have commit access to 0.92.x (or don't feel comfortable pushing to it), you can mark bugs in Launchpad with the 'backport-proposed' tag, so committers can more easily spot them. (But make sure the bug has a patch attached to it that will actually apply and build against 0.92.x.) A few release process todo's I'm aware of: * Mac builds - need a volunteer * 'make distcheck' - needs added to cmake * PPA recipe updates - needs scripted [hackfest: bryce/alex] * NEWS file update - change python script to use BeautifulSoup [bryce] * packager announcements - set up a proper mailing list [bryce] * Transition to new RSA 4096 GPG signing key [bryce] * cleanup the release documentation [bryce] * lp milestone, etc. updates - needs a LP script so its less manual Let me know if you'd like to help on any of these tasks. Bryce On Fri, Mar 23, 2018 at 10:42:17PM -0700, Bryce Harrington wrote: > Inkscape 0.92.3 is a maintenance release resolving numerous bugs and > making this the most stable release of the series. > > To download the latest packaged version of Inkscape visit: > > https://inkscape.org/release/0.92.3/ > > (Note: A build of 0.92.3 is not currently available for MacOS. The > project welcomes additional contributors with MacOS expertise.) > > Among the most reported bugs addressed were: > > * Blank pages being output when printing multiple copies of a document > * The inability to cancel during the export of large files > * Application crashes caused by dragging a path at a cap or line join > * Keyboard shortcut problems on non-Latin keyboard layouts > > Also a few performance improvements and usability enhancements of note: > > * New SVG export options from the command line > * Support for right-to-left text > * Improved ellipse controls > * Multi-line text support for the PDF+LaTeX export > * New render tile preferences for performance tuning > * Better startup performance for many Windows users > > Find out more about the release at: > > https://inkscape.org/en/news/2018/03/22/announcing-0923-release-inkscape/ > > > > > Inkscape 0.92.3 > > -~= Released 2018-03-11 =~- > > +----------------------------------------------------------------------+ > | Release Highlights | > +----------------------------------------------------------------------+ > > Inkscape 0.92.3 is mainly a stability and bugfix release, but it also > brings some small new features, like being able to set an ellipses' > radii numerically in the tool controls, or switching the writing > direction from left-to-right to right-to-left. Windows users will be > happy to learn that the long startup times many of them were seeing > could greatly be reduced. A new rendering option with an adjusted > default value can vastly improve performance when working with filters. > > Many of the bug fixes address important functionality, like printing > issues, crashes with the node tool or problems with keyboard shortcuts. > > > +----------------------------------------------------------------------+ > | Improvements | > +----------------------------------------------------------------------+ > > Command line usage > ================== > > Three new command line options controlling page size are supported when > exporting in SVG format: > > • --export-area-drawing (feature requests in bug #1597921 and bug #1722844) > • --export-area-page while using --export-id > • --export-margin > > > Text tool > ========= > > Support for switching between RTL and LTR writing directions has been > added (on narrow screens, find it by unfolding the overhang menu for the > text tool's tool controls by clicking on the triangle at the far right). > > > Circle/ellipse/arc tool > ======================= > > New fields for setting vertical/horizontal radius (Rx/Ry) were added to > the tool controls bar. (Bug #1181127) > > > PDF+LaTeX export > ================ > > Support for multi-line text with basic support for line-spacing > attribute was added. (Bug #771959) > > Please note: > > • Currently only the line-spacing of the top level text element is > considered, i.e. all lines in one text element share the same line > spacing. > • LaTeX is much more clever with respect to line spacing, so layout > might not always be exactly the same as in Inkscape. > • Make sure to use a continuously scalable font in LaTeX, otherwise > results might be unexpected. > > > Preferences > =========== > > A new renderer option called "Rendering tile multiplier" was > added. Making this value larger can speed up drawing, if you have large > areas with complex filters in your drawing or work a lot with high zoom > levels on filtered objects. Making the value smaller can make zooming > and panning in relevant areas faster on low-end hardware (if there are > no large filtered areas on the visible part of the canvas). The default > value makes your screen consist of about four tiles that are rendered > independently, if you're not using a hidpi screen (which requires more > tiles). For a more detailed explanation, see: > > https://gitlab.com/inkscape/inkscape/merge_requests/211#note_62157385. > > > Startup Performance > =================== > > The first start of Inkscape on Windows is much faster now. > > This is the result of improvements in fontconfig 2.13.0, a third party > library which handles font related tasks for Inkscape. One of the tasks > is creating an index of all fonts available on the system which is much > faster now. If the new indexing causes any issues (i.e. fonts or glyphs > not available that could be used before) make sure to let us know or > report the issue directly to the fontconfig project. > > > Extensions > ========== > > Extensions on Windows can now make use of Tkinter, without requiring > users to install it themselves. Tkinter provides functionality for > creating interactive graphical user interfaces. This is used, for > example, by the TexText extension that renders mathematical LaTeX > formulas to SVG (feature request at bug # 1735451). > > > +----------------------------------------------------------------------+ > | Regression Fixes | > +----------------------------------------------------------------------+ > > • Potentially missing command line output in Inkscape 0.92.2 on Windows 7. > (Bug #1714278) > • Extensions in the 'Raster' submenu relying on ImageMagick were > broken and caused crashes in Inkscape 0.92.2 on Windows. > (Bug #1720330) > • gcodetools were creating wrong orientation points since the dpi > change had been made for Inkscape 0.92. > (Bug #1680760) > • Regression on 0.92.2 makes it impossible to fill a powerstroke shape > (Bug #1715433) > • The preferences dialog was tiny by default. > (Bug #1360213) > • Node handles no longer get too large when selected, and they also > revert back to standard size when deselected. > (Bug #1568644) > • Export to .odg (Open Document Drawing) works again on Windows. > (Bug #1654034) > • Inkscape no longer freezes when trying to import clipart from > OpenClipart when the openclipart.org server takes too long to > respond to requests. > (Bug #1745521) > • Text that is written in vertical direction now has its marks > (e.g. accents) on the correct side again. > (gitlab commit 2abe0bb6) > • The 'Clone original' path effect works again to fill a path with a > PowerStroke applied to it (useful for drawing cartoons) > (Bug #1715433) > > > +----------------------------------------------------------------------+ > | Important bugfixes | > +----------------------------------------------------------------------+ > > • Fix crash when attempting to drag path at cap or line join. > (Bug #1691406) > • Inkscape process did not exit cleanly on Windows. > (Bugs #1412365 and #1715339; also causing #1714278) > • File extension was sometimes omitted when adding saved files to Windows' > list of "recently used documents" resulting in unusable links. > (git commit 4d599528) > • Do not crash on systems with illegal fontconfig configurations. > (Bug #1716516) > • Resolve issues when attempting to save files to non-existing > directories. Could happen for shortcuts.xml and when setting the > autosave location manually. > (Bug #1719629) > • Allow cancellation of bitmap export. > (Bug #1195929) > • Fix issues with PDF+LaTeX export: wrong stacking of text/graphics, missing > pages in PDF output. > (Bugs #771957, #1417470) > • Fix shortcuts not working as expected when a non-latin keyboard layout is > the primary keyboard layout on a system. > (Bugs #1226962, #1730246, #1734308) > • Printing multiple copies of the document resulted in one copy and many > blank pages. > (Bug #490866, #1733424) > • Fix export area when exporting single objects to SVG using the --export-id > command line switch. > (Bug #1306662, #1707368) > • Fix DXF output and Windows vector print scaling for documents with a custom > view box. > (Bug #1672066) > • Invalid output generated from extensions no longer makes Inkscape > crash. > (gitlab commit 608fa56e) > • The Ruler Live Path Effect now shows correct measurements in the default > template (and other non-px-based templates), too > (Bug #1460858) > • The Document Properties dialog now has a more compact layout, so all items > should be accessible on smaller screens > (Bug #1510831) > > > +----------------------------------------------------------------------+ > | More bug fixes | > +----------------------------------------------------------------------+ > > There were even more issues fixed than those listed above, but these > probably only affect a small portion of users, or are relevant for > development and packaging only. > > For a complete list, visit our launchpad bug tracker and see the commit > history on gitlab (all changes from August, 6th 2017 until release > date). > > > +----------------------------------------------------------------------+ > | Translations | > +----------------------------------------------------------------------+ > > The following UI translations received updates: > > • French > • German > • Icelandic > • Italian > • Korean > • Spanish > • Ukrainian > > The following installer translations received updates: > > • Korean > > > Contributing to interface translations > ====================================== > > Want to help with translations? Learn how to help at: > > https://inkscape.org/contribute/translations/ > > > +----------------------------------------------------------------------+ > | Documentation | > +----------------------------------------------------------------------+ > > > Documentation Relaunch > ====================== > > The Inkscape documentation repository, containing the man page, the > keyboard shortcut list as well as the tutorials and their respective > translation files, has been almost completely refactored (Java has been > dropped in favor of Python), and was updated to work with git and > gitlab. > > > Documentation Updates > ===================== > > The man page and the keyboard shortcut list have been updated. > > > Where to find recent documentation > ================================== > > Continuously updated man page (for command line usage), keyboard and > mouse shortcut list, tutorials and translation statistics for the > various parts of the Inkscape project are available on the inkscape.org > website: > > • Man page > • Keyboard shortcuts > • Tutorials > • Translation statistics for Inkscape 0.92 series / development branch > > Tutorials, as always, are also included with your Inkscape installation. > > > Contributing to documentation and documentation translation > =========================================================== > > Contributions to the documentation translations, as well as improvements > to its contents, are welcome at the inkscape-docs repository. > > > +----------------------------------------------------------------------+ > | Known issues | > +----------------------------------------------------------------------+ > > • DPI Change: known issues with 'Scale elements' option > (Bugs: 1653230,1653236,1654342,1654796,1654880,1654903,1655005,1655053,1660228) > • DPI Change: Default grids in documents created with Inkscape 0.91 don't > scale correctly. > (Bug #1653893) > • Line height: Changing "baseline spacing" stops working. > (Bug #1707808) > • Renderer: Artifacts in Gaussian blur effects with default quality settings. > (Bug #1656383) > • Node editor: Deselecting selected nodes of complex paths takes a long time. > (Bug #1652100) > • Performance: Using the objects dialog at least once in your Inkscape > session slows down actions such as duplicate and delete for files > with many objects. > (Bug #1431274) > > > ------------------------------------------------------------------------ > For information on prior releases, please see: > > http://wiki.inkscape.org/wiki/index.php/Inkscape > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > > iEYEARECAAYFAlq15TkACgkQEaMBVuDmdhFeGACffqDDMJ7PI1yYV8gVz8V1jekW > vEgAn1jy67X42/mi4eX+ebQEvz9FUkpn > =ITZ8 > -----END PGP SIGNATURE----- > ------------------------------------------------------------------------------ > 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 5

Inkscape Hackfest 2018 (Boston) Almost here!
by Martin Owens 25 Mar '18

25 Mar '18

Dear Hackers, Are we all looking forward to two weeks from now when we'll be dining on lobsters and dunken donuts? Well if you are coming, please do update the http://wiki.inkscape.org/w iki/index.php/Hackfest2018_Attendees page (or let me know and I'll do it for you) This is the rough itinerary for the week: * Sunday 25th, optional drink with local Free Software hackers at the Grendel's Den in Harvard Square. 8:00pm to 11:00pm Some touristing might be available if you like to see Harvard. * Monday 26th - Friday 30th, Hacking at the Red Hat offices near south station. Anyone lost can contact me +01 857 277 2117 (Signal App is good for anyone from abroad) * Wednesday 28th - User participation day, if we have some users available, we'll be listening to normal Inkscape users. * Thursday 29th - Tentative choice for Inkscape Dinner at Les Zygomates (http://winebar129.com) (If no one objects in the next few days, I'll book a table) Let me know what you're looking forward to working on while your here, I'd like to get a new article put together to kick things off. If you can do photography, please let me know. We'll need a group photo and someone with a nice camera and a good eye is needed sine CR isn't here. Anything else, please let me know. Thanks everyone! Best Regards, Martin Owens

7 6

Re: [Inkscape-devel] [Inkscape-user] Inkscape no fonts
by Sam 24 Mar '18

24 Mar '18

I see small boxes everywhere, i.e. in the menu, in the side bar. There is no font at all in Inkscape. I can't open Inkscape's settings because I don't know where the settings are because everything is only displayed as small boxes. Sam On 24.03.2018 14:00, Robert Funnell wrote: > On Sat, 24 Mar 2018, Sam wrote: > >> I try to run Inkscape 92.3 on OpenSuse 42.3 with snapd, but there is >> no fonts. It is running but i only see small square boxes. > > Are you saying that you see boxes when you add new text, or that you > see boxes where there's previously existing text in a drawing? > > - Robert >

2 2

Missing fonts
by Sam 24 Mar '18

24 Mar '18

Hi guys, I try to run Inkscape 92.3 on OpenSuse 42.3 with snapd 2.27.6-1.1, but there is no fonts. It is running but i only see small square boxes. Can anybody help me? Tnx Sam P.S.: I posted this post to the ML "User" by mistake, so this post exists twice. Sorry.

1 0