<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED DUPLICATE - IMAGE: Copy and paste a cropped image from LO to Tunderbird or MSWord has uncropped image as result"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=139398#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED DUPLICATE - IMAGE: Copy and paste a cropped image from LO to Tunderbird or MSWord has uncropped image as result"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=139398">bug 139398</a>
from <span class="vcard"><a class="email" href="mailto:simonswim@belgacom.net" title="simonswim@belgacom.net">simonswim@belgacom.net</a>
</span></b>
<pre>@heiko tietze,
added comment, about the functionalities,
-concern-1 security & privacy
after further evaluation in my opinion whatever solution should automatcally
restrict the copy of an image to WYSWYG as a requirement,
i understand that this does mean ELEMINATE attributes
rational: in 99% of cases - users that did modify an imgae (crop or compress
or . . . ) do intentionly remove the not-visible content
compare this operation with usage of image-processing software,
- then one uses a step/step method such that:
-- in each step you manipulate the image with ability to evaluatie/undo the
effect untill one is happy,
-- then we hit the "save" image button, NO way back
the intention for 82951 was to reduce the total size of the document,
so after the manipulation the image is WYSWYG
from the comment by dieter i do understand that 82951 is not solved,
- looking forward for the enhancement - wim</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>