Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use the shared-mime-info database for mime type support. #11

Closed
rhdunn opened this issue Oct 29, 2011 · 1 comment
Closed

Use the shared-mime-info database for mime type support. #11

rhdunn opened this issue Oct 29, 2011 · 1 comment
Labels
Milestone

Comments

@rhdunn
Copy link
Owner

@rhdunn rhdunn commented Oct 29, 2011

Replace the current mime-type support with the shared-mime-info database.

The idea here is to have a list of (mime-type-string => parser-function-pointer). The mime-type logic will then:
1/ build the RDF metadata for the supported document and audio mime-types using the mime-type database;
2/ use the magic detection logic from the mime-type database;
3/ use the XML namespace root and local-name from the mime-type database for XML documents.

Items 2 and 3 will be used as part of the handler lookup to get the parser function. The parser function will then be called to handle the data.

In some cases (email; mht; epub), this will involve recursive calls.

For the OCF handler, the information will need to be returned as RDF metadata to unify the parser interface.

@rhdunn rhdunn closed this Nov 3, 2011
@rhdunn
Copy link
Owner Author

@rhdunn rhdunn commented Nov 3, 2011

This has now been implemented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.