Blazor - missing translations

"Regarding the specific items you mentioned, we left the Caption and Tooltip items everywhere where they had non-empty values, so you should not be affected. As far as I understand, you are just clarifying our plans and motivation for this update. Am I correct?"

No - you removed translated Captions - after installing the hotfix - we have missing translations now? see my screens?

Thanks for the confirmation - we will double-check it, because there must be something else then. Please stay tuned.

thx - you removed also many other existing DE translations - just listed some of them

No - you removed translated Captions - after installing the hotfix - we have missing translations now? see my screens?

We discovered that there was a structural anomaly with the DE translations from the very beginning. Translations existed only for the DE culture, but there were no default (en-US) items in RESX or, in turn, in the localization service. Somebody on our side added DE RESX with these strings manually in the past (for example, for the DevExpress.ExpressApp.Notifications.Blazor module). This was incorrect (other people could not see the same localization items in the localization service). Recently, we wrote a test and a removal procedure to detect such anomalies and delete such orphan items (when the base items were non-existent).

We need a day or two to add the base items to the en-US RESX, and then a week or so to update the localization.devexpress.com accordingly. In the meantime, you can use the Model Editor to manually localize these items. We apologize for the inconvenience.

many other existing DE translations - just listed some of them

If you had other non-XAF related translations removed, please list them as well, because each case is unique and there may be different reasons. Thanks.

well the list is quite long - i did not look at all of them - but i think it does not make to list them all here? if you take a look at hotfix 24.2.5.25066 and 24.2.5.25075 you see a lot of .de.resx (and es / ja) files - where translated captions where removed? really across core and multiple modules?

I mostly asked about non-XAF items, if you noticed anything suspicious. We are well aware of the rest XAF items (like this CommonNotificationItem, CriteriaProvider, AboutInfo), which we are removing on purpose as per my original message. The idea is to reduce the number of items to be localized by removing redundant/duplicate and unused in the UI items.

We are dealing with thousands of items and there may be mistakes (even after 3 pairs of eyes), so we appreciate your feedback and understanding.

Sorry Dennis - i missed the non- XAF items. but i still not sure if understand it correctly. we are you for example removing AboutInfo? after the hotfix now those translations are missing? fully understand the idea of removing redundant/duplicate and unused in the UI items - but for example AbountInfo is used at least in winforms?

We noticed that some of our users do not use the AboutInfo mechanism at all and another part localizes the properties at the Application node level, which are then simply reflected in the unchanged AboutInfo_DetailView layout (via a Controller).

Only a tiny group of users customized the AboutInfo_DetailView itself and made localizations there instead of the Application node.

We are not removing the Application node translations, so it should not affect the majority of our users. Would you please clarify your current approach with the About form translation and why you were affected?

I do not talk about the AboutInfo_DetailView - you removed also BOModel - AboutInfo - Caption for example - window title looks now like this:

instead of:

Combined now with this - Xaf.Win - Wrong localization | DevExpress Support - in some minor versions we have a lot of breaking changes regarding localizations!? currently i dont know which localizations are elsewhere missing?

Thank you for the feedback, Noxe - we will return the AboutInfo_DetailView / Caption item. We missed it during our tests (the AboutInfo_DetailView localization is quite complex - strings from multiple unrelated places, and redundant as we see). Please accept our apologies for that.

I can assure you that we always try to minimize the number of changes for existing customers as much as we can. That is why at least 2 native-speaking German translators review changes and a 3rd engineer overviews them as well. Changes are still inevitable when you want to refactor such volumes of localizations, which, by the way, often contain errors (duplicates, unused items, and even sometimes product issues) accumulated over the years and which can be seen in customer apps and are now revealed by the increased number of internal auto-tests we conduct. We also cannot stop doing this revamp, because of the growing demand for easier localizations from both German and non-German customers (e.g., see T1269252 and many similar threads). I wish I had a magical way to keep everything as is and everyone happy, but it is unrealistic in this case - I appreciate your understanding.

The final destination is a Localization project on GitHub containing both RESX/JSON and precompiled assembly/NuGet packages for popular languages along with the tools to build such satellite packages on your own (from your own modifications). We also want to provide a visual tool similar to the one our German translators are using internally, to localize thousands of strings more efficiently (customers can also use or build their own tools above the GitHub one as well).

Thx Dennis - its not the DetailView / Caption - its more the BOModel Caption missing? Fully understand all you say - its just annoying to have them undocumented and between minors - if they are announced i have no problem with them at all. currently the generate lot of wasted time for just installing an minor of an hotfix.

IModelDetailView's Caption is calculated from IModelClass's Caption, so we wanted to leave the last layer only, because it always "wins".

Our v24.2.6 has not been released yet, and we wanted to inform our customers about the removal of empty and duplicateы XAF items via a breaking change, as always. Xaf.Win - Wrong localization | DevExpress Support was just a bug and not a massive change, like this time.

Considering that you have been comparing our source code between versions for years, how would you ideally want to be informed about such localization changes (considering the convenience of perceiving such information with multiple changes)? We will be more than happy to see what else we can do here.

"was just a bug and not a massive change, like this time" that depends - end users are very sensitive about such changes ;)

"how would you ideally want to be informed about such localization changes" - nothing special - BC tickets as always is more then enough!

- end users are very sensitive about such changes ;)

Yeah, no doubt - it is a sensitive topic for all (end-users, DevExpress customers, and us) - we are trying to do our best here and consider all the factors and past experience (for instance, many customers preferred to have the default en-US captions rather than have German nouns in lower case, broken umlauts, or other inconsistencies, which may naturally happen and happened in our community translations after all the user input, AI, human mistakes, etc.).

We need a day or two to add the base items to the en-US RESX, and then a week or so to update the localization.devexpress.com accordingly. In the meantime, you can use the Model Editor to manually localize these items. We apologize for the inconvenience.
…
nothing special - BC tickets as always is more then enough!

I just wanted to give you an update on this: we released v24.2.6 with many localization changes, and we are still publishing a breaking change (we will not list each and every localization string there but rather better explain what we are doing and why - as we discussed here).

As for the AboutInfo_DetailView / Caption item, it did not make it to the v24.2.6 release due to the label, sorry - we will add it to one of the hotfix builds. In the meantime, you can change About to Info manually in the Model Editor if you have not done so already.