Bug 77764 - FILEOPEN XML Content goes outside page area on Linux
Summary: FILEOPEN XML Content goes outside page area on Linux
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.2.3.3 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: MSO-XML2003
  Show dependency treegraph
 
Reported: 2014-04-22 11:30 UTC by shaman
Modified: 2023-09-24 03:15 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
files (776.50 KB, application/x-tar)
2014-04-22 11:30 UTC, shaman
Details

Note You need to log in before you can comment on or make changes to this bug.
Description shaman 2014-04-22 11:30:37 UTC
Created attachment 97741 [details]
files

test.xml differently file opens in Writer for Windows and Linux, see screen shot. I do not know how to solve it. 
Versions downloaded from https://ru.libreoffice.org/download/
Comment 1 retired 2014-05-07 14:13:43 UTC
Confirmed > NEW

On OSX and Windows displays ok, while on Ubuntu 14.04 the right side is not ended and display of document differs.
Comment 2 Matthew Francis 2014-08-17 14:28:02 UTC
Attempted to reproduce this while following up some other font related issues

On a fresh install of Ubuntu 14.04 with updates (-> LO 4.2.4.2), this looks OK to me
Comment 3 QA Administrators 2015-09-04 02:49:28 UTC Comment hidden (obsolete)
Comment 4 Buovjaga 2015-11-30 13:37:57 UTC
Still confirmed.

Ubuntu 15.10 64-bit 
Version: 5.0.3.2
Build ID: 1:5.0.3~rc2-0ubuntu1
Locale: en-US (en_US.UTF-8)
Comment 5 QA Administrators 2017-01-03 19:36:10 UTC Comment hidden (obsolete)
Comment 6 Thomas Lendo 2019-09-22 18:13:54 UTC
This is not a right bug report.
Nobody will ever 'fix' this (except by accident with fixing other bugs) as description of what is wrong is missing or steps to reproduce. A bug mix is not the right way to get something fixed.

Closing as INVALID due to the age.
Please reopen as NEW if you've other opinion with steps to reproduce ond a file created with a current version of LibreOffice that shows this bug(s).
Comment 7 Buovjaga 2019-09-23 06:40:37 UTC
Still confirmed on Linux, improved summary.

The XML type is

<?mso-application progid="Word.Document"?>
<w:wordDocument xmlns:w="http://schemas.microsoft.com/office/word/2003/wordml" xmlns:v="urn:schemas-microsoft-com:vml" xmlns:w10="urn:schemas-microsoft-com:office:word" xmlns:sl="http://schemas.microsoft.com/schemaLibrary/2003/core" xmlns:aml="http://schemas.microsoft.com/aml/2001/core" xmlns:wx="http://schemas.microsoft.com/office/word/2003/auxHint" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" w:macrosPresent="no" w:embeddedObjPresent="no" w:ocxPresent="no" xml:space="preserve">

Arch Linux 64-bit
Version: 6.4.0.0.alpha0+
Build ID: b9a776837462eeb6d50d0decc42604c0c3008eb1
CPU threads: 8; OS: Linux 5.2; UI render: default; VCL: kf5; 
Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US
Calc: threaded
Built on 11 August 2019
Comment 8 QA Administrators 2021-09-23 03:33:35 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2023-09-24 03:15:10 UTC
Dear shaman,

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