pt_PT_ao90 variant for pt_PT locale request

Due to the fact that we have two variants in Portuguese (Portugal, pt_PT), a new orthographic reform variant (AO90), which is not on yet, and the default pre-reform variant, and that we have offline tools to convert pre-AO90 to AO90, we initially thought of a way to still have only one publicly editable branch, the default variant, and the new one, that should only be edited by GTE/PTE, that would import the converted versions.

This would make possible to maintain only one branch, and manually update the AO90 variant.

AO90 is only mandatory for official institutions, and is not ratified by all other Portuguese speaking countries. Set aside the controversy ( or, the Portuguese WordPress Community publicly voted ( to maintain the pre-AO90 as the default language pack for WordPress pt_PT, so that no one is forced to use the AO90 version without opting-in. But as soon as variants became a part of core, we’ve been struggling with the need to have a way to serve both variants, without duplicating the translation flows. We’ve suggested other ways to include variants in the GlotPress workflow (, that would be useful for other locales also.

Having a read-only variant would make possible to use the available offline tools to do the automatic conversion. We’d maintain the default variant and import the converted language files to this second variant, that would be read-only or edited only by GTE/PTE.

In short…

As we talked with @ocean90 during WordCamp Europe, a “read-only” or GTE-only variant is not yet possible.

We shall, therefore, be doing this in phases.

First, we’re requesting a new variant for pt_PT, that could be pt_PT_ao90 or pt_PT_AO90 (I don’t actually know the rule for the suffix case), AO90 being the usually accepted acronym for Acordo Ortográfico da Língua Portuguesa de 1990.

We’ll also be suggesting portuguese language users who want to use the new AO90 variant to use a preferred languages plugin, like the one from @swissspidy (, that will allow them to have a fallback in case the new variant still has no translations for a theme or plugin they use, with the default pt_PT version being the first fallback, for example.

On a second phase, If and when we can have a read-only variant, it’ll be easy to manage. In the meantime, let’s try not to get too many contributions in this new variant, alerting users to the automatic conversion process we’re going to do offline.