pt-BR vs pt-PT: why a bare pt tag is a mistake
Portuguese is written and spoken on both sides of the Atlantic, and the two main varieties — Brazilian Portuguese and European Portuguese — are close enough that a translator working in one can read the other without difficulty. That closeness is exactly what makes them dangerous to treat as one target: they diverge in spelling, vocabulary, and address forms in ways that read as clearly foreign to a native speaker of the other variety, even when every sentence is grammatically correct.
Tagging: pt-BR and pt-PT, not a bare pt
In BCP 47, pt is the base language tag for Portuguese, and the region subtags pt-BR (Brazil) and pt-PT (Portugal, and the convention generally used for European Portuguese more broadly) distinguish the two written standards. A file tagged only pt gives a translator, or a translation memory tool, no signal about which spelling and vocabulary norms to apply, and inconsistency creeps in silently — one string using Brazilian conventions and the next using European ones, both technically valid Portuguese, but jarring together in the same interface.
Orthography and vocabulary differences
The two varieties diverged enough in spelling that a 1990 Orthographic Agreement was signed to bring them closer together, though its adoption and enforcement have varied, and everyday spelling differences persist in practice: European Portuguese keeps some consonants that Brazilian Portuguese drops in words like receção (European) versus recepção (Brazilian, 'reception').
Vocabulary differences are frequent enough to matter in ordinary UI text. A train is trem in Brazil and comboio in Portugal; a bus is ônibus in Brazil and autocarro in Portugal; a mobile phone is celular in Brazil and telemóvel in Portugal. None of these words are wrong in the other variety's country — they are simply not the word a local reader expects.
Gender and number agreement work the same way, but vocabulary shifts what they attach to
Portuguese nouns carry grammatical gender and pluralize with agreement across articles and adjectives, the same underlying mechanism in both varieties — a system localizers of Romance languages will recognize from Spanish or French. The practical trap for Portuguese specifically is that the diverging vocabulary means the gender of the 'same' concept is not always obvious across contexts, and a template built around one variety's noun for an item will need re-checking, not just re-translating, if it is adapted for the other variety.
Address forms differ more than the grammar looks
European Portuguese distinguishes tu (informal singular 'you') from você, which functions as a more formal or distancing address and takes third-person verb conjugation. Brazilian Portuguese uses você far more broadly as the default second-person pronoun in everyday speech across most regions, with tu surviving regionally and often mixed with third-person verb forms rather than the second-person forms it takes in Portugal. This means a script that reads as neutrally polite in Brazil can read as needlessly formal or slightly old-fashioned in Portugal, and vice versa — another reason the address-form decision needs to be made per variant, not once for 'Portuguese'.
Deciding what to ship
Brazil is Portuguese-speaking largest by population, so teams that ship only one Portuguese variant most often choose pt-BR; but if your audience data shows meaningful interest from Portugal or other European Portuguese-speaking markets, the vocabulary and address-form gap is wide enough that a single variant will read as noticeably foreign to whichever audience it was not written for.
- Always tag files pt-BR or pt-PT explicitly, never a bare pt
- Maintain a vocabulary glossary per variant for words known to diverge (trem/comboio, ônibus/autocarro, celular/telemóvel)
- Fix tu or você as the default address form per variant before translation begins
- Treat pt-BR and pt-PT as separate localization efforts, not one translation with regional find-and-replace