I changed the language settings from english to Chinese in Chrome browser. But navigator.language is still displaying as 'en-US'. Expected output should be 'zh'.
Whats the problem here?
You may have to change the language setting in two places.
If you're seeing Chrome menus and words in the wrong language, please follow the steps to change Chrome's default language: https://support.google.com/chrome/answer/95416?hl=en
If you're seeing all Google products in the wrong language, please go here to update your language settings: https://www.google.com/settings/account
Related
Jitsi not showing any option to change language in arabic in swift.I have checked many ways but not able to find any solution for it.
L20n is really helpful when it comes to implementing a localization requirement in our web application project and works perfectly fine in Chrome and Firefox and almost gets us there in Internet Explorer 11.
We are using HTML (which is supported) in the translation strings, they are formatted like this example:
"About <strong> a </strong>"
It works beautifully in Chrome and Firefox:
Translation result in Chrome
Unfortunately when I switched to Internet Explorer 11, getting this lovely sight on the same part of the page:
Translation result in IE 11
We're not doing anything weird or super special, it's pretty basic implementation.
Question is - has anyone encountered this issue while working with l20n and if so - is there anything that can be done to get Internet Explorer to render tags in translation strings?
After help from #Sampson (cheers!) and pointing out that a) It was issue on IE11/Edge Mode not Edge b) IE11 does not support one of the HTML5 elements such as Template, I dug around a little bit before I was about to announce complete defeat and digging through l20n github pages:
l20n compatibility
Using babel polyfill
Using patched webcomponents HTMLTemplateElement polyfill (link provided on page
I added babel and modified polyfill js file and after quick deploy and nervous refresh, it appeared the solution worked. Testing it as we speak so that it doesn't cause issues with the app but all looks good so far.
I know this is a workaround but our IE traffic is small enough yet I was not able to give up on these users that would like to use what I am currently working on in Irish and coincidentally would end up using IE11.
Due to the lack of support for the <template> element in Internet Explorer 11, the following fails:
// https://github.com/l20n/builds/blob/0d58a55afa6ae5aa868b8002fae5ee0e2124e35d/l20n.js#L94
var templateSupported = 'content' in document.createElement('template');
It's worth noting that the l20n.js team doesn't consider IE to be supported.
Spell check is not supporting in webkit.
If we add attribute "spellcheck=true" for the elements which required spell check, its not supported by webkit. Any one know how to deal with this?
node-webkit doesn't support's spell check , But you can find it in electron(previously called atom shell).It's also like a node-webkit Engine .It can render html,javascript and nodejs. If i made any mistake please correct me.
I have not find any tutorial about using xcode's "Fix and Continue feature". If someone knows how to use this please let me know. I would like to use this feature in iOs Apps. Does some knows a way to use this. Whenever I use this I got error "classname.m dylib" not found.
Here is a screen-shot when using fix and continue feature for iPhone apps.
Second result from just typing 'xcode fix and continue' into the search field on google gives http://thurly.net/14ty
This shows (albeit following a long previous tutorial) how fix and continue works.
I have a list of tags which when clicked, display a page which contains more info about that particular tag. In fact, it describes it in detail, in a i-frame .
The issue i am facing is that, when my firebug version 1.5.4 is enabled the details ares displayed but when i disable the Firebug, the details do not get displayed.
the coding has been done in vb.net
my browser is firefox v 3.6.8
I was looking for ideas on how i should go about fixing this issue.
One common way that "Firebug fixes buggy pages" is when developers use window.console() (or just console functions) in JavaScript development and then deploy without guarding the calls -- EG: if (window.console).