From: Sharon Kimble <boudiccas@skimble.plus.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: help-gnu-emacs@gnu.org
Subject: Re: changing from \cite{1} to \cite{MacRae,2002}
Date: Fri, 16 May 2014 15:40:35 +0100 [thread overview]
Message-ID: <87y4y1eqho.fsf@skimble.plus.com> (raw)
In-Reply-To: <87vbt641hy.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Fri, 16 May 2014 08:38:17 +0100")
[-- Attachment #1: Type: text/plain, Size: 3861 bytes --]
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> On Thursday, 15 May 2014 at 20:09, Sharon Kimble wrote:
>> I am using latex and working on a document all in emacs. I have been
>> using the biblatex citation system with the style "numerical", but
>> now want to use "authoryear".
>> At present -
>> ╭────
>> │\usepackage[backend=biber,style=verbose,style=number]{biblatex}
>> ╰────
>>
>> What I want to use -
>> ╭────
>> │\usepackage[backend=biber,style=verbose,style=authoryear]{biblatex}
>> ╰────
>
> Does this work? If not, what happens?
>
> The actual text inside the {} for the cite command has nothing to do
> with the form of output generated for the bibliography. It is simply
> used by biber to find the citation you want to cite. The format of the
> reference is controlled by the style.
After spending many hours on the bibliography I've got some
semblance of order for it.
╭────
│\usepackage[backend=biber,style=alphabetic]{biblatex} % this works
╰────
gives this in the text body
╭────
│This is despite research dating back 50 years which first proved the link between smoking and lung cancer [A54].
╰────
From this source
--8<---------------cut here---------------start------------->8---
@Article{21,
author = {Doll R Hill A.},
title = {The mortality of doctors in relation to their smoking habits; a preliminary report},
journaltitle = {British Medical Journal},
year = {1954},
key = {21},
number = {4877},
pages = {1451-1455},
}
--8<---------------cut here---------------end--------------->8---
If I run "biber uh2014" I get this
--8<---------------cut here---------------start------------->8---
INFO - Logfile is 'uh2014.blg'
INFO - Reading 'uh2014.bcf'
INFO - Found 25 citekeys in bib section 0
INFO - Processing section 0
INFO - Looking for bibtex format file 'uh2014.bib' for section 0
INFO - Decoding LaTeX character macros into UTF-8
INFO - Found BibTeX data source 'uh2014.bib'
INFO - Overriding locale 'en_GB.UTF-8' default tailoring 'variable = shifted' with 'variable = non-ignorable'
INFO - Sorting 'entry' list 'anyt' keys
INFO - No sort tailoring available for locale 'en_GB.UTF-8'
INFO - Writing 'uh2014.bbl' with encoding 'UTF-8'
INFO - Output to uh2014.bbl
--8<---------------cut here---------------end--------------->8---
I'm using this bash script to build my pdf
--8<---------------cut here---------------start------------->8---
#!/bin/bash
set -e
#set -x
#variables
filename="uh2014"
#############
xelatex $filename
biber $filename
biber $filename
xelatex $filename
biber $filename
xelatex $filename
makeindex $filename
makeindex $filename
xelatex $filename
makeglossaries $filename
xelatex $filename
xelatex $filename
--8<---------------cut here---------------end--------------->8---
and it is producing the output seen earlier in this mail.
So, how do I get a more worthwhile output, meaning with
"author/editor, year" please?
I've tried
--8<---------------cut here---------------start------------->8---
% \usepackage[backend=biber,style=biblatex-chicago]{biblatex}
% \usepackage[backend=bibtex,style=harvard]{biblatex}
--8<---------------cut here---------------end--------------->8---
and in each case it says that it can't find the relevant .sty,
although if I go to
/usr/share/texlive/texmf-dist/tex/latex/biblatex-chicago I can
plainly see "biblatex-chicago.sty".
I think that there is something wrong in my work-flow, but I don't
know what it is, so if somebody can help it would be much
appreciated.
Thanks
Sharon.
--
A taste of linux = http://www.sharons.org.uk
my git repo = https://bitbucket.org/boudiccas/dots
TGmeds = http://www.tgmeds.org.uk
Debian testing, Fluxbox 1.3.5, emacs 24.3.91.1
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2014-05-16 14:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 19:09 changing from \cite{1} to \cite{MacRae,2002} Sharon Kimble
2014-05-16 7:38 ` Eric S Fraga
2014-05-16 14:40 ` Sharon Kimble [this message]
[not found] <mailman.1413.1400181010.1147.help-gnu-emacs@gnu.org>
2014-05-16 1:45 ` Emanuel Berg
2014-05-16 14:45 ` Sharon Kimble
2014-05-16 16:21 ` Rasmus
2014-05-16 18:24 ` Sharon Kimble
2014-05-16 18:35 ` Rasmus
2014-05-17 9:00 ` Sharon Kimble
2014-05-17 17:02 ` Rasmus
[not found] ` <mailman.1498.1400264694.1147.help-gnu-emacs@gnu.org>
2014-05-17 9:06 ` Stefan Nobis
2014-05-17 9:10 ` Stefan Nobis
2014-05-16 15:20 ` Alberto Luaces
[not found] ` <mailman.1480.1400253690.1147.help-gnu-emacs@gnu.org>
2014-05-16 17:40 ` Emanuel Berg
2014-05-16 20:10 ` Thien-Thi Nguyen
[not found] ` <mailman.1503.1400270762.1147.help-gnu-emacs@gnu.org>
2014-05-16 23:00 ` Emanuel Berg
[not found] ` <mailman.1474.1400251548.1147.help-gnu-emacs@gnu.org>
2014-05-16 17:50 ` Emanuel Berg
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y4y1eqho.fsf@skimble.plus.com \
--to=boudiccas@skimble.plus.com \
--cc=e.fraga@ucl.ac.uk \
--cc=help-gnu-emacs@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.
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).