Bug 78405 - FILEOPEN: WPS DOC - Image size not correct (fixed by round-tripping in MSO)
Summary: FILEOPEN: WPS DOC - Image size not correct (fixed by round-tripping in MSO)
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:doc
Depends on:
Blocks: DOC-Images
  Show dependency treegraph
 
Reported: 2014-05-07 21:57 UTC by Yousuf Philips (jay) (retired)
Modified: 2025-06-01 03:10 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
the .doc file created in kingsoft writer (164.50 KB, application/msword)
2014-05-07 21:57 UTC, Yousuf Philips (jay) (retired)
Details
how it looks in 4.0 to 4.3 (23.83 KB, image/jpeg)
2014-05-07 21:57 UTC, Yousuf Philips (jay) (retired)
Details
how it looks in 3.6 (27.50 KB, image/jpeg)
2014-05-07 21:58 UTC, Yousuf Philips (jay) (retired)
Details
how it looks in word 2010 (10.97 KB, image/jpeg)
2014-05-07 21:58 UTC, Yousuf Philips (jay) (retired)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Yousuf Philips (jay) (retired) 2014-05-07 21:57:10 UTC
Created attachment 98642 [details]
the .doc file created in kingsoft writer

I opened up kingsoft writer and in a blank document imported an image, resized and centered it. Then i wrote a line of text and save the file as a .doc. Then i opened it up in LibO and the image is shown starting from the left margin and stretching past the right margin, is unresized and cropped. This was tested on Linux Mint on the latest releases of 4.0 to 4.2 as well as 4.3 alpha. In the latest 3.6, its resize from the left to right margin. The .doc opened correctly in kingsoft and word 2010.
Comment 1 Yousuf Philips (jay) (retired) 2014-05-07 21:57:48 UTC
Created attachment 98643 [details]
how it looks in 4.0 to 4.3
Comment 2 Yousuf Philips (jay) (retired) 2014-05-07 21:58:08 UTC
Created attachment 98644 [details]
how it looks in 3.6
Comment 3 Yousuf Philips (jay) (retired) 2014-05-07 21:58:25 UTC
Created attachment 98645 [details]
how it looks in word 2010
Comment 4 tommy27 2014-05-09 11:49:09 UTC
I confirm FILEOPEN issue under Win7x64 using LibO 4.2.3.3 4.3.0.0.alpha1+
Build ID: 657004ae5c9f4a07b2cdafbb21bc8657842d4d74
TinderBox: Win-x86@39, Branch:master, Time: 2014-05-08_00:35:12

status -> NEW
Comment 5 tommy27 2014-05-09 11:50:30 UTC
@Jay
is that image issue extension dependant?
I mean, does it happens with any kind of images or just with some types?
the image in the document was a .png, right?
Comment 6 Yousuf Philips (jay) (retired) 2014-05-09 17:23:11 UTC
no not extension dependant. it was a png but i just tested it with a jpg and same issue. are there any other extensions you'd like me to test it on?
Comment 7 tommy27 2014-05-09 17:50:29 UTC
no it's enough... if it's buggy with such common formats it probably have the same issue with other formats as well
Comment 8 QA Administrators 2015-06-08 14:42:46 UTC Comment hidden (obsolete)
Comment 9 Yousuf Philips (jay) (retired) 2015-06-10 06:39:49 UTC
Still present.

Version: 5.1.0.0.alpha1+
Build ID: 782c116b5ac39aef27c3a00f7fc145c9f755e3a3
TinderBox: Linux-rpm_deb-x86@45-TDF, Branch:master, Time: 2015-06-09_23:59:00
Comment 10 Robinson Tryon (qubit) 2015-12-09 18:43:17 UTC Comment hidden (obsolete)
Comment 11 Yousuf Philips (jay) (retired) 2017-09-29 20:00:44 UTC
Still repo.

Version: 6.0.0.0.alpha0+
Build ID: 115bed941d7b7ed1b95d6424bfb98456c1d87546
CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk2; 
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-09-06_22:52:59
Locale: en-US (en_US.UTF-8); Calc: group
Comment 12 QA Administrators 2018-09-30 02:49:58 UTC Comment hidden (obsolete, spam)
Comment 13 Justin L 2020-04-16 17:05:14 UTC
repo 7.0+
However, if I round-trip it with MS Word 2003, then the size is normal. So do we really care?
Comment 14 QA Administrators 2022-07-26 03:29:28 UTC Comment hidden (obsolete, spam)
Comment 15 Justin L 2023-05-27 01:44:50 UTC
repro 7.6+
Comment 16 QA Administrators 2025-06-01 03:10:52 UTC
Dear Yousuf Philips (jay) (retired),

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