Ability to manually specify locale in SSR

[demensky]

Description

There is no way to specify locale in AngularAppEngine#handle based on Accept-Language, Cookie, etc. The current implementation of AngularAppEngine chooses locale based on URL.

Describe the solution you'd like

Ability to specify an array of locales when calling handle:

 app.use('/**', (req, res, next) => {
   angularApp
-    .handle(req)
+    .handle(req, undefined, { locales: req.acceptsLanguages() })
     .then((response) =>
       response ? writeResponseToNodeResponse(response, res) : next(),
     )

As far as I understand, this will also require removing the locale prefix from <base href="…"/>.

Describe alternatives you've considered

No response

[alan-agius4]

It is not recommended to display application content based on the Cookie and Accept-Language headers while using the same URL. For more details, refer to Google's guidelines on managing multi-regional sites: Google's Multi-Regional Sites Documentation. Following this, I believe we should not add support for this, as it contradicts what's recommended.

However, an alternative feature could be implemented for cases where internationalization (i18n) is enabled. In this scenario, users can be redirected to their preferred language locale if no specific locale is included in the URL.

For example:

• http://www.example.com/ → http://www.example.com/fr (if the user's preferred language is French).
• http://www.example.com/ → http://www.example.com/en (if the user's preferred language is English).

[demensky]

@alan-agius4

This is relevant if the content is different in different locales. This is even stated in the link you provided:

If your site offers different content to users in different languages, countries, or regions, you can optimize Google Search results for your site.

Google recommends using different URLs for each language version of a page rather than using cookies or browser settings to adjust the content language on the page.

For example, I see different locales when I go to https://docs.google.com/, https://www.youtube.com/, https://translate.google.com/, etc. Even the link you provided opened in the locale that I use.

For example, in blogs, a link with a locale is quite relevant. But in admin panels, online stores, etc., this greatly interferes with users, because if they open a link from outside, we will show the UI not in the locale that is relevant for the user, but in the locale of the user who provided the link.

[alan-agius4]

This seems to be a rather specific use case, as Angular's build-time i18n generates separate files/routes for each locale, and these files are always located in different directories (including for client-side routing). This setup may not align well with your goal. Your use case might be better suited for runtime translations, where there are no separate resources nor route for each locale.

[angular-robot]

This feature request is now candidate for our backlog! In the next phase, the community has 60 days to upvote. If the request receives more than 20 upvotes, we'll move it to our consideration list.

You can find more details about the feature request process in our documentation.

[angular-robot]

Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

Find more details about Angular's feature request process in our documentation.

[angular-robot]

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.