All the localization files used for Orchard Core Commerce (OCC). As a package, it's available from two sources:

• The NuGet packages match the OrchardCore.Commerce package of the same major and minor versions. These are manually published from the main branch.
• The Cloudsmith packages are automatically published whenever the repository is synchronized with Crowdin and has new data in the l10n_main. The versions are not aligned, you can use the latest Translations and OCC packages together.

The localizations are delivered as an Orchard Core module.

1. Include the project (either <ProjectReference> or <PacakgeReference> works) in your main web project.
2. Enable the "Orchard Core Commerce - Translations" feature.

1. When the main branch of the OrchardCore.Commerce repository is updated, .pot files are generated and uploaded to the main branch of this repository.
2. Crowdin's GitHub integration periodically scans this repo and updates the template strings in our project.
3. When new translations are added in Crowdin, its GitHub integration periodically pushes them to the l10n_main branch. (This is the customary branch name for such staging branches.)
4. It also creates a pull request form l10n_main to main.
5. When l10n_main is updated, a new OrchardCore.Commerce.Translations prerelease package is published to Cloudsmith.
6. When the pull request is reviewed, it is manually merged into main.
7. When a new OCC package is manually released to NuGet, a matching translations package should also be published there.