Bug 103206 - FILEOPEN: Vertical numbers (added with a table/frame in the header) missing from left margin in DOCX (Pleading document)
Summary: FILEOPEN: Vertical numbers (added with a table/frame in the header) missing f...
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: interoperability
Keywords: bibisected, bisected, filter:docx
Depends on: 90534 103208
Blocks: DOCX-Frames DOCX-Header-Footer
  Show dependency treegraph
 
Reported: 2016-10-14 04:28 UTC by Robinson Tryon (qubit)
Modified: 2023-05-17 16:14 UTC (History)
12 users (show)

See Also:
Crash report or crash signature:


Attachments
screen shot showing situation in Word with Table/frame in header that is used for numbers and lines... (78.90 KB, image/png)
2016-10-14 13:12 UTC, Cor Nouws
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Robinson Tryon (qubit) 2016-10-14 04:28:27 UTC
+++ This bug was initially created as a clone of Bug #90534 +++

The court requires documents to have the numbers 1-28 in the left margin. (Word puts these in the header.)

Attachment 114701 [details] is a DOCX document that includes said line numbers as expected by the courts.

Here's how it looks in Mac Word 2011:  attachment 114709 [details]
Here's how it looks in a recent build of 5.3 alpha0: attachment 127334 [details]

In LibreOffice, the line numbers are missing.
Comment 1 Cor Nouws 2016-10-14 07:25:39 UTC
Indeed, this docx file opens broken, different. 
But no, it is not related to the format required by the court - one could get the needed result in another way too.

Even more broken in 3.3.0.4

wrt severity: Just a 'normal' formatting issue
Comment 2 Cor Nouws 2016-10-14 13:12:54 UTC
Created attachment 128005 [details]
screen shot showing situation in Word with Table/frame in header that is used for numbers and lines...
Comment 3 QA Administrators 2017-12-10 16:40:16 UTC Comment hidden (obsolete)
Comment 4 Cor Nouws 2017-12-28 22:54:05 UTC
still wrong in 
Version: 6.1.0.0.alpha0+
Build ID: a9b202a6b7000e7af34f2a639ca207122a3968bf
CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk2; 
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-12-26_23:09:36
Locale: nl-NL (nl_NL.UTF-8); Calc: group threaded
Comment 5 QA Administrators 2018-12-29 03:49:31 UTC Comment hidden (obsolete)
Comment 6 Timur 2020-01-17 13:47:32 UTC
Repro 6.5+.
Comment 7 NISZ LibreOffice Team 2020-05-19 15:59:52 UTC
In Word there is a very extreme paragraph in the header:
- it has Line Spacing of 792 pt at least. This makes it as tall as the whole page (visually this value is similar to a spacing above the paragraph), so the frame containing the table containing line numbers and double line right border fits.
- It has left and right vertical borders so that they are visible on the whole page.

The line spacing pushes the header to be an "overlay" over the whole page content. This does not happen when the file is opened in Writer.

The 792 pt line spacing is similar to what we saw in bug #122628 - Writer has a 10 cm (283 pt) hard limit on it too so 792 pt is imported as 10 cm.

The frame that wraps the table is not imported, only the table in it.
Writer then tries to display the page-sized tall table first, and after that the page tall paragraph with the left-right side borders - and all these in a 0 cm tall header.

These thing can be made visible after increasing the header height to 15 cm and gradually removing the tables contents.
Comment 8 Xisco Faulí 2020-11-10 10:15:39 UTC
The vertical numbers are displayed if https://cgit.freedesktop.org/libreoffice/core/commit/writerfilter?id=bdd4a238a1d8a0cbbebbd759011050659668f92b is reverted

@Justin Luth, since you wrote the commit mentioned, any idea of what is going on here ?
Comment 9 Justin L 2020-11-10 10:28:51 UTC
(In reply to Xisco Faulí from comment #8)
> @Justin Luth, since you wrote the commit mentioned, any idea of what is
> going on here ?
I would assume that in this case a default value just happens to work better than the specified values. That commit just says don't stop processing property values just because one of them has an error. That commit won't help anyone at all, unless there are only a FEW values that would be skipped by the problematic one.
Comment 10 QA Administrators 2022-11-27 03:37:31 UTC Comment hidden (obsolete, spam)
Comment 11 Justin L 2023-05-17 16:14:48 UTC
Basically, someone did all kinds of monkeying around to get a document to look the way they want in MS Word. But this isn't really word processing (comment 1).

This is a prime example of "it is time to redesign your document".