search

Triply-Dev / YASGUI.YASQE-deprecated

Deprecated, see https://github.com/TriplyDB/Yasgui for the Yasgui monorepo
MIT License
73 stars 36 forks source link

Consider internationalization #111

Closed jindrichmynarz closed 7 years ago

jindrichmynarz commented 7 years ago

I would be useful if the strings in English that are displayed to users were extracted to allow internationalization. Currently, these strings are scattered throughout the code, such as in the autocomplete or in the interface.

LaurensRietveld commented 7 years ago

Seems like a reasonable thing to do. The thing that's holding me back is the integration of 3rd party UI libs (e.g. datatables, Google chart, the pivot table plugin,and perhaps other in the future). These may or may not support internationalization..

jindrichmynarz commented 7 years ago

These are YASR plugins, right? In YASQE, internationalization would be related mostly to itself, so it may be simpler to achieve.

YASR already nicely exposes ways to localize plugins, such as YASR.plugins.table.defaults.datatable.language for DataTables.