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

[Beybalaev Murad Felixovich]

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

            Bug ID: 423560
           Summary: [Windows Store] Filename extension associations and
                    updates resetting them
           Product: okular
           Version: 1.10.1
          Platform: Other
                OS: Microsoft Windows
            Status: REPORTED
          Severity: wishlist
          Priority: NOR
         Component: general
          Assignee: okular-devel at kde.org
          Reporter: gness.na at gmail.com
  Target Milestone: ---

Created attachment 129708
  --> https://bugs.kde.org/attachment.cgi?id=129708&action=edit
Registry patch

I use Okular distributed on Windows Store on my Windows 10 OS.
Upon installation **and updates** Okular sets its filename extension
associations to only a handful of formats. It is in fact able to parse many
more formats but limitations of Windows Apps platform, subject to Windows
Store, make it impossible to open any arbitrary filetype in Okular straight
from OS without first launching Okular and using its "Open" dialog.

Note, that trying to associate an "App" installed through Windows Store using
the legacy OS "Open with" dialog just does not accomplish anything other than
leave you with a registry mess to clean up if forced.

I had to resort to writing my own registry patch (attached) to add all
supported associations bindings (and some that seem underdeveloped in the
Windows build, but it doesn't hurt anyway).

If you take a look at the attached registry patch, note that only the first key
with its many values (first 60 lines) is required — rest is just for extended
support and can be omitted AFAIC.
Also note, that key name (path) includes the version string.

Now for the meat of the issue: not only do I have to reapply the registry patch
on every update, but I also have to edit it in accordance with the new version
string every time.

I could write a script to heuristically accomplish this for me but it doesn't
feel like it's too much to ask you, as developers, to instead open the whole
array of associations by default or at least give me, as a user, an option to
enable further filename extension associations.

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