| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
| |
A lot of header clean-up.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- export of .odg files was completely broken on Windows as
"documentUri = Inkscape::URI(filename);" always failed
(Windows paths are never valid URIs because of '\')
- Linked images did not seem to be working on any OS
(probably regression in 6f844ef457690c841b0be91d70b1e54b61c04812)
I assume support for linked images is still sketchy but seems to
work in the most common cases; support for embedded images seems
to be non-existent, though.
Fixed bug:
- https://bugs.launchpad.net/inkscape/+bug/1654034
|
| |
|
|
|
|
|
|
|
| |
Replace "\stackrel" with "\tabular" to achieve constant line spacing.
The former varies line spacing depending on the content of the line
(i.e. an line containing "-" will have a very small height)
Add basic support for line-height.
(currently only the top level text element is considered)
|
| |
|
| |
Found via `codespell`
|
| | |
|
| |
|
|
|
| |
Fixed bug:
- https://bugs.launchpad.net/inkscape/+bug/1739497
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows to tell the user something more helpful than
"File could not be saved" (leaving the reason open for speculation).
The former implementation somehow grew to only ever throw
Inkscape::Extension::Output::save_failed for any exception that
occurred (which did not really matter as we did not throw anything
else but certainly wasn't very useful either).
Questionable throwing behavior was introduced in commits trying to
workaround other issues:
- output.cpp a874b82b41c08fc1738b449d400fcc6aeb85d72a
- system.cpp d8d60c60ebeeefb068d9b68bf7d96f1f1f88518a
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
This turned out to be a bit of a mess due to the interplay between
the classes Script / ExecutionEnv / Effect / PrefDialog.
(Basically they don't talk to each other much but all want to
contribute to the GUI)
Likely "Script" (and possibly "ExecutionEnv") should be refactored
to let the other classes handle UI exclusively and throw errors
where suitable.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
As the parser seems to wrap newlines into their own tspan which has
the same style as the preceding tspan the latex-text renderer
produced output like "\texbf{\\}" which broke compilation in LaTeX
|
| |
|
|
|
|
|
|
|
|
|
| |
Wrap text in "\shortstack" to allow for newlines using "\\".
The output extension already produced those but they are ignored
in a "\smash" environment.
Patch by Michael Jäntsch
Fixed bug:
- https://bugs.launchpad.net/inkscape/+bug/771959
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This also fixes an issue with multipage PDF output where an empty
string would have been assumed to require emission of the previous
page when in fact the CairoRenderer does not produce a new page in
this case resulting in another facet of
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1417470
Invisible characters might still cause this issue but it seems to be
a very unlikely scenario and there's no way to know this without
actually rendering the glyphs (which seems to be overkill here)
|
| |
|
|
|
|
| |
It happen often that the rendering was interrupted early but the
final "cairo_surface_status" claims success which results in
incomplete output but no user-visible warning.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The previous implementation [1] allowed to sandwich text between
graphical objects by outputting multiple (partial) PDF pages which
are then stacked in the final document to reveal the full image.
However this code failed for clipped/masked/transparent objects
as those are treated specially by the renderer resulting in missing
pages in the output causing [2].
The attempt to workaround this issue which was committed in
e4dea66a338824037b6c35b262aa8db4004b6581 (now reverted)
fixed document creation in LaTeX by inserting blank pages but did
not actually fix the issue with clipped/masked/transparent objects
typically resulting in a single page with the full image and all
text put on top.
This commit resolves the underlying issue, making the former
workaround unnecessary and allowing for proper overlaying of text
and arbitrarily clipped/masked/transparent objects
Fixed bugs:
- https://bugs.launchpad.net/inkscape/+bug/771957 [1]
- https://bugs.launchpad.net/inkscape/+bug/1417470 [2]
|
| |
|
|
| |
This reverts commit e4dea66a338824037b6c35b262aa8db4004b6581.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
- do not call cairo_show_page as the GtkPrintOperation seems to do
that internally (calling it manually will emit the current page,
clear it, and the cleared page seems to be emitted in error later)
- we can (and should) still call cairo_surface_destroy as it's doing
reference counting internally (we increase the reference count in
CairoRenderContext::setSurfaceTarget) and won't actually destroy
anything until the count reaches zero
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Previously only the first page was printed properly,
all following pages were either blank or were not printed at all.
This was caused by finishing/destroying the cairo surface of the
cairo context associated with the GtkPrintContext used for printing
which made it impossible to draw to it for any consecutive page
Fixed bugs:
- https://bugs.launchpad.net/inkscape/+bug/1733424
- https://bugs.launchpad.net/inkscape/+bug/490866
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Found using `codespell -q 3 -w --skip="*.svg,*.po,*.ts,./share/tutorials,./src/libavoid,./packaging/win32/languages,./man,./src/2geom" -I ../inkscape-whitelist.txt`
whereby whitelist file contained:
```
dum
iff
glight
substract
te
upto
```
|
| |/ |
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| | |
This replaces all usage of boost::scoped_ptr with std::unique_ptr.
Also removes the corresponding includes.
|
| | | |
|
| |/ |
|
| |
|
|
| |
Just use Gio::File when access to non-local files is needed.
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The crash only affected embedded images.
(we were already catching the exception when loading a linked file)
While at it add some error reporting via debug messages,
fix a memory leak and do some minor cleanup.
Fixed bug:
- https://bugs.launchpad.net/inkscape/+bug/1720330
|
| |/ |
|
| | |
|
| |
|
|
|
|
| |
The idea behind inkscape-version.h / inkscape-version.cpp is to
avoid rebuilding most of the code base when the version number
changes. Defining a version number in config.h defeats this purpose.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
... just a matter of taste.
But both wanna be initialized: fixed.
|
| |
|
|
| |
get_filename methods
|
| |
|
|
|
| |
Fixes Bug:
- https://launchpad.net/bugs/1417470
|
| |
|
| |
(bzr r15724)
|
| |
|
|
|
| |
longer tied to Adobe).
(bzr r15723)
|
| |
|
| |
(bzr r15720)
|
| |
|
| |
(bzr r15715)
|
| |
|
|
|
| |
placeholder instead
(bzr r15653)
|
| |
|
|
|
|
| |
Fixed bugs:
- https://launchpad.net/bugs/1686549
(bzr r15647)
|
| |
|
|
|
|
| |
http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/14978
http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/15047
(bzr r15638)
|