Spotfire Ideas Portal
As a Canadian company, many of our reports have to built bilingual. To support this endeavor, we often need to build twice the report just to have actual text (such as titles) that needs to be localized.
We would like to have an easier way to support multi-language, such as something like a document property XML file that allows the a DXP file to reference different display text based on some parameter.
0
Future Consideration
Required for our company as well. Listing main requirements:
All charts on the dashboards should display date-time format properly according to the localization settings of the browser.
There should be a default system setting for the language
Spotfire frame and spotfire dashboards should display content according to the Browser preferred language settings
If translation is not available for any of the preferred languages then default should be used
Translation of the dashboard content should be done via a file/database table, where all labels/expressions are listed and can be translated easily
If an upgrade introduces new labels/expressions, the new labels should automatically be added to the other languages as well
Labels/expressions that are not translated to other languages should be displayed in the default language
Data translation is not in scope.
Thanks for the additional detail.
We have had attempts similar to the example report, and always ran into issue with statically named items.
Major:
1. Updating table visualization to hide/unhide columns appropriate to that language.
2. Hide/unhide different filters depending on user's language preference.
3. Name of an Action Control cannot be mapped to a document property.
Minor:
1. localize library folder/report names
2. localize table names
3. localize filtering scheme names
Looking at it now, this can work, but there are gaps that I would like to address:
1. This solution relies on writing to document properties. There is hypothetically a limit of how many document properties we can use (isn't there, I recall 256 items).
2. This would only apply on things like labels. We would likely need this on other elements (first one comes to mind is action buttons.
It is possible to build an analysis supporting multiple languages using specific data tables and document properties. See attached DXP file and let me know if this works for you.