Neither Emacs nor Vim nor Nano handle ligature literal insertion well

Neither Emacs nor Vim nor Nano handle ligature literal insertion well

[Andrew Pennebaker]

[-- Attachment #1: Type: text/plain, Size: 1908 bytes --]

Hello,

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 am able to work around this limitation in most applications by
configuring TextExpander (macOS, Windows) or autokey (Linux) to match the
keyboard sequence "ae" and replace this with "æ". This allows most UTF-8
compatible graphical software, from Web browsers to document editors, to
correctly insert æ in place of ae. However, traditional text editors
including Emacs, Vim, and Nano are evidently NOT able to handle a literal æ
rune insertion, and tend to raise a generic error message when the text
expander application attempts to insert this key. This may be a result of a
conflict between shell encodings (need UTF-8 everywhere, though I'm
currently typing this with a bare Windows COMSPEC command prompt session).
In any case, it stinks that the user cannot easily insert ligatures into
text editors, so copying & pasting from Wikipedia via the OS clipboard
appears to be one of the more (in)convenient options for accessing
ligatures. We can do better!

-- 
Cheers,
Andrew

-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #2: Type: text/html, Size: 2352 bytes --]

bug#30331: Neither Emacs nor Vim nor Nano handle ligature literal insertion well

[Alan Third]

On Fri, Feb 02, 2018 at 04:31:05PM -0600, Andrew Pennebaker wrote:
> I am able to work around this limitation in most applications by
> configuring TextExpander (macOS, Windows) or autokey (Linux) to match the
> keyboard sequence "ae" and replace this with "æ". This allows most UTF-8
> compatible graphical software, from Web browsers to document editors, to
> correctly insert æ in place of ae. However, traditional text editors
> including Emacs, Vim, and Nano are evidently NOT able to handle a literal æ
> rune insertion, and tend to raise a generic error message when the text
> expander application attempts to insert this key.

I’m not sure about the use of TextExpander as I’ve never heard of it
before, but Emacs on macOS can handle the insertion of æ using alt‐’,
but you might need to change the default binding of the alt key
(https://www.emacswiki.org/emacs/EmacsForMacOS#toc30).

Aside from that Emacs allows you to enter æ using:

    C-x 8 RET LATIN SMALL LETTER AE

It’s a bit of a handful though, I know, but you can enter all sorts of
things:

    ffl fi 🙲

You should be able to configure abbrev-mode to automatically convert
ae to æ. Or maybe prettify symbols mode would do:

    http://www.modernemacs.com/post/prettify-mode/

Proper ligature support is purely a presentation issue, though, and
should happen automatically on software that supports it even if
you’re loading in text written in software that doesn’t.
-- 
Alan Third

bug#30331: Neither Emacs nor Vim nor Nano handle ligature literal insertion well

[Stephen Berman]

On Fri, 2 Feb 2018 23:38:21 +0000 Alan Third <alan@idiocy.org> wrote:

> On Fri, Feb 02, 2018 at 04:31:05PM -0600, Andrew Pennebaker wrote:
>> I am able to work around this limitation in most applications by
>> configuring TextExpander (macOS, Windows) or autokey (Linux) to match the
>> keyboard sequence "ae" and replace this with "æ". This allows most UTF-8
>> compatible graphical software, from Web browsers to document editors, to
>> correctly insert æ in place of ae. However, traditional text editors
>> including Emacs, Vim, and Nano are evidently NOT able to handle a literal æ
>> rune insertion, and tend to raise a generic error message when the text
>> expander application attempts to insert this key.
>
> I’m not sure about the use of TextExpander as I’ve never heard of it
> before, but Emacs on macOS can handle the insertion of æ using alt‐’,
> but you might need to change the default binding of the alt key
> (https://www.emacswiki.org/emacs/EmacsForMacOS#toc30).
>
> Aside from that Emacs allows you to enter æ using:
>
>     C-x 8 RET LATIN SMALL LETTER AE
>
> It’s a bit of a handful though, I know, 

A somewhat smaller handful is `C-x RET e6' (mentioned, as is the above
Unicode name method, in the *Help* you get by typing `C-u C-x =' on the
character æ).

>                                         but you can enter all sorts of
> things:
>
>     ffl fi 🙲
>
> You should be able to configure abbrev-mode to automatically convert
> ae to æ. 

You can also do that by using the norwegian-postfix input method
(entered by typing `C-x RET C-\ no TAB p TAB').

Steve Berman

bug#30331: Neither Emacs nor Vim nor Nano handle ligature literal insertion well

[Eli Zaretskii]

> 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.

Re: Neither Emacs nor Vim nor Nano handle ligature literal insertion well

[Lifepillar]

On 02/02/2018 23:31, Andrew Pennebaker wrote:
> Hello,
> 
> 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 am able to work around this limitation in most applications by 
> configuring TextExpander (macOS, Windows) or autokey (Linux) to match 
> the keyboard sequence "ae" and replace this with "æ". This allows most 
> UTF-8 compatible graphical software, from Web browsers to document 
> editors, to correctly insert æ in place of ae. However, traditional text 
> editors including Emacs, Vim, and Nano are evidently NOT able to handle 
> a literal æ rune insertion, and tend to raise a generic error message 
> when the text expander application attempts to insert this key.

Besides what others have suggested, on macOS I'd recommend Ukelele
(http://scripts.sil.org/ukelele). It allows you to easily define your
own system-wide keyboard layouts. According to the web site: "Ukelele
can assign multiple-character strings and can create "dead keys", where
a keystroke sets a new state that modifies the output of the following
keystroke."

Hope this helps,
Life.

-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

bug#30331: Neither Emacs nor Vim nor Nano handle ligature literal insertion well

[Richard Stallman]

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > However, traditional text editors
  > including Emacs, Vim, and Nano are evidently NOT able to handle a literal æ
  > rune insertion, and tend to raise a generic error message when the text
  > expander application attempts to insert this key.

I'd expect that Quail input methods could handle this for Emacs.  They
notice when you enter a' and convert it to á, so they could notice ae
and convert it to æ.

When you want separate a and e, you'd type another e.



-- 
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
Skype: No way! See https://stallman.org/skype.html.