[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Package Qt WebEngine dictionaries



I am developing a Qt WebEngine based web browser named Privacy Browser.


https://www.stoutner.com/privacy-browser-pc/


Currently it is in pre-alpha, but it will soon reach an alpha release stage, at which point I would like to package it for Debian.� I noticed that Debian does not currently ship packages for Qt WebEngine dictionaries.� Qt WebEngine can use Hunspell dictionaries compiled into a special binary format using qwebengine_convert_dict from the qtwebengine5-dev-tools package.

https://doc.qt.io/qt-5/qtwebengine-features.html#spellchecker


The binary packages should be placed (currently) in the /usr/share/qt5/qtwebengine_dictionaries directory, although I would assume that it would make sense to create a symlink from /usr/share/qt6/qtwebengine_dictionaries, and I would assume that when qt6 becomes the default the binary files should move there.


Once the binary dictionary files are in Debian any program that uses Qt WebEngine can take advantage of them (they do have to enable spell checking in their source code and select the desired language).


I created a feature request to work with the maintainer of the English Hunspell dictionary package (src: scowl) and it seems like the best way to handle this would be to use the existing source to create these binary files, either in the existing binary package or in a separate package.


https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017646


My questions for the Debian KDE community is if there is a preference for the naming convention of a possible new binary package and if the proposed file locations and symlinks are the best way to handle the installation.


My plan was to wait and see how things landed with the English package and then reach out to the maintainers of the other Hunspell languages and offer assistance to add the Qt WebEngine dictionaries to their packages as well.


Soren


--

Soren Stoutner

623-262-6169

soren@stoutner.com

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: