What LocaleReady refuses to translate

Translating text means changing it. Usually that’s exactly what you want — except when it isn’t. Hand “$13.50” to an automatic translator, and it might cheerfully turn it into “13,50 €.” That’s the right instinct for a sentence, and the wrong one for a price. Hand it a brand name, and it’ll translate that too, simply because nothing told it not to.

LocaleReady quietly protects three kinds of text before any of it reaches a translation service.

Money

Prices and amounts are spotted by their shape — a currency symbol or a code sitting next to a number — and set aside before the sentence is translated. The rest of the sentence translates normally, and the price gets put back exactly as it was written. This just happens, every time, with nothing to turn on.

Brand and product names

Some words should never change, no matter how confident a translator feels about it: “Acme Cloud” shouldn’t become “Nube Acme” in any language. Add the names you care about once, under Translation settings, and every translation respects them from then on.

The little placeholders a script fills in later

The trickiest case is the one that looks completely harmless. A shopping cart might show “### in cart” on the page, then quietly swap that “###” for a real number once it loads. Ask a translator to translate that sentence, and it has no way of knowing “###” isn’t just odd punctuation — it might move it, drop it, or change it just enough to break the number that was supposed to show up there.

LocaleReady sets placeholders like this aside before translating, and puts them back afterward, so they always come through in one piece.

The idea behind all three

Different problem each time, same trick: notice what shouldn’t change, set it aside, translate everything else, then put it back where it belongs. It’s the same approach you can use yourself for your own brand names.