Re: [Inkscape-devel] [Inkscape-user] Inkscape no fonts
by Sam
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
>
5 years, 2 months
Missing fonts
by Sam
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.
5 years, 2 months
Inkscape 0.92.3 bugfix release
by Bryce Harrington
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
5 years, 2 months
Extensions
by Martin Owens
Dear all,
I've separated out the extensions directory into a new repository:
https://gitlab.com/inkscape/extensions
I haven't yet removed the files from the master branch, but I will as
soon as I get a couple of nods of approval from other developers and
packagers as this change needs some consideration.
My first job is to upgrade extensions to python3 and to do this I'm
going to write tests. Please let me know if there are any extensions
tests already written I can use.
Best Regards, Martin Owens
5 years, 2 months
Re: [Inkscape-devel] Extensions
by Lex Neva
> 4. Adding their own UI. In the cases where the current inx based UI falls
> down (conditional values, and many more) the users want to able to use,
> say, Kivy or even tkinter to do dialogs. This is super hard and only one I
> know that works is the very recent embroidery extension which needs own
> installer and is so complex I can't follow it.
Oh dear! Sorry it's so confusing. As I think you understand, trying to
get a cross-platform UI working is quite difficult. And for translations,
we had to completely ignore inkex.localize() in favor of bundling our own
translations, because we can't get our translation strings into inkscape
fast enough.
On the plus side, we handle units and viewbox correctly and we're 96dpi
compatible already, so no work needed there. Thanks for all the work
you're doing!
We're happy to answer any questions you might have on how Ink/Stitch works.
I follow this list, if somewhat slowly at times, but the best way to reach
us is to file an issue (github. com/lexelby/inkstitch).
5 years, 2 months
GtkActions in toolbars
by Alex Valavanis
Hi All,
In preparation for the Hackfest, I'd like to start looking at ways to
reduce (eventually eliminate!) our use of GtkAction.
One of the main uses we currently have for them is in toolbars, where the
tool widgets (buttons, spinbuttons etc) are all some kind of subclass of
GtkAction, which has been removed from Gtk+ 4. This means that when the
user clicks on the button, it triggers an "activate" signal, which is
handled by a callback function.
My question is basically, "what's the point?" Is there any reason why we
can't just use a plain old button in most cases, and just connect up the
"clicked" signal instead?
If it really needs to be some kind of Action, we could migrate to the
GAction API, but this may be much more difficult.
Best wishes,
Alex
5 years, 2 months
LaTeX rendering fail
by Jakob Peder Pettersen
When running the command Extensions->Rendering->LaTeX and typing in any LaTeX expression, I get no output and Inkscape returns:
*** WARNING - the DELAYBIND command has been deprecated, and will be
removed in the next version. For now you can restore
the behaviour by using -dREALLYDEALYBIND but if you
require continued use of this command you should contact
the Ghostscript developers. Commercial customers of
Artifex should email their support contact, free users
are encouraged to talk to us on the #ghostscript IRC
channel on irc.freenode.net.
Unrecoverable error: undefined in DELAYBIND
PostScript/PDF Interpreter finished. Return status 65280 executed command : /usr/local/opt/ghostscript/bin/gs -q -dDELAYBIND -dWRITESYSTEMDICT -dNODISPLAY -dNOEPS /var/folders/z_/v0sm2gys3y77640_7m4t99k40000gp/T//psinQuRKci
The interpreter seems to have failed, cannot proceed !
Traceback (most recent call last):
File "eqtexsvg.py", line 160, in <module>
e.affect()
File "/Applications/Inkscape.app/Contents/Resources/share/inkscape/extensions/inkex.py", line 268, in affect
self.effect()
File "eqtexsvg.py", line 154, in effect
svg_open(self, svg_file)
File "eqtexsvg.py", line 81, in svg_open
doc = inkex.etree.parse(filename)
File "lxml.etree.pyx", line 3299, in lxml.etree.parse (src/lxml/lxml.etree.c:72421)
File "parser.pxi", line 1791, in lxml.etree._parseDocument (src/lxml/lxml.etree.c:105883)
File "parser.pxi", line 1817, in lxml.etree._parseDocumentFromURL (src/lxml/lxml.etree.c:106182)
File "parser.pxi", line 1721, in lxml.etree._parseDocFromFile (src/lxml/lxml.etree.c:105181)
File "parser.pxi", line 1122, in lxml.etree._BaseParser._parseDocFromFile (src/lxml/lxml.etree.c:100131)
File "parser.pxi", line 580, in lxml.etree._ParserContext._handleParseResultDoc (src/lxml/lxml.etree.c:94254)
File "parser.pxi", line 690, in lxml.etree._handleParseResult (src/lxml/lxml.etree.c:95690)
File "parser.pxi", line 620, in lxml.etree._raiseParseError (src/lxml/lxml.etree.c:94757)
lxml.etree.XMLSyntaxError: Document is empty, line 1, column 1
Using the extension Tex Text yields a similar error:
Traceback (most recent call last):
File "textext.py", line 210, in cb_ok
self.callback(self.text, self.preamble_file, self.scale_factor)
File "textext.py", line 369, in <lambda>
converter_cls, old_node))
File "textext.py", line 387, in do_convert
new_node = converter.convert(text, preamble_file, scale_factor)
File "textext.py", line 751, in convert
self.pdf_to_svg()
File "textext.py", line 849, in pdf_to_svg
+ pstoeditOpts)
File "textext.py", line 596, in exec_command
% (' '.join(cmd), p.returncode, out + err))
RuntimeError: Command pstoedit -f plot-svg /var/folders/z_/v0sm2gys3y77640_7m4t99k40000gp/T/tmpAZUsxB/tmp.pdf /var/folders/z_/v0sm2gys3y77640_7m4t99k40000gp/T/tmpAZUsxB/tmp.svg -dt -ssp -psarg -r9600x9600 failed (code 1): pstoedit: version 3.70 / DLL interface 108 (built: Sep 16 2017 - release build - g++ 4.2.1 Compatible Apple LLVM 9.0.0 (clang-900.0.37) - 64-bit) : Copyright (C) 1993 - 2014 Wolfgang Glunz
*** WARNING - the DELAYBIND command has been deprecated, and will be
removed in the next version. For now you can restore
the behaviour by using -dREALLYDEALYBIND but if you
require continued use of this command you should contact
the Ghostscript developers. Commercial customers of
Artifex should email their support contact, free users
are encouraged to talk to us on the #ghostscript IRC
channel on irc.freenode.net.
Unrecoverable error: undefined in DELAYBIND
PostScript/PDF Interpreter finished. Return status 65280 executed command : /usr/local/opt/ghostscript/bin/gs -q -dDELAYBIND -dWRITESYSTEMDICT -dNODISPLAY -dNOEPS -r9600x9600 /var/folders/z_/v0sm2gys3y77640_7m4t99k40000gp/T//psinu3vxOs
The interpreter seems to have failed, cannot proceed !
I suspect this is a bug in the respective Inkscape extensions for LaTeX output.
System information:
macOS 10.13.3
Inkscape 0.91
pdfTeX 3.14159265-2.6-1.40.16 (TeX Live 2015)
dvips(k) 5.995
pstoedit: version 3.70 / DLL interface 108 (built: Sep 16 2017 - release build - g++ 4.2.1 Compatible Apple LLVM 9.0.0 (clang-900.0.37) - 64-bit)
Best regards
Jakob Peder Pettersen
5 years, 2 months
Releasing Inkscape onto the Website
by Martin Owens
Dear developers,
The website supports developers submitting releases using the releases
app, we haven't linked to the releases app publically, but thanks to
Maren and others it's a mostly complete history of Inkscape package
files.
To upload an inkscape package:
a) Go to the website and login
b) Click the "Upload Art or Resource" (or click Submit in any of your
galleries to better organise your files)
c) Fill in all the fields you want, make sure to include the uploaded
file and gpg signature.
d) Select "Inkscape Package" in the category drop down.
e) Save.
f) Now re-edit the new upload.
This will give you the two new fields of "Release" and "Platform",
these ONLY appear if: The upload is in the Inkscape Package category
AND you have permission to edit releases. If you don't see these
fields, make sure you join the releases team at https://inkscape.org/en
/*release-team and try again.
You can only have ONE resource per release, per platform. So the
Inkscape 0.92.2pre0 release can have ONE Win32 MSI Package, ONE Mac OSX
10.9 DMG, etc etc. If you try to over-write, it will deny you setting
the platform and release fields.
We're going to try and keep the permissions to one person for each of
the main platforms. So bryce can do source uploads, tgh can do Mac
uploads etc etc. We make have some backups, but user wise it shouldn't
need every developer to be a release team member.
Let me know if you have issues.
Best Regards, Martin Owens
Your Friendly Website Admin
5 years, 2 months
Website Caching (again)and fall-back
by Martin Owens
Hi all,
This is a general notice, I've switched on nginx caching for non-logged
in users. 95% of all requests are to non-logged in users.
Caching is set to 1 hour, if you update a cms page, upload a new
resource or make a new release, there WILL be a delay to some users
getting the new information.
We are closely monitoring the web server and tweaking the settings as
needed. Average request times have be 0.9s-1.1s but some days see
spikes to 5s (for the whole day) so we want to try and reduce the
common load. Page loads for HITs are down to 120ms, compared to 980ms
for a MISS.
I've also removed cmsplugin-history which takes up a lot of RAM. There
may be some holes in the cms, so let me know if you hit one.
Page caching in nginx means that if the website goes down, nginx will
keep giving our users a website as much as possible. So we may see a
slight improvement in fall-over, certainly for normal users.
Best Regards, Martin Owens
5 years, 2 months
