Bug 83844 - FILEOPEN DOCX: HangingChars indent (and other *Chars indent variants) not parsed on import
Summary: FILEOPEN DOCX: HangingChars indent (and other *Chars indent variants) not par...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: All All
: low minor
Assignee: Not Assigned
Whiteboard: BSA
Keywords: filter:doc
Depends on:
Blocks: CJK DOC
  Show dependency treegraph
Reported: 2014-09-14 13:35 UTC by oversky0
Modified: 2020-08-01 11:39 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:
Regression By:

Word file has wrong format. (29.40 KB, application/msword)
2014-09-14 13:35 UTC, oversky0
Word 2007 vs LibO 4.3 (442.05 KB, image/png)
2014-09-14 18:02 UTC, Yousuf Philips (jay) (retired)

Note You need to log in before you can comment on or make changes to this bug.
Description oversky0 2014-09-14 13:35:37 UTC
Created attachment 106262 [details]
Word file has wrong format.

Problem description: 
See the following pictures.
Steps to reproduce:
Open the attached file.

Current behavior:
Expected behavior:

Operating System: Windows 7
Version: release
Comment 1 Yousuf Philips (jay) (retired) 2014-09-14 18:01:30 UTC
Hello oversky0,

Thank you for submitting the bug. I can confirm that the two bugs are available in 4.2.6 and 4.3.3 on Linux, but as we can only fix a single bug per bug report, i will go with incorrect paragraph indentation.

In LibO:
Before Text Indent: 17.09 cm
After Text Indent: -38.79 cm
First Line Indent: -38.79 cm

In MS Word:
Left : 0"
Right: 0"
Special: Hanging 5ch

It should also be noted that 3.3.0, 3.6.7 and 4.4 master states that the .doc file is corrupt and couldnt open it.

Build ID: f3cdb7804a26c5cf0623d9b83130594f83372768
TinderBox: Linux-rpm_deb-x86@45-TDF, Branch:libreoffice-4-3, Time: 2014-09-12_04:11:44
Comment 2 Yousuf Philips (jay) (retired) 2014-09-14 18:02:17 UTC
Created attachment 106279 [details]
Word 2007 vs LibO 4.3
Comment 3 Xisco Faulí 2015-09-09 09:43:50 UTC
This issue is still present in

Build ID: 81898c9f5c0d43f3473ba111d7b351050be20261
Locale: es-ES (es_ES)

on Windows 7 (64-bit)
Comment 4 Robinson Tryon (qubit) 2015-12-14 06:00:18 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2017-12-10 16:41:08 UTC Comment hidden (obsolete)
Comment 6 Cor Nouws 2017-12-28 22:49:25 UTC
partiallay improved in 
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

@oversky0@hotmail.com: can you please look at the issue and specify the current problem?
Comment 7 QA Administrators 2019-01-26 03:48:19 UTC Comment hidden (obsolete)
Comment 8 Timur 2019-01-28 14:37:06 UTC
If bug is about "wrong position" for those 1) and 2) then:
- LO 6.3+ opens it as reported,
- but LO opens fine same DOC/DOCX if resaved in MSO. 
We may regard this as a wrong DOC or that LO should open it like MSO. Although I'm not an optimist in cases like this one.

As for "should read 12" it's still as reported. 
MSO setting is Centered, Indentation 0 cm, Special Hanging 0,79 cm.
LO opens as Before text 0,79 cm, After text 0 cm, First line 0,79 cm.
I'd say it's now reported as Bug 108493.
Comment 9 Timur 2020-07-31 18:12:51 UTC
Attached DOC is really DOCM and it can be edited.
If we remove the following, that line opens correctly:
<w:ind w:left="31680" w:hangingChars="500" w:firstLine="31680"/>

So, somehow this file was created wrongly but MSO fixes that and saves properly, so that LO opens it fine next time.
Comment 10 Justin L 2020-08-01 11:39:49 UTC
MS documentation says that hangingChars (in 100th of a character) supersedes firstLine (and hanging). So for sure firstLine should be ignored. It looks like we don't import hangingChars - it is just skipped, and so are all of the other *Chars versions of indent:

The documentation does not specify the existence of w:left for w:ind, although LO has support for both left and right as well as start and end.

Does LO even know how to use a distance measurement of "char"? (I guess so, because I have seen it used in the UI.) I didn't see the definition of it in the documentation I was using.