From mboxrd@z Thu Jan 1 00:00:00 1970 From: Emmanuel Charpentier Subject: Re: Slight problems with links Date: Tue, 30 Apr 2019 09:45:55 +0200 Message-ID: <1d847241365c1b7f5741868e6fc6d7fcafe9d585.camel@free.fr> References: <602b6645ab39fabcceb851b8e4f12a15b0c04c20.camel@free.fr> <450323f31e177a8a66aea436c688ec066caf4f26.camel@free.fr> <871s1kouwt.fsf@geus3064linuxwsm.geus.dk> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:35162) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hLNSo-0007Lb-Hx for emacs-orgmode@gnu.org; Tue, 30 Apr 2019 03:46:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hLNSn-00038Q-Hy for emacs-orgmode@gnu.org; Tue, 30 Apr 2019 03:46:06 -0400 Received: from smtp1-g21.free.fr ([212.27.42.1]:3968) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hLNSn-00037j-CC for emacs-orgmode@gnu.org; Tue, 30 Apr 2019 03:46:05 -0400 In-Reply-To: <871s1kouwt.fsf@geus3064linuxwsm.geus.dk> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Ken Mankoff Cc: emacs-orgmode , John Kitchin Le mardi 30 avril 2019 =C3=A0 04:43 -0200, Ken Mankoff a =C3=A9crit : > Hi Emmanuel, >=20 > I have looked into PDF and DOCX export repeatedly over the years with > different versions of Org and Pandoc and Google Docs and keep finding > that the best method is Org -> LaTeX, and then LaTeX -> DOCX with > Pandoc. That's also basically the advice given by John Kitchin. > I use this babel block to achieve this: >=20 > #+BEGIN_SRC sh :results verbatim :var fn=3D(file-name-sans-extension > (buffer-name)) > bibexport -o ${fn}.bib ${fn}.aux > pandoc -f latex -i ${fn}.tex -t DOCX -o ${fn}.docx --bibliography > ./${fn}.bib > #+END_SRC >=20 > The first line may not be needed. That extracts the references used > in this document from my single massive (3500 element) bib file. Whew ! How do you manage this ?=20 I gave up using JabRef fo a large collection, and use Zotero (which allows me to share my bibliographic base with Wordheads co-workers.1 have about 14 000 references dispatched in one (small) personal library and three (large: academic physicians are (have to be) chatty...) shared libraries.=20 I create a problem specific collection to collect the relevant references, and export that. I found GetterBibtex's auto-export feature to be very useful. > The advantage of this Org -> LaTeX -> Pandoc -> DOCX method is that > if you need to patch something for Pandoc (e.g. to fix your code > captions or something) you could insert a NoWeb < pandoc>> block before the pandoc line that generates a second, > corrected, LaTeX file. Hmmm... this way lies madness : it multiplies the possible sources for a bug. I'd rather avoid that, and fight for a *correct* LaTeX source, which is not the case at the moment. >=20 > Note that I don't use org-ref, just the standard Org referencing > code, but I don't see why this would change anything, if you're able > to generate PDFs that meet your requirements. Org-ref has its points : it offers the ability to create/update and maintain a document-specific .bib file, ythanks to a set of interfaces to PubMed/DOI/etc.... I don't give up on the idea of suggesting to John Kitchin an interface to Zotero : a very crude interface r(Totxt) exists, that can be used to communicate with a local Zotero process. But this is now too rough (remaining bugs, etc..) to prepare a patch- request (I'm not much of a programmer...). Back to the problem at hand : I'm still bugged by the fact that ox- pandoc does the right thing in the present case (as well as the built- in HTML exporter, by the way), and that the built-in LaTeX exporter is buggy. I just posted a formal bug report limited to this. Cordially yours, -- Emmanuel Charpentier