Bug 13559 - Language settings not updating correctly
: Language settings not updating correctly
Status: RESOLVED DUPLICATE of bug 11360
Product: SqueezePlay
Classification: Unclassified
Component: UI
: unspecified
: PC Windows XP
: P3 normal (vote)
: 7.4.x
Assigned To: Michael Herger
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-08-21 08:51 UTC by Ryan
Modified: 2009-10-02 13:54 UTC (History)
4 users (show)

See Also:
Category: ---


Attachments
photo of a Baby while set in Russian. but showing English and Germain too (3.38 MB, image/jpeg)
2009-08-24 08:34 UTC, Ryan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan 2009-08-21 08:51:23 UTC
when switching languages not all menu items are changing. I switched from english to Russian and back and about half of the items in the setup menu are still in Russian.

After power cycling the menus are updated correctly.
Comment 1 James Richardson 2009-08-21 10:16:55 UTC
Ben: would this be yours or tom's to look at?
Comment 2 James Richardson 2009-08-21 10:18:14 UTC
*** Bug 13558 has been marked as a duplicate of this bug. ***
Comment 3 Ben Klaas 2009-08-22 19:32:10 UTC
mine, but toggling back and forth between languages is a corner case enough to drop this to a P2
Comment 4 Ryan 2009-08-24 08:34:53 UTC
Created attachment 5672 [details]
photo of a Baby while set in Russian. but showing English and Germain too

The Baby was set for Russian at the time of the photo.
Comment 5 Ben Klaas 2009-08-26 07:53:07 UTC
this is an administrative shuffle on priority fields to help make better judgment on the top end of the priority list. P4->P5, P3->P4, and P2->P3.
Comment 6 Ben Klaas 2009-10-02 11:34:12 UTC
Michael, this sounds like the old langs-not-synced-between-SP-and-SN issue. Are you familiar with this?
Comment 7 Michael Herger 2009-10-02 13:54:27 UTC
That's actually a dupe of 11360: menus loaded from remote sources (mysb.com) are cached for some time. Thus will still show the old language for a few minutes.

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