public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Sentences ending with `etc.'
Date: Sat, 11 Nov 2017 15:41:31 -0800	[thread overview]
Message-ID: <20171111234131.GB49916@MacBook-Air-2.local> (raw)
In-Reply-To: <CADAJKhADCA80g_keqHxoYwdeNBVEvuN_eGBGbRpzFvFeM5RRPg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Yes, this is true (though that sounds pretty informal).
Still, I think etc. at the end of the sentence is going to be more
common, so we should make that case work more easily, and
require the escape in the other case.

+++ Melroch [Nov 11 17 09:40 ]:
>   I can easily think of examples where "etc." is neither at the end of a
>   sentence nor followed by a comma, like "Apples etc. should be put in
>   the basket." (Maybe that is not good English? The Swedish equivalent is
>   perfectly OK even though you perhaps would more likely use the likewise
>   abbreviated Swedish calques rather than the Latin "etc.")
>   It seems to me that you have two choices: either you do include "etc."
>   in your abbreviations file and escape the period when it is at the end
>   of a sentence, or you don't include it and escape the following space
>   when it is not at the end of a sentence, but either way those who don't
>   agree with the default can clone the default abbreviations file to
>   `~/.pandoc/abbreviations` and modify it.
>
>   Den 10 nov 2017 05:25 skrev "John MacFarlane" <[1]jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>:
>
>     Good observation.
>     I've just removed etc. from the abbreviations list for
>     this reason.  I think it's usually used either at the
>     end of a sentence or with a following comma.
>     +++ Werner LEMBERG [Nov 09 17 17:04 ]:
>
>     [your pandoc 2.0.1.1 binary for Linux]
>     Suppose the following MarkDown input:
>     ---
>     This sentence is boring, too long, etc.  The next
>     sentence is as boring as the first.
>     ---
>     Calling
>      pandoc-2 -o pandoc-etc.tex [2]pandoc-etc.md
>     converts this to
>     ---
>     This sentence is boring, too long, etc.~The next sentence is as
>     boring
>     as the first.
>     ---
>     As you can see the `etc.' is followed by a protected space.
>     However,
>     in this very case there shouldn't be such a protected space since
>     `etc.' ends a sentence.
>     My question: How can I prevent that pandoc emits the `~' in this
>     situation?
>        Werner
>
>     --
>     You received this message because you are subscribed to the Google
>     Groups "pandoc-discuss" group.
>     To unsubscribe from this group and stop receiving emails from it,
>     send an email to [3]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>     To post to this group, send email to
>     [4]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>     To view this discussion on the web visit
>     [5]https://groups.google.com/d/msgid/pandoc-discuss/20171110042
>     455.GD70590%40MacBook-Air-2.local.
>     For more options, visit [6]https://groups.google.com/d/optout.
>
>   --
>   You received this message because you are subscribed to the Google
>   Groups "pandoc-discuss" group.
>   To unsubscribe from this group and stop receiving emails from it, send
>   an email to [7]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To post to this group, send email to
>   [8]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To view this discussion on the web visit
>   [9]https://groups.google.com/d/msgid/pandoc-discuss/CADAJKhADCA80g_keqH
>   xoYwdeNBVEvuN_eGBGbRpzFvFeM5RRPg%40mail.gmail.com.
>   For more options, visit [10]https://groups.google.com/d/optout.
>
>References
>
>   1. mailto:jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org
>   2. http://pandoc-etc.md/
>   3. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   4. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   5. https://groups.google.com/d/msgid/pandoc-discuss/20171110042455.GD70590-jF64zX8BO091tJRe0FUodcM6rOWSkUom@public.gmane.org
>   6. https://groups.google.com/d/optout
>   7. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   8. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   9. https://groups.google.com/d/msgid/pandoc-discuss/CADAJKhADCA80g_keqHxoYwdeNBVEvuN_eGBGbRpzFvFeM5RRPg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org?utm_medium=email&utm_source=footer
>  10. https://groups.google.com/d/optout


  parent reply	other threads:[~2017-11-11 23:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-09 16:04 Werner LEMBERG
     [not found] ` <20171109.170403.1361446875726483010.wl-mXXj517/zsQ@public.gmane.org>
2017-11-09 16:24   ` Mikolaj Machowski
     [not found]     ` <86d3c91d-485f-4709-bca2-93cbd7afcbcb-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-10  6:10       ` Werner LEMBERG
     [not found]         ` <20171110.071007.1786491178331954318.wl-mXXj517/zsQ@public.gmane.org>
2017-11-10  7:55           ` Mikolaj Machowski
     [not found]             ` <cd5b8895-5cfd-4bf9-878b-6630f6e9214a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-11  3:01               ` John MacFarlane
2017-11-10  4:24   ` John MacFarlane
     [not found]     ` <20171110042455.GD70590-jF64zX8BO091tJRe0FUodcM6rOWSkUom@public.gmane.org>
2017-11-10  5:57       ` Werner LEMBERG
2017-11-11  8:40       ` Melroch
     [not found]         ` <CADAJKhADCA80g_keqHxoYwdeNBVEvuN_eGBGbRpzFvFeM5RRPg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-11 23:41           ` John MacFarlane [this message]
2017-11-12 22:58           ` John Muccigrosso

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=20171111234131.GB49916@MacBook-Air-2.local \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /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.
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 NNTP newsgroup(s).