Description: We went through a rebranding in our company and changed the font we're using for all documents. Whenever I open an old document using the old CI/CD font I miss a function to enforce the new font for all defined styles of a document. While I can simply change the font for the "Default Paragraph Style" in a document I don't see an option to enforce a (new/changed) style attribute (e.g. the font family) for all styles of a document - this would be helpful to overwrite styles that had a manually set font family. Steps to Reproduce: * create an empty writer document * change the font family of e.g. the "Footnote" style to e.g. Arial * change the font family of the "Default Paragraph Style" style to e.g. Calibri * try to enforce that all styles use Calibri (also the manually set "Footnote" style) Actual Results: There is no easy way to enforce style attributes on all styles of a document. Expected Results: There should be an easy way to enforce a style attribute on the "Default Paragraph Style" on all other styles. Reproducible: Always User Profile Reset: No Additional Info: I flag this as "[Discussion]" - maybe I'm the only user with this problem or maybe there is an easy way to achieve what I want (and I just don't know about it) - so feel free to comment and/or educate me :) Thanks!
I don't know if there are such external tools - maybe some extensions? - but the whole thing is *properly* handled by consistent use of styles and templates. If some set of styles should use same value of a property - say, same font - they better inherit from a single style, at which level the font name is set. That is exactly why styles are useful - they assign their settings both to text using them, and to derived styles. If you base all your documents on a template that is in your templates path, you then would get notification when the *template* is modified, with suggestion to update styles in the opened document based on that template [1]. Of course, that depends on initial correct work with styles/templates. Given that the architecture of LibreOffice is focused on styles, and use of styles already provides the needed functionality, I doubt there could be some other mechanism *not* using proper features, that could achieve that. [1] https://help.libreoffice.org/7.2/en-US/text/shared/01/01020000.html?&DbPAR=SHARED#templates
Exactly what Mike wrote. If you make a template the default in the template manager all documents created new will use this format. The envisioned style checker barely sounds like a generic tool. You changed the font name others might want to check the font size. Colors are important for company branding while being irrelevant for individuals. Users take the predefined paragraph styles or self-made. And I can imagine the one or other user applying direct formatting too. Personally, I hate empty paragraphs to get spacing between paragraphs. Etc. pp... Hard to imagine that checking all these conditions is possible with a generic tool.
Further detail of Mike's explanation can be found in chapter 10 of the Writer Guide. The relevant sections: * Setting the "Default" Template. * Changing the template assigned to a document can be read on-line here: https://books.libreoffice.org/en/WG72/WG7210-WorkingWithTemplates.html The off-line edition of this and all our available guides can be downloaded from: https://documentation.libreoffice.org/en/english-documentation/ As a side note for future reference. Rather than raising issues in the bug tracking facility, it is better to use our support options to ask questions or seek assistance: * By posting to the user mailing list: users@global.libreoffice.org * By visiting or forum: https://ask.libreoffice.org/c/english/5 Hope this helps to resolve your issue.
I mostly agree with the PoV that the styles should only be "enforced" through the template. The world is just very often not perfect and I got to review too many documents where users did manual style assignments. I still see a certain demand that as a user it would be nice to change e.g. all font attributes of all styles of a specific document. But let's close this for now as I agree that this can be circumvented by working with styles in the correct way which is (as Mike pointed out) a basic focus of the architecture. Thanks to all of you for the valuable input!