Regarding the serialization of Spiro control points
by Fred Brennan
I write from the FontForge project. Of particular interest to me is the Spiro
spline feature, which was originated around ten years ago by Raph Levien.
One thing I'd like to add, (which would benefit both our projects,) is the
ability of FontForge to understand the Inkscape Spiro serialization format.
However, there are several things about the format which to me as an outsider
appear to be defects serious enough that I have no idea how to even *import*
these splines correctly, much less export our Spiro splines to this format. I
would very much like to support the _de facto_ standard Inkscape has
originated of supporting Spiro in SVG, but I am lost.
George Williams, FontForge's original author, noticed this defect over eleven
years ago. Things are virtually unchanged since then, I checked `git
Spiro has five point types, not including beginning and ending points. They
* G4 curve (o)
* G2 curve (c)
* Corner (v)
* Left Constraint ([)
* Right Constraint (])
The ASCII single letters are the normal method of Spiro serialization, as
championed by Raph Levien and by us in FontForge.
Inkscape seems to create what I will call a "pseudo-SVG path". So, it is not
really an SVG path, but rather is an SVG path which undergoes transformation
into the typical Spiro format. Inkscape stores this in the "original-d"
So, given a Bezier spline with control points defined as (x, y, c1, c2),
Inkscape interprets a control point with only (x, y) to be a corner, meanwhile
a control point with all four is a G4 curve, and (x, y, c1, NULL) is a left
constraint while (x, y, NULL, c2) is a right constraint.
I can probably overcome this, although George Williams was right to be
skeptical of this format. There is no way I can see to define a G2 curve in
this strange "original-d" format.
Thus, this email. I write to ask a few things. I suppose first of all, what
are the chances that we can convince you guys to store Spiro splines in
plate format, or another widely accepted Spiro serialization format?
Second, if we cannot convince you to do that, how do I export FontForge spiros
which contain G2 control points to Inkscape's original-d format? It's not
possible, yes? So should I just silently fail and save them as G4? The curves
will not be the same if I do that. Should I disallow export to SVG w/Spiro if
glyph contains G2 control point? That seems a steep cost that will just
confuse my users, so perhaps I should abandon the whole thing if it comes to
Fredrick Brennan (@ctrlcctrlv)
: https://levien.com/garden/ppedit/README, section "Plate files"
11 months, 4 weeks
How do I invoke my.custom.extension by CLI
this is my first post on this list. I'm not sure whether this is the
place to ask, but couldn't find a better one.
I chose to use inkscape for modifying vector-graphic-PDFs and convert
them to PNGs and also to a varienty of PDFs with extra information in a
background batch job. Basically this works well with official Inkscape
1.1 (c68e22c387, 2021-05-23) and the results are just as desired.
Unfortunatelly there is some glitch with inkscape freezing every some
To track down the above freeze I decided to try the latest inkscape
source and build it myself (Windows 10/Windows 11) to be able to debug
I found that the current app (24f6795) does not obey to the same CLI.
Calling --verb=my.custom.extension complains
Unable to find: my.custom.extension
verbs_action: Invalid verb: my.custom.extension
I get the same error message if I try to invoke as --
Both --action-list and --verb-list do not list any extensions.
The extension is part of the menu, so inkscape seems to know about it.
Commit 5e32ad5 "Menubar Filters + Extensions : Conversion to Actions"
removes extensions from the verb-list. Various comments suggest that
verbs are supposed to be moved to actions. Not sure whether that is the
plan for extensions as well.
So my question is: How can I invoke my custom extension from CLI in the
current version of inkscape (24f6795926, 2021-12-25) or any later?
Cheers and a happy new year to everybody,
Fwd: Scribus 1.5.8 released
by Maren Hachmann
Forwarding for your interest:
-------- Weitergeleitete Nachricht --------
The Scribus Team is pleased to announce the release of version 1.5.8.
Like previous releases, work on version 1.5.8 focused mostly on bugfixes
and code optimizations, the latter of which are expected to lead to
reliability and speed improvements. We have also begun to prepare
Scribus for using Qt6, which will make our work easier for future releases.
Most important changes
- UI Improvements for dark mode and some icon updates and window
- Improvements to file import (IDML, PDF, PNG, TIFF, SVG)
- Improvements to PDF export
- Improvements with respect to tables (undo/redo, styles)
- Improvements to the Story Editor
- Improvements to the build system
- Translation updates
- Scribus 1.5.8 now includes Python 3 and is built for mac OS Catalina
The complete changelog is available here:
https://bugs.scribus.net/changelog_page.php?version_id=112. More details
are available from the Scribus Commit Mailing List archive
(http://lists.scribus.net/pipermail/scribus-commit/), beginning with
revision 24637 in April 2021.
Please note that while some bug fixes still may be backported to the
1.4.x branch, we do not plan an official release of this version
anymore. If you think you need the changes, you have to check out the
SVN repository and build 1.4.9svn from source. We encourage all Linux
and *BSD distributions to switch from 1.4.x to this new version, since
it's not only much more versatile but also more stable.
For download links and checksums please visit:
The Scribus Team would like to thank Anduin.net and Modirum for their
continued hosting of all of the Scribus websites.
We are grateful to the Organisation Internationale de la Francophonie
The Scribus Team is also honored to have Resene Colours (New Zealand),
dtp studio Oldenburg (Germany), Scientific Illustration Services Corp.
(USA), the Newspaper Association of America (USA), Software Consulting
Services (USA), freieFarbe e.V. (Germany), bauwerk Kommunikationsdesign
(Germany) as Special Supporters and donors of color palettes and other
content since the 1.4.x release, just like we are grateful to the owner
of Vector Portal for the permission to distribute some of his work as
Finally, the Scribus Team would like to thank the many end users,
translators, testers and contributors who helped us with this release.
1 year, 1 month
Re: [Inkscape-translator] Re: Call for translations for Inkscape 1.1.2 (bug fix release, stable branch)
by Maren Hachmann
confirmed, it's an annoying GitLab issue that hasn't been addressed for
quite some time.
I think it could potentially be fixable by adjusting our Continuous
Integration to not have the Windows builds in a separate pipeline and to
just go by date instead or whatever. (or, of course, GitLab itself could
fix it, but they have known about the problem for a couple years now, so
I'm not hopeful.)
The summary is that the additional, scheduled (so, resource-conscious)
job of the Windows builds overwrites the build results listed in the
dropdown and drops old build results from the 'latest' job.
You can still always find the latest successful build for 1.1.x here in
this list (don't choose those that are have the little 'Scheduled'
badge, but the latest one of the others):
Or, just wait a bit... (not a great idea at the moment).
Or, currently, the po and pot files in the repository are up to date,
too, but that is never guaranteed.
I'm including the developer mailing list as this is something they might
have a way to fix.
Am 16.01.22 um 15:31 schrieb Firas Hanife:
> I'm not sure if it's only an issue on my side but I'm unable to get the
> latest translation from 1.1.x branch artifacts.
> The provided link leads to a "Page Not Found" message.
> Can anyone confirm?
> Thank you!
> Il giorno sab 15 gen 2022 alle ore 17:03 Maren Hachmann
> <maren(a)goos-habermann.de <mailto:email@example.com>> ha scritto:
> Hello Inkscape translators!
> This is the official call for translations for the upcoming Inkscape
> 1.1.2 , which is planned to be released in early February.
> 1.1.2 is expected to be the last in the 1.1.x series of Inkscape, and it
> is bugfix release, so the number of updated strings is small.
> If you'd like to contribute to 1.1.2 translations, please coordinate
> with everyone in your language's translation team, and get the latest po
> and pot files from
> Further information is available from
> <https://wiki.inkscape.org/wiki/Translation_information> and
> If you are a translator for any of the languages below, please also
> check your 1.1.x branch po file for errors – either using the
> translation tool of your choice, or by compiling it to a mo file on your
> computer and reading the output – as they contain formatting errors and
> / or do not properly indicate the language they are for (default value
> is still set):
> as, az, doi, en_AU, en_CA, eo, es_MX, fa, hy, kok@latin, ks@aran, mk,
> ml, mni@beng, mni, mr, or, sat@deva, sat, sd@deva, sd, ur, ta
> Inkscape 1.2 (currently still the same as the master branch) is
> approaching its alpha stage. Translations for 1.2 are already accepted,
> but it is expected that especially the newly added strings will still
> change until the release.
> Happy translating!
> Inkscape Translators mailing list --
> To unsubscribe send an email to
> Inkscape Translators mailing list -- inkscape-translator(a)lists.inkscape.org
> To unsubscribe send an email to inkscape-translator-leave(a)lists.inkscape.org
1 year, 2 months
How to get started with contributions
by Pranjit Kakoti
I am Pranjit Kakoti, an undergrad. I am in my first year at NIT Silchar. I
am new to open source contributions but I am well aware of C, C++, Python
and a little bit of data science and machine learning. I am open to
learning new technologies.I would love to contribute to your organisation
but could you please tell me how to get started?
Hoping to hear from you soon.
1 year, 2 months
Dev Environment Setup
by Aashutosh Konge
HI, it would be a huge help if anyone could resolve my issue with the dev
setup as mentioned in 'Getting started with inkscape', specifically with
the executable build. Whenever, I try to install the build dependencies on
Ubuntu 20.04 using '*bash install_dependencies --recommended'. *I seem to
be getting the same error for each dependency: *"**Failed to fetch
I've tried to find answers on the internet but none of them work out. It
would be a huge help if someone could help me with figuring out a
OS: Ubuntu 20.04.3
OS type: 64-bit
GNOME Version: 3.36.8
1 year, 2 months