emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Thomas S. Dye" <tsd@tsdye.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Export latex source blocks as HTML
Date: Mon, 1 Mar 2010 06:19:42 -1000	[thread overview]
Message-ID: <F6457D92-41E9-40D4-A533-D400B579239E@tsdye.com> (raw)
In-Reply-To: <37C769B3-28FC-4789-BB40-E3654E78BA26@gmail.com>


On Feb 28, 2010, at 9:54 PM, Carsten Dominik wrote:

>
> On Feb 28, 2010, at 5:57 PM, Thomas S. Dye wrote:
>
>>
>> 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).
>
> Does that need to be fixed somewhere?
>
> - Carsten
>
Hi Carsten,

I think we should add a footnote to the org-mode publishing section  
that points to the org-babel documentation (which should probably be  
augmented to make explicit the need for the :exports code header  
argument in org-mode publishing).  I'm willing to do these things when  
I find some time, but am wondering about making changes to the org- 
mode manual.  What's the polite way to do this?

All the best,
Tom

  reply	other threads:[~2010-03-01 16:19 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
2010-03-01  7:54     ` Carsten Dominik
2010-03-01 16:19       ` Thomas S. Dye [this message]
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=F6457D92-41E9-40D4-A533-D400B579239E@tsdye.com \
    --to=tsd@tsdye.com \
    --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).