setting target milestone to M11
Summary: resource out all hard coded strings & error messages → [feature] resource out all hard coded strings & error messages
need to identify all hard coded strings and error messages, and add StringBundle support to them.
reassign to Samir, per today's bug meeting.
Resourced strings now in chrome://xpinstall/locale/xpinstall.properties which translates to <dist>/bin/chrome/xpinstall/locale/en-US/xpisntall.properties. Modifying this file will modify UI action text.
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
Install action strings as well as dialog messages have now been resourced.
Failover now implemented: if the string bundle service is not available, or fails, or the xpinstall.properties file is not available then we will still display messages and log install actions, but in english instead of teh locale specific language. This is always the case for the install wizards where we cannot get the string bundle service. To test, just rename the xpinstall.properties file thus rendering it inaccessible. When you start apprunner after this, XPInstall will fail to load the .properties file but should still show messages on dialogs including the initial confirmation dialog.
Build 1999-10-18-09-M11(WIN), 1999-10-18-12-M11(MAC), 1999-10-18-08-M11(LINUX) Looks good.
Bulk move of XPInstall (component to be deleted) bugs to Installer: XPInstall Engine
You need to log in before you can comment on or make changes to this bug.