From: Bart Bunting <bart@ursys.com.au>
To: emacs-orgmode@gnu.org
Subject: LaTeX table export issue
Date: Thu, 22 Jul 2010 21:46:55 +1000 [thread overview]
Message-ID: <87eiev20y8.fsf@bunting.net.au> (raw)
Hi all,
I have found what is possibly a bug in the LaTeX export in org-mode but
I'm not totally sure.
I am no LaTeX expert, in fact I know very little about it. I have used
a process of ilimination to try and produce the simplest case I can to
demonstrate the issue.
What happens is that if I have a table at the top of my document before
a heading line and use the #+ATTR_LaTeX: setting it appears that the
settings used in that #+ATTR_LaTeX: line are then used for all
subsequent tables and other #+ATTR_LaTeX: lines are ignored.
If I add a heading line before the first #+ATTR_LaTeX: line then each
table works as expected.
To demonstrate the issue I have created the small org-mode file below.
Steps to reproduce:
- copy the below text into a .org file.
- remove the "Section One" heading.
- export to pdf.
You will see that the second table inherits the settings from the first.
Next:
- Put the "Section One" heading back.
- Export to pdf again.
You will see that now each table has it's own correct settings.
I hope this makes sense to someone :)
Regards
Bart
--- Sample org file ---
* Section One
#+ATTR_LaTeX: align=|p{50mm}|p{50mm}|
|---+------------------+--------------------------|
| | Reference | 333 |
|---+------------------+--------------------------|
| | Document Name: | wibble |
|---+------------------+--------------------------|
* Section Two
#+ATTR_LaTeX: align=|p{50mm}|p{40mm}|p{30mm}|
|---------------+------------+-----------|
| Plan | Contention | Monthly |
|---------------+------------+-----------|
| 512/256Kbps | 16:1 | $565.00 |
|---------------+------------+-----------|
next reply other threads:[~2010-07-22 11:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 11:46 Bart Bunting [this message]
2010-07-25 16:22 ` LaTeX table export issue David Maus
2010-08-16 12:36 ` Carsten Dominik
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eiev20y8.fsf@bunting.net.au \
--to=bart@ursys.com.au \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.