Bugzilla – Bug 9586
Default per player language is English
Last modified: 2009-09-08 09:14:56 UTC
When setting up a player, if the language chosen is not English and the SqueezeNetwork UI language is not English, then the player default is English. For example, if I configure Boom in its setup to be Italian and on SqueezeNetwork the UI is set to Italian, then the language displayed on Boom is English. This is due to the per player setting on SqueezeNetwork defaulting to English. Don't know what the behavior should be, maybe it follows the SN UI or is linked to the account's country setting?
Verified this does not happen when doing a first time connect to SC 7.2.x. Both SC and Player stay in the chosen language. When connecting an unregistered player to SN or test.SN for the first time, the player is defaulted from the chosen language, to English. This happens for all languages, not just Italian
change 4625 - default player language setting to the user's language setting Please note that the "visit www.sn.com..." line will still be displayed in EN. This probably needs a firmware change to transmit the language selected in firmware to SN when connecting for the very first time. Should this be a hotfix?
I vote for yes, as this would improve user experience, especially for our growing European customers.
The firmware language is sent as part of the HELO packet, so we can use that.
Change 23310, default language to firmware language.
I'm still seeing this bug with Boom fw 39 connecting to test.sn with both my SN account and Boom set to Spanish once connected all menu's are in English.
Ross: were you connected to test.sn or production.sn at the time of your testing.
Ross to retest today. This work's on Michael's local SC.
Andy notes that this player should be excised from the prefs file to make sure that setting is not saved. Michael says there was a bug where the player firmware preference was used instead of any other setting at one time.
Works great now!
This bug has been fixed in the latest release of SqueezeNetwork! If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.