Based on discussion in 65241, it has now been deemed appropriate to remove the Set Language/Region menu from the View menu in Navigator, as the ability to download more content packs has been added to the content packs preferences panel. The menu itself serves only to blur the separation between UI language packs and content packs by presenting them in a single menu (whereas they are now separate entities, accessed from different places within the preferences dialog). I suggest we remove this item if possible in a limbo build. Should be easy (it has been done successfully before). Also cc'ing PM and UE to ensure I read comments in 65241 correctly.

Packs PM -> Agreed, so long as the new prefs code works for all platforms.

90083 becomes invalid once this one is fixed.

No, please do NOT do this on the Netscape 6.1 branch. The pref panel we added for content packs and the language switchign in prefs is still not proven - in fact there have been too many reopens etc of it not working properly. I do not wish to take the risk of removing this and then finding that the pref pan els do not work properly in the shipping product in some case. The right place for this work is the trunk.

Blake - could we hold a bit on this so that Netscape can keep this item in the menu (to preserve menu compatibility with the next release). Let me get some agreement from docs/ue/intl on whether we can live without this or whether we need to file another bug to restore it Netscape's commercial tree. thanks! Vishy

Bug 90304 looks like a dupe of this one, except that 90304 calls for "Apply Theme" to be removed as well.

*** Bug 90304 has been marked as a duplicate of this bug. ***

just FYI, in 0.9.2 release, "Languages and Web Content" items in "View" menu are disfunctional - as far as multiple users of my language packs stated, and as far as I've seen on my linux and win32 systems.

*** This bug has been marked as a duplicate of 61162 ***

mass verification of duplicate bugs: to find all bugspam pertaining to this, set your search string to "DuplicateBugsBelongInZahadum". if you think this particular bug is *not* a duplicate, please provide a compelling reason, as well as check a recent *trunk* build (on the appropriate platform[s]), before reopening.