From: Eli Zaretskii <eliz@gnu.org>
To: Robert Boyer <robertstephenboyer@gmail.com>
Cc: ramanahouston@outlook.com, 74469@debbugs.gnu.org
Subject: bug#74469: bug in ispell-buffer
Date: Fri, 22 Nov 2024 13:47:12 +0200 [thread overview]
Message-ID: <86ed33o5hb.fsf@gnu.org> (raw)
In-Reply-To: <CAP9n0TNCFAxv_UZnsZArT7a=rkYWR3G6Gy_EyptffTeOePni=A@mail.gmail.com> (message from Robert Boyer on Fri, 22 Nov 2024 04:17:11 -0600)
> From: Robert Boyer <robertstephenboyer@gmail.com>
> Date: Fri, 22 Nov 2024 04:17:11 -0600
> Cc: 74469@debbugs.gnu.org, rms@gnu.org
>
> Perhaps I can answer a few of your questions, but Emacs, as always, answers the
> most. See far below.
>
> Ispell-breaks on:
>
> ōm namō bhagavatē śrī aruṇācala ramaṇāya
>
> > Breaks how?
>
> Here is the error report I see:
>
> Debugger entered--Lisp error: (error "Ispell misalignment: word ‘nam’ point 122; probabl...")
> error("Ispell misalignment: word `%s' point %d; probably ..." "nam" 122)
> ispell-process-line("^> ōm namō bhagavatē śrī aruṇācala ramaṇāya\n" nil)
> ispell-region(1 5627)
> ispell-buffer()
> funcall-interactively(ispell-buffer)
> command-execute(ispell-buffer record)
> execute-extended-command(nil "ispell-buffer" "ispell-b")
> funcall-interactively(execute-extended-command nil "ispell-buffer" "ispell-b")
> command-execute(execute-extended-command)
>
> > Please tell more details about the problem, so we could investigate it
> > and attempt to fix it whatever needs fixing.
>
> > Specifically, we need to know the following:
>
> > in what language is the above text written?
>
> I am not certain. 'Indian' is a sick response. Perhaps Tamil? Perhaps
> Sanskrit. My Guru, Kumar Saran (ramanahouston@outlook.com) can tell you
> precisely. I have cc'd him on this message.
>
> > What spell-checking program do you use as the back-end for ispell-buffer?
>
> I am as dumb as I rock. I have no idea. I use a Chromebook, I am sure. I get
> ispell with the single Debian Gnu Linux shell command:
>
> sudo apt install ispell
What is the value of ispell-program-name? After you invoke
ispell-buffer for the first time in an Emacs session, type
M-: ispell-program-name RET
and tell what it displays. If it says your spell-checking program is
Ispell, then the above error message is expected: Ispell does not
support languages whose text cannot be encoded in single-byte
encoding, while the text you show needs something like UTF-8 to
encode.
Also, type this:
M-: ispell-current-dictionary RET
and tell what it displays.
Thanks.
next prev parent reply other threads:[~2024-11-22 11:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 5:34 bug#74469: bug in ispell-buffer Robert Boyer
2024-11-22 7:13 ` Eli Zaretskii
2024-11-22 10:17 ` Robert Boyer
2024-11-22 11:47 ` Eli Zaretskii [this message]
2024-11-22 12:08 ` Robert Boyer
2024-11-22 12:14 ` Eli Zaretskii
2024-11-22 12:27 ` Robert Boyer
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86ed33o5hb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74469@debbugs.gnu.org \
--cc=ramanahouston@outlook.com \
--cc=robertstephenboyer@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.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).