<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - "Load styles" should not import content" href="https://bugs.documentfoundation.org/show_bug.cgi?id=131347#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - "Load styles" should not import content" href="https://bugs.documentfoundation.org/show_bug.cgi?id=131347">bug 131347</a> from <a class="email" href="mailto:lobugs@ikr.uni-stuttgart.de" title="Ulrich Gemkow <lobugs@ikr.uni-stuttgart.de>"> Ulrich Gemkow</a> <pre>My starting point for separating style and content would be the (my) goal behind styles and importing styles: To allow central managed style templates which may be imported in different (maybe existing) documents to allow for an consistent look of all documents importing the style. Then "style" is all what is common to all documents regarding their look and content is what is specific to each document. Examples from my point of view - When a header contains a page number field, this is style - When a header contains "typed in text" (i.e. a documents title) this is content Not importing "typed in text" from a header is also consistent with importing styles from the text part of a document - only the style and not text from a paragraph is imported. So is see this as a bug and a barrier for the way toward style based document management.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>