Automatic Variants for GlotPress

= What does this plugin really do? It extends the translation platform GlotPress used to translate WordPress projects. Since GlotPress 3.x there is a new Variants feature, enabling some Locales to be a variant of a root Locale. With this, comes fallback. If a translation doesn't exist on the variant, it assumes its root translation. This plugin links both Locales in a way that you only need to focus in translating and manage consistency on the root, knowing that the variant is being automatically converted and synced with no human action needed. With this tool, the translators can continue to provide both Locales with the minimum effort. = Does translate.wp.org supports automatically converted variants? No(t yet). This is a working proof of concept, it works on any GlotPress 3.x, but isn't running on translate.wp.org (GlotPress based) at the moment. = Should this feature be a part of GlotPress itself? To be discussed. The relationship between root/variant depend on each team that uses GlotPress. Depending on how the translation team decides to work. It's useful if automatic conversion is wanted. For teams that want a root/variant to work automatically, GlotPress could integrate this optional feature of setting a specific variant to be automatically converted from its root with a custom hookable process, and turning the variant read-only. This can be used by any Locale team that want to hook an automatic conversion between root and variant Locales. This plugin is intended to be a proof of concept to use and test this workflow. = What versions of GlotPress are compatible with this plugin? The Variants feature was introduced in GlotPress 3.0.0-alpha. Later, on GlotPress 3.0.0-beta the Variants feature was removed temporarily, so for now the GlotPress alpha version is the only Variants compatible version, and you must install it for this plugin to do its magic. Sure! You are welcome to report any issues or add feature suggestions on the GitHub repository.