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

Supporting multiple languages / localization #18

Open
MrCsabaToth opened this issue May 28, 2018 · 3 comments
Open

Supporting multiple languages / localization #18

MrCsabaToth opened this issue May 28, 2018 · 3 comments

Comments

@MrCsabaToth
Copy link
Contributor

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

  1. Separate resources into a file.
  2. Tune the build system to consume that.
  3. 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.

@MrCsabaToth
Copy link
Contributor Author

I have an implementation (https://robisim74.github.io/angular-l10n) using https://robisim74.github.io/angular-l10n but I'd need to separate it into a clean branch and also improve it further for a PR

@MrCsabaToth
Copy link
Contributor Author

See it working on https://valleydevfest.com

@MrCsabaToth
Copy link
Contributor Author

I have a PR in the pipeline but first I'd like the #31 to be reviewed and merged

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

No branches or pull requests

2 participants