Bug 98675 - Missing possibility to print style definitions
Summary: Missing possibility to print style definitions
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
4.0.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Template-Manager
  Show dependency treegraph
 
Reported: 2016-03-15 08:42 UTC by Ulrich Windl
Modified: 2024-06-05 03:20 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
screen shot showing how you could print the properties in previous versions (108.48 KB, image/png)
2017-08-11 15:53 UTC, Cor Nouws
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ulrich Windl 2016-03-15 08:42:43 UTC
When I try to print the style properties for a template, the only things I find in the menu to manage templates are "Sort by name" and "refresh".
Was it necessary to mess up the user interface once again? Where are the options to print style properties?
Comment 1 Cor Nouws 2016-03-15 12:14:00 UTC Comment hidden (no-value)
Comment 2 Ulrich Windl 2016-03-15 12:55:51 UTC Comment hidden (no-value)
Comment 3 Cor Nouws 2016-03-15 14:00:03 UTC Comment hidden (no-value)
Comment 4 Adolfo Jayme Barrientos 2016-03-22 05:12:39 UTC
> Was it necessary to mess up the user interface once again? Where are the
> options to print style properties?

Funny that you say “once again” (implying recency), since the last time the Template Manager was touched was in a 2012 (IIRC) Google Summer of Code project: that is almost four years ago. In a few months we’re going to release version 5.2 and you’re complaining about a change that was introduced in 4.0 (which is ancient by now). And no, we’re not happy with the current status quo either.

So, Ulrich, if you’re interested in our plans for the template manager, be sure to check out these UX documents and provide feedback:

https://docs.google.com/document/d/1JRPNdeHQpgqiqJv8LW-RHOjtHN8EMX0qK98QBnr10Yg/edit#heading=h.q1t6im2oip6e
https://docs.google.com/document/d/1Ri2jznhcQmCtk3cVygEhwN7pi8FkbIVV_OvRQce_n6Y/edit#heading=h.icneug3ebnpf
Comment 5 Ulrich Windl 2016-03-22 07:45:41 UTC
(In reply to Adolfo Jayme from comment #4)
> > Was it necessary to mess up the user interface once again? Where are the
> > options to print style properties?
> 
> Funny that you say “once again” (implying recency), since the last time the
> Template Manager was touched was in a 2012 (IIRC) Google Summer of Code
> project: that is almost four years ago. In a few months we’re going to

OK, maybe it's the first time you broke the UI for the template manager, but actually I'm talking about the feature to print style definitions that used to be in the template manager for some obscure reason, and most users were unable to find it there. Now that the users are used to find it there, it's gone, and I couldn't find it elsewhere so far. And I don't need the feature frequently, because I'm not changing my styles that frequently. Recently there was some change in corporate design, and I tried to document the style changes (Long story for this issue).

> release version 5.2 and you’re complaining about a change that was
> introduced in 4.0 (which is ancient by now). And no, we’re not happy with
> the current status quo either.

BTW: You make versions ancient, not the user.

> 
> So, Ulrich, if you’re interested in our plans for the template manager, be
> sure to check out these UX documents and provide feedback:

In the first step I'd be happy to display/print the style definitions.

> 
> https://docs.google.com/document/d/1JRPNdeHQpgqiqJv8LW-
> RHOjtHN8EMX0qK98QBnr10Yg/edit#heading=h.q1t6im2oip6e
> https://docs.google.com/document/d/
> 1Ri2jznhcQmCtk3cVygEhwN7pi8FkbIVV_OvRQce_n6Y/edit#heading=h.icneug3ebnpf
Comment 6 Ulrich Windl 2016-03-22 07:53:29 UTC
(In reply to Adolfo Jayme from comment #4)
> So, Ulrich, if you’re interested in our plans for the template manager, be
> sure to check out these UX documents and provide feedback:
> 
> https://docs.google.com/document/d/1JRPNdeHQpgqiqJv8LW-RHOjtHN8EMX0qK98QBnr10Yg/edit#heading=h.q1t6im2oip6e
> https://docs.google.com/document/d/1Ri2jznhcQmCtk3cVygEhwN7pi8FkbIVV_OvRQce_n6Y/edit#heading=h.icneug3ebnpf

Having browsed those, you captured the issues I guess, but as indicated in comment 5 my problem is actually different (see comment 0).
Comment 7 Samuel Mehrbrodt (allotropia) 2016-06-07 15:03:45 UTC
(In reply to Ulrich Windl from comment #0)
> When I try to print the style properties for a template, the only things I
> find in the menu to manage templates are "Sort by name" and "refresh".
> Was it necessary to mess up the user interface once again? Where are the
> options to print style properties?

What do you mean with "printing style properties"? Can you post a screenshot of the former functionality?
What should be the output?
And what is the usecase?
Comment 8 Ulrich Windl 2016-06-23 09:01:36 UTC
(In reply to Samuel Mehrbrodt (CIB) from comment #7)
> What do you mean with "printing style properties"? Can you post a screenshot
> of the former functionality?

I'd wish my brain had perfect image memory and I could make digital copies of those; unfortunately I cannot provide a screenshot when I last used the feature.
"printing style properties" is the feature to display all the properties set for all the styles being defined or used in the current document. Preferrably you can print that document then. Clear now?

(Almost 30 years ago a product named "Ventura Publisher" (running with DOS/GEM) had that feature, too. And some older OpenOffice had a limited version of that, too...)

> What should be the output?

A structured document showing (in a preferrably clever way) all the formatting properties of all styles being defined or used for a document).

> And what is the usecase?

The use case is:
1) Documenting the formatting styles
2) Check the formatting styles for consistency
3) Help product support (=you) with style issues

(In reply to Cor Nouws from comment #1)
The link https://bugs.documentfoundation.org/buglist.cgi?cmdtype=runnamed&list_id=598334&namedcmd=TemplateManager still does not work.
Comment 9 Cor Nouws 2016-06-23 21:01:37 UTC Comment hidden (no-value)
Comment 10 Samuel Mehrbrodt (allotropia) 2016-11-25 08:53:53 UTC Comment hidden (obsolete)
Comment 11 QA Administrators 2017-05-31 10:50:54 UTC Comment hidden (obsolete)
Comment 12 Ulrich Windl 2017-06-01 06:13:27 UTC
(In reply to Samuel Mehrbrodt (CIB) from comment #10)

> Yes, please; also the OpenOffice/LibreOffice version where this was
> available would be useful.

Accidentially I had my StarOffice 9 book in hands: The feature is present there. Is that enough for a version where the feature was present?
Comment 13 Cor Nouws 2017-08-11 15:52:33 UTC
In OOo: File-Template-Manage-DoubleClick..see Styles .. RightClick...See-Print-Option
(will attach screen shot) > new
Comment 14 Cor Nouws 2017-08-11 15:53:25 UTC
Created attachment 135473 [details]
screen shot showing how you could print the properties in previous versions
Comment 15 QA Administrators 2018-08-12 02:35:30 UTC Comment hidden (obsolete)
Comment 16 Cor Nouws 2019-06-07 07:45:07 UTC
still misses in 6.3 master
Comment 17 Buovjaga 2020-06-04 16:49:22 UTC
bibisectRequest here does not make sense as this is clearly about the redesign of the template manager.

(In reply to Cor Nouws from comment #13)
> In OOo: File-Template-Manage-DoubleClick..see Styles ..
> RightClick...See-Print-Option
> (will attach screen shot) > new

To clarify on this: you double-click the template name in the list and it expands a child entry "Styles", which you can then right-click and select Print.
Comment 18 QA Administrators 2022-06-05 03:41:08 UTC Comment hidden (obsolete)
Comment 19 QA Administrators 2024-06-05 03:20:06 UTC
Dear Ulrich Windl,

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