Should all manifests be in English?

[latere-a-latere]

Using @donid's handy dandy WingetRepoBrowser tool I discovered that the packages Tencent.TencentMeeting and Tencent.TencentVideo both have Mandarin descriptions.

While I understand how this happened, Tencent being a Chinese company primarily catering to Chinese users, I was wondering if this should be corrected to an English translation and if all future manifests should be in English. (at least until support for multi-language manifests is added)

These are currently the only two packages that are non-english and I'd rather tackle this early on than later when we have thousands of packages.

[OfficialEsco]

Late answer is better then never
Does the validation fail if you use this? The ManifestSpec dosn't say its NOT supported so...

Localization:
  - Language: es-MX
    Description: Text to display for es-MX
    Homepage: https://github.com/microsoft/msix-packaging/es-MX
    LicenseUrl: https://github.com/microsoft/msix-packaging/blob/master/LICENSE-es-MX

[denelon]

We're currently working through support for multiple languages, and attempting to take a more inclusive approach. One of the thoughts is to provide a "default" locale. That should help with manifests that have been generated without default support for any specific language. One of our goals is to make sure it's relatively simple to add localized content without having to modify the entire manifest. This would allow for example, the two Chinese packages to have the manifest in the original locale, and for others to be able to add a localized description for any other language.

[lychichem]

We're currently working through support for multiple languages, and attempting to take a more inclusive approach. One of the thoughts is to provide a "default" locale. That should help with manifests that have been generated without default support for any specific language. One of our goals is to make sure it's relatively simple to add localized content without having to modify the entire manifest. This would allow for example, the two Chinese packages to have the manifest in the original locale, and for others to be able to add a localized description for any other language.

Maybe what we need is not only localized description, can the installer itself be set to use a local variable given by winget if it support l10n? Or can we use download link like .../firefox-<local>.exe?

[denelon]

The new manifest schema we're working on will support several l10n solutions. I hope we have a JSON schema to share with the new proposal in the coming weeks. You will be able to have descriptive meta-data per locale and/or localized installers. We've seen both scenarios.