From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 70984@debbugs.gnu.org
Subject: bug#70984: 30.0.50; Improved support for entering quotation marks
Date: Thu, 16 May 2024 18:55:10 +0300 [thread overview]
Message-ID: <86cypliwf5.fsf@gnu.org> (raw)
In-Reply-To: <87r0e1j03u.fsf@gmail.com> (message from Robert Pluim on Thu, 16 May 2024 16:35:33 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Date: Thu, 16 May 2024 16:35:33 +0200
>
> * lisp/international/iso-transl.el (iso-transl-char-map): Add entries
> for "low" single and double quotation marks.
> (iso-transl-language-alist): Add convenient support for the official
> German quoting style, which uses "low" double quotes on the left,
> and *left* double quotes on the right. Add support for single
> guillemets to the French language entrey.
^^^^^^
A typo?
> +*** Add 'C-x 8' key translations for "low" quotes "„", and "‚".
This style is for ChangeLog entries, not for NEWS. In NEWS we say
something like "New 'C-x 8' key translations for..." instead.
> +*** "latin-prefix" and "latin-postfix" quotation marks additions.
> +These input methods can now produce single, double and "low" left and
> +right quotation marks:
> +"‘", "’", "“", "”", "„", and "‚"
Why is the last line broken in the middle?
> +*** "latin-prefix" and "latin-postfix" guillemets support.
> +These input methods can now produce single guillemets. For
> +"latin-prefix" use "~~<" and "~~>", for "latin-postfix" use "<~" and
> +">~". Double guillemets were already supported.
Suggest to show the guillemets themselves: not sure everyone knows
what they are.
Are any of these worthy of being mentioned in the user manual (the
"Inserting Text" node)?
next prev parent reply other threads:[~2024-05-16 15:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 14:35 bug#70984: 30.0.50; Improved support for entering quotation marks Robert Pluim
2024-05-16 15:55 ` Eli Zaretskii [this message]
2024-05-17 7:45 ` bug#70984: 30.0.50; Improved support for entering quotation marks, " Robert Pluim
2024-05-17 8:21 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-17 8:59 ` Robert Pluim
2024-05-17 9:59 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-17 12:10 ` Robert Pluim
2024-05-17 12:53 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-17 13:15 ` Robert Pluim
2024-05-17 13:21 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-03 11:33 ` Robert Pluim
2024-05-17 10:44 ` Eli Zaretskii
2024-05-17 12:15 ` Robert Pluim
2024-05-17 13:05 ` Eli Zaretskii
2024-05-17 13:27 ` Robert Pluim
2024-05-17 13:38 ` Eli Zaretskii
2024-05-17 15:41 ` Robert Pluim
2024-05-18 10:57 ` Eli Zaretskii
2024-05-16 16:05 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=86cypliwf5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=70984@debbugs.gnu.org \
--cc=rpluim@gmail.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.