Selected fonts are getting split if English locale is used.
Steps to Reproduce:
1. Check if your locale is English (LANG=en_US.UTF-8)
2. Install Vollkorn font (just as a example) (http://vollkorn-typeface.com/)
3. Start LibreOffice Writer and check new font
Font is split into 'Vollkorn', 'Vollkorn Black' and 'Vollkorn Semibold' families
New font is expected to be available as one 'Vollkorn' family. Works only with selected fonts (e.g. Arno Pro, Minion Pro, Warnock Pro), but since result heavily depends on locale used I consider it as LO bug.
User Profile Reset: No
1. Check if your locale is Russian (LANG=ru_RU.UTF-8)
2. Start LibreOffice Writer and check new font
3. New font is available as one family, no split happens.
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:56.0) Gecko/20100101 Firefox/56.0
Created attachment 136826 [details]
Screenshot of LO font dialog, started in English locale (top) and Russian (bottom)
Reproduced by running
Arch Linux 64-bit, KDE Plasma 5
Build ID: 64024d7c18bd114eb9958cf80eea9129e09923bd
CPU threads: 8; OS: Linux 4.13; UI render: default; VCL: kde4;
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on November 3rd 2017
Arch Linux 64-bit
Version 22.214.171.124 (Build ID: e183d5b)
The behaviour under the English locale is the correct one IMO, since otherwise you wouldn’t have a way to use Vollkorn Black or Warnock Pro Caption etc.
(In reply to Khaled Hosny from comment #3)
> The behaviour under the English locale is the correct one IMO, since
> otherwise you wouldn’t have a way to use Vollkorn Black or Warnock Pro
> Caption etc.
I believe it is not. They belong to one family, additional properties are available in Format -> Character -> Style.
(In reply to Timur I. Davletshin from comment #4)
> (In reply to Khaled Hosny from comment #3)
> > The behaviour under the English locale is the correct one IMO, since
> > otherwise you wouldn’t have a way to use Vollkorn Black or Warnock Pro
> > Caption etc.
> I believe it is not. They belong to one family, additional properties are
> available in Format -> Character -> Style.
But you can’t select them from the main UI since only buttons for R/I/B/BI are provided. The way other office suite(s) work is by grouping only the four basic styles and anything else is considered a separate family.
(In reply to Khaled Hosny from comment #5)
> (In reply to Timur I. Davletshin from comment #4)
> > (In reply to Khaled Hosny from comment #3)
> > > The behaviour under the English locale is the correct one IMO, since
> > > otherwise you wouldn’t have a way to use Vollkorn Black or Warnock Pro
> > > Caption etc.
> > I believe it is not. They belong to one family, additional properties are
> > available in Format -> Character -> Style.
> But you can’t select them from the main UI since only buttons for R/I/B/BI
> are provided. The way other office suite(s) work is by grouping only the
> four basic styles and anything else is considered a separate family.
I have little chance to use other office suites last decade, so cannot comment which way is de facto standard these days. But without any doubt compatibility should not depend on locale used on client's PC. E.g. I received document created in Russian locale and fonts are mess on my English locale PC. IMHO opinion, relying on font family specified in font file is the best approach. Some foundries make fonts available as stylistic variants, others prefer to define separate family name.
*** Bug 113682 has been marked as a duplicate of this bug. ***
Still can be reproduced in LO 6.0
** Please read this message in its entirety before responding **
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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
Still repro with 6.3.4 and also current master, running on Arch Linux.
With LANG=et_EE or en_GB (regardless of the actual UI language in LibO), the various weights of fonts like Fira Sans are grouped into one family (and, in case there are many weights, some of them are rendered inaccessible); with en_US, the weights are listed as separate families (which makes the font list very, very long if one has many multi-weight fonts installed).
In any case, current dependency on system locale breaks document interoperability.
I'll try my luck bibisecting this later today/tomorrow.
Bibisected first using the sparse Releases repository, which said 126.96.36.199 was the fist bad "commit". So tried with 44max repository, where:
35dc99d53b0a61823b3731e866dd9da0ab3b9141 is the first bad commit
Author: Caolán McNamara <email@example.com>
AuthorDate: Fri Sep 12 10:20:48 2014 +0100
Commit: Caolán McNamara <firstname.lastname@example.org>
CommitDate: Fri Sep 12 10:28:21 2014 +0100
Related: fdo#82259 implement mac ttf fontname encoding support
which is why these font's are not appearing under Linux
... which looks like a credible cause indeed (and was backported to 4.3.3 - https://wiki.documentfoundation.org/Releases/4.3.3/RC1).
Adding Caolán to CC.
However I notice that the above results contradict the "Version 188.8.131.52" information currently in the ticket, so I tested that version specifically using both the Releases bibisect repo and old appimages - and I don't see this behaviour there:
184.108.40.206 is fine (no difference between en_US and others).
220.127.116.11 appimage is fine as well, but
18.104.22.168 appimage is broken (different font listing between en_US and others).
This matches with the bibisect result, too.
One thing to note is that I had to run the bibisect using SAL_USE_VCLPLUGIN=gen because otherwise LibO wouldn't start. I don't know if different VCL plugin could affect this?