Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Use antialiasing when comparing pdf files #30068

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

Draft
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

jkseppan
Copy link
Member

@jkseppan jkseppan commented May 18, 2025

Render at 600dpi and scale down to 150dpi.

The low-resolution non-antialiased rendering is convenient in that it hides minor font differences, but it can hide actual rendering errors and cause problems. For example, #29392 needs to change multiple baseline files because of minor differences only visible because of the low-resolution rasterisation.

@jkseppan jkseppan force-pushed the pdf-test-resolution branch from 6afa531 to 645322b Compare May 18, 2025 15:26
Perhaps this is causing the EPS failures
@anntzer
Copy link
Contributor

anntzer commented May 23, 2025

I didn't check, but did all the baselines get updated because they were in fact already slightly invalid but the errors were hidden by the low resolution? If so, does it mean that the regeneration of most baselines arising from the current work to update freetype & parts of the text rendering stack would mean that after they get merged (perhaps not so quickly...), this PR would no longer need to further update them?

Perhaps as a temporary workaround (to limit baseline updates) we could have two test formats, ".pdf" and ".aa600.pdf" where only the latter would be tested after AA rasterization at 600dpi?

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

Successfully merging this pull request may close these issues.

2 participants