For some reason the order of input is affection the output of the display. My default setting is font 'Liberation Serif' [OPTION A] If I check - Insert/Special Character - Type in field 'search': question - Select font 'Marlett' After this I do see 3 options. [OPTION B] If I check - Insert/Special Character - Select font 'Marlett' - Type in field 'search': question After this I do see 0 options. This does not seem to be correct. Other question to this subject: - What kind of character am I inserting when following Option-A? The appearance of the question mark changes after the font is being changed!
Less an issue with the order in GUI, and more to do with a symbol font like Marlett. Symbol fonts receive the SYMBOL_CHARSET mapping of their PUA onto the lower 254 characters of ASCII A symbol font like Marlett will rarely if ever have its PUA mapped onto the Unicode system codepoint names, meaning the Search function in our Special Symbol dialog will find nothing. But, there is a LibreOffice issue in populating the character map. When the font does not have coverage of UCS name string (i.e. no matching glyphs in the font) the chart should show nothing. Instead it is receiving some weird hybrid chart. For example...search for "combi" for alll COMBINING form UCS, and select U+338 for "COMBINING LONG SOLIDUS OVERLAY". Change from from default Liberation Serif to Liberation Sans Narrow (that has no coverage of U+338). We get the correct glyph preview with a "Missing character" label. But we also get an incorrect chart of glyphs--there are no combining characters in Liberation Sans Narrow, so the chart *should* be empty. And in another glitch, again selecting Liberation Serif font from the drop list, will show the correct glyph from the font--but the font chart is *empty*. As if the chart is not being recalculated on font change.
Thanks for the explanation, and rephrasing, of this problem. Hopefully someone can correct this.
Dear Luuk, 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
Dear Luuk, 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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still present in Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b5c3a7502f7ff6ccf0f829c1f3a2ba50b8584c41 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (de_DE); UI: en-GB Calc: CL threaded
Still present in: Version: 24.2.1.2 (X86_64) / LibreOffice Community Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac CPU threads: 12; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: threaded
(In reply to Luuk from comment #6) > Still present in: > Version: 24.2.1.2 (X86_64) / LibreOffice Community > Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac > CPU threads: 12; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: > win > Locale: nl-NL (nl_NL); UI: en-US > Calc: threaded (the 'Insert / Special Character' showing wrong characters is still present, my second question is answered already...)
(In reply to Luuk from comment #7) > (In reply to Luuk from comment #6) > > Still present in: > > Version: 24.2.1.2 (X86_64) / LibreOffice Community > > Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac > > CPU threads: 12; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: > > win > > Locale: nl-NL (nl_NL); UI: en-US > > Calc: threaded > > (the 'Insert / Special Character' showing wrong characters is still present, > my second question is answered already...) I find that if I do a second font selection from the drop list (or close/reopen the SCD) the charmap refreshes with the desired font. It should change/redraw the charmap on first change of font. But it seems to hold any valid found glyph from prior font selection--then releases it on a second font selection. Can see the utility in the UI of keeping prior found glyph queued--to show the same glyph with a font change. But shouldn't require a second font selection when the new font selected does not cover the prior glyph. Easy (consistent) to work around but maybe need additional logic when font selected does not cover a prior covered code point. E.g. change from Liberation Sans --> Liberation Sans Narrow; or Liberation Serif --> Marlett @Mike, Samuel -- think this was Akshay Deep's GSOC 2017 work on the search for the SCD. https://gerrit.libreoffice.org/c/core/+/40563 any cycles to have a look?
(In reply to V Stuart Foote from comment #8) previous issue of a "odd" charmap result on font change has been resolved, e.g. Marlett returns an empty charmap for any search. Or Liberation Sans Narrow chart is empty of combining chars with "combi" but "com" does return UCS names with COMMA.
https://gerrit.libreoffice.org/c/core/+/171446
Mike Kaganski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/055c906d7b3f2e3709292d1410358d4e66a500ed tdf#123527: use the new font in SvxSearchCharSet::RecalculateFont It will be available in 25.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Verified the font handling in SCD is now more responsive. Changing font (of a Paragraph in use) or in the SCD directly now rebuilds the charmap results and any search results against UCS name on first go. =-testing-= 2024-08-04 TB77 nightly Version: 25.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 055c906d7b3f2e3709292d1410358d4e66a500ed CPU threads: 8; OS: Windows 11 X86_64 (10.0 build 22631); UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded
Mike Kaganski committed a patch related to this issue. It has been pushed to "libreoffice-24-8": https://git.libreoffice.org/core/commit/b3104dab9c9ef6cdbc0535a066011eb43a58cd09 tdf#123527: use the new font in SvxSearchCharSet::RecalculateFont It will be available in 24.8.1. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.