Bug 81887 - Fileopen: Vertical text with fixed spacing from DOC/DOCX not displayed correctly in table
Summary: Fileopen: Vertical text with fixed spacing from DOC/DOCX not displayed correc...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords: filter:docx
Depends on:
Blocks: DOCX-Tables
  Show dependency treegraph
 
Reported: 2014-07-29 21:40 UTC by freeman3
Modified: 2023-09-26 03:14 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:


Attachments
Sample doc file (453.00 KB, application/msword)
2014-07-29 21:40 UTC, freeman3
Details
Screnshot bad columns (19.10 KB, image/png)
2014-08-04 14:55 UTC, freeman3
Details
PDF export of LibO 4.3.1 (top) VS Word 2007 (bottom) (264.07 KB, image/png)
2014-08-04 22:59 UTC, Yousuf Philips (jay) (retired)
Details
Sample DOC reduced to 1-page table (344.14 KB, application/msword)
2017-08-22 13:13 UTC, Timur
Details
Test DOCX (13.07 KB, application/wps-office.docx)
2017-08-22 13:25 UTC, Timur
Details
Original bugdoc in current 6.5 (119.85 KB, image/png)
2020-03-30 11:55 UTC, NISZ LibreOffice Team
Details
Simplified docx example in current 6.5 (130.45 KB, image/png)
2020-03-30 12:14 UTC, NISZ LibreOffice Team
Details
this is how I see the heading (62.82 KB, image/png)
2021-08-23 12:53 UTC, BogdanB
Details

Note You need to log in before you can comment on or make changes to this bug.
Description freeman3 2014-07-29 21:40:07 UTC
Created attachment 103657 [details]
Sample doc file

Problem description: 
Forms created in MS Word are not displayed correctly in LO. Attaching sample file, see page 3. Column title are not readable, some filds in form are not selectable

Steps to reproduce:
1. Open sample file
2. ....
3. ....

Current behavior:

Expected behavior:
Forms should look the same as i MS office
              
Operating System: All
Version: 4.2.2.1 release
Comment 1 Yousuf Philips (jay) (retired) 2014-08-04 03:37:09 UTC
Hello freeman3,

Thank you for submitting the bug. Can you specify which column has fields that are not selectable, possibly with a screenshot.
Comment 2 freeman3 2014-08-04 14:55:57 UTC
Created attachment 103999 [details]
Screnshot bad columns

hello
unclickable form fields are in some other file, i have to to find it first.
what about column titles? can you see it correctly?
attaching screenshot how it look on my computer
Comment 3 Yousuf Philips (jay) (retired) 2014-08-04 22:59:10 UTC
Created attachment 104029 [details]
PDF export of LibO 4.3.1 (top) VS Word 2007 (bottom)

Hi freeman3,

Yes i see there is a problem with the vertical table header text on page 3, similar to your attachment. I have attached how the PDF export looks like, as it isnt render well there as well.
Comment 4 QA Administrators 2015-09-04 02:49:46 UTC Comment hidden (obsolete)
Comment 5 Buovjaga 2015-11-30 13:56:56 UTC
Still confirmed.

Win 7 Pro 64-bit Version: 5.2.0.0.alpha0+
Build ID: a7c3a2a9be83686657c06f37d521f9f6d2004ddd
Threads 4; Ver: Windows 6.1; Render: default; 
TinderBox: Win-x86@39, Branch:master, Time: 2015-11-28_04:39:18
Locale: fi-FI (fi_FI)
Comment 6 Robinson Tryon (qubit) 2015-12-09 18:47:49 UTC Comment hidden (obsolete)
Comment 7 Timur 2017-08-22 13:13:47 UTC
Created attachment 135730 [details]
Sample DOC reduced to 1-page table

This is not a correct bug report. 
Title "VIEWING: Forms in writer are not displayed correctly" is too general because forms are displayed fine. Text content in table is not, but it's not because of write-protect. 
To check text is there: Ctrl+A and Ctrl+C in cell to copy text, Ctrl+V in other document, clear formatting, text is there.
To confirm, I attach Sample DOC unprotected and reduced to 1-page table.
Comment 8 Timur 2017-08-22 13:25:02 UTC
Created attachment 135731 [details]
Test DOCX

Same for DOC and DOCX, problem comes from vertical text with fixed spacing, as shown on attached test DOCX.
Comment 9 QA Administrators 2018-08-23 02:42:03 UTC Comment hidden (obsolete, spam)
Comment 10 NISZ LibreOffice Team 2020-03-30 11:55:47 UTC
Created attachment 159144 [details]
Original bugdoc in current 6.5

With recent improvements in BTLR handling the original document looks rather good with:

Version: 7.0.0.0.alpha0+ (x64)
Build ID: bc898e2c2784e36ad4d4cdf6d962e39069d2c82d
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win; 
Locale: hu-HU (hu_HU); UI-Language: en-US
Calc: CL

The rotated text is still not (partially) bold though.
Comment 11 NISZ LibreOffice Team 2020-03-30 12:14:34 UTC
Created attachment 159147 [details]
Simplified docx example in current 6.5

Attachment #135731 [details] in current master is still not the same as in Word:

Version: 7.0.0.0.alpha0+ (x64)
Build ID: bc898e2c2784e36ad4d4cdf6d962e39069d2c82d
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win; 
Locale: hu-HU (hu_HU); UI-Language: en-US
Calc: CL

The problem is that the second tables first cell ("Vertical text with fixed spacing") has settings that make the text appear in Word until the word "fixed". As you can see it is right at the vertical cell separator line, as if the internal cell padding were ignored.

Writer on the other hand shows the word "fixed" cut vertically in half.

In this picture I had manually changed the imported 0.19 cm right cell padding to 0 and boom: the word "fixed" appears fully, like in Word.

Of course we get the red triangle too, since there is one more word in the cell.
Comment 12 NISZ LibreOffice Team 2020-03-30 12:19:17 UTC
Changing meta bug to writer-tables
Comment 13 BogdanB 2021-08-23 12:53:59 UTC
Created attachment 174490 [details]
this is how I see the heading

Version: 7.3.0.0.alpha0+ / LibreOffice Community
Build ID: 5b025285b3528910a4360899abb2bbbaadc72c97
CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded
Comment 14 QA Administrators 2023-09-26 03:14:27 UTC
Dear freeman3,

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