Expand description
Deterministic catalog generation and opt-in source diagnostics for ProTranslate.
A build script explicitly names its catalog files. Generated providers use static tables and typed accessors; no runtime resource discovery is required.
Structs§
- Build
Diagnostic - A deterministic, source-associated catalog or usage diagnostic.
- Builder
- Cargo build-script entry point. Files are explicit and tracked with
rerun-if-changed. Only changed output bytes are written. - Catalog
Compiler - Framework-independent compiler usable in build scripts, editors and CI tools.
- Catalog
File Options - Explicit format and culture overrides for one build-script catalog file.
- Catalog
Input - One explicitly supplied catalog.
nameis a stable source label, not a discovery path. - Compilation
- The generated Rust and manifest can be inspected without writing any files.
- KeyUsage
- A static or dynamic translation use.
argument_count = Nonemeans lookup, or an argument slice whose length the caller cannot prove at build time. - Source
Analysis - Source
Analysis Options - Rust syntax analysis is opt-in and scoped to explicit receiver expressions. This avoids claiming semantic type analysis that a build script cannot perform.
Enums§
- Build
Error - Build-script failure, including all source diagnostics when generation was rejected.
- Diagnostic
Severity - Build diagnostics preserve the upstream PTA/PTSG identifiers where applicable.
Functions§
- analyze_
rust_ source - Inspect literal keys, file-local string constants, generated key constants, and
statically sized argument arrays for selected translation service receivers.
Macros are opaque except for a
vec![...]used as the format argument list.