Bug 68183 - FILESAVE: Disabling the creation of automatic RSID marks in automatic-styles is impossible
Summary: FILESAVE: Disabling the creation of automatic RSID marks in automatic-styles ...
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: Other All
: low minor
Assignee: Miklos Vajna
QA Contact:
Whiteboard: BSA target:4.5.0
Depends on:
Reported: 2013-08-16 12:22 UTC by Holger Schmithüsen
Modified: 2015-02-02 16:23 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Holger Schmithüsen 2013-08-16 12:22:49 UTC
Problem description:
When creating paragraphs using existing styles, Writer creates automatic styles for each individual paragraph (also for headings) in "content.xml" (document saved as odt or fodt) . This creates unnecessary and confusing overhead in the xml-file like:

<style:style style:name="P1" style:family="paragraph" style:parent-style-name="Text_20_body">
<style:text-properties officeooo:paragraph-rsid="00063317"/>
<style:style style:name="P2" style:family="paragraph" style:parent-style-name="Title">
<style:text-properties officeooo:paragraph-rsid="00063317"/>
<style:style style:name="T1" style:family="text">
<style:text-properties officeooo:rsid="00063317"/>

Whereas the actual content reads:

<text:p text:style-name="P2"><text:span text:style-name="T1">This is my title</text:span></text:p>
<text:p text:style-name="P1"><text:span text:style-name="T1">This is a text body paragraph.</text:span></text:p>

When manually removing direct formatting (by selecting all text and clicking "Format - Clear direct formatting"), the same information is stored already a bit cleaner, but still with the unused and useless style "T1":

<style:style style:name="T1" style:family="text">
<style:text-properties officeooo:rsid="00063317"/>

<text:p text:style-name="Title">This is my title</text:p>
<text:p text:style-name="Text_20_body">This is a text body paragraph.</text:p>

When manually reassigning the styles to each paragraph (by selecting each paragraph and double clicking on the respective style), the same information is stored straight and clean:


<text:p text:style-name="Title">This is my title</text:p>
<text:p text:style-name="Text_20_body">This is a text body paragraph.</text:p>

Steps to reproduce:
1. Open a new Writer document
2. Open the styles window (F11)
3. Select the style "Title"
4. Enter a title "This is my title"
5. Select the style "Text Body"
6. Enter a paragraph "This is a text body paragraph."
7. Save as odt or fodt: Three (unnecessary) automatic styles are saved
now either:
8a. Remove all direct formatting by clicking "Format - Clear direct formatting"
9a. Save again: The content is clean, but <office:automatic-styles> keeps the useless element named "T1".
or alternatively:
8b. Click in the title and then double click on the style "Title"
9b. Click in the text paragraph and then double click on the style "Text Body"
10b. Save again: This removes unnecessary automatic styles completely and saves the content nice and clean.

Current behavior:
See above steps 7. and 9a.

Expected behavior:
See above step 10b. This should be the default behaviour without doing steps 8b and 9b.

Thanks for improvement!
Operating System: All
Version: release
Comment 1 Urmas 2013-08-17 19:57:50 UTC
Those are not "useless" styles, they do carry revision ids.
Comment 2 Jean-Baptiste Faure 2013-08-18 06:12:57 UTC
Hi Cédric,

Do you confirm comment #1 ?

Best regards. JBF
Comment 3 Holger Schmithüsen 2013-08-19 10:20:23 UTC
(In reply to comment #1)
> Those are not "useless" styles, they do carry revision ids.

All right, I now see the use of the rsids (to identify which content has been created in which session). However, two questions arise from that:

1. The attributes "officeooo:paragraph-rsid" and "officeooo:rsid" of <style:text-properties> are not in the "OASIS OpenDocument 1.2 standard", therefore they must be part of "1.2 extended". (BTW, where can I see what's behind this?) Wouldn't it then be more convenient to allow every content element (like <text:p> here) to have a rsid-attribute, rather then defining styles that contain this information?

2. Why do the rsids vanish, when the styles are reassigned to the paragraphs (see steps 8b and 9b of the initial post)?

Regards, Holger
Comment 4 João Paulo 2014-11-03 23:23:07 UTC
Hi, and forgive my rude english (non native speaker here).

Running LibreOffice, build id edfb5295ba211bd31ad47d0bad0118690f76407d, on Windows Vista 64 bit edition, this version also presents the same behavior.

Please explain to me why this isn't a bug, as explained on #2 on the last comment by @Holger?

Also, shouldn't LibreOffice have an option to disable the creation of those RSIDs? I searched the Preferences, LibreOffice Writer, Comparing (or so it should be localized), there is no option to fully disable it.

I think this should be treated as a bug, as this behavior is undesired, or at least as a feature request.

I am reopening this bug, as it makes documents bigger and more complex to handle than needed, but as of a low and minor importance, as it has a partial workaround for removing the extra complexity at the cost of removing the direct format applied.

Feel free to change it to "Enhancement", or even to raise the importance of the bug, but please do not close it.
Comment 5 Joel Madero 2014-11-04 16:29:24 UTC
I don't see that this was confirmed by QA team - moving to UNCONFIRMED as REOPENED is incorrect. Thanks
Comment 6 Miklos Vajna 2015-02-01 22:45:43 UTC
I confirm the problem. We could indeed have a new option that disables generation of RSIDs.
Comment 7 Commit Notification 2015-02-02 13:25:39 UTC
Miklos Vajna committed a patch related to this issue.
It has been pushed to "master":


tdf#68183 sw: config option for disabling the creation of automatic RSID marks

It will be available in 4.5.0.

The patch should be included in the daily builds available at
http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
Affected users are encouraged to test the fix and report feedback.