emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Adonay Felipe Nogueira <adfeno@hyperbola.info>
To: emacs-orgmode@gnu.org
Subject: Re: Can export the files with bibliography only to LaTeX
Date: Sat, 16 Dec 2017 18:54:37 -0200	[thread overview]
Message-ID: <87zi6ijsvm.fsf@hyperbola.info> (raw)
In-Reply-To: <87mv2joefp.fsf@gmail.com> (Tim Cross's message of "Sat, 16 Dec 2017 08:43:06 +1100")

This serves as good argumentation:

For all of those reading this and which have other people making demands
such as "you must use this (non-free) software", please remind these
people that what matters is the content, not the tool in this case.

Besides, if they really want to go the "efficiency" route, they should
just accept plain text files since these are lightweight. ;)

2017-12-16T08:43:06+1100 Tim Cross wrote:
> The saddest part of this message is the last line about your publishers
> also requiring word doc! A long time since I had to deal with
> publishers, but at least they use to require Latex (albeit often with
> weird *.sty files!).
>
> After 17 years working in an 'admin' area of a University, I got to the
> end of my tether and resigned 3 weeks ago. A big part of this was due to
> the extent the administrative arm is now dictating direction and a
> feeling the tail is now wagging the dog. Too much of what is being
> required is based on making the administration 'efficient' rather than
> focusing on making teaching, learning and research effective.
>
> Good news is 7 days after finishing, I got a new position within a
> research centre where my role is 100% technical, I'm free to use
> whatever 'tool' I want provided I produce the final outcome i.e. good
> looking presentations and documents (all org and Latex!) and solid
> technical solutions.
>
> Like others who have replied, Pandoc was my 'goto' solution for dealing
> with administration. It is an incredibly powerful tool and worth some
> time investment IMO.
>
> Tim

  reply	other threads:[~2017-12-16 20:54 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
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 [this message]
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=87zi6ijsvm.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).