Web Fonts Working Group - Activity in 2025
No matches.
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
Shinichiro Yabu (Studio株式会社) joined.
-
GitHub
w3c/ift-client-tests
-
1 pull request opened.
-
Update test-plan.md with the results of working group discussions around client side testing. w3c/ift-client-tests#5, by @garretrieger.
-
-
2 pull requests merged.
-
Update test-plan.md with the results of working group discussions around client side testing. w3c/ift-client-tests#5.
-
Added IFT encoder and outline formats w3c/ift-client-tests#4.
-
-
1 pull request received 2 new comments.
-
Added IFT encoder and outline formats w3c/ift-client-tests#4 (2 comments by @garretrieger, @streude)
-
w3c/ift-encoder
-
3 pull requests opened.
-
Add complex condition finder to the closure segmenter. w3c/ift-encoder#171, by @garretrieger.
-
Formatting. w3c/ift-encoder#170, by @garretrieger.
-
Add font collection fallback glyph closure analysis scripts w3c/ift-encoder#169, by @garretrieger.
-
-
2 pull requests merged.
-
Formatting. w3c/ift-encoder#170.
-
Add font collection fallback glyph closure analysis scripts w3c/ift-encoder#169.
-
-
1 pull request received 18 new comments.
-
Add complex condition finder to the closure segmenter. w3c/ift-encoder#171 (18 comments by @garretrieger, @skef)
-
TR publications
-
1 document published.
-
Incremental Font Transfer published as a Candidate Recommendation Draft. History of Incremental Font Transfer
-
Past meetings
Participants
-
5 participants joined.
-
Sejal Anand (Microsoft Corporation) joined.
-
Takeru Suzuki (Studio株式会社) joined.
-
Taro Nakagami (Studio株式会社) joined.
-
Koyo Isono (Studio株式会社) joined.
-
Yuki Morota (Studio株式会社) joined.
-
-
1 organization joined.
-
Studio株式会社 joined.
-
GitHub
w3c/ift-client-tests
-
1 pull request opened.
-
Added IFT encoder and outline formats w3c/ift-client-tests#4, by @streude.
-
-
1 pull request merged.
-
Test Generation w3c/ift-client-tests#3.
-
-
1 pull request received 1 new comment.
w3c/IFT
-
2 pull requests opened.
-
Nov2025 crd w3c/IFT#305, by @svgeesus.
-
Remove a couple of non-normative musts. w3c/IFT#304, by @garretrieger.
-
-
2 pull requests merged.
-
Nov2025 crd w3c/IFT#305.
-
Remove a couple of non-normative musts. w3c/IFT#304.
-
w3c/ift-encoder
-
3 pull requests opened.
-
For best case size computation add a configurable reduction percentage. w3c/ift-encoder#168, by @garretrieger.
-
Use average rather than minimum probability from the probability bound. w3c/ift-encoder#167, by @garretrieger.
-
Redo the best case probability threshold mechanism. w3c/ift-encoder#166, by @garretrieger.
-
-
5 pull requests merged.
-
For best case size computation add a configurable reduction percentage. w3c/ift-encoder#168.
-
Use average rather than minimum probability from the probability bound. w3c/ift-encoder#167.
-
Redo the best case probability threshold mechanism. w3c/ift-encoder#166.
-
Update closure_glyph_segmentation.md to reflect the current state. w3c/ift-encoder#163.
-
Add built-in support for loading data files from ift-encoder-data. w3c/ift-encoder#165.
-
Past meetings
-
1 meeting.
GitHub
w3c/ift-encoder
-
17 pull requests opened.
-
Add built-in support for loading data files from ift-encoder-data. w3c/ift-encoder#165, by @garretrieger.
-
Add support for loading sharded Riegeli frequency files. w3c/ift-encoder#164, by @garretrieger.
-
Update closure_glyph_segmentation.md to reflect the current state. w3c/ift-encoder#163, by @garretrieger.
-
Add and optional 'preprocess merging' step to the closure segmenter. w3c/ift-encoder#161, by @garretrieger.
-
Add option to estimate brotli compressed sizes w3c/ift-encoder#160, by @garretrieger.
-
Init Font Merging Optimizations and Config Toggle for Enabling/Disabling Patch Merging. w3c/ift-encoder#159, by @garretrieger.
-
Add helper util to convert riegeli frequency data files to human readable format. w3c/ift-encoder#158, by @garretrieger.
-
Implement design space union/subtraction. w3c/ift-encoder#157, by @garretrieger.
-
Clean up closure segmenter logging. w3c/ift-encoder#156, by @garretrieger.
-
In segmenter config add mechanism to make it easier to add optional feature segments. w3c/ift-encoder#155, by @garretrieger.
-
Allow segmentation plan to utilize glyphs in the initial font definition. w3c/ift-encoder#154, by @garretrieger.
-
Fix IsVariable check in compiler. w3c/ift-encoder#153, by @garretrieger.
-
Add optional fallback merge group in segmenter config. w3c/ift-encoder#152, by @garretrieger.
-
Update closure segmenter to be able to do merging for multiple script frequency data sets. w3c/ift-encoder#151, by @garretrieger.
-
Add alternative style merging operation: patch combination merge. w3c/ift-encoder#149, by @garretrieger.
-
-
15 pull requests merged.
-
Add support for loading sharded Riegeli frequency files. w3c/ift-encoder#164.
-
Add and optional 'preprocess merging' step to the closure segmenter. w3c/ift-encoder#161.
-
Add option to estimate brotli compressed sizes w3c/ift-encoder#160.
-
Add helper util to convert riegeli frequency data files to human readable format. w3c/ift-encoder#158.
-
Implement design space union/subtraction. w3c/ift-encoder#157.
-
Clean up closure segmenter logging. w3c/ift-encoder#156.
-
Allow segmentation plan to utilize glyphs in the initial font definition. w3c/ift-encoder#154.
-
Fix IsVariable check in compiler. w3c/ift-encoder#153.
-
Add optional fallback merge group in segmenter config. w3c/ift-encoder#152.
-
Add alternative style merging operation: patch combination merge. w3c/ift-encoder#149.
-
w3c/ift-encoder-data
-
3 pull requests opened.
-
Add the actual data files and remove the download script. w3c/ift-encoder-data#3, by @garretrieger.
-
Fix script name in README.md w3c/ift-encoder-data#2, by @garretrieger.
-
-
3 pull requests merged.
-
Add the actual data files and remove the download script. w3c/ift-encoder-data#3.
-
Fix script name in README.md w3c/ift-encoder-data#2.
-
w3c/ift-client-tests
-
1 pull request opened.
-
Test Generation w3c/ift-client-tests#3, by @streude.
-
-
1 pull request merged.
-
Start a test plan document. w3c/ift-client-tests#2.
-
-
2 pull requests received 12 new comments.
w3c/IFT
-
2 pull requests opened.
-
Back to Editor's Draft w3c/IFT#303, by @svgeesus.
-
Add conform, client classes to normative algorithms. w3c/IFT#302, by @garretrieger.
-
-
2 pull requests merged.
-
Back to Editor's Draft w3c/IFT#303.
-
Add conform, client classes to normative algorithms. w3c/IFT#302.
-
-
1 pull request received 5 new comments.
-
Add conform, client classes to normative algorithms. w3c/IFT#302 (5 comments by @garretrieger, @svgeesus, @vlevantovsky)
-
Past meetings
Participants
-
3 participants joined.
-
Sakito Mukai (Cybozu) joined.
-
Kazuhiro Tobita (Cybozu) joined.
-
Cybozu W3C (Cybozu) joined.
-
-
1 organization joined.
-
Cybozu joined.
-
GitHub
w3c/ift-encoder
-
1 issue received 2 new comments.
-
Implement serialization of a Format 1 Patch map w3c/ift-encoder#107 (2 comments by @garretrieger, @RoelN)
-
-
6 pull requests opened.
-
Refactor GlyphGroupings to use separate exclusive glyphs grouping. w3c/ift-encoder#148, by @garretrieger.
-
Implement Bigram Probability Cost based merging. w3c/ift-encoder#145, by @garretrieger.
-
compile error on linux system w3c/ift-encoder#144, by @bhoehl.
-
Prepare cost based merging to be able to optionally utilize code point pair frequencies. w3c/ift-encoder#143, by @garretrieger.
-
-
7 pull requests merged.
-
Refactor GlyphGroupings to use separate exclusive glyphs grouping. w3c/ift-encoder#148.
-
Implement Bigram Probability Cost based merging. w3c/ift-encoder#145.
-
compile error on linux system w3c/ift-encoder#144.
-
Optimizations to cost based segment merging. w3c/ift-encoder#142.
-
w3c/ift-client-tests
-
1 pull request opened.
-
Start a test plan document. w3c/ift-client-tests#2, by @garretrieger.
-
-
1 pull request received 2 new comments.
w3c/IFT
-
1 pull request opened.
-
Add client/encoder tags to the conformance spans. w3c/IFT#301, by @garretrieger.
-
-
1 pull request merged.
-
Add client/encoder tags to the conformance spans. w3c/IFT#301.
-
-
1 pull request received 13 new comments.
-
Add client/encoder tags to the conformance spans. w3c/IFT#301 (13 comments by @garretrieger, @svgeesus)
-
Past meetings
-
1 meeting.
GitHub
w3c/ift-client-tests
-
1 pull request opened.
-
Coverage check w3c/ift-client-tests#1, by @streude.
-
-
1 pull request merged.
-
Coverage check w3c/ift-client-tests#1.
-
w3c/IFT
-
2 issues closed.
-
RFC2119 should inside non-normative Note w3c/IFT#289.
-
1 issue received 1 new comment.
-
6 pull requests opened.
-
Update Overview.html to reflect recent changes. w3c/IFT#300, by @garretrieger.
-
Remove conformance keyword from 'font subset' definition. w3c/IFT#295, by @garretrieger.
-
Remove conformance keywords (should) from 'Note:' in 4.6 w3c/IFT#294, by @garretrieger.
-
Create conform.css w3c/IFT#293, by @svgeesus.
-
Rebuild HTML to include changes from #291 w3c/IFT#292, by @garretrieger.
-
Added conformance span tags to Overview.bs w3c/IFT#291, by @streude.
-
-
6 pull requests merged.
-
Create conform.css w3c/IFT#293.
-
Update Overview.html to reflect recent changes. w3c/IFT#300.
-
Rebuild HTML to include changes from #291 w3c/IFT#292.
-
Added conformance span tags to Overview.bs w3c/IFT#291.
-
-
2 pull requests received 10 new comments.
w3c/ift-encoder
-
1 pull request opened.
-
Optimizations to cost based segment merging. w3c/ift-encoder#142, by @garretrieger.
-
-
1 pull request merged.
-
Experimental cost based segment merging implementation. w3c/ift-encoder#141.
-
w3c/woff
-
1 issue opened.
TR publications
-
2 documents published.
-
Incremental Font Transfer published as a Candidate Recommendation Snapshot. History of Incremental Font Transfer
-
Incremental Font Transfer published as a Working Draft. History of Incremental Font Transfer
-
Past meetings
Participants
-
1 participant joined.
-
Milan Ramadev (Monotype) joined.
-
GitHub
w3c/IFT
-
3 issues opened.
-
RFC2119 should inside non-normative Note w3c/IFT#289, by @svgeesus.
-
Undesirable use of "should" in definition of font subset w3c/IFT#288, by @svgeesus.
-
Better definition for text shaping w3c/IFT#285, by @svgeesus.
-
-
2 issues closed.
-
Better definition for text shaping w3c/IFT#285.
-
Review feedback wrt making spec more readable w3c/IFT#213.
-
-
3 issues received 12 new comments.
-
Considerations for "desiccated" initial font files w3c/IFT#201 (3 comments by @garretrieger, @skef, @svgeesus)
-
5 pull requests opened.
-
Mark appendix b (examples) as non normative. w3c/IFT#290, by @garretrieger.
-
CR July 2025 w3c/IFT#287, by @svgeesus.
-
Cleanup references to rfc6570. w3c/IFT#284, by @garretrieger.
-
[editorial] Updated changes since 20 Feb WD w3c/IFT#283, by @svgeesus.
-
-
5 pull requests merged.
-
Mark appendix b (examples) as non normative. w3c/IFT#290.
-
CR July 2025 w3c/IFT#287.
-
Cleanup references to rfc6570. w3c/IFT#284.
-
[editorial] Updated changes since 20 Feb WD w3c/IFT#283.
-
-
2 pull requests received 11 new comments.
w3c/ift-encoder
-
1 issue closed.
-
Pull in the list of always on features from the specification. w3c/ift-encoder#106.
-
-
5 pull requests opened.
-
Experimental cost based segment merging implementation. w3c/ift-encoder#141, by @garretrieger.
-
Fix bad url template in closure segmenter util. w3c/ift-encoder#140, by @garretrieger.
-
Split all of the helper classes in closure glyph segmenter out. w3c/ift-encoder#139, by @garretrieger.
-
Use IFT spec default feature registry. w3c/ift-encoder#138, by @garretrieger.
-
Improve Encoding of Table Keyed Patch Maps w3c/ift-encoder#137, by @garretrieger.
-
-
4 pull requests merged.
-
Fix bad url template in closure segmenter util. w3c/ift-encoder#140.
-
Split all of the helper classes in closure glyph segmenter out. w3c/ift-encoder#139.
-
Use IFT spec default feature registry. w3c/ift-encoder#138.
-
Improve Encoding of Table Keyed Patch Maps w3c/ift-encoder#137.
-
Past meetings
-
1 meeting.
GitHub
w3c/ift-encoder
-
1 issue opened.
-
[DELETED] Created in wrong repository by mistake w3c/ift-encoder#136, by @terkel.
-
-
1 issue closed.
-
[DELETED] Created in wrong repository by mistake w3c/ift-encoder#136.
-
-
1 issue received 2 new comments.
-
7 pull requests opened.
-
Rename Encoder and Encoder Config to Compiler and Segmentation Plan w3c/ift-encoder#135, by @garretrieger.
-
Some cleanup and a bug fix in the encoder implementation. w3c/ift-encoder#134, by @garretrieger.
-
Add a document detailing how the encoder implementation works. w3c/ift-encoder#133, by @garretrieger.
-
Use full invalidation (instead of partial) patches when modifying design space. w3c/ift-encoder#132, by @garretrieger.
-
Update URL templates to the new opcode format. w3c/ift-encoder#131, by @garretrieger.
-
Update bazel deps to latest versions and add some bazelrc flags for osx compilation. w3c/ift-encoder#130, by @garretrieger.
-
Implement support for optional layout feature segmentation and encoding. w3c/ift-encoder#129, by @garretrieger.
-
-
7 pull requests merged.
-
Add a document detailing how the encoder implementation works. w3c/ift-encoder#133.
-
Rename Encoder and Encoder Config to Compiler and Segmentation Plan w3c/ift-encoder#135.
-
Some cleanup and a bug fix in the encoder implementation. w3c/ift-encoder#134.
-
Use full invalidation (instead of partial) patches when modifying design space. w3c/ift-encoder#132.
-
Update URL templates to the new opcode format. w3c/ift-encoder#131.
-
Implement support for optional layout feature segmentation and encoding. w3c/ift-encoder#129.
-
Update bazel deps to latest versions and add some bazelrc flags for osx compilation. w3c/ift-encoder#130.
-
-
2 pull requests received 16 new comments.
-
Add a document detailing how the encoder implementation works. w3c/ift-encoder#133 (15 comments by @garretrieger, @skef)
-
Implement support for optional layout feature segmentation and encoding. w3c/ift-encoder#129 (1 comment by @skef)
-
w3c/IFT
-
5 issues closed.
-
Use of URI templates seems problematic w3c/IFT#259.
-
Wide Review of 20 Feb 2025 WD of IFT w3c/IFT#193.
-
4 issues received 8 new comments.
-
Work through privacy implications of new patch patterns w3c/IFT#267 (3 comments by @garretrieger, @svgeesus)
-
2 pull requests opened.
-
Expand privacy section to provide guidance for encoders. w3c/IFT#282, by @garretrieger.
-
-
3 pull requests merged.
-
3 pull requests received 33 new comments.
-
Drop rfc6570 uri templates, replace with opcode encoded template. w3c/IFT#281 (20 comments by @garretrieger, @skef, @svgeesus)
-
[IFT] add more specific information on configuring the fetch request. w3c/IFT#280 (7 comments by @garretrieger, @noamr, @svgeesus)
-
Expand privacy section to provide guidance for encoders. w3c/IFT#282 (6 comments by @garretrieger, @svgeesus)
-
Past meetings
-
1 meeting.
GitHub
w3c/IFT
-
4 issues opened.
-
Make non-invalidating patch request ordering deterministic. w3c/IFT#277, by @garretrieger.
-
Load patch file fetching algorithms is lacking details w3c/IFT#276, by @annevk.
-
Leaking exact content of an element? w3c/IFT#272, by @svgeesus.
-
-
4 issues closed.
-
Leaking exact content of an element? w3c/IFT#272.
-
General recommendations for WOFF2 IFT w3c/IFT#270.
-
5 issues received 25 new comments.
-
Leaking exact content of an element? w3c/IFT#272 (13 comments by @annevk, @garretrieger, @jandrieu, @skef, @svgeesus)
-
General recommendations for WOFF2 IFT w3c/IFT#270 (7 comments by @garretrieger, @jlarmstrongiv, @svgeesus)
-
Load patch file fetching algorithms is lacking details w3c/IFT#276 (3 comments by @annevk, @garretrieger)
-
Load patch file does not define what happens when the URL fails to parse w3c/IFT#275 (1 comment by @garretrieger)
-
-
5 pull requests opened.
-
Specify what to do if URL parsing fails. w3c/IFT#278, by @garretrieger.
-
5 pull requests merged.
-
Specify what to do if URL parsing fails. w3c/IFT#278.
-
2 pull requests received 6 new comments.
-
Specify a selection/fetch ordering for non-invalidating patches. w3c/IFT#279 (4 comments by @garretrieger, @skef)
-
Add a note about optimizing glyph keyed patch application when multiple patches are present. w3c/IFT#274 (2 comments by @garretrieger, @skef)
-
w3c/ift-encoder
-
2 issues closed.
-
Change Encoder::OutgoingEdges mechanism to use the multi-patch feature w3c/ift-encoder#103.
-
Extend encoder to support CFF/CFF2 w3c/ift-encoder#102.
-
-
2 issues received 2 new comments.
-
Change Encoder::OutgoingEdges mechanism to use the multi-patch feature w3c/ift-encoder#103 (1 comment by @garretrieger)
-
-
4 pull requests opened.
-
In font2ift by default output a woff2 encoded font with an option to disable. w3c/ift-encoder#128, by @garretrieger.
-
Update README to remove sentence about CFF/CFF2 not being supported. w3c/ift-encoder#127, by @garretrieger.
-
Implement patch preload lists in the encoder w3c/ift-encoder#126, by @garretrieger.
-
[closure segmenter] Further speed up the closure segmenter run time. w3c/ift-encoder#125, by @garretrieger.
-
-
4 pull requests merged.
-
In font2ift by default output a woff2 encoded font with an option to disable. w3c/ift-encoder#128.
-
Update README to remove sentence about CFF/CFF2 not being supported. w3c/ift-encoder#127.
-
Implement patch preload lists in the encoder w3c/ift-encoder#126.
-
[closure segmenter] Further speed up the closure segmenter run time. w3c/ift-encoder#125.
-
Past meetings
Participants
-
1 participant joined.
-
Dileep Maurya (Microsoft Corporation) joined.
-
GitHub
w3c/IFT
-
2 issues opened.
-
General recommendations for WOFF2 IFT w3c/IFT#270, by @svgeesus.
-
Work through privacy implications of new patch patterns w3c/IFT#267, by @skef.
-
-
4 issues closed.
-
Shared Brotli ID is expired w3c/IFT#101.
-
Clarify handling of CFF and CFF2 w3c/IFT#260.
-
Possible "all other codepoints" semantic? w3c/IFT#192.
-
-
8 issues received 16 new comments.
-
Use of URI templates seems problematic w3c/IFT#259 (7 comments by @annevk, @garretrieger, @sisidovski, @svgeesus)
-
-
4 pull requests opened.
-
Update to (current) shared brotli 15, #101 w3c/IFT#269, by @svgeesus.
-
[explainer] WebKit is now positive w3c/IFT#268, by @svgeesus.
-
3 pull requests merged.
-
Update to (current) shared brotli 15, #101 w3c/IFT#269.
-
[explainer] WebKit is now positive w3c/IFT#268.
-
-
2 pull requests received 3 new comments.
w3c/ift-encoder
-
13 pull requests opened.
-
[closure segmenter] Add incremental glyph grouping to the closure segmenter merging loop. w3c/ift-encoder#124, by @garretrieger.
-
[closure segmenter] remove conditions that become empty. w3c/ift-encoder#123, by @garretrieger.
-
More ideas on segmentation relating to layout features w3c/ift-encoder#122, by @skef.
-
Add CFF/CFF2 support into the glyph keyed closure segmenter util. w3c/ift-encoder#121, by @garretrieger.
-
Allow the set of initial codepoints to be specified in closure_glyph_keyed_segmenter_util. w3c/ift-encoder#120, by @garretrieger.
-
Consolidate usages of hb_set_unique_ptr, flat_hash_set, and btree_set to IntSet. w3c/ift-encoder#119, by @garretrieger.
-
Create a wrapper around hb_set_t, IntSet, that acts like a standard collection class. w3c/ift-encoder#118, by @garretrieger.
-
Add an end to end testing shell script. w3c/ift-encoder#117, by @garretrieger.
-
Make GlyphSegmentation file encapsulation match object encapsulation w3c/ift-encoder#116, by @skef.
-
Some segmentation principles w3c/ift-encoder#115, by @skef.
-
Set cff charstring offset flags in format 2. w3c/ift-encoder#114, by @garretrieger.
-
Add CFF/CFF2 charstring offsets to encoded fonts. w3c/ift-encoder#113, by @garretrieger.
-
Add support for encoding CFF2 fonts. w3c/ift-encoder#112, by @garretrieger.
-
-
13 pull requests merged.
-
More ideas on segmentation relating to layout features w3c/ift-encoder#122.
-
[closure segmenter] remove conditions that become empty. w3c/ift-encoder#123.
-
Add CFF/CFF2 support into the glyph keyed closure segmenter util. w3c/ift-encoder#121.
-
Consolidate usages of hb_set_unique_ptr, flat_hash_set, and btree_set to IntSet. w3c/ift-encoder#119.
-
Some segmentation principles w3c/ift-encoder#115.
-
Add an end to end testing shell script. w3c/ift-encoder#117.
-
Make GlyphSegmentation file encapsulation match object encapsulation w3c/ift-encoder#116.
-
Set cff charstring offset flags in format 2. w3c/ift-encoder#114.
-
Add CFF/CFF2 charstring offsets to encoded fonts. w3c/ift-encoder#113.
-
Add support for encoding CFF2 fonts. w3c/ift-encoder#112.
Lifecycle
-
1 charter started.
-
Chartered until 21 March 2027.
-
Past meetings
Participants
-
1 participant joined.
-
Yongji Chen (Monotype) joined.
-
-
3 participants left.
-
Sahil Dua (Monotype) left.
-
Christopher Chapman (Adobe) left.
-
Persa Zula (Adobe) left.
-
GitHub
w3c/IFT
-
2 issues opened.
-
Clarify handling of CFF and CFF2 w3c/IFT#260, by @skef.
-
Use of URI templates seems problematic w3c/IFT#259, by @annevk.
-
-
1 issue closed.
-
Rechartering for 2025-26 w3c/IFT#248.
-
-
4 issues received 39 new comments.
-
Use of URI templates seems problematic w3c/IFT#259 (21 comments by @annevk, @garretrieger, @sisidovski, @skef, @svgeesus)
-
Clarify handling of CFF and CFF2 w3c/IFT#260 (14 comments by @garretrieger, @jfkthame, @skef, @svgeesus)
-
-
5 pull requests opened.
-
Add CFF specific requirements for IFT w3c/IFT#264, by @garretrieger.
-
Switch to WhatWG URL and Limit URL Templates to level 1 w3c/IFT#263, by @garretrieger.
-
5 pull requests merged.
-
Add CFF specific requirements for IFT w3c/IFT#264.
-
4 pull requests received 20 new comments.
-
Switch to WhatWG URL and Limit URL Templates to level 1 w3c/IFT#263 (11 comments by @garretrieger, @skef, @svgeesus)
-
Spec changes to allow entries to optionally include patch preload lists. w3c/IFT#262 (6 comments by @garretrieger, @skef)
-
For fonts with CFF or CFF2 tables add a field to the patch map with o w3c/IFT#265 (2 comments by @garretrieger, @skef)
-
w3c/ift-encoder
-
7 issues opened.
-
Remove the "last gid" hack from encoder implementation w3c/ift-encoder#108, by @garretrieger.
-
Implement serialization of a Format 1 Patch map w3c/ift-encoder#107, by @garretrieger.
-
Pull in the list of always on features from the specification. w3c/ift-encoder#106, by @garretrieger.
-
Potential special handling of "alt" features w3c/ift-encoder#105, by @skef.
-
Change implementation of desiccated font files w3c/ift-encoder#104, by @skef.
-
Change Encoder::OutgoingEdges mechanism to use the multi-patch feature w3c/ift-encoder#103, by @skef.
-
Extend encoder to support CFF/CFF2 w3c/ift-encoder#102, by @skef.
-
-
2 issues closed.
-
Add support for VCDIFF w3c/ift-encoder#31.
-
-
5 issues received 9 new comments.
-
Potential special handling of "alt" features w3c/ift-encoder#105 (4 comments by @garretrieger, @skef)
-
Change implementation of desiccated font files w3c/ift-encoder#104 (2 comments by @garretrieger, @skef)
-
Remove the "last gid" hack from encoder implementation w3c/ift-encoder#108 (1 comment by @garretrieger)
-
Update SparseBitSet implementation to support variable branch factor and intervals w3c/ift-encoder#32 (1 comment by @garretrieger)
-
-
4 pull requests opened.
-
Add encoder support for CFF fonts w3c/ift-encoder#111, by @garretrieger.
-
Update README and add utility for generating Table Keyed (Non Glyph) encoder configs w3c/ift-encoder#110, by @garretrieger.
-
Bug fix: don't include gvar in all table keyed patches. w3c/ift-encoder#109, by @garretrieger.
-
Add capability to convert from a GlyphSegmentation to an encoder config. w3c/ift-encoder#101, by @garretrieger.
-
-
6 pull requests merged.
-
Add encoder support for CFF fonts w3c/ift-encoder#111.
-
Update README and add utility for generating Table Keyed (Non Glyph) encoder configs w3c/ift-encoder#110.
-
Bug fix: don't include gvar in all table keyed patches. w3c/ift-encoder#109.
-
Add a document explaining how the glyph keyed segment generation process works. w3c/ift-encoder#97.
-
Add capability to convert from a GlyphSegmentation to an encoder config. w3c/ift-encoder#101.
-
-
3 pull requests received 6 new comments.
-
Add a document explaining how the glyph keyed segment generation process works. w3c/ift-encoder#97 (4 comments by @garretrieger, @skef)
-
Add capability to convert from a GlyphSegmentation to an encoder config. w3c/ift-encoder#101 (1 comment by @garretrieger)
-
TR publications
-
1 document published.
-
Incremental Font Transfer published as a Working Draft. History of Incremental Font Transfer
-
Past meetings
-
1 meeting.
GitHub
w3c/ift-encoder
-
6 pull requests opened.
-
Fix overflow on short loca with offset values > 65536. w3c/ift-encoder#100, by @garretrieger.
-
Rework the encoder api to specify conditions with codepoints instead of gids w3c/ift-encoder#99, by @garretrieger.
-
Decouple the closure based glyph segmentation functionality from GlyphSegmentation. w3c/ift-encoder#98, by @garretrieger.
-
Add a document explaining how the glyph keyed segment generation process works. w3c/ift-encoder#97, by @garretrieger.
-
In the glyph keyed segmenter implement merging of base patches w3c/ift-encoder#96, by @garretrieger.
-
Activation conditions and child entry indices w3c/ift-encoder#95, by @garretrieger.
-
-
4 pull requests merged.
-
Rework the encoder api to specify conditions with codepoints instead of gids w3c/ift-encoder#99.
-
Fix overflow on short loca with offset values > 65536. w3c/ift-encoder#100.
-
In the glyph keyed segmenter implement merging of base patches w3c/ift-encoder#96.
-
Activation conditions and child entry indices w3c/ift-encoder#95.
-
-
1 pull request closed.
-
2 pull requests received 40 new comments.
-
Add a document explaining how the glyph keyed segment generation process works. w3c/ift-encoder#97 (37 comments by @garretrieger, @skef, @svgeesus)
-
Decouple the closure based glyph segmentation functionality from GlyphSegmentation. w3c/ift-encoder#98 (3 comments by @garretrieger, @skef)
-
w3c/IFT
-
2 issues opened.
-
Republish a Working Draft w3c/IFT#256, by @svgeesus.
-
Stakeholder feedback w3c/IFT#253, by @svgeesus.
-
-
4 issues closed.
-
Republish a Working Draft w3c/IFT#256.
-
Stakeholder feedback w3c/IFT#253.
-
-
5 issues received 10 new comments.
-
5 pull requests opened.
-
Changes for February Working Draft, #256 w3c/IFT#258, by @svgeesus.
-
[Explainer] Update stakeholder positions, fix #253 w3c/IFT#257, by @svgeesus.
-
[Explainer] Update TOC w3c/IFT#255, by @svgeesus.
-
Rewrite explainer to say what IFT does w3c/IFT#254, by @svgeesus.
-
Rework the copy indices mechanism w3c/IFT#252, by @garretrieger.
-
-
5 pull requests merged.
-
Changes for February Working Draft, #256 w3c/IFT#258.
-
Rework the copy indices mechanism w3c/IFT#252.
-
[Explainer] Update stakeholder positions, fix #253 w3c/IFT#257.
-
[Explainer] Update TOC w3c/IFT#255.
-
Rewrite explainer to say what IFT does w3c/IFT#254.
-
-
2 pull requests received 52 new comments.
-
Rewrite explainer to say what IFT does w3c/IFT#254 (9 comments by @garretrieger, @svgeesus, @vlevantovsky)
Past meetings
Participants
-
2 participants joined.
-
Scott Treude (Monotype) joined.
-
Vinay Singh (Microsoft Corporation) joined.
-
-
1 participant left.
-
Adam Langley (Google LLC) left.
-
GitHub
w3c/IFT
-
2 issues received 2 new comments.
-
3 pull requests opened.
-
[editorial] back to ED, remove hardcoded date w3c/IFT#250, by @svgeesus.
-
Some clarifications around uri templates w3c/IFT#249, by @garretrieger.
-
3 pull requests merged.
-
[editorial] back to ED, remove hardcoded date w3c/IFT#250.
-
Some clarifications around uri templates w3c/IFT#249.
-
1 pull request received 2 new comments.
w3c/ift-encoder
-
11 pull requests opened.
-
Begin implementing a prototype Glyph segmenter w3c/ift-encoder#94, by @garretrieger.
-
Allow encoder to use short loca when possible. w3c/ift-encoder#93, by @garretrieger.
-
Add a utility that can convert from an IFTB info dump into an encoder config w3c/ift-encoder#92, by @garretrieger.
-
Add support for design space segments to font2ift. w3c/ift-encoder#91, by @garretrieger.
-
Cleanup remaining references to IFTB w3c/ift-encoder#90, by @garretrieger.
-
Update the encoder api and config to not utilize IFTB patches as inputs w3c/ift-encoder#89, by @garretrieger.
-
Remove js_client and get hedron working again. w3c/ift-encoder#88, by @garretrieger.
-
Reenable integration tests using the fontations rust client. w3c/ift-encoder#86, by @garretrieger.
-
Add support for generating glyph keyed patches w3c/ift-encoder#85, by @garretrieger.
-
Begin updating the encoder to be compliant with the current specification. w3c/ift-encoder#84, by @garretrieger.
-
-
10 pull requests merged.
-
Begin implementing a prototype Glyph segmenter w3c/ift-encoder#94.
-
Allow encoder to use short loca when possible. w3c/ift-encoder#93.
-
Add a utility that can convert from an IFTB info dump into an encoder config w3c/ift-encoder#92.
-
Add support for design space segments to font2ift. w3c/ift-encoder#91.
-
Cleanup remaining references to IFTB w3c/ift-encoder#90.
-
Update the encoder api and config to not utilize IFTB patches as inputs w3c/ift-encoder#89.
-
Remove js_client and get hedron working again. w3c/ift-encoder#88.
-
Reenable integration tests using the fontations rust client. w3c/ift-encoder#86.
-
Add support for generating glyph keyed patches w3c/ift-encoder#85.
-
Begin updating the encoder to be compliant with the current specification. w3c/ift-encoder#84.
-