Description: For the Recent Documents (all libreoffice components) and Input Bar (Calc), at least, documents with Hebrew names and input in Hebrew displays in what looks like some ancient semetic font, at a guess. There is no means to change the font, from what I can tell, and I'm not sure exactly which font it is. Needless to say, this makes identifying what one is typing or loading a bit difficult. Bug persists in all late 5.x versions I have used, as well as the 6.0 series I am currently using. Steps to Reproduce: 1. Load a document with a Hebrew filename 2. Go to Recent Documents 3. Look at the display font for the file or 1. Open Calc 2. Type Hebrew in the input bar 3. Look at it Actual Results: I would expect the font to be something correct and basic, eg TNR, Arial, etc, or to have an option to set which font is desired. Expected Results: Some incorrect font is used, displaying the text completely illegibly Reproducible: Always User Profile Reset: No Additional Info: At the least, having an option to set the font would be helpful, but why and how it's choosing whichever font it is choosing is probably interesting in and of itself, instead of using the universal unicode font sets.
Created attachment 145371 [details] partial screen capture of recent documents menu look at lines 5 and 9 for examples of what i am talking about. this is not a normal hebrew font and i'm not sure which font it is.
5.4.6 is EOL, and font handling on Windows has been reworked in current master/6.2.0 please retest against a nightly master.
This has been a problem SINCE the late 5.x series. It persists in the update I did today for the 6.x stable series. (I just found that it also exists for the database field and description names, which means that I have absolutely no idea what I'm typing.)
Created attachment 145372 [details] capture of table create error The font handling is completely broken here - you can see that it's overlapping, blanking, etc. It's also impossible to discern what the error actually is.
please reference bug 120310 for additional info about the fail - that's a much more serious fail than merely a font problem.
(In reply to elflng.libreoffice from comment #5) > please reference bug 120310 for additional info about the fail - that's a > much more serious fail than merely a font problem. And again, please test in current nightly build of master/6.2.0--*not* 6.0.6 nor 6.1.2!
I am on a production machine. Can the two versions exist simultaneously?
https://wiki.documentfoundation.org/Installing_in_parallel so from a Windows cmd command line, a /a switch with a TARGETDIR set. E.g.: msiexec.exe /a libo-master64~2018-10-03_23.04.03_LibreOfficeDev_6.2.0.0.alpha0_Win_x64.msi TARGETDIR="C:\LODev620_testing" Then to isolate the user profile, edit the C:\LODev620_testing\program\bootstrap.ini and reset UserINstallation= to point to $ORIGIN\..\Data\settings Install will be isolate from your production install LO instance. Similar parallel installs can be done for Linux and macOS builds as noted in the Wiki. The nightly TinderBox builds are here: https://dev-builds.libreoffice.org/daily/master/
Todah, I'll get to it in a few minutes and post results. (The input sanitisation bug is much more serious and should be looked at first, if it's not already handled.)
(In reply to elflng.libreoffice from comment #9) > Todah, I'll get to it in a few minutes and post results. (The input > sanitisation bug is much more serious and should be looked at first, if it's > not already handled.) Did you have the chance to look at it?
Dear elflng.libreoffice, 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 elflng.libreoffice, 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