Pseudolocalization Catalog Builder

How to use Pseudolocalization Catalog Builder

Create a separate pseudo-language catalog for checking whether your interface exposes translated resources and leaves room for longer text. A fixed accent map and visible wrappers make the transformation repeatable. The report preserves every original message, protected token span and padding count, while the downloaded JSON contains only the transformed catalog ready for your own application-specific review.

1. Enter a flat JSON object with one to two hundred original string values.
2. Choose variable-only protection for the declared {{ASCII.own.path}} grammar or literal text, and an explicit padding percentage.
3. Download the separate pseudo catalog, compare source/token evidence and test it in your actual interface.

Good to know

• At most 100,000 JSON characters, 200 messages, 100 characters per nonblank key and 2,000 characters per value. Unsupported nested/non-string values, duplicate JSON members, malformed Unicode and document controls other than tab/CR/LF are refused. Empty source values remain empty.
• The deterministic map changes ASCII vowels plus c, n and y in both cases to a fixed accented counterpart. Other characters, including emoji and existing combining sequences, remain unchanged. This is deliberately artificial test text, not a translation or a named real language.
• Variable-only mode protects the exact source spelling of at most 100 {{ASCII.own.path}} tokens per message, including optional ASCII spaces/tabs inside braces. Bare braces, unsupported token names, unclosed tokens, sections and expressions are refused. Paths are never looked up or executed. Literal mode protects no syntax.
• Padding adds exactly ceil(original literal Unicode scalar count × selected percentage / 100) tildes, excluding protected token spelling. A separator space and fixed [!! / !!] wrappers are additional. Scalars are not grapheme clusters or rendered width; the tool does not predict actual font metrics or a translation’s final length.
• No ICU, printf, HTML, JSX, framework escaping, Windows/ICU pseudo-locale conformance, RTL-layout simulation or application compatibility is claimed. Literal mode can alter format syntax; choose it only for actual literal strings. No user markup is mounted, request sent, history saved or original file edited.
• Processing is local. Output is limited to 1,000,000 text characters unless a stricter file limit is stated.