https://bugs.documentfoundation.org/show_bug.cgi?id=38194

--- Comment #59 from V Stuart Foote <vsfo...@libreoffice.org> ---
(In reply to Heiko Tietze from comment #54)
> I dislike the DF separation from CS/PS+PDF. Users need to fully understand
> the formatting to deal with all these options. Maybe it would be easier to
> handle if we had a menu button, eg. next to the 'Show non-printable
> characters' icon, named for example 'Spot formats' which offers a couple of
> checkboxes including 
> 
> * "All formatting" (checking all below), 
> * "Direct formatting" (it's one important use case to show all places where
> character attributes got changed, see bug 106556; I think users expect this
> to include PDF too and we could do without the colored variants of PS), 
> * "Paragraph Styles" and 
> * "Character Styles".
> 
> Most users are probably not aware of CS, haven't tried to switch from the PS
> view to CS if checking the Stylist at all, and do DF only (also for the
> whole paragraph).

No, I think Jim got this right--with style focus via the SB deck controls only.
They do not belong on the Menus & TBs (and can't be added effectively to the
NB).

The DF visibility toggle (as for bug 106556) is actually satisfied by this.
Although I think the character DF UNO really belongs as a checkbox on the
Styles -> Character content panel.  I.e. everything provided from the SB.

This will facilitate an "Eve" user working from the 'Fomatting (Styles)' TB
with the Styles SB deck enabled--having as now customized the DF toggle UNO to
the TB--they'd toggle to see why their layout is affected (better if checkbox
toggle from the Styles -> Character content panel). But they'd otherwise leave
the DF spotlights off and layout with styles rather than DF.

"Benjamin" users would not be as concerned with styles in general, so the DF
toggle UNO with just icon and tooltip can go to 'Standard' TB and probably the
'Format' menus. With the customize checkbox for the NB users that choose to
work with the SB.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to