Yes, this is the right place.
As I started to say on that list, it seems to me that this may be a
font-specific problem.
Fonts have hints. I've seen similar issues when the hints are poor.
Unfortunately there is no easy way to know if they are poor.
Some clients/apps/rendering systems by policy ignore hints so they may
look OK,
but then they may not look as good on a case where the hints were good
and important.
If I knew exactly what font you were using I could look at it.
Note that Java 2D most definitely does use a fontrasteriser.
Oracle's builds use a one that ships with the JDK binaries (not source)
All openjdk builds use freetype. On Linux this means Ubuntu's openjdk will
use the exact same copy of freetype as used for rendering the rest of
your desktop!
So if it looks bad with that, it will look bad on your desktop unless
the font is interpreted differently.
I expect Android Studio uses the same platform freetype, and if you are
using the same font
there that is why I think it may be down to hinting.
I looked through all the fonts on 16.04 but didn't see a problem with "#"
So (off-list) email me the exact font and the size and rendering options
you are using.
-phil.
On 12/15/2016 05:30 AM, Artur Rataj wrote:
Hello, I discussed the problem on dev-build
http://mail.openjdk.java.net/
<http://java.net/>pipermail/build-dev/2016-December/018353.html
but have been redirected here, thanks Eric!
I would like to ask why OpenJDK on Linux has by default an inferior
font rendering quality, when there are OpenJDK variants also for
Linux which can render the same fonts with a very high quality.
I described the problem in more detail and with images here:
https://stackoverflow.com/questions/41149451/a-method-of-getting-a-linux-jdk-tarball-with-freetype-like-font-rendering
Best regards,
Artur
