Closed
Bug 343931
Opened 18 years ago
Closed 18 years ago
Set app name in InfoPlist.strings during build based on --enable-official-branding
Categories
(Firefox Build System :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla1.8.1beta2
People
(Reporter: moco, Assigned: mark)
References
Details
(Keywords: fixed1.8.1)
Attachments
(1 file, 1 obsolete file)
10.12 KB,
patch
|
benjamin
:
review+
beltzner
:
approval1.8.1+
|
Details | Diff | Splinter Review |
have a branded version of InfoPlist.strings under other-licenses
suggested by robert.
when you have --enable-official-branding on mac, we should override dist/Firefox.app/Contents/Resources/English.lproj/InfoPlist.strings (which normally comes from
mozilla/browser/app/macbuild/Contents/Resources/English.lproj/InfoPlist.strings) with a Firefox branded one from somewhere under mozilla/other-licenses.
see bug #343825 for more info about why this would be good.
Note, this file is UTF16 and contains something like:
1 /* Localized versions of Info.plist keys */
2
3 CFBundleName = "Bon Echo";
4 NSHumanReadableCopyright = "Copyright © 1998 - 2006 Contributors.";
Note, the tbird version is not UTF16, so it is lxr'able and editable with simple editors. (See http://lxr.mozilla.org/mozilla1.8/source/mail/app/macbuild/Contents/Resources/English.lproj/InfoPlist.strings)
Does anyone know why the firefox one is UTF16?
Reporter | ||
Comment 1•18 years ago
|
||
worth fixing for b2, to prevent future pain.
Target Milestone: --- → Firefox 2 beta2
Assignee | ||
Comment 2•18 years ago
|
||
The file is supposed to be UTF-16, although UTF-8 usually works. Translators of apps that go through the traditional OS X localization process get upset when .strings files are UTF-8 because Apple's localization tools insist that they be UTF-16.
What we should do is have InfoPlist.strings.in, in UTF-8, and let sed replace a token with $MOZ_APP_DISPLAYNAME, and pipe its output into iconv to produce a UTF-16 InfoPlist.strings. That way, we won't need a branded version in other-licenses, we can let the right file with the right content and right encoding be generated dynamcially.
Then we should think about doing the same thing with the copyright year, to eliminate the depth of the annual "happy new year" changes.
Finally, get rid of that damn period in NSHumanReadableCopyright.
Comment 3•18 years ago
|
||
I think Mark has the right approach
Summary: have a branded version of InfoPlist.strings under other-licenses → Set app name in InfoPlist.strings during build based on --enable-official-branding
Comment 4•18 years ago
|
||
Seth - could you verify this does the right thing. I didn't bother with including the cvs remove of the old plist file.
Assignee: sspitzer → robert.bugzilla
Status: NEW → ASSIGNED
Attachment #229523 -
Flags: review?(sspitzer)
Reporter | ||
Comment 5•18 years ago
|
||
> Seth - could you verify this does the right thing.
testing now...
Reporter | ||
Comment 6•18 years ago
|
||
I tested it, and this patch works for me.
robert and I were wondering about:
NSHumanReadableCopyright = "Copyright © 1998 - 2006 Contributors.";
a) where does the copyright item appear? How can you see it?
b) Is it convention to not have the "." at the end?
Assignee | ||
Comment 7•18 years ago
|
||
NSHumanReadableCopyright is "required," but it's only used by the default Cocoa about box. We don't use the default Cocoa about box, even when we're a Cocoa app. But because Apple calls the key "required," we should supply something rational anyway.
And get rid of the period.
And I'd prefer to see APP_NAME enclosed in some @ guards to make it clear that we do substitution.
And I'd prefer to see the transformation done in a pipeline, avoiding the need for unnecessary temporary files.
+ sed -e "s/@APP_NAME@/$(APP_NAME)/" $(srcdir)/macbuild/Contents/Resources/English.lproj/InfoPlist.strings.in | iconv -f UTF-8 -t UTF-16 > $(DIST)/$(APP_NAME).app/Contents/Resources/$(AB).lproj/InfoPlist.strings
Updated•18 years ago
|
Attachment #229523 -
Attachment is obsolete: true
Attachment #229523 -
Flags: review?(sspitzer)
Comment 8•18 years ago
|
||
Mark, would you be willing to fix this bug... I'd like to simplify the change from nightly to the official build process but I don't have a Mac currently and would prefer not to introduce inconsistencies between the Mac OS X build files or to go through the files to make them consistent.
Assignee: robert.bugzilla → nobody
Status: ASSIGNED → NEW
Assignee | ||
Comment 9•18 years ago
|
||
Assignee | ||
Updated•18 years ago
|
Component: General → Build Config
Flags: review?(benjamin)
Product: Firefox → Core
Hardware: PC → Macintosh
Target Milestone: Firefox 2 beta2 → mozilla1.8.1beta2
Version: Trunk → 1.8 Branch
Comment 10•18 years ago
|
||
Mark, changing the product removed the review request you had set
Assignee | ||
Comment 11•18 years ago
|
||
Comment on attachment 229855 [details] [diff] [review]
Patch for Firefox and Thunderbird, tested
Doh! I hate it when that happens.
Attachment #229855 -
Flags: review?(benjamin)
Updated•18 years ago
|
Attachment #229855 -
Flags: review?(benjamin) → review+
Assignee | ||
Comment 12•18 years ago
|
||
Checked in on the trunk.
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 13•18 years ago
|
||
Comment on attachment 229855 [details] [diff] [review]
Patch for Firefox and Thunderbird, tested
This is a build config-only change that eases the transitions back and forth between BonEcho and Firefox.
Attachment #229855 -
Flags: approval1.8.1?
Comment 14•18 years ago
|
||
Comment on attachment 229855 [details] [diff] [review]
Patch for Firefox and Thunderbird, tested
a=drivers, please land on the 181branch
Attachment #229855 -
Flags: approval1.8.1? → approval1.8.1+
Assignee | ||
Comment 15•18 years ago
|
||
Checked in on MOZILLA_1_8_BRANCH for 1.8.1b2.
Keywords: fixed1.8.1
Comment 16•18 years ago
|
||
Hmm, this looks nice... We should probably do the same for SeaMonkey...
Comment 17•18 years ago
|
||
I'm seeing this in my Firefox trunk build:
...
creating security/manager/locales/Makefile
creating browser/Makefile
Unknown variable:browser/app/Makefile:367: sed -e "s/@APP_VERSION@/$(APP_VERSION)/" -e "s/@APP_NAME@/$(APP_NAME)/" $(srcdir)/macbuild/Contents/Info.plist.in > $(DIST)/$(APP_NAME).app/Contents/Info.plist
This is in the long list of makefiles that are created by configure. Looking at today's tinderbox logs for Firefox & Thunderbird, Trunk and 1.8 branch, I see much the same.
Is the escaping of the @ used in bug 345388 needed here too ?
Also, where would I check in the Mac Firefox 2.0b2 RC builds that the app name and version are being set correctly ?
Assignee | ||
Comment 18•18 years ago
|
||
Yes, this is the escaping thing.
Updated•7 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•