From: tsd@tsdye.com (Thomas S. Dye)
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: LaTeX export, problem with quotes
Date: Thu, 26 Dec 2013 07:57:36 -1000 [thread overview]
Message-ID: <m1fvpfcx67.fsf@tsdye.com> (raw)
In-Reply-To: <87mwjnsfzc.fsf@gmail.com> (Nicolas Goaziou's message of "Thu, 26 Dec 2013 18:02:15 +0100")
Aloha Nicolas,
Ah, I see what's happening now. I've set up asynchronous export to use
the Org mode that ships with Emacs, rather than the one from the git
repo. Of course, that doesn't track your changes.
In this case, where many potential users of my reproducible research
document aren't using the latest Org mode, a file-specific
org-entities-user entry looks like the best solution.
Thanks for your patience as I puzzled this out online.
All the best,
Tom
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> tsd@tsdye.com (Thomas S. Dye) writes:
>
>> I'm getting the same incorrect result as before with:
>>
>> Org-mode version 8.2.4 (release_8.2.4-391-g954168 @
>> /Users/dk/.emacs.d/src/org-mode/lisp/)
>
> Did you reload Org? I cannot reproduce the problem anymore.
>
>>> Nevertheless, there will always be failing cases in smart quote
>>> detection (see `org-export-smart-quotes-regexps').
>>
>> I can't comprehend the regular expression(s) there, unfortunately. If it
>> is the case that there will always be failing cases, and my goal is to
>> create a stable piece of reproducible research, would you recommend an
>> approach that sets org-entities-user appropriately at the file-local
>> level, or something else?
>
> I mean that choosing between an opening quote, a closing quote, or
> nothing is done with a regexp. It cannot cover all cases, and some
> tricky situations will fool smart quote mechanism.
>
> If that happens, and if `org-export-smart-quotes-regexps' cannot be
> improved to handle the situation consistently, you will have to specify
> LaTeX quote code manually (e.g. with an export snippet, or an entity).
>
> I cannot see the link with reproducible research, though.
>
>
> Regards,
--
T.S. Dye & Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com
prev parent reply other threads:[~2013-12-26 17:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-25 17:29 LaTeX export, problem with quotes Thomas S. Dye
2013-12-26 11:45 ` Nicolas Goaziou
2013-12-26 16:49 ` Thomas S. Dye
2013-12-26 17:02 ` Nicolas Goaziou
2013-12-26 17:47 ` Thomas S. Dye
2013-12-26 17:57 ` Thomas S. Dye [this message]
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=m1fvpfcx67.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@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/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).