unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: paul <goodoldpaul@autistici.org>
Cc: 44457-done@debbugs.gnu.org
Subject: bug#44457: [PATCH]: gnu: Add hunspell-dict-it-it.
Date: Sun, 27 Dec 2020 16:17:25 +0100	[thread overview]
Message-ID: <87blefth16.fsf@gnu.org> (raw)
In-Reply-To: <9a6e026f-d5be-883f-f11b-b383ec858ec7@autistici.org> (paul's message of "Wed, 23 Dec 2020 20:15:11 +0100")

Hi,

paul <goodoldpaul@autistici.org> skribis:

> We definitely can but if I understood correctly they are generated
> from STOW wordlists [0] which seems to contain only variants of the
> English language.

Oh right.

> Since also the Libreoffice repository contains some of those variants,
> I was wondering, to achieve better consistency with future
> dictionaries, if it's worth either
>
> - to migrate the duplicates to use (hunspell-dictionary) from (gnu
>   packages hunspell)
>
> - or just to use STOW for the English language and its variants and
>   Libreoffice dictionaries for all the supported languages
>
> I believe either way we should be able to avoid collisions, but maybe
> I should just rename this one dictionary and, after we reach
> consensus, we can always decide to change it back. What do you think?

I think it’s fine this way, I hadn’t realized that the hunspell-dict-*
from aspell.scm were English only.

Now, I just noticed that libreoffice.scm also :-) comes with
huspell-dict-* packages, which are built from yet other sources (primary
sources it seems, rather than LibreOffice).

I’ve applied this patch, but perhaps we should now move those
dictionaries from libreoffice.scm to hunspell.scm?

Thanks!

Ludo’.




  reply	other threads:[~2020-12-27 15:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-05  1:22 [bug#44457] [PATCH]: gnu: Add hunspell-dict-it-it paul
2020-11-05 15:31 ` Jonathan Brielmaier
2020-11-07  1:20 ` paul
2020-12-23 16:29   ` Ludovic Courtès
2020-12-23 19:15     ` paul
2020-12-27 15:17       ` Ludovic Courtès [this message]
2020-11-30 23:28 ` [bug#44457] [PATCH] " paul

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87blefth16.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=44457-done@debbugs.gnu.org \
    --cc=goodoldpaul@autistici.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).