From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Bib bug in using months
Date: Tue, 09 May 2006 21:26:08 +0200 [thread overview]
Message-ID: <4460ECD0.6020402@elvenkind.com> (raw)
In-Reply-To: <Pine.WNT.4.63.0605091508010.3620@nqvgln>
Aditya Mahajan wrote:
>
>
> Thanks. For my present project I need short month names, and the
> deadline is tomorrow. So, I will stick to the manual solution at the
> moment.
There should be no need for manual fixes, just do this:
\unprotect
\def\insertmonth#1#2#3%
{\bibdoifelse{\@@pb@month}%
{#1\doifnumberelse{\@@pb@month}%
{\@EA\doconvertshortmonth\@EA{\@@pb@month}}%
{\@@pb@month}#2}{#3}}
\protect
\def\doconvertshortmonth#1%
{\ifcase#1\or % adjust names as you like
jan\or feb\or mar\or apr\or may\or jun\or
jul\or aug\or sep\or oct\or nov\or dec\else !!!\fi }
Cheers, Taco
next prev parent reply other threads:[~2006-05-09 19:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-08 6:18 Aditya Mahajan
2006-05-08 13:08 ` Taco Hoekwater
2006-05-09 19:09 ` Aditya Mahajan
2006-05-09 19:26 ` Taco Hoekwater [this message]
2006-05-10 23:53 ` Aditya Mahajan
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4460ECD0.6020402@elvenkind.com \
--to=taco@elvenkind.com \
--cc=ntg-context@ntg.nl \
/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 NNTP newsgroup(s).