Problem description: Having both normal (e.g. PT Sans) and 'variant' (e.g. PT Sans Bold) versions of a font installed (as per Control Panel > Fonts), the 'variant' version is not recognised is not recognised as being installed. When part of a document is specified as using that font (as per drop down menu) default font selected by LO is used instead. Specifying it in font selection dialogue (for Character style, Find & Replace by Format, etc.) leads to 'This font is not installed...' message Steps to reproduce: 1. Choose appropriate font, with bold (or other) variant. 2. Type in variant font name manually, in font selection box in dialogue, or in formatting tool bar (for a selection) Current behaviour: Variant font is not recognised as installed, or used Expected behaviour: Variant font should be recognised as installed and used, either directly or after conversion to normal font with (e.g.) Bold attribute applied. Operating System: Windows XP Version: 3.6.6.2 release
I think it should not be possible to choose a font name that is not in the list of installed fonts. Because now you can pick 'any' font.... This is also possible in LO 4.0.3.3 on Windows7
Ability to specify font manually (by typing in name, regardless of it being installed or not), rather than just select from list is only of relevance to this issue in creating test case to demonstrate system behaviour (and is not of itself an issue - there are perfectly valid (if unusual) reasons for doing so). Testing after upgrading LO to 4.0.3.3 (still Windows XP) shows same behaviour. Problem originally showed up to me when: 1) Received document (.doc file) from colleague, using PT Sans fonts (which I did not have). Whole document had seen in substituted, seriffed, font, so obviously wrong: but not unexpected behaviour OO/LO have long done this for uninstalled fonts. 2) Obtained and installed PT Sans font - including both PT Sans and PT Sans Bold fonts (as .ttf files and entries in Windows Control Panel Display). Sections of document specified as PT Sans now ok; sections in PT Sans Bold still in substitute font => this issue (as font now installed, so should be used) Determination that font name ("PT Sans Bold") could be entered manually, and that in some places gave 'not installed' message (although Windows says it is), came later in trying things out. Also found same behaviour with other installed fonts, e.g. Arial & Arial Bold.
Created attachment 80672 [details] Sample Document in .odt format to show problem Most of document is in PT Sans family font - see included comment.
Created attachment 80673 [details] Same Document in .doc (Word) format
** 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 on a currently supported version of LibreOffice (4.4.1 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-03-16
Bug still present, in LO 4.4.1 on Windows XP, and on Windows 7.
** 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 on a currently supported version of LibreOffice (5.0.5 or 5.1.2 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
** 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 on a currently supported version of LibreOffice (5.2.7 or 5.3.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170522
LO 6.2.4.2 installed on Kubuntu 18.04 and in a virtual machine of Lubuntu 16.04. My ODT file uses Cambria (TTF) as the default and only font. Cambria is installed on both flavors of Ubuntu. It is recognized by LO on Kubuntu and displays well. On Lubuntu, it throws the message "This font has not been installed ...", and consequently it displays wrongly. There is a large selection of directories called 'fonts' on the operating system. I have installed the Cambria fonts in all of them, run 'sudo fc-cache -f -v' and got the response that Cambria is installed. The question is why LO Writer does not recognize this, or rather, what I have to do to make LO Writer see the installed fonts. The problem has also been discussed on https://askubuntu.com/questions/1005777/restore-locally-installed-fonts-after-libreoffice-upgrade and there it appeared to be solved. But it is definitely not solved on all flavors of Ubuntu.
Dear Jeremy, 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 https://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! Warm Regards, QA Team MassPing-UntouchedBug
Problem still present in latest version of Libre Office, Help About info as requested: Version: 7.2.2.2 (x64) / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: threaded Note: the PT Sans font family (used in sample documents previously supplied) may now be downloaded as part of the PT Public Pack, from https://www.paratype.com/collections/pt/44157 .
PT Sans Bold is not the family name, so typing it in the font family nale field will result in a missing font. LibreOffice works on separate family name and style name, and that can be easily changed nor it is a desirable thing to change for an office application.