From: "Thomas S. Dye" <tsd@tsdye.com>
To: Rasmus <rasmus.pank@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Questions on LaTeX Exporter
Date: Sat, 5 Mar 2011 13:25:09 -1000 [thread overview]
Message-ID: <80B13489-D629-4DE3-A344-6A74EE38D804@tsdye.com> (raw)
In-Reply-To: <87ei6lpa06.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2427 bytes --]
Aloha Rasmus,
On Mar 5, 2011, at 10:50 AM, Rasmus wrote:
> Hi,
>
> I am trying to move more seriouse text tasks from AUCTeX to Org.
> Mostly
> because it allows me to link to pdf articles, and have * COMMENT in
> the
> same file.
>
This would make you an "early adopter." I haven't been able to solve
all the issues translating from Org-mode to LaTeX yet, but I recently
completed a conference paper without using babel code blocks and it
looks fine. Of course, the paper doesn't have abbreviations that end
with dots ...
> However, I have noticed at least one non-acceptable issue. When using
> using English, LaTeX (via Babel or just default) full-stops (≈double
> space) will be inserted after dots. However, with abbrevation one
> would
> use an ordinary space (i.e.\ an escaped space ("\ ") in LaTeX). Org
> does
> not seem to notice abbrivations—how could it?—and further "\ " is
> interpreted literaly. I need to have an escaped space.
>
> One solution, which would yield much overheat, would be to use babel
> and
> LaTeX fragments. See:
>
> http://repo.or.cz/w/Worg.git/blob_plain/HEAD:/org-contrib/babel/examples/o18.org
>
Yes, and the overhead does get in the way, at least for my writing
projects. Literate programming of prose, which is essentially what
LaTeX code blocks in babel yield, is a bit different than LP for a
software project. In my experience, prose blocks don't require as
much explanation as source code often does, so some of the rationale
for literate programming isn't applicable, and it is very difficult,
at least for me, to stitch together good prose if isn't organized
linearly. A typical paragraph isn't as independent as a well-written
function. I haven't figured out how to write a generic segue.
On the other hand, I think it is the only way currently to get from
Org-mode to perfect LaTeX.
> Also, for fixme notes, I use =[[latex:fixme][insert citation]]= at the
> moment. Does anybody have a nicer solution? For example, having the
> fixme note folded, placed in a footnote or similar?
>
If you figure this one out, please share. I've been over-using the
extensible link syntax. It is great, no doubt about it, but after a
while it feels like I'm working for Org-mode rather than the other way
round.
All the best,
Tom
> --
> Thanks,
> Rasmus
>
>
>
[-- Attachment #2: Type: text/html, Size: 3177 bytes --]
next prev parent reply other threads:[~2011-03-05 23:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-05 20:50 Questions on LaTeX Exporter Rasmus
2011-03-05 23:25 ` Thomas S. Dye [this message]
2011-03-06 13:21 ` Rasmus
2011-03-06 22:39 ` Thomas S. Dye
2011-03-07 9:46 ` Lawrence Mitchell
2011-03-07 11:11 ` Rasmus Pank Roulund
2011-03-07 11:50 ` Eric S Fraga
2011-03-07 12:10 ` Rasmus Pank Roulund
2011-03-07 12:30 ` suvayu ali
2011-03-07 12:49 ` Rasmus Pank Roulund
2011-03-07 13:01 ` Suvayu Ali
2011-03-07 16:30 ` Thomas S. Dye
2011-03-07 9:25 ` Eric S Fraga
2011-03-07 14:00 ` Lawrence Mitchell
2011-03-07 16:18 ` Thomas S. Dye
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=80B13489-D629-4DE3-A344-6A74EE38D804@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus.pank@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).