<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - UI: Being able use the option 'Save' Image without conversion"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=138837#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - UI: Being able use the option 'Save' Image without conversion"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=138837">bug 138837</a>
from <span class="vcard"><a class="email" href="mailto:telesto@surfxs.nl" title="Telesto <telesto@surfxs.nl>"> <span class="fn">Telesto</span></a>
</span></b>
<pre>(In reply to V Stuart Foote from <a href="show_bug.cgi?id=138837#c2">comment #2</a>)
<span class="quote">> The source image is held in ODF archive, and is parsed to identify the image
> type.
>
> Wouldn't a direct extraction of the image from archive, bypassing the Save
> dialog's conversion, be the use case?</span >
Yes
--
More specific. I would be inclined to interpret "save" as store (as loseless).
I tend to see current implementation actually as export behaviour (depending of
file format). Even svg imaged are transformed (and save currently even break
things)
Extracting is the zip is not that conveniened.. not user friendly and kind of
technical.. Also not everybody is aware of impact of reconversion. Or needing
that.
And currently jpg export dialog not working properly (but that's more short
sighted argument (on state of instead of the long term vision). Pain point
especially dpi suggestion based on screen resolution. But in any case still
reconversion..</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>