https://issues.apache.org/ooo/show_bug.cgi?id=123295
Armin Le Grand <armin.le.gr...@me.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |armin.le.gr...@me.com
--- Comment #3 from Armin Le Grand <armin.le.gr...@me.com> ---
ALG: Indeed, as described. Checked the GdiMtfExporter, there is support for a
GraphicLink object in PdfExtOutDevData which is used here (metafile actions
with the correctly clipped graphic are ignored). That extra PDF export data is
created in VclMetafileProcessor2D::processBasePrimitive2D (before primitives
the stuff in svtools/source/graphic/grfmgr.cxx, see UnoControlPDFExportContact
was used).
It gets processed in pdfextoutdevdata.cxx where in
PDFExtOutDevDataSync::EndGroupGfxLink the extra data is read and used.
Interestingly in the preparation and in the usage a clip range is provided
additionally to the original range and used to set a clip region at the
PdfWriter, so this may be broken. Checking...
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
