Skip to content
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

Ugly regular font after FreeType update #7032

Closed
Epicus7 opened this issue Jan 10, 2019 · 4 comments

Comments

Projects
None yet
5 participants
@Epicus7
Copy link

commented Jan 10, 2019

After 3be6ab5 regular font (not bolded as in english translation) has become ugly. Especially noticeable, for example, in the Russian translation.

image

  • OpenTTD was compilled with Visual Studio 2017 and runned on Windows 10 with Russian localization.
  • All libraries was dowloaded via vcpkg, according to readme.
  • OpenTTD version is 5e51d9e.

The problem is new version of FreeType library (>=2.8.0). You can downgrade it to 2.6.3 by vcpkg or take version from "useful" pack and see how fonts looked like earlier.

The small font on the map is generally unreadable, so it's impossible to play with such font.

I have tried to enable antialiasing, but it makes fonts blurred and texts should be readable without it as in previous version.

OS: Windows 10 x64
Compiler: VS2017
Version: 5e51d9e
Localization: Russian

Steps to reproduce:

  • Prepare 3rd-party libraries according to readme, using vcpkg.
  • Check version of FreeType (.\vcpkg list). It should be 2.8.1.
  • Compile with VS2017.
  • Run OpenTTD.
  • Enable Russian localization.
  • Fonts are ugly :(

Steps to see how fonts were looked earlier (or you can just run OpenTTD 1.8.0 release with Russian localization):

  • Remove FreeType (.\vcpkg remove freetype:x64-windows-static)
  • Revert FreeType folder of vcpkg repo to 2.6.3 (git checkout f7de134 -- ports/freetype)
  • Install FreeType (.\vcpkg install freetype:x64-windows-static)
  • Recompile OpenTTD with VS2017, run and change localization to Russian.
  • Fonts are fine.
@nielsmh

This comment has been minimized.

Copy link
Contributor

commented Jan 11, 2019

I think the issue has to do with hinting, or perhaps lack of it.

@glx22

This comment has been minimized.

Copy link
Contributor

commented Jan 17, 2019

Using MSYS2, fonts are ugly with freetype 2.9.1 too

@PeterN

This comment has been minimized.

Copy link
Member

commented Jan 17, 2019

Is anyone able to try with an update-to-date freetype on Linux? Mine is from Debian Stable, so not so much...

glx22 added a commit to glx22/OpenTTD that referenced this issue Jan 17, 2019

@planetmaker

This comment has been minimized.

Copy link
Contributor

commented Jan 17, 2019

For what it's worth: on linux with libfreetype 2.8 the same issue shows.

@LordAro LordAro closed this in 1623cb5 Jan 17, 2019

nielsmh added a commit to nielsmh/OpenTTD that referenced this issue Mar 11, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.