We did receive a report, that on a Windows Phone 8.1 there is a message that the html5 overideMimeType is not supported. This message does mean that the dictionary files, which are locally stored on the device in the html5 application cache, cannot be read, i.e. translations will not work.
The DfM WebApp runs nicely since version 11 of the Internet Explorer; Internet Explorer versions prior to 11 (e.g. Internet Explorer 9 and Internet Explorer 10) had a poor support for HTML5 and the DfM WebApp does not run on those older Internet Explorer versions.
What version of Internet Explorer is running on Windows Phone 8.1 ?
Html5test.com reports I am using version 11 for wp8.
I'll report if I find a solution.
Guess that should mean that IE 11 does implement overrideMimeType: http://msdn.microsoft.com/en-us/library/ie/dn448456(v=vs.85).aspx (http://msdn.microsoft.com/en-us/library/ie/dn448456(v=vs.85).aspx) ; or not ? Well that description is really not clear for me. At least the Windows IE 11 does implement overrideMimeType.
Besides, long term I plan to replace overrideMimeType: when I change to web workers. But that will take quite some time, cause web workers do not provide multithreading as Java does (described here: http://dictionarymid.sourceforge.net/forum/index.php?topic=285.msg1534#msg1534 (http://dictionarymid.sourceforge.net/forum/index.php?topic=285.msg1534#msg1534)). I will have to do some substantial redesign due to the restrictions of web workers.
Guess Microsoft will soon provide an updated version of the IE for Windows Phone ? That should solve all problems.
The setting of WP8.1's IE is limited. It does not even display it's version number. I tried doing both desktop and mobile mode with no success. Seems to me that the mobile version does not support this.
Hope that Windows do update mobile IE to support this.
I did read that there is a new version of Windows Mobile 8.1 and that there is an updated IE included which is supposed to improve HTML5 compatibility. I am confident that this IE update will resolve the issue on Windows Mobile.
Please keep us updated once you receive that update - thanks a lot !