1. Add a font replacement entry with "Screen only" 2. Nothing happens. To see it applied, you need to check "Always" option. That is unexpected and not intuitive.
Can you expand on the steps a bit. I'm not sure how I do a "screen only" font replacement. Thanks!
Sorry didnt' explore enough, here are steps: Tools -> Options -> Fonts Check "Apply replacement table" Font: Select a font that's in use on screen, "Replace with" choose another font Click Green Check Mark Check "Screen only" option in dialog Click OK Agreed, nothing happens and that's no good, might be useful just to disable the feature (screen only) until it's fixed - this would probably be an easy hack. Marking: New (Confirmed) Minor (not a common feature, doesn't prevent high quality work, work around is just manually changing font) Low (really uncommon feature to use, easy work around) Thanks for reporting this one
Also changing version to 3.6.3.2 as I've confirmed it on that version (Version is the oldest version that the bug is confirmed on, not the latest version it's confirmed on). Also updating Platform Thanks again
I ‘m sorry, but I think the behaviour in the mentioned case is correct. I assume that you replaced a font which is installed on your system. For this case the help says „Font replacement only on screen, but only if font is not available.“. The problem is, that the word „Always” is misleading. If checked the meaning is: Also replace font if used font is installed. If not checked the meaning is: Only replace font if used font is not installed. In order to improve this, “Always” could be replaced by “Also if font is installed”. Or another possibility: Add a hint to this option page, where the meaning of “Always” is explained. But I think in the other case, where the font which shall be replaced is not installed, the behaviour is not correct: [1] Create a short text and assign a font to this text, that is not installed on your system. The font name is displayed in italic and a tip is displayed, that the font is substituted (since LO Version 4.1.0). Perhaps you know, but I don’t know which font is used in this case. I call it here “standard replacement”. [2] Change option: Replace the not-installed font with a font which is installed. Check “Screen only” and don’t check “Always”. I expect in this case, that the font is replaced by the defined replacement font. But it is still replaced with the “standard replacement”. I think there are some more cases where the font replacement does not work correctly. I described them in bug 43185. Furthermore in order to make it more transparent for a user what happens, the hint could be improved: “The current font ‘ABC’ is not installed on your system and is substituted by the font ‘XYZ’". And in the other case: "The installed font 'ABC' is substituted by the font 'XYZ'". And just a bagatelle: In the hint the word “substituted” is used. I think it is better to use always the same word, in this case “to replace” or “replacement”.
** 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-04-01
Checked again with 4.4.3. The behaviour has not changed since version 4.1.0. As I mentioned in comment 4 I think the original behaviour as described in comment 2 is correct. Furthermore I also mentioned that there are other problems in connection with the font replacement (see comment 4 and bug 43185) which still exist.
** 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.1.5 or 5.2.1 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-20160920
Bug still exists in version 5.2.2 with Win7.
(In reply to Harald Koester from comment #8) > Bug still exists in version 5.2.2 with Win7. Sorry, that's not correct. The 'behaviour' is still the same. To my opinion the described behaviour is not a bug.
** 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! Warm Regards, QA Team MassPing-UntouchedBug
Checked with version 6.1.1 (64 bit, Win 10). Behaviour has not changed. To my opinion not a bug.
Dear Urmas, 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! Warm Regards, QA Team MassPing-UntouchedBug
Since there has been no contradiction against comment 4, I close this bug as NOTABUG.