Closed
Bug 871970
Opened 12 years ago
Closed 12 years ago
Rename datareporting_crashreporter_title entity to reflect string change in data reporting string
Categories
(Firefox Health Report Graveyard :: Client: Android, defect)
Firefox Health Report Graveyard
Client: Android
Tracking
(Not tracked)
RESOLVED
FIXED
Firefox 24
People
(Reporter: flod, Assigned: liuche)
References
Details
Attachments
(1 file, 3 obsolete files)
As explained in Bug 862116 Comment 15
-<!ENTITY datareporting_crashreporter_title "&brandShortName; Crash Reporter">
+<!ENTITY datareporting_crashreporter_title2 "&brandShortName; Crash Reporter">
+<!ENTITY datareporting_crashreporter_title "Crash Reporter">
Unfortunately this already landed in mozilla-central, so a name change for datareporting_crashreporter_title is needed at this point.
About string changes after landing
https://developer.mozilla.org/en-US/docs/Making_String_Changes
Comment 1•12 years ago
|
||
> About string changes after landing
> https://developer.mozilla.org/en-US/docs/Making_String_Changes
Thanks for the documentation link, flod.
Assignee | ||
Comment 2•12 years ago
|
||
Sorry for the localization problem, Francesco. I've uploaded a patch to rename the old crashreporter entity to its originally landed name and update the new string. If I'm wrong about what you meant by renaming, please correct me!
Attachment #749369 -
Flags: review?(nalexander)
Flags: needinfo?(francesco.lodolo)
Assignee | ||
Comment 3•12 years ago
|
||
Forgot to fix in strings.
Attachment #749369 -
Attachment is obsolete: true
Attachment #749369 -
Flags: review?(nalexander)
Reporter | ||
Comment 4•12 years ago
|
||
It's too late for that approach: once a string lands on mozilla-central, if you want to change its content you need to change its ID too. That's the only way to ensure that localizers see the change and don't use outdated strings as a reference.
Now on mozilla-central there are these two strings
<!ENTITY datareporting_crashreporter_title2 "&brandShortName; Crash Reporter">
<!ENTITY datareporting_crashreporter_title "Crash Reporter">
datareporting_crashreporter_title has been changed from the original value in bug 862116, so it has to be renamed. But now you want to change both strings, so you need new IDs for both.
My suggestion would to add strings like these
<!ENTITY datareporting_crashreporter_titleLong "&brandShortName; Crash Reporter">
<!ENTITY datareporting_crashreporter_titleShort "Crash Reporter">
Flags: needinfo?(francesco.lodolo)
Assignee | ||
Comment 5•12 years ago
|
||
Renamed both strings, and updated references up the chain.
Attachment #749378 -
Attachment is obsolete: true
Attachment #749382 -
Flags: review?(sriram)
Attachment #749382 -
Flags: feedback?(francesco.lodolo)
Comment 6•12 years ago
|
||
Comment on attachment 749382 [details] [diff] [review]
Part 1: Rename old crashreporter entity to previous property name v3
Review of attachment 749382 [details] [diff] [review]:
-----------------------------------------------------------------
We don't use camelCase in entities/strings. Please change that to an _underscore. Rest looks fine.
Attachment #749382 -
Flags: review?(sriram) → review+
Reporter | ||
Comment 7•12 years ago
|
||
Sorry, didn't know that.
Patch looks good, but looking at the code I have a doubt: is the string datareporting_crashreporter_title2 (now to be changed in datareporting_crashreporter_title_long) used somewhere?
Assignee | ||
Comment 8•12 years ago
|
||
No, this is basically a complete string replace - we no longer want to use the old crashreporter string. Should I remove it completely if it's no longer going to be used?
Reporter | ||
Comment 9•12 years ago
|
||
If it's not used anymore absolutely yes.
Bug 862116 comment 13 made me think that it was still used somewhere.
Assignee | ||
Comment 10•12 years ago
|
||
Updated to remove camelCase and removed old crashreporter string completely.
Attachment #749382 -
Attachment is obsolete: true
Attachment #749382 -
Flags: feedback?(francesco.lodolo)
Assignee | ||
Comment 11•12 years ago
|
||
Updated•12 years ago
|
Assignee: nobody → liuche
Status: NEW → ASSIGNED
Target Milestone: --- → Firefox 24
Comment 12•12 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Firefox Health Report → Firefox Health Report Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•