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

Re: Bug#1020387: dictionaries-common: Consensus regarding the packaging of the Qt WebEngine hunspell binary dictionaries



On Fri, Oct 14, 2022 at 02:58:17PM -0400, Andres Salomon wrote:
> In my opinion, chromium's (, or QT's, or whoever's) bdic support should be
> merged upstream into hunspell, and hunspell should be shipping bdic files in
> /usr/share/hunspell alongside the .aff and .dic files. I don't know how
> active hunspell upstream is, though, and how amenable they'd be to patches.
> I see at least one person created an hunspell-with-bdic-support fork a
> decade ago: https://github.com/sheremetyev/hunspell
> 
> That would allow chromium and other hunspell users to link against a system
> hunspell when desired, dropping all the bdict versioning stuff and the
> custom paths. I'm pretty sure I could get a patch to link against system
> hunspell into chromium upstream, provided bdic support made it into upstream
> hunspell.
> 
> I wouldn't want to see debian carrying bdic patches in its hunspell package,
> though; nor would I want to see the security team needing to deal with a
> hunspell fork package.

I think you are the first to mention "integrating" bdic into hunspell
itself, and to mention that effectively the parser is based on hunspell
itself…

From what I know, the hunspell project is basically in maintenance mode,
with nobody actively doing anything to it.  Pretty much all changes in
the past years were done by drive-by contributors.

This is to say, I can't deny that somebody proposing MRs upstream might
actually see them merged.

> >   5) something else
> >   (The order mentions my personal preference)
> > - Is there some commandline client for auto-testing the bdic files?
> > - How to reuse the bdic files with chromium?
> > - 3 bugs in qwebengine_convert_dict reported by Soren Stoutner
> 
> 
> I just took a peek at qtwebengine-opensource-src-5.15.10+dfsg, and I see
> that they're using the exact same hunspell fork from chromium.  :(

Not surprising since afaik qtwebengine is basically a fork of chromium
itself...

-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
More about me:  https://mapreri.org                             : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

Attachment: signature.asc
Description: PGP signature


Reply to: