We're migrating away from L10n-per-element to L10n-per-page in an effort to reduce confusion. If you have an AMO account (you have one, right?) you can see an example of our current L10n on the "In a little more detail..." box on https://addons.mozilla.org/en-US/firefox/users/edit#user-profile An example of the new workflow is available at: http://people.mozilla.com/~chowse/drop/amo/devtools/v3/interaction/localization.png I suspect the backend will remain mostly similar (accepts a bunch of well named variables in a POST and stores them in the right places) but the front end is where the juicy bits lay. The mockup is nicely detailed (thanks chowse) so I won't spell it all out here, but this bug consists of doing it all. If there are further questions we can answer them here and/or file more bugs if they are late in the game.
https://github.com/jbalogh/zamboni/commit/02a7753 I have this working on the Description field in edit add-on, there seems to be some query caching going on with the translated values. I dont' know all the fields that should be localized, but I'm going to expand the coverage in a separate bug.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.