From: Avdi Grimm <groups@inbox.avdi.org>
To: emacs-orgmode@gnu.org
Subject: Re: Dumbquotes in exported source listings
Date: Sun, 1 May 2011 12:41:15 -0400 [thread overview]
Message-ID: <BANLkTi=U_Q2tQ6rDRdcJBF4P2uVpXfqL-g@mail.gmail.com> (raw)
In-Reply-To: <871v0ji04p.fsf@benfinney.id.au>
On Sat, Apr 30, 2011 at 11:13 PM, Ben Finney > Those aren't even
“smart quotes” (the term usually applied to the quote
> characters from Microsoft's standards-violating character set). Those
> are what might be called “TeX quotes” (though the convention pre-dates
> even TeX), since TeX uses ‘`’ for an opening single quote and ‘``’ for
> an opening double quote.
I'll reiterate: this is in literal code-listing sections, not English
text sections. The listings in the plain org file ARE the correct
single-quote character. Something in the pipeline is "cleverly"
converting them to "TeX-quotes", and I don't know what.
--
Avdi Grimm
http://avdi.org
next prev parent reply other threads:[~2011-05-01 16:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-30 23:39 Dumbquotes in exported source listings Avdi Grimm
2011-05-01 3:13 ` Ben Finney
2011-05-01 16:41 ` Avdi Grimm [this message]
2011-05-01 19:08 ` Nick Dokos
2011-05-01 20:26 ` Sébastien Vauban
2011-05-01 21:31 ` Nick Dokos
2011-05-01 21:40 ` Ben Finney
2011-05-01 21:27 ` Ben Finney
-- strict thread matches above, loose matches on Subject: below --
2011-04-27 20:57 Missing Introduction and About sections in LaTeX export Avdi Grimm
2011-04-27 22:21 ` Avdi Grimm
2011-04-28 11:06 ` Eric S Fraga
[not found] ` <groups@inbox.avdi.org>
2011-04-27 21:41 ` Nick Dokos
2011-04-27 21:47 ` Avdi Grimm
2011-04-27 22:23 ` Nick Dokos
2011-04-28 7:55 ` Sébastien Vauban
2011-04-28 11:36 ` Nick Dokos
2011-05-01 19:04 ` Dumbquotes in exported source listings Nick Dokos
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTi=U_Q2tQ6rDRdcJBF4P2uVpXfqL-g@mail.gmail.com' \
--to=groups@inbox.avdi.org \
--cc=avdi@avdi.org \
--cc=emacs-orgmode@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).