emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: windy <chxp_moon@163.com>
To: Ken Mankoff <mankoff@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Organizing and taming hectic Academia work (faculty viewpoint)? Tips or a good guides sought after :)
Date: Thu, 11 Jun 2015 20:54:30 +0800 (CST)	[thread overview]
Message-ID: <4becbb40.3d2.14de2af9ffc.Coremail.chxp_moon@163.com> (raw)
In-Reply-To: <m2pp528mln.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 866 bytes --]

Thanks.

However, pandoc hardly to deal right about the figure caption number, the table (table caption) and the  superscript.
The export in org-mode perform well in everything except for the bibtex.
I prefer the inherent method in org-mode.

The command I use: pandoc --bibliography=zotero.bib --filter pandoc-citeproc 12.tex -o 12.docx

By the way, I like the output style in ODT of org-exporter and I am lazy to adjust the pandoc export style...







在2015年06月11 20时18分, "Ken Mankoff"<mankoff@gmail.com>写道:


On 2015-06-10 at 22:07, windy <chxp_moon@163.com> wrote:
> I finnally export as ODT and change into DOC version, it seems works
> well for that only no reference generate. Wish a more wisdom ODT
> exporter in org-mode. Bibtex is a big problem when export into
> different format files.

Org -> LaTeX --Pandoc--> DOCX  supports references.

 -k.

[-- Attachment #2: Type: text/html, Size: 1340 bytes --]

  reply	other threads:[~2015-06-11 12:55 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-08 16:39 Organizing and taming hectic Academia work (faculty viewpoint)? Tips or a good guides sought after :) Xebar Saram
2015-06-08 21:16 ` M
2015-06-09  5:13   ` Xebar Saram
2015-06-09  7:00     ` Holger Wenzel
2015-06-09 13:21       ` John Kitchin
2015-06-10  1:57         ` windy
2015-06-10 13:49           ` John Kitchin
2015-06-10 14:14             ` Ken Mankoff
2015-06-10 20:58               ` Titus von der Malsburg
2015-06-11  5:30                 ` Rasmus
2015-06-11 14:56                 ` Phillip Lord
2015-06-11 17:02                   ` John Kitchin
2015-06-12 13:24                     ` Phillip Lord
2015-06-10 14:16             ` Julian Burgos
2015-06-11  2:07               ` windy
2015-06-11  5:38                 ` Rasmus
2015-06-11 12:19                   ` windy
2015-06-11 12:18                 ` Ken Mankoff
2015-06-11 12:54                   ` windy [this message]
2015-06-12 14:02               ` Ken Mankoff
2015-06-13 19:06                 ` Xebar Saram
2015-06-13 19:52                   ` John Kitchin
2015-06-15 17:33                 ` Julian Burgos
2015-06-16  1:49               ` Bob Newell
2015-06-16 23:15                 ` Alan L Tyree
2015-06-10 18:51           ` Eric S Fraga
2015-06-09  9:49 ` Alan Schmitt
2015-08-26 14:17 ` Anders Johansson

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=4becbb40.3d2.14de2af9ffc.Coremail.chxp_moon@163.com \
    --to=chxp_moon@163.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mankoff@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).