emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Thomas S. Dye" <tsd@tsdye.com>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode@gnu.org
Subject: Re: Export latex source blocks as HTML
Date: Sun, 28 Feb 2010 06:57:40 -1000	[thread overview]
Message-ID: <72D73972-320C-4093-A603-6CCE2E9831E6@tsdye.com> (raw)
In-Reply-To: <6457.1267332445@gamaville.dokosmarshall.org>


On Feb 27, 2010, at 6:47 PM, Nick Dokos wrote:

> Thomas S. Dye <tsd@tsdye.com> wrote:
>
>> Aloha all,
>>
>> Exporting this file to html gives me a source code block for bibtex  
>> but not for latex.
>>
>> * Test export
>> #+BEGIN_SRC latex
>>  No export with latex
>> #+END_SRC
>>
>> #+BEGIN_SRC bibtex
>>  Export OK with bibtex
>> #+END_SRC
>>
>> Does anyone else see this?  Any idea what I might have messed up?   
>> Files that used to export perfectly have all lost their latex  
>> source code blocks in
>> HTML output.
>>
>
> Tom,
>
> I just put the above in a file and exported it to html. I get the
> attached html file (which, afaict, contains both latex and bibtex src
> blocks, in contrast to what you get). This is with Org-mode version
> 6.34trans (release_6.34c.103.g8625e).
>
> HTH,
> Nick
>
> <tomdye.org><tomdye.html>

Thanks Nick,

My results are due to org-babel.  The recently augmented support for  
LaTeX sets the default to :exports results, when the org-mode  
publishing process wants :exports code.  I was aware of the change but  
not prepared to understand all its ramifications.

All the best,
Tom

  parent reply	other threads:[~2010-02-28 16:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-27  3:07 Export latex source blocks as HTML Thomas S. Dye
     [not found] ` <6457.1267332445@gamaville.dokosmarshall.org>
2010-02-28 16:57   ` Thomas S. Dye [this message]
2010-03-01  7:54     ` Carsten Dominik
2010-03-01 16:19       ` Thomas S. Dye
2010-03-01 17:14         ` 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

  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=72D73972-320C-4093-A603-6CCE2E9831E6@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicholas.dokos@hp.com \
    /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).