Am 05.02.2013 um 09:27 schrieb Martin Costabel:
> The question is whether the octave programmers misunderstood this only in
> their warning text or also in the octave code.
Another question also exists: how do Octave and GraphicsMagick interchange
graphics data? Is it by standard file formats (in memory or on disk) or is it
via an API? In the first case the differences in pixel resolution should not
play any role, because *standard* (external) data formats are used. (PNG is
PNG, no matter if it's 1 bit or 64 bit deep. Each such object is identifying
itself by a header, so writer and reader have the exact knowledge of the object
and GraphicsMagick – and also Octave – can use internally whatever format it
wishes or prefers to use for its own private working representation of the
external graphics object.) If the data exchange works via APIs then both users
of this API might have to stick to some agreed upon value – if there's no way
to negotiate via the API this value.
--
Greetings
Pete
If it dies, it's biology. If it blows up, it's chemistry. If it doesn't work,
it's physics.
– University washroom sgraffito
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Fink-users mailing list
[email protected]
List archive:
http://news.gmane.org/gmane.os.macosx.fink.user
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users
