-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At 10:43 27-01-2002, Norman Walsh wrote:
For any given bibliography style, it's not too hard. But doing
anything that works for you and me out of the box is essentially
impossible.
Hmm... it should be possible to collect code for standard and house
RefDB stores far more information for a bibliographic reference than
just the bibliographic data. As RefDB was designed from the ground up
as a collaborative tool, it is necessary to store a part of this
information, like personal notes or availability information (i.e. a
URL to an electronic
Mark Wroth wrote:
At 02.01.27 13:45 -0500, Norman Walsh wrote:
[...]
I think what's needed here is the equivalent of a BibTeX for DocBook.
That is, something that takes biblioentry's and a style and produces
bibliomixed's. I think that's a lot saner than trying to get the
stylesheets to
On Saturday 26 January 2002 05:22, Markus Hoenicka wrote:
I believe what you have in mind is much easier to achieve with driver
files for the stylesheets. Your software just needs to emit a proper
driver file for the style you want to apply. This happens to be the
way RefDB
/ Dave Pawson [EMAIL PROTECTED] was heard to say:
| I have no idea what the issues are that make a biblio such a beast to style.
Consider the following entry:
biblioentry id=Walsh97
abbrevWalsh97/abbrev
biblioset relation=article
titleA Guide to XML/title
/ Bernd Kreimeier [EMAIL PROTECTED] was heard to say:
| Norman Walsh wrote:
[...]
| How does BibTeX deal with punctuation around optional entries?
|
| It doesn't, IIRC. Can't remember whether you get a bibtex processing
| error, or whether they are just ignored. That's why I find the
| cooked
At 13:43 27/01/2002 -0500, Norman Walsh wrote:
snip/
The same code that helps to produce title pages is supposed to be able
to help produce bibliographies, but I haven't (yet) got all that stuff
working.
Markus mailed me off list, some of the complexities.
Seems even more personal taste than
RefDB can do precisely this. It has an input filter for raw DocBook
bibliographies (with some constraints, as the DocBook markup is not
rich enough to handle various reference types, so you have to use a
few attributes in a way RefDB understands) and can emit cooked DocBook
bibliographies based
Hi,
with the upcoming changes to RefDB it will be possible to utilize
integrated databases as well. This could be embedded MySQL or SQLite
or something, thus no extra software will be needed.
regards,
Markus
Egon Willighagen writes:
The downside of this, however, is that you use extra
Hi Dave,
the problem is less the markup but the rendering in the transformed
documents. DocBook is good enough to hold any information you need to
start with, but the publisher's requirements about formatting are
pretty strange. Commercial bibliography tools which are mainly
targeted at the
/ Bernd Kreimeier [EMAIL PROTECTED] was heard to say:
| I think I'd have to change the DTD first. There seems an information
| loss when expressing proper BibTex entries using DocBook, and the
What information is lost? Can you provide a BibTeX entry and the corresponding
DocBook entry showing
Norman Walsh wrote:
/ Mark Wroth [EMAIL PROTECTED] was heard to say:
| BibTeX allows any fields in any entry. Each bibliography style then
| parses the fields into required, optional, and ignored, and
| provides typesetting rules for the required and optional fields. Any
| field that is
Norman Walsh wrote:
Do the rules ever reorder fields?
The styles do. The order (author first, or title first, or year...)
depends on the journal or proceedings you submit to. The elements
(records) can be in a fixed order (I honestly don't remember, I
don't think I ever changed the
At 02.01.25 09:57 -0500, Norman Walsh wrote:
/ Mark Wroth [EMAIL PROTECTED] was heard to say:
| BibTeX allows any fields in any entry. Each bibliography style then
| parses the fields into required, optional, and ignored, and
| provides typesetting rules for the required and optional fields.
I believe what you have in mind is much easier to achieve with driver
files for the stylesheets. Your software just needs to emit a proper
driver file for the style you want to apply. This happens to be the
way RefDB (http://refdb.sourceforge.net) deals with this problem. No
modifications to the
Bernd Kreimeier writes:
Norman Walsh wrote:
Do the rules ever reorder fields?
The styles do. The order (author first, or title first, or year...)
depends on the journal or proceedings you submit to. The elements
(records) can be in a fixed order (I honestly don't
At 02.01.25 11:48 -0800, Bernd Kreimeier wrote:
Norman Walsh wrote:
Do the rules ever reorder fields?
The styles do. The order (author first, or title first, or year...)
depends on the journal or proceedings you submit to. The elements
(records) can be in a fixed order (I honestly don't
Hi Markus.
Please excuse my ignorance, but would someone do a little educating please?
I have no idea what the issues are that make a biblio such a beast to style.
If anyone has a demo of a good markup+display of a snippet of biblio
I'd much appreciate it.
Or am I the only one on the list that
/ Bernd Kreimeier [EMAIL PROTECTED] was heard to say:
| I do not want to rely on the bibliomixed etc. cooked elements
| as they seem to be a procedural markup fallback for breakdown of
| biblioentry?
The problem with biblioentry (for me :-) is that it's impossible to
design an out of the box
Norman Walsh wrote:
/ Bernd Kreimeier [EMAIL PROTECTED] was heard to say:
| I do not want to rely on the bibliomixed etc. cooked elements
| as they seem to be a procedural markup fallback for breakdown of
| biblioentry?
The problem with biblioentry (for me :-) is that it's impossible to
Norman Walsh wrote:
If you have a strictly mandated house style for bibliographic data,
There is the database format (e.g. BibTeX), and there are the citation
styles for various journals. The problem is that the writer maintains
the former, but the target publication determines the latter.
Jirka Kosek wrote:
I plan to add support for ISO 690 rendering of biblioentryes. However it
is pretty down on my to-do list. And as Norm said, it is very hard to
handle all possible combinations of biblioentry content.
I would guess that BibTex for that reason defined a small number of
22 matches
Mail list logo
