From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: eggert@cs.ucla.edu, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: master 3fc859d: Go back to iso-2022-7bit for titdic-cnv.el again
Date: Mon, 06 Jan 2020 20:26:53 +0200 [thread overview]
Message-ID: <83a770e902.fsf@gnu.org> (raw)
In-Reply-To: <87r20c78to.fsf@igel.home> (message from Andreas Schwab on Mon, 06 Jan 2020 19:12:35 +0100)
> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, eggert@cs.ucla.edu, emacs-devel@gnu.org
> Date: Mon, 06 Jan 2020 19:12:35 +0100
>
> On Jan 06 2020, Stefan Monnier wrote:
>
> > Agreed. My point was mostly that reverting the encoding to iso-2022 is
> > probably not the best course of action and that other than "uselessly
> > complex code" I couldn't find a concrete problem description that can
> > help decide whether the charset properties are actually relevant.
>
> In the compiled file, the strings lose their charset property, thus the
> reencoding into iso-2022-7bit was a no-op.
Indeed. My idea was to have the call to propertize in the generated
input method. But again, I'm not yet sure this is worth the hassle.
next prev parent reply other threads:[~2020-01-06 18:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200105203051.21185.19313@vcs0.savannah.gnu.org>
[not found] ` <20200105203053.36B932105B@vcs0.savannah.gnu.org>
2020-01-05 20:55 ` master 3fc859d: Go back to iso-2022-7bit for titdic-cnv.el again Stefan Monnier
2020-01-06 17:07 ` Eli Zaretskii
2020-01-06 17:53 ` Stefan Monnier
2020-01-06 18:12 ` Andreas Schwab
2020-01-06 18:21 ` Stefan Monnier
2020-01-06 18:26 ` Eli Zaretskii [this message]
2020-01-06 18:24 ` 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
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=83a770e902.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@linux-m68k.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/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).