{"id":66832,"date":"2026-05-14T21:01:20","date_gmt":"2026-05-14T21:01:20","guid":{"rendered":"https:\/\/make.wordpress.org\/polyglots\/?p=66832"},"modified":"2026-05-15T19:58:06","modified_gmt":"2026-05-15T19:58:06","slug":"added-a-validation-top-bar-and-an-opt-out-in-the-translation-editor","status":"publish","type":"post","link":"https:\/\/make.wordpress.org\/polyglots\/2026\/05\/14\/added-a-validation-top-bar-and-an-opt-out-in-the-translation-editor\/","title":{"rendered":"Added a validation top bar (and an opt-out) in the translation editor"},"content":{"rendered":"

Validators in the translation editorTranslation Editor<\/span> Translation editors can approve translations for projects. The GTE (General Translation Editor) and LM (Locale Manager) roles can add new users with the \"Project Translation Editor\" role that can approve translations for specific projects. There are two different Translation Editor roles: \rGeneral Translation Editor<\/a> and Project Translation Editor<\/a><\/span><\/span><\/span> often jump to the Discussion<\/em> or Others<\/em> tab to check context before acting on a stringString<\/span> A string is a translatable part of the software. A translation consists of a multitude of localized strings.<\/span><\/span><\/span>. The problem: the Approve, Reject, and Fuzzy buttons only live in the MetaMeta<\/span> Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.<\/span><\/span><\/span> panel, so the moment you leave that tab, the action buttons disappear. You have to switch back just to act on what you came to act on.<\/p>\n\n\n\n

I have added a fixed top bar inside the translation editor that mirrors those buttons. It stays visible regardless of the tab you are on, so you can approve, reject, or mark a string as fuzzy without leaving Discussion<\/em> or Others<\/em>.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

How it works<\/h2>\n\n\n\n