emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Vaidheeswaran C <vaidheeswaran.chinnaraju@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Richard Lawrence <richard.lawrence@berkeley.edu>, emacs-orgmode@gnu.org
Subject: Re: Citation syntax and ODT
Date: Tue, 24 Feb 2015 12:07:46 +0530	[thread overview]
Message-ID: <54EC1C3A.2040706@gmail.com> (raw)
In-Reply-To: <m2zj83rgfn.fsf@tsdye.com>

On Tuesday 24 February 2015 11:37 AM, Thomas S. Dye wrote:
> 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?
>> 2. Give us some concrete examples of what 'this tool' does.
>>     a) Can an elisp module aspire to replicate what 'this tool' does?
>>     b) 'The task' that 'this tool' accomplishes, is it 'common' across
>>        all the citation engines that the participants (in this
>>        discussion) have in mind.

If someone could respond to above questions with concrete examples I
will give it due attention.

> 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 will be happy to excuse myself from this discussion if ODT/JabRef
integration is of no interest to the community.

  reply	other threads:[~2015-02-24  6:36 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
2015-02-24  6:37                   ` Vaidheeswaran C [this message]
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=54EC1C3A.2040706@gmail.com \
    --to=vaidheeswaran.chinnaraju@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=richard.lawrence@berkeley.edu \
    --cc=tsd@tsdye.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).