https://bugs.kde.org/show_bug.cgi?id=360821
Boudewijn Rempt changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=360821
Gary Wang changed:
What|Removed |Added
CC||wzc782970...@gmail.com
--- Comment #47 from Gary
https://bugs.kde.org/show_bug.cgi?id=360821
Dmitry Nezhevenko changed:
What|Removed |Added
CC||d...@inhex.net
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=360821
caulier.gil...@gmail.com changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/kde/ |
https://bugs.kde.org/show_bug.cgi?id=360821
Boudewijn Rempt changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=360821
Boudewijn Rempt changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=360821
--- Comment #44 from maderios ---
Hi
I posted here a bug report to Gimp Team about Gimp 2.10 XCF support
https://gitlab.gnome.org/GNOME/gimp/issues/3990
This is a copy:
GIMP version: 2.10.12
Operating System: Arch Linux and all others
Is the issue
https://bugs.kde.org/show_bug.cgi?id=360821
--- Comment #43 from Christoph Feck ---
*** Bug 412339 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=360821
--- Comment #42 from Boudewijn Rempt ---
No, kimageformats (and qimagio) is only suitable as a fallback for formats we
haven't implemented yet, it's not possible to offer image format specific
options for export, or multiple layers of different kinds
https://bugs.kde.org/show_bug.cgi?id=360821
--- Comment #41 from Holger ---
(In reply to Boudewijn Rempt from comment #33)
> That used to be the way Krita imported/exported images. It was not a huge
> success, and we moved away to using libpng etc. directly.
But libpng is png only, right? OTH
https://bugs.kde.org/show_bug.cgi?id=360821
--- Comment #40 from maderios ---
@Christoph Feck
Libmagick is required by 16 Arch package, whose ImageMagick, Transcode,
Cuneiform, Sk1, Converseen...
https://www.archlinux.org/packages/extra/x86_64/libmagick/
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=360821
--- Comment #39 from Christoph Feck ---
Packages depend on the ImageMagick binary, not the libraries.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=360821
--- Comment #38 from Boudewijn Rempt ---
Either they don't care, or they have the manpower to follow the api changes, or
whatever. I'm not here to argue with you: I give you the benefit of my
experience with ImageMagick, but if you want to come up with
https://bugs.kde.org/show_bug.cgi?id=360821
--- Comment #37 from maderios ---
(In reply to Boudewijn Rempt from comment #35)
> The ImageMagick API's are very unstable: there is no guarantee of source
> compatibility between versions.
In this case, why 91 softwares (see Arch IM page) depend on
https://bugs.kde.org/show_bug.cgi?id=360821
--- Comment #36 from caulier.gil...@gmail.com ---
Ah yes, i hear about the IM vs GM story.
IM XCF codec is here :
https://github.com/ImageMagick/ImageMagick/blob/master/coders/xcf.c
Gilles Caulier
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=360821
--- Comment #35 from Boudewijn Rempt ---
The ImageMagick API's are very unstable: there is no guarantee of source
compatibility between versions. That's why GraphicsMagick was created back in
the days, but that fell behind. It was a huge maintenance
https://bugs.kde.org/show_bug.cgi?id=360821
--- Comment #34 from caulier.gil...@gmail.com ---
ImageMagick C++ API have been a problem ? Which one exactly ? The IM C++
exception no compatible with Qt ?
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=360821
--- Comment #33 from Boudewijn Rempt ---
That used to be the way Krita imported/exported images. It was not a huge
success, and we moved away to using libpng etc. directly.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=360821
--- Comment #32 from Holger ---
@Gilles
I love that suggestion, as it will also solve the long-standing SVG issue: bug
336436
Hope I'm not the april fool now!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=360821
--- Comment #31 from caulier.gil...@gmail.com ---
To replace whole image format supported by KImageFormat certainly no, but to
call ImageMagick C++ API to get the big advantage to render plenty of image
formats, yes...
https://bugs.kde.org/show_bug.cgi?id=360821
--- Comment #30 from Albert Astals Cid ---
You can't replace kimageformats with imagemagick, that simply makes no sense
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=360821
--- Comment #29 from maderios ---
If I understand:
- For three years, Kimageformats can't diplay xcf files (except old gimp files)
- ImageMagick can display all xcf files (I tested it)
Replacing Kimageformats by ImageMagick could be a good way to solve
https://bugs.kde.org/show_bug.cgi?id=360821
Boudewijn Rempt changed:
What|Removed |Added
Summary|Show xcf files (from Gimp |Gimp 2.10 xcf files cannot
23 matches
Mail list logo
