Split Fortran into fixed and free source by file extension

[ararslan]

This permits applying a different tm_scope for modern Fortran.

Description

Currently all Fortran files are recognized as fixed-source (think FORTRAN 77 style), which is provided by the TextMate bundle as source.fortran. However, the old style really only applies for a few file extensions. Instead, we can do as @pchaigno suggested and split the definitions into two "dialects" sharing a common group, one for fixed-source and one for free-source (i.e. modern).

Checklist:

• I am fixing a misclassified language
  • I have included a new sample for the misclassified language:
    • Sample source(s):
      • [URL to each sample source, if applicable]
    • Sample license(s):
  • I have included a change to the heuristics to distinguish my language from others using the same extension.

I'll need a bit of guidance for completing the checklist here.

EDIT: Meant to make this a draft PR.

Fixes #4799...?

[Alhadis]

I'm not familiar with Fortran, but I'm wondering if the hassle over syntax highlighting can be resolved with a carefully crafted grammar that can recognise both dialects. From what I've read here, though, that mightn't be easy.

In either case, I'm okay with the split, provided the issues I mentioned are addressed.

[stale]

This pull request has been automatically marked as stale because it has not had recent activity, and will be closed if no further activity occurs. If this pull request was overlooked, forgotten, or should remain open for any other reason, please reply here to call attention to it and remove the stale status. Thank you for your contributions.

[stale]

This pull request has been automatically marked as stale because it has not had recent activity, and will be closed if no further activity occurs. If this pull request was overlooked, forgotten, or should remain open for any other reason, please reply here to call attention to it and remove the stale status. Thank you for your contributions.

[jacobwilliams]

Still needed. The broken version is still being used on GitHub.

[ararslan]

Sorry, I just haven't had time to revisit this. If you'd like to take a stab at it, please feel free to base your work off of this branch if it would help.

[stale]

This pull request has been automatically marked as stale because it has not had recent activity, and will be closed if no further activity occurs. If this pull request was overlooked, forgotten, or should remain open for any other reason, please reply here to call attention to it and remove the stale status. Thank you for your contributions.

[ararslan]

Still relevant but still no time to revisit.

[stale]

This pull request has been automatically marked as stale because it has not had recent activity, and will be closed if no further activity occurs. If this pull request was overlooked, forgotten, or should remain open for any other reason, please reply here to call attention to it and remove the stale status. Thank you for your contributions.

[ararslan]

Same deal

[lildude]

I'll pick this up and implement my suggestion.

[lildude]

🎉 all done.

[lildude]

For those watching this, I won't be able to make a release until after 2 Jun, so these changes won't appear on GitHub.com until probably the week after at the earliest.

[ararslan]

Thanks so much for getting this over the finish line, I really appreciate it!