Hacker News Reader

Years ago when I worked at Microsoft, they had a "pseudo localization" tool, at least for Visual Studio, that would inject backwards text, longer text, etc... It was gibberish, but it gave QA instant feedback on whether the UI would accommodate the localization process.

I did a quick web search, and it appears to be a well-understood practice, even covered in a different Shopify blog:

https://www.shopify.com/partners/blog/pseudo-localization.

View on HN

I like to have a "double length" localization mode that doubles the English text; useful for fixing some layout issues while waiting for translations.

A separate toggle to underline everything going through the localization system (or adding some __delimiters__ around it if you don't support rich text) is great for spotting text that is not running through localization yet.

Once you have translations back, a "longest length" translation mode is more useful. It picks the longest translation for each token, no matter what the language. Confusing to look at, but great for seeing only the places where you actually have text-fit issues.

Another tip I've found in pseudo-localization is to add in lots of emoji to the text. That can help check some Unicode assumptions/encoding issues in your localization pipelines in ways English readers can better visualize.

Reply on news.ycombinator.com