From: Vikas Rawal <vikaslists@agrarianresearch.org>
To: John Kitchin <johnrkitchin@gmail.com>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: exporting zotxt or orgref links to HTML and ODF
Date: Thu, 29 Jan 2015 19:09:36 +0530 [thread overview]
Message-ID: <44717D9A-6D03-4F98-AB76-27A171DC92E8@agrarianresearch.org> (raw)
In-Reply-To: <m27fw5sorh.fsf@gmail.com>
For my use case, I find the native Org to Odt export has several limitations:
1. No support for bibtex
2. I end up using quite a bit of LaTeX-specific stuff for formatting tables and graphics. All of that gets messed up when I do Org to Odt export.
I agree, a robust org to odt/docx export would be very helpful.
Vikas
> On 29-Jan-2015, at 6:54 pm, John Kitchin <johnrkitchin@gmail.com> wrote:
>
> That could be an option. I was mostly looking at feasibility for org to
> docx. There is no obvious advantage to go through markdown, I just had
> some handy machinery in org-ref to export my cite links to the pandoc
> format in that export. I have since figured out a simple way to insert
> pandoc citations in org directly, and do an org -> docx in pandoc
> directly.
>
> It looks like there are limitations all around. My sense is pandoc is
> just a temporary solution until there is (one day) a full org export to docx
> solution. I am not that experienced with the ODT export, so i don't know
> what the state of citation support in those are.
>
> Luckily that is not something I need often, but a robust org to docx
> export would be helpful to many!
>
> Vikas Rawal writes:
>
>>>
>>> The conversion is not perfect, but it gets pretty far. Probably not far
>>> enough to use for production except in the simplest cases.
>>>
>>>
>>
>> John,
>>
>> If your main objective is support for citations, why not go from Org to LaTeX, and then use Pandoc to convert from LaTeX to DocX? Is there an advantage in going through Markdown instead of LaTeX?
>>
>> In my experiments in going Org->LaTeX->(via Pandoc)DocX, I find Bibtex citations to work well. But there are other limitations of Pandoc (for example, lack of support for various LaTeX environments for making tables).
>>
>> Vikas
>
> --
> Professor John Kitchin
> Doherty Hall A207F
> Department of Chemical Engineering
> Carnegie Mellon University
> Pittsburgh, PA 15213
> 412-268-7803
> @johnkitchin
> http://kitchingroup.cheme.cmu.edu
next prev parent reply other threads:[~2015-01-29 13:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMfbzvA83eSWe79Ot=yX+_s_g33gpLnP-z+zQ52QFJm+iJTR+Q@mail.gmail.com>
2015-01-28 21:53 ` exporting zotxt or orgref links to HTML and ODF Matt Price
2015-01-28 23:01 ` John Kitchin
2015-01-29 1:34 ` Matt Price
2015-01-29 1:48 ` John Kitchin
[not found] ` <CAN_Dec80Su+5Nh5mqNxBXsLu_gm93aY77B=2Zrce-TJ1RPKCig@mail.gmail.com>
2015-01-29 13:06 ` John Kitchin
2015-01-29 13:11 ` Vikas Rawal
2015-01-29 13:24 ` John Kitchin
2015-01-29 13:39 ` Vikas Rawal [this message]
2015-01-29 13:09 ` John Kitchin
2015-01-29 2:26 ` Vikas Rawal
2015-01-26 16:29 Matt Price
[not found] ` <54C67E1A.8080706@law.lsu.edu>
2015-01-26 20:40 ` Matt Price
2015-01-26 21:53 ` Monroe, Will
2015-01-27 8:25 ` Eric S Fraga
2015-01-27 9:23 ` Christian Moe
2015-01-27 13:30 ` Rasmus
2015-01-27 13:51 ` Matt Price
2015-01-27 14:14 ` Rasmus
2015-01-27 18:17 ` John Kitchin
2015-01-27 15:24 ` Christian Moe
2015-01-27 17:24 ` Richard Lawrence
2015-01-27 17:50 ` Rasmus
2015-01-28 4:09 ` Richard Lawrence
2015-01-27 20:01 ` Christian Moe
2015-01-27 22:08 ` Rasmus
2015-01-27 22:15 ` John Kitchin
2015-01-28 2:10 ` Matt Price
2015-01-28 6:37 ` Erik Hetzner
2015-02-01 4:20 ` Erik Hetzner
2015-01-27 12:01 ` Vikas Rawal
2015-01-27 13:12 ` Matt Price
2015-01-27 14:28 ` Eric S Fraga
2015-01-27 13:31 ` Albert Krewinkel
[not found] ` <m2vbjsvay0.fsf@christianmoe.com>
[not found] ` <CAN_Dec9qBWWWgdX+wQhdgbthMg_ZOgbOMFoXFixSc4=74avMjw@mail.gmail.com>
2015-01-27 14:41 ` Christian Moe
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=44717D9A-6D03-4F98-AB76-27A171DC92E8@agrarianresearch.org \
--to=vikaslists@agrarianresearch.org \
--cc=emacs-orgmode@gnu.org \
--cc=johnrkitchin@gmail.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).