From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Pennebaker <andrew.pennebaker@gmail.com>
Cc: vim_use@googlegroups.com, help-nano@gnu.org, 30331@debbugs.gnu.org
Subject: bug#30331: Neither Emacs nor Vim nor Nano handle ligature literal insertion well
Date: Sat, 03 Feb 2018 10:45:12 +0200 [thread overview]
Message-ID: <83lggabgx3.fsf@gnu.org> (raw)
In-Reply-To: <CAHXt_SV2P_ieU+UNHx8QoGX9CfoT38BoO01u9Er4dVqqm2Bxyw@mail.gmail.com> (message from Andrew Pennebaker on Fri, 2 Feb 2018 16:31:05 -0600)
> From: Andrew Pennebaker <andrew.pennebaker@gmail.com>
> Date: Fri, 2 Feb 2018 16:31:05 -0600
>
> I would really like convenient access to ligatures in my word processing software. Unfortunately, none of the
> major text editing applications appears to handle ligatures intelligently: Each of Emacs, Vim, Nano, MS Word,
> Google Drive, Libre Office, and InDesign type a dumb "ae" when the user presses the a and e keyboard keys,
> whereas historically this sequence is typically rendered with the ash æ rune.
I don't see how any text-based application could do that
automatically, since there are many cases where "ae" needs to be left
as literal 2 characters. Just a few random examples:
maestro
Rafael
(Joan) Baez
I think the right thing would be to have a special key sequence for
inserting ligatures, since the need for that is somewhat rare,
certainly more rare than the need to insert the characters literally.
next prev parent reply other threads:[~2018-02-03 8:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 22:31 Neither Emacs nor Vim nor Nano handle ligature literal insertion well Andrew Pennebaker
2018-02-02 23:38 ` bug#30331: " Alan Third
2018-02-02 23:58 ` Stephen Berman
2018-02-03 8:45 ` Eli Zaretskii [this message]
2018-02-03 9:56 ` Lifepillar
2018-02-03 19:13 ` bug#30331: " Richard Stallman
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=83lggabgx3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=30331@debbugs.gnu.org \
--cc=andrew.pennebaker@gmail.com \
--cc=help-nano@gnu.org \
--cc=vim_use@googlegroups.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 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.