This is a multi-part message in MIME format.
--nextPart1774896.M3Ca5PYbuj
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="iso-8859-1"
I am developing a Qt WebEngine based web browser named Privacy Browser.
https://www.stoutner.com/privacy-browser-pc/[1]
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[2]
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[3]
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
[email protected]
--------
[1]
https://www.stoutner.com/privacy-browser-pc/
[2]
https://doc.qt.io/qt-5/qtwebengine-features.html#spellchecker
[3]
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017646
--nextPart1774896.M3Ca5PYbuj
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="iso-8859-1"
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">I am developing a Qt WebEngine based web browser named Privacy Browser.</p>
<br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"><a href="
https://www.stoutner.com/privacy-browser-pc/">https://www.stoutner.com/privacy-browser-pc/</a></p>
<br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">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.</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">�</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"><a href="
https://doc.qt.io/qt-5/qtwebengine-features.html#spellchecker">https://doc.qt.io/qt-5/qtwebengine-features.html#spellchecker</a></p>
<br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">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.</p>
<br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">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).</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"><br />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.</p>
<br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"><a href="
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017646">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017646</a></p>
<br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">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.</p>
<br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">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.</p>
<br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">Soren</p>
<br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">-- </p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">Soren Stoutner</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">623-262-6169</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">
[email protected] </p>
</body>
</html>
--nextPart1774896.M3Ca5PYbuj--
-----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmMmSu8ACgkQwufLJ66w tgNzxg//aq3dHrkrwK0fWNUVX4XpYoQrg53YYDtSLMfS0gy3oJu6DRpf0G8OGlMO bWGKR/ZytB2kRi6Zr2+ZgL+MIv4yaBQsxonyUrRjlVuGaCQDllN0fupKGfSPrxm4 7vSGrf41lTwsf3ZOXUbFzwk4O4SSQrLuGiC5wYenSGes62LGK+kb1jq4SksAEnYj RTu3JiJ00WoN8VwIUM0v8Sa3T1V9GlNdEfUNkaln5N9n1IJmikBPlSkatiTPXPke qYvsV0ONuIMIsdoD4dxLQzdoP++eUM4ev9UkG7FFo1WRiUdc8NS98XOhdzenMKwi 6urZkoB5LFq32IfFdvqMaepygIKeI3DU4yrUoa1zzuewQ8YQZ3Tzzlv7tWQACUdw TGEDgai76NqUYlA2yoTzKIuX3pMGu6Cv1mZXGgmypkOn6kZeZZaBbTza5ZS4Dyr1 eXh7OmUZKs5e6sOmNIu53pNdRIokxQmJKAfkzlxiCFmM4g8Irf3IH3GFhyagGico xxn7zyRctTKN7NuT1mr0tmkxDm3LIiYyA//yMY899bER8/fpPZun7cz0GjelyyW6 iJ+EBk5JWHbAM0YA0RyP+YJvQw9TubPG+boLLCkTSHv3KiijGHx/8b6XPnG33uFs MIE9E+XxTxg0A+vMA4PapgTUi+STx/cqbQkPpyMrfyHeCkEUiMo=
=TCdH
-----END PGP SIGNATURE-----
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)