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

Update documentation to remove 'desirable' suggestion for what is not a clear cut approach #21644

Merged
merged 1 commit into from Sep 16, 2015

Conversation

AvnerCohen
Copy link
Contributor

I suggest to remove the desirable comment.

I have been supporting large, small and huge I18n'ed systems. I came to clearly conclude that using plain text format/YAMLs as the backend for the translated data is the way to go, it makes things far superior in:

  1. Auditing, change control and versions
  2. Scaling translation with external services is easier with YML and flat file, rather than dumping and re-inserting data to tables.
  3. Environment management - no need to move data from dev to prod in the form of insert scripts, it's all part of the code base.

I could well be wrong, but at the very least, if not whole-heartily recommending using simple YAMLs as I18n storage, I think it would be more helpful to drop the "desirable" references to (questionable) alternatives.

@rails-bot
Copy link

r? @arthurnn

(@rails-bot has picked a reviewer for you, use r? to override)

claudiob added a commit that referenced this pull request Sep 16, 2015
Update documentation to remove 'desirable' suggestion for what is not a clear cut approach
@claudiob claudiob merged commit 7a93952 into rails:master Sep 16, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants