tamper[box]

Pseudo-Localizer

Expose clipping with expanded test strings

Will translated text fit? Accent and expand resource strings while preserving keys and recognized placeholders.

Will translated text fit? Accent and expand resource strings while preserving keys and recognized placeholders. Check locally in your browser. No upload. Jump to: What does it mean?, How to fix it, Break it, Ask your agent.

Example Synthetic checkout strings combine readable text, a named placeholder and an ICU plural expression.

3 strings pseudo-localized.

Pseudo-localization is a layout aid, not a translation. Entire ICU blocks stay unchanged. Inline XML markup is refused to prevent tag loss.

The resource file stays in your browser. Strings are accented and padded here and never uploaded.

Nothing is sent to our server. This tool has no server step.

Findings

2 checks and notes
  • Info Verify in the running application

    Accent substitution and padding expose some layout issues. This does not simulate translation quality, bidirectional layout or every script.

  • Pass 3 strings pseudo-localized

    Resource keys and ARB metadata are preserved. Placeholder blocks, including complete ICU expressions, are left unchanged.

Evidence

Strings transformed3
Padding percent30
Input characters116
Output characters147

Pseudo-localized resource

Show the pseudo-localized resource 5 lines · 147 characters
{
  "welcome": "[Ħëľľö {name} ~~~~]",
  "cart": "[{count, plural, one {One item} other {# items}} ~~~~~~~~~~~~~~~]",
  "button": "[Çöñŧïñüë ~~~]"
}

What this result means

Written for the example.

  • Ask for a review of the findings and a test that verifies the proposed fix. Input values are not included automatically.

  • Synthetic checkout strings combine readable text, a named placeholder and an ICU plural expression.

  • Synthetic checkout strings combine readable text, a named placeholder and an ICU plural expression.

  • Check representative input and one deliberate failure. Confirm the result in the application that consumes it.

  • Read the findings before changing the input. Break it lets you inspect a failure, and Heal it restores the previous input.

  • Pseudo-localization is a layout aid, not a translation. Entire ICU blocks stay unchanged. Inline XML markup is refused to prevent tag loss.

How it works

Pseudo-Localizer reads resource file locally and presents findings with the evidence behind them. Synthetic checkout strings combine readable text, a named placeholder and an ICU plural expression. The full method, every rule and worked examples are on docs.tamperbox.dev.

Limits and interpretation

Pseudo-localization is a layout aid, not a translation. Entire ICU blocks stay unchanged. Inline XML markup is refused to prevent tag loss. Inputs are limited to 1,000,000 characters per field. Nothing is fetched from addresses embedded in input. Explicit copies and downloads are under your control.

Frequently asked questions

Is my input uploaded?

No. Parsing and output generation run in your browser. Source values are not sent to a server.

What does the opening example demonstrate?

Synthetic checkout strings combine readable text, a named placeholder and an ICU plural expression. It is synthetic data. Replace it with your own input to inspect a different case.

Does a passing result prove my application works?

No. Pseudo-localization is a layout aid, not a translation. Entire ICU blocks stay unchanged. Inline XML markup is refused to prevent tag loss. Verify the result in your test environment before relying on it.

References

Are you an AI agent? You are in the right place.

Read this tool as plain text with its methods and limits. Use the website interface; no dedicated MCP operation is available.