From: Nick Dokos <nicholas.dokos@hp.com>
To: avdi@avdi.org
Cc: nicholas.dokos@hp.com, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Dumbquotes in exported source listings
Date: Sun, 01 May 2011 15:04:50 -0400 [thread overview]
Message-ID: <10967.1304276690@alphaville.americas.hpqcorp.net> (raw)
In-Reply-To: Message from Avdi Grimm <groups@inbox.avdi.org> of "Sat, 30 Apr 2011 19:39:29 EDT." <BANLkTi=p7J2q15feBEEG6Md12sgHDTDRxw@mail.gmail.com>
Avdi Grimm <groups@inbox.avdi.org> wrote:
> So I'm writing an eBook with lots of source code listings, using
> org-mode-LaTeX->PDF with the "minted" package providing source code
> highlighting. For the most part I'm really, really happy with the
> toolchain; thank you to those that pointed me in the direction of
> "minted".
>
> One issue: my beta reviewers have noted that when copy-and-pasting
> source code listings that contain single-quoted strings, they are
> getting "smart quotes"--i.e. the first quote is a backquote, the
> second quote is a single quote. This breaks the pasted code.
>
In cases like this, an example would help: what you start with in the org
file, what it looks like in the tex file (and any other intermediate files[fn:1])
and what the resulting PDF file looks like. FWIW, I tried exporting to PDF
the following:
--8<---------------cut here---------------start------------->8---
* foo
#+begin_src elisp :results value :exports both
(setq foo '(bar baz))
#+end_src
#+results:
| bar | baz |
--8<---------------cut here---------------end--------------->8---
and then, while viewing the PDF file with xpdf, tried pasting the
lisp-expression from the PDF back into the org file (and even evaluated
it). This worked without a hitch.
So please give us more information.
Nick
PS. IIRC, a long time there was a problem like this: trying to copy and paste
a lisp expression from the org manual resulted in an error because of a "wrong"
quote. I couldn't remember the details so I searched the mailing list. The thread
starts at
http://thread.gmane.org/gmane.emacs.orgmode/6610
but a) the warning does not appear in the Org manual any longer and b) I
now cannot reproduce *that* problem at all (not with xpdf, not with
evince and not even with acroread). But it *was* a problem with an older
version of acroread (and, apparently evince as well), so maybe that's
where you should concentrate your investigations: what PDF viewer are you
using and what is the version?
Footnotes:
[fn:1] Don't know anything about minted so this part of the toolchain is
opaque to me: I don't know if it produces other intermediate files.
next prev parent reply other threads:[~2011-05-01 19:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 20:57 Missing Introduction and About sections in LaTeX export Avdi Grimm
[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 ` Nick Dokos [this message]
2011-04-27 22:21 ` Avdi Grimm
2011-04-28 11:06 ` Eric S Fraga
-- strict thread matches above, loose matches on Subject: below --
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
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
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=10967.1304276690@alphaville.americas.hpqcorp.net \
--to=nicholas.dokos@hp.com \
--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).