emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Mark Elston <m_elston@comcast.net>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: org-mode emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Oddity in LaTeX export?
Date: Fri, 01 Jan 2010 21:08:02 -0800	[thread overview]
Message-ID: <4B3ED4B2.10503@comcast.net> (raw)
In-Reply-To: <75A0700F-0DE4-46CC-B930-788C777FE5AE@gmail.com>

Carsten,

This was fixed a week ago or two.  I don't remember the checkin but I
saw it in the log and verified the fix works.

I remember looking at the diffs and it had to do with preprocessing the
TEXT section as well....

Thanks.

Mark

Carsten Dominik wrote:
> Hi,
> 
> Is this already fixed, or still an open issue?
> 
> Thanks.
> 
> - Carsten
> 
> On Dec 13, 2009, at 4:52 PM, Mark Elston wrote:
> 
>> Nick Dokos wrote:
>>> Mark Elston <m_elston@comcast.net> wrote:
>>>> I have a standard format I like to use in creating some class notes
>>>> in latex.  I use memoir and have a boilerplate that only differs
>>>> in the title from notes to notes.  I have decided to try to manage
>>>> my documentation for my notes in org to see if it is easier to do.
>>>> Mostly (so far) it is a pretty good match.
>>>>
>>>> However, I have run into a snag for exporting the notes to latex.
>>>> I tried using the #+TITLE: directive but got page numbers (in roman)
>>>> on the first couple of pages.  This looked ugly.
>>> Can you post the tex file that is produced with the TITLE directive? I
>>> don't understand why/how roman page numbers are produced (but I don't
>>> know memoir well).
>>
>> Actually, part of the boilerplate includes a \pagenumbering{roman}
>> *after* the titlingpage environment.  This is probably what caused it.
>> After all my remaining boilerplate (including a Preface section) I
>> insert a \pagenumbering{arabic} and this restarts the page numbers
>> from 1.
>>
>>>> So I set the#+TITLE: directive to be empty and added to the #+TEXT: 
>>>> block
>>>> the following:
>>>>
>>>> #+TEXT: \title{ABC Class Notes}
>>>> #+TEXT: \begin{titlingpage}
>>>> #+TEXT: \maketitle
>>>> #+TEXT: \end{titlingpage}
>>>>
>>>> This almost works.  The problem is the first of these lines gets
>>>> exported with the closing '}' escaped.  In other words it comes
>>>> out as:
>>>>
>>>> \title{ABC Class Notes\}
>>>>
>>>> I am not sure why this is or what to do about it.
>>> This is probably a bug - Carsten has fixed a number of instances
>>> of such escaped braces I believe.
>>
>> Should I submit a bug report?  As I was working with this another
>> piece of boilerplate I had (and removed) was:
>>
>> #+TEXT: \shorttableofcontents{Sessions}{0}
>>
>> which resulted in:
>>
>> \shorttableofcontents{Sessions}{0\}
>>
>> I don't have to have the short table of contents so I removed it
>> but it is another such escaped backslash.
>>
>>>> BTW, I had to set the TITLE directive to empty since just having it
>>>> resulted in an automatic \maketitle export which was not surrounded
>>>> by the titlingpage environment.  I really wanted that titlingpage
>>>> environment and I couldn't think of another way of  handling it.
>>>>
>>> You can perhaps redefine org-export-latex-title-command:
>>> (setq org-export-latex-title-command 
>>> "\\begin{titlingpage}\n\\maketitle\n\\end{titlingpage}")
>>> and try using the TITLE directive again.
>>
>> Can I set this on a case-by-case basis?  Not all my documents use
>> memoir.  I think the titlingpage environment is memoir-specific.
>>
>> Mark
>>
>>
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Please use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
> 
> - Carsten
> 
> 
> 
> 

      reply	other threads:[~2010-01-02  5:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-13  5:48 Oddity in LaTeX export? Mark Elston
2009-12-13  7:35 ` Nick Dokos
2009-12-13 15:52   ` Mark Elston
2010-01-01 10:34     ` Carsten Dominik
2010-01-02  5:08       ` Mark Elston [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:
  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=4B3ED4B2.10503@comcast.net \
    --to=m_elston@comcast.net \
    --cc=carsten.dominik@gmail.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).