l10n from early on
Bug #1255185 reported by
Arash Badie Modiri
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Flashback |
Confirmed
|
High
|
Unassigned | ||
Bug Description
the app should be translatable and localized from early on, it'd get harder as we add strings to ui. these are localization points that come to my mind:
* normal strings: this one is straight forward.
* fetched data: some services (including tmdb) provide some localized content. we should have a measure of their integrity before we could enable use of their translated content inside the app.
* country specific data: like different parental advisory systems / currencies / services available and so on. this one is tricky. We don't have any of these kinds of content for now.
Revision history for this message
| Nekhelesh Ramananthan (nik90) wrote | #1 |
| Changed in cliffhanger: | |
| status: | New → Confirmed |
| importance: | Undecided → High |
| milestone: | none → 0.1 |
| Changed in cliffhanger: | |
| milestone: | 0.1 → 0.2 |
| Changed in cliffhanger: | |
| milestone: | 0.2 → 0.3 |
| Changed in cliffhanger: | |
| milestone: | 0.3 → 0.3.1 |
| Changed in cliffhanger: | |
| milestone: | 0.3.2 → backlog |
To post a comment you must log in.
Nice catch! I will have a commit in the near future focussed towards making all strings currently in the app internationalised.