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
We'd want to provide localized version of our DevFest site. This will be crucial for us because this year we plan to support the large number of Spanish speaking minorities explicitly, and the front facing state for that is the conference website. (At some point Hoverboard v1 BTW provided support for that, using Polymer's capability, but was slashed due to people complaining about difficult setup).
Expected Behavior
The default resources would be separated from the source, and the additional locales would reside next to that. The build step would consume these versions and produce a site where it can be toggled somewhere.
Current Behavior
Right now it seems that the resources are not separated. As far as I see there's no localization foundation. I'm not skilled in Angular particularly to tell how easy it is to implement this whole ticket.
Possible Implementation
Separate resources into a file.
Tune the build system to consume that.
Allow additional resources and provide toggle system.
Context (Environment)
We at least Spanish version besides English. At some point with Hoverboard v1 we had Hmong and Farsi localizations as well, which I produced by auto translation script using Google Translate API.
The text was updated successfully, but these errors were encountered:
We'd want to provide localized version of our DevFest site. This will be crucial for us because this year we plan to support the large number of Spanish speaking minorities explicitly, and the front facing state for that is the conference website. (At some point Hoverboard v1 BTW provided support for that, using Polymer's capability, but was slashed due to people complaining about difficult setup).
Expected Behavior
The default resources would be separated from the source, and the additional locales would reside next to that. The build step would consume these versions and produce a site where it can be toggled somewhere.
Current Behavior
Right now it seems that the resources are not separated. As far as I see there's no localization foundation. I'm not skilled in Angular particularly to tell how easy it is to implement this whole ticket.
Possible Implementation
Context (Environment)
We at least Spanish version besides English. At some point with Hoverboard v1 we had Hmong and Farsi localizations as well, which I produced by auto translation script using Google Translate API.
The text was updated successfully, but these errors were encountered: