Created attachment 150012 [details] Example manfistation and non-manifestation of this issue Hebrew punctuation mostly overlays the glyph it's applied to - with lines or dots above, below or inside the glyph. This most works fine in LO; and it also works fine when you're in Track Changes mode - the it's simply given a different color and rendered the same way. But - if you mix the two, things go wrong: If you add a Hebrew punctuation mark in Track Changes to a letter that's not in Track Changes, or the other way around: A non-Track-Changes punctuation mark to a track changes letter - the punctuation mark gets rendered _after_ the letter. See attachment for two examples - with a Mapiq (=Dagesh) mark and with a Patah. Note that this does _not_ seem to occur with Arabic, although I haven't checked that thoroughly.
The mark placement is broken in Arabic as well, and both issues are most likely another manifestation of bug 61444.
(In reply to Khaled Hosny (inactive) from comment #1) > The mark placement is broken in Arabic as well, and both issues are most > likely another manifestation of bug 61444. Can you post an example document in which this bug manifests for Arabic text?
(In reply to Eyal Rozenberg from comment #2) > (In reply to Khaled Hosny (inactive) from comment #1) > > The mark placement is broken in Arabic as well, and both issues are most > > likely another manifestation of bug 61444. > > Can you post an example document in which this bug manifests for Arabic text? In the example you attached, the Arabic mark position is different between the first and the next two lines (might not be as visible in all fonts).
Created attachment 150045 [details] Screenshot of the Arabic lines
(In reply to Khaled Hosny (inactive) from comment #3) > In the example you attached, the Arabic mark position is different between > the first and the next two lines (might not be as visible in all fonts). Yeah, you're right - it is shifted in position, although not as extremely as with the Hebrew. Can you CONFIRM, then?
Also reproduced in LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
(In reply to Xisco Faulí from comment #6) > Also reproduced in > > LibreOffice 3.3.0 > OOO330m19 (Build:6) > tag libreoffice-3.3.0.4 Yes, it is basically the same thing as bug 61444 which is inherited from OOo. I’m inclined to mark it as duplicate, as I don’t think there is way to fix it without at least fixing bug 61444 first.
(In reply to Khaled Hosny (inactive) from comment #7) > Yes, it is basically the same thing as bug 61444 which is inherited from > OOo. I’m inclined to mark it as duplicate, as I don’t think there is way to > fix it without at least fixing bug 61444 first. I'm marking it as dependent for now. It is not 100% clear to me that this will automagically be resolved by a resolution of bug 61444, and anyway it's significant enough to test separately after bug 61444 is resolved.
Dear Eyal Rozenberg, 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
Bug still manifests (for Hebrew and for Arabic) with: Version: 24.2.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 516f800f84b533db0082b1f39c19d1af40ab29c8 CPU threads: 4; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: he-IL (en_IL); UI: en-US