Internationalization

Internationalization manifests hold localized messages for one language and optional namespace. Layouts and components refer to keys; the renderer selects messages based on ReportArtefact.language and namespaces.

Spec outline

apiVersion: bino.bi/v1alpha1
kind: Internationalization
metadata:
  name: systemTexts_de
spec:
  code: de-DE
  namespace: _system
  content: {} # object or JSON string

Fields:

• spec.code – locale code, for example de-DE or en-US.
• spec.namespace – optional namespace to group keys.
• spec.content – key/value map as object or JSON string.

YAML object content

---
apiVersion: bino.bi/v1alpha1
kind: Internationalization
metadata:
  name: systemTexts_de
spec:
  code: de-DE
  namespace: _system
  content:
    report.title.sales_overview: "Sales Overview"
    report.subtitle.q1_2024: "Q1 2024"
    card.title.revenue: "Revenue"
    card.title.ebit: "EBIT"

JSON string content

---
apiVersion: bino.bi/v1alpha1
kind: Internationalization
metadata:
  name: productTexts_en
spec:
  code: en-US
  namespace: products
  content: >-
    {"product.applications":"Applications","product.infrastructure":"Infrastructure"}

You can organize translations by language, business domain, or report, as long as namespaces and keys stay consistent with layout conventions.

Attribute Reference

Common Metadata

Attribute	Type	Required	Default	Description
apiVersion	string	yes	—	Must be bino.bi/v1alpha1.
kind	string	yes	—	Must be Internationalization.
metadata.name	string	yes	—	Unique identifier for this translation set.
metadata.labels	object	no	—	Key-value pairs for categorization and constraint matching.
metadata.annotations	object	no	—	Arbitrary key-value metadata, not used by the system.
metadata.description	string	no	—	Free-form description.
metadata.constraints	array	no	—	Conditional inclusion rules. See Constraints.

Spec Attributes

Attribute	Type	Required	Default	Description	Sample
spec.code	string	yes	—	Locale code (BCP 47 tag).	code: de-DE
spec.namespace	string	no	—	Optional lookup namespace for the translation block. Components reference translations by namespace.	namespace: _system
spec.content	object or string	yes	—	Key-value map of translations. Can be a YAML object or a JSON string.	see below

Content as YAML object

spec:
  content:
    report.title: "Sales Overview"
    card.title.revenue: "Revenue"
    card.title.ebit: "EBIT"

Content as JSON string

spec:
  content: >-
    {"report.title":"Sales Overview","card.title.revenue":"Revenue"}