Any Gramax catalog can become multilingual: choose a main language, add additional ones, and publish translations with the same section structure. Readers switch languages on the portal, while editors work with the original and translation in one process
Multilanguage without duplication
The value of multilanguage support isn't only translating articles. It helps serve different audiences on one portal, reduce drift between locales, and keep the knowledge base whole even when work happens in several languages
One portal for all audiences
Public and internal documentation become more accessible to teams and regions without separate catalogs
Less drift between languages
A shared catalog structure keeps materials in sync instead of scattering them across versions of the tree
Faster translation work
The editor sees the original next to the translation, so less time goes to finding context and matching phrasing
Better for global teams
Every audience gets materials in a familiar language, while the company keeps one connected knowledge base
Multilanguage features
Keep every locale in one article tree and let readers switch language right on the portal
Main and additional languages
Choose a base language for a catalog and add extra locales without a separate structure for each one
Shared structure and the original as context
Translations live in the same article tree, and when needed the editor sees the original material as a reference
Language switch right on the portal
Readers change locale on the same portal without moving between separate copies of the catalog's documentation