Configure Phrase 3: Locale Eater

Description

Working with Translation to get Phrase ready for them to start on translating the emails. In our current setup after , Phrase will push and pull from the same set of files. This will cause conflicts with changes from coders, as well as changes from the original source of our locale files (rails-i18n) when we need to update them.

Requirements: inside config/locales,

  • "en" files are only edited by coders (custom order, code comments that should not be overwritten by Phrase);

  • files imported from rails-i18n are also only edited by coders;

  • all other locale files are generated by Phrase, should not be edited by coders, should not include the default locale "en", and should not re-export the translations from rails-i18n.

The application will use everything in config/locales - so coders can edit "en" files and immediately see changes without waiting for a push-pull round trip with Phrase.

Testing:

Let’s do a smoke test to make sure the locale files are getting loaded.

  • Log in, post a work, and then delete the work. You should get an email about the work being deleted and it should look normal, i.e. not say “translation missing.”

  • Make an unsuccessful attempt to log in as an admin, e.g. by entering the wrong username. You should get a blue flash error message and not, say, a 500 page or some text saying “translation missing.”

TBD: we need to retry the GitHub integration in Phrase and make sure the resulting pull requests are reviewable.

Assignee

Unassigned

Reporter

redsummernight

Roadmap

Internationalization

Priority

Medium

Affects versions

Fix versions

None

Components

BackEnd
FrontEnd

Difficulty

Medium

Required Access Level

Translator

Milestone

Internal 0.9