<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Label this issue](https://contributors.gitlab.com/manage-issue?action=label&projectId=278964&issueIid=19484) - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=19484) </details> <!--IssueSummary end--> When replacing hard coded English strings with [i18n helpers](https://docs.gitlab.com/ce/development/i18n_guide.html), there is currently no way to check that all texts were caught. Pseudo-localization helps verify that all strings have been externalized and can help verify that designs accommodate languages that have longer words and phrases than English. ### Proposal Add a dummy language for development which replaces all translatable texts with psuedo-localized strings. - accent each character (yields a visibly different but still legible string) - add tilde (~) to make all words 35% longer (simulates longer words in other languages to identify overflow problems) We will need to handle inline HTML, placeholders, and emoji so they are not mangled with accents. (e.g `em` should not be mangled in string like "this is <em>important</em>") ### Links Localizing Slack: https://slack.engineering/localizing-slack-680c4bc7f45a