Localization
International-ready applications with optional localized routing, configurable languages and layered translations.
Core translation languages
APPNETOS Core applications are supplied with translations for 81 languages, backed by a global English fallback.
Prepared language entries
The MongoDB language template provides 438 language and locale entries that can be enabled or reduced to fit an application.
Independent components
Localized routing, language selection and translation loading can be configured independently.
Built for international applications
APPNETOS treats localization as a core capability, not an afterthought. Developers can deliver regional URLs, choose an active language from configured options and merge translations from multiple applications without building their own localization infrastructure. The supplied Core translations provide a head start; individual applications remain responsible for their own content and translations.
Three components, clear responsibilities
Simple by default, multilingual when needed
A language collection is optional. If no collection is mapped, Core\Languages creates the
virtual global language and uses it as the active and default language. Applications such
as APPNETOS Docs can keep their language-specific text directly in Twig templates without requiring
language documents. A mapped collection enables active-language selection for multilingual applications.
The diagram shows two configuration alternatives, not sequential runtime stages.
Localization does not force routing conventions
Localized URI documents are optional. URI resolution uses the active language managed by Core\Languages,
not the other way around. Applications may also omit URI document routing entirely and implement their
own routes.
Implementation notes
The 81 pretranslated languages and 438 prepared language/locale entries describe the supplied APPNETOS resources. Which languages are actually available at runtime depends on the active documents in the application's mapped language collection. Translation caching is optional and enabled by a concrete context implementation.