Matlab source files not opened as text files

[zingmars]

Actual behaviour

When opening a file with a .m extension (Matlab source file), the app downloads it and prompts you to open with apps that don't even deal with text files - https://i.imgur.com/tXdv7PA.jpg.

Perhaps consider adding "Open As" button the same way the Total Commander app does (it lets you open files as if they were a text file/image/video/music no matter what the extension or mime type is, in case the app doesn't recognise it properly)?

Expected behaviour

Either it should open as a text file, or it should let you to open it with an app that supports text files

Steps to reproduce

1. Have a .m file on NextCloud
2. Try to open it with the Android app

Environment data

Android version: 8.0.0

Device model: OnePlus 3

Stock or customized system: Stock

Nextcloud app version: 2.0.0

Nextcloud server version: v13.0.0b4

[AndyScherzinger]

@jancborchardt @MorrisJobke @tobiasKaminsky @mario What do you think? The Android app implements the Nextcloud servers mime type detection 1:1, so since the server doesn't know of .m neither does the Android client. So we could implement the mechanism described in the issue leaving the decision about the mime type to the user in case we can't/don't detect it but this would then of course add yet another menu entry to the file item menu.

[jancborchardt]

If we know that something doesn't work as expected, we shouldn't leave it up to every single user to manage it. :)

Meaning: We should add the .m mimetype to the server, and have it open as textfile (if no Matlab program is installed) as that seems the expected way.
No extra menu entry.

[zingmars]

From how I see it, cataloguing every single major extension is going to be a fairly major task though, not to mention that the user might have files that he has himself created with arbitrary file extensions. You wouldn't be making the users to manage, you would be giving them the option to do so if they desire it.

[jancborchardt]

We’re not building Nextcloud to give people settings/options, we’re building it to offer solutions.

And if adding certain extensions manually is necessary for that then so be it. You did have the feedback, and that’s how we properly solve it. :)

[AndyScherzinger]

@jancborchardt would in your opinion this solution also apply for nextcloud/server#2073?

[jancborchardt]

@AndyScherzinger I guess it does, no? As you say in that thread:

an we basically would need to have a mime type detection for .love file extension to map to application/x-love-game

So yeah, we do have to do what feels like strange handcoding for specific filetypes. But if that helps make the experience for those as expected, it’s the proper solution.

[Spartachetto]

The problem with the various file formats happens also in the web interface.

It was reported both for the text editor: Manage the file extensions associated with texteditor (by me...) and and for the server[enhancement] NC needs a mime type handler selector (by an app developer).
If you read the text editor issues, several of them are about adding various file formats...

I wonder if a unified solution could be possible...

[Spartachetto]

@AndyScherzinger I have the impression that this is a duplicate of nextcloud/server#1756.

That issue made you open another issue in the server repository: Recognize further file extensions as text files (to be opened in the "in-app" text editor).

[AndyScherzinger]

@Spartachetto to some extend yes but relying on the server's mimeType detection hasn't been implemented yet and also the servers mimeType detection would have to be extended to recognize Matlab files since that would be yet another extension.