https://bz.apache.org/ooo/show_bug.cgi?id=126953
--- Comment #26 from orcmid <[email protected]> --- (In reply to orcmid from comment #21) > (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. It appears that the Windows 10 Anniversary Edition (to be release at the beginning of August) is now feature complete. According to this message, <https://www.thurrott.com/windows/windows-10/72455/microsoft-enters-home-stretch-new-windows-insider-release>, Build 14383 is now available to Windows Insiders. I assume fast ring and possibly the slow ring too. This build is appropriate for testing of AOO operability, since they are only looking for bugs now. The comments on that blog post are important here and also on some other issues about AOO operating with display scaling. UWP is about Universal Windows Platform, and it is for responsive applications that scale from mobile up to large-screen systems. WPF is about Windows Presentation Foundation, and it is about APIs in Windows that I am pretty certain are younger than the Apache OpenOffice code base. This should have nothing to do with the Verdana problem but should be relevant to folks who experience fuzzy fonts in AOO when they exercise diplay scaling. -- You are receiving this mail because: You are the assignee for the issue.
