Download the PHP package lhcze/bcp47-tag without Composer
On this page you can find all versions of the php package lhcze/bcp47-tag. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package bcp47-tag
🌐 BCP47Tag
🪐 Don’t panic. Your tag is valid.
Validate, Normalize & Canonicalize BCP 47 Language Tags (en, en-US, zh-Hant-CN, etc.)
BCP47Tag is a robust PHP library for working with BCP 47 language tags:
- ✔️ Validates against the real IANA Language Subtag Registry
- ✔️ ABNF-compliant (RFC 5646)
- ✔️ Supports language, script, region, variant, grandfathered tags
- ✔️ Auto-normalizes casing & separators (
en_us→en-US) - ✔️ Automatically expands collapsed ranges from the registry
- ✔️ Resolves partial language tags (e.g.,
en→en-US) using custom canonical matching, with scoring - ✔️ Error handling via clear exception types
- ✔️ Lightweight
LanguageTagVO for validated tags - ✔️ Works perfectly with
ext-intl—no surprises upon feeding ICU - ✔️ Easy fallback mechanism
- ️🫧 Supports grandfathered tags so old, they still remember when Unicode 2.0 was hot
- 🖖 Accepts
i-klingonandi-enochianfor your occult projects -
🤓
ABNFso clean, linguists shed a single tear❓ Why not just use
ext-intl?Good question — and the answer is: you should keep using it!
ext-intl(ICU) is brilliant at formatting if your tag is clean.
However, it does not:
- ✅ Validate that your tag fully follows the BCP 47 ABNF rules.
- ✅ Reject or warn about grandfathered or deprecated subtags.
- ✅ Match your tags against the authoritative IANA Language Subtag Registry.
- ✅ Resolve partial input (
en→en-US) to a known canonical list. - ✅ Enforce known tags only with
knownTags+requireCanonical.
If you’re in Symfony, you might also use
#[Assert\Locale]for basic input validation.
And that’s fine for checking user input — but it stops at structure. It won’t canonicalize, resolve, or check IANA.
👉 So the best practice:
- ✅ Use BCP47Tag to validate & normalize.
- ✅ Hand the cleaned tag to
ext-intlor whatever else you have for formatting & display. - ✅ Trust you’ll never feed ICU any garbage.
- ✅ Carry around immutable LanguageTag value object across your code base instead of string
BCP47Tag: RFC 5646 + IANA + real normalization + fallback + resolution.
No hustle with regex, str_replace() or guesswork.
⚡️ Installation
🚀 Basic Usage
🔍 Features & Flow
-
Normalize + parse
Clean casing/formatting and parse into components. -
Validate against IANA
Broken input or fallback triggers explicit exceptions:BCP47InvalidLocaleExceptionBCP47InvalidFallbackLocaleException
-
Canonical matching (optional)
- Pass an array of
useCanonicalMatchTags - Each is matched and scored:
+100 language match, +10 region, +1 script - Highest score wins.
- Same score makes the first one to have it to make a home run
- Pass an array of
- LanguageTag VO
Immutable, validated,Stringable&JsonSerializable.
📜 Supported Tags
BCP47Tag uses a precompiled static PHP snapshot of the latest IANA Language Subtag Registry to validate languages, scripts, regions, variants, and grandfathered tags. The registry is loaded once per process, kept hot in OPcache for maximum speed.
- ✅ ISO language, script, region, variants
- ✅ Grandfathered/deprecated tags (e.g.,
i-klingon) - ✅ Collapsed registry ranges are auto-expanded
- ⚠️ Extensions & private-use subtags (future)
🧩 Key API
| Method | Description |
|---|---|
__construct(string $input, ?string $fallback, ?array $useCanonicalMatchTags) |
Main entry |
getInputLocale() |
Original input string |
getNormalized() |
RFC‑5646 formatted tag |
getICUformat() |
Underscore variant (xx_XX) |
getLanguageTag() |
Returns LanguageTag VO |
__toString() / jsonSerialize() |
Returns normalized string |
📜 The Official BCP 47 ABNF
The syntax tags must follow is defined by RFC 5646 in ABNF:
Examples:
- ✅
en→ valid - ✅
en-US→ valid - ✅
zh-Hant-CN→ valid - ✅
i-klingon→ valid (grandfathered) - ✅
en-US-x-private→ valid (extension/private use) - ❌
en-US--US→ invalid
BCP47Tag respects this ABNF, so your tags match the real spec — no hidden assumptions.
❓ Why is this useful?
Use cases include:
- Validating API
Accept-Languageheaders - Multi-regional CMS deployments
- Internationalization pipelines
- Locale-dependent services where mis-typed tags lead to silent failures
⚙️ Requirements
- PHP 8.3+
ext-intl
🧪 Tests
📌 Roadmap
- ✅ IANA Language Subtag Registry integration
- ✅ Language, script, region, variant validation
- ✅ Lazy singleton registry loader
- ✅ Static PHP snapshot of the IANA registry for ultra-fast lookups
- ✅ Canonical matching with scoring
- ✅ Typed exceptions for flow control
- ⚙️ Extension/subtag support (planned)
- ⚙️ Additional data use from IANA registry (suppress-script subtag, preferred, prefix)
- ⚙️ Auto-registry refresh script
📖 License
MIT
🔗 References
🧬 Now go and boldly canonicalize strange new tags the BCP 47 way! 🌍✨
All versions of bcp47-tag with dependencies
ext-intl Version *
ext-curl Version *