Hi Konrad,
I added the localisation packages to the package.json for node in the source and it builds.
I am able to hard code, foreign characters intoi the source and see them rendered within the graylog UI on our dev server.
Looking at the structure of graylog, it just imports all the pages. On option would be to use a language detector to determine the language and then change app routing accordingly.
In this scenario, there would be two copies of the source tree for the web interface at following urls as an example
http://127.0.0.1:9000 - default english version
http://127.0.0.1:9000/fr - say french version
This would mean that the compiled build would get huge very quickly.
An alternate method would be to hard code each language support within components of each page using the language detector to determine which to show.
The second is probably better in terms of size of compiled output / execution time.
What are your thoughts?
Jake