https://bz.apache.org/ooo/show_bug.cgi?id=126953
--- Comment #21 from orcmid <[email protected]> --- (In reply to billp from comment #20) > Sorry, I forgot to mention my operating system. I'm using Windows 10 Pro > Insider Preview, Build 14372. Whoa. So attributing a problem on a pre-release build of Windows 10 to Apache OpenOffice may not be quite fair. While Microsoft is probably very close to release of the Windows 10 Anniversary Edition, and there has been an avalanche of Insider builds recently, we really can't spend too much effort on font-rendering matters that may be a function of non-released Windows builds and not AOO. One thing we need to do is have people be clear when they are using advance versions of releases, whether Windows or AOO. Unfortunately, Microsoft has made it more difficult for an user to determine exactly what the version and update status is for a Windows 10 released version. (I'm also not certain this should have been closed based on one reporter having the problem disappear. For this kind of thing, it could be coincidental. Let's see if others continue to report the issue in one flavor or another.) -- You are receiving this mail because: You are the assignee for the issue.
