On 12/29/07, Ingrid Giffin <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I have a 26-page ms if you're interested. I expect you want something
> longer, though.
>
eventually, yes, but for now, your 26 pager is longer than anything I
have, so yes, do give it to me. Here's the thing though --
it has to be in RTF, and citations have to be in the TeX style
\cite{<cite_key>} (actually, as long as they are referred to by
cite_key, it really doesn't matter whether or not they are enclosed in
{} as I can always change the pattern in my program). I would also
need to know the citation-style that you are following. Detailed
instructions on it would be great... for example, how to treat
citations with more than n authors, when to use et al. and when to use
&, how to treat subsequent citations to the same work, etc.
Do send it to me along with the bibliography.
> Ingrid
>
>
> On 12/29/07 9:37 AM, "P Kishor" <[EMAIL PROTECTED]> wrote:
>
> > I frequently file books and committee reports (those published by the
> > National Academy Press are a good example) where there is no "author"
> > but there are "editor"s. Since my BD generates cite_keys as %a1_%Y_u2,
> > the %a part goes unfilled in the cite_keys for these reports. Is there
> > any way to ask BD to use the author, but if author is not set then use
> > the editor?
> >
> > Another question -- what is the best practice? Do folks file the
> > entire reports? (that is what I do, because that is how I find them).
> > But then, how do you cite individual papers within those reports as in
> > case of conf. proceedings, the reports are typically a set of papers
> > by indiv. authors preceded by come commentary by the editors... can I
> > generate indiv. cite_keys for each component paper? I realize I am
> > probably asking a basic BD-use question, so if this use-case is
> > already described somewhere, kindly point me to it.
> >
> > Finally, I haven't yet received any scapegoat to give me his/her
> > *very* long manuscript to test my Perl script. If you are hesitant
> > about privacy, I will reiterate my solemn promise to use your work
> > *only* for testing (of course, I will probably learn a lot from
> > glancing at your work, which I will have to do in order to determine
> > the efficacy of my script). You will be credited, of course, and if my
> > script does become useful, you would have contributed to another
> > BD-enhancing tool. And, needless to say, your manuscript and bib will
> > not leave my laptop ever.
> >
> > Graçias.
>
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bibdesk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bibdesk-users
