Language auto-detection broken
Reported by Allen Pike | September 18th, 2008 @ 02:40 PM | in REL 0.9.21
The auto-detection and localization feature of SC does not work in 0.9.17. In both development and production modes, String.currentLanguage() is set correctly, but it does not load the appropriate strings.js file required for that language. Erich and I have already spoken about this on IRC and he is on the case.
Comments and changes to this ticket
-
Erich Ocean (onitunes) September 30th, 2008 @ 04:03 AM
- → Milestone changed from “” to “REL 0.9.21”
- → State changed from “new” to “hold”
So...this needs some work. For now, using sc-build with relative paths will allow you to configure the default index.html with the language you want to forward to (you will have to do this manually after running sc-build).
I have confirmed that you cannot "pick and choose" languages within a single client, as would appear to be the case with the language detection code. In fact, you really need to actually load the correct client, with the correct language.
My recommendation (for now) is to run sc-build in relative path mode and put whatever language detection logic in the default index.html file. Then load the corresponding sub-client based on that logic.
Best, Erich
-
Erich Ocean (onitunes) November 8th, 2008 @ 09:29 AM
- → Assigned user cleared.
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
SproutCore: JavaScript Application Framework
Source available from github
The Git repository resides at http://github.com/sproutit
Check out the current development trunk with:
git clone git://github.com/sproutit/sproutcore.git
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
Submitting Patches
Resist adding new tags, use the ones in the tag cloud already. If you are submitting a patch or a pull request from a fork, tag the ticket as a "patch". If you are submitting a new feature enhancement, tag it as "enhancement". If you are submitting a fix for a bug, tag it as "fix".
Thanks!
We're glad you're contributing. Feel free to drop by the Google Group as well to let us know you are involved.
