Closed Bug 824470 Opened 13 years ago Closed 13 years ago

Brazil Real currency is hardcoded in the Cost Control application

Categories

(Firefox OS Graveyard :: Gaia::Cost Control, defect, P3)

defect

Tracking

(blocking-basecamp:+, b2g18+ fixed)

RESOLVED FIXED
B2G C4 (2jan on)
blocking-basecamp +
Tracking Status
b2g18 + fixed

People

(Reporter: Pike, Assigned: arcturus)

Details

(Keywords: productization)

Attachments

(1 file, 1 obsolete file)

I've just came across bug 816927, which hard-codes the brazil real as currency within gaia code. Not sure how wide-spread that is.
bug 816927 seeks to remove that app as the fix. I'm confused about if the app will make its return before shipping. anyone have clarity there? I guess the way to assess this bug is to do some greping over the source looking for anything Real or maybe Peso related can be found. The list is long with many false positives in this mxr search. https://mxr.mozilla.org/gaia/search?string=real I wonder if others have ideas on how to do some better searching?
Not really good to search for, but appearing at a few places is 'R$' for the Brazil real. I think the backgroundservice doesn't have anything to do with removing the cost control app?
We're shipping in multiple markets with different currencies, so requesting blocking on doing the audit described above.
blocking-basecamp: --- → ?
I looked at this a bit more from the technical side, via git grep -I 'R\$' and it seems that to some extent build/applications-data.js takes care of things, though I'm not sure if that's as good as things should be. In particular if we're dealing with people using multiple SIM cards while traveling. Apart from that, I found apps/costcontrol/fte.html: R$ apps/costcontrol/index.html: <span id="settings-low-limit-currenc The index.html one seems to be overwritten via apps/costcontrol/js/settings/settings.js, but I'm not sure in a good or timely fashion. I couldn't track down the fte.html one. neither of which I could track down to get configure
Triage: BB+ , in agreement with comment 3
blocking-basecamp: ? → +
Adding some guys responsible for Cost Control and FTE, could you guys check comment #4?
As far as I understand Cost Control this will be seen only if you use a Vivo prepaid card. Renominating based on that and let's ask more information to Salva.
blocking-basecamp: + → ?
Flags: needinfo?(salva)
Summary: Brazil Real currency sprinkled within gaia code → Brazil Real currency is hardcoded in the Cost Control application
The currency of Cost Control is set in OEM configuration. So settings module should load the actual currency and put where it is required. It should not be hardcoded in the HTML so I take the bug (but I'm on vacations yet).
Flags: needinfo?(salva)
Assignee: nobody → salva
blocking-basecamp: ? → -
tracking-b2g18: --- → +
AFAIK, we're shipping 1.0 outside of Brazil as well. We shouldn't hardocde any curencies at all. Re-requesting basecamp-blocking.
blocking-basecamp: - → ?
It is not a matter of i18n but a matter of wich currency is used by your operator to take count of your credit. That is because it is your operator who is in charge of customize this value.
Of course, as I said in comment 8 "It should not be hardcoded in the HTML so I take the bug (but I'm on vacations yet)."
Cool, we're on the same page then :)
Triage: BB+
blocking-basecamp: ? → +
Priority: -- → P3
Target Milestone: --- → B2G C4 (2jan on)
Stealing another one ;)
Assignee: salva → francisco.jordano
Attached file Pointer to GitHub PR 7346 (obsolete) —
Attachment #698904 - Flags: review?(salva)
Comment on attachment 698904 [details] Pointer to GitHub PR 7346 Why add currency to .properties at all? If it's supposed to work as a fallback for when configuration.credit.currency is not set, then I don't think this is desirable. Depending on the locale set by the user, we'd show different currencies, but the same number. This can be harmful to the user. If the currency is not given by the carrier, I think we should display an error message and possibly even not allow to use the cost control app (?).
Yeah, what stas said, the currency shouldn't show up in l10n. Unless, you know, a few releases in the future, we'd had a currency database that'd allow us to have a localized name for the 'R$' brazilian real as well as euros, greek drachmen etc, so that you could get the localized currency name if you used your German phone with a Greek SIM card and cost-control communication.
Hi guys, taking into account the feedback I'll just remove the fallback from l10n. Thanks a lot for the feedback.
New version without l10n requirements. Just based on configuration by partner.
Attachment #698904 - Attachment is obsolete: true
Attachment #698904 - Flags: review?(salva)
Attachment #698926 - Flags: review?(salva)
Component: Gaia → Gaia::Cost Control
QA Contact: carlos.martinez
Attachment #698926 - Flags: review?(salva) → review+
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: