Created attachment 67719 [details] Meeting minutes, with captured text image on page 3. An imported docx file has an imported image (scanned text). This displays correctly in the edit window. In the print preview the image is enlarged and clipped. When printed (HP D7160) it is reduced to about 20%. I have also printed the file to SnagIt (image capture). In this case it is reduced to about 40%.
Confirmed with supplied sample document on openSUSE 12.2 (x86-64) with: - LO Version 4.0.0.0.alpha0+ (Build ID: 67fca3), pulled 19 November 2012. - LibreOffice 3.5:build-403 Build ID: 350m1(Build:403) Problem not confined to bitmaps. I can supply an example with a vector based graph that is also extremely enlarged when printed or exported to pdf.
When opening the sample document with Libre Office version 4.0.0.0.alpha0+ (Build ID: 56d3de), on openSUSE 11.4 (x86_64), build with --enable-symbols --enable-debug, the following waring appears several times: warn:svl.items:19480:1:/home/stephan/Software/libreoffice-master/core/svl/source/items/itempool.cxx:517: fuer Image, dort gibt es derzeit keine Statics - Bug When exporting to PDF the scanned page is not present in the PDF. Just an empty page. Same result with LO Version 3.6:build-302 (Build ID: 360m1(Build:302)) on openSUSE 11.4. When opening my DOCX with the vector based graph a similar warning appears: warn:legacy.osl:18226:1:/home/stephan/Software/libreoffice-master/core/oox/source/docprop/docprophandler.cxx:319: For now unexpected tags are ignored! warn:legacy.osl:18226:1:/home/stephan/Software/libreoffice-master/core/oox/source/helper/storagebase.cxx:74: StorageBase::StorageBase - missing base input stream warn:svl.items:18226:1:/home/stephan/Software/libreoffice-master/core/svl/source/items/itempool.cxx:517: fuer Image, dort gibt es derzeit keine Static
Reproducible with MASTER on Ubuntu 12.04 (32-bit): Version: 4.2.0.0.alpha0+ Build ID: c2530b02311c46529eed53ee688bf6c83ce4b86
Restricted my LibreOffice hacking area
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.