Description: When glyphs loom inside the area of an adjacent glyph, you see that highlighting one glyph cuts off the other one. Steps to Reproduce: 1. Type something italic with big letters that have content in the upper right area of their square area, like “I” or “S” with serifs. 2. Select the glyph to the right side. 3. Choose a highlight colour. Actual Results: The highlight colour cuts off the adjacent glyph. So this highlighting is even _before_the_foreground_ of the glyph which got cut-off. Expected Results: I expect the highlight colour to be a background colour and therefore behind _every_ glyph – thus not being able cutting off another glyph. Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0
Created attachment 137175 [details] Example
Created attachment 137599 [details] Document for testing Not reproduced with Liberation Serif. Arch Linux 64-bit, KDE Plasma 5 Version: 6.0.0.0.alpha1+ Build ID: f657454b69c813b90a8b3c1adb2feef1066dbd35 CPU threads: 8; OS: Linux 4.13; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on November 7th 2017
Created attachment 137623 [details] Reproduced with Liberation Serif
And I think the highlighting of italic text should be italic, too.
Can't reproduce I couldn't see adjacent glyph cut-off windows 10 Version: 5.4.2.2 (x64) Build ID: 22b09f6418e8c2d508a9eaf86b2399209b0990f4 CPU threads: 8; OS: Windows 6.19; UI render: default; Locale: en-US (en_US); Calc: groupVersion: 5.4.2.2 (x64) Build ID: 22b09f6418e8c2d508a9eaf86b2399209b0990f4 CPU threads: 8; OS: Windows 6.19; UI render: default; Locale: en-US (en_US); Calc: group
Reproducible for me with Version: 6.0.0.0.alpha1 (x64) Build ID: c1d1f859b268f650143d48f294999cda0fa57350 CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: de-DE (de_DE); Calc: group and Liberation Serif Italics (using 'f')
(In reply to zyklon87 from comment #4) > And I think the highlighting of italic text should be italic, too. The issue is reproduced especialy on : • Operating system : Windows 8.1 Pro 64-bits. • LibreOffice : Version: 5.4.3.1 (x64) Build ID: 32c8895c6cae21571f364dbb059f419a743ee44d CPU threads: 4; OS: Windows 6.29; UI render: default; Locale: en-US (en_US); Calc: group And also on : • Operating system : Ubuntu 16.04.3 64-bits. • LibreOffice :Version: 5.4.3.1 Build ID: 32c8895c6cae21571f364dbb059f419a743ee44d CPU threads: 8; OS: Linux 4.4; UI render: default; VCL: gtk2; Locale: ja-JP (ja_JP.UTF-8); Calc: group
Mohamed, I don't understand, why you changed the system from "All" to "Linux", because I could reproduce it with Win10 and you reproduced it with Win 8.1. So please give an explanation or change it back to "All"
I also don't understand, why you confirmed it and changed it back to unconfirmed => set to NEW again
Created attachment 137645 [details] Document for testing Ok, with ffff as the string I repro
(In reply to Dieter Praas from comment #9) > I also don't understand, why you confirmed it and changed it back to > unconfirmed => set to NEW again I am sorry, it was a mistake. Somebody was saving changes at the same time and I got notification to merge it with mine.
** 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
Still repro with Version: 6.2.0.0.alpha1+ (x64) Build ID: 8274c4c62df5b937b3f0bec9e1eeca85f3b219d4 CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-10-22_01:47:50 Locale: en-US (de_DE); Calc: CL
Dear zyklon87, 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
Still reproducible in v6.3.4.2
Still the same with Version: 7.2.3.2 (x64) / LibreOffice Community Build ID: d166454616c1632304285822f9c83ce2e660fd92 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL Tested with attachment 137645 [details] from comment 10.
*** This bug has been marked as a duplicate of bug 43643 ***