Closed Bug 8140 Opened 21 years ago Closed 21 years ago

[feature] resource out all hard coded strings & error messages

Categories

(Core Graveyard :: Installer: XPInstall Engine, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: cathleennscp, Assigned: samir_bugzilla)

References

Details

Target Milestone: M11
setting target milestone to M11
Blocks: 11020
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.
Assignee: cathleen → sgehani
reassign to Samir, per today's bug meeting.
Blocks: 12805
Status: NEW → ASSIGNED
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
Closed: 21 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.
Status: RESOLVED → VERIFIED
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
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.