emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Srinivas Pavani <sp_us@yahoo.com>
To: emacs-orgmode@gnu.org
Subject: org-article & #+INCLUDE LaTex support
Date: Fri, 19 Nov 2010 18:08:31 +0000 (UTC)	[thread overview]
Message-ID: <loom.20101119T185451-59@post.gmane.org> (raw)

Tom,

I have been trying to use the org-article LaTEX setup to get consistent look 
and feel across my documents. 

I found out that if you insert the following lines directly in a file 
(test.org), the desired output is produced. However if you insert the lines in 
an #+INCLUDE file, then the outcome is different. The settings of org-article 
are ignored.


Test case 1:

File: test.org

#+OPTIONS: H:3
#+LaTeX_CLASS: org-article
#+LaTeX_CLASS_OPTIONS: 
[koma,letterpaper,captions=tableheading,utopia,11pt,listings-
sv,microtype,paralist,colorlinks=true,urlcolor=blue,secnums]
#+LATEX_HEADER: \usepackage[AUTO]{inputenc}

* Sample Heading1
** Sample Heading2
*** Sample Heading3
Content goes here

----------------------------

Test case 2:
File: test.org

#+include: boiler.org
#+OPTIONS: H:3

* Sample Heading1
** Sample Heading2
*** Sample Heading3

Content goes here


File: boiler.org
#+OPTIONS: H:2
#+LaTeX_CLASS: org-article
#+LaTeX_CLASS_OPTIONS: 
[koma,letterpaper,captions=tableheading,utopia,11pt,listings-
sv,microtype,paralist,colorlinks=true,urlcolor=blue,secnums]
#+LATEX_HEADER: \usepackage[AUTO]{inputenc}

It seems that when files are included, the contents of the included file are 
not evaluated consistently. This seems like it is more of an issue with org-
mode and interpreting include file contents.

- Srinivas

             reply	other threads:[~2010-11-19 18:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-19 18:08 Srinivas Pavani [this message]
2010-11-19 18:43 ` org-article & #+INCLUDE LaTex support 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=loom.20101119T185451-59@post.gmane.org \
    --to=sp_us@yahoo.com \
    --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).