emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: John Rakestraw <lists@johnrakestraw.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: additional bugs in latex export
Date: Tue, 16 Dec 2008 08:41:57 +0100	[thread overview]
Message-ID: <6EC63A39-A2A4-4390-A71C-2FAC13A9B79E@uva.nl> (raw)
In-Reply-To: <20081021223915.2b600344@buster.rakestrawmornlocal>

On Oct 22, 2008, at 4:39 AM, John Rakestraw wrote:

> Hi --
> I'm starting to use latex export more, and noticed three problems
> related to tables:
>  - If the first column in a table has an inactive time stamp, then
>    strange things happen -- in various tests, I've seen only
>    seemingly random cells from a long table exported, or sometimes
>    only the header row (that doesn't have the time stamp in it) and
>    no other rows exported.

At least with the current version I cannot reproduce this - but I
have been fiddling with the Export.  Please try if you still have
this issue, and if yes, make me a test case.

>  - If the text in the first column begins with a left bracket, then
>    the first cell in each row is blank.

Same as above.

>  - If a table is long enough that it should continue on a following
>    page, there's no page break -- instead, lines continue into the
>    bottom margin. What fits on that page prints, but nothing else
>    prints. If I break the table at the bottom of the page with an
>    empty line, the rest of the table continues as expected on the
>    following page.

This is a problem with LaTeX, a special environment is needed
for such tables, and because Org does not know the font and paper
sizes, it cannot automatically switch.

However, you can do now:

#+ATTR_LaTeX: longtable

| a | b | c |
| 1 | 2 | 3 |

which will switch to the long table environment just for this table.

Hope this helps.

- Carsten

      reply	other threads:[~2008-12-16  7:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-22  2:39 additional bugs in latex export John Rakestraw
2008-12-16  7:41 ` Carsten Dominik [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:

  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=6EC63A39-A2A4-4390-A71C-2FAC13A9B79E@uva.nl \
    --to=dominik@science.uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=lists@johnrakestraw.com \


* 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


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).