Bug 60741 - FORMATTING: Libreoffice does not display different weights of one font via formatting toolbar
Summary: FORMATTING: Libreoffice does not display different weights of one font via fo...
Status: RESOLVED DUPLICATE of bug 66792
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
4.0.0.3 release
Hardware: Other macOS (All)
: high enhancement
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-12 17:45 UTC by c933465
Modified: 2018-01-05 10:31 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Font Menu in Writer (52.48 KB, image/png)
2013-02-12 18:44 UTC, Emir Sarı
Details
Font Menu in Neooffice Writer (for comparison) (48.09 KB, image/png)
2013-02-12 18:45 UTC, Emir Sarı
Details

Note You need to log in before you can comment on or make changes to this bug.
Description c933465 2013-02-12 17:45:04 UTC
Problem description: 

as described in subject

Steps to reproduce:
1. install "titilium text" font family
2. open new document
3. select the font

Current behavior:

ony one weight showing in font list

Expected behavior:

all weights from "1wt" to "999wt" should be available
Operating System: Mac OS X
Version: 4.0.0.3 release
Comment 1 Emir Sarı 2013-02-12 18:43:43 UTC
Well, actually, this is a long-due bug/lack of feature that prevents LO being used as a "decent" word-processing software on Mac platform. LO is not able to use different font weights. I don't know what's the situation on different platforms, but on Mac it is as explained.
Comment 2 Emir Sarı 2013-02-12 18:44:22 UTC
Created attachment 74705 [details]
Font Menu in Writer
Comment 3 Emir Sarı 2013-02-12 18:45:01 UTC
Created attachment 74706 [details]
Font Menu in Neooffice Writer (for comparison)
Comment 4 Emir Sarı 2013-02-12 18:47:12 UTC
--Ignore my previous comment, LO can use different font weights, but you have to access them via character menu!
Comment 5 Stefan Knorr (astron) 2013-11-10 20:12:21 UTC

*** This bug has been marked as a duplicate of bug 66792 ***