-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blurry font on macOS #8387
Comments
As I mentioned in the linked issue, looks still good on my MacBook (Big Sur). Might be this java bug? https://bugs.openjdk.java.net/browse/JDK-8236689 |
Yes, I think it's that java bug. Looks like the issue is that it renders fine on my laptop screen but fails if I put it on an external monitor. |
It seems it's fixed with openjfx18. We will upgrade to that once it's officially released (probably it will be released around March). It will also (hopefully) contain some other mac fixes. |
@yoachim Can you please test the latest dev version? We just upgraded to jfx 18 https://builds.jabref.org/main/ |
Font looks great on the external monitor. It can't open or import my .bib file, so that's an issue. |
@yoachim Ugh .Can you please check if there are any errors present in the log? Can you also try to open your bib file with TextEditor and check the encoding? |
Looks like its' a plain ASCII file. I can create new libraries fine, so probably just a rouge entry in my giant old .bib file that I can root out. |
When you try to import your bib file into a new library, JabRef should log an error to the log and tell you which entry is broken or where it is broken (refs #8298 not sure when the error is shown) But as the original issue is now fixed, I close this issue! |
JabRef version
5.4 (latest release)
Operating system
macOS
Details on version and operating system
No response
Checked with the latest development build
Steps to reproduce the behaviour
Just loading up the latest version on my mac, the font look terrible. I assume this is some java sillyness.
I tried changing the Info.plist file line:
to
but that didn't help.
Looks like this might be the same issue as #6757
Appendix
The text was updated successfully, but these errors were encountered: