Each string you submit will be validated (usually within a few days), and then you’ll appear as a Translation Contributor on the en_GB Team page<\/a>.<\/p>\n\n\n\n WordPress Core, plugins, themes, mobile apps, and other strings can be translated from American English ( Beyond the usual converting s’s into c’s (eg the noun \u2018license\u2019 becomes \u2018licence\u2019), z’s into s’s (eg \u2018customize\u2019 becomes \u2018customise\u2019), and adding u’s (eg \u2018color\u2019 becomes \u2018colour\u2019), here is a list of other things we take into consideration when translating into Our glossary<\/a> covers a fair number of the changes British English makes to American English.<\/p>\n\n\n\n A lot of the strings will be exactly the same. Others will only change on spelling or the occasional different word. Capitalisation and word form (ie ending in \u2013ed<\/em> or \u2013s<\/em>) should be maintained or adapted as necessary.<\/p>\n\n\n\n You can find a detailed list of agreed changes for all English variations on this spreadsheet: Note that some strings have been validated before these variations were decided, so if you see a different version, please reject it and submit a new string. If we ever get global searching across all projects, we’ll handle it then.<\/p>\n\n\n\n Other changes would be where demo content uses dollars and an American city that could be changed to pounds and London respectively. At the moment, other than what might appear each day, there are no fuzzy strings or strings that are waiting – we keep on top of those a few times a week. Otherwise, we submit and validate strings on popular projects (to bring the benefit to a wider range of people) and projects that maybe nobody but the author has used (to clear off the hundreds of those tiny plugins).<\/p>\n\n\n\n Our challenge is to get the most popular themes<\/a> and plugins<\/a> translated. The data from these pages is updated in real time. <\/p>\n\n\n\n When submitting strings, start on the Development\/Stable (code) strings first, and leave the Readme projects until afterwards. When a string set reaches 90%, it has the possibility of being delivered to end-users via language packs, unless there is an existing language pack, in which case there is no threshold. Having the code found in everyone’s WordPress installs showing up as the right language is more beneficial than having the plugin screen contents being translated.<\/p>\n\n\n\n For the Readme, there’s no limit – once a string is translated, it is used (after a few minutes), even if all the other strings remain untranslated. The benefit of getting Readme strings to 100%, means that it’s easier to see when any new strings are added to a project, as the overall translation percentage will drop from 100%.<\/p>\n\n\n\n If you’re interested in contributing, just follow the steps above and start contributing today!<\/p>\n\n\n\n Also, if you want to discuss anything regarding translating into British English, please join our UK Slack<\/a>, and the “#en-gb” channel.en_US<\/code>) to British English (en_GB<\/code>) using a system called GlotPress.<\/p>\n\n\n\nStyle Guide<\/h3>\n\n\n\n
en_GB<\/code>:<\/p>\n\n\n\n\n
Glossary<\/h3>\n\n\n\n
\nWordPress.org Shared English Variants Translation Glossary<\/a>.<\/p>\n\n\n\n
<\/p>\n\n\n\nOrder of Translations<\/h3>\n\n\n\n
<\/p>\n\n\n\nUsing GlotPress<\/h2>\n\n\n\n
![\"Screenshot](\"https:\/\/en-gb.wordpress.org\/files\/2015\/11\/Screenshot-2015-11-20-23.56.02.png\")