Veriqa.Core.ChannelLocales
0.6.1
Prefix Reserved
dotnet add package Veriqa.Core.ChannelLocales --version 0.6.1
NuGet\Install-Package Veriqa.Core.ChannelLocales -Version 0.6.1
<PackageReference Include="Veriqa.Core.ChannelLocales" Version="0.6.1" />
<PackageVersion Include="Veriqa.Core.ChannelLocales" Version="0.6.1" />
<PackageReference Include="Veriqa.Core.ChannelLocales" />
paket add Veriqa.Core.ChannelLocales --version 0.6.1
#r "nuget: Veriqa.Core.ChannelLocales, 0.6.1"
#:package Veriqa.Core.ChannelLocales@0.6.1
#addin nuget:?package=Veriqa.Core.ChannelLocales&version=0.6.1
#tool nuget:?package=Veriqa.Core.ChannelLocales&version=0.6.1
Veriqa.Core.ChannelLocales
The locale catalogue of the Veriqa core contour, shipped as package content.
This package contains no assembly. It carries the translation files of the sign-in window and the
channel messages — en.json, ru.json, zh.json, pseudo.json — and a build targets file that
copies them into the consuming application's output directory under veriqa-channel-locales/.
Why a package
Veriqa localizes through Natural Keys: the key is the English text, so this catalogue is the
authoritative list of the strings a user sees while authenticating. An application that runs the
Veriqa issuer in-process resolves those strings against its own locale files, which means a
key missing there silently falls back to English for the end user. A gate exists for exactly that
(check6_web_superset_of_channel), and it needs both catalogues side by side.
Inside this repository the gate reads two directories of one working tree. A consumer that lives in a repository of its own has no such directory — it takes this package instead, pinned to a version, and compares its locales against the catalogue that version declares.
The copy lands in its own directory and never in the consumer's wwwroot/locales: the two
catalogues are compared, not merged.
Use
<PackageReference Include="Veriqa.Core.ChannelLocales" Version="0.1.0-dev.42" />
After a build the files are at veriqa-channel-locales/ beside the entry assembly. en.json is
the key list: every key of the catalogue is one of its property names.
Learn more about Target Frameworks and .NET Standard.
-
net10.0
- No dependencies.
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.