| Summary: | FORMATTING: [ENHANCEMENT] Print the style catalog | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | ajlittoz <page74010-sf> |
| Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | medium | CC: | page74010-sf |
| Version: | 4.1.0.4 release | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | BSA | ||
| i915 platform: | i915 features: | ||
Sorry, I made a mistake. Second paragraph should read: "Many decades ago, MS Word ... had a feature ..." (not "add"). I am confirming this report. In the context specified by the reporter (technical writing / QA of large and complex documents) I feel this would be a useful feature to have. I am not sure this feature has ever been included in LO/OOo so the version may need to be set back to v3.3.0 - I will leave the QA team to determine how best to handle this. Setting status to NEW and Importance to ENHANCEMENT. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Problem description: -------------------- When you're faced with designing a "standardized" layout for a family of document, you need to have a glance simultaneously at all your styles, mainly to their relationships and their "delta-differences. This helps to conceive the minimal set with "orthogonality". Many decades ago, MS Word (I remember this was the case with Mac Word v4.0) add a feature to print its style catalog when the style window was in the front. I do not know if it is still possible. Steps to reproduce: ------------------- Not applicable Current behavior: ----------------- None Expected behavior: ------------------ Select a style category (Hierachical, Applied, Custom, ...) et request printing the set (or create a document which can later be commented to explain the style semantics). The result should be the same as in the 'Organizer' tab of a style definition dialog to enhance the inheritance relationship. Motivation: ----------- This is part of Quality Assurance. User and Development manuals are written for programs, but documentation for documentation is a bit lagging behind what's done in the technical field. This is all the more necessary since documentation is now a team development effort and spans many years. Many software release are based on the same fundamental textual background and marketing loves to change periodically their graphical chart (which should not impact the semantic content of the manuals). Operating System: All Version: 4.1.0.4 release