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

Expedient plan for moving to read-fonts #13

Open
dfrg opened this issue Sep 11, 2024 · 0 comments
Open

Expedient plan for moving to read-fonts #13

dfrg opened this issue Sep 11, 2024 · 0 comments

Comments

@dfrg
Copy link
Collaborator

dfrg commented Sep 11, 2024

The goal is to replace ttf-parser with small diffs that don't break tests. With that in mind, I'm using the following process:

  1. Replaces calls into ttf-parser with stubs that contain the simplest equivalent read-fonts code that preserves behavior. This code may not be architecturally ideal, might have performance issues and will probably be missing comments and tests.
  2. Audit the new code, likely moving the bulk of it to read-fonts. Make it commented, tested and fast.
  3. Implement architectural changes to match the patterns used in skrifa. Most specifically, let's support acceleration structures that aren't bound to the lifetime of font data.

The rationale for this approach is that it’ll be vastly simpler to do cleanup and architectural changes if we’re not dancing around ttf-parser (or worse, mixed ttf-parser/read-fonts) code.

ref comments in #8

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

No branches or pull requests

1 participant