English/French ICU Message Regression Fixtures

For localization engineers maintaining English and French message catalogs, LocaleWitness generates repeatable input cases and coverage evidence before a release. It does not translate messages or judge translation quality.

What you receive

One ZIP with preserved source and target messages, parsed syntax, branch witnesses and expected rendered strings, a syntax-preserving pseudolocale, changes from an optional previous release, and a coverage report. Files: input.schema.json, bundle.json, witnesses.json, pseudolocale.json, release-delta.json, report.md and PROFILE.md. The completed-packet dataset row links to the ZIP and gives its SHA-256.

Inspect the report before using the fixtures. This is a bounded testing profile, not proof that a translated application is correct. Download the packet before your Apify storage retention expires.

Input example

Set the payload field to:

{
  "source_locale": "en",
  "target_locale": "fr",
  "source": {
    "greeting": "Hello {name}",
    "basket": "{count, plural, =0 {Empty} one {# item} other {# items}}"
  },
  "target": {
    "greeting": "Bonjour {name}",
    "basket": "{count, plural, =0 {Vide} one {# article} other {# articles}}"
  }
}

Supported scope

English and French only. Named arguments, select, plural, selectordinal, exact integer selectors, offsets, fallback branches and apostrophe quoting are supported. Numeric arguments are integers 0-999. Maximum 32 messages, 4096 UTF-8 bytes per message, 65536 message/key bytes, 8 argument names and 2048 total witnesses. max_combinations defaults 128 and is capped at 512 per message.

Dates, times, number formatters, skeletons, decimals, locale aliases, full ICU/CLDR conformance and translation quality are outside this profile. The JSON bundle is not a compiled JavaScript library.

Incomplete combination coverage returns UNKNOWN without a completed-packet dataset row. Invalid input returns an input diagnostic. Neither is a successful packet.

Data handling

This edition runs on Apify. Your supplied catalogs and generated files are processed and stored there under your account and Apify retention settings. Use synthetic or authorized data. Do not upload credentials or sensitive personal information. Artifact URLs may be shared: treat them as access-bearing links. This is not a local-only or permanent storage service.

Reuse

Use the JSON witnesses in your own test runner; compare the actual application output with the declared expected strings. Keep original message IDs and review every release delta. No external messages or application changes are performed.

Run and download

1. Review the supported input and try the included synthetic example. Replace payload with your authorized records. For API runs, send an object with a single payload field containing that input.
2. Run the Actor. Open Status and coverage to inspect the result.
3. For a completed result, open Download completed ZIP or the artifact link in the dataset. Save and extract the ZIP before Apify retention expires. Open the HTML report where provided; retain the JSON and CSV evidence.

Price and unsuccessful runs

$0.50 per completed packet, with one packet per run and no start fee. A retry of the same run reuses the packet and the same billing identity. Starting a separate run is a separate request. Invalid input or an incomplete UNKNOWN result produces a diagnostic without a completed-packet charge. A completed conflict or shortage report can still require manual review; PASS does not mean every business problem was resolved.

The minimum run budget is $0.50. The example is a normal run and follows the same price; it is not a free preview promise. Apify handles account billing. These files are not permanent storage: download them promptly.

Access and support

Your input and output are processed on Apify under the run owner's account. Use authorized data and opaque IDs; do not upload passwords or sensitive personal records. Treat artifact URLs as access-bearing links and share them only intentionally. The USTA report may fetch the Satoshi font; it does not upload your report. For a product issue, use this Actor's Issues tab with the run ID and a redacted example. Never post private input or access-bearing links in a public issue.