Description: With Bug 59699, the INCLUDEPICTURE command has been partly fixed, such that RTF documents with a linked image will generally display the linked image. However, it seems that only PNG files (such as the one linked in the attachment of the mentioned bug report) show up correctly, while (all/some?) JPG files are inserted as a tiny thumbnail only. Comment 14 of the mentioned bug also indicates this problem, but AFAIK, there has not been a follow-up bug report. To reproduce, I created a 200x200 pixel sample image and saved it in PNG and JPG format. I created an RTF file with the following code: {\rtf1 JPG {\field{\*\fldinst{ INCLUDEPICTURE "C:\\\\Temp\\\\sample.jpg" \\* MERGEFORMAT \\d}}{\fldrslt}} \par PNG {\field{\*\fldinst{ INCLUDEPICTURE "C:\\\\Temp\\\\sample.png" \\* MERGEFORMAT \\d}}{\fldrslt}} \par } (Paths must be adjusted upon reproducing). When opening the file in MS Word, both pictures show up with the same size. When opening with LibreOffice Writer, the PNG shows up at its normal size, but the JPG is just a small, say 5x5 px, rectangle. When opening the properties of the JPG file, the size information is set to 0.04cm, but when clicking on "original size", the actual size of the image seems to appear and after that the PNG and JPG files are of the same size. I have also tried saving the raw RTF file quoted above as a LibreOffice RTF file. This will embed both images and I noticed that the \picscalex and \picscaley of the JPG is 0, but 100 for the PNG. Maybe this is the origin of the problem? The embedded picture headers are: JPG: \picscalex0\picscaley0\piccropl0\piccropr0\piccropt0\piccropb0\picw200\pich200\picwgoal4050\pichgoal4050\jpegblip PNG: \picscalex100\picscaley100\piccropl0\piccropr0\piccropt0\piccropb0\picw200\pich200\picwgoal4049\pichgoal4049\pngblip Steps to Reproduce: 1. Create sample image and save as PNG and JPG 2. Create RTF file linking both images (see MWE in the description) 3. Open RTF in LibreOffice writer Actual Results: PNG is displayed correctly, JPG is shown as very small thumbnail. Expected Results: Linked JPG and PNG show the same image with the same size. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.4.3.2 (x64) / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 16; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: CL
Created attachment 184176 [details] Minimal working example
I confirm the problem with Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 376152fbd110cdc0a2cde1fa9758f36c016d9352 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (de_DE); UI: en-GB Calc: CL threaded Steps: 1. Open sample_saved_with_writer from attachment 184176 [details] cc: Miklos Vajna Miklos, since you've fixed bug 59699, you might be interested in this
Dear libreoffice, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still present Version: 25.2.2.1 (X86_64) / LibreOffice Community Build ID: 38d746d66d9b82fa248a2e90142b9dd3ddd1d6cd CPU threads: 12; OS: Windows 11 X86_64 (10.0 build 22631); UI render: Skia/Vulkan; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL threaded