Orchard Core translations provide two kinds of NuGet packages:
- Culture Specific Packages: A NuGet package that targets a single culture, named
OrchardCore.Translations.{culture}.nupkgwhere{culture}is the culture it contains. - Translations Meta Package: A NuGet package named
OrchardCore.Translations.All.nupkgwhich references the cultures selected for inclusion in the meta package.
Crowdin Translations:
Localization/*.pot contains the English source catalogs copied from Orchard
Core by the Sync POT files workflow.
Translated catalogs live in Localization/<culture>/*.po. Crowdin
synchronizes the source catalogs and proposes translation updates through GitHub
pull requests, using the integration configuration in crowdin.yml.
Repository-side translation edits must also be imported into Crowdin; ensure the
integration is configured to import new translations, or upload them explicitly.
Exporting translations from Crowdin is not a substitute for importing those edits.
cultures.json controls packaging, not Crowdin's language mapping.
pack.ps1 reads each culture's settings:
| Setting | Purpose |
|---|---|
name |
Culture suffix of the NuGet package and culture folder inside that package. |
folder |
Source folder under Localization from which to copy the PO files. |
display-name |
Human-readable language name used in package metadata. |
generate-package |
Whether to build the culture-specific package. |
meta-package |
Whether to include that package as a dependency of OrchardCore.Translations.All. |
All three packaging workflows call pack.ps1: pull requests build packages,
pushes to main or dev publish 4.0.0-preview-* packages to Cloudsmith, and version tags
or a manual release run publish stable packages to NuGet.org. Packaging copies
the selected catalogs; it does not translate them or reconcile duplicate folders.
Maintain only two Chinese source folders, matching Crowdin's current output:
Localization/zh-Hans for Simplified Chinese and Localization/zh-Hant for
Traditional Chinese. The culture mappings generate four packages:
| Package suffix | Source folder | Folder inside the package |
|---|---|---|
zh-Hans |
Localization/zh-Hans |
content/Localization/zh-Hans |
zh-CN |
Localization/zh-Hans |
content/Localization/zh-CN |
zh-Hant |
Localization/zh-Hant |
content/Localization/zh-Hant |
zh-TW |
Localization/zh-Hant |
content/Localization/zh-TW |
The regional packages intentionally reuse the corresponding script-level
translations. Separate Localization/zh-CN and Localization/zh-TW source folders
are unnecessary and are not read by packaging. Update zh-Hans or zh-Hant
directly, including when generating AI-assisted translations; do not recreate
the historical regional folders.
The repository includes the
orchardcore-translations skill
for generating translation batches and safely importing their JSON responses.
It fills only missing translation values, preserves populated translations, and
removes obsolete entries from the selected culture without changing POT files or
other cultures. Review AI-generated translations before merging them.
Generated prompts include POT translator notes, format argument names, and
inclusive plural count ranges. Each PO file keeps its own valid Plural-Forms
rule, rather than being automatically migrated to Orchard Core's CLDR 49
fallback. Existing headerless plural catalogs require a separate review and
migration before generating or importing translations; --plural-forms supplies
rules only for new catalogs. Merge relevant Sync POT files updates before
relying on new source metadata.
In the Copilot app, select the Orchard Core translator custom agent, or ask:
Use the orchardcore-translations skill to complete French translations in Localization/fr, with 200 translation values per batch. Locate the Orchard Core source checkout before generating prompts.
In IDEs that support Copilot prompt files, use /translate-culture. The skill
is also discoverable automatically by compatible Copilot clients. Prompt files
are IDE entry points, not Copilot app suggested-prompt configuration.
The full translation workflow requires the Copilot app's coordinated chat-session
tools so each batch inherits the caller's model and effort settings. Other
clients can generate prompts and import completed JSON responses using the
bundled scripts, but should not silently substitute another dispatcher. To
generate prompts without changing catalogs, explicitly request "generate prompts
only." All generation requires a separate, readable
OrchardCMS/OrchardCore source checkout for translation context, Python 3.10 or
later, and the dependency in
requirements.txt.
The agent asks for missing inputs, including the batch size, before generating.
Keep generated artifacts outside this repository.
Run the skill's regression tests from the repository root:
python3 -m pip install -r .github/skills/orchardcore-translations/scripts/requirements.txt
python3 -m unittest discover -s .github/skills/orchardcore-translations/scripts -p 'test_*.py'The Sync POT files GitHub Actions workflow runs every Monday at 03:00 UTC and
can also be started manually using Run workflow in the Actions tab. It clones
the main branch of OrchardCMS/OrchardCore, replaces Localization/*.pot with
the upstream templates (including removing obsolete templates), and creates or
updates a pull request if Git detects changes. Translated .po files are not changed.
The repository's Settings > Actions > General > Workflow permissions must
allow GitHub Actions to create pull requests. The workflow uses GITHUB_TOKEN
with write permissions for repository contents and pull requests.
The following steps are needed to release new Orchard Core Translations NuGet packages:
- In GitHub's Actions tab, select Sync POT files and click Run workflow
on
main, or use the latest scheduled run. - Review and merge the resulting Update POT files from Orchard Core pull request, if there are changes. This copies the upstream POT files directly; no local source checkout or extraction tool is needed.
- Go to https://crowdin.com/project/orchard-core.
- Go to Integrations > GitHub and click Sync Now to synchronize the updated source catalogs, then complete any missing translations in Crowdin.
- Sync again to export translations and find the New Crowdin updates pull request at https://github.com/OrchardCMS/OrchardCore.Translations/pulls.
- Review and merge it.
- Push a new version tag to this repository, such as
v3.0.0, to publish stable packages, or run Publish Stable Packages manually with the desired version.