-
Notifications
You must be signed in to change notification settings - Fork 243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for multiple extensions to same target introduce the translations bug #7790
Comments
Thanks for bringing this also to my attention - I am currently splitting my objects, and only now I'm seeing that I'm affected as well. It also affects page extensions. The first page extension caption changes are considered, the second page extension (in my case for an action) is not. @BazookaMusic Losing translations is a major issue for every AppSource developer. It would be good to give this issue some higher priority. |
I'll accept this as it's clearly a bug across compiler and runtime and has direct customer impact |
Microsoft does not fully follow the xliff standard when creating the *.g.xlf we use to copy. - <file datatype="xml" source-language="en-US" target-language="de-DE" original="Awesome App" tool-id="MultilingualAppToolkit" product-name="n/a" product-version="n/a" build-num="n/a">
+ <file datatype="xml" source-language="en-US" target-language="de-DE" original="Awesome App.g.xlf" tool-id="MultilingualAppToolkit" product-name="n/a" product-version="n/a" build-num="n/a"> Colleagues created a support request |
@BazookaMusic Can you give an update, please? |
@thpeder is working on this so I'll let him provide any updates on the progress of this one |
I can give an update since I actually worked on this recently. This has turned out to be a much bigger issue than we first expected. Our plan now is to fix this in BC 24/25 (it is a server side fix) in a minimally disruptive way, the fixes have been merged so I expect the servers to be hotfixed in the next few weeks. But in BC26 onwards, we're rethinking how we do translation keys for extension objects. We haven't fully settled on the solution yet, but it's likely that there will be some changes in BC26 for extension object translation keys across the board. |
1. Describe the bug
When using multiple table extensions to same table then translations does not work correctly.
Only first table extension is translated.
It is probably due to bad "trans-unit id" in XLF file.
2. To Reproduce
Steps to reproduce the behavior:
3. Expected behavior
The all fields from all table extension are translated.
4. Actual behavior
Only fields from first table extension are translated.
5. Versions:
Internal work item: AB#541532
The text was updated successfully, but these errors were encountered: