Replies: 1 comment 2 replies
-
|
I bet you all here this a lot... Thanks for reading my post. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
This is the second release candidate build of Windows Package Manager v1.12. If you find any bugs or problems, please help us out by filing an issue.
New in v1.12
winget mcpfor assistance on configuring your client.Fontas anInstallerTypeandNestedInstallerType.Bug Fixes
UTF-8 BOMencoding when the schema header is on the first lineFont Support
Font Install and Uninstall via manifest and package source for user and machine scopes has been added.
A sample Font manifest can be found at:
https://github.com/microsoft/winget-pkgs/tree/master/fonts/m/Microsoft/FluentFonts/1.0.0.0
At this time install and removal of fonts is only supported for fonts installed via WinGet Package.
Fonts must either be the Installer or a .zip archive of NestedInstaller fonts.
A new explicit source for fonts has been added "winget-font".
winget search font -s winget-fontThis source is not yet accepting public submissions at this time.
Experimental Features
Experimental support for Fonts
The following snippet enables experimental support for fonts via
winget settings. Thewinget font listcommand will list installed font families and the number of installed font faces.{ "$schema" "https://aka.ms/winget-settings.schema.json", "experimentalFeatures": { "fonts": true } }The font 'list' command has been updated with a new '--details' feature for an alternate view of the installed fonts.
What's Changed
New Contributors
Full Changelog: v1.11.400...v1.12.350
This discussion was created from the release Windows Package Manager 1.12.350.
Beta Was this translation helpful? Give feedback.
All reactions