Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Localizer class #36

Open
roman-yagodin opened this issue Mar 16, 2020 · 0 comments
Open

Localizer class #36

roman-yagodin opened this issue Mar 16, 2020 · 0 comments

Comments

@roman-yagodin
Copy link
Member

roman-yagodin commented Mar 16, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant