Home

Globalize2

Next Up

• Implementation details of Locale load paths? (see this gist)
• Implementation details of Content Translation.
• Implementation progress.

Priorities

1. Locale + Translation classes
2. view translations with yaml (file/dir structure)
3. basic model translations (simplest thing possible)

Meta

• We will use RSpec for testing, along with a model factory such as Object Daddy or Factorygirl.
• The top-most module will be Globalize.
• The plugin will be distributed as a gem plugin.

Component Specifications

YAML-based View Translation

Content Translation

Locale Class

Other Stuff

• Locale switching after translated model is already loaded
• Chained Backend
• Fallbacks
• Caching
• Helpers
• Currency formatting
• Form processing
• View template switching
• Determining locale from HTTP, etc
• Translation view generator — creates controller/view to manage translations online
• Rake tasks
  • dump, load translations
  • generate migrations
  • look for untranslated keys (possibly)

Notes

To run the specs go to the projects root dir and run: spec -O spec/spec.opts spec