Created attachment 79951 [details]
test document + screenshot
Problem description: Adding a comma into Hebrew text with diacritics causes display corruption. The same happens when opening previously saved document with such content (doesn't matter in which format it was saved).
It's a Windows-only bug, and not a recent one - I remember this happening back in early OOo 3.x days.
After some research I've found that this happens only with fonts which don't contain the letter 'b' (LATIN SMALL LETTER B) (In fact they don't contain any Latin letters, because they're Hebrew-only fonts). So it's seems that LO have a check for that letter anywhere in the code.
After adding that letter to the font (even an empty one), this bug goes away. You can add an empty character to a font using FontForge by selecting the letter 'b' and going through Metrics->Set Both Bearing. Unfortunately this can't be done with non-free fonts due to legal restrictions, making them unusable with LO.
I'm attaching a test document + screenshot of the bug. You can get the font that used from: http://culmus.sourceforge.net/fancy/dorian.tar.gz
Operating System: Windows 7
Version: 188.8.131.52 release
Changed Summary to a more descriptive one. Also it reflects my latest finding, that actually there is no need to add diacritics in order to trigger this bug, only Hebrew text with commas needed (don't know how I missed that...). I'll attach a second (simpler) test case that reflects that.
By the way, the latest Apache OO release (4.0) doesn't suffer from this issue (verified on Windows 7 32-bit), as opposite to previous releases that behave like the current LO, so it might be helpful to check their code and see what they changed.
Created attachment 83266 [details]
Created attachment 83267 [details]
Screenshot of the second test-case, that shows the bug
Created attachment 83268 [details]
Screenshot from Linux (This is how it should be)
The bug is still there in version 184.108.40.206 (Windows version)
(In reply to comment #5)
> The bug is still there in version 220.127.116.11 (Windows version)
Indeed, and also in Version: 18.104.22.168.alpha0+
Build ID: cc2a405915e82c4b332dd25457f76704dc536d7f
TinderBox: Win-x86@39, Branch:master, Time: 2013-10-15_15:51:52
Maxim Monastirsky committed a patch related to this issue.
It has been pushed to "master":
fdo#65124 define HAVE_FMERGENEUTRALITEMS for MSVC build
The patch should be included in the daily builds available at
http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
Affected users are encouraged to test the fix and report feedback.
Reopening since the above commit fixes the bug only for Windows 7, while Windows XP is still affected. Probably because fMergeNeutralItems introduced in Vista.
Maxim - can we assign this bug to you? Else it would be nice to close this as FIXED and open a new bug report for Windows XP only. We only use REOPENED for bugs that are currently assigned to developers.
(In reply to Joel Madero from comment #9)
> Maxim - can we assign this bug to you? Else it would be nice to close this
> as FIXED and open a new bug report for Windows XP only.
Let's close this one, since I'm probably not going to work on it anymore. I don't even know whether it's still reproducible under XP.