[okular] [Bug 423560] [Windows Store] Filename extension associations and updates resetting them

Beybalaev Murad Felixovich bugzilla_noreply at kde.org
Wed Jul 8 00:04:50 BST 2020


https://bugs.kde.org/show_bug.cgi?id=423560

--- Comment #4 from Beybalaev Murad Felixovich <gness.na at gmail.com> ---
(In reply to Hannah von Reth from comment #3)
> Hi if your interested in extending the default associated files, feel free
> to fill in the mime types and extensions in here
> https://invent.kde.org/packaging/craft-blueprints-kde/-/blob/master/kde/
> applications/okular/okular.py#L53

The list already has to be somewhere in the codebase, since the Windows build
comes with one used for internal operation. Okular must be passing it to the OS
shell when creating its "Open file" dialog — the dialog lists all of the
supported extensions for filtering. That's where I ripped them from for my
registry patch. And then I added *.txt on my own, which was not listed for some
reason.

Here's a screenshot: https://i.imgur.com/lcDWUeQ.png

I could format that list to your language and code style, reference
corresponding mime types, maybe even test if each of them works nominally on
Windows. But...
1. It would be kind of a waste to duplicate something that's already somewhere
in the codebase.
2. I'd hate to go through the whole rigamarole of creating a local GitLabs
Community account, cloning the whole repo to edit 2 strings and then pull
requesting...

Do let me know if you can't locate the existing list that's somewhere out there
already. I'd look for it myself, but I'd just get lost in the vast KDE
codebase.

And would it be fine if I just sent a formatted list in a letter, releasing any
rights I could have for it, so you can slap your lovely GPL2 on it?

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Okular-devel mailing list