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

Chrome/Chromium does not use system FreeType #3

Open
pdeljanov opened this issue Mar 18, 2019 · 5 comments
Open

Chrome/Chromium does not use system FreeType #3

pdeljanov opened this issue Mar 18, 2019 · 5 comments
Assignees
Labels
enhancement New feature or request

Comments

@pdeljanov
Copy link
Owner

Chrome and Chromium-based browsers or applications do not use the system FreeType library. Therefore these applications don't get the Infinality improvements. There isn't much that can be done unfortunately other than compiling Chromium using the system FreeType library. This can be accomplished by setting the build flag: use_system_freetype=true.

I will consider adding a Chromium PKGBUILD in here to support this, but compiling Chromium is generally not feasible unless you have an extremely strong computer.

@pdeljanov pdeljanov added the enhancement New feature or request label Mar 18, 2019
@pdeljanov pdeljanov self-assigned this Mar 18, 2019
@TomaszGasior
Copy link

chromium package on Arch official repo is affected too?

@pdeljanov
Copy link
Owner Author

chromium package on Arch official repo is affected too?

Yes, no official or AUR chromium package is built with the use_system_freetype=true build flag. You could always modify the PKGBUILD for chromium, but the build will probably take the better part of a day...

An alternative is Firefox, which does use the system's FreeType library (for now), but it has other font rendering problems unrelated to infinality-remix.

@jstkdng
Copy link

jstkdng commented Dec 24, 2019

no official or AUR chromium package is built with the use_system_freetype=true build flag

hey now, ungoogled-chromium-bin is built with the use_system_freetype=true flag.

but compiling Chromium is generally not feasible unless you have an extremely strong computer.

can confirm this, but you can also use OpenSUSE's Build Service, I use it to compile ungoogled-chromium-bin https://build.opensuse.org/package/show/home:justkidding:arch/ungoogled-chromium.
really helps out a lot.

@amelia808
Copy link

no official or AUR chromium package is built with the use_system_freetype=true build flag

hey now, ungoogled-chromium-bin is built with the use_system_freetype=true flag.

but compiling Chromium is generally not feasible unless you have an extremely strong computer.

can confirm this, but you can also use OpenSUSE's Build Service, I use it to compile ungoogled-chromium-bin https://build.opensuse.org/package/show/home:justkidding:arch/ungoogled-chromium.
really helps out a lot.

Did you notice a difference? I compiled chromium with the flag and couldn't see any changes.

@pdeljanov
Copy link
Owner Author

no official or AUR chromium package is built with the use_system_freetype=true build flag

hey now, ungoogled-chromium-bin is built with the use_system_freetype=true flag.

Thanks, good to know!

Did you notice a difference? I compiled chromium with the flag and couldn't see any changes.

I personally run the official Chrome build, so I wouldn't be able to tell you. However, you could try comparing the same page on Firefox (71 or later) vs. chromium. I can confirm that Firefox renders as expected with Infinality.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants