Description: MacOS supports the Composite Font Representation, a format for composing a single logical font from several font files to circumvent OpenType’s 65,535-glyph limit. When a CFR font is installed, LibreOffice fails to start. Steps to Reproduce: 1. Download and install the CFR font Hanazono Mincho and its component fonts: https://github.com/cjkvi/HanaMinAFDKO/releases/download/8.030/HanaMin.sfont https://github.com/cjkvi/HanaMinAFDKO/releases/download/8.030/HanaMinA.otf https://github.com/cjkvi/HanaMinAFDKO/releases/download/8.030/HanaMinB.otf https://github.com/cjkvi/HanaMinAFDKO/releases/download/8.030/HanaMinC.otf 2. Try to open LibreOffice. ( The issue can also be reproduced with the sample font “Unicode CFR” found here: http://blogs.adobe.com/CCJKType/2012/07/cfr-support-in-mountain-lion.html ) Actual Results: LibreOffice exits before the splash screen would appear. If run from the console, it prints “Application Error”. After deleting any CFR fonts, LibreOffice runs normally again. Expected Results: CFR fonts should be supported or, if that’s too much trouble, ignored. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 6.1.2.1 Build ID: 65905a128db06ba48db947242809d14d3f9a93fe CPU threads: 4; OS: Mac OS X 10.14; UI render: default; Locale: en-US (en_US.UTF-8); Calc: group threaded
No repro with Version: 5.2.5.1 Build ID: 0312e1a284a7d50ca85a365c316c7abbf20a4d22 Threads CPU : 4; Version de l'OS :Mac OS X 10.14.1; UI Render : par défaut; Locale : fr-FR (fr_FR.UTF-8); Calc: group I installed the font files and started LO 5251 - no crash. Also no repro when testing with: Version: 6.1.2.1 Build ID: 65905a128db06ba48db947242809d14d3f9a93fe Threads CPU : 4; OS : Mac OS X 10.14.1; UI Render : par défaut; Locale : fr-FR (fr_FR.UTF-8); Calc: group threaded Sorry, there must be something else going on, or a difference between mine and your system.
FWIW, I also see the fonts listed in the font menu dropdown list in Writer.
Works fine for me too, installing the four Hanazono Mincho fonts (aside, is the .sfont working? It's 909 bytes and FontBook reports a serious error with it) Can you test again on the latest release? Version: 6.3.0.0.alpha0+ Build ID: ea9c13be02ba731074fa4207944ff7df40a0fb5c CPU threads: 2; OS: Mac OS X 10.13.6; UI render: default; VCL: osx; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2019-04-10_20:43:17 Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded
Dear hatschky, 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
Dear hatschky, 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-FollowUp