How to use this text tool
- Paste your source or load the sample.
- Set the available option for your target output.
- Run the tool and read any input warning.
- Review, copy, or download the result.
ICU Message Formatter handles the small but fussy part of working with icu message and variables. Paste a real example, adjust the option when one is available, and inspect the result beside the source. Processing stays in the browser, so it is useful for quick drafts, debugging, and one-off checks without setting up a package or command-line tool.
This tool parses the supplied icu message and variables and produces formatted message using rules suited to ICU Message Formatter. It reports useful counts so you can spot unexpectedly empty or broad results.
Always compare generated or extracted output with the original source before replacing production code or translations.
Load the sample and select Format ICU Message. The result demonstrates the exact output format, including any inferred types, matches, or validation notes.
All core parsing and transformation is performed with JavaScript in the current browser tab. No external API key or build step is required.
This lightweight tool focuses on common syntax. Project conventions, advanced schemas, locale rules, and compiler-specific checks may require a dedicated parser or build tool.
No. The conversion runs in your browser, although the page itself may load normal site resources.
Paste the source text shown by the input label and use the sample as a format guide.
Treat the result as a starting point. Check naming, types, escaping, and project-specific conventions before shipping it.
The input may be empty, malformed, or missing a required option. The error message identifies the first condition the tool could not process.
Yes. Use Download TXT for the main output. When structured rows or JSON are available, the matching export buttons appear after processing.
| Check | Why it matters |
|---|---|
| Syntax | Confirm the result parses in its target environment. |
| Semantics | Review inferred values and project conventions. |
| Privacy | Remove secrets before sharing exported output. |