From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: setupitemize confusion
Date: Thu, 27 Jul 2006 09:43:08 +0200 [thread overview]
Message-ID: <44C86E8C.4050205@elvenkind.com> (raw)
In-Reply-To: <44C863D1.2000009@nibua-r.org>
Renaud AUBIN wrote:
> Steffen Wolfrum a écrit :
>
>>The bib module won't help (I assume): the bibliography is already
>>typed, not generated.
>>
>>Steffen
>>
>>
>
> Hi Steffen, Aditya,
>
> I'm agree with Aditya, Taco can surely help on this point...
> I'm also interested by this feature (to Taco: since IEEE bib formatting
> follows it ;) )
It would not be very hard to add this feature to the module,
but that will probably not help Steffen in this case.
Taco
next prev parent reply other threads:[~2006-07-27 7:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 21:58 Steffen Wolfrum
2006-07-27 5:32 ` Aditya Mahajan
2006-07-27 5:54 ` Steffen Wolfrum
2006-07-27 6:05 ` Aditya Mahajan
2006-07-27 6:17 ` Steffen Wolfrum
2006-07-27 6:57 ` Renaud AUBIN
2006-07-27 7:43 ` Taco Hoekwater [this message]
2006-07-27 7:50 ` Renaud AUBIN
2006-07-27 7:11 ` Renaud AUBIN
2006-07-27 7:50 ` Steffen Wolfrum
2006-07-27 8:36 ` Taco Hoekwater
2006-07-27 8:58 ` Steffen Wolfrum
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=44C86E8C.4050205@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).