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
Localization is something that we've supported in the past that has not been properly addressed in the new version of d3plus. D3 contains some great time formatters, so let's implement a solution that combines any built-ins we can find with more specific word localizations (like the text for the "back" button).
My current idea is to have a global locale object exported by this module, and that object would contain keys for each language, which then in turn contain keys for specific types of localizations. An example format is here:
This object would be created in src/locale/index.js, importing all of the d3-time-format language modules, and importing our own modules from files like src/locale/text/es-ES.js. We would then add a .locale("es-ES") method to BaseClass so that every component can support localization.
Localization is something that we've supported in the past that has not been properly addressed in the new version of d3plus. D3 contains some great time formatters, so let's implement a solution that combines any built-ins we can find with more specific word localizations (like the text for the "back" button).
My current idea is to have a global
locale
object exported by this module, and that object would contain keys for each language, which then in turn contain keys for specific types of localizations. An example format is here:This object would be created in
src/locale/index.js
, importing all of the d3-time-format language modules, and importing our own modules from files likesrc/locale/text/es-ES.js
. We would then add a.locale("es-ES")
method toBaseClass
so that every component can support localization.@cnavarreteliz, @nbond211, thoughts?
The text was updated successfully, but these errors were encountered: