Support .ltxt extraction in Tower

RESOLVED FIXED in 4.x (triaged)

Status

P3
normal
RESOLVED FIXED
9 years ago
3 years ago

People

(Reporter: clouserw, Assigned: clouserw)

Tracking

unspecified
4.x (triaged)

Details

(Assignee)

Description

9 years ago
Remember how we said we'd need to support normal django extraction so we didn't collapse whitespace in emails?  Well, that time is now.  And babel doesn't have django extraction built in, of course.

babeldjango does what we want perfectly, but raises an exception by trying to load the settings from extract.py (?!)  http://babel.edgewall.org/browser/contrib/django/babeldjango/extract.py#L17

Without that line, it works great.
(Assignee)

Updated

9 years ago
Assignee: nobody → clouserw
(Assignee)

Comment 1

9 years ago
I filed http://babel.edgewall.org/ticket/215 last week.  Still no response.  I'd rather them fix it than copy the function, but we'll do what we have to.  If it's not fixed by 5.10, I'll fix it then.
(Assignee)

Updated

9 years ago
Target Milestone: 5.9 → 5.11
(Assignee)

Comment 2

9 years ago
This isn't important until we start sending emails
Target Milestone: 5.11 → 4.x (triaged)
(Assignee)

Updated

7 years ago
Blocks: 635840
Wil, want to update babel so we can get localized emails? :DD
(Assignee)

Comment 4

6 years ago
Yes.  I'll evaluate how it fits in with our new plans of getting rid of vendor.  Pip would make it easy.
(Assignee)

Comment 5

5 years ago
pretty sure we do this now.
Status: NEW → RESOLVED
Last Resolved: 5 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.