Hi @p3x-robot - thanks for submitting this. To help me understand what action can be taken here could you clarify what you mean by:

I am blocked by the way @angular/localize is implemented. It is overly complex and if I want to simple want switch to another language I would have to fire up a new application, which is a huge overhead.

What is blocking you?
What do you mean by fire up a new application?
Are you talking about the browser or the server?
What would be the ideal solution for you in concrete terms?

Hi @p3x-robot - thanks for submitting this. To help me understand what action can be taken here could you clarify what you mean by:

I am blocked by the way @angular/localize is implemented. It is overly complex and if I want to simple want switch to another language I would have to fire up a new application, which is a huge overhead.

What is blocking you?
What do you mean by fire up a new application?
Are you talking about the browser or the server?
What would be the ideal solution for you in concrete terms?

Basically, in the official guide, there is no info about how to implement with SSR with localization without having multiple SSR apps. The only way is to make it to fire every localization in a new SSR app.
Is there a way to implement localization with 1 SSR app?

I talk about this => https://angular.io/guide/i18n
If we use without SSR, it is simple, because, you just deploy in the proper dictories (like /var/www/domain.com/en and /var/www/domain.com/es and /var/www/domain.com/hu etc.. and it works. But there is no info how to use it with SSR, which is crucial to have a complete solution. In AngularJs it is much simpler, although there is no SSR...

So, I feel, the SSR and localization are not friends at the moment.

this guide is good (without SSR):
https://dev.to/angular/deploying-an-i18n-angular-app-with-angular-cli-2fb9

But what about SSR AND localization?

OK now I understand. I don't know much about how SSR works. Do you have a link to a guide for that? Are you using @angular/universal only? Or are you using something like https://github.com/scullyio/scully?

It looks like i18n support is still on the roadmap for Scully: https://github.com/scullyio/scully/blob/master/docs/roadmap.md#L12

and there is quite some discussion going on here: scullyio/scully#318

It seems there is also discussion on the Universal repo: angular/angular-cli#25726

Transferring this issue there as it is not specifically a framework issue, since the @angular/localize package is unlikely to need to change to improve this support.

Actually I don't have rights to transfer it :-/

But I am going to close this and suggest that you continue the discussion at angular/angular-cli#25726

ok, thanks, got it

Fwiw, check this article about supporting i18n with Universal:

https://medium.com/@marcozuccaroli/a-multilanguage-application-with-angular-universal-6e5fe4c2d81c

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}