https://bugs.documentfoundation.org/show_bug.cgi?id=103514
--- Comment #8 from V Stuart Foote <vstuart.fo...@utsa.edu> ---
So, this applies to the new common layout, but it will do nothing for releases
through 5.2--should the old DirectWrite with OpenGL rendering need to be
corrected?
(In reply to Khaled Hosny from comment #3)
> We should simply disable bitmap-only fonts, as a matter of fact I did this
> already last night for the new layout. Can you try with a build that has
> commit 48304cb5b4d8df71463837e2e48aa7c4d9594df9? (I don’t have a Windows box
> handy to test right now).
Testing that on Windows 8.1 Ent 64-bit en-US with
Version: 5.3.0.0.alpha1+
Build ID: 9c34797cc98030614b384b6ea0f233d59ae82253
CPU Threads: 8; OS Version: Windows 6.29; UI Render: GL;
TinderBox: Win-x86@39, Branch:master, Time: 2016-10-26_03:58:19
Locale: en-US (en_US); Calc: CL
Enabling SAL common layout composing the Writer canvas is now ignoring system
installed bitmap fonts (on Windows Courier, MS Serif and MS Sans Serif). The
WinLayout fallback seems to be making reasonable font selections--Mono spaced
for Courier, a Serif font, and a Sans Serif respectively.
Unfortunately we have no way to determine exactly the font being substituted.
But the Tools -> Options -> Fonts: font table substitution can be used to
manually select the replacement font to be used.
The Special Character dialog also is ignoring the system installed fonts. With
common layout, the dialog is offering system font Segoe UI as the replacement
font as the edit cursor is positioned into on a word with the "not installed"
font [1].
=-Note-=
[1]. Adjusting the Special Character dialog to offer the substituted font at
the text cursor rather than Segoe system default at the text cursor would be
helpful
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
