Description: I am developing a musical neume font. I have certain font marks get anchored to glyphs. While the woff font behaves correctly. The otf font in LibreWriter behave correctly initially. It breaks as soon as I change the color of any mark to glyph character. Steps to Reproduce: 1.Install the font from www.anisimkalugin.com/neume_font/kruki_kalashnikov.ttf 2.Open LibreOffice Writer and set the text Wáà change the font face to kruk 3. Select the á character. Its a bit difficult so you may need to switch to a different font colorize it and then switch it back to kruk and you will see the problem. Actual Results: The color change breaks the _shaper feature of the font faces. Expected Results: The color change shouldn't break the _shaper feature of the font face and simply change the color of the mark. Reproducible: Always User Profile Reset: No Additional Info: Version: 6.4.4.2 (x64) Build ID: 3d775be2011f3886db32dfd395a6a6d1ca2630ff CPU threads: 8; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: GL; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: CL video demonstrating the issue: www.anisimkalugin.com/neume_font/font_issues.mp4 image demonstrating the issue: http://www.anisimkalugin.com/neume_font/font_issues.jpg font face to use: http://www.anisimkalugin.com/neume_font/kruki_kalashnikov.ttf
Created attachment 162576 [details] displays font issues Displays font issues and what the font is supposed to look like
Created attachment 162577 [details] video displaying how to repro the bug Video displaying how to reproduce the bug
Created attachment 162578 [details] font face Font face that I am developing.
The GPOS table needs to be fully implemented. I tried the same font on Scribus and it works. https://bugs.scribus.net/view.php?id=7910
Definitely agree that the change needs to be done. However, it's not the only bug I found with the language: sometimes, even without a color change it still has the characters overlap with I space things out. Version: 7.1.0.0.alpha0+ Build ID: 52820b52b3bca45e2db527d1cc5f4488b2e0b9d0 CPU threads: 8; OS: Mac OS X 10.15.6; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
I understand. This font is a bit cryptic and one has to understand the neumes system/logic. The most simplistic explanation is, characters [ÂÃÍÎÏÐÖáâãçêëìíîïóö] get anchored to [A-z, a-z]. They will either be positioned to the west/north west. The implementation that is needed is a standard GPOS lookup table. https://docs.microsoft.com/en-us/typography/opentype/spec/gpos So the if following sequence [pì cÐ ¡?£ï Qì] works. Meaning when the anchor characters color is changed, the anchor characters stay attached to the destination anchors location (west/north west) then the GPOS look up table is working properly. My hunch is... When the color button is clicked the look up table is never reapplied. Currently when the fonts are set the GPOS table is being applied, as soon as the color is changed the GPOS table is ignored.
NEW per comment 5
Dear a.kalugin, 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
*** This bug has been marked as a duplicate of bug 61444 ***