Bug 148174 - FILEOPEN DOCX Ref field incorrect with "Paragraph # in full context" and "Relative position of paragraph" enabled
Summary: FILEOPEN DOCX Ref field incorrect with "Paragraph # in full context" and "Rel...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: DOCX-Fields
  Show dependency treegraph
 
Reported: 2022-03-25 07:59 UTC by Gabor Kelemen (allotropia)
Modified: 2024-04-09 03:13 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
The paragraph numbered 10 in Word and Writer (163.31 KB, image/png)
2022-03-25 07:59 UTC, Gabor Kelemen (allotropia)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gabor Kelemen (allotropia) 2022-03-25 07:59:41 UTC
Created attachment 179097 [details]
The paragraph numbered 10 in Word and Writer

This is a followup to bug 145215

attachment 175829 [details] contains some example fields on page 51 under title "Schedule 99"

Many of these are appearing the same as in Word, this report focuses on the "Ref" field of paragraph 10.

The common pattern in the paragraphs 8-10 is they have the field option "Relative position of paragraph" enabled.
Since this option is not supported in Writer, all of these are mapped to the option "Above/below".

The paragraph 4 has the same field settings except this "Relative position of paragraph" setting is disabled.

Paragraph 10 has the "Paragraph # in full context" plus "Relative position of paragraph" which results in "2.2.1 (i) above" in Word. This is imported incorrectly as "above" in Writer.
Paragraph 4 has only the "Paragraph # in full context" field option enabled, which results in "2.2.1 (i)" in Word. This is imported correctly in Writer.
-> Writer should have a similar option for the Bookmarks field that gives the referenced bookmarks position in full context.

Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: a2c3ef6d8108355ce5daf6ff72310ac93ae745f0
CPU threads: 14; OS: Windows 10.0 Build 19044; UI render: default; VCL: win
Locale: en-US (hu_HU); UI: en-US
Calc: threaded Jumbo
Comment 1 Dieter 2022-04-09 11:39:01 UTC
I confirm it with

Version: 7.3.2.2 (x64) / LibreOffice Community
Build ID: 49f2b1bff42cfccbd8f788c8dc32c1c309559be0
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: zh-CN (de_DE); UI: en-GB
Calc: CL
Comment 2 QA Administrators 2024-04-09 03:13:21 UTC
Dear Gabor Kelemen (allotropia),

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