[dundee] Emacs and org-mode

[Axel]

BibTex is brilliant and make your live easier, but please don't write  
the bib file by oneself.

Use something such as KBibTex to crate and manage the bib file. A  
benefit is you can just key in the title into the search field and  
download all other information from the internet.

There is also support for is brilliant Harvard style (*lol*):  
http://www.ctan.org/tex-archive/macros/latex/contrib/harvard/ There is  
no warranty, I never use this packages.


Quoting Kris Davidson <davidson.kris at gmail.com>:

> Bibtex is fairly easy its just standard LaTeX in a different file,
> makes referencing a bit more automated.
>
> for example in my abertaydissertation.tex I have:
>
> % Bibliography
> \nocite{*} % include everything in the abertaydissertation.bib file
> \bibliographystyle{plain} % I hate Harvard referencing its for
> humanities students, stupid university.
> \bibliography{abertaydissertation}
>
> ... use of internal private addresses \cite{rfc:priv}, NAT
> \cite{rfc:nat1,rfc:nat2} and CIDR \cite{rfc:cidr1,rfc:cidr2} has
> helped...
>
> then in the abertaydissertation.bib file I have:
>
> @misc{rfc:cidr2,
> author="F. Baker and E. Lear and R. Droms",
> title="{Procedures for Renumbering an IPv6 Network without a Flag Day}",
> series="Request for Comments",
> number="4192",
> howpublished="RFC 4192 (Informational)",
> publisher="IETF",
> organization="Internet Engineering Task Force",
> year=2005,
> month=September,
> note="\texttt{\url{http://www.ietf.org/rfc/rfc4192.txt} [last accessed
> 18\textsuperscript{th} of May 2009]}",
> }
>
> @misc{rfc:nat1,
>   author="P. Srisuresh and M. Holdrege",
>   title="{IP Network Address Translator (NAT) Terminology and  
> Considerations}",
>   series="Request for Comments",
>   number="2663",
>   howpublished="RFC 2663 (Informational)",
>   publisher="IETF",
>   organization="Internet Engineering Task Force",
>   year=1999,
>   month=August,
>   note="\texttt{\url{http://www.ietf.org/rfc/rfc2663.txt} [last
> accessed 18\textsuperscript{th} of May 2009]}",
> }
>
> Then I just need to compile the file twice and thats it.
>
> Kris
>
> On 17 May 2010 14:12, Nistur <nistur at googlemail.com> wrote:
>> Thanks for the explanation
>>
>> I looked into BibTex and was looking to use that, but, quite honestly,
>> it seems a bit incomprehensible at the moment, especially considering
>> I have until Wednesday to hand this in. I just haven't got time. As
>> for putting footnotes in, we've been told that we can't do that. All
>> referencing in text has to be done in line in Harvard style. Much as I
>> agree that the footnotes are much neater, I can't do that.
>>
>> Ahh well. Keeping plugging on with my work.
>> I think I've just about had enough with memes... why didn't I do my
>> dissertation on a subject that would have me reading and writing about
>> _computing_ subjects, not sociology that hurts my head :(
>>
>> Nistur
>>
>> On Mon, May 17, 2010 at 2:08 PM, Kris Davidson  
>> <davidson.kris at gmail.com> wrote:
>>> I tend to prefer \href{} myself, its more intelligent than \url{}
>>> theres an explanation here, under section 4.
>>>
>>> http://www.tug.org/applications/hyperref/manual.html
>>>
>>> You probably know this already but you'll want to use Bibtex for
>>> referencing. I quite liked the way footnotes looked in my dissertation
>>> also, seemed to improve the overall appearance.
>>>
>>> Kris
>>>
>>> _______________________________________________
>>> dundee GNU/Linux Users Group mailing list
>>> dundee at lists.lug.org.uk  http://dundeelug.org.uk
>>> https://mailman.lug.org.uk/mailman/listinfo/dundee
>>> Chat on IRC, #tlug on irc.lug.org.uk
>>>
>>
>
> _______________________________________________
> dundee GNU/Linux Users Group mailing list
> dundee at lists.lug.org.uk  http://dundeelug.org.uk
> https://mailman.lug.org.uk/mailman/listinfo/dundee
> Chat on IRC, #tlug on irc.lug.org.uk