Web Fonts Working Group - Activity in 2024
No matches.
TR publications
-
1 document published.
-
Range Request Incremental Font Transfer published as a Discontinued Draft. History of Range Request Incremental Font Transfer
-
Past meetings
GitHub
w3c/IFT
-
2 issues opened.
-
Rechartering for 2025-26 w3c/IFT#248, by @svgeesus.
-
-
4 issues closed.
-
Extension algorithm language and pre-loading w3c/IFT#231.
-
7 issues received 22 new comments.
-
Discontinue the "Incremental Font Transfer via Range Request" specification w3c/IFT#230 (4 comments by @garretrieger, @svgeesus)
-
Patch type combinations -- normative vs non-normative guidance w3c/IFT#240 (1 comment by @garretrieger)
-
2 pull requests opened.
-
actually use the abstract in the spec w3c/IFT#247, by @svgeesus.
-
Better abstract #213 w3c/IFT#246, by @svgeesus.
-
-
3 pull requests merged.
-
actually use the abstract in the spec w3c/IFT#247.
-
Better abstract #213 w3c/IFT#246.
-
-
1 pull request received 1 new comment.
Past meetings
-
1 meeting.
GitHub
w3c/IFT
-
8 issues opened.
-
Patch type combinations -- normative vs non-normative guidance w3c/IFT#240, by @skef.
-
Alternative high-level breakdown of patch extension algorithm w3c/IFT#239, by @skef.
-
Potential invalidating patch criterion for extension algorithm w3c/IFT#235, by @skef.
-
Clear up "encoding" vs "format" w3c/IFT#234, by @skef.
-
Grouping of patches during extension w3c/IFT#233, by @skef.
-
Extension algorithm language and pre-loading w3c/IFT#231, by @skef.
-
-
7 issues closed.
-
Grouping of patches during extension w3c/IFT#233.
-
Add `@supports` example to IFT spec w3c/IFT#212.
-
Clear up "encoding" vs "format" w3c/IFT#234.
-
Advice for `unicode-range` w3c/IFT#210.
-
7 issues received 36 new comments.
-
Potential invalidating patch criterion for extension algorithm w3c/IFT#235 (17 comments by @garretrieger, @skef)
-
Patch type combinations -- normative vs non-normative guidance w3c/IFT#240 (8 comments by @garretrieger, @skef)
-
Performance of unified extension algorithm for "no invalidation" patches w3c/IFT#232 (3 comments by @garretrieger)
-
Alternative high-level breakdown of patch extension algorithm w3c/IFT#239 (2 comments by @garretrieger)
-
-
7 pull requests opened.
-
Update extension algorithm to include explicit prefetching. w3c/IFT#244, by @garretrieger.
-
Make some updates to encoder requirements w3c/IFT#242, by @garretrieger.
-
Fix a couple of mistakes in the URI template examples. w3c/IFT#236, by @garretrieger.
-
-
8 pull requests merged.
-
Make some updates to encoder requirements w3c/IFT#242.
-
Add note about using unicode-range + IFT. w3c/IFT#226.
-
3 pull requests received 14 new comments.
-
Add appendix B which contains an example of the extension algorithm execution. w3c/IFT#237 (11 comments by @garretrieger, @skef)
-
Update extension algorithm to include explicit prefetching. w3c/IFT#244 (2 comments by @garretrieger, @skef)
-
Add mechanism for handling UVS sequences (and other similar cases) w3c/IFT#222 (1 comment by @svgeesus)
-
Past meetings
GitHub
w3c/IFT
-
2 issues opened.
-
Detecting codepoint readiness w3c/IFT#223, by @garretrieger.
-
5 issues closed.
-
Detecting codepoint readiness w3c/IFT#223.
-
I18n checklist answers for 9 July WD of IFT w3c/IFT#195.
-
Minimum patch sizes? w3c/IFT#207.
-
Incremental Font Transfer and WOFF1 w3c/IFT#211.
-
Remove full file brotli patch mechanism w3c/IFT#214.
-
-
6 issues received 24 new comments.
-
Minimum patch sizes? w3c/IFT#207 (12 comments by @garretrieger, @pes10k, @skef, @svgeesus, @vlevantovsky)
-
Add concrete examples to the application of a patch section w3c/IFT#216 (1 comment by @vlevantovsky)
-
-
10 pull requests opened.
-
Add note about using unicode-range + IFT. w3c/IFT#226, by @garretrieger.
-
Various tweaks to Glyph Keyed format text w3c/IFT#221, by @garretrieger.
-
9 pull requests merged.
-
Various tweaks to Glyph Keyed format text w3c/IFT#221.
-
4 pull requests received 18 new comments.
-
Add a more general readiness check for finding which parts within a shaping unit are supported. w3c/IFT#227 (7 comments by @garretrieger, @skef)
-
Add mechanism for handling UVS sequences (and other similar cases) w3c/IFT#222 (5 comments by @garretrieger, @skef)
-
Add a procedure to check what content an IFT font can render. w3c/IFT#224 (4 comments by @garretrieger, @skef)
-
Tweaks to table keyed patches based on experience implementing it. w3c/IFT#220 (2 comments by @skef, @svgeesus)
-
w3c/ift-encoder
-
1 pull request opened.
-
Implement encoding of format 2 IFT patch maps w3c/ift-encoder#83, by @garretrieger.
-
-
1 pull request merged.
-
Implement encoding of format 2 IFT patch maps w3c/ift-encoder#83.
-
Past meetings
Participants
-
1 participant left.
-
David Kuettel (Google LLC) left.
-
GitHub
w3c/IFT
-
7 issues opened.
-
Add concrete examples to the application of a patch section w3c/IFT#216, by @rsheeter.
-
Remove full file brotli patch mechanism w3c/IFT#214, by @rsheeter.
-
Review feedback wrt making spec more readable w3c/IFT#213, by @rsheeter.
-
Add `@supports` example to IFT spec w3c/IFT#212, by @svgeesus.
-
Incremental Font Transfer and WOFF1 w3c/IFT#211, by @svgeesus.
-
Advice for `unicode-range` w3c/IFT#210, by @svgeesus.
-
Minimum patch sizes? w3c/IFT#207, by @pes10k.
-
-
2 issues closed.
-
Advice for "on by default" features w3c/IFT#206.
-
Document serializing/caching of patched font w3c/IFT#196.
-
-
1 issue reopened.
-
Document serializing/caching of patched font w3c/IFT#196, by @svgeesus.
-
-
5 issues received 7 new comments.
-
4 pull requests opened.
-
Number Security, Privacy, Changes w3c/IFT#215, by @svgeesus.
-
Add guidance on "default" features w3c/IFT#208, by @garretrieger.
-
3 pull requests merged.
-
Number Security, Privacy, Changes w3c/IFT#215.
-
Add guidance on "default" features w3c/IFT#208.
-
TR publications
-
1 document published.
-
WOFF File Format 2.0 published as a Recommendation. History of WOFF File Format 2.0
-
Past meetings
Participants
-
3 participants joined.
-
Abhishek Singh (Microsoft Corporation) joined.
-
Ragvesh Sharma (Microsoft Corporation) joined.
-
Rakesh Goulikar (Microsoft Corporation) joined.
-
GitHub
w3c/IFT
-
3 issues opened.
-
Advice for "on by default" features w3c/IFT#206, by @garretrieger.
-
Considerations for "desiccated" initial font files w3c/IFT#201, by @skef.
-
-
2 issues closed.
-
5 issues received 8 new comments.
-
Consistently use `code point` instead of sometimes saying `codepoint` w3c/IFT#200 (2 comments by @garretrieger, @svgeesus)
-
4 pull requests opened.
-
Add a small section explaining caching incremental fonts. w3c/IFT#205, by @garretrieger.
-
Clarify how to handle format 2 string entry id's. w3c/IFT#204, by @garretrieger.
-
Add more Normative Validation rules for Format 2 w3c/IFT#203, by @garretrieger.
-
Prefer 'code point' over 'codepoint'. w3c/IFT#202, by @garretrieger.
-
-
5 pull requests merged.
-
Clarify how to handle format 2 string entry id's. w3c/IFT#204.
-
Add more Normative Validation rules for Format 2 w3c/IFT#203.
-
Prefer 'code point' over 'codepoint'. w3c/IFT#202.
-
2 pull requests received 10 new comments.
-
In format 1 ignore most invalid data instead of failing with an error. w3c/IFT#199 (8 comments by @garretrieger, @skef)
-
w3c/woff
-
2 issues closed.
-
3 issues received 9 new comments.
-
Clarify WOFF2 header majorVersion and minorVersion w3c/woff#28 (7 comments by @garretrieger, @Lorp, @svgeesus, @vlevantovsky)
-
Distinguish "Decoding of bounding boxes" section from "Decoding of Composite Glyphs" section w3c/woff#29 (1 comment by @svgeesus)
-
-
2 pull requests opened.
-
[editorial] Add missing header for clarity, fix #29 w3c/woff#33, by @svgeesus.
-
3 pull requests merged.
-
[editorial] Add missing header for clarity, fix #29 w3c/woff#33.
-
Make the two previous proposed corrections normative w3c/woff#32.
-
2 pull requests received 4 new comments.
-
Make the two previous proposed corrections normative w3c/woff#32 (2 comments by @garretrieger, @svgeesus)
TR publications
-
1 document published.
-
Incremental Font Transfer published as a Working Draft. History of Incremental Font Transfer
-
Past meetings
GitHub
w3c/woff
-
2 issues received 6 new comments.
-
2 pull requests opened.
-
Make the two previous proposed corrections normative w3c/woff#32, by @svgeesus.
-
Draft woff2 implementation report w3c/woff#31, by @svgeesus.
-
-
1 pull request merged.
-
Draft woff2 implementation report w3c/woff#31.
-
w3c/IFT
-
6 issues opened.
-
Document serializing/caching of patched font w3c/IFT#196, by @pmeenan.
-
I18n checklist answers for 9 July WD of IFT w3c/IFT#195, by @svgeesus.
-
Security self-review answers for 9 July 2024 WD of IFT w3c/IFT#194, by @svgeesus.
-
Wide Review of 20 Feb 2025 WD of IFT w3c/IFT#193, by @svgeesus.
-
Possible "all other codepoints" semantic? w3c/IFT#192, by @skef.
-
2 issues closed.
-
Early wide review of IFT w3c/IFT#33.
-
Rewrite explainer w3c/IFT#160.
-
-
6 issues received 22 new comments.
-
Should we require Erroring on Validation Requirements for Format 1 Patch Map? w3c/IFT#198 (6 comments by @garretrieger, @skef)
-
7 pull requests opened.
-
Additional adjustments to format 1 patch map w3c/IFT#197, by @garretrieger.
-
Make Some Adjustments to Format 1 Patch Map w3c/IFT#190, by @garretrieger.
-
Updates for publication as WD on 2024 07 09 w3c/IFT#189, by @svgeesus.
-
initial explainer rewrite w3c/IFT#187, by @svgeesus.
-
6 pull requests merged.
-
Additional adjustments to format 1 patch map w3c/IFT#197.
-
Make Some Adjustments to Format 1 Patch Map w3c/IFT#190.
-
Updates for publication as WD on 2024 07 09 w3c/IFT#189.
-
initial explainer rewrite w3c/IFT#187.
-
-
1 pull request closed.
-
IFTB draft w3c/IFT#151.
-
-
5 pull requests received 36 new comments.
Past meetings
GitHub
w3c/IFT
-
2 issues opened.
-
Aspects of streamed decoding on the client side w3c/IFT#183, by @skef.
-
Mixing patch types and GID "management" w3c/IFT#182, by @skef.
-
-
3 issues closed.
-
Aspects of streamed decoding on the client side w3c/IFT#183.
-
Mixing patch types and GID "management" w3c/IFT#182.
-
Encoder requirements questions/issues w3c/IFT#176.
-
-
1 issue received 2 new comments.
-
3 pull requests opened.
-
Add more guidance about network round trips + patch types. w3c/IFT#186, by @garretrieger.
-
When talking about mixing patch types mention retain gids. w3c/IFT#184, by @garretrieger.
-
-
4 pull requests merged.
-
2 pull requests received 4 new comments.
-
Add more guidance about network round trips + patch types. w3c/IFT#186 (2 comments by @garretrieger, @skef)
-
Add a note to encoding guidance about table order in brotli patches. w3c/IFT#185 (2 comments by @garretrieger)
-
Past meetings
-
1 meeting.
GitHub
w3c/IFT
-
2 issues opened.
-
Partial invalidation brotli patches? w3c/IFT#177, by @skef.
-
Encoder requirements questions/issues w3c/IFT#176, by @skef.
-
-
3 issues closed.
-
Partial invalidation brotli patches? w3c/IFT#177.
-
Different URL ID encoding w3c/IFT#167.
-
-
4 issues received 5 new comments.
-
7 pull requests opened.
-
Tweaks to encoder section wording w3c/IFT#181, by @garretrieger.
-
Different encoding section language w3c/IFT#178, by @skef.
-
Add More Encoding guidance w3c/IFT#174, by @garretrieger.
-
Add text for the privacy considerations section. w3c/IFT#173, by @garretrieger.
-
-
8 pull requests merged.
-
Tweaks to encoder section wording w3c/IFT#181.
-
Different encoding section language w3c/IFT#178.
-
Fill out the 'Handle errors' section. w3c/IFT#163.
-
Add text for the privacy considerations section. w3c/IFT#173.
-
Switch ID encoding to base32hex w3c/IFT#169.
-
Major Reorganization of Spec Sections. w3c/IFT#171.
-
-
1 pull request closed.
-
Add More Encoding guidance w3c/IFT#174.
-
-
6 pull requests received 34 new comments.
-
Add text for the privacy considerations section. w3c/IFT#173 (10 comments by @garretrieger, @skef, @svgeesus)
-
Note the mitigations for limiting the number of requests in security considerations. w3c/IFT#180 (3 comments by @garretrieger, @skef)
-
First pass at adding iteration limits to the extension algorithm. w3c/IFT#175 (1 comment by @garretrieger)
Past meetings
GitHub
w3c/IFT
-
2 issues opened.
-
Different URL ID encoding w3c/IFT#167, by @skef.
-
Rewrite explainer w3c/IFT#160, by @svgeesus.
-
-
2 issues received 18 new comments.
-
11 pull requests opened.
-
Suggested reorg edits and additions w3c/IFT#172, by @skef.
-
Major Reorganization of Spec Sections. w3c/IFT#171, by @garretrieger.
-
Rebuild Overview.html using the newest version of bikeshed. w3c/IFT#170, by @garretrieger.
-
Switch ID encoding to base32hex w3c/IFT#169, by @skef.
-
Rework patch categorization w3c/IFT#166, by @garretrieger.
-
Add optional ID string mapping to format 2. w3c/IFT#165, by @garretrieger.
-
Fill out the 'Handle errors' section. w3c/IFT#163, by @garretrieger.
-
Add text for the "Load a Patch File" algorithm. w3c/IFT#162, by @garretrieger.
-
Updates to the encoder section + TODO cleanup w3c/IFT#161, by @garretrieger.
-
-
9 pull requests merged.
-
Suggested reorg edits and additions w3c/IFT#172.
-
Rework patch categorization w3c/IFT#166.
-
Add optional ID string mapping to format 2. w3c/IFT#165.
-
Updates to the encoder section + TODO cleanup w3c/IFT#161.
-
Add text for the "Load a Patch File" algorithm. w3c/IFT#162.
-
Add specification for the Format 2 Patch Map w3c/IFT#159.
-
-
9 pull requests received 90 new comments.
-
For patch application specify that checksums need to be updated. w3c/IFT#168 (25 comments by @garretrieger, @skef, @svgeesus)
-
Past meetings
-
1 meeting.
GitHub
w3c/IFT
-
1 pull request opened.
-
Add specification for the Format 2 Patch Map w3c/IFT#159, by @garretrieger.
-
-
1 pull request received 17 new comments.
Past meetings
Participants
-
1 participant joined.
-
Jeff Carey (Monotype) joined.
-
GitHub
w3c/IFT
-
1 issue closed.
-
Poor cacheing properties w3c/IFT#119.
-
-
1 issue received 2 new comments.
-
4 pull requests opened.
-
Some editorial suggestions w3c/IFT#158, by @skef.
-
Update Overview.html to reflect changes in metadata. w3c/IFT#156, by @garretrieger.
-
-
4 pull requests merged.
-
Some editorial suggestions w3c/IFT#158.
-
Update Overview.html to reflect changes in metadata. w3c/IFT#156.
-
-
3 pull requests received 9 new comments.
-
Add additional introductory sections and a new Encoder section w3c/IFT#157 (5 comments by @svgeesus)
-
Add a new static incremental font transfer spec to replace patch subset and range request. w3c/IFT#155 (1 comment by @svgeesus)
-
Past meetings
-
1 meeting.
Participants
-
3 participants joined.
-
Atilla Korap (Monotype) joined.
-
Sahil Dua (Monotype) joined.
-
Bryan Comeau (Monotype) joined.
-
-
1 participant left.
-
yogesh pathak (Monotype) left.
-
GitHub
w3c/ift-encoder
-
1 pull request opened.
-
Add support for design space augmentation with a mix of shared brotli and IFTB patches. w3c/ift-encoder#82, by @garretrieger.
-
-
1 pull request merged.