Open mickmister opened 3 years ago
First step would just to introduce a class LocalizationHandler
that does basically nothing. Then we can move to a more robust implementation.
We should be creating the ids for the strings as we go. Something like zendesk.ticket.not_found
In order to prepare for localization, we should start putting any user-facing strings through an i18n pipeline.
We can eventually use something robust like https://github.com/mashpie/i18n-node for the javascript apps