Quote:
Originally Posted by luite
The method uds::PluginMgr::create_document first calls uds::PluginMgr::get_plugin_path to check this map for one of the hardcoded extensions. Unknown extensions are handled by loading all plugins and checking them to see if the format is supported.
There may be something that goes wrong there.
|
That would be my guess too. I haven't checked, but I think the mobipocket plugin for some reason reports it can open the djvu file. When it actually opens the file, the plugin finds that it is not a valid Mobipocket.
You might be able to work around it by renaming the Mobipocket plugin so it is probed _after_ the DJVU plugin. In that case, opening Mobipocket files will take a bit longer as UDS has to check all plugins first.