That, of course, depends on the application requirement.
I work on a very large app which is not (only) used by ourselves, but by
other organizations.
And on each organization, administrators can change translations on the fly
- just a F5 or logout / login away.
In this scenario, of course,
Hello everyone,
I'm trying to make a decision for my new project whether to use static or
dynamic string internationalization.
I know how to use both. It's more about pros and cons:
- The big advantage of dynamic internationalization to me, is that I can
store my translations in a database,
- The big advantage of dynamic internationalization to me, is that I can
store my translations in a database, and update texts without the need of
stopping servers to deploy a new compiled version of my application.
Not sure if its that big of an advantage. IMHO translations rarely
