https://bugs.documentfoundation.org/show_bug.cgi?id=118902
Caolán McNamara <caol...@redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vmik...@collabora.com
--- Comment #9 from Caolán McNamara <caol...@redhat.com> ---
The code in
https://cgit.freedesktop.org/libreoffice/core/commit/?id=fab0a2c6068577081abdad90a3b1191b6fc5df29
is fontconfig-using platforms only, so not windows or mac and the problem is
reported initially on windows, so changing that code so won't have an effect on
that platform.
wrt regression vs AOO/OOo we replaced the rtf parser with a different one, it
is very plausible that's the crucial difference and there isn't a simple commit
that if reverted makes it all work like the past
mike's initial comment is probably the way to go and something like at
writerfilter/source/dmapper/DomainMapper.cxx:356 of
case NS_ooxml::LN_CT_Fonts_ascii:
adding a line under
m_pImpl->GetTopContext()->Insert(PROP_CHAR_FONT_NAME, uno::makeAny(
sStringValue ))
of
m_pImpl->GetTopContext()->Insert(PROP_CHAR_FONT_NAME_COMPLEX, uno::makeAny(
sStringValue ));
might be the right thing to do, but I don't know the full consequences of
making that change. Presumably LN_CT_Fonts_hAnsiTheme has a similar issue,
maybe others too
--
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
