Description: Tofu characters are displayed in Today's hint #34 so the hint is not readable. Its screenshot will be attached later. Steps to Reproduce: 1.Start LibreOffice 2.Open a file 3.Check the today's hint #34 Actual Results: There are tofu characters in the description of the hint. So user is not be able to read the hint. Expected Results: No tofu Reproducible: Always User Profile Reset: No Additional Info: Libre Office Version:7.2.6.2 Language* Japanese
Created attachment 178978 [details] Screenshot
Created attachment 184442 [details] 7.4 screenshot I can't reproduce in LO 7.4, even though the japanese translation doesn't seem to have changed between 7.2 and 7.4. Here is the string on Weblate: https://translations.documentfoundation.org/translate/libo_ui-7-4/cuimessages/ja/?checksum=f63013140dba4f68 LO 7.2 will not see any more releases. Can you please try a more recent version? Maybe in safe mode too? My version: Version: 7.4.3.2 / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: ja-JP Calc: threaded
(In reply to Stéphane Guillou (stragu) from comment #2) > Created attachment 184442 [details] > 7.4 screenshot > > I can't reproduce in LO 7.4, even though the japanese translation doesn't > seem to have changed between 7.2 and 7.4. Here is the string on Weblate: > https://translations.documentfoundation.org/translate/libo_ui-7-4/ > cuimessages/ja/?checksum=f63013140dba4f68 > > LO 7.2 will not see any more releases. Can you please try a more recent > version? Maybe in safe mode too? > > My version: > Version: 7.4.3.2 / LibreOffice Community > Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 > CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 > Locale: en-AU (en_AU.UTF-8); UI: ja-JP > Calc: threaded I tried to reproduce the defect on 7.3.7.2. But the defect was not done.
The fix for bug#148470 also solved this one. (was able to reproduce in 7.2.7 and in 7.3.3, but 7.3.4 and later are fixed) *** This bug has been marked as a duplicate of bug 148470 ***