Internationalization - Do you make sure your language follows the user's regional settings?

Developers too often change the 'Language' settings on reports in order to make it look ok for how they want to see it. Without realizing that they are now not supporting multiple cultures.

To do this, you need to set the 'Language' to "=User!Language". Then the report will recognize user client's culture settings, e.g. IE's languages settings.

Now you can specify this on either the culture sensitive controls or the whole report. Generally, is better specify this property on the whole report.

❌ Figure: Bad example - 'Language' setting is set to a specific culture

✅ Figure: Good example - 'Language' setting is set to '=User!Language' to detect user's culture automatically

✅ Figure: Good example - The data respects user's Language preference of IE in this case English (Australia)

✅ Figure: Good example - Likewise the data also respects user's Language preference of IE in this case Chinese (China)

Public Function Language()
    Try
        Return Report.User!Language
    Catch
        Return "en-AU"
    End Try
End Function

✅ Good example - Use above function to replace your reference to "Report.User!Language"/. It allows the subscription to work correctly