Re: [O] ODT export --> opening in Okular?

On Tue, 11 Dec 2018 01:00:15 +0800 wrote > Check your ~/.mailcap and/or /etc/mailcap file as well: there are indeed > many twisty passages through org-open-file, so you may end up calling > whatever the system has set up (correctly or not). > Nick Aha, that was the answer.

Re: [O] ODT export --> opening in Okular?

James Harkins writes: > ... > As a final test, I deleted both the PDF and ODT entries from > org-file-apps -- so that there is absolutely no reference in any org > code file or variable to okular -- and it is *still* opening the > exported ODT in okular! Which strikes me as insane. > >

Re: [O] ODT export --> opening in Okular?

On Sunday, 9 Dec 2018 at 18:20, Ken Mankoff wrote: > On 2018-12-09 at 17:45 -0800, James Harkins wrote: >> Anyway, the solution for now, as I'm under some time pressure, is to >> declare that ODT export is broken on my system until I can scrape >> together some time to upgrade org. PDF export is

Re: [O] ODT export --> opening in Okular?

On 2018-12-09 at 17:45 -0800, James Harkins wrote: > Anyway, the solution for now, as I'm under some time pressure, is to > declare that ODT export is broken on my system until I can scrape > together some time to upgrade org. PDF export is actually OK for now > (and working fine). But export

Re: [O] ODT export --> opening in Okular?

On Mon, 10 Dec 2018 07:25:13 +0800 briangpowell wrote > * Suggest you try changing this: > > ("\\.odt\\'" . "libreoffice6.0 %s" > * To this instead: > > ("\\.odt\\'" . "libreoffice %s" > --since "libreoffice6.0" is a specific link that is subject to change--not > only by

Re: [O] ODT export --> opening in Okular?

* Suggest you try changing this: ("\\.odt\\'" . "libreoffice6.0 %s" * To this instead: ("\\.odt\\'" . "libreoffice %s" --since "libreoffice6.0" is a specific link that is subject to change--not only by you but by your chosen operating system package manager Unless of course, you

[O] ODT export --> opening in Okular?

Hi, I realize I'm running an older version of org-mode (8.3.3), but things are working for me generally and I'm not in a position to monkey around with my environment right now. Anyway, something strange. A few months ago, I was able to export to ODT and the file would open in LibreOffice.

[O] ODT export with #+NAME'd equation is failing

Hi List, I'm trying to export a document to ODT and it fails if the following two lines included: #+NAME: eq:foo See Equation [[eq:foo]]. If I comment out one or the other it works. I can re-create this using the latest Org and the following MWE: 1) Contents of DEBUG.el. are: (add-to-list

[O] ODT export of SVG image, wrong size properties

Hi, I am exporting a document to ODT, including a small SVG image. #+name: Notation1 #+caption: Transcription into Western notation of an example pattern string. #+attr_odt: :width 6.88 :height 1.87 [[./notated-example.svg]] The frame properties, however, do not respect the given size

Re: [O] ODT export

Hi Philip, Philip Hudson writes: > First time out, very disappointing and confusing results. Did you try the ODT exporter again with better results? -- Bastien

Re: [O] ODT export

On Wednesday, 12 Oct 2016 at 08:59, Christian Moe wrote: > I've never know this to fail as such. I did have a problem for a while Not sure if this is relevant but just in case... I had problems with ODT export for quite some time with the default style. I finally tracked it down to having some

Re: [O] ODT export

Haven't done this in a while, but I just tested, and ODT custom style files work fine for me under Org 8.3.4. (Note: I haven't pulled the latest Org changes; waiting for another package to catch up.) I've never know this to fail as such. I did have a problem for a while using .odt files as

Re: [O] ODT export

Hi Philip. >> First time out, very disappointing and confusing results. >> Having created a styled example.odt file as per instructions in the manual... >> [...] >> (info "(org) Applying custom styles") > Sanity check: anyone able to confirm they've done this successfully? I did it, but a looong

Re: [O] ODT export

On 8 October 2016 at 09:10, Philip Hudson wrote: > First time out, very disappointing and confusing results. > > Having created a styled example.odt file as per instructions in the manual... > > (info "(org) Applying custom styles") Sanity check: anyone able to confirm

[O] ODT export

First time out, very disappointing and confusing results. Having created a styled example.odt file as per instructions in the manual... (info "(org) Applying custom styles") (BTW, the string "Stylist" does not appear anywhere in LibreOffice's UI; there's more than enough difficulty here without

[O] [odt-export] Setting Text Colour for odt export

Hi I am using --8<---cut here---start->8--- \color{red} some red text \color{black} and we continue with black --8<---cut here---end--->8--- to set the text colour for sections in my document for LaTeX export, but this

Re: [O] [odt-export] Setting Text Colour for odt export

Rasmus writes: > Hi, > > Rainer M Krug writes: > >> I am using >> >> \color{red} some red text \color{black} and we continue with black >> >> to set the text colour for sections in my document for LaTeX export, but >> this does obviously does not org for odt

Re: [O] [odt-export] Setting Text Colour for odt export

Hi, Rainer M Krug writes: > I am using > > \color{red} some red text \color{black} and we continue with black > > to set the text colour for sections in my document for LaTeX export, but > this does obviously does not org for odt export. > > What can I use to achieve the same

Re: [O] ODT export backend missing

Hi Jorge. >> The export dispatcher does not show ODT. I see no errors in the >> messages buffer, and Emacs does not print any error to the terminal. > I discovered command org-odt-export-to-odt and called it directly. Worked. > Should have thought of it before. Sorry. While true and not a

[O] ODT export backend missing

The export dispatcher does not show ODT. I see no errors in the messages buffer, and Emacs does not print any error to the terminal. This is Ubuntu 15.04, Emacs 24.5 (compiled myself). I have tested with recent Org (from package.el) and with stock Org. I have in fact tested with stock emacs

Re: [O] ODT export backend missing

On Thu, Sep 10, 2015 at 5:48 PM, Jorge wrote: > The export dispatcher does not show ODT. I see no errors in the > messages buffer, and Emacs does not print any error to the terminal. I discovered command org-odt-export-to-odt and called it directly. Worked. Should have

Re: [O] ODT export backend missing

Jorge writes: > The export dispatcher does not show ODT. I see no errors in the > messages buffer, and Emacs does not print any error to the terminal. > > This is Ubuntu 15.04, Emacs 24.5 (compiled myself). I have tested > with recent Org (from package.el) and with stock

Re: [O] ODT export: Issues with `org-export-footnote-first-reference-p'

Hello, Christian Moe m...@christianmoe.com writes: Would it make sense to be able to link to a footnote label? Rationale: 1. If a footnote definition is already meaningfully labeled, a dedicated target is redundant. 2. Since you can link to named tables, source blocks etc., users might

Re: [O] ODT export: Issues with `org-export-footnote-first-reference-p'

Vaidheeswaran C vaidheeswaran.chinnar...@gmail.com writes: Allow me to revisit this thread in a week or 10 days so that I can 1. take a look at ODF standard. 2. dig in to LibreOffice discussion lists to see whether such instances have ever surfaced (and how they were dealt with). Until

Re: [O] ODT export: Issues with `org-export-footnote-first-reference-p'

Vaidheeswaran vaidheeswaran.chinnar...@gmail.com writes: What changes need to be made in ox.el and/or ox-odt.el so that the snippet I shared produces the right XML acceptable for LibreOffice. text1 [fn:1] text2 [fn:2] [fn:1] footdef1[fn:2] [fn:2] footdef2 For purposes of ODT backend,

Re: [O] ODT export: Issues with `org-export-footnote-first-reference-p'

Allow me to revisit this thread in a week or 10 days so that I can 1. take a look at ODF standard. 2. dig in to LibreOffice discussion lists to see whether such instances have ever surfaced (and how they were dealt with). Until then, please keep the patch in waiting. On Friday 13

Re: [O] ODT export: Issues with `org-export-footnote-first-reference-p'

Aloha Vaidheeswaran, Thanks very much for the detailed response and the link to the book. That's an interesting example I won't soon forget. The forward reference in the footnote is unusual. In this case it appears to be standing in for the lack of an index entry for either trichiliocosm or

Re: [O] ODT export: Issues with `org-export-footnote-first-reference-p'

Vaidheeswaran C vaidheeswaran.chinnar...@gmail.com writes: I still think that the snippet I shared should have worked. Clearly `org-export-footnote-first-reference-p' is misbehaving. It does, e.g., when exporting to LaTeX. This is an odt limitation. So, I disagree,

Re: [O] ODT export: Issues with `org-export-footnote-first-reference-p'

On Thursday 12 February 2015 02:42 AM, Nicolas Goaziou wrote: It does, e.g., when exporting to LaTeX. This is an odt limitation. So, I disagree, `org-export-footnote-first-reference-p' is correct here. Let me put my question this way: What changes need to be made in ox.el and/or ox-odt.el

Re: [O] ODT export: Issues with `org-export-footnote-first-reference-p'

On Thursday 12 February 2015 12:49 PM, Thomas S. Dye wrote: Aloha Vaidheeswaran, This is an odd example that I don't recall having seen in any publication. I don't doubt examples might exist, but don't remember having seen one. Can you point me to a real-world example of a footnote referring

Re: [O] ODT export: Issues with `org-export-footnote-first-reference-p'

Aloha Vaidheeswaran, This is an odd example that I don't recall having seen in any publication. I don't doubt examples might exist, but don't remember having seen one. Can you point me to a real-world example of a footnote referring to a subsequent footnote that I might reference either on-line

Re: [O] ODT export: Issues with `org-export-footnote-first-reference-p'

On Tuesday 10 February 2015 06:26 PM, Christian Moe wrote: Thanks for this. You have [fn:1] footdef1[fn:2] [fn:2] footdef2 What do you expect to see in ODT? Presumably not a footnote in a footnote, since LibreOffice doesn't allow you to place one. An ODT cross-reference to the

[O] ODT export: Issues with `org-export-footnote-first-reference-p'

The attached file, when exported to ODT fails to open in LibreOffice exporter. The reason failure is that the exported __XML__ file has nested footnote definiton i.e., a footnote definition within a footnote definiton. In concrete terms, there is some confusion wrt the return value of

Re: [O] ODT export: Issues with `org-export-footnote-first-reference-p'

Hello, Vaidheeswaran C vaidheeswaran.chinnar...@gmail.com writes: That said, it is difficult for me to conceive of a footnote that is referenced solely by other footnotes. i.e., it is reasonable to assume that a given footnote is either not referenced at all or is referenced atleast once in

Re: [O] ODT export: Issues with `org-export-footnote-first-reference-p'

Hello, Christian Moe m...@christianmoe.com writes: An ODT cross-reference to the footnote? That makes sense, but should that be achieved by footnoting inside a footnote, or is the appropriate thing to do to use a dedicated target and link? [fn:1] footdef1, see also [[thatotherfootnote]].

Re: [O] ODT export: Issues with `org-export-footnote-first-reference-p'

On Wednesday 11 February 2015 11:32 AM, Vaidheeswaran wrote: This should be fixed. Thank you. Not yet. See attached files. Operator error. Sorry.

Re: [O] ODT export: Issues with `org-export-footnote-first-reference-p'

On Wednesday 11 February 2015 02:59 AM, Nicolas Goaziou wrote: Hello, Vaidheeswaran Cvaidheeswaran.chinnar...@gmail.com writes: That said, it is difficult for me to conceive of a footnote that is referenced solely by other footnotes. i.e., it is reasonable to assume that a given footnote is

Re: [O] ODT export: Issues with `org-export-footnote-first-reference-p'

On Wednesday 11 February 2015 02:58 AM, Nicolas Goaziou wrote: Hello, Christian Moem...@christianmoe.com writes: An ODT cross-reference to the footnote? That makes sense, but should that be achieved by footnoting inside a footnote, or is the appropriate thing to do to use a dedicated target

Re: [O] ODT export: Issues with `org-export-footnote-first-reference-p'

Hi, Thanks for this. You have [fn:1] footdef1[fn:2] [fn:2] footdef2 What do you expect to see in ODT? Presumably not a footnote in a footnote, since LibreOffice doesn't allow you to place one. An ODT cross-reference to the footnote? That makes sense, but should that be achieved by

Re: [O] odt export of subtree: set/suppress the date in the export

CM m...@christianmoe.com: I cannot reproduce either problem, though I seem to remember some difficulty with changing date fields in the past. What Org version are you using? Um... a heap of different versions it looks like, on the systems I use regularily, some from ELPA (one of the ELPA

Re: [O] odt export of subtree: set/suppress the date in the export

Christian Moe m...@christianmoe.com: Does setting the subtree's :EXPORT_DATE: property to the date of the meeting do what you're looking for? Nope. Still outputs the date of the export. And since writing the posting I've discovered another annoying property of the date: it will switch to

Re: [O] odt export of subtree: set/suppress the date in the export

I cannot reproduce either problem, though I seem to remember some difficulty with changing date fields in the past. What Org version are you using? You can turn the use of date fields in LibreOffice on or off with org-odt-use-date-fields. With date fields set to t: - Setting :EXPORT_DATE: in

[O] odt export of subtree: set/suppress the date in the export

Emacs version: GNU Emacs 24.3.1 (i386-mingw-nt6.1.7601) of 2013-03-17 on MARVIN Org version: Org-mode version 7.9.3f (release_7.9.3f-17-g7524ef @ c:/ProgramFiles/emacs-24.3/lisp/org/) I use org to take notes in meetings. When I make an ODT export of the subtree for the meeting minutes, I

Re: [O] odt export of subtree: set/suppress the date in the export

Hi, Does setting the subtree's :EXPORT_DATE: property to the date of the meeting do what you're looking for? Yours, Christian Steinar Bang writes: Emacs version: GNU Emacs 24.3.1 (i386-mingw-nt6.1.7601) of 2013-03-17 on MARVIN Org version: Org-mode version 7.9.3f

Re: [O] ODT export displays incorrect title and author in libreoffice

On Wednesday, 22 Oct 2014 at 23:56, Rasmus wrote: Won't you pick up Org shipped with Emacs with emacs -Q? yes I would but I set the load path before I load org so I pick up the new version. Maybe you can reset it by: mv ~/.config/libreoffice{,.bak} Thanks. I'll try this. -- : Eric S

[O] ODT export displays incorrect title and author in libreoffice

Hi, I am not sure if my problem is with org or with libreoffice; most likely, the combination of the two! In any case, when I export to ODT, the title and author fields do not appear as they should, instead displaying DocInformation:Title and DocInformation:Created. See attached screenshot.

Re: [O] ODT export displays incorrect title and author in libreoffice

Hi Eric, Eric S Fraga e.fr...@ucl.ac.uk writes: I am not sure if my problem is with org or with libreoffice; most likely, the combination of the two! In any case, when I export to ODT, the title and author fields do not appear as they should, instead displaying DocInformation:Title and

Re: [O] ODT export displays incorrect title and author in libreoffice

On Wednesday, 22 Oct 2014 at 19:33, Rasmus wrote: Hi Eric, Eric S Fraga e.fr...@ucl.ac.uk writes: I am not sure if my problem is with org or with libreoffice; most likely, the combination of the two! In any case, when I export to ODT, the title and author fields do not appear as they

Re: [O] ODT export displays incorrect title and author in libreoffice

Eric S Fraga e.fr...@ucl.ac.uk writes: On Wednesday, 22 Oct 2014 at 19:33, Rasmus wrote: Hi Eric, Eric S Fraga e.fr...@ucl.ac.uk writes: I am not sure if my problem is with org or with libreoffice; most likely, the combination of the two! In any case, when I export to ODT, the title and

Re: [O] ODT export produces odt file which MS Word 2007 can't open

Gary Oberbrunner ga...@oberbrunner.com writes: I don't have OpenOffice on this machine so can't check it there. Using LibreOffice, I re-saved the file you shared to use OpenDocument-v1.1 format. Does Word import this file without errors? Btw, the files created by the ODT exporter are marked

Re: [O] ODT export produces odt file which MS Word 2007 can't open

Gary Oberbrunner ga...@oberbrunner.com writes: Yes, Word opens your resaved version with no errors. So there is some truth to Word complaining when confronted with OpenDocument v1.2 format files. It does have odd large bullets with the number 10 in the bullet; that is so weird I've attached

Re: [O] ODT export produces odt file which MS Word 2007 can't open

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/25/13, 20:09 , Jambunathan K wrote: Gary Oberbrunner ga...@oberbrunner.com writes: Yes, Word opens your resaved version with no errors. So there is some truth to Word complaining when confronted with OpenDocument v1.2 format files.

[O] ODT export produces odt file which MS Word 2007 can't open

This simple org file: * This is a list * Here's another item produces the simple-list.odt file attached with the latest org-mode (from git master). MS Word 2007 (10.0.6683.5002) SP3 can't open it; it says the file cannot be opened because there are problems with it, then says it's corrupt. It

Re: [O] odt export with 'header'

Andreas Leha writes: Hi Christian, [bringing this back on the list] Oops. 3. Give the first page the page style OrgFirstPage. Which I had to create new. Is that intended? (...) It doesn't strictly have to be that style, or an Org-prefixed style at all, but it's strange that you

Re: [O] odt export with 'header'

Uh, I said: Right. I can't actually find a useful field to insert for email, apart from InsertFieldsDocumentSenderE-mail, which is populated from the user data registered for LibreOffice on your user account, not from the document information, which does not contain email info. But

Re: [O] odt export with 'header'

Christian Moe m...@christianmoe.com writes: [...] 3. Give the first page the page style OrgFirstPage. Which I had to create new. Is that intended? (...) It doesn't strictly have to be that style, or an Org-prefixed style at all, but it's strange that you don't have them. Yes, which

Re: [O] odt export with 'header'

Christian Moe m...@christianmoe.com writes: Uh, I said: Right. I can't actually find a useful field to insert for email, apart from InsertFieldsDocumentSenderE-mail, which is populated from the user data registered for LibreOffice on your user account, not from the document information,

Re: [O] odt export with 'header'

Hi, Andreas, Did this work for you? I'll write it up on Worg if it seems useful. Yours, Christian Christian Moe writes: Hi, Andreas Leha writes: I'd like to have a 'header' on the first page of a odt exported document Here is a fiddly way to do it. (...) The trick is to put your header

Re: [O] odt export with 'header'

Hi Christian, thanks a lot for this. It was definitely helpful. Sorry, I did not get back to this earlier. I do have some issues with this, still -- see my inline comments below. Christian Moe m...@christianmoe.com writes: Hi, Andreas Leha writes: I'd like to have a 'header' on the

Re: [O] odt export with 'header'

Hi Christian, Christian Moe m...@christianmoe.com writes: Hi, Andreas, Did this work for you? I'll write it up on Worg if it seems useful. It is definitely useful and I think it should be documented somewhere. Very nicely written as well. Worg seems appropriate. I guess other people will

Re: [O] odt export with 'header'

Andreas Leha writes: 3. Give the first page the page style OrgFirstPage. Which I had to create new. Is that intended? No, I get that out of the box on a clean system, so I think you should see it too. (Along with OrgTitlePage, which is the style I actually used for testing, and

Re: [O] odt export with 'header'

Christian Moe m...@christianmoe.com writes: Andreas Leha writes: 3. Give the first page the page style OrgFirstPage. Which I had to create new. Is that intended? No, I get that out of the box on a clean system, so I think you should see it too. (Along with OrgTitlePage, which is the

Re: [O] odt export with 'header'

Hi Christian, [bringing this back on the list] Andreas Leha andreas.l...@med.uni-goettingen.de writes: Christian Moe m...@christianmoe.com writes: Andreas Leha writes: 3. Give the first page the page style OrgFirstPage. Which I had to create new. Is that intended? No, I get that out

Re: [O] odt export with 'header'

Hi, Andreas Leha writes: I'd like to have a 'header' on the first page of a odt exported document Here is a fiddly way to do it. There may be easier and/or more correct ways. And perhaps the ODT exporter could use a preamble option like the HTML exporter has. But this should work, more or

[O] odt export with 'header'

Hi all, I'd like to have a 'header' on the first page of a odt exported document -- something like this: , | Some fixed text here +---+ | | some logo | |

Re: [O] ODT export failed: wrong number of agruments

On Sep 20, 2013, at 6:20 AM, Carsten Dominik carsten.domi...@gmail.com wrote: On 20.9.2013, at 02:36, Matt Price mopto...@gmail.com wrote: lots of questions lately! Sorry. I am trying to export an org-file to odt after having created a deck.js presentation from the same file. Exports

[O] ODT export failed: wrong number of agruments

lots of questions lately! Sorry. I am trying to export an org-file to odt after having created a deck.js presentation from the same file. Exports to html work fine, and exports of other files to odt also seem to work. With this image-heavy org-file I'm having trouble. Export fails thus:

Re: [O] ODT export failed: wrong number of agruments

On Thu, Sep 19, 2013 at 8:36 PM, Matt Price mopto...@gmail.com wrote: lots of questions lately! Sorry. I am trying to export an org-file to odt after having created a deck.js presentation from the same file. Exports to html work fine, and exports of other files to odt also seem to work.

Re: [O] ODT export failed: wrong number of agruments

On 20.9.2013, at 02:36, Matt Price mopto...@gmail.com wrote: lots of questions lately! Sorry. I am trying to export an org-file to odt after having created a deck.js presentation from the same file. Exports to html work fine, and exports of other files to odt also seem to work. With

Re: [O] odt export version conflict on emacs for mac os x

Hi, can someone please summarize this discussion for me and tell me what action is required? Thank you! - Carsten On 29.8.2013, at 20:25, Skip Collins skip.coll...@gmail.com wrote: Jambunathan K kjambunat...@gmail.com wrote: After I do an ODT export, many ox-odt variables are duplicated

Re: [O] odt export version conflict on emacs for mac os x

Skip Collins skip.coll...@gmail.com writes: I started digging into this when I noticed some odd behavior while using ODT export. I think I am stuck using the older, buggier ox-odt and my setup is mixing two versions of org. Your settings seem OK to me. 1) an odt file is generated (good)

Re: [O] odt export version conflict on emacs for mac os x

Skip Collins skip.coll...@gmail.com writes: After I do an ODT export, many ox-odt variables are duplicated with old variable names: | [-]-\ Group Org Export ODT | | |--- Option Org Odt Schema Dir | | |--- Option Org Odt Content Template File Above ones come from NEW

Re: [O] odt export version conflict on emacs for mac os x

Carsten Dominik writes: can someone please summarize this discussion for me and tell me what action is required? There is nothing to do here. The legacy defcustoms are built into Emacs and are not easy to remove as there is no official interface to do this. I have code that tries to do clean

Re: [O] odt export version conflict on emacs for mac os x

There is nothing to do here. The legacy defcustoms are built into Emacs and are not easy to remove as there is no official interface to do this. I have code that tries to do clean things up, but it may have unwanted side-effects depending on how the startup files are organized. Hi, Achim

Re: [O] odt export version conflict on emacs for mac os x

On 31.8.2013, at 09:26, Achim Gratz strom...@nexgo.de wrote: Carsten Dominik writes: can someone please summarize this discussion for me and tell me what action is required? There is nothing to do here. The legacy defcustoms are built into Emacs and are not easy to remove as there is no

Re: [O] odt export version conflict on emacs for mac os x

Carsten Dominik carsten.domi...@gmail.com writes: On 31.8.2013, at 09:26, Achim Gratz strom...@nexgo.de wrote: There is nothing to do here. The new variables can and must be put in to a new groups. Thank you very much Achim. If you cannot kill someone just ostracize them. Segregation

Re: [O] odt export version conflict on emacs for mac os x

Best way to explain is with an example: 1. emacs -Q 2. eval this (add-to-list 'load-path ~/src/org-mode/lisp/) (require 'org-loaddefs) Ensure that there is org-loaddefs available from git path. 3. M-x load-library ox-odt.el 4. Ensure (featurep 'org-odt) reports nothing. 5. M-x

Re: [O] odt export version conflict on emacs for mac os x

Christian Moe writes: Could you give a pointer to your code? I'd like to try it. Here it is again: --8---cut here---start-8--- ;; ;; Kill any old org remnants ;; ;; clean load-path (setq load-path (delq nil (mapcar (function (lambda

Re: [O] odt export version conflict on emacs for mac os x

Hi, I confirm that I see the same behavior, i.e. after ODT export old variable names show up in the customize group, similar to what you show below. This is on GNU Emacs 24.3.1 on a Mac, installed with homebrew, with Org-mode 8.0.7 installed via `make update2'. This probably accounts for my

Re: [O] odt export version conflict on emacs for mac os x

Thanks Christian. That this behavior shows up in homebrew leads me to suspect it might be happening on all platforms with recent Emacs, unless steps are taken to eradicate the bundled org-mode. Exactly what those steps should be is not clear to me. I suppose I could just delete files inside

Re: [O] odt export version conflict on emacs for mac os x

I think this is a bug. Can someone confirm? After I do an ODT export, many ox-odt variables are duplicated with old variable names: | [-]-\ Group Org Export ODT | | |--- Option Org Odt Prettify Xml | | |--- Option Org Odt Schema Dir | | |--- Option Org Odt Content Template

Re: [O] ODT export

I don't think you can convert latex bits to org automatically. I was in a similar situation few days ago. I had very satisfying results using LaTeX2HTML and libreoffice convert. (org → latex → html → odt/doc) Thanks Yagnesh. I want to have a working org file that generate odt. Have

Re: [O] ODT export

╭─┤ http://askubuntu.com/a/239332/18411 ├─ │Believe it or not, with complex documents and lots of packages included, I got │much better results with LaTeX2HTML than with LaTeX2RTF, Pandoc or TeX4ht. │ │ latex2html texfile.tex -split 0 -no_navigation -info -address

[O] odt export version conflict on emacs for mac os x

The version of org that comes with my stock Emacs on OS X (from emacsformacosx.org) seems to conflict with my git installation of org. This is particularly evident when trying to use ODT export. Emacs.app is located in the usual /Applications folder. The newer org, which I intend to completely

[O] ODT export

I have an org file with some latex src code blocks embedded in it. These are mainly tables which could not be made using orgmode and had to be coded in latex (orgmode does not allow putting notes at the bottom of table using something like threeparttable). I now need to convert the document to

Re: [O] ODT export

Hello Vikas, I don't think you can convert latex bits to org automatically. I was in a similar situation few days ago. I had very satisfying results using LaTeX2HTML and libreoffice convert. (org → latex → html → odt/doc) Citing the procedure I used to convert. ╭─┤

Re: [O] odt export not working

Nick, I meant to include (setq org-export-backends '(odt)) in my .emacs file. I did that, and now I get the odt exporter as an option when I do C-c C-e. I usually try no to use things that make changes to my .emacs file direcly because I generate my .emacs file from an .org file (through

Re: [O] odt export not working

Manfred Lotz manfred.lotz at arcor.de writes: Are you calling (require 'ox-odt) somewhere in your config? Or configuring `org-export-backends'? ODT export isn't loaded by default, you'll have to load it explicitly by one of those two methods. This should be included in the manual. From

Re: [O] odt export not working

Hello, Julian Burgos jul...@hafro.is writes: Manfred Lotz manfred.lotz at arcor.de writes: Are you calling (require 'ox-odt) somewhere in your config? Or configuring `org-export-backends'? ODT export isn't loaded by default, you'll have to load it explicitly by one of those two methods.

Re: [O] odt export not working

Right... I did not saw it. And even if I did, I would not know that the package needed for loading the back-end for ODT is called ox-odt. Nicolas Goaziou writes: Hello, Julian Burgos jul...@hafro.is writes: Manfred Lotz manfred.lotz at arcor.de writes: Are you calling (require 'ox-odt)

Re: [O] odt export not working

Just thinking how to things easier for noobs like me. :) Julian M. Burgos writes: Right... I did not saw it. And even if I did, I would not know that the package needed for loading the back-end for ODT is called ox-odt. Nicolas Goaziou writes: Hello, Julian Burgos jul...@hafro.is

Re: [O] odt export not working

Julian M. Burgos jul...@hafro.is writes: Right... I did not saw it. And even if I did, I would not know that the package needed for loading the back-end for ODT is called ox-odt. You don't need to know that. The manual tells you to customize `org-export-backends' instead. Regards, --

Re: [O] odt export not working

Ok, I see what you mean. So I should do (setq org-export-backends '(odt)) or something like that. Fair enough. :) Nicolas Goaziou writes: Julian M. Burgos jul...@hafro.is writes: Right... I did not saw it. And even if I did, I would not know that the package needed for loading the

Re: [O] odt export not working

Julian M. Burgos jul...@hafro.is writes: Ok, I see what you mean. So I should do (setq org-export-backends '(odt)) or something like that. Fair enough. :) That's *not* what Nicolas suggested and it's *not* what you should do. Just do C-h v org-export-backends and click the Customize

Re: [O] odt export not working

On Tue, May 7, 2013 at 11:32 AM, Nick Dokos ndo...@gmail.com wrote: Julian M. Burgos jul...@hafro.is writes: Ok, I see what you mean. So I should do (setq org-export-backends '(odt)) or something like that. Fair enough. :) That's *not* what Nicolas suggested and it's *not* what you should

Re: [O] odt export not working

John Hendy jw.he...@gmail.com writes: #+begin_quote 3 Installation PP There are two ways to install export back-ends. 1. You may customize `org-export-backends' variable. It contains the list of back-ends that should always be available. 2. You can also simply require the

[O] odt export not working

Hi there, Using org-mode 8.0-2-g77476c (fedora 18 system) exporting to odt doesn't work. zip program is available. When I do =C-c C-e= the *Org Export Dispatcher* buffer pops up but showing nothing related to odt. When now typing =o o= I get =Invalid Key=. Any idea what's going wrong. --

Re: [O] odt export not working

Manfred Lotz manfred.l...@arcor.de writes: Hi there, Using org-mode 8.0-2-g77476c (fedora 18 system) exporting to odt doesn't work. zip program is available. When I do =C-c C-e= the *Org Export Dispatcher* buffer pops up but showing nothing related to odt. When now typing =o o= I get

Re: [O] odt export not working

On Sun, 21 Apr 2013 22:29:10 +0800 Eric Abrahamsen e...@ericabrahamsen.net wrote: Manfred Lotz manfred.l...@arcor.de writes: Hi there, Using org-mode 8.0-2-g77476c (fedora 18 system) exporting to odt doesn't work. zip program is available. When I do =C-c C-e= the *Org Export

[O] [odt] Export of LaTeX Fragments

Hi, today I had to send over a document in MS Word format. Suprise suprise guess I am not the first one on that mailing list. I was happy to use the new odt export feature and it did the best job out of some other constellations (org-html-word, org-pdf-odt via pdf import plugin, org-pdf-copy

  1   2   >