From: tsd@tsdye.com (Thomas S. Dye)
To: Vaidheeswaran C <vaidheeswaran.chinnaraju@gmail.com>
Cc: Richard Lawrence <richard.lawrence@berkeley.edu>, emacs-orgmode@gnu.org
Subject: Re: Citation syntax and ODT
Date: Mon, 23 Feb 2015 20:07:08 -1000 [thread overview]
Message-ID: <m2zj83rgfn.fsf@tsdye.com> (raw)
In-Reply-To: <54EC0CB1.2020408@gmail.com> (Vaidheeswaran C.'s message of "Tue, 24 Feb 2015 11:01:29 +0530")
Aloha Vaidheeswaran C,
Vaidheeswaran C <vaidheeswaran.chinnaraju@gmail.com> writes:
> On Tuesday 24 February 2015 10:31 AM, Thomas S. Dye wrote:
>> Vaidheeswaran C<vaidheeswaran.chinnaraju@gmail.com> writes:
>>
>>> Often times there is a difference between what is possible and what is
>>> the common practice. So,
>>>
>>> 1. How often do you intermix in-text and parenthetical styles.
>>
>> Every day?
>
> Ok.
>
>>> 2. Can the document author re-word his work in such a way that an
>>> in-text or parenthetical citation could be replaced by the other
>>> without compromising on the overall style of the produced document.
>>
>> Yes, but the author will certainly choose to use a tool that doesn't
>> require this.
>
> (Let me remind you, when it comes to LaTeX, I have zero knowledge.)
>
> 1. When you say 'tool' what exactly do you mean?
A citation manager.
> 2. Give us some concrete examples of what 'this tool' does.
Manages citations. The author wants to do as little of this as
possible.
> a) Can an elisp module aspire to replicate what 'this tool' does?
Yes, I believe so.
> b) 'The task' that 'this tool' accomplishes, is it 'common' across
> all the citation engines that the participants (in this
> discussion) have in mind.
I don't know. Do other citation engines require that a document author
re-word his work in such a way that in-text or parenthetical citations
could be replaced by the other?
> ----------------------------------------------------------------
>
> Org crowd is essentially a LaTeX crowd and Emacs crowd is invariably
> academic in nature. It is for this sole reason, that one often
> doesn't hear much frequent complaints regarding lack of citation
> support.
Actually, Org mode supports citations quite well through links, so there
is no need to complain.
In my field of archaeology it is not unusual to find a journal that does
not accept LaTeX. When the journal requires Word, which is very common,
I've been converting from LaTeX with tex4ht, but it would be neat to
export directly to ODT.
> (I think), if we could keep the OTHER users -- by this I mean, users
> of ASCII or HTML or ODT backends happy or 'just happy' we have made a
> good progress.
Agreed. Are they unhappy now? I use the ASCII and HTML exporters
regularly, and I'm quite happy with them.
> Pleasing LaTeX crowd, which is already pleased with status-quo seems a
> bit pointless to me. Put other way, the LaTeX crowd should represent
> just those aspects which it is displeased with.
There is no displeasure in my corner of the LaTeX crowd.
I believe we are all here on this list because we enjoy Emacs and Org
mode, which is an awesome tool for authors.
All the best,
Tom
--
T.S. Dye & Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com
next prev parent reply other threads:[~2015-02-24 6:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-22 7:22 Citation syntax and ODT Vaidheeswaran
2015-02-23 4:11 ` Richard Lawrence
2015-02-23 6:22 ` Vaidheeswaran
2015-02-23 7:10 ` Vaidheeswaran
2015-02-23 17:15 ` Richard Lawrence
2015-02-23 18:11 ` Vaidheeswaran C
2015-02-23 23:25 ` Richard Lawrence
2015-02-24 3:26 ` Alexis
2015-02-24 3:52 ` Vaidheeswaran C
2015-02-24 4:34 ` Vaidheeswaran C
2015-02-24 5:01 ` Thomas S. Dye
2015-02-24 5:31 ` Vaidheeswaran C
2015-02-24 6:07 ` Thomas S. Dye [this message]
2015-02-24 6:37 ` Vaidheeswaran C
2015-02-24 7:48 ` Thomas S. Dye
2015-02-24 17:19 ` Jorge A. Alfaro-Murillo
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=m2zj83rgfn.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=richard.lawrence@berkeley.edu \
--cc=vaidheeswaran.chinnaraju@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).