From aaee78ecc72d37a1b2e1fd07a4014a4d37ac06ed Mon Sep 17 00:00:00 2001 From: Karl Berry Date: Sun, 23 Dec 2007 23:54:09 +0000 Subject: move bibhtml doc to bibtex git-svn-id: svn://tug.org/texlive/trunk@5849 c570f23f-e606-0410-a88d-b1316a301751 --- Master/texmf-dist/doc/bibtex/bibhtml/LICENCE | 340 ++++++++++++++ Master/texmf-dist/doc/bibtex/bibhtml/bibhtml | 464 +++++++++++++++++++ Master/texmf-dist/doc/bibtex/bibhtml/bibhtml.html | 522 ++++++++++++++++++++++ Master/texmf-dist/doc/bibtex/bibhtml/bibhtml.xslt | 55 +++ Master/texmf-dist/doc/latex/bibhtml/LICENCE | 340 -------------- Master/texmf-dist/doc/latex/bibhtml/bibhtml | 464 ------------------- Master/texmf-dist/doc/latex/bibhtml/bibhtml.html | 522 ---------------------- Master/texmf-dist/doc/latex/bibhtml/bibhtml.xslt | 55 --- 8 files changed, 1381 insertions(+), 1381 deletions(-) create mode 100644 Master/texmf-dist/doc/bibtex/bibhtml/LICENCE create mode 100755 Master/texmf-dist/doc/bibtex/bibhtml/bibhtml create mode 100644 Master/texmf-dist/doc/bibtex/bibhtml/bibhtml.html create mode 100644 Master/texmf-dist/doc/bibtex/bibhtml/bibhtml.xslt delete mode 100644 Master/texmf-dist/doc/latex/bibhtml/LICENCE delete mode 100755 Master/texmf-dist/doc/latex/bibhtml/bibhtml delete mode 100644 Master/texmf-dist/doc/latex/bibhtml/bibhtml.html delete mode 100644 Master/texmf-dist/doc/latex/bibhtml/bibhtml.xslt (limited to 'Master/texmf-dist') diff --git a/Master/texmf-dist/doc/bibtex/bibhtml/LICENCE b/Master/texmf-dist/doc/bibtex/bibhtml/LICENCE new file mode 100644 index 00000000000..3912109b5cd --- /dev/null +++ b/Master/texmf-dist/doc/bibtex/bibhtml/LICENCE @@ -0,0 +1,340 @@ + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 + + Copyright (C) 1989, 1991 Free Software Foundation, Inc. + 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +License is intended to guarantee your freedom to share and change free +software--to make sure the software is free for all its users. This +General Public License applies to most of the Free Software +Foundation's software and to any other program whose authors commit to +using it. (Some other Free Software Foundation software is covered by +the GNU Library General Public License instead.) You can apply it to +your programs, too. + + When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge for +this service if you wish), that you receive source code or can get it +if you want it, that you can change the software or use pieces of it +in new free programs; and that you know you can do these things. + + To protect your rights, we need to make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the rights. +These restrictions translate to certain responsibilities for you if you +distribute copies of the software, or if you modify it. + + For example, if you distribute copies of such a program, whether +gratis or for a fee, you must give the recipients all the rights that +you have. You must make sure that they, too, receive or can get the +source code. And you must show them these terms so they know their +rights. + + We protect your rights with two steps: (1) copyright the software, and +(2) offer you this license which gives you legal permission to copy, +distribute and/or modify the software. + + Also, for each author's protection and ours, we want to make certain +that everyone understands that there is no warranty for this free +software. If the software is modified by someone else and passed on, we +want its recipients to know that what they have is not the original, so +that any problems introduced by others will not reflect on the original +authors' reputations. + + Finally, any free program is threatened constantly by software +patents. We wish to avoid the danger that redistributors of a free +program will individually obtain patent licenses, in effect making the +program proprietary. To prevent this, we have made it clear that any +patent must be licensed for everyone's free use or not licensed at all. + + The precise terms and conditions for copying, distribution and +modification follow. + + GNU GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License applies to any program or other work which contains +a notice placed by the copyright holder saying it may be distributed +under the terms of this General Public License. The "Program", below, +refers to any such program or work, and a "work based on the Program" +means either the Program or any derivative work under copyright law: +that is to say, a work containing the Program or a portion of it, +either verbatim or with modifications and/or translated into another +language. (Hereinafter, translation is included without limitation in +the term "modification".) Each licensee is addressed as "you". + +Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running the Program is not restricted, and the output from the Program +is covered only if its contents constitute a work based on the +Program (independent of having been made by running the Program). +Whether that is true depends on what the Program does. + + 1. You may copy and distribute verbatim copies of the Program's +source code as you receive it, in any medium, provided that you +conspicuously and appropriately publish on each copy an appropriate +copyright notice and disclaimer of warranty; keep intact all the +notices that refer to this License and to the absence of any warranty; +and give any other recipients of the Program a copy of this License +along with the Program. + +You may charge a fee for the physical act of transferring a copy, and +you may at your option offer warranty protection in exchange for a fee. + + 2. You may modify your copy or copies of the Program or any portion +of it, thus forming a work based on the Program, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + + a) You must cause the modified files to carry prominent notices + stating that you changed the files and the date of any change. + + b) You must cause any work that you distribute or publish, that in + whole or in part contains or is derived from the Program or any + part thereof, to be licensed as a whole at no charge to all third + parties under the terms of this License. + + c) If the modified program normally reads commands interactively + when run, you must cause it, when started running for such + interactive use in the most ordinary way, to print or display an + announcement including an appropriate copyright notice and a + notice that there is no warranty (or else, saying that you provide + a warranty) and that users may redistribute the program under + these conditions, and telling the user how to view a copy of this + License. (Exception: if the Program itself is interactive but + does not normally print such an announcement, your work based on + the Program is not required to print an announcement.) + +These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Program, +and can be reasonably considered independent and separate works in +themselves, then this License, and its terms, do not apply to those +sections when you distribute them as separate works. But when you +distribute the same sections as part of a whole which is a work based +on the Program, the distribution of the whole must be on the terms of +this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote it. + +Thus, it is not the intent of this section to claim rights or contest +your rights to work written entirely by you; rather, the intent is to +exercise the right to control the distribution of derivative or +collective works based on the Program. + +In addition, mere aggregation of another work not based on the Program +with the Program (or with a work based on the Program) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. + + 3. You may copy and distribute the Program (or a work based on it, +under Section 2) in object code or executable form under the terms of +Sections 1 and 2 above provided that you also do one of the following: + + a) Accompany it with the complete corresponding machine-readable + source code, which must be distributed under the terms of Sections + 1 and 2 above on a medium customarily used for software interchange; or, + + b) Accompany it with a written offer, valid for at least three + years, to give any third party, for a charge no more than your + cost of physically performing source distribution, a complete + machine-readable copy of the corresponding source code, to be + distributed under the terms of Sections 1 and 2 above on a medium + customarily used for software interchange; or, + + c) Accompany it with the information you received as to the offer + to distribute corresponding source code. (This alternative is + allowed only for noncommercial distribution and only if you + received the program in object code or executable form with such + an offer, in accord with Subsection b above.) + +The source code for a work means the preferred form of the work for +making modifications to it. For an executable work, complete source +code means all the source code for all modules it contains, plus any +associated interface definition files, plus the scripts used to +control compilation and installation of the executable. However, as a +special exception, the source code distributed need not include +anything that is normally distributed (in either source or binary +form) with the major components (compiler, kernel, and so on) of the +operating system on which the executable runs, unless that component +itself accompanies the executable. + +If distribution of executable or object code is made by offering +access to copy from a designated place, then offering equivalent +access to copy the source code from the same place counts as +distribution of the source code, even though third parties are not +compelled to copy the source along with the object code. + + 4. You may not copy, modify, sublicense, or distribute the Program +except as expressly provided under this License. Any attempt +otherwise to copy, modify, sublicense or distribute the Program is +void, and will automatically terminate your rights under this License. +However, parties who have received copies, or rights, from you under +this License will not have their licenses terminated so long as such +parties remain in full compliance. + + 5. You are not required to accept this License, since you have not +signed it. However, nothing else grants you permission to modify or +distribute the Program or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Program (or any work based on the +Program), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Program or works based on it. + + 6. Each time you redistribute the Program (or any work based on the +Program), the recipient automatically receives a license from the +original licensor to copy, distribute or modify the Program subject to +these terms and conditions. You may not impose any further +restrictions on the recipients' exercise of the rights granted herein. +You are not responsible for enforcing compliance by third parties to +this License. + + 7. If, as a consequence of a court judgment or allegation of patent +infringement or for any other reason (not limited to patent issues), +conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot +distribute so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you +may not distribute the Program at all. For example, if a patent +license would not permit royalty-free redistribution of the Program by +all those who receive copies directly or indirectly through you, then +the only way you could satisfy both it and this License would be to +refrain entirely from distribution of the Program. + +If any portion of this section is held invalid or unenforceable under +any particular circumstance, the balance of the section is intended to +apply and the section as a whole is intended to apply in other +circumstances. + +It is not the purpose of this section to induce you to infringe any +patents or other property right claims or to contest validity of any +such claims; this section has the sole purpose of protecting the +integrity of the free software distribution system, which is +implemented by public license practices. Many people have made +generous contributions to the wide range of software distributed +through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is willing +to distribute software through any other system and a licensee cannot +impose that choice. + +This section is intended to make thoroughly clear what is believed to +be a consequence of the rest of this License. + + 8. If the distribution and/or use of the Program is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Program under this License +may add an explicit geographical distribution limitation excluding +those countries, so that distribution is permitted only in or among +countries not thus excluded. In such case, this License incorporates +the limitation as if written in the body of this License. + + 9. The Free Software Foundation may publish revised and/or new versions +of the General Public License from time to time. Such new versions will +be similar in spirit to the present version, but may differ in detail to +address new problems or concerns. + +Each version is given a distinguishing version number. If the Program +specifies a version number of this License which applies to it and "any +later version", you have the option of following the terms and conditions +either of that version or of any later version published by the Free +Software Foundation. If the Program does not specify a version number of +this License, you may choose any version ever published by the Free Software +Foundation. + + 10. If you wish to incorporate parts of the Program into other free +programs whose distribution conditions are different, write to the author +to ask for permission. For software which is copyrighted by the Free +Software Foundation, write to the Free Software Foundation; we sometimes +make exceptions for this. Our decision will be guided by the two goals +of preserving the free status of all derivatives of our free software and +of promoting the sharing and reuse of software generally. + + NO WARRANTY + + 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY +FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN +OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES +PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED +OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF +MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS +TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE +PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, +REPAIR OR CORRECTION. + + 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR +REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, +INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING +OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED +TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY +YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER +PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE +POSSIBILITY OF SUCH DAMAGES. + + END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Programs + + If you develop a new program, and you want it to be of the greatest +possible use to the public, the best way to achieve this is to make it +free software which everyone can redistribute and change under these terms. + + To do so, attach the following notices to the program. It is safest +to attach them to the start of each source file to most effectively +convey the exclusion of warranty; and each file should have at least +the "copyright" line and a pointer to where the full notice is found. + + + Copyright (C) + + This program is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; either version 2 of the License, or + (at your option) any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this program; if not, write to the Free Software + Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA + + +Also add information on how to contact you by electronic and paper mail. + +If the program is interactive, make it output a short notice like this +when it starts in an interactive mode: + + Gnomovision version 69, Copyright (C) year name of author + Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. + This is free software, and you are welcome to redistribute it + under certain conditions; type `show c' for details. + +The hypothetical commands `show w' and `show c' should show the appropriate +parts of the General Public License. Of course, the commands you use may +be called something other than `show w' and `show c'; they could even be +mouse-clicks or menu items--whatever suits your program. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a "copyright disclaimer" for the program, if +necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the program + `Gnomovision' (which makes passes at compilers) written by James Hacker. + + , 1 April 1989 + Ty Coon, President of Vice + +This General Public License does not permit incorporating your program into +proprietary programs. If your program is a subroutine library, you may +consider it more useful to permit linking proprietary applications with the +library. If this is what you want to do, use the GNU Library General +Public License instead of this License. diff --git a/Master/texmf-dist/doc/bibtex/bibhtml/bibhtml b/Master/texmf-dist/doc/bibtex/bibhtml/bibhtml new file mode 100755 index 00000000000..4d645bba496 --- /dev/null +++ b/Master/texmf-dist/doc/bibtex/bibhtml/bibhtml @@ -0,0 +1,464 @@ +#! /usr/bin/env perl +## 'perl -w' is good, but the PERL on the previous line is substituted, +## by default, by '/usr/bin/env perl', and that doesn't always cope well +## with multiple arguments, so leave the option off. +# +# This software is copyright, 1999, 2005, Norman Gray. +# +# This program is free software; you can redistribute it and/or +# modify it under the terms of the GNU General Public License +# as published by the Free Software Foundation; either version 2 +# of the License, or (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program; if not, write to the Free Software +# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. +# +# Author: Norman Gray, norman@astro.gla.ac.uk. +# Department of Physics and Astronomy, University of Glasgow, UK +# +# See the file LICENCE for a copy of the GPL. +# You can also find an online copy at http://www.gnu.org/copyleft/gpl.html . +# +# $Id: bibhtml.in,v 1.5 2005/09/19 16:18:43 norman Exp $ +# +# See +# for documentation. + +use strict; + +my $version = 'Bibhtml, version 1.3, Norman Gray , 2006 October 31'; + + +# configuration... +my $rootname = 'bibliography'; +my $bibdata = ''; # default bibdata is ./bib.bib +my $bibstyle = ''; # default, below, is plainhtml +my $bibconfig = 'bibhtml.config'; # configuration file + +my $html3 = 0; +my $citeall = 0; +my $verbose = 1; +my $mergebib = 0; +my $strippis = 0; # if true, then strip PIs from output + +# configuration variables +my $endash; +my $nbsp; + +my $bibfilename; # the name of the .bib file +my $bblfilename; # the name of the generated .bbl file +my $auxfilename; # the .aux file we generate here + +# control flags +my $phase; +my $foundslot; # true when we're in the gap between + # + +# set to 1 to switch on debugging, set > 1 to exit after option parsing +my $debug = 0; + +# normalise progname - part after last slash +$0 =~ /([^\/]*)$/; +my $progname = $1; + +if ($#ARGV < $[) { + print "Usage: $progname filename ...\n[$version]\n"; + exit 1; +} + +# get directory of first arg (this is where we'll search for bibhtml.config) +$ARGV[0] =~ /[^\/:]*$/; +my $defdir = $`; +#print "defdir $defdir\n"; + + +#------ + +# if -c is present in the argument list, then undefine $bibconfig, +# and so don't read it automatically at the beginning +for (@ARGV) { if (/^-c/) { undef ($bibconfig); last; }} +if (defined ($bibconfig) && (-r $bibconfig)) { + readconfig ($bibconfig); +} + +# Option processing +while ($_ = $ARGV[0], /^[-+]/) +{ + # print "ARGV[0]=$_\n"; + if (/^([-+])3/ ) { $html3= ($1 eq '+') } + if (/^-v/) { $verbose = 1 } + if (/^-q/) { $verbose = 0 } + if (/^-a/) { $citeall = 1 } + if (/^-V/) { print STDERR $version, "\n"; exit } + if (/^--version/) { print STDERR $version, "\n"; exit } + if (/^--merge/) { $mergebib = 1 } + if (/^--strip/) { $strippis = 1 } + if (/^--help/) { printhelp(); exit } + + shift; + last if ($#ARGV < $[); + if (/^-r/) { $rootname = $ARGV[0]; shift } + if (/^-b/) { $bibdata = $ARGV[0]; shift } + if (/^-s/) { $bibstyle = $ARGV[0]; shift } + if (/^-c/) { my $bibconfig = $ARGV[0]; + shift; + readconfig ($bibconfig); } + last if ($#ARGV < $[); +} + + +if ($debug) +{ + # debugging arglist... + print STDERR "rootname $rootname, bibdata $bibdata\n"; + if ($html3) { print STDERR "html3\n"; } + if ($verbose) { print STDERR "verbose\n"; } + if ($citeall) { print STDERR "citeall\n"; } + print STDERR "ARGV @ARGV\n"; + exit if ($debug > 1); +} + +if ($mergebib) { + # usage is bibhtml file.bbl file.html - do nothing other than + # merge a bbl file into an html file + if ($#ARGV < 1) { + print "Usage: $progname --merge file.bbl file.html\n"; + exit; + } + + $phase = +1; + $bblfilename = $ARGV[0]; + $bibfilename = $ARGV[1]; + # Insist that both files have the correct extension + # This route will mostly be called by scripts, so this check is + # both useful and easily satisfied + ($bblfilename =~ /\.bbl$/) && ($bibfilename =~ /\.html$/) + || do { + print STDERR "Usage: $progname --merge file.bbl file.html\n\tfile extensions required!\n"; + exit; + }; +} +else +{ + if ($#ARGV < $[) + { + print "Usage: $progname filename ...\n"; + exit; + } + + # If the command name is bibhtml, then do everything. + # If it isn't, then use the name of the (first) argument to work out which + # phase to perform. If it's a .bbl file, then merge it with the .html + # file, if not, then create the .aux file ready for BibTeX to be + # invoked manually. + if ($progname eq 'bibhtml') + { + $phase = 0; + } + else + { + if ($ARGV[0] =~ /(.*)\.bbl$/) + { + $rootname = $1; + $phase = +1; + } + else + { + $phase = -1; + } + } +} + +if ($debug) +{ + print STDERR "rootname $rootname\nbibdata $bibdata\nphase $phase, html3 $html3\n"; +#exit; +} + + +my @date = localtime(time); +my @mname = ("January", "February", "March", "April", "May", "June", + "July", "August", "September", "October", "November", "December"); + +$bblfilename = "$rootname.bbl" unless (defined ($bblfilename)); +$bibfilename = "$rootname.html" unless (defined ($bibfilename)); +$auxfilename = "$rootname.aux" unless (defined ($auxfilename)); + +print "bibfilename=$bibfilename\nbibdata=$bibdata\n" if $verbose; + +######################################## +# +# Start the scanning phase + +if ($phase <= 0) # -1 or 0 +{ + print "Creating $auxfilename...\n" if ($verbose); + + open (OUT, ">$auxfilename") || die "can't open $auxfilename to write\n"; + print OUT "\\relax\n"; # not really necessary, but... + + if ($citeall) + { + print "Citing all...\n" if ($verbose); + print OUT "\\citation{*}\n"; + } + else + { + foreach my $fn (@ARGV) + { + my $t; # temporary string + print "scanning $fn...\n" if ($verbose); + + open (IN, "$fn") || die "can't open $fn to read\n"; + + while () + { + # Match possibly multiple times on one line + # Note bibfilename must be present, even if this is the + # bibliography itself. + foreach my $m (/$bibfilename#([^\"]+)/g) { + print OUT "\\citation{$m}\n"; + } + if (($t) = /<\?bibhtml\s+bibdata\s+([\w,]*)/) { + # accumulate bibdata + if ($bibdata eq '') { + $bibdata = $t; + } else { + $bibdata .= ',' . $t; + } + print "bibdata=$bibdata\n" if $verbose; + } + if (($t) = /<\?bibhtml\s+bibstyle\s+(\w*)/) { + # do not override any value specified on the command line + $bibstyle = $t if $bibstyle eq ''; + print "bibstyle=$bibstyle\n" if $verbose; + } + } + + close (IN); + } + } + + $bibdata = 'bib' if ($bibdata eq ''); + $bibstyle = 'plainhtml' if ($bibstyle eq ''); + + print OUT "\\bibstyle{$bibstyle}\n"; + print OUT "\\bibdata{$bibdata}\n"; + + close (OUT); +} + +######################################## +# +# Call BibTeX + +if ($phase == 0) +{ + print "Calling BibTeX...\n" if ($verbose); + + system ("bibtex $rootname")==0 || die "can't bibtex $auxfilename\n"; +} + +######################################## +# +# Substitution phase + +if ($phase >= 0 && -r "$bblfilename") # $phase +1 or 0 +{ + print "Merging $bblfilename into $bibfilename...\n" if ($verbose); + + # now merge the new bbl file with the old bibfilename, between the + # pattern /$bibfilename") ||die "can't open $bibfilename to write"; + select (OUT); + open (ORIG, "$bibfilename.old")||die "can't open $bibfilename.old to read"; + } + open (BBL, "$bblfilename") ||die "can't open $bblfilename to read"; + + + $foundslot = 0; # copy the old to the new up to pattern + + FINDSLOT: while () + { + if (/<\?bibhtml\s+today/ || / + + + + + + Bibhtml documentation + + + + + + + +

Bibhtml

+ +
+

Bibhtml consists of a set of BibTeX style files, which +allow you to use BibTeX to produce bibliographies in HTML. As well, +it includes a Perl script which orchestrates the various steps +required to manage such a bibliography for one or more HTML files. +The references in the text are linked directly to the corresponding +bibliography entry, and if a URL is defined in the entry within the +BibTeX database file, then the generated bibliography entry is linked +to this.

+ +

This page is http://purl.org/nxg/dist/bibhtml

+ +

This documentation describes +bibhtml, version 1.3, 2006 October 31.

+
+ +

Contents

+ + +

Bibhtml consists of a set of BibTeX style files, which +allow you to use BibTeX to produce bibliographies in HTML. As well, +it includes a Perl script which orchestrates the various steps +required to manage such a bibliography for one or more HTML files. +The references in the text are linked directly to the corresponding +bibliography entry, and if a URL is defined in the entry within the +BibTeX database file, then the generated bibliography entry is linked +to this.

+ +

The BibTeX style files are plainhtml.bst and +alphahtml.bst, which are derived from the standard files +plain.bst and alpha.bst. As well, there are +.bst files which produce their output in date order. To +use them, you should generate an .aux file by some +appropriate means, and include the line +\bibstyle{plainhtml}. Run BibTeX, and the result is a +.bbl file, in broadly the `plain' style, but formatted +using HTML rather than LaTeX. This might form a useful component of a +XSLT-based workflow. For further details, see the discussion of the +style files below.

+ +

The bibhtml script can orchestrate generating and using +this .aux file, and you can specify the style file to use +either with the -s option, or with +the processing instructions described below.

+ +

Running bibhtml

+ +

The BibTeX database

+ +

Bibhtml works with a standard BibTeX database -- it is +intended to be compatible with a database used in the standard way +with LaTeX. The BibTeX style files +distributed with this package define an additional +url field: if this is present, then the generated entry +will contain a link to this URL. They also define an +eprint field -- if you do not use the LANL preprint +archive, this will be of no interest to you.

+ +

TeX features such as ~ and -- are translated to +corresponding HTML entities (controlled with the +3 +switch, see below), but other TeX constructions will make their way +into the generated HTML, and look a little odd. I might try to deal +with these in future versions.

+ +

Preparing the text

+ +

You prepare your text simply by including links to the bibliography file +(the default is bibliography.html), followed by a fragment +composed of the BibTeX citation key. Thus, you might cite [grendel89] +with

+
<a href="bibliography.html#grendel89">(Grendel, 1989)</a>
+

(of course, the link text can be anything you like). That's all there is to +it. When you run bibhtml, it generates an +.aux file which makes BibTeX produce references for exactly those +keys which appear in this way.

+ +

Preparing the bibliography file -- processing +instructions supported

+ +

The bibliography file is an ordinary HTML document (which may +itself have citations within it), distinguished only by having two +processing instructions within it. +Bibhtml replaces everything between +<?bibhtml start ?> +and +<?bibhtml end ?> +(which should be on lines by themselves) with the formatted +bibliography. It leaves those instructions in place, naturally, so once +this file is set up, you shouldn't have to touch it again. Older +versions of bibhtml used the magic comments <-- bibhtml start +--> and <-- bibhtml end -->: these are +still supported, but are deprecated and may disappear in a future version.

+ +

Alternatively, you may include the processing instruction +<?bibhtml insert?>. This acts broadly like the +start and end processing instructions, +except that the line is completely replaced by the inserted +bibliography. This is useful if the file being processed is a +generated file (perhaps the output of a separate XML tool-chain, for +example), which will not therefore have to be rescanned in future.

+ +

You can specify the bibliography database and style file either on +the command line (see below) or using the +<?bibhtml bibdata bibfile?> +and <?bibhtml bibstylestylefile?> instructions. The +value of `bibdata' is cumulative, and appends to any value specified +on the command line. A value of `bibstyle' specified on the command +line, in contrast, overrides any value in the file.

+ +

As a special case, bibhtml also replaces the line after a +comment <?bibhtml today ?> with today's date.

+ +

Summary of processing instructions:

+ +
+
<?bibhtml start?> and <?bibhtml +stop?>
+
Bracket the bibliography -- any text between these PIs is replaced +when bibhtml is next run.
+ +
<?bibhtml insert?>
+
This PI is replaced by the bibliography when bibhtml is +next run. This PI is always removed, irrespective of the presence or +absence of the --strip option.
+ +
<?bibhtml bibdata bibfile?>
+
Specify the bibliography database to be used. This is the +analogue of a +\bibliography{bibfile} command in a +LaTeX file; see also the -b command-line option.
+ +
<?bibhtml bibstyle stylefile?>
+
Specify the bibliography style to be used. This is the analogue +of \bibliographystyle{stylefile} +command in a LaTex file; see also the -s command-line option.
+ +
<?bibhtml today?>
+
Replace the following line by today's date.
+
+ +

Supported options

+ +

Usage

+
+% bibhtml [options...] filename...
+% bibhtml --merge file.bbl file.html
+
+ +

The filename argument is the name of a file to be scanned.

+ +

Bibhtml takes a list of HTML files as argument (though see +below for a two-pass variant). It creates an +.aux file, runs BibTeX, and merges the resulting +.bbl file (if it exists) into bibliography.html, or +whatever has been specified as the bibliography file name.

+ +

There are several options:

+
+
-3, +3
+
Set this to +3 if you want ~ translated to +&nbsp;, and -- to +&enspace;. Or set it to -3 (the default) if you +don't.
+ +
-a
+
If this option is set, bibhtml won't bother scanning any +files at all, and will generate references for all the entries in your +database. This is equivalent to \nocite{*} in LaTeX.
+ +
-b bibdata
+
The name of your BibTeX database file, as it would be specified in a +\bibliography{} command in LaTeX. Unless you happen to +keep all your references in a file called bib.bib, you'll +probably want to change this. Or you can use the <?bibhtml +bibdata xxx?> processing instruction.
+ +
-c configfile
+
Specifies a configuration file which contains a single line of +options, which are inserted in the command line at that point.
+ +
--merge
+
In this special case, bibhtml takes two arguments, a +.bbl file and an .html file, +merges the first into the second, and nothing else. It's +intended to be used when you have generated a +.bbl file by a separate run of BibTeX, and simply +wish to merge the results into your bibliography file. As +such, it will most likely be useful as part of a script, or +other post-processing system.
+ +
-r rootname
+
Specify this and you'll create rootname.html, +rootname.aux and so on. Why not just stick with the default +`bibliography'...?
+ +
-s bibstyle
+
The name of the BibTeX bibliography style you want to use, as it +would be specified for the \bibstyle command in +LaTeX. If you want to have a different layout for your HTML +bibliographies, please don't change the file plainhtml.bst +distributed with bibhtml. Instead, make a copy of +plainhtml.bst under a different name, edit it as much as you +like, and use this option of bibhtml to use the modified +version instead of the default. Or you can use the <?bibhtml +bibstyle xxx?> processing instruction.
+ +
--strip
+
If this option is set, then strip all processing-instruction lines +from the output file. This means that the resulting file cannot be +processed again by bibhtml, and so is appropriate when the +file is the output of a separate tool-chain.
+ +
-V, --version
+
Bibhtml prints the version information and exits.
+ +
-v, -q
+
Do you want the program to be verbose or quiet? The default is -v, +verbose.
+ +
+ +

The defaults for the various parameters are unlikely to be helpful, +so you're likely to want to set one or more of them every time you run +the program. It is for this reason, and because you're likely to want +the same set of options every time you create the bibliography for a +set of files in a directory, that you can put a collection of options +in a configuration file. This can be specified on the command line +with the option -c configfilename. If this option +is not given, then bibhtml looks for a file named +bibhtml.config. For example, the configuration +file might contain:

+ +
+-b mybib +3 -r refs
+
+ +

BibTeX style files

+ +

bibhtml depends on several BibTeX style files. +plainhtml.bst, plainhtmldate.bst and +plainhtmldater.bst are derived from the standard +plain.bst. All produce HTML, but the latter two sort the +output by date and reverse date, rather than by author. +alphahtml.bst and friends were derived from the standard +alpha.bst, and contributed to the package, by Franz +G. Fischer, Franz.Fischer@lpr.e-technik.tu-muenchen.de, +to whom thanks are due.

+ +

These style files support an additional entry type, +@webpage, and two additional fields on all entry types, +url and lastchecked, which give the URL +associated with the reference, and the date at which the URL was last +verified to be still present. See also the urlbst +package, which performs a different role, but implements the same +BibTeX extensions.

+ +

Although these style files are distributed as part of +bibhtml they are also useful in isolation, as part of a +larger system which generates HTML.

+ +

The distribution includes a sample XSLT script, +bibhtml.xslt which shows how you might use XSLT to +extract citations from a source file into an .aux +file.

+ +

The distributed .bst files have two configurable +parameters, which you might want to adjust for your installation:

+ +

The variable 'xxxmirror gives the host name of the arXiv mirror which will be used +when generating links to eprints. The default setting in the +.bst files is:

+
+"xxx.arxiv.org" 'xxxmirror :=
+
+ +

By default, the style files generate link targets in the +bibliography with the same name as the citation key. Thus a BibTeX +entry with key surname99, say, would appear in the +generated HTML .bbl file wrapped in <a +name="surname99">...</a>. If this is inconvenient, +perhaps because it conflicts with other links within the file, +then you can adjust the 'hrefprefix variable within the +style file, to specify a prefix which should appear in the link key. +Thus setting

+
+"ref:" 'hrefprefix :=
+
+

in the .bst file would produce links like <a +name="ref:surname99">...</a> in the .bbl +file.

+ +

Installation

+ +

Nothing to it.... On Unix, for example, put bibhtml +somewhere in your path and make it executable (chmod u+x +bibhtml), and put *.bst somewhere BibTeX +will find it (this means either looking at the +environment variable BSTINPUTS, or running the command +kpsepath bst, if you have it). If you want to use the two-pass variant of the program, then make a symbolic +link with ln -s bibhtml bibhtml2.

+ +

If you wish, you may change the distributed BibTeX style files (see +above) to the extent of changing the +`eprint' mirror site from the master xxx.arxiv.org to a +more local mirror. If you don't use the LANL preprint archive, this +will be of no interest to you.

+ +

Two-pass bibhtml

+ +

You might sometimes have a need to invoke the +two phases separately. If you make a symbolic link to the program via +ln -s bibhtml bibhtml2, then you can generate an +aux-file alone by giving the command bibhtml2 *.html, +say; and you can merge a bbl-file into the bibliography file with the +command bibhtml2 bibliography.bbl. The command line option +--merge above may be more suitable +if you are calling this code from a script, as it requires you to +specify both the .bbl and the .html file it +is being merged with, (and so it is more robust, and more flexible).

+ +

On Unix, this works because the program is able to +detect the name it was invoked under. This may be more difficult on other +platforms. If so, please get in touch, with suggestions.

+ + +

Example

+ +

There are multiple sources of advice for how to cite electronic +documents. The most formal are an ISO standard [ISO 690-2], and the American +Psychological Association's guidance [APA 2003]. As well, there are older, but still useful +discussions in +Walker and +Emory.

+ +

We also include here a test entry, +which has some odd characters in the title and URL.

+ +

This file was processed with the command bibhtml -r bibhtml +bibhtml.html to produce the document you are reading now.

+ +

References

+ + +
+ +
[apa03] American Psychological Society.
+ APA style: Electronic + references. + [Online, cited September 2005]. +
+ +
[test] A. N. Experimenter.
+ bibhtml tests - how do we handle odd ( &) + characters?. + This is a test entry. +
+ +
[iso690] ISO 690-2.
+ ISO 690-2, bibliographic references to electronic documents + (excerpts). + [Online, cited September 2005]. +
+ +
[emory95] libsf@web.cc.emory.edu.
+ Citation + formats. + [Online]. +
+ +
[walker95] Janice R Walker.
+ MLA-style + citations of electronic sources. + Technical Report 4/95, Department of English, University of South Florida, + January 1995. + Endorsed by the Alliance for Computers and Writing. +
+ +
+ + + + +

See also the documentation for the urlbst +package, which generates BibTeX style files for ordinary LaTeX +output (which also supports a @webpage entry type, and +url and lastchecked fields), and which +contains a similar list of references concerned with citing online +sources.

+ +

Distribution

+ +

Changes

+ +
+ +
1.3, 2006 October 31
+
    +
  • Add hrefprefix parameterisation to style files.
  • +
  • xxx.arxiv.org is now the default e-prints host.
  • +
  • Some improvements to documentation.
  • +
+
+ +
1.2, 2005 September 19
+
    +
  • Changes to .bst style files, adding +@webpage entry type, and lastchecked field +to all entry types.
  • +
  • Updates to documentation, fixing broken links to online references +discussing how to cite online sources.
  • +
  • No reports of breakage from beta releases below.
  • +
+
+ +
1.2b2, 2005 August 30
+
    +
  • Bugfix -- correctly escape characters in .bbl hrefs
  • +
  • Portability fix -- use /usr/bin/env perl at the top of the +script, rather than /usr/bin/perl; this should be more +portable.
  • +
+
+ +
1.2b1, 2005 August 19
+
    +
  • Use processing instructions such as +<?bibhtml start?>, rather than magic comments (the +old behaviour is still temporarily supported).
  • +
  • Add a new directive -- <?bibhtml insert?> +inserts the bibliography in-place.
  • +
  • Debugging output is now written to stderr rather than stdout.
  • +
  • Add --help and --strip options.
  • +
  • Documentation improvements.
  • +
  • Bugfix -- URLs are now properly escaped in the bibliography.
  • +
+
+
+ +

Obtaining bibhtml

+ +

Bibhtml is available on CTAN at +biblio/bibtex/contrib/bibhtml/, +and at +@HOMEPAGE.

+ +

Download the distribution: +bibhtml-1.3.tar.gz.

+ +

Do let me know if +you use this stuff. I'd be grateful for any bug reports, +and bug fixes, and also for any comments on the clarity or +otherwise of this documentation.

+ +

Licence

+ +

This software is copyright, 1999, 2005, Norman Gray. It is released +under the terms of the GNU General Public Licence. See the copyright +declaration at the top of file bibhtml, and the file +LICENCE for the licence conditions. You can find an +online copy of the GPL at http://www.gnu.org/copyleft/gpl.html.

+ +
+Norman
+2006 October 31 +
+ + + diff --git a/Master/texmf-dist/doc/bibtex/bibhtml/bibhtml.xslt b/Master/texmf-dist/doc/bibtex/bibhtml/bibhtml.xslt new file mode 100644 index 00000000000..0980890f171 --- /dev/null +++ b/Master/texmf-dist/doc/bibtex/bibhtml/bibhtml.xslt @@ -0,0 +1,55 @@ + + + + + + + + + + bibstyle + plainhtml + + + + + + citation + + + + + + + + + + \ + + { + + } + + + + diff --git a/Master/texmf-dist/doc/latex/bibhtml/LICENCE b/Master/texmf-dist/doc/latex/bibhtml/LICENCE deleted file mode 100644 index 3912109b5cd..00000000000 --- a/Master/texmf-dist/doc/latex/bibhtml/LICENCE +++ /dev/null @@ -1,340 +0,0 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 - - Copyright (C) 1989, 1991 Free Software Foundation, Inc. - 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA - Everyone is permitted to copy and distribute verbatim copies - of this license document, but changing it is not allowed. - - Preamble - - The licenses for most software are designed to take away your -freedom to share and change it. By contrast, the GNU General Public -License is intended to guarantee your freedom to share and change free -software--to make sure the software is free for all its users. This -General Public License applies to most of the Free Software -Foundation's software and to any other program whose authors commit to -using it. (Some other Free Software Foundation software is covered by -the GNU Library General Public License instead.) You can apply it to -your programs, too. - - When we speak of free software, we are referring to freedom, not -price. Our General Public Licenses are designed to make sure that you -have the freedom to distribute copies of free software (and charge for -this service if you wish), that you receive source code or can get it -if you want it, that you can change the software or use pieces of it -in new free programs; and that you know you can do these things. - - To protect your rights, we need to make restrictions that forbid -anyone to deny you these rights or to ask you to surrender the rights. -These restrictions translate to certain responsibilities for you if you -distribute copies of the software, or if you modify it. - - For example, if you distribute copies of such a program, whether -gratis or for a fee, you must give the recipients all the rights that -you have. You must make sure that they, too, receive or can get the -source code. And you must show them these terms so they know their -rights. - - We protect your rights with two steps: (1) copyright the software, and -(2) offer you this license which gives you legal permission to copy, -distribute and/or modify the software. - - Also, for each author's protection and ours, we want to make certain -that everyone understands that there is no warranty for this free -software. If the software is modified by someone else and passed on, we -want its recipients to know that what they have is not the original, so -that any problems introduced by others will not reflect on the original -authors' reputations. - - Finally, any free program is threatened constantly by software -patents. We wish to avoid the danger that redistributors of a free -program will individually obtain patent licenses, in effect making the -program proprietary. To prevent this, we have made it clear that any -patent must be licensed for everyone's free use or not licensed at all. - - The precise terms and conditions for copying, distribution and -modification follow. - - GNU GENERAL PUBLIC LICENSE - TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION - - 0. This License applies to any program or other work which contains -a notice placed by the copyright holder saying it may be distributed -under the terms of this General Public License. The "Program", below, -refers to any such program or work, and a "work based on the Program" -means either the Program or any derivative work under copyright law: -that is to say, a work containing the Program or a portion of it, -either verbatim or with modifications and/or translated into another -language. (Hereinafter, translation is included without limitation in -the term "modification".) Each licensee is addressed as "you". - -Activities other than copying, distribution and modification are not -covered by this License; they are outside its scope. The act of -running the Program is not restricted, and the output from the Program -is covered only if its contents constitute a work based on the -Program (independent of having been made by running the Program). -Whether that is true depends on what the Program does. - - 1. You may copy and distribute verbatim copies of the Program's -source code as you receive it, in any medium, provided that you -conspicuously and appropriately publish on each copy an appropriate -copyright notice and disclaimer of warranty; keep intact all the -notices that refer to this License and to the absence of any warranty; -and give any other recipients of the Program a copy of this License -along with the Program. - -You may charge a fee for the physical act of transferring a copy, and -you may at your option offer warranty protection in exchange for a fee. - - 2. You may modify your copy or copies of the Program or any portion -of it, thus forming a work based on the Program, and copy and -distribute such modifications or work under the terms of Section 1 -above, provided that you also meet all of these conditions: - - a) You must cause the modified files to carry prominent notices - stating that you changed the files and the date of any change. - - b) You must cause any work that you distribute or publish, that in - whole or in part contains or is derived from the Program or any - part thereof, to be licensed as a whole at no charge to all third - parties under the terms of this License. - - c) If the modified program normally reads commands interactively - when run, you must cause it, when started running for such - interactive use in the most ordinary way, to print or display an - announcement including an appropriate copyright notice and a - notice that there is no warranty (or else, saying that you provide - a warranty) and that users may redistribute the program under - these conditions, and telling the user how to view a copy of this - License. (Exception: if the Program itself is interactive but - does not normally print such an announcement, your work based on - the Program is not required to print an announcement.) - -These requirements apply to the modified work as a whole. If -identifiable sections of that work are not derived from the Program, -and can be reasonably considered independent and separate works in -themselves, then this License, and its terms, do not apply to those -sections when you distribute them as separate works. But when you -distribute the same sections as part of a whole which is a work based -on the Program, the distribution of the whole must be on the terms of -this License, whose permissions for other licensees extend to the -entire whole, and thus to each and every part regardless of who wrote it. - -Thus, it is not the intent of this section to claim rights or contest -your rights to work written entirely by you; rather, the intent is to -exercise the right to control the distribution of derivative or -collective works based on the Program. - -In addition, mere aggregation of another work not based on the Program -with the Program (or with a work based on the Program) on a volume of -a storage or distribution medium does not bring the other work under -the scope of this License. - - 3. You may copy and distribute the Program (or a work based on it, -under Section 2) in object code or executable form under the terms of -Sections 1 and 2 above provided that you also do one of the following: - - a) Accompany it with the complete corresponding machine-readable - source code, which must be distributed under the terms of Sections - 1 and 2 above on a medium customarily used for software interchange; or, - - b) Accompany it with a written offer, valid for at least three - years, to give any third party, for a charge no more than your - cost of physically performing source distribution, a complete - machine-readable copy of the corresponding source code, to be - distributed under the terms of Sections 1 and 2 above on a medium - customarily used for software interchange; or, - - c) Accompany it with the information you received as to the offer - to distribute corresponding source code. (This alternative is - allowed only for noncommercial distribution and only if you - received the program in object code or executable form with such - an offer, in accord with Subsection b above.) - -The source code for a work means the preferred form of the work for -making modifications to it. For an executable work, complete source -code means all the source code for all modules it contains, plus any -associated interface definition files, plus the scripts used to -control compilation and installation of the executable. However, as a -special exception, the source code distributed need not include -anything that is normally distributed (in either source or binary -form) with the major components (compiler, kernel, and so on) of the -operating system on which the executable runs, unless that component -itself accompanies the executable. - -If distribution of executable or object code is made by offering -access to copy from a designated place, then offering equivalent -access to copy the source code from the same place counts as -distribution of the source code, even though third parties are not -compelled to copy the source along with the object code. - - 4. You may not copy, modify, sublicense, or distribute the Program -except as expressly provided under this License. Any attempt -otherwise to copy, modify, sublicense or distribute the Program is -void, and will automatically terminate your rights under this License. -However, parties who have received copies, or rights, from you under -this License will not have their licenses terminated so long as such -parties remain in full compliance. - - 5. You are not required to accept this License, since you have not -signed it. However, nothing else grants you permission to modify or -distribute the Program or its derivative works. These actions are -prohibited by law if you do not accept this License. Therefore, by -modifying or distributing the Program (or any work based on the -Program), you indicate your acceptance of this License to do so, and -all its terms and conditions for copying, distributing or modifying -the Program or works based on it. - - 6. Each time you redistribute the Program (or any work based on the -Program), the recipient automatically receives a license from the -original licensor to copy, distribute or modify the Program subject to -these terms and conditions. You may not impose any further -restrictions on the recipients' exercise of the rights granted herein. -You are not responsible for enforcing compliance by third parties to -this License. - - 7. If, as a consequence of a court judgment or allegation of patent -infringement or for any other reason (not limited to patent issues), -conditions are imposed on you (whether by court order, agreement or -otherwise) that contradict the conditions of this License, they do not -excuse you from the conditions of this License. If you cannot -distribute so as to satisfy simultaneously your obligations under this -License and any other pertinent obligations, then as a consequence you -may not distribute the Program at all. For example, if a patent -license would not permit royalty-free redistribution of the Program by -all those who receive copies directly or indirectly through you, then -the only way you could satisfy both it and this License would be to -refrain entirely from distribution of the Program. - -If any portion of this section is held invalid or unenforceable under -any particular circumstance, the balance of the section is intended to -apply and the section as a whole is intended to apply in other -circumstances. - -It is not the purpose of this section to induce you to infringe any -patents or other property right claims or to contest validity of any -such claims; this section has the sole purpose of protecting the -integrity of the free software distribution system, which is -implemented by public license practices. Many people have made -generous contributions to the wide range of software distributed -through that system in reliance on consistent application of that -system; it is up to the author/donor to decide if he or she is willing -to distribute software through any other system and a licensee cannot -impose that choice. - -This section is intended to make thoroughly clear what is believed to -be a consequence of the rest of this License. - - 8. If the distribution and/or use of the Program is restricted in -certain countries either by patents or by copyrighted interfaces, the -original copyright holder who places the Program under this License -may add an explicit geographical distribution limitation excluding -those countries, so that distribution is permitted only in or among -countries not thus excluded. In such case, this License incorporates -the limitation as if written in the body of this License. - - 9. The Free Software Foundation may publish revised and/or new versions -of the General Public License from time to time. Such new versions will -be similar in spirit to the present version, but may differ in detail to -address new problems or concerns. - -Each version is given a distinguishing version number. If the Program -specifies a version number of this License which applies to it and "any -later version", you have the option of following the terms and conditions -either of that version or of any later version published by the Free -Software Foundation. If the Program does not specify a version number of -this License, you may choose any version ever published by the Free Software -Foundation. - - 10. If you wish to incorporate parts of the Program into other free -programs whose distribution conditions are different, write to the author -to ask for permission. For software which is copyrighted by the Free -Software Foundation, write to the Free Software Foundation; we sometimes -make exceptions for this. Our decision will be guided by the two goals -of preserving the free status of all derivatives of our free software and -of promoting the sharing and reuse of software generally. - - NO WARRANTY - - 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY -FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN -OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES -PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED -OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF -MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS -TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE -PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, -REPAIR OR CORRECTION. - - 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING -WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR -REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, -INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING -OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED -TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY -YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER -PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE -POSSIBILITY OF SUCH DAMAGES. - - END OF TERMS AND CONDITIONS - - How to Apply These Terms to Your New Programs - - If you develop a new program, and you want it to be of the greatest -possible use to the public, the best way to achieve this is to make it -free software which everyone can redistribute and change under these terms. - - To do so, attach the following notices to the program. It is safest -to attach them to the start of each source file to most effectively -convey the exclusion of warranty; and each file should have at least -the "copyright" line and a pointer to where the full notice is found. - - - Copyright (C) - - This program is free software; you can redistribute it and/or modify - it under the terms of the GNU General Public License as published by - the Free Software Foundation; either version 2 of the License, or - (at your option) any later version. - - This program is distributed in the hope that it will be useful, - but WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - GNU General Public License for more details. - - You should have received a copy of the GNU General Public License - along with this program; if not, write to the Free Software - Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA - - -Also add information on how to contact you by electronic and paper mail. - -If the program is interactive, make it output a short notice like this -when it starts in an interactive mode: - - Gnomovision version 69, Copyright (C) year name of author - Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. - This is free software, and you are welcome to redistribute it - under certain conditions; type `show c' for details. - -The hypothetical commands `show w' and `show c' should show the appropriate -parts of the General Public License. Of course, the commands you use may -be called something other than `show w' and `show c'; they could even be -mouse-clicks or menu items--whatever suits your program. - -You should also get your employer (if you work as a programmer) or your -school, if any, to sign a "copyright disclaimer" for the program, if -necessary. Here is a sample; alter the names: - - Yoyodyne, Inc., hereby disclaims all copyright interest in the program - `Gnomovision' (which makes passes at compilers) written by James Hacker. - - , 1 April 1989 - Ty Coon, President of Vice - -This General Public License does not permit incorporating your program into -proprietary programs. If your program is a subroutine library, you may -consider it more useful to permit linking proprietary applications with the -library. If this is what you want to do, use the GNU Library General -Public License instead of this License. diff --git a/Master/texmf-dist/doc/latex/bibhtml/bibhtml b/Master/texmf-dist/doc/latex/bibhtml/bibhtml deleted file mode 100755 index 4d645bba496..00000000000 --- a/Master/texmf-dist/doc/latex/bibhtml/bibhtml +++ /dev/null @@ -1,464 +0,0 @@ -#! /usr/bin/env perl -## 'perl -w' is good, but the PERL on the previous line is substituted, -## by default, by '/usr/bin/env perl', and that doesn't always cope well -## with multiple arguments, so leave the option off. -# -# This software is copyright, 1999, 2005, Norman Gray. -# -# This program is free software; you can redistribute it and/or -# modify it under the terms of the GNU General Public License -# as published by the Free Software Foundation; either version 2 -# of the License, or (at your option) any later version. -# -# This program is distributed in the hope that it will be useful, -# but WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the -# GNU General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with this program; if not, write to the Free Software -# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. -# -# Author: Norman Gray, norman@astro.gla.ac.uk. -# Department of Physics and Astronomy, University of Glasgow, UK -# -# See the file LICENCE for a copy of the GPL. -# You can also find an online copy at http://www.gnu.org/copyleft/gpl.html . -# -# $Id: bibhtml.in,v 1.5 2005/09/19 16:18:43 norman Exp $ -# -# See -# for documentation. - -use strict; - -my $version = 'Bibhtml, version 1.3, Norman Gray , 2006 October 31'; - - -# configuration... -my $rootname = 'bibliography'; -my $bibdata = ''; # default bibdata is ./bib.bib -my $bibstyle = ''; # default, below, is plainhtml -my $bibconfig = 'bibhtml.config'; # configuration file - -my $html3 = 0; -my $citeall = 0; -my $verbose = 1; -my $mergebib = 0; -my $strippis = 0; # if true, then strip PIs from output - -# configuration variables -my $endash; -my $nbsp; - -my $bibfilename; # the name of the .bib file -my $bblfilename; # the name of the generated .bbl file -my $auxfilename; # the .aux file we generate here - -# control flags -my $phase; -my $foundslot; # true when we're in the gap between - # - -# set to 1 to switch on debugging, set > 1 to exit after option parsing -my $debug = 0; - -# normalise progname - part after last slash -$0 =~ /([^\/]*)$/; -my $progname = $1; - -if ($#ARGV < $[) { - print "Usage: $progname filename ...\n[$version]\n"; - exit 1; -} - -# get directory of first arg (this is where we'll search for bibhtml.config) -$ARGV[0] =~ /[^\/:]*$/; -my $defdir = $`; -#print "defdir $defdir\n"; - - -#------ - -# if -c is present in the argument list, then undefine $bibconfig, -# and so don't read it automatically at the beginning -for (@ARGV) { if (/^-c/) { undef ($bibconfig); last; }} -if (defined ($bibconfig) && (-r $bibconfig)) { - readconfig ($bibconfig); -} - -# Option processing -while ($_ = $ARGV[0], /^[-+]/) -{ - # print "ARGV[0]=$_\n"; - if (/^([-+])3/ ) { $html3= ($1 eq '+') } - if (/^-v/) { $verbose = 1 } - if (/^-q/) { $verbose = 0 } - if (/^-a/) { $citeall = 1 } - if (/^-V/) { print STDERR $version, "\n"; exit } - if (/^--version/) { print STDERR $version, "\n"; exit } - if (/^--merge/) { $mergebib = 1 } - if (/^--strip/) { $strippis = 1 } - if (/^--help/) { printhelp(); exit } - - shift; - last if ($#ARGV < $[); - if (/^-r/) { $rootname = $ARGV[0]; shift } - if (/^-b/) { $bibdata = $ARGV[0]; shift } - if (/^-s/) { $bibstyle = $ARGV[0]; shift } - if (/^-c/) { my $bibconfig = $ARGV[0]; - shift; - readconfig ($bibconfig); } - last if ($#ARGV < $[); -} - - -if ($debug) -{ - # debugging arglist... - print STDERR "rootname $rootname, bibdata $bibdata\n"; - if ($html3) { print STDERR "html3\n"; } - if ($verbose) { print STDERR "verbose\n"; } - if ($citeall) { print STDERR "citeall\n"; } - print STDERR "ARGV @ARGV\n"; - exit if ($debug > 1); -} - -if ($mergebib) { - # usage is bibhtml file.bbl file.html - do nothing other than - # merge a bbl file into an html file - if ($#ARGV < 1) { - print "Usage: $progname --merge file.bbl file.html\n"; - exit; - } - - $phase = +1; - $bblfilename = $ARGV[0]; - $bibfilename = $ARGV[1]; - # Insist that both files have the correct extension - # This route will mostly be called by scripts, so this check is - # both useful and easily satisfied - ($bblfilename =~ /\.bbl$/) && ($bibfilename =~ /\.html$/) - || do { - print STDERR "Usage: $progname --merge file.bbl file.html\n\tfile extensions required!\n"; - exit; - }; -} -else -{ - if ($#ARGV < $[) - { - print "Usage: $progname filename ...\n"; - exit; - } - - # If the command name is bibhtml, then do everything. - # If it isn't, then use the name of the (first) argument to work out which - # phase to perform. If it's a .bbl file, then merge it with the .html - # file, if not, then create the .aux file ready for BibTeX to be - # invoked manually. - if ($progname eq 'bibhtml') - { - $phase = 0; - } - else - { - if ($ARGV[0] =~ /(.*)\.bbl$/) - { - $rootname = $1; - $phase = +1; - } - else - { - $phase = -1; - } - } -} - -if ($debug) -{ - print STDERR "rootname $rootname\nbibdata $bibdata\nphase $phase, html3 $html3\n"; -#exit; -} - - -my @date = localtime(time); -my @mname = ("January", "February", "March", "April", "May", "June", - "July", "August", "September", "October", "November", "December"); - -$bblfilename = "$rootname.bbl" unless (defined ($bblfilename)); -$bibfilename = "$rootname.html" unless (defined ($bibfilename)); -$auxfilename = "$rootname.aux" unless (defined ($auxfilename)); - -print "bibfilename=$bibfilename\nbibdata=$bibdata\n" if $verbose; - -######################################## -# -# Start the scanning phase - -if ($phase <= 0) # -1 or 0 -{ - print "Creating $auxfilename...\n" if ($verbose); - - open (OUT, ">$auxfilename") || die "can't open $auxfilename to write\n"; - print OUT "\\relax\n"; # not really necessary, but... - - if ($citeall) - { - print "Citing all...\n" if ($verbose); - print OUT "\\citation{*}\n"; - } - else - { - foreach my $fn (@ARGV) - { - my $t; # temporary string - print "scanning $fn...\n" if ($verbose); - - open (IN, "$fn") || die "can't open $fn to read\n"; - - while () - { - # Match possibly multiple times on one line - # Note bibfilename must be present, even if this is the - # bibliography itself. - foreach my $m (/$bibfilename#([^\"]+)/g) { - print OUT "\\citation{$m}\n"; - } - if (($t) = /<\?bibhtml\s+bibdata\s+([\w,]*)/) { - # accumulate bibdata - if ($bibdata eq '') { - $bibdata = $t; - } else { - $bibdata .= ',' . $t; - } - print "bibdata=$bibdata\n" if $verbose; - } - if (($t) = /<\?bibhtml\s+bibstyle\s+(\w*)/) { - # do not override any value specified on the command line - $bibstyle = $t if $bibstyle eq ''; - print "bibstyle=$bibstyle\n" if $verbose; - } - } - - close (IN); - } - } - - $bibdata = 'bib' if ($bibdata eq ''); - $bibstyle = 'plainhtml' if ($bibstyle eq ''); - - print OUT "\\bibstyle{$bibstyle}\n"; - print OUT "\\bibdata{$bibdata}\n"; - - close (OUT); -} - -######################################## -# -# Call BibTeX - -if ($phase == 0) -{ - print "Calling BibTeX...\n" if ($verbose); - - system ("bibtex $rootname")==0 || die "can't bibtex $auxfilename\n"; -} - -######################################## -# -# Substitution phase - -if ($phase >= 0 && -r "$bblfilename") # $phase +1 or 0 -{ - print "Merging $bblfilename into $bibfilename...\n" if ($verbose); - - # now merge the new bbl file with the old bibfilename, between the - # pattern /$bibfilename") ||die "can't open $bibfilename to write"; - select (OUT); - open (ORIG, "$bibfilename.old")||die "can't open $bibfilename.old to read"; - } - open (BBL, "$bblfilename") ||die "can't open $bblfilename to read"; - - - $foundslot = 0; # copy the old to the new up to pattern - - FINDSLOT: while () - { - if (/<\?bibhtml\s+today/ || / - - - - - - Bibhtml documentation - - - - - - - -

Bibhtml

- -
-

Bibhtml consists of a set of BibTeX style files, which -allow you to use BibTeX to produce bibliographies in HTML. As well, -it includes a Perl script which orchestrates the various steps -required to manage such a bibliography for one or more HTML files. -The references in the text are linked directly to the corresponding -bibliography entry, and if a URL is defined in the entry within the -BibTeX database file, then the generated bibliography entry is linked -to this.

- -

This page is http://purl.org/nxg/dist/bibhtml

- -

This documentation describes -bibhtml, version 1.3, 2006 October 31.

-
- -

Contents

- - -

Bibhtml consists of a set of BibTeX style files, which -allow you to use BibTeX to produce bibliographies in HTML. As well, -it includes a Perl script which orchestrates the various steps -required to manage such a bibliography for one or more HTML files. -The references in the text are linked directly to the corresponding -bibliography entry, and if a URL is defined in the entry within the -BibTeX database file, then the generated bibliography entry is linked -to this.

- -

The BibTeX style files are plainhtml.bst and -alphahtml.bst, which are derived from the standard files -plain.bst and alpha.bst. As well, there are -.bst files which produce their output in date order. To -use them, you should generate an .aux file by some -appropriate means, and include the line -\bibstyle{plainhtml}. Run BibTeX, and the result is a -.bbl file, in broadly the `plain' style, but formatted -using HTML rather than LaTeX. This might form a useful component of a -XSLT-based workflow. For further details, see the discussion of the -style files below.

- -

The bibhtml script can orchestrate generating and using -this .aux file, and you can specify the style file to use -either with the -s option, or with -the processing instructions described below.

- -

Running bibhtml

- -

The BibTeX database

- -

Bibhtml works with a standard BibTeX database -- it is -intended to be compatible with a database used in the standard way -with LaTeX. The BibTeX style files -distributed with this package define an additional -url field: if this is present, then the generated entry -will contain a link to this URL. They also define an -eprint field -- if you do not use the LANL preprint -archive, this will be of no interest to you.

- -

TeX features such as ~ and -- are translated to -corresponding HTML entities (controlled with the +3 -switch, see below), but other TeX constructions will make their way -into the generated HTML, and look a little odd. I might try to deal -with these in future versions.

- -

Preparing the text

- -

You prepare your text simply by including links to the bibliography file -(the default is bibliography.html), followed by a fragment -composed of the BibTeX citation key. Thus, you might cite [grendel89] -with

-
<a href="bibliography.html#grendel89">(Grendel, 1989)</a>
-

(of course, the link text can be anything you like). That's all there is to -it. When you run bibhtml, it generates an -.aux file which makes BibTeX produce references for exactly those -keys which appear in this way.

- -

Preparing the bibliography file -- processing -instructions supported

- -

The bibliography file is an ordinary HTML document (which may -itself have citations within it), distinguished only by having two -processing instructions within it. -Bibhtml replaces everything between -<?bibhtml start ?> -and -<?bibhtml end ?> -(which should be on lines by themselves) with the formatted -bibliography. It leaves those instructions in place, naturally, so once -this file is set up, you shouldn't have to touch it again. Older -versions of bibhtml used the magic comments <-- bibhtml start ---> and <-- bibhtml end -->: these are -still supported, but are deprecated and may disappear in a future version.

- -

Alternatively, you may include the processing instruction -<?bibhtml insert?>. This acts broadly like the -start and end processing instructions, -except that the line is completely replaced by the inserted -bibliography. This is useful if the file being processed is a -generated file (perhaps the output of a separate XML tool-chain, for -example), which will not therefore have to be rescanned in future.

- -

You can specify the bibliography database and style file either on -the command line (see below) or using the -<?bibhtml bibdata bibfile?> -and <?bibhtml bibstylestylefile?> instructions. The -value of `bibdata' is cumulative, and appends to any value specified -on the command line. A value of `bibstyle' specified on the command -line, in contrast, overrides any value in the file.

- -

As a special case, bibhtml also replaces the line after a -comment <?bibhtml today ?> with today's date.

- -

Summary of processing instructions:

- -
-
<?bibhtml start?> and <?bibhtml -stop?>
-
Bracket the bibliography -- any text between these PIs is replaced -when bibhtml is next run.
- -
<?bibhtml insert?>
-
This PI is replaced by the bibliography when bibhtml is -next run. This PI is always removed, irrespective of the presence or -absence of the --strip option.
- -
<?bibhtml bibdata bibfile?>
-
Specify the bibliography database to be used. This is the -analogue of a -\bibliography{bibfile} command in a -LaTeX file; see also the -b command-line option.
- -
<?bibhtml bibstyle stylefile?>
-
Specify the bibliography style to be used. This is the analogue -of \bibliographystyle{stylefile} -command in a LaTex file; see also the -s command-line option.
- -
<?bibhtml today?>
-
Replace the following line by today's date.
-
- -

Supported options

- -

Usage

-
-% bibhtml [options...] filename...
-% bibhtml --merge file.bbl file.html
-
- -

The filename argument is the name of a file to be scanned.

- -

Bibhtml takes a list of HTML files as argument (though see -below for a two-pass variant). It creates an -.aux file, runs BibTeX, and merges the resulting -.bbl file (if it exists) into bibliography.html, or -whatever has been specified as the bibliography file name.

- -

There are several options:

-
-
-3, +3
-
Set this to +3 if you want ~ translated to -&nbsp;, and -- to -&enspace;. Or set it to -3 (the default) if you -don't.
- -
-a
-
If this option is set, bibhtml won't bother scanning any -files at all, and will generate references for all the entries in your -database. This is equivalent to \nocite{*} in LaTeX.
- -
-b bibdata
-
The name of your BibTeX database file, as it would be specified in a -\bibliography{} command in LaTeX. Unless you happen to -keep all your references in a file called bib.bib, you'll -probably want to change this. Or you can use the <?bibhtml -bibdata xxx?> processing instruction.
- -
-c configfile
-
Specifies a configuration file which contains a single line of -options, which are inserted in the command line at that point.
- -
--merge
-
In this special case, bibhtml takes two arguments, a -.bbl file and an .html file, -merges the first into the second, and nothing else. It's -intended to be used when you have generated a -.bbl file by a separate run of BibTeX, and simply -wish to merge the results into your bibliography file. As -such, it will most likely be useful as part of a script, or -other post-processing system.
- -
-r rootname
-
Specify this and you'll create rootname.html, -rootname.aux and so on. Why not just stick with the default -`bibliography'...?
- -
-s bibstyle
-
The name of the BibTeX bibliography style you want to use, as it -would be specified for the \bibstyle command in -LaTeX. If you want to have a different layout for your HTML -bibliographies, please don't change the file plainhtml.bst -distributed with bibhtml. Instead, make a copy of -plainhtml.bst under a different name, edit it as much as you -like, and use this option of bibhtml to use the modified -version instead of the default. Or you can use the <?bibhtml -bibstyle xxx?> processing instruction.
- -
--strip
-
If this option is set, then strip all processing-instruction lines -from the output file. This means that the resulting file cannot be -processed again by bibhtml, and so is appropriate when the -file is the output of a separate tool-chain.
- -
-V, --version
-
Bibhtml prints the version information and exits.
- -
-v, -q
-
Do you want the program to be verbose or quiet? The default is -v, -verbose.
- -
- -

The defaults for the various parameters are unlikely to be helpful, -so you're likely to want to set one or more of them every time you run -the program. It is for this reason, and because you're likely to want -the same set of options every time you create the bibliography for a -set of files in a directory, that you can put a collection of options -in a configuration file. This can be specified on the command line -with the option -c configfilename. If this option -is not given, then bibhtml looks for a file named -bibhtml.config. For example, the configuration -file might contain:

- -
--b mybib +3 -r refs
-
- -

BibTeX style files

- -

bibhtml depends on several BibTeX style files. -plainhtml.bst, plainhtmldate.bst and -plainhtmldater.bst are derived from the standard -plain.bst. All produce HTML, but the latter two sort the -output by date and reverse date, rather than by author. -alphahtml.bst and friends were derived from the standard -alpha.bst, and contributed to the package, by Franz -G. Fischer, Franz.Fischer@lpr.e-technik.tu-muenchen.de, -to whom thanks are due.

- -

These style files support an additional entry type, -@webpage, and two additional fields on all entry types, -url and lastchecked, which give the URL -associated with the reference, and the date at which the URL was last -verified to be still present. See also the urlbst -package, which performs a different role, but implements the same -BibTeX extensions.

- -

Although these style files are distributed as part of -bibhtml they are also useful in isolation, as part of a -larger system which generates HTML.

- -

The distribution includes a sample XSLT script, -bibhtml.xslt which shows how you might use XSLT to -extract citations from a source file into an .aux -file.

- -

The distributed .bst files have two configurable -parameters, which you might want to adjust for your installation:

- -

The variable 'xxxmirror gives the host name of the arXiv mirror which will be used -when generating links to eprints. The default setting in the -.bst files is:

-
-"xxx.arxiv.org" 'xxxmirror :=
-
- -

By default, the style files generate link targets in the -bibliography with the same name as the citation key. Thus a BibTeX -entry with key surname99, say, would appear in the -generated HTML .bbl file wrapped in <a -name="surname99">...</a>. If this is inconvenient, -perhaps because it conflicts with other links within the file, -then you can adjust the 'hrefprefix variable within the -style file, to specify a prefix which should appear in the link key. -Thus setting

-
-"ref:" 'hrefprefix :=
-
-

in the .bst file would produce links like <a -name="ref:surname99">...</a> in the .bbl -file.

- -

Installation

- -

Nothing to it.... On Unix, for example, put bibhtml -somewhere in your path and make it executable (chmod u+x -bibhtml), and put *.bst somewhere BibTeX -will find it (this means either looking at the -environment variable BSTINPUTS, or running the command -kpsepath bst, if you have it). If you want to use the two-pass variant of the program, then make a symbolic -link with ln -s bibhtml bibhtml2.

- -

If you wish, you may change the distributed BibTeX style files (see -above) to the extent of changing the -`eprint' mirror site from the master xxx.arxiv.org to a -more local mirror. If you don't use the LANL preprint archive, this -will be of no interest to you.

- -

Two-pass bibhtml

- -

You might sometimes have a need to invoke the -two phases separately. If you make a symbolic link to the program via -ln -s bibhtml bibhtml2, then you can generate an -aux-file alone by giving the command bibhtml2 *.html, -say; and you can merge a bbl-file into the bibliography file with the -command bibhtml2 bibliography.bbl. The command line option ---merge above may be more suitable -if you are calling this code from a script, as it requires you to -specify both the .bbl and the .html file it -is being merged with, (and so it is more robust, and more flexible).

- -

On Unix, this works because the program is able to -detect the name it was invoked under. This may be more difficult on other -platforms. If so, please get in touch, with suggestions.

- - -

Example

- -

There are multiple sources of advice for how to cite electronic -documents. The most formal are an ISO standard [ISO 690-2], and the American -Psychological Association's guidance [APA 2003]. As well, there are older, but still useful -discussions in -Walker and -Emory.

- -

We also include here a test entry, -which has some odd characters in the title and URL.

- -

This file was processed with the command bibhtml -r bibhtml -bibhtml.html to produce the document you are reading now.

- -

References

- - -
- -
[apa03] American Psychological Society.
- APA style: Electronic - references. - [Online, cited September 2005]. -
- -
[test] A. N. Experimenter.
- bibhtml tests - how do we handle odd ( &) - characters?. - This is a test entry. -
- -
[iso690] ISO 690-2.
- ISO 690-2, bibliographic references to electronic documents - (excerpts). - [Online, cited September 2005]. -
- -
[emory95] libsf@web.cc.emory.edu.
- Citation - formats. - [Online]. -
- -
[walker95] Janice R Walker.
- MLA-style - citations of electronic sources. - Technical Report 4/95, Department of English, University of South Florida, - January 1995. - Endorsed by the Alliance for Computers and Writing. -
- -
- - - - -

See also the documentation for the urlbst -package, which generates BibTeX style files for ordinary LaTeX -output (which also supports a @webpage entry type, and -url and lastchecked fields), and which -contains a similar list of references concerned with citing online -sources.

- -

Distribution

- -

Changes

- -
- -
1.3, 2006 October 31
-
    -
  • Add hrefprefix parameterisation to style files.
  • -
  • xxx.arxiv.org is now the default e-prints host.
  • -
  • Some improvements to documentation.
  • -
-
- -
1.2, 2005 September 19
-
    -
  • Changes to .bst style files, adding -@webpage entry type, and lastchecked field -to all entry types.
  • -
  • Updates to documentation, fixing broken links to online references -discussing how to cite online sources.
  • -
  • No reports of breakage from beta releases below.
  • -
-
- -
1.2b2, 2005 August 30
-
    -
  • Bugfix -- correctly escape characters in .bbl hrefs
  • -
  • Portability fix -- use /usr/bin/env perl at the top of the -script, rather than /usr/bin/perl; this should be more -portable.
  • -
-
- -
1.2b1, 2005 August 19
-
    -
  • Use processing instructions such as -<?bibhtml start?>, rather than magic comments (the -old behaviour is still temporarily supported).
  • -
  • Add a new directive -- <?bibhtml insert?> -inserts the bibliography in-place.
  • -
  • Debugging output is now written to stderr rather than stdout.
  • -
  • Add --help and --strip options.
  • -
  • Documentation improvements.
  • -
  • Bugfix -- URLs are now properly escaped in the bibliography.
  • -
-
-
- -

Obtaining bibhtml

- -

Bibhtml is available on CTAN at -biblio/bibtex/contrib/bibhtml/, -and at -@HOMEPAGE.

- -

Download the distribution: -bibhtml-1.3.tar.gz.

- -

Do let me know if -you use this stuff. I'd be grateful for any bug reports, -and bug fixes, and also for any comments on the clarity or -otherwise of this documentation.

- -

Licence

- -

This software is copyright, 1999, 2005, Norman Gray. It is released -under the terms of the GNU General Public Licence. See the copyright -declaration at the top of file bibhtml, and the file -LICENCE for the licence conditions. You can find an -online copy of the GPL at http://www.gnu.org/copyleft/gpl.html.

- -
-Norman
-2006 October 31 -
- - - diff --git a/Master/texmf-dist/doc/latex/bibhtml/bibhtml.xslt b/Master/texmf-dist/doc/latex/bibhtml/bibhtml.xslt deleted file mode 100644 index 0980890f171..00000000000 --- a/Master/texmf-dist/doc/latex/bibhtml/bibhtml.xslt +++ /dev/null @@ -1,55 +0,0 @@ - - - - - - - - - - bibstyle - plainhtml - - - - - - citation - - - - - - - - - - \ - - { - - } - - - - -- cgit v1.2.3