LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

Options: Use Forum View

Use Proportional Font
Show HTML Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
David Carlisle <[log in to unmask]>
Reply To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Date:
Tue, 10 Nov 1998 16:22:49 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
> Yes.  However, why not send additional files?  Not the equivalent of the
> .bib, but the equivalent of the .blg.
                                   bbl?

The publisher is likely to want `the equivalent of the .bib'.

While authors may be given latex classes and supporting packages to
produce a manuscript that looks more or less like the printed journal,
these days the main requirement of the electronic document, especially
the frontmatter section, is that it can be parsed and the data stuck
into some document database maintained in house by the publisher.  In
some cases the publisher may want to convert the whole document (as they
don't use tex in house at all) but even when they do use tex to format,
they probably want to extract the frontmatter fields as data.  So the
aim of the game is to provide a system where the author provides as much
information as possible, not one where they supply the information half
digested with a view to one particular set of formatting requirements.

(speaking of .bib -> .bbl one thing I did was to try to make a bibtex
style set up so that essentially the .bbl file contained sufficient
information to re-create the .bib fields, so that even though the author
could submit the putatively `formatted' version of the bibliography, the
individual fields like author name and journal title and dates were
unambiguously marked up in the result, not needing to be guessed from
font changes).

David

ATOM RSS1 RSS2
https://listserv.uni-heidelberg.de/cgi-bin/wa?A2=LATEX-L;7a2a145d.0106&FT=M&P=T&H=N&S=a
listserv.uni-heidelberg.de
CC-MAIN-2024-22
77105
application/http; msgtype=response
sha1:I54QEWX2JQQZKHETJHUZQ5ZJRGURN3HI
<urn:uuid:ce650fa7-ee7a-44d9-a90b-5988dcef8bde>
2024-05-21T23:20:40Z
129.206.100.94
text/html
sha1:HJUGZUIKCQP66DXODLXVO45FAGTQ47C6
<urn:uuid:230b306d-53f8-41a0-a4ff-c8a624c3351f>
https://listserv.uni-heidelberg.de/cgi-bin/wa?A2=LATEX-L;7a2a145d.0106&FT=M&P=T&H=N&S=a
response
<urn:uuid:a0131478-6018-471f-ac51-894ba0e720b2>
isPartOf: CC-MAIN-2024-22
publisher: Common Crawl
description: Wide crawl of the web for May 2024
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-184
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.5-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/