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

Organizing file extensions #142

Open
margaretha opened this issue Mar 23, 2022 · 4 comments
Open

Organizing file extensions #142

margaretha opened this issue Mar 23, 2022 · 4 comments

Comments

@margaretha
Copy link
Collaborator

margaretha commented Mar 23, 2022

It could be useful to be able to group the file-extensions by domains or at least to see to which domain a file-extension belongs.

When users are not familiar some file extensions, which domains they belong would be quite informative and provides a nice quick hint. The information is also pretty interesting because it exposes some implicit relations (extension - format - domain).

The implementation maybe somewhat complicated since file-extensions maybe used in multiple formats and formats may have multiple domains.

Another idea is to filter domains simply alphabetically, since the list is quite long.

This ticket is a follow-up to the issue #108 .

@margaretha
Copy link
Collaborator Author

margaretha commented Mar 23, 2022

Actually it is maybe useful to include domains in format pages.

@bansp
Copy link
Member

bansp commented Mar 23, 2022

You mean information generated on the basis of recommendations? Interesting.

@bansp
Copy link
Member

bansp commented Mar 23, 2022

I'm in two minds wrt allowing domains to intervene. But it may be an interesting perk whose significance I simply don't fully grasp yet, now that I can only imagine such a system.
I would say it definitely sounds like a very good idea ( and in fact a separate ticket ) to display in format descriptions the list of domains that currently mention the given format as recommended or acceptable (maybe not so much if they mention it as deprecated).
Whether the same is true of extensions, I cannot say for sure, but it definitely never hurts to try.

EDIT: Oh, but we do implement the "very good idea" by providing tables of recommendations inside every format description. So we're down to considering whether it's useful to have a relationship between extensions and domains that is not mitigated by formats. Right, I'm not hugely excited, but that may be because my imagination is poor, in this regard.

@bansp bansp added this to the the milestone that isn't milestone Mar 21, 2023
@bansp
Copy link
Member

bansp commented Oct 25, 2023

I tend towards a wontfix, here. Extensions are in some way accidental, they can be missing, especially in *nix systems. They will also most probably sometimes be "homographic", meaning the same sequence of characters used as an extension for two or more different formats.

Listing them, sure, by all means. But I'd rather not make them first-order citizens, so to say.

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

No branches or pull requests

2 participants