Description: https://imgur.com/a/IkjWB1a 如圖，當我在自行選擇欄使用"DF中太楷書體" 或是把文字變成"玉山風體"字型時，writer 或是 impress 就會莫名其妙停止運作。 Steps to Reproduce: 1.在系統字型安裝 "df中太楷書體" "玉山風體" 2.打開writer 或者 impress 3.輸入文字 4.將輸入文字的字型變更成 "df中太楷書體" "玉山風體" Actual Results: libre office停止運作 Expected Results: 應該順暢執行，可以使用這些字型 Reproducible: Always User Profile Reset: No Additional Info: 如果問題回報表單也能寫成繁體中文就好了
Would it be possible you write in English? I used Google translate and it seems Writer and Impress stop working when you use "Df in the book" font. Do you have last version of this font? If yes, where can it downloaded? (if it's a free font). Kevin: thought you might be interested in this one.
Translation: Description: https://imgur.com/a/IkjWB1a See the screenshot, if I use "DF中太楷書體(DF Zhongtai Kai Shu)" font in the self selection section or change the text font to "玉山風體 (Yushan Feng)", Writer or Impress will stop working unexpectly. Steps to Reproduce: 1.Install "DF中太楷書體(DF Zhongtai Kai Shu)" and "玉山風體 (Yushan Feng)" fonts in your system. 2. Open Writer or Impres 3. Type in text. 4. Change the font of the text you typed to the two fonts mentioned above. Actual Results: libre office stops working. Expected Results: Should work and able ti change the fonts. Reproducible: Always User Profile Reset: No Additional Info: It will be good if the feedback form can be written in Traditional Chinese.
@yu.tzeng: Where can we get the fonts you mentioned? I don't have them. 这两个字体在哪里下载？
I managed to get the "DF中太楷书体" font and tested on Windows 10 X64 with LibreOffice 6.1. I do not reproduce. 版本：6.1.2.1 (x64) Build ID：65905a128db06ba48db947242809d14d3f9a93fe CPU 线程：4; 操作系统：Windows 10.0; UI 渲染：GL; 区域语言：zh-CN (zh_CN); Calc: CL @yu.tzeng: Would you copy and paste the information from "Help -> About" dialog? 我试了一下，无法重现，请你复制粘贴一下“帮助-关于”界面上的所有信息。谢谢！ For the test, I am sharing the font: http://home.suokunlong.cn/nextcloud/index.php/s/Nj4pbiecSxDkm4j . Anyone interested to test this bug can download the font from my link. For lience reasons, I will delete this share when this bug is closed. Thanks.
With master sources updated today + gen rendering, I don't reproduce this. Yu.Tzeng: would it be possible you retrieve a backtrace? (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows:_How_to_get_a_backtrace)
Thank you for reporting the bug. To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and re-test? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present
Dear yu.tzeng, 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 yu.tzeng, 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