Calc use is a lot more on-screen, and at lower size in points (10 instead of 12 on my Linux machine).
Currently, the font order is:
Nachlieli CLM;Alef;Noto Sans Hebrew;Liberation Sans;Arial;Arial Hebrew;Lucida Sans Unicode;Lucida Grande;Arial Unicode MS
But Nachlieli CLM has relatively low readability, IMO, in small font sizes, and Alef is not much tter. I therefore suggest that the order become:
Liberation Sans;Noto Sans Hebrew;Nachlieli CLM;Alef;Arial;Arial Hebrew;Lucida Sans Unicode;Lucida Grande;Arial Unicode MS
Arial;Liberation Sans;Noto Sans Hebrew;Nachlieli CLM;Alef;Arial Hebrew;Lucida Sans Unicode;Lucida Grande;Arial Unicode MS
(Note that I havent' sctually looked at the last three on the list recently.
Steps to Reproduce:
Type in some Hebrew text along a column.
Text comes out in Nachlieli CLM, and is not very readoable
Text comes out in a more readable font
User Profile Reset: No
Created attachment 145519 [details]
Arial, Alef, Liberation Sans and Nachlieli at 10pt
Some have raised the question of whether Alef should not be used before Liberation Sans. Well, no...
Attached is a screenshot with the three fonts used for the same content - a part of an LO Calc chart. Note that Liberation Sans' readability advantage is a bit of a "cheat" since its glyph width and height at 10pt are larger than Arial's and Alef's.
Nachlieli comes in third IMHO, but it's not as readable as Liberation Sans. (It's about as readable even as Liberation Sans at 9pt, maybe less; but that would definitely be an unfair comparison).
Ok. Feel free to propose a patch https://wiki.documentfoundation.org/Development/gerrit
Dear Eyal Rozenberg,
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
(In reply to Buovjaga from comment #2)
> Ok. Feel free to propose a patch
I actually need to get around to proposing that patch. It's just that I've never done anything like that for LO before; I don't have a checked out copy of the sources.
Anyway, this bug should not be auto-closed...
(In reply to Eyal Rozenberg from comment #4)
> (In reply to Buovjaga from comment #2)
> > Ok. Feel free to propose a patch
> > https://wiki.documentfoundation.org/Development/gerrit
> I actually need to get around to proposing that patch. It's just that I've
> never done anything like that for LO before; I don't have a checked out copy
> of the sources.
> Anyway, this bug should not be auto-closed...
To avoid cloning the source, you can also edit directly in gerrit: https://wiki.documentfoundation.org/Documentation/GerritEditing