public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Pander <pander@users.sourceforge.net>
To: Marco Atzeri <marco.atzeri@gmail.com>, cygwin@cygwin.com
Subject: Re: How to make a package request
Date: Sat, 4 Apr 2020 13:39:37 +0200	[thread overview]
Message-ID: <3e5c9702-4470-6c6a-53fb-04f592e2b049@users.sourceforge.net> (raw)
In-Reply-To: <8a20030f-6785-f840-6666-3e1c2af23ebe@gmail.com>


On 4/4/20 3:55 AM, Marco Atzeri via Cygwin wrote:
> Am 03.04.2020 um 22:08 schrieb Pander via Cygwin:
>> Hi all,
>>
>> How can I make a package request for Nuspell?
>>
>> Nuspell is a spell checking library and command-line tool written in
>> modern C++, see https://nuspell.github.io/ and
>> https://github.com/nuspell/nuspell/wiki/Nuspell-packaged-binaries
>>
>> Thanks,
>>
>> Pander
>>
>
> Are you offering yourself as maintainer ?
> https://cygwin.com/packaging-contributors-guide.html

Tempting but no, I already maintain packages for several platforms. See
https://github.com/nuspell/misc-nuspell/tree/master/packaging The files
there will help packaging for cygwin.

Packaging Nuspell is similar to Hunspell, but more easy as Nuspell uses
CMake. Recently, Enchant is supporting Nuspell and now I am working on
the integration with Firefox. With the support of Mozilla, we try to be
a drop-in replacement for Hunspell and to have better performance and
maintanability.

>
>
> currently we have already aspell and hunspell
> as general purpose spell checkers

The functionality of Aspell is very inferior to that of Hunspell and
Nuspell. Hunspell is very hard to maintain and extend and sometimes has
security issues as it has been written in an older form of C++. If you
are interested, here is more on the subject:

https://archive.fosdem.org/2016/schedule/event/integrating_spell_and_grammar_checking/

https://archive.fosdem.org/2019/schedule/event/nuspell/

https://fosdem.org/2020/schedule/event/clc_nuspell_version_3_of_the_new_spell_checker/

Best,

Pander

>
> Regards
> Marco
>
> -- 
> Problem reports:      https://cygwin.com/problems.html
> FAQ:                  https://cygwin.com/faq/
> Documentation:        https://cygwin.com/docs.html
> Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2020-04-04 11:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03 20:08 Pander
2020-04-04  1:55 ` Marco Atzeri
2020-04-04 11:39   ` Pander [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3e5c9702-4470-6c6a-53fb-04f592e2b049@users.sourceforge.net \
    --to=pander@users.sourceforge.net \
    --cc=cygwin@cygwin.com \
    --cc=marco.atzeri@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).