Closed Bug 333816 Opened 19 years ago Closed 18 years ago

Do not hardcode the application name in InfoPlist.strings

Categories

(Firefox Build System :: General, defect)

Product:
Firefox Build System
Component:
General
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 343931

People

(Reporter: beltzner, Unassigned)

References

Details

For Mac-OSX builds, we now use /browser/app/macbuild/Contents/Resources/English.lproj/InfoPlist.strings to provide the menubar title of the application. I'm changing that from "Deer Park" to "Minefield" in bug 308973, but am wondering where we pick up the menubar title when the official-branding switch is turned on. I don't see an equivalent file in the /other-licenses directory ...
From the same place... before releases we were changing it back to "Firefox". Note: utf-16 file.
Summary: Where does the InfoPlist.strings for official-branding builds come from? → Do not hardcode the application name in InfoPlist.strings
in #developers, josh, Mano, mento, bsmedberg and I were spitballing the idea of using the value in brand.dtd or brand.properties and then generate the plist file in UTF-16 during the build process using something like: iconv -f UTF-8 -t UTF-16 < somecvsfile.plist-utf8 > InfoPlist.strings
I would just use $(MOZ_APP_DISPLAYNAME), unless you're planning on making that dependent on some branding flag as well.
Fixed last summer, in bug 343931.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
Component: Build Config → General
Product: Firefox → Firefox Build System
You need to log in before you can comment on or make changes to this bug.