From: Lars Ingebrigtsen <larsi@gnus.org>
To: Sebastian Urban <mrsebastianurban@gmail.com>
Cc: 36359@debbugs.gnu.org
Subject: bug#36359: 'sentence-end-base' 3 additional symbols
Date: Tue, 09 Jul 2019 14:17:12 +0200 [thread overview]
Message-ID: <m3k1crxv07.fsf@gnus.org> (raw)
In-Reply-To: <30a6aa9c-c2db-5142-ddad-cc742b27e0ce@gmail.com> (Sebastian Urban's message of "Tue, 9 Jul 2019 11:07:38 +0200")
Sebastian Urban <mrsebastianurban@gmail.com> writes:
>> (...) but do people use > in these circumstances?
>
> Well, I was thinking about writing them in LaTeX documents, where (if
> font encoding is OT4 or T1) you can get '»' by typing '>>'. If this
> is not enough, then skip it, I'll set it manually.
But you end up with » in the buffer, so I don't quite follow how
having > in sentence-end-base is useful...
>> And › I've never seen before -- what language is that used in?
>
> And this is (I think) used for inner quotes, just like '’',
> i.e. « ... ‹ ... › ... ».
Right:
« La Constitution du 3 septembre 1791 proclame la nécessité d'‹ une instruction
publique, commune à tous les citoyens, gratuite à l'égard des parties
d'enseignement indispensables pour tous les hommes ›. »
That example is also interesting because it has the full stop before the
», while I was wondering whether the French did that (or put it after
the »), so I guess that answers that.
So unless anybody objects, I'm adding › and » to the regexp.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-07-09 12:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 16:13 bug#36359: 'sentence-end-base' 3 additional symbols Sebastian Urban
2019-07-09 1:12 ` Lars Ingebrigtsen
2019-07-09 9:07 ` Sebastian Urban
2019-07-09 12:17 ` Lars Ingebrigtsen [this message]
2019-07-09 18:29 ` Sebastian Urban
2019-07-09 19:40 ` Lars Ingebrigtsen
2019-07-10 7:18 ` Sebastian Urban
2019-08-01 13:27 ` Sebastian Urban
2019-08-01 13:29 ` Lars Ingebrigtsen
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=m3k1crxv07.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=36359@debbugs.gnu.org \
--cc=mrsebastianurban@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 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).