Typography Rules · practical reference

Portuguese: Portugal and Brazil

Compare the model’s quotation and currency treatment before normalizing regional material.

Decide what the text is meant to follow

  • Is Portugal or Brazil the intended publication context?
  • Do quoted examples deliberately retain source typography?
  • Does the currency symbol identify the intended amount and currency?

Interpret the example in context

A Brazilian R$ amount and a Portugal-oriented euro example should not be normalized by guessing from language alone.

The current model provides distinct regional choices, including different currency context and quote forms. Follow the publication’s intended convention, check the original numeric value and retain legitimate source differences. This is targeted typography review rather than general Portuguese grammar checking.

Inspect the current plugin model

These fields describe the built-in plugin defaults. Read Language & rules for the policy actually used in your inspection; a custom team profile can differ. The defaults are not a universal style guide and do not promise equal rule coverage. Expand a specific locale to compare its expectations.

Portuguese (Portugal) pt-PT

Portuguese (Portugal)

pt-PT
Quote pairs
«…» “…”
Numbers
Decimal comma; dot grouping
Date order
Day–month–year
Currency
Suffix model · €, EUR
Short-word list
No short-word list in this model
Punctuation notes
Use the rule’s actual contextual evidence
Portuguese (Brazil) pt-BR

Portuguese (Brazil)

pt-BR
Quote pairs
“…” ‘…’
Numbers
Decimal comma; dot grouping
Date order
Day–month–year
Currency
Prefix model · R$, BRL
Short-word list
No short-word list in this model
Punctuation notes
Use the rule’s actual contextual evidence

Use the language evidence deliberately

  1. Check paragraph-language attributes, intended publication convention and actual active policy.
  2. Inspect representative text and read the resolved language and coverage in the panel.
  3. Review complete quotations, numeric source values and relevant line boundaries before any edit.
  4. Apply intended policy changes and inspect again. Retain intentional source differences and obtain competent language review where needed.

Continue with the current workflow

Compare two locale models → · Choose a language policy →