Settings pukLastChanceMsg string / PUK strings possible enhancements

NEW
Unassigned

Status

Firefox OS
Gaia::Settings
5 years ago
2 years ago

People

(Reporter: aryx, Unassigned)

Tracking

unspecified

Firefox Tracking Flags

(blocking-basecamp:-, tracking-b2g:backlog)

Details

The following string sounds strange:

apps/email/email.properties Reviewed
setup-empty-account-prompt=You are not setup to send or receive email. Would you like to do that now?


And here, I would replace "the wrong PUK code" with "a wrong PUK code":
apps/settings/settings.properties
#TODO: pukLastChanceMsg=Last chance to enter the correct PUK code. Your SIM card will be permanently unusable if you enter in the wrong PUK code. Refer to your SIM card documentation or contact your carrier for more information.
blocking-basecamp: --- → ?

Comment 1

5 years ago
Casey - are the strings to spec?

Since we're focused on Portuguese for our v1, this is not a blocker.
blocking-basecamp: ? → -
Flags: needinfo?(kyee)

Comment 2

5 years ago
Yes, strings are to spec.   The language could probably use some massaging, but I'll leave that up to the copy folks to sort out.
Flags: needinfo?(kyee)
Re-nominating, because we need good quality en-US strings to provide good translations.
blocking-basecamp: - → ?
Keywords: late-l10n
blocking-basecamp: ? → -
Would it make a little more sense if it is :

setup-empty-account-prompt=You are not set up to send or receive email. Would you like to do that now?
in Portuguese (pt-BR), this string was 'softened' ;-)
The current string is
http://hg.mozilla.org/gaia-l10n/en-US/file/default/apps/email/email.properties
setup-empty-account-prompt=You are not set up to send or receive email. Would you like to do that now?

Which makes enough sense to me.

Removing late-l10n keyword, it would make more sense to have individual bug for each app. :matej is a good reference to improve strings.
Keywords: late-l10n
More strings to check.

Comment 8

4 years ago
I'm not as bothered by this one, but it would be good to come up with something better during the audit. Thanks.
Consider also other strings in comment 0 
I agree that you can enter "a wrong PIN", not "the wrong PIN".
(In reply to Francesco Lodolo [:flod] from comment #9)
> Consider also other strings in comment 0 
> I agree that you can enter "a wrong PIN", not "the wrong PIN".

Isn't there only one correct PIN? In which case "that wrong PIN" is correct. "A wrong PIN" makes it sound like there are several correct ones you could enter.
Sorry, I wrote PIN but it's PUK in those strings (3 of them, AFAIK).
(In reply to Francesco Lodolo [:flod] from comment #11)
> Sorry, I wrote PIN but it's PUK in those strings (3 of them, AFAIK).

Right, sorry, I just copied what you wrote. Same thing, though. Since (I believe) there's only one correct code a user can enter, it should be "the." Small tweak to the original:

apps/settings/settings.properties
#TODO: pukLastChanceMsg=Last chance to enter the correct PUK code. Your SIM card will be permanently unusable if you enter in the wrong code. Refer to your SIM card documentation or contact your carrier for more information.

Comment 13

4 years ago
(In reply to Matej Novak [:matej] from comment #12)
> (In reply to Francesco Lodolo [:flod] from comment #11)
> > Sorry, I wrote PIN but it's PUK in those strings (3 of them, AFAIK).
> 
> Right, sorry, I just copied what you wrote. Same thing, though. Since (I
> believe) there's only one correct code a user can enter, it should be "the."
> Small tweak to the original:
> 
> apps/settings/settings.properties
> #TODO: pukLastChanceMsg=Last chance to enter the correct PUK code. Your SIM
> card will be permanently unusable if you enter in the wrong code. Refer to
> your SIM card documentation or contact your carrier for more information.

Just thinking, I thought a last chance for PUK just rendered the SIM unusable until your provider unlocks it again, last I heard it was not permanent..
If you insert the wrong PIN 3 times, you can reenable the SIM with the PUK code.

Inserting multiple times the wrong PUK code (I think 10 times) will render the SIM completely unusable, beyond recovery.
Component: Gaia → Gaia::E-Mail
(In response to :gasolin moving the bug to e-mail): There is no email action to be taken per comment 6.  I'm moving this to settings since it seems like there has been some meaningful discussion for settings and so maybe the bug is useful there.  If settings doesn't want the bug, please mark resolve invalid or worksforme or whatever.
Component: Gaia::E-Mail → Gaia::Settings
Summary: 'You are not setup' sounds strange → Settings pukLastChanceMsg string / PUK strings possible enhancements
need clarify it when blocker solved
tracking-b2g: --- → backlog
You need to log in before you can comment on or make changes to this bug.