The default bug view has changed. See this FAQ.

Loading and Install text has mixed capitalization.

VERIFIED FIXED in Firefox 6

Status

Fennec Graveyard
General
VERIFIED FIXED
6 years ago
6 years ago

People

(Reporter: dougt, Assigned: dougt)

Tracking

({verified-aurora})

Trunk
Firefox 6
All
Android
verified-aurora

Details

Attachments

(1 attachment)

(Assignee)

Description

6 years ago
Loading and Install text has mixed capitalization.

http://mxr.mozilla.org/mozilla-central/source/embedding/android/locales/en-US/android_strings.dtd


I think we want:


<!ENTITY  splash_screen_label "Loading">
<!ENTITY  splash_screen_installing "Installing Libraries\u2026">

Instead of what we currently have.
(Assignee)

Comment 1

6 years ago
Created attachment 539840 [details] [diff] [review]
patch v.1
Assignee: nobody → doug.turner
Attachment #539840 - Flags: review?(mark.finkle)
(Assignee)

Updated

6 years ago
tracking-fennec: --- → 6+
Attachment #539840 - Flags: review?(mark.finkle) → review+
You updated the string entities too! Excellent.
(Assignee)

Comment 3

6 years ago
http://hg.mozilla.org/mozilla-central/rev/9a4d38add60a

Mark, should we get this on the 6 train?
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
(Assignee)

Updated

6 years ago
Attachment #539840 - Flags: approval-mozilla-aurora?
Comment on attachment 539840 [details] [diff] [review]
patch v.1

Android only and low risk
Attachment #539840 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Target Milestone: --- → Firefox 6
status-firefox6: --- → affected
Mozilla/5.0 (Android; Linux armv71; rv7.0a1) Gecko/20110622 Firefox/7.0a1 Fennec/7.0a1
Device: Thunderbolt
OS: Android 2.2

Mozilla/5.0 (Android; Linux armv71; rv7.0a1) Gecko/20110622 Firefox/7.0a1 Fennec/7.0a1
Device: HTC Flyer
OS: Android 2.3
Status: RESOLVED → VERIFIED
(Assignee)

Comment 6

6 years ago
http://hg.mozilla.org/releases/mozilla-aurora/rev/80cc8011254e
status-firefox6: affected → fixed

Comment 7

6 years ago
Umm, why is a locale change accepted on Aurora? We promise to be L10n frozen from Aurora on to release, I don't think we should change that, esp. not for something that trivial.
(In reply to comment #7)
> Umm, why is a locale change accepted on Aurora? We promise to be L10n frozen
> from Aurora on to release, I don't think we should change that, esp. not for
> something that trivial.

Looking around for the golden rule, I found a proposal Axel wrote:
http://groups.google.com/group/mozilla.dev.planning/msg/8e660e18b6daf4f4

I read that saying Aurora was the last place where string changes could happen. Beta was a "no-change without driver approval" zone. Also, we were over 2 weeks away from the branch move when the patch was approved.

Comment 9

6 years ago
(In reply to comment #8)
> Looking around for the golden rule, I found a proposal Axel wrote

I CCed him, he should clarify.

> I read that saying Aurora was the last place where string changes could
> happen. Beta was a "no-change without driver approval" zone. Also, we were
> over 2 weeks away from the branch move when the patch was approved.

That message seems to be from even before we got things rolling fully in the new system. From all I know Aurora should (ideally) be the last place where changes *in the localizations* happen, but strings on en-US need to be frozen at the time when the code *enters* Aurora, i.e. string changes can only happen on mozilla-central, not on mozilla-aurora.

This is what all other code changes have been following so far, and I actually only came here because localizers complained.

I'll let Axel resolve this, though.
(In reply to comment #9)

> That message seems to be from even before we got things rolling fully in the
> new system. From all I know Aurora should (ideally) be the last place where
> changes *in the localizations* happen, but strings on en-US need to be
> frozen at the time when the code *enters* Aurora, i.e. string changes can
> only happen on mozilla-central, not on mozilla-aurora.

This is correct.  

Is there a chance that we can back this patch out on 6 and target 7?
(In reply to comment #10)

> Is there a chance that we can back this patch out on 6 and target 7?

backing out
backout from aurora:
http://hg.mozilla.org/releases/mozilla-aurora/rev/05281bcf64d3
Thanks Mark!
status-firefox6: fixed → ---
tracking-fennec: 6+ → 7+
status-firefox7: --- → fixed
Verified fixed on this cycle (7)

Mozilla/5.0 (Android; Linux armv7l; rv:7.0a2) Gecko/20110727 Firefox/7.0a2 Fennec/7.0a2
Keywords: verified-aurora
You need to log in before you can comment on or make changes to this bug.