From: Martin Kletzander <mk@linux.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 25830@debbugs.gnu.org
Subject: bug#25830: 25.2; ispell doesn't parse hunspell dictionaries properly
Date: Wed, 22 Feb 2017 17:43:10 +0100 [thread overview]
Message-ID: <20170222164310.GA3470@wheatley> (raw)
In-Reply-To: <83d1eatcxo.fsf@gnu.org>
On Wed, Feb 22, 2017 at 06:20:19PM +0200, Eli Zaretskii wrote:
>> Date: Wed, 22 Feb 2017 11:40:25 +0100
>> From: Martin Kletzander <mk@linux.com>
>> Cc: 25830@debbugs.gnu.org
>>
>> $ locale
>> LANG=en_GB.utf8
>> LC_CTYPE=en_GB.utf8
>> LC_NUMERIC="en_GB.utf8"
>> LC_TIME="en_GB.utf8"
>> LC_COLLATE="en_GB.utf8"
>> LC_MONETARY="en_GB.utf8"
>> LC_MESSAGES="en_GB.utf8"
>> LC_PAPER="en_GB.utf8"
>> LC_NAME="en_GB.utf8"
>> LC_ADDRESS="en_GB.utf8"
>> LC_TELEPHONE="en_GB.utf8"
>> LC_MEASUREMENT="en_GB.utf8"
>> LC_IDENTIFICATION="en_GB.utf8"
>> LC_ALL=
>>
>> Honestly, I don't know where it takes the cs_CZ from, *but* if it
>> didn't, I would have to modify it so that it does. Simply because
>> that's what I want it to do by default.
>
>Interesting. What version of Hunspell is that?
1.6.0
next prev parent reply other threads:[~2017-02-22 16:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 9:18 bug#25830: 25.2; ispell doesn't parse hunspell dictionaries properly Martin Kletzander
2017-02-21 17:23 ` Eli Zaretskii
2017-02-21 20:24 ` Martin Kletzander
2017-02-21 20:44 ` Eli Zaretskii
2017-02-22 10:40 ` Martin Kletzander
2017-02-22 16:20 ` Eli Zaretskii
2017-02-22 16:43 ` Martin Kletzander [this message]
2017-02-25 8:24 ` Eli Zaretskii
2017-02-25 12:15 ` Martin Kletzander
2017-02-25 12:41 ` Eli Zaretskii
2017-02-25 13:10 ` Martin Kletzander
2017-02-27 15:54 ` Eli Zaretskii
2017-02-28 21:53 ` Martin Kletzander
2017-03-05 15:42 ` Eli Zaretskii
2017-03-07 16:51 ` Eli Zaretskii
2017-03-25 16:13 ` Eli Zaretskii
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=20170222164310.GA3470@wheatley \
--to=mk@linux.com \
--cc=25830@debbugs.gnu.org \
--cc=eliz@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.