From: Eli Zaretskii <eliz@gnu.org>
To: Reuben Thomas <rrt@sc3d.org>
Cc: 28179@debbugs.gnu.org
Subject: bug#28179: Fix use of string-to-multibyte in ispell.el
Date: Tue, 22 Aug 2017 19:38:49 +0300 [thread overview]
Message-ID: <83r2w3a76u.fsf@gnu.org> (raw)
In-Reply-To: <c0831087-d7f3-1001-575d-708ed9ce2d72@sc3d.org> (message from Reuben Thomas on Tue, 22 Aug 2017 01:51:53 +0100)
> From: Reuben Thomas <rrt@sc3d.org>
> Date: Tue, 22 Aug 2017 01:51:53 +0100
>
> ;; Return a string decoded from Nth element of the current dictionary.
> (defun ispell-get-decoded-string (n)
> "Get the decoded string in slot N of the descriptor of the current dict."
> (let* ((slot (or
> (assoc ispell-current-dictionary ispell-local-dictionary-alist)
> (assoc ispell-current-dictionary ispell-dictionary-alist)
> - (error "No data for dictionary \"%s\", neither in `ispell-local-dictionary-alist' nor in `ispell-dictionary-alist'"
> - ispell-current-dictionary)))
> - (str (nth n slot)))
> - (when (and (> (length str) 0)
> - (not (multibyte-string-p str)))
> - (setq str (ispell-decode-string str))
> - (or (multibyte-string-p str)
> - (setq str (string-to-multibyte str))))
Are you sure we don't need to ensure ispell-get-decoded-string always
returns a multibyte string? What if decode-coding-string returns a
pure ASCII string, which is therefore unibyte?
IOW, it looks like you didn't replace the call to string-to-multibyte
with something equivalent, you simply removed that call. If you
analyzed the code and concluded that this call is redundant, please
tell the details of your analysis.
Thanks.
next prev parent reply other threads:[~2017-08-22 16:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 0:51 bug#28179: Fix use of string-to-multibyte in ispell.el Reuben Thomas
2017-08-22 16:38 ` Eli Zaretskii [this message]
2017-08-22 17:04 ` Reuben Thomas
2017-08-22 17:23 ` Eli Zaretskii
2017-08-24 18:52 ` bug#28179: Closing bug: patch is installed Reuben Thomas
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=83r2w3a76u.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28179@debbugs.gnu.org \
--cc=rrt@sc3d.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.