The WordPress Gutenberg project’s plan for internationalization (i18n) and localization (l10n) of Full Site Editing themes (FSE) has not yet been formulated. I’ve written a proposal, entitled Internationalization and localization: translating templates and template parts, raised as Feature request #27402.
I believe that very little needs to be done to Internationalize a file containing Gutenberg blocks and HTML, and that it can be translated and localized into a statically delivered file in the user’s required locale ( language and country ) using the process described in the feature request.
This post briefly discusses some of the challenges of translating rich text content.
Last updated:December 6, 2020
A few months ago, having resolved to internationalize, localize and test my WordPress plugins, I started busily beavering away at a solution that will enable me to automatically deliver UK English versions of my plugins. Now that Global WordPress Translation Day #3 is fast approaching it seems timely to write up an outline of my approach. The solution involves a number of fairly well defined processes, and a lot of repetition.
Last updated:November 7, 2017
After a discussion with Paul Gibbs at #wcukretreat about Internationalization (i18n) and Localization (l10n) of my WordPress plugins – he was reviewing my code for the oik-css plugin – I decided to bite the bullet and see what I needed to do for the oik suite of plugins. Here are the results of the first part of my investigation.
Last updated:August 18, 2014