We want to change the description of the homepage in the migration wizard, http://lxr.mozilla.org/l10n-mozilla1.8/source/fy-NL/other-licenses/branding/firefox/brand.properties It should look like http://lxr.mozilla.org/mozilla/source/other-licenses/branding/firefox/locales/en-US/brand.properties The corresponding patch is the en-US part in https://bugzilla.mozilla.org/attachment.cgi?id=257411&action=diff#mozilla/other-licenses/branding/firefox/locales/en-US/brand.properties_sec1 Current String in English for homePageSingleStartMain: "Firefox Start, a fast search page with search results by XXX" New String: "Firefox Start, a fast home page with built-in search" Please create the patch as cvs -z3 diff -u fy-NL/other-licenses/branding/firefox/brand.properties from the l10n directory, we'll try to grab those patches together and land them with the en-US change. See bug 372409 and bug 371309 for more information.
Created attachment 257662 [details] [diff] [review] homePageSingleStartMain string change I hope I did this one right, otherwise please let me know. Wim
Comment on attachment 257662 [details] [diff] [review] homePageSingleStartMain string change approval-l10n is dead, cancelling that. Note that we'll land the patches we get in one go, so there's currently no need to request approval for those. On the patch, is there a line ending change going on? And the en-US patch removed quite a few entries, which you're adding back.
Created attachment 257671 [details] [diff] [review] changed endings and removed lines This one must be better. Wim
Attachment #257662 - Attachment is obsolete: true
Comment on attachment 257671 [details] [diff] [review] changed endings and removed lines Yes, thanks, this one looks good. You don't need to worry about landing that on the branch, we intend to do that in one go with the en-US patch.
Adding fixed220.127.116.11 keyword as I landed the patch here as part of bug 372409 and attachment 258556 [details] [diff] [review]. Please land this on the trunk yourself and mark this bug fixed, and use the verified18.104.22.168 keyword after verifying my landing on the branch. Thanks for the patches.
From what I can see, this bug is FIXED.
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.