European Portuguese português europeu pt-PT

Lokalized supports cardinality, cardinality range, and ordinality rules for European Portuguese.

Additional modeled concepts for European Portuguese: grammatical gender.

Cardinalities

  • CARDINALITY_ONE

    Matches i = 1 and v = 0

    Example Integers: 1

  • CARDINALITY_MANY

    Matches e = 0 and i != 0 and i % 1000000 = 0 and v = 0 or e != 0..5

    Example Integers: 1000000, …

  • CARDINALITY_OTHER

    Matches all other values

    Example Integers: 0, 2, 16, 100, 1000, 10000, 100000, …

    Example Decimals: 0.0, 1.5, 10.0, 100.0, 1000.0, 10000.0, 100000.0, 1000000.0, …

Cardinality example

This localized strings file selects the localized form of “day” for a delivery estimate. Raw numbers choose the CLDR category; values formatted with the JDK NumberFormat are interpolated for display.

Sample localized strings file
pt-PT.json Localized Strings File (European Portuguese)
{
  "Delivery.LeadTime": {
    "commentary": "Estimated delivery time, expressed in days.",
    "translation": "{{leadTime}}",
    "placeholders": {
      "leadTime": {
        "value": "dayCount",
        "translations": {
          "CARDINALITY_ONE": "{{formattedDayCount}} dia",
          "CARDINALITY_MANY": "{{formattedDayCount}} dias",
          "CARDINALITY_OTHER": "{{formattedDayCount}} dias"
        }
      }
    }
  }
}
Usage and expected results

The Java code passes each raw number for cardinality selection and formats its display value separately with NumberFormat.

Locale locale = Locale.forLanguageTag("pt-PT");

Strings strings = Strings.withFallbackLocale(locale)
  .localizedStringSupplier(() -> LocalizedStringLoader.loadFromFilesystem(Paths.get("strings")))
  .localeSupplier((matcher) -> matcher.bestMatchFor(locale))
  .build();

NumberFormat numberFormat = NumberFormat.getNumberInstance(locale);

// Raw numbers select language forms; NumberFormat produces the display values

// CARDINALITY_ONE
Number oneDayCount = 1;
String oneFormattedDayCount = numberFormat.format(oneDayCount);

// Expected: 1 dia
assertEquals(oneFormattedDayCount + " dia", strings.get(
  "Delivery.LeadTime", Map.of("dayCount", oneDayCount, "formattedDayCount", oneFormattedDayCount)
));

// CARDINALITY_MANY
Number manyDayCount = 1_000_000;
String manyFormattedDayCount = numberFormat.format(manyDayCount);

// Expected: 1<NBSP>000<NBSP>000 dias
assertEquals(manyFormattedDayCount + " dias", strings.get(
  "Delivery.LeadTime", Map.of("dayCount", manyDayCount, "formattedDayCount", manyFormattedDayCount)
));

// CARDINALITY_OTHER
Number otherDayCount = 0;
String otherFormattedDayCount = numberFormat.format(otherDayCount);

// Expected: 0 dias
assertEquals(otherFormattedDayCount + " dias", strings.get(
  "Delivery.LeadTime", Map.of("dayCount", otherDayCount, "formattedDayCount", otherFormattedDayCount)
));

Cardinality Ranges

These are CLDR's explicit range mappings. For any start/end pair not listed, Cardinality.forRange(...) falls back to the ending cardinality.

  • CARDINALITY_ONE - CARDINALITY_ONE

    Matches CARDINALITY_ONE

  • CARDINALITY_ONE - CARDINALITY_OTHER

    Matches CARDINALITY_OTHER

  • CARDINALITY_OTHER - CARDINALITY_OTHER

    Matches CARDINALITY_OTHER

Cardinality range example

The start and end cardinalities select the locale's CLDR range result. The selected form wraps a separately formatted display range.

Sample localized strings file
pt-PT.json Localized Strings File (European Portuguese)
{
  "Delivery.Window": {
    "commentary": "Estimated delivery window, expressed as a range of days.",
    "translation": "{{window}}",
    "placeholders": {
      "window": {
        "range": {
          "start": "minDays",
          "end": "maxDays"
        },
        "translations": {
          "CARDINALITY_ONE": "{{formattedDayRange}} dia",
          "CARDINALITY_MANY": "{{formattedDayRange}} dias",
          "CARDINALITY_OTHER": "{{formattedDayRange}} dias"
        }
      }
    }
  }
}
Usage and expected results

The Java code passes raw range endpoints for selection. Because NumberFormat formats one number at a time, it formats both endpoints separately and joins them for display; choose range punctuation appropriate to your application.

Locale locale = Locale.forLanguageTag("pt-PT");

Strings strings = Strings.withFallbackLocale(locale)
  .localizedStringSupplier(() -> LocalizedStringLoader.loadFromFilesystem(Paths.get("strings")))
  .localeSupplier((matcher) -> matcher.bestMatchFor(locale))
  .build();

NumberFormat numberFormat = NumberFormat.getNumberInstance(locale);

// Raw numbers select language forms; NumberFormat produces the display values

// CARDINALITY_OTHER range
Number minDays = 1;
String formattedMinDays = numberFormat.format(minDays);
Number maxDays = 2;
String formattedMaxDays = numberFormat.format(maxDays);
String formattedDayRange = formattedMinDays + "-" + formattedMaxDays;

assertEquals(Cardinality.OTHER, Cardinality.forRange(
  Cardinality.forNumber(minDays, locale),
  Cardinality.forNumber(maxDays, locale),
  locale
));

// Expected: 1-2 dias
assertEquals(formattedDayRange + " dias", strings.get(
  "Delivery.Window",
  Map.of("minDays", minDays, "maxDays", maxDays, "formattedDayRange", formattedDayRange)
));

Ordinalities

All ordinal numbers use ORDINALITY_OTHER; no value selects a different form.

Example: 2.º lugar.

Language-Specific Examples

These examples show how Lokalized models grammatical choices and translation behavior that commonly affect European Portuguese application copy. Each example identifies the Lokalized language forms and other library features it uses.

Customer status by gender

Portuguese articles and predicate adjectives can change together when a customer label refers to a man or a woman.

Language references: Infopédia: cliente is a two-gender noun, Ciberdúvidas: adjective agreement in Portuguese

Lokalized forms used: Gender

Sample localized strings file
pt-PT.json Localized Strings File (European Portuguese)
{
  "The customer is active.": {
    "translation": "{{customer}} está {{active}}.",
    "placeholders": {
      "customer": {
        "value": "gender",
        "translations": {
          "GENDER_MASCULINE": "O cliente",
          "GENDER_FEMININE": "A cliente"
        }
      },
      "active": {
        "value": "gender",
        "translations": {
          "GENDER_MASCULINE": "ativo",
          "GENDER_FEMININE": "ativa"
        }
      }
    }
  }
}
Usage and expected results
Locale locale = Locale.forLanguageTag("pt-PT");

Strings strings = Strings.withFallbackLocale(locale)
  .localizedStringSupplier(() -> LocalizedStringLoader.loadFromFilesystem(Paths.get("strings")))
  .localeSupplier((matcher) -> matcher.bestMatchFor(locale))
  .build();

assertEquals("O cliente está ativo.", strings.get(
  "The customer is active.", Map.of("gender", Gender.MASCULINE)
));

assertEquals("A cliente está ativa.", strings.get(
  "The customer is active.", Map.of("gender", Gender.FEMININE)
));

Addendum: Language Form Rules

The language form expressions above are specified by Unicode Technical Standard #35 and use the following notation:

  • n absolute value of the source number (integer and decimals)
  • i integer digits of n
  • v number of visible fraction digits in n, with trailing zeros
  • w number of visible fraction digits in n, without trailing zeros
  • f visible fractional digits in n, with trailing zeros
  • t visible fractional digits in n, without trailing zeros
  • c/e compact decimal exponent operands used by some CLDR compact-number rules