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

CFF2 table update #48

Open
josh-hadley opened this issue Dec 22, 2021 · 7 comments
Open

CFF2 table update #48

josh-hadley opened this issue Dec 22, 2021 · 7 comments

Comments

@josh-hadley
Copy link

josh-hadley commented Dec 22, 2021

Laurence Penney, in cooperation with Adobe and with guidance from Vlad Levantovsky and Peter Constable, has prepared an overhauled CFF2 table specification described as:

This is proposed as an updated specification for the CFF2 table in OpenType fonts. The updated proposal fixes errors, has more explanations, clearer tabulation, and has involved restructuring and rewriting the entire document. It also removes dependencies on other documents, notably the Adobe Type 1 specification.

We hope that its publication will make CFF2 fonts significantly easier to understand for developers of font tools, font rasterizers, and any other code that deals with binary fonts.

This is a work in progress; the current DRAFT is available to review ahead of the formal submission process here: #49

@simoncozens
Copy link

I have some feedback to this. Can I suggest it be submitted as a pull request (not intending to be merged) as a way for people to add line-by-line feedback?

@josh-hadley
Copy link
Author

I defer to @vlevantovsky on that question; I was advised specifically to create an issue for this. I do appreciate that a PR would make it easier to do quoted reviews.

@vlevantovsky
Copy link
Collaborator

Since we are discussing this for the purposes of fine-tuning an input contribution, I think it would be fine to do it as a PR. We cannot host output documents online (unless they're approved as public and then placed in a specific location) but as far as input contributions are concerned, until they are submitted and accepted the copyrights belong to authors.

@josh-hadley
Copy link
Author

no-merge PR with updated content: #49

@vlevantovsky
Copy link
Collaborator

vlevantovsky commented Jan 6, 2022

Thank you @josh-hadley.
All, please note that the document uploaded for review is a draft of the input contribution to be submitted by a member of this AHG for consideration at the next WG meeting - something that we'll have a chance to discuss at a later time as part of the formal review process, if the proposed changes are adopted.
Your comments and suggested improvements would be very much appreciated; however, the member preparing this contribution (Adobe) is under no obligation to adopt them as part of this input submission. Please also note that if your comments are incorporated as part of the input contribution, the copyrights for that contribution will still belong to Adobe.

@josh-hadley
Copy link
Author

Pinging @simoncozens — as you requested, a PR has been created (#49) to enable line-by-line feedback, if you're still interested. The proposal will be submitted for the formal review process soon.

@simoncozens
Copy link

Thank you - I am interested, and I know time is short, but I have been busy with other things. I only really have editorial rather than technical changes.

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

3 participants