[haiku-commits] Re: haiku: hrev50959 - src/servers/app/font src/servers/app docs/interface_guidelines 3rdparty/mmu_man/scripts src/add-ons/translators/rtf
- From: waddlesplash <waddlesplash@xxxxxxxxx>
- To: haiku-commits@xxxxxxxxxxxxx
- Date: Sat, 18 Feb 2017 17:51:02 -0500
On Sat, Feb 18, 2017 at 4:05 PM, Fredrik Holmqvist <
fredrik.holmqvist@xxxxxxxxx> wrote:
Did we really agree to this?. We decided to leave Deja Vu as it wasn't the
way forward even though the switch wasn't perfect and now you switch back
because it isn't perfect? Am I missing something?
"Wasn't the way forward": As far as I could tell, the decision to switch
happened for 2 reasons:
1. Noto looked better with the new font rendering
2. Noto had better Unicode support.
The first of these has been significantly improved by disabling the
average-based subpixel filter in app_server. The second turned out to be
false -- while Noto has fonts for any language, DejaVu actually has support
for a lot more languages in a single font (see commit message). So that
turned out to not be true either, and having DejaVu be default with Noto
available in a package is a much better solution.
If you know something I don't, please speak up.
As far as I understand for better font rendering we need a modern font and
then improve our font rendering. Much better commit messages than 'we just
chatted a bit' please for any commits like this...
DejaVu *is* a modern font, it's still under active development and looks
great on, say, Ubuntu's font rendering. We just need to improve our font
rendering by using freetype differently, although the tweaks I made to
app_server already helped significantly.
Also, I elaborated quite a lot in the commit message about why Noto isn't
actually better than DejaVu. What should I have included?
-waddlesplash
Other related posts:
