Hi, Jambunathan, Sorry, it took me a long time to get around to this. I pulled your current version this morning. Tested with LibreOffice 3.3.2, Emacs 23.3.1 and Org-mode 7.5 under Mac OS X 10.6.7 this time. You have addressed all my reports, and it's working fine with the test document. However, I have two and a half new issues to report for ODT output (HTML is fine). - The centered paragraph is not centered. - Description lists are now formatted with bulleting (see the enclosed output). Both term and description are bulleted, and in addition, there's an empty bulleted line between them. IIRC, description lists were nicely formatted the last time I tested, so something must have broken. - Radio-target links work perfectly well, but in a slightly different way than I expected (must be clicked like external links, not internal ones; see below). On 4/12/11 10:33 AM, Jambunathan K wrote: > > Christian > > I have fixed most of the issues that you had reported earlier. > > I have added two new features: > > 1. Attaching Custom Styles to the document > - See http://permalink.gmane.org/gmane.emacs.orgmode/40026 I confirm that this works, both with reference to a specific styles.xml and with reference to an .odt document. This is a major advance! > 2. TOC and Outline numbering are done natively. i.e., > Tools->Update->Update All would update TOC index automagically. (This > wasn't the case with earlier exporter) I hadn't tried that before, but I can confirm that it works now. >> * Blocks >> >> There's no syntax highlighting in exported src blocks (ODT and HTML >> both). Not a priority? > > Currently syntax highlighting is done using htmlize. This package is not > part of Emacs proper and has to be installed separately. Since my setup > instructions doesn't include htmlize as part of load path, HTML source > blocks are uncolored. > > As for ODT, fonitification support is missing. I can probably take it up > once my sources gets in to Orgmode proper. I see, thanks. For .odt export, there are probably many cases where black-and-white is preferable anyway. >> The OrgVerse style can, luckily, be changed to something more >> poetic... > > May be if you can share your config for OrgVerse I can include it in the > default styles file. Well, like I said, it's user-changeable anyway, and it's probably not a heavily used feature, so it's no big deal at all. Still, I'd suggest basing the default verse on default paragraph style, not preformatted; dropping the background/borders; and indenting, as with the HTML output. I have done that in the enclosed. ---and while we're at it: Trimming leading spaces from the verse lines would be good. Of course, it could be objected that in much modern verse, layout elements are significant, so it would be better to use a fixed-width font, like you're doing now, and not mess with the whitespace at all. In any case, I'd lose the background and borders. > I have fixed issues with LaTeX: verbatim. I confirm this is fixed. Still don't have dvipng working, so I can't report on that. >> >> Everything shows up in HTML, but linebreaks before the >> =\end{equation}= line are lost. > > In the master branch, the html exporter doesn't seem to be terminating > each line of \begin{equation} ... \end{equation} with
. I see your > POV that including of line breaks will make the output pretty. For now I > have retained the existing behaviour of HTML exporter. OK. >> * Links >> >> The link to =Dedicated Target1= under 8.2.3 does not work when clicked >> (in odt -- it works in html). Hovering does show a popup, >> =.OrgXref.Dedicated-Target1=. All other links work as expected. > > I have fixed this. I confirm that this link is fixed. Radioed target: This works, but in a slightly puzzling way. Unlike the other internal links, simply clicking the link does not take me to the target. On the Mac, I have to CMD-click it, same as when clicking on an external URL. >> >> * Captions, labels, references > (...) > > The caption now has a Colon separator. > >> - However, the reference to that table appears as a hyperlink saying >> "10", and the hyperlink does not appear to work. A cross-reference >> link to "Table 1" would be better. > >> On opening, caption and reference labels include verbatim the >> reference key used in the Org source, which was my main concern last >> time. >> >> But now I realize that this is not an issue after all! =Tools> Update >>> Update all= takes care of automatic renumbering of all >> labels/references. This should probably be mentioned in the >> documentation. > > Tools->Update->Update All (OpenOffice.org) will make sure that all > references to Tables and Images are 'correct'. Yes, this needs to be > mentioned in the manual. > >> Exporting one of my own documents, I also found that: > >> - A space is inserted before *footnote markers*; it shouldn't be. You >> can't see this in the text document, where there is space before all >> footnote references anyway. This is now fixed. >> - Paragraphs were frequently split up, mid-sentence, by unwanted >> paragraph breaks. This bug is a bit of a mystery. The extra >> paragraph breaks appear where there is a newline in the text. But I >> can't discern any pattern as to why breaks are inserted at these >> newlines and not others. Nothing similar happens in HTML export. > > Doest his problem still exists with the new odt exporter. Can you send > me a sample .org file and the generated .odt file. This problem persists. From experimenting a bit, it seems that the *line break before a line containing a footnote* is turned into a paragraph break. I will send a small sample separately. >> Tomorrow, I'll throw a 40-page report at it and see what happens. >> :) > > What happened? It went very well, except that some oversized graphics went badly astray (but that counts as user error) and the problem with paragraph breaks before lines with footnotes. Yours, Christian