Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upStudio document MIME type? #309
Open
Labels
Comments
|
Writing OS-specific metadata seems kinda weird – I think that adding them through the OS makes sense, and your link has a few good directions. If you end up with an XML file (like in the second example), you could put it in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
So I've finally gotten Studio running on an Ubuntu VM rather than my macbook; it took a bit of confusing setup but it's basically working now.
However, the one issue that I'm still having is file association: Ubuntu associates files by MIME type rather than by suffix, and for some reason it considers all files saved by Studio to be of type "plain text document". Meaning, if I change them to open in Studio rather than gedit, then so do all my .txt files.
I'm not really sure what the usual approach for fixing this is—is there a way for Studio to write a MIME type to the file's metadata when it saves it? Or would it be better to add a system-wide MIME type association to the .IO suffix as explained here? https://help.ubuntu.com/community/AddingMimeTypes (Maybe the checkout could include a .sh file for adding-if-absent, and the Ubuntu build instructions could include running that file?)
I am still absolutely brand new at Linux, so I have absolutely no idea if I'm even barking up the right tree here—it took me ages just to get Studio to even appear in the "open with" list. (Actually come to think of it, I guess that ought to be in the same hypothetical setup .sh file?)