Bug 93607 - text:id in <text:alphabetical-index-mark-start/> changes when saving
Summary: text:id in <text:alphabetical-index-mark-start/> changes when saving
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.0.0.5 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Concordance-File
  Show dependency treegraph
 
Reported: 2015-08-23 18:37 UTC by Jos van den Oever
Modified: 2023-04-23 18:44 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
A file with <text:alphabetical-index-mark-start/> and <text:alphabetical-index-mark-end/>. Loading and saving this file gives new values for the attribute text:id. (18.46 KB, application/xml)
2015-08-23 18:37 UTC, Jos van den Oever
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jos van den Oever 2015-08-23 18:37:19 UTC
Created attachment 118105 [details]
A file with <text:alphabetical-index-mark-start/> and <text:alphabetical-index-mark-end/>. Loading and saving this file gives new values for the attribute text:id.

Saving a document with <text:alphabetical-index-mark-start/> and <text:alphabetical-index-mark-end/> give a new value for the text:id attribute. 

This is inconvenient when comparing different version of the document. The diff is larger than it needs to be. The value of the text:id attribute should not change when the file is edited.

The values of the text:id attribute can be quickly seen:

xmlstarlet fo test.fodt | xmlstarlet sel -t -m '//text:alphabetical-index-mark-start/@text:id' -v . -n
Comment 1 Buovjaga 2015-09-12 15:42:54 UTC
Confirmed.

Win 7 Pro 64-bit, Version: 5.0.1.2 (32-bit)
Build ID: 81898c9f5c0d43f3473ba111d7b351050be20261
Locale: fi-FI (fi_FI)
Comment 2 QA Administrators 2016-09-20 10:32:22 UTC Comment hidden (obsolete)
Comment 3 Jos van den Oever 2016-09-20 11:50:16 UTC
This bug is still present in LibreOffice 5.1.2 on Linux 4.4.
Comment 4 Xisco Faulí 2017-09-29 08:53:28 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2019-12-03 14:45:04 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2021-12-03 04:39:44 UTC
Dear Jos van den Oever,

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