P.S.A. Font Contributions

[denelon]

We're in the process of standing up the new font source for WinGet.

We will not be accepting community contributions until after the WinGet 1.12 client has rolled out to a majority of users to make sure folks don't have a bad experience trying to install fonts with older clients.

The first PR has been merged for fonts in the "/fonts" directory.

With preview versions of WinGet it will be possible to install the fonts using those manifests directly.

[DandelionSprout]

Looking through https://github.com/microsoft/winget-pkgs/tree/master/fonts/m/Microsoft/FluentFonts/1.0.0.0 as makeshift documentation, I notice it relies on a "Not yet released that I currently know of" Manifest 1.12, which makes me wonder about two things in particular:

• Any reason why Manifest 1.11 has been skipped (unless 1.12 indeed remains planned for release at some later point than a 1.11 release)?
• Would it be too late for me to suggest ideas for Manifests 1.12 and/or 1.11? I've been planning to suggest increasing the max number of tags from 16 to 50 (but I never got around to suggesting it), though admittedly only sporadic situations like the Epic Games Launcher and AOMEI Partition Assistant packages would've benefitted from such an increase.

[denelon]

@DandelionSprout there were no schema changes for WinGet 1.11 so we didn't release a new version of the schema. There are schema changes in 1.12 so we bumped up the minor schema version and added the new non-breaking elements.

Feel free to create an Issue (Feature) over at winget-cli to increase the number of allowed tags. It is probably a relatively small change for client validation and for the REST source. No guarantee that it will get prioritized but it might be small enough for a community contribution.

[RokeJulianLockhart]

@denelon, with winget-cli/issues/166#issuecomment-3433573409 completed, is submitting font requests now acceptable? I ask per issues/306015, which I filed before reading this...

[DandelionSprout]

As far as I can personally tell, the 1.12 manifest has not been formally completed yet. I know that since it is (or has been?) debated in microsoft/winget-cli#5784 whether it was viable to squeeze in an increase in the amount of allowed tags in time for 1.12 or not.

I myself have a package for the Nishiki-teki font ready for submission pretty much as soon as community font PRs get the go-ahead, however.

[denelon]

We typically don't accept newer schema submissions until a few weeks after the client is rolled out to make sure most folks get the benefits offered in the new release with new schema version behavior.

Fonts is a bit of a snowflake here as it's a separate source with "explicit: true' targeting. We're still doing the full end-to-end validation on the validation infrastructure and publishing infrastructure side with fonts which is why we added the first couple to the repository. We will start slow to make sure to try and catch/resolve any problems before we open up fonts for community submission which may end up being slightly after the manifest submissions for 1.12 start flowing.

That's why this issue was pinned 👍