Summary: | Text formatted with only styles and manually is not visually different | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | belomir <leggis> |
Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | enhancement | CC: | heiko.tietze, philipz85, robinson.libreoffice, zen |
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 107326 | ||
Attachments: | highlight direct formatting concept |
Description
belomir
2015-01-05 15:16:19 UTC
Jay: Perhaps you can provide some insight here? Thanks! Though i see very little use cases to this, maybe text which has direct formatting applied to it can appear in a different color than text which only uses styles, but this setting would not be enabled by default.
I know MSO has a style inspector (attachment 102031 [details]) which shows the paragraph and character level styles and direct formatting applied to text.
Created attachment 112391 [details]
highlight direct formatting concept
I wrote a little macro for demonstration.
I don't know how to make such the instrument and how to use it: should it have ability to select all of direct formatted objects, should it count them etc.
This is in UX-advise for triage, so: Status -> NEW We're replacing our use of the 'ux-advise' component with a keyword: Component -> LibreOffice Add Keyword: needsUXEval [NinjaEdit] Might this issue be solved if a solution for bug 34002 was developed? (In reply to David from comment #6) > Might this issue be solved if a solution for bug 34002 was developed? No dont think reveal codes is a suitable solution for this issue. Seems like solution for Bug 106556 would solve the need. I'll mark as a duplicate but let CC'ed UX gives a comment here. *** This bug has been marked as a duplicate of bug 106556 *** (In reply to Timur from comment #8) > Seems like solution for Bug 106556 would solve the need. Yes, and there is another aspect discussed at bug 115311 with a mockup how it could be solved. |