From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Latex export bugs and a request Date: Mon, 16 Mar 2009 22:16:48 +0100 Message-ID: <4CCC1BE5-B46F-4A01-AB69-AB1A28F4FF86@uva.nl> References: <87zlflcm6t.fsf@fastmail.fm> Mime-Version: 1.0 (Apple Message framework v930.3) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LjKB6-0004qJ-Iw for emacs-orgmode@gnu.org; Mon, 16 Mar 2009 17:16:56 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LjKB2-0004q7-RW for emacs-orgmode@gnu.org; Mon, 16 Mar 2009 17:16:56 -0400 Received: from [199.232.76.173] (port=55751 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LjKB2-0004q4-Ka for emacs-orgmode@gnu.org; Mon, 16 Mar 2009 17:16:52 -0400 Received: from mail-ew0-f179.google.com ([209.85.219.179]:35070) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LjKB2-0001gj-7K for emacs-orgmode@gnu.org; Mon, 16 Mar 2009 17:16:52 -0400 Received: by ewy27 with SMTP id 27so4890395ewy.42 for ; Mon, 16 Mar 2009 14:16:50 -0700 (PDT) In-Reply-To: <87zlflcm6t.fsf@fastmail.fm> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Matthew Lundin Cc: Org-mode ml Hi Matt, On Mar 16, 2009, at 8:16 PM, Matthew Lundin wrote: > > Hi Carsten, > > I have a three minor LaTeX export bugs to report and a request. > > 1. I a table group begins in the first column of a table, the boundary > is missing in the latex export. > > --8<---------------cut here---------------start------------->8--- > |---+------+----+---------| > | / | < | | > | > | | Here | is | a table | > |---+------+----+---------| > --8<---------------cut here---------------end--------------->8--- > > produces > > ,---- > | \begin{center} > | \begin{tabular}{lll|} > | \hline > | Here & is & a table \\ > | \hline > | \end{tabular} > | \end{center} > `---- > > Note the {lll|} rather than {|lll}. Strange, I am getting {lll}, with no vertical lines on either outside. Ah, you have org-export-latex-tables-column-borders turned on. Yes, there was a bug, fixed now. Thanks! > > 2. Headlines greater than n when H:n (e.g., level three headlines > when H > is set to 2) are exported as description lists. > > Is this the intended behavior? This is how Bastien designed it, and it is similar to the HTML way, turning these into lists. It works fine if there is any text before the plain list bullets. Do you have a better proposal? > > 3. A different issue: html export seems ignores anything inside of > #+begin_latex ... #+end_latex, but the LaTeX exporter does not ignore > the #+begin_html, #+end_html, and #+html directives. > > Would it be possible to have the latex exporter ignore markup > designated as html? I am unable to reproduce this, works fine for me. > > 4. Finally, a request > > Would it be possible to add markup for centered text to org-mode? I've > begun to create documents in org mode for export both to html and > LaTeX. > For now, my workaround is to create macros for centered text that I > comment out depend on how the document is to be exported. But it would > be great if there was something like #+begin_center ... #+end_center. OK, we have now #+begin_center > > ,---- > | #+MACRO: begincenter #+latex: \begin{center} > | #+MACRO: endcenter #+latex: \end{center} > | # #+MACRO: begincenter #+html:
> | # #+MACRO: endcenter #+html:
> `---- > > A related thought (and sorry for the very long email), is there any > way > to define these types of macros globally, rather than in-buffer? It > would be really nice to be able to set commonly used macros globally. > Even nicer would be the ability to define macros that are context > sensitive: i.e., one substitution for for LaTeX export, another > substitution for HTML export. This might make it easier to export the > same source file to different outputs. Just a wishlist item.... Yes, guess we could have global macros, and also macros that expand depending on exporter type. I have not though much about it, maybe you'd like to draw up a syntax? - Carsten