Not sure about things in platform like Windows, but I think Libreoffice should honor fontconfig first when it exists in system. It seems like a font preference list (http://opengrok.libreoffice.org/xref/core/officecfg/registry/data/org/openoffice/VCL.xcu) is built into LO and fontconfig would only be honored when no fonts in the list is installed. I noticed this because the new URW font release (http://git.ghostscript.com/?p=urw-core35-fonts.git) has switched to new font (family) names, so when I got this instead of the popular old "1.07pre44" release (http://svn.ghostscript.com/ghostscript/tags/urw-fonts-1.0.7pre44/), LO would not prefer "Nimbus Roman" (which was "Nimbus Roman No9 L") unless other fonts in the list like Dejavu are not installed, despite all fontconfig rules.
VCL.xcu is only used on Windows.
I am not sure whether it's related to the VCL.xcu. The main point of this bug report is about the upstream font name changes of the Nimbus fonts. Though it is probably one of the files which need updates. This fontconfig patch could be a reference: http://cgit.freedesktop.org/fontconfig/commit/?id=b732bf057f4b3ec3bac539803005e9c42d056b2a Here I can see in Linux, if the old version of Nimbus fonts are installed (named "Nimbus Roman No9 L" and "Nimbus Sans L"), LibreOffice will default to them (an example is `Options -> LibreOffice Writer -> Base Fonts (Western) -> Default`), but if the new version is installed instead (Named "Nimbus Roman" and "Nimbus Sans"), LibreOffice would default to Dejavu fonts instead. For Writer, this can still be set manually in the option I mentioned above, but for other components similar option doesn't seem to exist.
let's move it back to UNCONFIRMED @Tom Yan is the issue still present in LibO 4.4.3.2?
Yes. I checked again last time with that version.
any news about 5.2.3.3? is issue still present or changed?
(In reply to tommy27 from comment #5) > any news about 5.2.3.3? is issue still present or changed? Or Tom could even test with 5.4 master, because Khaled has been doing fontconfig changes as recently as a couple of days ago. http://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86_64@70-TDF/current/ https://wiki.documentfoundation.org/Installing_in_parallel/Linux Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20170628
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20170727