When I change user interface language from Enlgish to Korean, LO and OO fail to change Korean fonts' name. For example, Batang font is also '바탕'. Font list should show '바탕' not 'Batang' in Korean mode. While windows version can do that, mac version cannot. Even if I changed operating system(sierra) language, still same issue. Does it matter? Yes. LO and OO cannot recognize Batang and 바탕 are actually same in both mac and windows while MS Office and Hancom Office can do that. LO shows italic 'batang' font while '바탕' is already on the font list of formatting bar. I know italic font means it is not installed. This is serious compatibility issue. All other korean fonts have same problem. I think japanese and chinese fonts have same problem since they also have two name. (Actually this is second bug. But I don't report this now.)
I fix my report. I found user interface language cannot change font name. Windows system language can do. Windows Korean interface show korean font name(바탕) instead of english name(batang) in LO. 바탕 and batang are same font. Mac cannot do that. I am not sure whether this is LO's bug. Other software like iWork, textedit, and MS office show korean font name(바탕) in mac os korean interface. LO and OO show only enlgish name(batang) in mac os korean interface.
Not sure how to reproduce this to attempt confirmation. If I change the system language to Korean on my Mac, I have to restart it for the changes to take effect. This will lead to the login screen asking for my password, which I will have no idea how to type in Korean.
Ideally, we'd need another Korean tester/user on QA with an OSX system to confirm this report.
I have successfully found Korean Mac testers on Reddit before, but it would be interesting to see Jeehyun first test with 5.3: http://www.libreoffice.org/download/pre-releases/ Perhaps HarfBuzz affects this as well..
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-20170727
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-20170830