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

Internationalise all of the views. #4057

Closed
wants to merge 1 commit into from
Closed

Internationalise all of the views. #4057

wants to merge 1 commit into from

Conversation

treacher
Copy link

@treacher treacher commented Apr 24, 2016

Hello, this PR is to figure out if there is much of an appetite for internationalising everything. I'm going through the process of doing this at the moment in a rails application so thought it might be worth while contributing it back so that others don't have to.

TODO:

  • Standard views
  • Simple Form views
  • Markerb mailer views
  • Shared links
  • Make sure en.yml is in alphabetical order
  • Squash commits

At the moment the approach I'm taking is to have everything as a seperate key even if the content is the same as you can see in this example here. This is to increase the flexibility incase users of the gem want to customise the button text for example.

Thanks :)

- i18nify confirmation views
- Internationalise confirmation_instructions mailer.
- Internationalise password_change mailer.
- Internationalise password_change, reset_password and unlock mailers. Tidied up confirmation instructions mailer.
- Internationalise passwords views.
- Internationalise registration views
- Internationalise session views
- Internationalise shared links
- Internationalise unlock views
- Internationalise hint for passwords#edit view
- Internationalise simple form views for confirmations and passwords
- Internationalise simple form views for registrations, sessions and unlocks
- Update en.yml so that keys are in alphabetical order.
- Internationalise markerb templates
@josevalim
Copy link
Contributor

Hi @Galkon,

Thank you but we don't plan to accept this PR because the views were always meant to be a starting point and not a final version. Also, adding translation calls to them make the views much harder to understand to everyone not using i18n.

Please see #2058 #1642 #1983 #1989 #3684 and many others similar issues/pull requests for the reasons.

@josevalim josevalim closed this Apr 24, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants