orchardcore-data-localization

Orchard Core Data Localization

Guidelines

• Enable OrchardCore.DataLocalization (depends on OrchardCore.Localization) for database-backed translations of dynamic strings such as content type and field display names, admin menu text, and permission categories.
• Use PO files (OrchardCore.Localization, see orchardcore-localization) for static UI strings in views and code, including permission descriptions declared with LocalizationSource.Create(value, typeof(DeclaringType)).
• Use OrchardCore.ContentLocalization for translating content items.
• Implement ILocalizationDataProvider to expose custom translatable strings.
• Keys must be human-readable display values, because untranslated keys are displayed as-is.
• Use IDataLocalizer (aliased as D) in Razor and the d filter in Liquid.
• All recipe JSON must be wrapped in { "steps": [...] }.
• All C# classes must use the sealed modifier, except View Models.

Enabling Data Localization

{
  "steps": [
    {
      "name": "Feature",
      "enable": [
        "OrchardCore.DataLocalization"
      ]
    }
  ]
}

Admin UI

Settings → Localization → Dynamic Translations opens the translation editor: pick a culture, search, filter by category, and edit each string; auto-save (on by default) saves after 2 seconds of inactivity. The Statistics page shows overall, per-culture, and per-category progress (green ≥75%, yellow 25–74%, red <25%).

Permissions

OrchardCore.Localization.Data.DataLocalizationPermissions declares: