Re: character sets as they relate to “Raw” string literals for elisp

[Eli Zaretskii]

> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Thu, 7 Oct 2021 09:14:47 -0400
> Cc: db48x@db48x.net, yuri.v.khan@gmail.com, emacs-devel@gnu.org, 
>       monnier@iro.umontreal.ca, juri@linkov.net
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> Normally Texinfo represents an em-dash in ASCII output with two
> >> dashes, not just one.  It would be `...from a core dump-–provided
> >> that a core dump...'
> 
> This does not seem to happen in (info "(texinfo) Conventions"):
> 
>     * Use three hyphens in a row, '---', to produce a long dash--like
>       this (called an "em dash"), used for punctuation in sentences.

You mean, you expected to see em dash there?  They deliberately used
@samp{---} to prevent that, because otherwise the text would be
confusing: it talks about typing 3 dashes in the Texinfo sources.  And
texinfo.texi doesn't have "@documentencoding UTF-8" which AFAIR is
required for the generation of non-ASCII characters from these
multiple dashes.

> They use two HYPHEN-MINUS characters to represents an em-dash.

You mean, 3, not 2, right?

> > That has changed, since we nowadays by default use UTF-8 encoding in
> > our Info manuals.  With that, '---' produces the Unicode em-dash
> > character, displayed as a wide dash, and '--' produces a Unicode
> > en-dash character, displayed as somewhat more narrow dash (but still
> > wider than the ASCII dash).
> 
> IMHO, this is a bug that we should look into, as the correct style used
> in the texinfo manual is more readable.  As Juri points out, it is not
> well suited for a monospace font.

What is the bug that you want to fix here?  I'm not sure I understand.

> I guess texinfo would need some way to produce the previous style em
> dashes, while still using utf-8?  Or something?
> 
> Or perhaps we could add some code info.el to add a space on each side of
> an em dash, but that seems like bit of a hack.

I don't really see what needs to be fixed here.  The original Texinfo
source doesn't have the spaces, according to the US English
conventions we use.  And the produced text also doesn't have any
spaces.  So we get back what we asked for, and Texinfo isn't the one
to blame: it just did what we told it to do.

Or what am I missing?