You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, for i18n we rely directly on system locale. We should depend on and use an external locale-data such as what Babel does.
This would provide a real support for Alpine Linux for instance (see #133 (review) for more context / details about Alpine issue) and less system-dependent behaviors.
We have to check all our use cases to check how to implement this with minimal/no impact.
The text was updated successfully, but these errors were encountered:
After discussing with @rgaudin it is clear that we do not really have a precise idea of how localization should work. So for 4.0.0 we will rather remove i18n translation. It is anyway rarely used by scrapers: ted => barely translated in Hindi, not used in Zimfarm ; openedx => barely translated in Hindi, not working anymore ; nautilus => only translated to FR.
Plan is to confirm what is the proper API and proper way of doing translations across scrapers without current issues on system dependencies.
Currently, for i18n we rely directly on system locale. We should depend on and use an external locale-data such as what Babel does.
This would provide a real support for Alpine Linux for instance (see #133 (review) for more context / details about Alpine issue) and less system-dependent behaviors.
We have to check all our use cases to check how to implement this with minimal/no impact.
The text was updated successfully, but these errors were encountered: