Date: prev next · Thread: first prev next last
March 2015 Archives by date, by thread · List index


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

Robinson Tryon (qubit) <qubit@runcibility.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
                 CC|                            |libreoffice-ux-advise@lists
                   |                            |.freedesktop.org,
                   |                            |qubit@runcibility.com
          Component|Writer                      |ux-advise
     Ever confirmed|0                           |1

--- Comment #1 from Robinson Tryon (qubit) <qubit@runcibility.com> ---
(In reply to Christopher R Lee from comment #0)
Currently, in LO 'emphasis' and 'strong emphasis' are the only built-in
styles that give italic and bold font variants. If you want to be sure to
get italic and bold, as well as other variants (small caps etc), you have to
create your own new styles. User styles can make your work less easy to
follow by other team members, and they might not be picked up by export
filters, which are increasingly being used.

Sounds like the UX Team might have something useful to say on this topic :-)
Component -> UX-Advise
Status -> NEW

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.