Feature proposal:Hope to increase the resolution of resources.pri in the language resource package

[Gaoyifei1011]

Describe the bug

Feature proposal:Feature proposal:Hope to increase the resolution of resources.pri in the language resource package

----------------------------------

希望能增加对语言资源包的 resources.pri 的解析

---

目前可以通过 ResourceLoader API 来读取本地 resources.pri 的文件信息，但是部分安装包里面包含语言资源包，里面单独存放了特定语言下的 resources.pri。如果使用 makepri.exe 解析，需要使用 /ExternalSchema 参数，并添加应用包的 resources.pri 才能解析成功。所以希望 WASDK 在 MRT Core 也能增加相应的功能。

----------------------------------

Currently, you can read the local resources.pri file information through the ResourceLoader API. However, some installation packages contain language resource packages, which separately store resources.pri in a specific language. If makepri.exe is used for parsing, you need to use the /ExternalSchema parameter and add resources.pri of the application package to make the parsing successful. Therefore, it is hoped that WASDK can also add corresponding functions in MRT Core.

---

For example, the simplified Chinese resource file of Notepad and the resource file corresponding to the Notepad installation package

----------------------------------

比如，记事本的简体中文资源文件和记事本安装包对应的资源文件

Steps to reproduce the bug

See description

Expected behavior

See description

Screenshots

See description

NuGet package version

Windows App SDK 1.6.3: 1.6.250108002

Packaging type

Packaged (MSIX)

Windows version

Windows 11 version 24H2 (22621, October 2024 Update)

IDE

Visual Studio 2022

Additional context

None

[similar-issues-ai]

We've found some similar issues:

• Feature proposal:Hope to read Pri file resource content from stream #5068 , similarity score: 83%

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

[Gaoyifei1011]

We've found some similar issues:

• Feature proposal:Hope to read Pri file resource content from stream #5068 , similarity score: 83%

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

none

[RDMacLachlan]

Can you help us to understand what specifically you are interested in with this feature request. Are you looking for: Increase the list of Screen Resolutions as available settings, if so what specifically?

[Gaoyifei1011]

Can you help us to understand what specifically you are interested in with this feature request. Are you looking for: Increase the list of Screen Resolutions as available settings, if so what specifically?

The reason comes from this
In recent days I tried to build an application package resolver. When I resolved to resources.pri of the application package, I found that the resources.pri of the language resource package needed to rely on the resources.pri of the application package to read properly. However, when I tried to use WASDK's resourcemanager API, I did not find a suitable API call.
Therefore, it is hoped that WASDK's MRT Core can improve the corresponding implementation, and at present, the corresponding resources can only be manually proposed by Makepri.exe program

----------------------------------------

原因来源于此
最近几天我尝试构建一个应用包解析器，当解析到应用包的 resources.pri 时，发现读取语言资源包的 resources.pri 需要依赖应用包的 resources.pri 才能正常读取。然而我尝试使用 WASDK 的 resourcemanager API 时，并没有发现合适的 API 调用。
所以希望 WASDK 的 MRT Core 能够完善相应的实现，目前也只能通过 Makepri.exe 程序来手动提出相应的资源

[DarranRowe]

@RDMacLachlan

My guess is that this is about automatic support for split resources. Right now, the only way split resources will work is if they are in a resource package or if you manually use the .pri. In an unpackaged context, it feels like only a monolithic .pri file is expected.

Suppose you have an unpackaged application with a layout such as:

Where the resources were split but the user wanted the extra resources installed. If the user had the DPI Scale set to 150% then scale-150 would be the better match, but MRT Core will only look in MrtTest.pri in this case, so it will never see the extra resources.