Eric S Fraga <ucec...@ucl.ac.uk> writes: > Nicolas Goaziou <n.goaz...@gmail.com> writes: > >> Hello, >> >>>>>>> Eric S Fraga writes: >> >>> I believe both of these problems are related to the new list >>> handling as I used to be able to export inline tasks perfectly fine >>> in September. >> >> Well, this is strange. I tried to get back to 7.01h, 7.01 and 6.36c >> and I obtain this same behavior. >> >> What kind of export did you use to obtain? >> >> Regards, >> >> -- Nicolas > > Well, now that you ask, I'm not sure what I used to obtain! <blush> I > don't have any PDFs from when I was preparing my big proposal in August > and September other than the final version (which obviously didn't have > any inline tasks in it...). So maybe I've been very unfair to you and > the problem has always existed. Sorry! > > It's still the case that there are two problems. For the first, there's > obviously some leakage from the HTML export into the LaTeX export in > that the list entry (which comes from the inline heading) is given an > argument that seems to be HTML/CSS code... For the second problem, > maybe I've misunderstood the export of a sub-tree -- I've initiated the > export outside the inline heading so the export should include > everything below the heading above? > > I'll play around some more tonight if I get a chance to see if I can > narrow down the reasons for the failure.
I have done so and there's some interesting behaviour. Here is a summary of 4 different results exporting essentially the same content for the attached org file: 1. export the whole file (C-cC-ed) produces a document with all the content but with the inline task defining a latex =\item= with a strange label (as indicated in my earlier message). 2. go to the headline and select the sub-tree (C-c@) and then export (C-cC-ed) generates a PDF with only the text up to the start (but not including) of the inline task. 3. place the cursor on *point 1* and export the sub-tree (C-cC-e1d) generates the same output as the previous point. 4. finally, place the cursor on *point 2* and export the sub-tree (C-cC-e1d) exports only the text *after* the inline task. Basically, for the last three cases, the exporter has a problem figuring out what sub-tree actually is. I don't think the problems have anything to do with the new list handling (apologies again!). I hope this helps somebody figure out what is going on. Thanks, eric
# -*- coding: utf-8; -*- #+TITLE: examplebug.org #+AUTHOR: Eric S Fraga #+EMAIL: e.fr...@ucl.ac.uk #+DESCRIPTION: #+KEYWORDS: #+LANGUAGE: en #+OPTIONS: H:3 num:t toc:nil \n:nil @:t ::t |:t ^:t -:t f:t *:t <:t #+OPTIONS: TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:not-in-toc #+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0 path:http://orgmode.org/org-info.js #+EXPORT_SELECT_TAGS: export #+EXPORT_EXCLUDE_TAGS: noexport #+LINK_UP: #+LINK_HOME: #+XSLT: * problem exporting to latex with inline tasks *point 1* I often use inline tasks to help me organise my thoughts as I am writing long documents. However, exporting these no longer seems to work. ***************************** TODO figure out why this doesn't work ***************************** END *point 2* This is some text the follows the inline task.
-- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 23.2.1 : using Org-mode version 7.02trans (release_7.3.6.gf0d2)
_______________________________________________ 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
