Bug 158028 - Newly created DOCX files do not remember border values after saving and quitting
Summary: Newly created DOCX files do not remember border values after saving and quitting
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.1.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: DOCX-Paragraph
  Show dependency treegraph
 
Reported: 2023-11-01 15:17 UTC by Camaleón
Modified: 2023-11-24 16:23 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
File1 is the offending DOCX file (5.15 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2023-11-02 07:22 UTC, Camaleón
Details
File2 is an ODT file working fine (10.87 KB, application/vnd.oasis.opendocument.text)
2023-11-02 07:23 UTC, Camaleón
Details
This how it looks DOCX file file after opening (1.98 KB, image/png)
2023-11-02 07:24 UTC, Camaleón
Details
This how it should render DOCX file file after opening (2.20 KB, image/png)
2023-11-02 07:24 UTC, Camaleón
Details
Screenshot with the style inspector on odt and docx. (253.41 KB, image/png)
2023-11-02 16:38 UTC, m_a_riosv
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Camaleón 2023-11-01 15:17:50 UTC
Description:
1. When I create a new LibreOffice Writer DOCX file, and set a border space for a paragraph to 0.1 inches, the setting is honored until I save the document as docx and close LO writer.

2. When I open the previously created docx file, the border spacing is not kept and revert back to 0 inches, so every time I close the file I have to set the borders again.

3. This behavior does not happen with ODT files (borders values are properly honored and kept after saving/close operations).

4. This happens on my Debian 11 (linux), 64 bits system, with XFCE DE, not sure if the same goes for Windows systems.

Steps to Reproduce:
1. Create a new DOCX file, select a bunch of text and set a border value for all of the sides (top, bottom, left and right) to 0,1 inches. The borders are properly applied.

2. Save the file as DOCX and quit Writer.

3. Open the file and check for the borders value of the text, they are now set to 0 (no borders at all).

Actual Results:
Borders values already set are missing (not kept), restore back to «0»

Expected Results:
Borders values already set are kept, after saving/closing docx file.


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.6.2.1 (X86_64) / LibreOffice Community
Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333
CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: gtk3
Locale: es-ES (es_ES.UTF-8); UI: es-ES
Calc: threaded
Comment 1 m_a_riosv 2023-11-01 19:08:09 UTC
Please attach the odt sample file.
Comment 2 Camaleón 2023-11-02 07:22:44 UTC
Created attachment 190598 [details]
File1 is the offending DOCX file
Comment 3 Camaleón 2023-11-02 07:23:38 UTC
Created attachment 190599 [details]
File2 is an ODT file working fine
Comment 4 Camaleón 2023-11-02 07:24:27 UTC
Created attachment 190600 [details]
This how it looks DOCX file file after opening
Comment 5 Camaleón 2023-11-02 07:24:58 UTC
Created attachment 190601 [details]
This how it should render DOCX file file after opening
Comment 6 m_a_riosv 2023-11-02 16:38:36 UTC
Created attachment 190622 [details]
Screenshot with the style inspector on odt and docx.

Seems direct format, it's really different, after save odt as docx.

Version: 7.6.1.2 (X86_64) / LibreOffice Community
Build ID: f5defcebd022c5bc36bbb79be232cb6926d8f674
CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL threaded

Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: d8326f1f54b2f4644b52fbfa7106eeeae6e5bb7b
CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL threaded
Comment 7 Piotr 2023-11-24 16:23:23 UTC
I saw a problem on version 6.1 on windows 10