also sprach grubert@... <grubert@...> [=
2006.07.31.1033 +0100]:
> it would be much easier for me if i get an example of input and the=20
> expected output, this might even find into the test set of docutils,
> "it does not work" is unlikely to get fixed.
I understand, but there are many paths to do, so which one do we go?
Do we generate a .aux file and use bibtex, then parse the output and
turn it into rst? That's a hack! Or should we see where
python-bibtex can take us and go from there? I think that's the
better way to do it for all but the latex output format. In that
case, we should really just let latex/bibtex work together.
FWIW, here's an example BibTeX entry:
@BOOK{Krafft:2005:DSCT,
title =3D {The Debian System --- Concepts and Techniques},
publisher =3D {Open Source Press},
year =3D {2005},
author =3D {Martin F. Krafft},
address =3D {Munich, Germany},
month =3D {June},
owner =3D {madduck},
timestamp =3D {2006.07.27},
url =3D {http://debiansystem.info}
}
Now, in terms of the syntax to use in the text, [Krafft:2005:DSCT]_
would be good, but it's taken already. Could we do something like
(Krafft:2005:DSCT)_, or is this too close? or {} ?
Note that the colons need not appear in the identifier, that's just
the format I follow.
--=20
martin; (greetings from the heart of the sun.)
\____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@...
=20
spamtraps: madduck.bogus@...
=20
it's as bad as you think, and they are out to get you.
|