Change Details

If there is a direct match for a mime type, only the matching plugin(s) is (are) returned, inheritance is not considered. Otherwise, all matches for all mime ancestors are returned, even if one plugin is a much better match than any other. Up until now, the only extractor selected by inheritance was the plain text extractor, so there was one fuzzy matched plugin at most. With the XML extractor, the XML extractor should be preferred over the plain test extractor. Depends on D16592

Currently, if there is a direct match for a mime type, only the matching plugin(s) is (are) returned, inheritance is not considered. Otherwise, all matches for all mime ancestors are returned, even if one plugin is a much better match than any other. Change the inheritance case to only return well matching extractors. Up until now, the only extractor selected by inheritance was the plain text extractor, so there was one fuzzy matched plugin at most. With the XML extractor, the XML extractor should be preferred over the plain test extractor. Depends on D16592

IfCurrently, if there is a direct match for a mime type, only the matching plugin(s) is (are) returned, inheritance is not considered. Otherwise, all matches for all mime ancestors are returned, even if one plugin is a much better match than any other. Change the inheritance case to only return well matching match than any otherextractors. Up until now, the only extractor selected by inheritance was the plain text extractor, so there was one fuzzy matched plugin at most. With the XML extractor, the XML extractor should be preferred over the plain test extractor. Depends on D16592