Jan Amann

Can you share more details about your use case why you'd want to keep cookie-based detection but not `accept-language`? How does the current behavior of the middleware get in the...

Thanks for the details! > Given that there is no locale prefix in the URL, no locale cookie, the first time should be redirected to https://abc.multi-tenant.com/en-GB because we want all...

Thanks for chiming in here @pomber! For my better understanding, can you provide some background on why you'd want to ignore the `accept-language` header? What is the motivation that aims...

Here's an update: https://github.com/lokalise/i18n-ally/issues/1009#issuecomment-2545525703

I've added a PR with a failing test to hopefully verify the fix in #3769. See https://github.com/urql-graphql/urql/pull/3769#issuecomment-3228118780

Hmm, I generally agree that it would be good to ignore whitespace, but the other side is that if other tools (like `semantic-release`) don't apply the same trimming, then you'll...

Hey, thanks for chiming in here @hugotiger! Right, I didn't notice that there's even docs on this behavior. I did add a workaround in https://github.com/amannn/next-intl/pull/1578. I guess you still have...

I think the easiest might be to create an isolated reproduction with https://github.com/amannn/next-intl-bug-repro-app-router. If we can reproduce it there, we can set up a unit test similar to what I...

This bug also seems to occur with this pattern: ```tsx export const metadata: Metadata = { metadataBase: "http://localhost:3000", alternates: { canonical: "./", }, }; ``` See https://github.com/amannn/next-intl/issues/2119

Maybe `useRoute` could be helpful to address this: https://github.com/vercel/next.js/pull/85527