Extract localizer class to reuse in different scenarios.
It can use different backends (DNN, NGettext).
DNN backend will resource file root file, NGettext backend - text catalog.
Backport some code from R7.Epsilon for the case of "single" resource file for entire extension / subsystem.
DNN backend will need to implement plural forms.
NGettext backend will possibly need to implement DNN-like Host/Portal overrides. E.g. we would have several text catalogs under the hood, and try to get string from Portal one, then from Host one, and only then from System one.
Also would be nice to provide relative benchmarks of both backends.
Viewmodel context classes could reuse existing localizers.
Extract localizer class to reuse in different scenarios.
It can use different backends (DNN, NGettext).
DNN backend will resource file root file, NGettext backend - text catalog.
Backport some code from R7.Epsilon for the case of "single" resource file for entire extension / subsystem.
DNN backend will need to implement plural forms.
NGettext backend will possibly need to implement DNN-like Host/Portal overrides. E.g. we would have several text catalogs under the hood, and try to get string from Portal one, then from Host one, and only then from System one.
Also would be nice to provide relative benchmarks of both backends.
Viewmodel context classes could reuse existing localizers.