Locales and RTL

Formatting accepts bounded language/script/region/variant locale IDs with RFC5646 extension groups and private-use tails attached to a language. Both separators are accepted; browser tags use hyphens and PHP IDs use underscores:

Watch this in the workshop: 52:13 — resolve labels and RTL direction for one note instance.

use Bjanczak\FilamentFlexFields\Support\Locale\LocaleContext;

$locale = new LocaleContext(
    locale: 'en-US-u-ca-buddhist-nu-thai',
    translationLocales: ['en', 'en_US', 'pl'],
    fallback: 'en',
);

$locale->formatting->tag; // en-US-u-ca-buddhist-nu-thai
$locale->translationChain; // ['en_US', 'en']

A missing exact translation drops the complete extension block before trying region/script/variant parents. No dangling en_US_u or partial extension becomes a translation candidate. Explicit scripts determine direction (ar-Latn is LTR). FamilyRenderContext uses the same locale admission as ordinary formatting. Duplicate extension singletons, empty extension values, malformed variants and oversized IDs reject. The syntax contract does not bundle the IANA/Unicode registries or claim every calendar/numbering option exists in the installed ICU or browser. Grandfathered tags, extlang forms and private-use-only locale IDs remain unsupported. See RFC5646.

Continue reading

Extension guides · Definition and registration reference

Last modified on October 17, 2026

Getting started

Components and families

Composition

Configuration and values

JavaScript and interactions

Assets and delivery

Appearance and discovery

Publishing and support

Continue reading

​Continue reading

Continue reading