Refactor BibTeX file field

JabRef should be convenient for new users to use. When using the file field, the format for each file entry is description:link:type. Multiple values can be put in separated by ;. At each file, fields can be omitted. file = {desc} is a valid enry. Naively, I would have assumed that desc is the link. Furthermore type is a custom JabRef string, but Media Types are the accepted standard for providing types.

Therefore, I propose the new format link:description:media type.

Furthermore, I propose dropping support for the legacy fields pdf and ps. These fields were legacy from the end of 2007 on. Even though some users want to keep the old fields, I would vote for an intuitive handling of references to external files instead of clutter the UI with legacy things. (I currently can't find the email in the mailinglist where we discussed that :()

Discussion points

• Is media type too over-engineered? Can we drop the type completely and derive the type by the file extension?
• Are : and ; good separators?
• Is file really more intuitive than separate pdf and ps links? Should we keep the pdf field?
• Should the new field be called attachments to enable easy migration from the old format to the new one?

Next steps

I would propose a discussion at this issue and I'll update this text accordingly.

We should also remove "Tools -> Legacy Tools...".

More to read

• Old style: http://jabref.sourceforge.net/help/ExternalFiles.php
• Current style: http://jabref.sourceforge.net/help/FileLinks.php

No files, tests, or entry points are named. Read the linked old-style and current-style file-link documentation, then resolve the proposed format, separator and media-type choices, legacy pdf/ps handling, field naming, and removal of Tools -> Legacy Tools before implementation.