Template Helpers

Macros available on the Route facade (and one on the Route instance) for use in controllers, Blade templates, and middleware.

`Route::localizedUrl($locale, $absolute = true)`

The current request's URL in another locale, in canonical form (no prefix when the target is the hidden default). Use for <link rel="alternate" hreflang> tags, canonical URLs, and sitemaps:

blade

@foreach (config('localizer.supported_locales') as $locale)
    <link rel="alternate"
          hreflang="{{ $locale }}"
          href="{{ Route::localizedUrl($locale) }}" />
@endforeach

For an in-page language switcher, use Route::localizedSwitcherUrl($locale) instead - it always emits the prefixed form. See Language Switcher.

Current route	Behavior
Named (recommended)	Resolved through `route()`.
Unnamed `Route::localize()`	URI prefix swap on the request path.
Unnamed `Route::translate()`	Resolved through `route()`.
Outside a request	Throws `LogicException`.

The current request's query string is preserved on the localized URL, so pagination and filter URLs like /posts?page=2&sort=name keep the user on the same page after a locale switch. Route defaults set by Route::view(), Route::redirect(), or ->defaults() are stripped from the result - they belong to the route's controller, not the URL.

`Route::hasLocalized($name)`

True if the name was registered through Route::localize() or Route::translate():

blade

@if (Route::hasLocalized('about'))
    <a href="{{ route('about') }}">{{ __('About') }}</a>
@endif

Use this instead of Route::has('about'). The macros never register the bare base name - they register with_locale.about, without_locale.about, and (for Route::translate()) translated_{$locale}.about. Route::has('about') therefore returns false even though route('about') resolves correctly through the package's URL generator. Route::hasLocalized() checks all variants for you.

`Route::isLocalized()`

True if the current request matched a localizer-managed route. Useful for showing a switcher only on localized pages:

blade

@if (Route::isLocalized())
    @include('partials.language-switcher')
@endif

`$route->baseName()` and `Route::currentBaseName()`

Return the route's bare base name with the localizer prefix stripped. with_locale.about, without_locale.about, and translated_de.about all collapse to about. Foreign-named routes (e.g. admin.dashboard) and unnamed routes pass through unchanged.

Use this whenever you compare against a known name - middleware, authorization gates, analytics, breadcrumb lookups - so the comparison keeps working across all locale variants:

php

// In a custom middleware:
if ($request->route()->baseName() === 'about') {
    // ...
}

// Outside a Route instance, when you only care about the current request:
if (Route::currentBaseName() === 'about') {
    // ...
}

Route::currentBaseName() returns null when called outside a request (no current route), so it's safe to use without a guard.

The same logic is exposed as Localizer::baseName($name) if you need to strip an arbitrary route name (e.g. one read from logs or a queue payload).

`Localizer::currentLocaleDirection()` and `Localizer::localeDirection($locale)`

Writing direction ('rtl' or 'ltr') for the current app locale, or for any locale you pass in. Typical use is the dir attribute on <html>:

blade

<html lang="{{ app()->getLocale() }}" dir="{{ Localizer::currentLocaleDirection() }}">

localeDirection($locale) is the per-locale variant, useful when rendering a list of options in a language switcher:

blade

@foreach (config('localizer.supported_locales') as $locale)
    <a href="{{ Route::localizedSwitcherUrl($locale) }}"
       dir="{{ Localizer::localeDirection($locale) }}">
        {{ $locale }}
    </a>
@endforeach

How the direction is resolved

Three steps, first match wins:

Explicit override via localizer.locale_directions. Highest priority - useful when you want to pin an unusual locale or override the auto-detection:
php
```
// config/localizer.php
'locale_directions' => [
    'ku'  => 'rtl', // pin Kurdish to RTL even though some variants are LTR
],
```
Script subtag in the locale itself, matched against an ISO 15924 RTL script list. uz-Arab resolves to rtl, uz-Latn to ltr. Needs ext-intl (used by default in most Laravel setups).
Language default script. Languages without an explicit script subtag (ar, fa, he, ...) are looked up in a built-in map and matched against the RTL script list. Languages not in the map fall back to 'ltr'.

The built-in RTL languages cover ar, fa, ur, ps, sd, ks, ug, ku, he, yi, dv. The built-in RTL scripts cover Arab, Hebr, Thaa, Nkoo, Mand, Adlm, Rohg, Yezi.

If you need to extend either set, add config keys (your values are merged with the defaults; you don't need to repeat them):

php

// config/localizer.php
'language_scripts' => [
    'xx' => 'Arab', // your invented language code maps to Arabic script
],
'rtl_scripts' => [
    // extra ISO 15924 codes you want treated as RTL
],

For most apps just listing locales in supported_locales is enough - the defaults handle the common cases without further configuration.

Template Helpers ​

Route::localizedUrl($locale, $absolute = true) ​

Route::hasLocalized($name) ​

Route::isLocalized() ​

$route->baseName() and Route::currentBaseName() ​

Localizer::currentLocaleDirection() and Localizer::localeDirection($locale) ​

How the direction is resolved ​

Template Helpers

`Route::localizedUrl($locale, $absolute = true)`

`Route::hasLocalized($name)`

`Route::isLocalized()`

`$route->baseName()` and `Route::currentBaseName()`

`Localizer::currentLocaleDirection()` and `Localizer::localeDirection($locale)`

How the direction is resolved