From: Tim Cross <theophilusx@gmail.com>
To: Melleus <melleus@openmailbox.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Can export the files with bibliography only to LaTeX
Date: Sat, 16 Dec 2017 08:43:06 +1100 [thread overview]
Message-ID: <87mv2joefp.fsf@gmail.com> (raw)
In-Reply-To: <87374cqklv.fsf@openmailbox.org>
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
Melleus <melleus@openmailbox.org> writes:
> Eric S Fraga <esflists@gmail.com> writes:
>
>> On Thursday, 14 Dec 2017 at 10:11, Adonay Felipe Nogueira wrote:
>>> Indeed, Pandoc is a way out ;)
>>>
>>> I just would advise against converting from LaTeX to Word DOC.
>>
>> [...]
>>
>>> Relying on these formats such as DOC and DOCX only serve to
>>> make people more dependent on the non-free software behind these.
>>
>> 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.
>
> Yes, to take the choise away from customer is very powerful business
> strategy. And a very destructive one either, as many bright minds are
> wasted on creating products that could not compete if not only those
> artificial "standards" supported not by logical reasoning, but by
> interests of the most powerful players.
>
> So I need to adopt DOC/DOCX in my workflow somehow. It is required by my
> university and by my publishers also.
--
Tim Cross
next prev parent reply other threads:[~2017-12-15 21:43 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 [this message]
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=87mv2joefp.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=melleus@openmailbox.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).