Evaluate using `i18n_patterns` to support language-agnostic links

[jacobtylerwalls]

As Tobias pointed out when LocaleMiddleware was removed, the site uses URL-based language selection, not header-based language selection. However, my understanding is that we could use both if we use i18n_patterns():

https://docs.djangoproject.com/en/6.0/topics/i18n/translation/#language-prefix-in-url-patterns

For instance, when creating blog & forum posts announcing releases, I could provide language-agnostic links like

/stable/...

instead of

/en/stable/...

to avoid privileging English.

Has this been discussed before? I certainly wouldn't want this proposal to resurface any headaches like #868.

[manvendra5345]

Hello! I’m interested in contributing to this project as part of GSoC.
Could you please assign this issue to me? I’d love to work on it and get started.
Thanks!

[jacobtylerwalls]

Thanks for your interest. It's a little early for that, since we're not sure we even want to do this. (I'm half-expecting someone to point out I've misunderstood the use case or add history around why it wouldn't suit us.)

[manvendra5345]

Ok sir thanks for letting me know. But if thers eis an issue u see fit for me let me know as I am just strating my open source contribution and dont have much prior knowledge.