The Viewmaker now supports translated view names, allowing view names generated by the system to be displayed in the active language across the user interface (UI), printed documents, and exports.
This enhancement improves consistency in multilingual environments and ensures that Viewmaker outputs align with the selected language of the project.
How translated view names work
Viewmaker‑generated view names are localized by using the standard translation system (PO files).
Instead of being fixed in English, view names are now translated dynamically based on the active language, while still preserving the technical identifiers required by the system.
Each view name is composed of two parts:
- A translatable base name, which is translated according to the active language
- A non‑translatable parameter, such as a numeric suffix, which is appended to the translated name
The final displayed view name combines both parts and appears consistently in:
- The Viewmaker user interface
- Printed views
- Exported documents
No additional action is required by end users once translations are in place.
Generating translations
Translated view names rely on standard translation files. To make new or updated view names available for translation, a translation generation action must be triggered. This action creates or updates the translation entries used by the system. For technical details about this process, see: Configuring translated view names in Viewmaker
Backward compatibility
This feature is fully backward compatible:
- Projects using older Viewmaker data continue to work unchanged
- If translated view name data is not available, Viewmaker automatically falls back to the previous behavior
- No migration is required
Version information
Translated view names are available in:
- Backend builds dated February 4th, 2026 or later
- Core 16.20 or higher