Web Fonts Working Group - Activity in 2022
No matches.
Past meetings
GitHub
w3c/IFT
-
1 issue closed.
-
IFT and offline reading w3c/IFT#129.
-
-
2 issues received 2 new comments.
-
1 pull request merged.
w3c/ift-encoder
-
1 pull request opened.
-
Don't access bit buffer element 0 if it's not there. w3c/ift-encoder#59, by @garretrieger.
-
-
1 pull request merged.
-
Don't access bit buffer element 0 if it's not there. w3c/ift-encoder#59.
-
Lifecycle
-
1 charter extension.
-
Charter extended until 15 March 2023.
-
Past meetings
Participants
-
2 participants joined.
-
Jigna Islaniya (Skynet Technologies) joined.
-
Kirit Bhatt (Skynet Technologies) joined.
-
-
1 organization joined.
-
Skynet Technologies joined.
-
GitHub
w3c/IFT
-
2 issues opened.
-
IFT and offline reading w3c/IFT#129, by @svgeesus.
-
Add QUERY as a HTTP method type used for patch subset. w3c/IFT#127, by @garretrieger.
-
-
6 issues closed.
-
Optimize for one page, many pages, or both? w3c/IFT#118.
-
Questions about section 4.4: Client w3c/IFT#121.
-
Algorithms can be a bit more algorithmic w3c/IFT#106.
-
Redundant feature reduction w3c/IFT#94.
-
Bikeshed supports http header autolinks w3c/IFT#114.
-
-
7 issues received 9 new comments.
-
w3c/IFT#93 (1 comment by @garretrieger)
-
8 pull requests opened.
-
Clarify how brotli patches are made. w3c/IFT#134, by @garretrieger.
-
Expand section of reducing the number of network requests. w3c/IFT#133, by @garretrieger.
-
Remove ordering and patched checksum from response. w3c/IFT#132, by @garretrieger.
-
Update remaining algorithms to use markup w3c/IFT#131, by @garretrieger.
-
Update "Extend the font subset" to use algorithm markup. w3c/IFT#130, by @garretrieger.
-
7 pull requests merged.
-
Clarify how brotli patches are made. w3c/IFT#134.
-
Remove ordering and patched checksum from response. w3c/IFT#132.
-
Update remaining algorithms to use markup w3c/IFT#131.
Past meetings
Participants
-
1 participant left.
-
Bianca Berning (Dalton Maag Ltd) left.
-
-
1 organization left.
-
Dalton Maag Ltd left.
-
GitHub
w3c/ift-encoder
-
3 pull requests opened.
-
Add [[fallthrough]] annotation. w3c/ift-encoder#58, by @garretrieger.
-
BrotliFontDiff add support for diffing loca, hmtx, and vmtx. w3c/ift-encoder#57, by @garretrieger.
-
Add experimental custom brotli font differ. w3c/ift-encoder#56, by @garretrieger.
-
-
3 pull requests merged.
-
Add [[fallthrough]] annotation. w3c/ift-encoder#58.
-
BrotliFontDiff add support for diffing loca, hmtx, and vmtx. w3c/ift-encoder#57.
-
Add experimental custom brotli font differ. w3c/ift-encoder#56.
-
-
1 pull request received 1 new comment.
w3c/IFT
-
1 issue received 1 new comment.
Past meetings
GitHub
w3c/IFT
-
4 issues opened.
-
Client conformance tests w3c/IFT#125, by @garretrieger.
-
Create an explainer for the IFT Patch Subset specification. w3c/IFT#124, by @garretrieger.
-
Consider placing client state as a table in the font. w3c/IFT#123, by @garretrieger.
-
Questions about section 4.4: Client w3c/IFT#121, by @skef.
-
-
7 issues closed.
-
Transfer coding for compression won't work w3c/IFT#115.
-
Why do we have two methods w3c/IFT#120.
-
Ease of font re-ordering for performance w3c/IFT#117.
-
Compression performance tradeoffs w3c/IFT#108.
-
FAST Checklist review for IFT w3c/IFT#32.
-
-
15 issues received 34 new comments.
-
Optimize for one page, many pages, or both? w3c/IFT#118 (5 comments by @garretrieger, @martinthomson, @svgeesus)
-
Transfer coding for compression won't work w3c/IFT#115 (4 comments by @garretrieger, @martinthomson, @svgeesus)
-
Explain more clearly why we have two methods and what the trade-offs are. w3c/IFT#104 (3 comments by @garretrieger, @martinthomson, @svgeesus)
-
w3c/IFT#93 (1 comment by @svgeesus)
-
IFT Method Fallback table should have an "ambivalent client" column w3c/IFT#63 (1 comment by @garretrieger)
-
-
1 pull request opened.
-
1 pull request merged.
Past meetings
GitHub
w3c/IFT
-
7 issues opened.
-
Why do we have two methods w3c/IFT#120, by @svgeesus.
-
Poor cacheing properties w3c/IFT#119, by @svgeesus.
-
Optimize for one page, many pages, or both? w3c/IFT#118, by @svgeesus.
-
Ease of font re-ordering for performance w3c/IFT#117, by @svgeesus.
-
Novel, NIH things w3c/IFT#116, by @svgeesus.
-
Transfer coding for compression won't work w3c/IFT#115, by @svgeesus.
-
Bikeshed supports http header autolinks w3c/IFT#114, by @svgeesus.
-
-
3 issues closed.
-
Query parameters w3c/IFT#75.
-
Negotiation algorithm is not ideal w3c/IFT#107.
-
11 issues received 18 new comments.
-
1 pull request opened.
-
Revise method selection and negotiation. w3c/IFT#113, by @garretrieger.
-
-
1 pull request merged.
-
Revise method selection and negotiation. w3c/IFT#113.
-
-
1 pull request received 10 new comments.
-
Revise method selection and negotiation. w3c/IFT#113 (10 comments by @garretrieger, @svgeesus, @vlevantovsky)
-
w3c/woff
-
1 issue opened.
-
Typo: "wass" w3c/woff#24, by @PeterCon.
-
Past meetings
-
1 meeting.
GitHub
w3c/IFT
-
7 issues opened.
-
Advice on optimal arrangement for range requests? w3c/IFT#110, by @yoavweiss.
-
It'd be interesting to discuss markup discoverability w3c/IFT#109, by @yoavweiss.
-
Compression performance tradeoffs w3c/IFT#108, by @yoavweiss.
-
Negotiation algorithm is not ideal w3c/IFT#107, by @yoavweiss.
-
Algorithms can be a bit more algorithmic w3c/IFT#106, by @yoavweiss.
-
Integer should be 64 instead of 66 bits w3c/IFT#105, by @achristensen07.
-
-
1 issue closed.
-
Integer should be 64 instead of 66 bits w3c/IFT#105.
-
-
12 issues received 26 new comments.
-
It'd be interesting to discuss markup discoverability w3c/IFT#109 (2 comments by @garretrieger, @yoavweiss)
-
Advice on optimal arrangement for range requests? w3c/IFT#110 (2 comments by @garretrieger, @svgeesus)
-
Explain more clearly why we have two methods and what the trade-offs are. w3c/IFT#104 (2 comments by @svgeesus, @tiroj)
-
Closing the initial range request connection, or leaving it open, may cause performance problems w3c/IFT#74 (1 comment by @yoavweiss)
-
2 pull requests opened.
-
Add "Performance Considerations" section. w3c/IFT#112, by @garretrieger.
-
Shrink Integer primitive range to match that of an int64_t. w3c/IFT#111, by @garretrieger.
-
-
2 pull requests merged.
-
Add "Performance Considerations" section. w3c/IFT#112.
-
-
1 pull request received 2 new comments.
TR publications
-
1 document published.
-
Incremental Font Transfer published as a Working Draft. History of Incremental Font Transfer
-
Past meetings
GitHub
w3c/IFT
-
2 issues opened.
-
A-la-carte IFT (IFT Client Javascript API) w3c/IFT#103, by @skef.
-
Shared Brotli ID is expired w3c/IFT#101, by @svgeesus.
-
-
7 issues closed.
-
Method-specific privacy sections w3c/IFT#62.
-
Font Collection support w3c/IFT#28.
-
Support OpenType Features (discretionary) w3c/IFT#87.
-
One outline table w3c/IFT#82.
-
14 issues received 35 new comments.
-
Proposal would allow pages to learn how the user is interacting with the site w3c/IFT#50 (8 comments by @pes10k, @svgeesus)
-
usage of terminology 'codepoints' in patch subset spec. w3c/IFT#73 (3 comments by @himorin, @r12a, @svgeesus)
-
Closing the initial range request connection, or leaving it open, may cause performance problems w3c/IFT#74 (1 comment by @svgeesus)
-
Clarify how saved client state interacts with user agent caching. w3c/IFT#72 (1 comment by @garretrieger)
-
Font extension fetching bypasses CSS font fetching definitions w3c/IFT#69 (1 comment by @garretrieger)
-
-
6 pull requests opened.
-
Make HTTP RFC references more specific. w3c/IFT#102, by @garretrieger.
-
One outline table, fix #82 w3c/IFT#96, by @svgeesus.
-
-
7 pull requests merged.
-
Make HTTP RFC references more specific. w3c/IFT#102.
-
One outline table, fix #82 w3c/IFT#96.
-
-
3 pull requests received 8 new comments.
-
[patch_subset] Add ability to selective transfer opentype layout features. w3c/IFT#95 (3 comments by @garretrieger, @svgeesus)
-
Provide guidance on how a client may choose to integrate with it's HTTP cache. w3c/IFT#98 (1 comment by @svgeesus)
w3c/woff2-tests
-
1 issue closed.
-
Incorrect fragment for collection w3c/woff2-tests#16.
-
-
1 issue received 3 new comments.
-
3 pull requests opened.
-
Add tests for the new overlapBitmap functionality. w3c/woff2-tests#19, by @garretrieger.
-
Fix test available-002 (opentype collections support). w3c/woff2-tests#18, by @garretrieger.
-
Migrate generators from python2 to python3. w3c/woff2-tests#17, by @garretrieger.
-
-
3 pull requests merged.
-
Add tests for the new overlapBitmap functionality. w3c/woff2-tests#19.
-
Fix test available-002 (opentype collections support). w3c/woff2-tests#18.
-
Migrate generators from python2 to python3. w3c/woff2-tests#17.
-
-
1 pull request received 4 new comments.
Past meetings
Participants
-
1 participant joined.
-
Skef Iterum (W3C Invited Experts) joined.
-
-
1 participant left.
-
David Singer (Apple Inc.) left.
-
GitHub
w3c/IFT
-
1 issue opened.
-
Redundant feature reduction w3c/IFT#94, by @skef.
-
-
2 issues closed.
-
Range Request needs to be normative :) w3c/IFT#81.
-
1 issue reopened.
-
10 issues received 22 new comments.
-
Support OpenType Features (discretionary) w3c/IFT#87 (8 comments by @garretrieger, @svgeesus, @tiroj)
-
Require supporting both IFT methods by User Agents w3c/IFT#57 (2 comments by @garretrieger, @svgeesus)
-
w3c/IFT#93 (1 comment by @garretrieger)
-
Server may reply (how else can it, while still doing patch-subset)? w3c/IFT#83 (1 comment by @svgeesus)
-
Proposal would allow pages to learn how the user is interacting with the site w3c/IFT#50 (1 comment by @svgeesus)
-
-
4 pull requests opened.
-
fix #83 for realz w3c/IFT#92, by @svgeesus.
-
4 pull requests merged.
-
fix #83 for realz w3c/IFT#92.
-
Fix #83 w3c/IFT#91.
-
Fix #81 w3c/IFT#90.
-
-
2 pull requests received 7 new comments.
-
[patch_subset] Add ability to selective transfer opentype layout features. w3c/IFT#95 (5 comments by @khaledhosny)
-
w3c/woff
-
1 issue reopened.
-
Wide review and Implementation status, Proposed Changes w3c/woff#15, by @svgeesus.
-
-
2 issues received 7 new comments.
-
1 pull request opened.
-
Broken link w3c/woff#23, by @svgeesus.
-
-
1 pull request merged.
-
Broken link w3c/woff#23.
-
TR publications
-
1 document published.
-
Fonts for the Web: Rationale, 1996 published as a Note. History of Fonts for the Web: Rationale, 1996
-
GitHub
w3c/ift-server-tests
-
2 pull requests opened.
-
Add original vs subset font shaping tests. w3c/ift-server-tests#10, by @garretrieger.
-
Add conformance tests for subset/original_axis_space fields in the response. w3c/ift-server-tests#9, by @garretrieger.
-
-
2 pull requests merged.
-
Add original vs subset font shaping tests. w3c/ift-server-tests#10.
-
Add conformance tests for subset/original_axis_space fields in the response. w3c/ift-server-tests#9.
-
w3c/IFT
-
2 pull requests opened.
-
1 pull request merged.
w3c/ift-encoder
-
1 pull request opened.
-
Add support for server reporting the fonts axis space. w3c/ift-encoder#55, by @garretrieger.
-
-
1 pull request merged.
-
Add support for server reporting the fonts axis space. w3c/ift-encoder#55.
-
TR publications
-
1 document published.
-
WOFF File Format 2.0 published as a Recommendation. History of WOFF File Format 2.0
-
Past meetings
Participants
-
1 participant left.
-
Tao Mu (Loongson Technology Corporation Limited) left.
-
GitHub
w3c/IFT
-
4 issues opened.
-
Support OpenType Features (discretionary) w3c/IFT#87, by @davelab6.
-
One outline table w3c/IFT#82, by @svgeesus.
-
Range Request needs to be normative :) w3c/IFT#81, by @svgeesus.
-
-
7 issues received 10 new comments.
-
Closing the initial range request connection, or leaving it open, may cause performance problems w3c/IFT#74 (2 comments by @svgeesus)
-
Server may reply (how else can it, while still doing patch-subset)? w3c/IFT#83 (1 comment by @garretrieger)
-
3 pull requests opened.
-
Tags some additional server conformance requirements. w3c/IFT#86, by @garretrieger.
-
Update sparse bit set details. w3c/IFT#85, by @garretrieger.
-
Link publication history, both previous versions w3c/IFT#84, by @svgeesus.
-
-
5 pull requests merged.
-
Update sparse bit set details. w3c/IFT#85.
-
Link publication history, both previous versions w3c/IFT#84.
-
Expand patch subset overview section. w3c/IFT#77.
-
1 pull request received 2 new comments.
-
Tag conformance statements around server response requirements. w3c/IFT#80 (2 comments by @garretrieger, @svgeesus)
-
w3c/ift-server-tests
-
4 pull requests opened.
-
Add tests for handling of unrecognized and/or malformed inputs. w3c/ift-server-tests#8, by @garretrieger.
-
Add a bunch more tests for non-covered server conformance statements. w3c/ift-server-tests#7, by @garretrieger.
-
Test a patch request that utilizes codepoint reordering. w3c/ift-server-tests#6, by @garretrieger.
-
Add test of the servers patch functionality. w3c/ift-server-tests#5, by @garretrieger.
-
-
4 pull requests merged.
-
Add tests for handling of unrecognized and/or malformed inputs. w3c/ift-server-tests#8.
-
Add a bunch more tests for non-covered server conformance statements. w3c/ift-server-tests#7.
-
Test a patch request that utilizes codepoint reordering. w3c/ift-server-tests#6.
-
Add test of the servers patch functionality. w3c/ift-server-tests#5.
-
w3c/ift-encoder
-
13 pull requests opened.
-
Update js_client to work with indices_needed. w3c/ift-encoder#54, by @garretrieger.
-
Reject requests that are missing required checksums or protocol version. w3c/ift-encoder#53, by @garretrieger.
-
Use new Harfbuzz array import/export to speed up encode and decode. w3c/ift-encoder#52, by @andyjgf.
-
Update Harfbuzz to a pre-release version of 4.1.1 w3c/ift-encoder#51, by @andyjgf.
-
Update to Harfbuzz 4.1.0 w3c/ift-encoder#50, by @andyjgf.
-
Fix tests, clean up code. w3c/ift-encoder#49, by @andyjgf.
-
Convert to use unordered_map. w3c/ift-encoder#48, by @andyjgf.
-
Convert some additions to bitwise ORs. w3c/ift-encoder#47, by @andyjgf.
-
Remove un-helpfull vector sizing. w3c/ift-encoder#46, by @andyjgf.
-
Speed up encoding and decoding by using bit logic. w3c/ift-encoder#45, by @andyjgf.
-
Convert BranchFactor enum to use values 0..3. w3c/ift-encoder#44, by @andyjgf.
-
Add option to automatically estimate the optimal branch factor when e… w3c/ift-encoder#43, by @andyjgf.
-
Update client and server to use indices_have/needed fields of PatchRequest. w3c/ift-encoder#42, by @garretrieger.
-
-
14 pull requests merged.
-
Update js_client to work with indices_needed. w3c/ift-encoder#54.
-
Reject requests that are missing required checksums or protocol version. w3c/ift-encoder#53.
-
Use new Harfbuzz array import/export to speed up encode and decode. w3c/ift-encoder#52.
-
Update Harfbuzz to a pre-release version of 4.1.1 w3c/ift-encoder#51.
-
Update to Harfbuzz 4.1.0 w3c/ift-encoder#50.
-
Add checksum tests derived from spec examples. w3c/ift-encoder#15.
-
Fix tests, clean up code. w3c/ift-encoder#49.
-
Convert to use unordered_map. w3c/ift-encoder#48.
-
Convert some additions to bitwise ORs. w3c/ift-encoder#47.
-
Remove un-helpfull vector sizing. w3c/ift-encoder#46.
-
Speed up encoding and decoding by using bit logic. w3c/ift-encoder#45.
-
Convert BranchFactor enum to use values 0..3. w3c/ift-encoder#44.
-
Add option to automatically estimate the optimal branch factor when e… w3c/ift-encoder#43.
-
Update client and server to use indices_have/needed fields of PatchRequest. w3c/ift-encoder#42.
-
-
2 pull requests received 5 new comments.
-
Use new Harfbuzz array import/export to speed up encode and decode. w3c/ift-encoder#52 (4 comments by @andyjgf, @garretrieger)
-
w3c/woff
-
1 issue received 3 new comments.
-
3 pull requests opened.
-
Back to Editors Draft w3c/woff#22, by @svgeesus.
-
Update README.md w3c/woff#21, by @svgeesus.
-
Updated rec w3c/woff#20, by @svgeesus.
-
-
3 pull requests merged.
-
Back to Editors Draft w3c/woff#22.
-
Update README.md w3c/woff#21.
-
Updated rec w3c/woff#20.
-
-
2 pull requests received 3 new comments.
Past meetings
Participants
-
1 participant joined.
-
Tao Mu (Loongson Technology Corporation Limited) joined.
-
-
1 organization joined.
-
Loongson Technology Corporation Limited joined.
-
GitHub
w3c/ift-server-tests
-
1 pull request opened.
-
Implement remaining TODO's around patch validation checks. w3c/ift-server-tests#4, by @garretrieger.
-
-
1 pull request merged.
-
Implement remaining TODO's around patch validation checks. w3c/ift-server-tests#4.
-
w3c/IFT
-
3 issues opened.
-
Specifying Range Request implementation details w3c/IFT#79, by @vlevantovsky.
-
Query parameters w3c/IFT#75, by @mnot.
-
-
1 issue closed.
-
Path Forwards: one, two, three specs? w3c/IFT#48.
-
-
8 issues received 13 new comments.
-
Proposal would allow pages to learn how the user is interacting with the site w3c/IFT#50 (3 comments by @pes10k, @svgeesus)
-
Including network state is a privacy harm (and maybe not needed) w3c/IFT#49 (2 comments by @pes10k, @svgeesus)
-
-
4 pull requests opened.
-
Expand patch subset overview section. w3c/IFT#77, by @garretrieger.
-
Merging Patch-Subset and Range-Request specs w3c/IFT#76, by @litherum.
-
2 pull requests merged.
-
Merging Patch-Subset and Range-Request specs w3c/IFT#76.
-
2 pull requests received 12 new comments.
-
Expand patch subset overview section. w3c/IFT#77 (8 comments by @garretrieger, @svgeesus, @vlevantovsky)
-
Merging Patch-Subset and Range-Request specs w3c/IFT#76 (4 comments by @garretrieger, @vlevantovsky)
-
w3c/ift-encoder
-
4 pull requests opened.
-
Fix upper limit test (0xFFFFFFFF is a reserved value). w3c/ift-encoder#41, by @andyjgf.
-
Add upper limits on tree depths, only encode the 32 bit range. w3c/ift-encoder#40, by @andyjgf.
-
Encode filled nodes as zeros. w3c/ift-encoder#39, by @andyjgf.
-
Add variable branch factor to sparse bit set decoding. w3c/ift-encoder#38, by @andyjgf.
-
-
5 pull requests merged.
-
Fix upper limit test (0xFFFFFFFF is a reserved value). w3c/ift-encoder#41.
-
Add upper limits on tree depths, only encode the 32 bit range. w3c/ift-encoder#40.
-
Encode filled nodes as zeros. w3c/ift-encoder#39.
-
Add variable branch factor to sparse bit set decoding. w3c/ift-encoder#38.
-
Add variable branch factor to encoding of sparse bit sets. w3c/ift-encoder#37.
-
TR publications
-
1 document published.
-
Incremental Font Transfer via Range Request published as a First Public Working Draft. History of Incremental Font Transfer via Range Request
-
Past meetings
-
1 meeting.
GitHub
w3c/ift-encoder
-
3 pull requests opened.
-
Add variable branch factor to encoding of sparse bit sets. w3c/ift-encoder#37, by @andyjgf.
-
Fix Brotli's build error. w3c/ift-encoder#36, by @andyjgf.
-
Fix compiler warning. w3c/ift-encoder#35, by @andyjgf.
-
-
2 pull requests merged.
-
Fix Brotli's build error. w3c/ift-encoder#36.
-
Fix compiler warning. w3c/ift-encoder#35.
-
w3c/IFT
-
1 issue closed.
-
3 issues received 5 new comments.
-
Require that incrementally-loaded fonts not be preserved nor exposed to other origins w3c/IFT#43 (1 comment by @pes10k)
w3c/woff
-
1 issue opened.
-
2 issues closed.
-
2 issues received 10 new comments.
-
Bug report: Variable CFF2 fonts stop working if WOFF2 compressed w3c/woff#19 (6 comments by @jfkthame, @svgeesus)
-
-
2 pull requests opened.
-
Update to 14496-22:2019 and CSS Fonts 3 Rec, 2018 w3c/woff#17, by @svgeesus.
-
2 pull requests merged.
-
Update to 14496-22:2019 and CSS Fonts 3 Rec, 2018 w3c/woff#17.
-
2 pull requests received 5 new comments.
-
Inline editorial corrections, promte substantive to Proposed Corrections w3c/woff#18 (3 comments by @svgeesus, @vlevantovsky)
-
Update to 14496-22:2019 and CSS Fonts 3 Rec, 2018 w3c/woff#17 (2 comments by @svgeesus, @vlevantovsky)
-