Modeling multiple many-to-many relationships based around a language component

Creating copies/views of the model on a per-language basis is in my back pocket in the event that there's absolutely no other solution to this issue. That was actually the very first idea that I pitched to my client, but they are adamant about having a single report from a standpoint of simplifying both development and maintenance.

We are migrating their current reporting from Qlik, and Qlik handles this issue seamlessly via the ability to add conditional statements to practically any object in a report, so it would be a difficult conversation to tell them that this functionality they've utilized for years in their old solution is not available in the new solution that they're investing a lot of time and money into.