[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #44118] imwrite saves wrong pixel values into
From: |
H. G. |
Subject: |
[Octave-bug-tracker] [bug #44118] imwrite saves wrong pixel values into jpg file |
Date: |
Fri, 30 Jan 2015 19:36:02 +0000 |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:35.0) Gecko/20100101 Firefox/35.0 |
Follow-up Comment #7, bug #44118 (project octave):
For me it sounds reasonable that Octave uses some kind of library for the
import and export of image files. And I don't have enough expertise to judge
if GraphicsMagick is the right library for Octave or not.
I also have not the knowledge and time to switch the Octave code over to a
different image format library, nor the money to pay someone to do this.
I personally can live with this behavior, I'll just use a different file
format then. But I also want Octave to be a useful and competitive tool for
more other people, and do quite some advertising for it. That's why I like to
look for feasable ways to improve Octave, and that's why I file bug reports
here.
In my opinion properly saving a grayscale jpg file should be a routine task
for an image file library, it doesn't sound too exotic. Therefore: Might there
be a possibility that we can get the GraphicsMagick developers to change /
correct this in their library? Can we file a useful bug report for
GraphicsMagick somewhere and then hope?
(Or might there still be some parameter for GraphicsMagick that we do not use
properly in our code, I guess it's in __magick_read__.cc ?)
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?44118>
_______________________________________________
Nachricht gesendet von/durch Savannah
http://savannah.gnu.org/