D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-890L => Topic started by: jarome on May 21, 2015, 11:32:10 AM
-
Google Chrome insists on translating all the router pages from Chinese to English, even though the original IS in English.
-
What version of Chrome are you using?
Does his happen on a different PC with Chrome?
Does this happen with IE or FF?
Try Opera or FF?
Disable any security browser Add-ons like No Script and Ad-Block or configure them to allow All Pages when connected to the router.
Clear all browser caches.
Be sure to log into the Admin account on the router.
Try turning off these features in Chrome:
Top right corner, little bars for options > Settings > Settings (on left) > Show advanced settings.
Uncheck these:
Use a web service to help resolve navigation errors
Use a prediction service to help complete searches and URLs typed in the address bar
Predict network actions to improve page load performance
Enable phishing and malware protection
Post a picture of what your seeing in Chrome:
Adding Screenshots In A Post (http://forums.dlink.com/index.php?topic=58120.0)
-
Actually the login page flicks on and disappears in Firefox on my Mac.
On Chrome I am using Version 43.0.2357.73 beta (64-bit) and on Windows. Both say it is Chinese. But it only does this the first time I connect. There is a popup in the top-left corner that says "This page is being translated" and now it changes to "This page could not be translated". But it is cosmetic.
Now I get it again:
https://www.dropbox.com/s/fdx4jbvql7ffx2p/Chinese.png
It works properly on Safari.
Firefox's 38.0.5 page source is
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html lang="zh_TW" xml:lang="zh_TW" xmlns="http://www.w3c.org/1999/xhtml">
<head></head>
<body id="main" style="display:none">
<div id="wrapper"></div>
</body>
</html
This is a problem for firefox users on a Mac. Firefox on Linux works OK.
-
What region are you located? ???
-
I am in Tennessee!
-
I haven't seen any issues with mine and others haven't mentioned it...possible browser configuration with your PC(s)?
You might try reloading the FW file using the following:
Link> >FW Update Process (http://forums.dlink.com/index.php?topic=42457.0)
Use IE or FF to do this. Clear all browser cashes before and after the last factory reset. Disable any 3rd party PC security SW and browser add-ons.
-
I just reloaded the firmware a la the process, and I got Chinese before and after doing so.
-
D-Link considers this a minor annoyance and will review it. As long as the UI is correctly displaying in English, you'll be fine. The UI supports a few different languages so Chrome and FF are picking up on the course language coding and converting it. Maybe D-Link will adjust this in the future versions for the NA region. ::)
Enjoy for now.
-
I agree totally about the Chinese.
But not displaying at all in my Firefox is more serious. This happens even if I start Firefox on my Mac in safe mode which disables all plugins.
-
I'll check on this with my Mac and see what I find. I have Mac and Windows. ::)
-
I can report back that FF v37.0.1 and v38.0.1 are working with the routers UI on Mac OSX 10.10.3 Mac Mini 2012
-
I'm also having Google Chrome trying to translate from Chinese.
Google Chrome: Version 45.0.2454.37 beta-m (64-bit)
-
Link>Welcome! (http://forums.dlink.com/index.php?topic=48135.0)
- What Hardware version is your router? Look at sticker under the router case.
- Link>What Firmware (http://forums.dlink.com/index.php?topic=47512.0) version is currently loaded? Found on the routers web page under status.
- What region are you located?
Do other browser experience this for you? IE or FF?
I'm also having Google Chrome trying to translate from Chinese.
Google Chrome: Version 45.0.2454.37 beta-m (64-bit)
-
I know this is a dead topic, but I think I found the reason.
If you look at the source for the page, this is near the top:
<html xmlns="http://www.w3c.org/1999/xhtml" xml:lang="zh_TW" lang="zh_TW">
-
Thanks for posting as it was mentioned earlier that there was this issue. I believe this issue has been fixed in a more recent build of FW. ;)