clarkwinkelmann The prefix on all pages based on browser headers is an interesting way to go, it would make a lot of sense, it is probably the best solution for guest users, as in most cases it will work correctly and if it doesn't the user will still have the option to change the language of the page and force the desired language.
What I had originally thought was based on the core language selector, so it would follow the current behaviour, with the difference of saving the user a couple of steps in the process.
Currently if a guest user enters a post and wants to see it in another language, assuming it is written in the other language, they would have to do the following:
- Enter the link to the post (English) -> Change the language of the site -> Search for the same post on the site (which can be a cumbersome task) -> View the post (Italian).
In this way the steps would be reduced to the following:
- Enter the link to the post (English) -> Change the language of the site -> View the post (Italian)
The main advantage of this is that everything happens on the same page, the feeling for the user would be that of pressing a button to translate the page.
But with what you have commented I have realized a serious problem with this solution, if the redirection of the post is based on the language selector, if the default language of the web is French, when entering the URL of the post in English automatically redirect the guest user to the French post, also we can suppose that maybe the user really wants to see is the post in Italian, so in this case even if you had specifically forced the language that had the URL the result would not have been satisfactory, a real mess 😂
In this scenario the browser headers would probably have been the best option, don't you think?