From: Adonay Felipe Nogueira <adfeno@hyperbola.info>
To: emacs-orgmode@gnu.org
Subject: Re: Can export the files with bibliography only to LaTeX
Date: Thu, 14 Dec 2017 14:09:15 -0200 [thread overview]
Message-ID: <87fu8db8b8.fsf@hyperbola.info> (raw)
In-Reply-To: <87a7ylpk75.fsf@gmail.com> (Eric S. Fraga's message of "Thu, 14 Dec 2017 12:28:46 +0000")
Interesting...
Is this really a requirement? Did you actually asked which formats they
support? Perhaps with careful negotiation, you might come up with good
outcomes. For example: support for sending your work as PDF, TXT or
HTML.
In the case of HTML, you can use any of these to convert your LaTeX file
to HTML:
a) htlatex "File.tex"; although I don't know if this one will do
multiple runs automatically.
b) make4ht "File.tex"; if I'm not mistaken, this last method automates
the various runs of mk4ht; or lastly
c) pass "htlatex" as the LaTeX command (`-latex=' option) in `latexmk',
see the texdoc for `latexmk' and for `htlatex' to know what to put in
the `-latex=' option.
2017-12-14T12:28:46+0000 Eric S Fraga wrote:
> [...]
>
>
> I am sympathetic to these views but unfortunately it's not always
> possible. My university, for instance, requires me to prepare exam
> scripts in DOC (hence my related email a few minutes ago... my yearly
> task of preparing scripts is upon me). I hate it but I have no choice.
next prev parent reply other threads:[~2017-12-14 16:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 19:50 Can export the files with bibliography only to LaTeX Melleus
2017-12-14 9:06 ` Julian M. Burgos
2017-12-14 9:29 ` Alan Schmitt
2017-12-15 11:27 ` Melleus
2017-12-14 12:11 ` Adonay Felipe Nogueira
2017-12-14 12:28 ` Eric S Fraga
2017-12-14 16:09 ` Adonay Felipe Nogueira [this message]
2017-12-15 12:15 ` Eric S Fraga
2017-12-15 11:46 ` Melleus
2017-12-15 21:43 ` Tim Cross
2017-12-16 20:54 ` Adonay Felipe Nogueira
2017-12-17 13:07 ` Eric S Fraga
2017-12-28 21:18 ` Melleus
-- strict thread matches above, loose matches on Subject: below --
2017-12-15 3:18 edgar
2017-12-15 12:21 ` Eric S Fraga
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=87fu8db8b8.fsf@hyperbola.info \
--to=adfeno@hyperbola.info \
--cc=emacs-orgmode@gnu.org \
/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).