The locale manifests have licenses in there, and proprietary ones are "License: Proprietary". Not sure what happens if there's no license on something, but it probably either counts as proprietary or doesn't display it. The only drawback is that we'll need to parse the manifests and it won't work with non-English manifests without having a list of potential matches for "proprietary". Actually, just having a list of potential matches (I'll do English, then Simplified Chinese, then other languages as those two seem to be the most prominent main locale manifest languages in the winget-pkgs repo last I checked) is way better than having to use a translation thing. Probably could use a Switch...Case statement on String.Contains to reduce the needed cycles.
Licenses won't be shown in a column, only used to determine if we should display a package based on the user's preferences.
The locale manifests have licenses in there, and proprietary ones are "License: Proprietary". Not sure what happens if there's no license on something, but it probably either counts as proprietary or doesn't display it. The only drawback is that we'll need to parse the manifests and it won't work with non-English manifests without having a list of potential matches for "proprietary". Actually, just having a list of potential matches (I'll do English, then Simplified Chinese, then other languages as those two seem to be the most prominent main locale manifest languages in the winget-pkgs repo last I checked) is way better than having to use a translation thing. Probably could use a Switch...Case statement on String.Contains to reduce the needed cycles.
Licenses won't be shown in a column, only used to determine if we should display a package based on the user's preferences.