https://bugs.documentfoundation.org/show_bug.cgi?id=124191
V Stuart Foote <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.documentfounda
| |tion.org/show_bug.cgi?id=11
| |5117
CC| |[email protected],
| |[email protected],
| |[email protected]
--- Comment #1 from V Stuart Foote <[email protected]> ---
I can not reproduce on Windows 10 Pro 64-bit en-US (1803) with
LinLibertine_R_G.ttf, v5.10 (mod 13-1-2012) of Linux Libertine G is installed
to system. Testing:
Version: 6.1.4.2 (x64)
Build ID: 9d0f32d1f0b509096fd65e0d4bec26ddd1938fd3
CPU threads: 8; OS: Windows 10.0; UI render: GL;
Locale: en-US (en_US); Calc: group threaded
or current master/6.3.0alpha0+
with or without OpenGL rendering enabled.
Only issue I notice is that the "Linux Libertine G" font name gets exported to
PDF as "LinuxLibertineG" and is treated as a missing font on paste back to
Writer. So could be a font fall back issue.
But, guess the Linux Libertine G font could have issues with ligature tables
causing the missing glyphs from the text strings "copied" to clipboard--I'm
just not seeing it with this build
A couple of past issues as in the see also bug 115117, but did not want to dupe
to that without some review.
Believe proposed work implementing tagged PDF with /ActualText structs for bug
117428 would improve this work flow--giving better fidelity of text copied out
from body of PDF.
@Khaled, Miklos any thoughts?
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
