Accent every letter, pad each string to translation length, and wrap it in markers. Then run the course. Text still in English was never sent for translation, text missing its closing marker was truncated by the layout, and text that overflows will overflow in German. None of it needs a translator.
Free · No account · Your files never upload
%Username% renders as literal text rather than a name, the substitution is failing and it will fail in every language.Placeholders, markup tags and HTML entities pass through untouched, which is the whole point: running the pseudo-localized build proves the substitution still works. Padding goes at the end of each string rather than through the words, so the original stays readable while the added length is obvious.
Turns your source text into something that looks translated without being translated. Every letter becomes an accented look-alike, each string is padded to the length a real translation would need, and the whole thing is wrapped in markers.
Because three separate faults become visible at once, and none of them need a translator or a budget. Text still in plain English was never sent for localization, which means it is hard-coded somewhere: in an image, a variable, a script, a player setting. Text missing its closing marker has been truncated by the layout, and it will truncate the real translation too. Text that overflows will overflow in German, which expands about as much as the padding.
Deliberately. If %Username% renders as a name in the pseudo-localized build, the substitution works. If it renders as literal text, it is broken, and it would have been broken in every language. Testing that before a translator is engaged is the cheapest bug you will ever find.
Before the file goes out, not after it comes back. Everything it finds is a defect in your build rather than in the translation, and every one of them is cheaper to fix while the course is still in your hands.