Closed Bug 1001430 Opened 11 years ago Closed 9 years ago

add infrastructure for pulling strings out of the database for l10n

Categories

(Input Graveyard :: Backend, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: willkg, Assigned: willkg)

References

Details

(Whiteboard: u=dev c=backend p=1 s=input.2015q4)

We need to add infrastructure that pulls data out of the database and puts it in a .py file for strings extraction. We'll need this for any product-related strings like descriptions.
I'm pretty sure this isn't hard to do. It involves creating a new django command to build a file or something like that. Kitsune has this, so I'll look at what they do and follow suit.
Assignee: nobody → willkg
Priority: -- → P2
Whiteboard: u=dev c=backend p=1 s=input.2014q2
Pushing this off until 2014q3. Fixing it doesn't affect anything slated for this quarter.
Whiteboard: u=dev c=backend p=1 s=input.2014q2 → u=dev c=backend p=1 s=input.2014q3
Whiteboard: u=dev c=backend p=1 s=input.2014q3 → u=dev c=backend p=1 s=input.2014q4
Bumping to 2015q1 because we're out of time for 2014q4.
Whiteboard: u=dev c=backend p=1 s=input.2014q4 → u=dev c=backend p=1 s=input.2015q1
Changing this to a P1. It should get done asap.
Priority: P2 → P1
Ran out of time this quarter. Pushing it off. :(
Whiteboard: u=dev c=backend p=1 s=input.2015q1 → u=dev c=backend p=1 s=input.2015q2
Whiteboard: u=dev c=backend p=1 s=input.2015q2 → u=dev c=backend p=1 s=input.2015q3
We have a couple of strings that are affected now. However, we're in a new quarter.
Whiteboard: u=dev c=backend p=1 s=input.2015q3 → u=dev c=backend p=1 s=input.2015q4
Status: NEW → ASSIGNED
Landed in https://github.com/mozilla/fjord/commit/92c778c56fc92805885363c150a07e32052d157c Pushed to prod just now. Synced strings so product names are now translateable.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Bug #1226601 covers fixing some problems with the extract_db command I wrote for this bug. :(
Product: Input → Input Graveyard
You need to log in before you can comment on or make changes to this bug.