0

I have a Angular app that I am trying to localize. What I have so far is that all my displayed values are located in a single json file (stringResources.json). After translation I will have multiple files, one for each of the languages that I want to support (i.e en.json, fr.json ect). I use AOT compilation so my options seem to be

What I did was to generate multiple builds by using this package to output a different build for every language file, and each of these builds work well. I cannot seem to figure out how to do the server side logic to deliver the correct package based on url or language detection

I have 2 questions:

1) What would be the best way to make my app support l10n(localization)? It seems I have no need to go into Angular's built in i18n, since I already have the string files extracted and available?

2) What are some resources I can look into to figure out the server side logic and how to organize the structure for the different builds? I have tried changing the web.config file but that seems it will interfere with the app's routing logic

WhatDoesTheStackSay
  • 1

1 Answers1

0

Unfortunately I do not know much about angular.

But you might read this article...

I would recommend looking into a i18n lib that is ready to be used in different frameworks, in frontend and backend, i.e. i18next

There are some vue libs too: i.e. ng-i18next or ng2-i18next or angular-i18next

Further you should not only consider that you have to instrument your code (i18n) to get your app/website translated. You should think about the process too - how will you solve continuous localization, how you keep track of progress, etc...

For a translation management+ system you might eg. have a look at locize it plays well with all json based i18n frameworks... and provides a lot more than traditional systems.

adrai
  • 2,495
  • 1
  • 15
  • 18