feat: Encode non-ASCII characters in pathnames returned from navigation APIs

[amannn]

With #959, the middleware already handled decoding of non-ASCII characters.

This allows you to define localized pathnames like so:

import {defineRouting} from 'next-intl/routing';
 
export const routing = defineRouting({
  locales: ['en', 'ja'],
  defaultLocale: 'en',
  pathnames: {
    '/about': {
      'de': '/über-uns'
  }
}

Since Next.js automatically encodes incoming pathnames, this supports incoming requests both for decoded pathnames (e.g. /de/über-uns), as well as encoded ones (e.g. /de/%C3%BCber-uns).

One piece has been missing though: Pathnames returned from navigation APIs should be turned into an encoded form.

Now, next-intl handles this as well:

import {Link, getPathname} from '@/i18n/navigation';

// href="/de/%C3%BCber-uns"
<Link href="/about" locale="de" />

// pathname = "/de/%C3%BCber-uns"
const pathname = getPathname({href: '/about', locale: 'de'});

This change brings the navigation APIs in line with Google's recommendation to encode non-ASCII pathnames.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
next-intl-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 11, 2025 11:55am
next-intl-example-app-router	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 11, 2025 11:55am
next-intl-example-app-router-without-i18n-routing	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 11, 2025 11:55am