Some of you may have heard of the fact that Autodesk is now supporting
SVG, and to be fair, that was long overdue, but at least one is closer
to having the choice of ditching AI8 format once and for all for a
universal format. I'm having a issue importing a 1 KB optimized SVG from
there seems to be a bug in dxf-import.py in line 443:
w = 90.0/25.4*vals[groups['370']]/00.0
This always crashed with a division by 0. A quick look reveals, this has
to crash. I found a bugfix online which makes this line:
w = 90.0/25.4*vals[groups['370']]/100.0
That helps and provides the desired results. The question is if this is
the desired value or if the developer intended a different number?
I have tried to submit a bug report via launchpad multiple times during
the day but it seems to not like me today, thus I am submitting it via
When I save an optimized .svg with the option "Convert CSS attributes
to XML attributes" enabled with Inkscape 0.91 (Ubuntu 16.04), any
application that I have tested but Inkscape do not display some parts
of an image with the resulting file. I managed to create a MWE that
should be handy enough for a successful analysis.
Attached you can find the original Inkscape .svg and two
optimized .svg files created with the CSS option turned on and off
respectively. When the option is off then all applications render the
dot fine, when it is on only Inkscape recognizes it.
Dipl.-Ing. Stefan Tauner
Research and Development
Embedded Systems Department
University of Applied Sciences Technikum Wien
Hoechstaedtplatz 6, 1200 Vienna, Austria
T: +43 1 333 40 77-316
Because the feeddback for the previous video, I update it a bit.
To enter in rotate mode you need SpaceBar+RightClick. or use the new
widget in the bottom.
Thanks to all viewers, and people involved.
In trunk, all images dragged into the canvas are automatically put in a group.
Is there a reason for this change?
It's been a bit of a pain over the last few weeks, because:
1. It requires ungrouping the image, or clicking into the image group
to view image properties
2. It requires the same to trace bitmap.
Any ideas as to why this change was made?
Hey folks. So I've recently branched out into several FLOSS communities,
and so I'm exposed to a lot more wishlist items. Generelly they are things
on the roadmap, and many have to do with the SVG spec.
When someone expresses a need for *x-feature* I generally send them to this
page to help: https://inkscape.org/en/support-us/svg-standards-work/
I was wondering if this is the best thing to do.
I get a lot of requests to help the project from people who I help get to
grips with Inkscape and other FLOSS.
Can someone provide a list of current links to parts of the project that
need financial aide? I can sort out who to send where (based on the
features they are interested in).
But a comprehensive list of donation links would be awesome. :)
On Sun, Oct 23, 2016 at 4:29 PM, Arlo Barnes <arlo.barnes@...400...> wrote:
> However, I recommend not continuing to use the phrase, but instead replacing
> it with something like "material considered inappropriate or offensive will
> be disqualified, at the judges' sole and final discretion".
Thank you for the feedback and input. I have modified the text and it
now reads "It must not contain anything inappropriate or otherwise
offensive. We recommend avoiding things such as nudity, violence, and
political or religious imagery. Material considered inappropriate or
offensive will be disqualified at the development team's sole and
> That over with, I look forward to submitting my entries.
I just noticed in 0.92-pre2, at least on Windows, the mouse middle
button does not pan anymore.
On 0.91 installation, same machine, middle mouse button pans.
[ If enabling "scrolling" by space key (checkbox "Mouse move pans when
Space is pressed"), that kind of panning works, however you need to
have the canvas "focused" for this to work (you get this gratis with
middle mouse button), so it's really inconvenient in comparison. ]
Can anyone confirm with Linux build, or on another Windows machine?
This feels more likely to be me having some corruption in my
installations, than an actual regression, so I hesitate to report it
The Inkscape team and community is winding down development and
preparing to release Inkscape 0.92. With the upcoming release, we need
to have a new About Screen done. This brings us to the Inkscape 0.92
About Screen Contest!
This time we are hosting the contest on our website.
For contest rules, more info, and to submit your entry please visit
November 13, 2016
Here's an update on where we are in getting the release out.
1. Windows packaging seems to be shaping up well. Packages for
0.91pre1 are posted to the website. Hopefully we'll see 0.92pre2
OSX still appears in need of volunteers to get packaging sorted.
It looks like we may be forced to omit this from our release
announcement plans, but let's give it a few more days. If anyone
is working on or plans to work on OSX packages, please contact me
2. DPI Scaling bug #1389723 - We still need someone to work on this
bug; there have not been new comments.
*** We still need someone to adopt this issue and run it to
3. Disable unstable features, bug #1589340 - I pushed the MESH option
fix. suv's summarized the remaining bits needing done and this
looks straightforward to get finished.
4. Fonts not shown in font manager (Win32), bug #1416674 - This is
now dropped as a release blocker. It still needs added to the
5. About screen - Work is under way here; hopefully this can get
taken care of quickly.
6. Release Notes - Apart from perhaps adding a few more known issues,
we are probably at a point we can consider the Notes complete.
This would be a good point to start translating them (or to bring
existing translations up to date.)
7. New snapshot. I've posted source packages for 0.92pre2; there
were a few little hitches but nothing major, and nothing that
looks like it would impact finalizing 0.92.0.