Created attachment 120142 [details] image writer quality corrupted Insert an image in the Writer document, select a frame around it - image quality is corrupted! See examples in the files attached.
By "Frame" I understand you actually mean "Borders". If not, please give steps how to "add a frame to an image". I would not call what you show "corruption". It seems to have smoothed the edges in the image a bit. Maybe it is OpenGL doing it. Please attach an example file with both of your example images. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the document.
Created attachment 120413 [details] two images
(In reply to stasiascani from comment #2) > Created attachment 120413 [details] > two images Can't see any difference, when I look at the file. Not even the slight difference seen in your screenshots. Win 7 Pro 64-bit, Version: 5.0.3.2 (x64) Build ID: e5f16313668ac592c1bfb310f4390624e3dbfb75 Locale: fi-FI (fi_FI)
Created attachment 120421 [details] more examples Try to unframe the last image on the left and then frame it again. An image on the right is what I see exactly on the left. The letters and table lines are not sharp because the border was applied.
I can see the difference, both in Windows and Linux, with current 5.1.3.2 version. It's more noticeable if the border width is increased. The reason for that is the image with the border has to take up exactly the same area as the one without borders (set in right click -> Format Image... -> Type). Therefore the image itself becomes a bit smaller, that's why the quality looks worse. That is not a bug. I guess it would be nice to have an option to set whether the border is on the inside of the edge (like now), outside the edge (what you're looking for, when the image itself isn't resized on a border width change), or centered over the edge. I'm closing the report as NOTABUG, but if you'd like to suggest this as an enhancement request, change status back to UNCONFIRMED.
All right, enhancement request it is.
Actually, this has already been reported as bug 90070. *** This bug has been marked as a duplicate of bug 90070 ***