diff options
| author | Karl Berry <karl@freefriends.org> | 2019-07-02 20:58:10 +0000 |
|---|---|---|
| committer | Karl Berry <karl@freefriends.org> | 2019-07-02 20:58:10 +0000 |
| commit | 0224d61fd55e2ceab02210fc8d671a3b186293b1 (patch) | |
| tree | 1977220f6d5ed5f2059503449d36c3151afeb5c5 /Master/texmf-dist/doc/bibtex/urlbst | |
| parent | ad5ffc75cdf78f6cf6160e4334d45be15dd48221 (diff) | |
urlbst (2jul19)
git-svn-id: svn://tug.org/texlive/trunk@51530 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf-dist/doc/bibtex/urlbst')
| -rw-r--r-- | Master/texmf-dist/doc/bibtex/urlbst/LICENCE-gpl-2.0.txt | 339 | ||||
| -rw-r--r-- | Master/texmf-dist/doc/bibtex/urlbst/LICENCE-lppl.txt | 416 | ||||
| -rw-r--r-- | Master/texmf-dist/doc/bibtex/urlbst/Makefile.in | 189 | ||||
| -rw-r--r-- | Master/texmf-dist/doc/bibtex/urlbst/README | 436 | ||||
| -rw-r--r-- | Master/texmf-dist/doc/bibtex/urlbst/VERSION | 2 | ||||
| -rw-r--r-- | Master/texmf-dist/doc/bibtex/urlbst/urlbst.bib | 25 | ||||
| -rw-r--r-- | Master/texmf-dist/doc/bibtex/urlbst/urlbst.html | 143 | ||||
| -rw-r--r-- | Master/texmf-dist/doc/bibtex/urlbst/urlbst.html.in | 411 | ||||
| -rw-r--r-- | Master/texmf-dist/doc/bibtex/urlbst/urlbst.in | 91 | ||||
| -rw-r--r-- | Master/texmf-dist/doc/bibtex/urlbst/urlbst.pdf | bin | 210289 -> 205285 bytes | |||
| -rw-r--r-- | Master/texmf-dist/doc/bibtex/urlbst/urlbst.tex | 134 | ||||
| -rw-r--r-- | Master/texmf-dist/doc/bibtex/urlbst/urlbst.tex.in | 282 |
12 files changed, 1132 insertions, 1336 deletions
diff --git a/Master/texmf-dist/doc/bibtex/urlbst/LICENCE-gpl-2.0.txt b/Master/texmf-dist/doc/bibtex/urlbst/LICENCE-gpl-2.0.txt new file mode 100644 index 00000000000..d159169d105 --- /dev/null +++ b/Master/texmf-dist/doc/bibtex/urlbst/LICENCE-gpl-2.0.txt @@ -0,0 +1,339 @@ + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 + + Copyright (C) 1989, 1991 Free Software Foundation, Inc., + 51 Franklin Street, 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 Lesser 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. + + <one line to give the program's name and a brief idea of what it does.> + Copyright (C) <year> <name of author> + + 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 Street, 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. + + <signature of Ty Coon>, 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 Lesser General +Public License instead of this License. diff --git a/Master/texmf-dist/doc/bibtex/urlbst/LICENCE-lppl.txt b/Master/texmf-dist/doc/bibtex/urlbst/LICENCE-lppl.txt new file mode 100644 index 00000000000..22443139013 --- /dev/null +++ b/Master/texmf-dist/doc/bibtex/urlbst/LICENCE-lppl.txt @@ -0,0 +1,416 @@ +The LaTeX Project Public License +=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- + +LPPL Version 1.3c 2008-05-04 + +Copyright 1999 2002-2008 LaTeX3 Project + Everyone is allowed to distribute verbatim copies of this + license document, but modification of it is not allowed. + + +PREAMBLE +======== + +The LaTeX Project Public License (LPPL) is the primary license under +which the LaTeX kernel and the base LaTeX packages are distributed. + +You may use this license for any work of which you hold the copyright +and which you wish to distribute. This license may be particularly +suitable if your work is TeX-related (such as a LaTeX package), but +it is written in such a way that you can use it even if your work is +unrelated to TeX. + +The section `WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE', +below, gives instructions, examples, and recommendations for authors +who are considering distributing their works under this license. + +This license gives conditions under which a work may be distributed +and modified, as well as conditions under which modified versions of +that work may be distributed. + +We, the LaTeX3 Project, believe that the conditions below give you +the freedom to make and distribute modified versions of your work +that conform with whatever technical specifications you wish while +maintaining the availability, integrity, and reliability of +that work. If you do not see how to achieve your goal while +meeting these conditions, then read the document `cfgguide.tex' +and `modguide.tex' in the base LaTeX distribution for suggestions. + + +DEFINITIONS +=========== + +In this license document the following terms are used: + + `Work' + Any work being distributed under this License. + + `Derived Work' + Any work that under any applicable law is derived from the Work. + + `Modification' + Any procedure that produces a Derived Work under any applicable + law -- for example, the production of a file containing an + original file associated with the Work or a significant portion of + such a file, either verbatim or with modifications and/or + translated into another language. + + `Modify' + To apply any procedure that produces a Derived Work under any + applicable law. + + `Distribution' + Making copies of the Work available from one person to another, in + whole or in part. Distribution includes (but is not limited to) + making any electronic components of the Work accessible by + file transfer protocols such as FTP or HTTP or by shared file + systems such as Sun's Network File System (NFS). + + `Compiled Work' + A version of the Work that has been processed into a form where it + is directly usable on a computer system. This processing may + include using installation facilities provided by the Work, + transformations of the Work, copying of components of the Work, or + other activities. Note that modification of any installation + facilities provided by the Work constitutes modification of the Work. + + `Current Maintainer' + A person or persons nominated as such within the Work. If there is + no such explicit nomination then it is the `Copyright Holder' under + any applicable law. + + `Base Interpreter' + A program or process that is normally needed for running or + interpreting a part or the whole of the Work. + + A Base Interpreter may depend on external components but these + are not considered part of the Base Interpreter provided that each + external component clearly identifies itself whenever it is used + interactively. Unless explicitly specified when applying the + license to the Work, the only applicable Base Interpreter is a + `LaTeX-Format' or in the case of files belonging to the + `LaTeX-format' a program implementing the `TeX language'. + + + +CONDITIONS ON DISTRIBUTION AND MODIFICATION +=========================================== + +1. Activities other than distribution and/or modification of the Work +are not covered by this license; they are outside its scope. In +particular, the act of running the Work is not restricted and no +requirements are made concerning any offers of support for the Work. + +2. You may distribute a complete, unmodified copy of the Work as you +received it. Distribution of only part of the Work is considered +modification of the Work, and no right to distribute such a Derived +Work may be assumed under the terms of this clause. + +3. You may distribute a Compiled Work that has been generated from a +complete, unmodified copy of the Work as distributed under Clause 2 +above, as long as that Compiled Work is distributed in such a way that +the recipients may install the Compiled Work on their system exactly +as it would have been installed if they generated a Compiled Work +directly from the Work. + +4. If you are the Current Maintainer of the Work, you may, without +restriction, modify the Work, thus creating a Derived Work. You may +also distribute the Derived Work without restriction, including +Compiled Works generated from the Derived Work. Derived Works +distributed in this manner by the Current Maintainer are considered to +be updated versions of the Work. + +5. If you are not the Current Maintainer of the Work, you may modify +your copy of the Work, thus creating a Derived Work based on the Work, +and compile this Derived Work, thus creating a Compiled Work based on +the Derived Work. + +6. If you are not the Current Maintainer of the Work, you may +distribute a Derived Work provided the following conditions are met +for every component of the Work unless that component clearly states +in the copyright notice that it is exempt from that condition. Only +the Current Maintainer is allowed to add such statements of exemption +to a component of the Work. + + a. If a component of this Derived Work can be a direct replacement + for a component of the Work when that component is used with the + Base Interpreter, then, wherever this component of the Work + identifies itself to the user when used interactively with that + Base Interpreter, the replacement component of this Derived Work + clearly and unambiguously identifies itself as a modified version + of this component to the user when used interactively with that + Base Interpreter. + + b. Every component of the Derived Work contains prominent notices + detailing the nature of the changes to that component, or a + prominent reference to another file that is distributed as part + of the Derived Work and that contains a complete and accurate log + of the changes. + + c. No information in the Derived Work implies that any persons, + including (but not limited to) the authors of the original version + of the Work, provide any support, including (but not limited to) + the reporting and handling of errors, to recipients of the + Derived Work unless those persons have stated explicitly that + they do provide such support for the Derived Work. + + d. You distribute at least one of the following with the Derived Work: + + 1. A complete, unmodified copy of the Work; + if your distribution of a modified component is made by + offering access to copy the modified component from a + designated place, then offering equivalent access to copy + the Work from the same or some similar place meets this + condition, even though third parties are not compelled to + copy the Work along with the modified component; + + 2. Information that is sufficient to obtain a complete, + unmodified copy of the Work. + +7. If you are not the Current Maintainer of the Work, you may +distribute a Compiled Work generated from a Derived Work, as long as +the Derived Work is distributed to all recipients of the Compiled +Work, and as long as the conditions of Clause 6, above, are met with +regard to the Derived Work. + +8. The conditions above are not intended to prohibit, and hence do not +apply to, the modification, by any method, of any component so that it +becomes identical to an updated version of that component of the Work as +it is distributed by the Current Maintainer under Clause 4, above. + +9. Distribution of the Work or any Derived Work in an alternative +format, where the Work or that Derived Work (in whole or in part) is +then produced by applying some process to that format, does not relax or +nullify any sections of this license as they pertain to the results of +applying that process. + +10. a. A Derived Work may be distributed under a different license + provided that license itself honors the conditions listed in + Clause 6 above, in regard to the Work, though it does not have + to honor the rest of the conditions in this license. + + b. If a Derived Work is distributed under a different license, that + Derived Work must provide sufficient documentation as part of + itself to allow each recipient of that Derived Work to honor the + restrictions in Clause 6 above, concerning changes from the Work. + +11. This license places no restrictions on works that are unrelated to +the Work, nor does this license place any restrictions on aggregating +such works with the Work by any means. + +12. Nothing in this license is intended to, or may be used to, prevent +complete compliance by all parties with all applicable laws. + + +NO WARRANTY +=========== + +There is no warranty for the Work. Except when otherwise stated in +writing, the Copyright Holder provides the Work `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 Work is with you. Should the Work prove defective, you assume +the cost of all necessary servicing, repair, or correction. + +In no event unless required by applicable law or agreed to in writing +will The Copyright Holder, or any author named in the components of the +Work, or any other party who may distribute and/or modify the Work as +permitted above, be liable to you for damages, including any general, +special, incidental or consequential damages arising out of any use of +the Work or out of inability to use the Work (including, but not limited +to, loss of data, data being rendered inaccurate, or losses sustained by +anyone as a result of any failure of the Work to operate with any other +programs), even if the Copyright Holder or said author or said other +party has been advised of the possibility of such damages. + + +MAINTENANCE OF THE WORK +======================= + +The Work has the status `author-maintained' if the Copyright Holder +explicitly and prominently states near the primary copyright notice in +the Work that the Work can only be maintained by the Copyright Holder +or simply that it is `author-maintained'. + +The Work has the status `maintained' if there is a Current Maintainer +who has indicated in the Work that they are willing to receive error +reports for the Work (for example, by supplying a valid e-mail +address). It is not required for the Current Maintainer to acknowledge +or act upon these error reports. + +The Work changes from status `maintained' to `unmaintained' if there +is no Current Maintainer, or the person stated to be Current +Maintainer of the work cannot be reached through the indicated means +of communication for a period of six months, and there are no other +significant signs of active maintenance. + +You can become the Current Maintainer of the Work by agreement with +any existing Current Maintainer to take over this role. + +If the Work is unmaintained, you can become the Current Maintainer of +the Work through the following steps: + + 1. Make a reasonable attempt to trace the Current Maintainer (and + the Copyright Holder, if the two differ) through the means of + an Internet or similar search. + + 2. If this search is successful, then enquire whether the Work + is still maintained. + + a. If it is being maintained, then ask the Current Maintainer + to update their communication data within one month. + + b. If the search is unsuccessful or no action to resume active + maintenance is taken by the Current Maintainer, then announce + within the pertinent community your intention to take over + maintenance. (If the Work is a LaTeX work, this could be + done, for example, by posting to comp.text.tex.) + + 3a. If the Current Maintainer is reachable and agrees to pass + maintenance of the Work to you, then this takes effect + immediately upon announcement. + + b. If the Current Maintainer is not reachable and the Copyright + Holder agrees that maintenance of the Work be passed to you, + then this takes effect immediately upon announcement. + + 4. If you make an `intention announcement' as described in 2b. above + and after three months your intention is challenged neither by + the Current Maintainer nor by the Copyright Holder nor by other + people, then you may arrange for the Work to be changed so as + to name you as the (new) Current Maintainer. + + 5. If the previously unreachable Current Maintainer becomes + reachable once more within three months of a change completed + under the terms of 3b) or 4), then that Current Maintainer must + become or remain the Current Maintainer upon request provided + they then update their communication data within one month. + +A change in the Current Maintainer does not, of itself, alter the fact +that the Work is distributed under the LPPL license. + +If you become the Current Maintainer of the Work, you should +immediately provide, within the Work, a prominent and unambiguous +statement of your status as Current Maintainer. You should also +announce your new status to the same pertinent community as +in 2b) above. + + +WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE +====================================================== + +This section contains important instructions, examples, and +recommendations for authors who are considering distributing their +works under this license. These authors are addressed as `you' in +this section. + +Choosing This License or Another License +---------------------------------------- + +If for any part of your work you want or need to use *distribution* +conditions that differ significantly from those in this license, then +do not refer to this license anywhere in your work but, instead, +distribute your work under a different license. You may use the text +of this license as a model for your own license, but your license +should not refer to the LPPL or otherwise give the impression that +your work is distributed under the LPPL. + +The document `modguide.tex' in the base LaTeX distribution explains +the motivation behind the conditions of this license. It explains, +for example, why distributing LaTeX under the GNU General Public +License (GPL) was considered inappropriate. Even if your work is +unrelated to LaTeX, the discussion in `modguide.tex' may still be +relevant, and authors intending to distribute their works under any +license are encouraged to read it. + +A Recommendation on Modification Without Distribution +----------------------------------------------------- + +It is wise never to modify a component of the Work, even for your own +personal use, without also meeting the above conditions for +distributing the modified component. While you might intend that such +modifications will never be distributed, often this will happen by +accident -- you may forget that you have modified that component; or +it may not occur to you when allowing others to access the modified +version that you are thus distributing it and violating the conditions +of this license in ways that could have legal implications and, worse, +cause problems for the community. It is therefore usually in your +best interest to keep your copy of the Work identical with the public +one. Many works provide ways to control the behavior of that work +without altering any of its licensed components. + +How to Use This License +----------------------- + +To use this license, place in each of the components of your work both +an explicit copyright notice including your name and the year the work +was authored and/or last substantially modified. Include also a +statement that the distribution and/or modification of that +component is constrained by the conditions in this license. + +Here is an example of such a notice and statement: + + %% pig.dtx + %% Copyright 2005 M. Y. Name + % + % This work may be distributed and/or modified under the + % conditions of the LaTeX Project Public License, either version 1.3 + % of this license or (at your option) any later version. + % The latest version of this license is in + % http://www.latex-project.org/lppl.txt + % and version 1.3 or later is part of all distributions of LaTeX + % version 2005/12/01 or later. + % + % This work has the LPPL maintenance status `maintained'. + % + % The Current Maintainer of this work is M. Y. Name. + % + % This work consists of the files pig.dtx and pig.ins + % and the derived file pig.sty. + +Given such a notice and statement in a file, the conditions +given in this license document would apply, with the `Work' referring +to the three files `pig.dtx', `pig.ins', and `pig.sty' (the last being +generated from `pig.dtx' using `pig.ins'), the `Base Interpreter' +referring to any `LaTeX-Format', and both `Copyright Holder' and +`Current Maintainer' referring to the person `M. Y. Name'. + +If you do not want the Maintenance section of LPPL to apply to your +Work, change `maintained' above into `author-maintained'. +However, we recommend that you use `maintained', as the Maintenance +section was added in order to ensure that your Work remains useful to +the community even when you can no longer maintain and support it +yourself. + +Derived Works That Are Not Replacements +--------------------------------------- + +Several clauses of the LPPL specify means to provide reliability and +stability for the user community. They therefore concern themselves +with the case that a Derived Work is intended to be used as a +(compatible or incompatible) replacement of the original Work. If +this is not the case (e.g., if a few lines of code are reused for a +completely different task), then clauses 6b and 6d shall not apply. + + +Important Recommendations +------------------------- + + Defining What Constitutes the Work + + The LPPL requires that distributions of the Work contain all the + files of the Work. It is therefore important that you provide a + way for the licensee to determine which files constitute the Work. + This could, for example, be achieved by explicitly listing all the + files of the Work near the copyright notice of each file or by + using a line such as: + + % This work consists of all files listed in manifest.txt. + + in that place. In the absence of an unequivocal list it might be + impossible for the licensee to determine what is considered by you + to comprise the Work and, in such a case, the licensee would be + entitled to make reasonable conjectures as to which files comprise + the Work. + diff --git a/Master/texmf-dist/doc/bibtex/urlbst/Makefile.in b/Master/texmf-dist/doc/bibtex/urlbst/Makefile.in deleted file mode 100644 index 4eba106fa06..00000000000 --- a/Master/texmf-dist/doc/bibtex/urlbst/Makefile.in +++ /dev/null @@ -1,189 +0,0 @@ -# BSTSTYLES are the standard styles that we distribute -BSTSTYLES=plainurl.bst unsrturl.bst alphaurl.bst abbrvurl.bst -# TESTSTYLES are a couple of extra ones that we explicitly test -TESTSTYLES=mlaurl.bst - -MAINTAINER_FILES= Makefile configure -GENERATED=urlbst urlbst.tex urlbst.pdf urlbst.html README VERSION $(BSTSTYLES) -# distribute generated files -# ...plus the configure files -# ...plus the configured files -DISTRIBS=$(GENERATED) \ - configure configure.ac \ - urlbst.in urlbst.bib urlbst.tex.in urlbst.html.in Makefile.in - -prefix=@prefix@ -exec_prefix=@exec_prefix@ -bindir=@bindir@ -DIST=urlbst-@PACKAGE_VERSION@ - -# On OS X, the following avoids extended attributes being included -TAR=COPYFILE_DISABLE=1 tar -#TAR=tar - -### Implicit rules - -# Don't include --inlinelinks when generating %url.bst here, as we -# do want the links visible when generating the documentation, and it's -# probably abetter default in any case. -%url.bst: urlbst - export BSTINPUTS=test: ; \ - if test -z "`kpsewhich ${@:url.bst=.bst}`"; then \ - echo "Can't locate ${@:url.bst=.bst}"; \ - else \ - ./urlbst --eprint --doi --pubmed --hyperref `kpsewhich ${@:url.bst=.bst}` $@; \ - fi - -# Incomplete TeX support -%.ps: %.dvi - dvips -o $@ $< -%.bbl: %.tex plainurl.bst - pdflatex $< - if ! test -f $@ || grep -q 'Citation.*undefined' ${<:.tex=.log}; then \ - bibtex ${<:.tex=}; \ - pdflatex $<; \ - rm ${<:.tex=.pdf}; \ - fi -%.pdf: %.tex %.bbl - pdflatex $< -%.dvi: %.tex %.bbl - latex $< -%.gz: % - gzip --best -f $< - -.PRECIOUS: .bbl - -### Targets start here - -all: urlbst - -dist: $(DIST).tar.gz $(DIST).zip - -$(DIST).tar: $(DIST)/urlbst.in - $(TAR) cf $@ $(DIST) - -$(DIST).zip: $(DIST)/urlbst.in - zip -r $@ $(DIST) - -$(DIST)/urlbst.in: $(DISTRIBS) - if test -d $(DIST); then rm -Rf $(DIST); fi && mkdir $(DIST) - cp $(DISTRIBS) $(DIST) - -# The following appears not to work. -# Perhaps it has to be installed, rather than run from the .app bundle -# (but it doesn't give you any choice about where you install it, -# and I'm not going to put it in a system location) -#PLATYPUS=/Data/LocalApplications/Platypus-4.0/Platypus.app/Contents/Resources/platypus -PLATYPUS=/usr/local/bin/platypus -urlbst.app: urlbst - rm -Rf urlbst.app - $(PLATYPUS) -a urlbst -c "$$PWD/urlbst" -o 'Progress Bar' \ - -p /usr/bin/perl -V @PACKAGE_VERSION@ -u Norman\ Gray -I uk.me.nxg.urlbst \ - -D -R -N CALLED_FROM_PLATYPUS=1 $$PWD/urlbst.app -urlbst-app.zip: urlbst.app - zip -r urlbst-app.zip urlbst.app - -#$(DIST).tar: $(DISTRIBS) -# sed '1s,.*,#! /usr/bin/env perl,' urlbst >tmp && mv tmp urlbst \ -# && chmod +x urlbst -# rm -Rf $(DIST) $(DIST).tar -# mkdir $(DIST) -# cp $(DISTRIBS) $(DIST) -# tar cf $@ $(DIST) -# rm -Rf $(DIST) - -urlbst: urlbst.in config.status - ./config.status urlbst - -urlbst.tex: urlbst.tex.in config.status - ./config.status urlbst.tex - -urlbst.html: urlbst.html.in config.status - ./config.status urlbst.html - -Makefile: Makefile.in config.status - ./config.status Makefile - -configure: configure.ac - autoconf - -config.status: configure - ./configure - -# Version stamp file, included in the distribution for convenience, -# so it's easy to see which version it is has been unpacked at CTAN. -VERSION: - echo $(DIST) >VERSION - -# The README is just a plain-text version of urlbst.html -README: urlbst.html prepare-roff.sed - xsltproc html2roff.xslt urlbst.html \ - | sed -f prepare-roff.sed \ - | nroff -Tutf8 -ms \ - | sed '/XXXEND/,$$d' >README - -# Write a roff file -- there comes a point where a string of -e '' -# commands is more confusing than is safe -# (plus trying to get '$a\' into that is mind-bending). -prepare-roff.sed: - rm -f $@ - { echo '$$a\'; echo '\'; echo 'XXXEND'; echo '/^ *$$/d'; echo 's/^ *//'; echo 's/^\.$$/\&./'; echo 's/^\. /\&. /'; } >$@ - -# Very simple install target -- hardly worth bothering, really.... -install: urlbst - cp urlbst $(bindir) - -# Very simple test target -- just check that we don't bomb converting -# the standard styles -test: $(BSTSTYLES) $(TESTSTYLES) - for f in $(BSTSTYLES) $(TESTSTYLES); do \ - ROOT=`echo $$f|sed s/\.bst$$//`; \ - printf '\\relax\n' > test-$$ROOT.aux; \ - printf '\\citation{*}\n' >> test-$$ROOT.aux; \ - printf '\\bibdata{urlbst}\n' >> test-$$ROOT.aux; \ - printf '\\bibstyle{'"$$ROOT"'}\n' >> test-$$ROOT.aux; \ - bibtex test-$$ROOT; \ - done - -# Brute-force test target, which finds all the system .bst files, -# converts them, and runs BibTeX on them. It doesn't test the results -# in any way -- you have to do that by eye. -# -# No, this is a hopelessly blunderbus approach. And in any case the -# 'locate *.bst' doesn't work. At least the following would find only things -# on the .bst search path. -# BSTPATH=`kpsepath bst` -# for d in `IFS=:; echo $BSTPATH`; do -# dd=`expr "$d" : '!*\(.*[^/]\)/*$'` -# echo dd=$dd -# test -d "$dd" && find $dd -name \*.bst -# done -test-all: - printf '\\relax\n'>test-all.mainaux - sed -n 's/^.*{\(test:.*\),/\\citation{\1}/p' urlbst.bib>>test-all.mainaux - for f in `locate '*.bst' | grep -v norman`; do T=`echo $$f|sed 's+.*/\(.*\)\.bst+\1url+'`;perl urlbst $$f $$T.bst; if test $$? = 0; then TF=test-$$T.aux; cp test-all.mainaux $$TF;printf '\\bibdata{urlbst}\n'>>$$TF; printf '\\bibstyle{$$T}\n'>>$$TF; else rm $$T.bst; fi done - for f in `ls test-*.aux|sed s+.aux++`;do bibtex $$f;done - rm test-all.mainaux - -# Tarball for unpacking in the webpage distribution directory -webpage-tarball.tar: urlbst.pdf urlbst.html $(DIST).tar.gz $(DIST).zip - mkdir webpage-tarball - cp urlbst.pdf $(DIST).tar.gz $(DIST).zip webpage-tarball - cp urlbst.html webpage-tarball/index.html - cd webpage-tarball; $(TAR) cf ../webpage-tarball.tar * - rm -Rf webpage-tarball - -tidy: - rm -f webpage-tarball.tar - rm -f *~ test-* - rm -f *.aux *.bbl *.log *.blg *.dvi *.pdf - rm -Rf urlbst.app - -clean: tidy - rm -f *.bst - rm -Rf config.status autom4te.cache prepare-roff.sed - rm -Rf $(DIST).tar $(DIST).tar.gz $(DIST).zip $(DIST) - rm -f $(GENERATED) - -maintainer-clean: clean - rm -f $(MAINTAINER_FILES) diff --git a/Master/texmf-dist/doc/bibtex/urlbst/README b/Master/texmf-dist/doc/bibtex/urlbst/README index 38dfabd93d0..d9705a58402 100644 --- a/Master/texmf-dist/doc/bibtex/urlbst/README +++ b/Master/texmf-dist/doc/bibtex/urlbst/README @@ -1,383 +1,53 @@ - - - - - - - - - - UUrrllbbsstt - - - - _A_B_S_T_R_A_C_T - - A script to add a wweebbppaaggee BibTeX entry type, - and add support for general uurrll and llaassttcchheecckkeedd - fields, to (most) BibTeX ..bbsstt files. Optionally - adds basic support for eepprriinntt , ddooii and ppuubbmmeedd - fields, and hypertex/hyperref support. - - The Persistent URL for this page is - hhttttpp::////ppuurrll..oorrgg//nnxxgg//ddiisstt//uurrllbbsstt &. - - Version 0.7, 2011 July 20. - - - Contents - -* Usage - -* For example... - -* Download and installation - -* Further Information - -* Version history - - The standard BibTeX styles have no explicit support for -the web, in that they include no ‘webpage’ type, and have no -support for adding URLs to references. There are rumours -that such support might appear in BibTeX 1.0, but there is -no estimate of when that is likely to arrive. - - The Perl script uurrllbbsstt can be used to add this support -to an arbitrary ..bbsstt file which has a reasonably ‘conven‐ -tional’ structure. The result is meant to be robust rather -than pretty. - - It has a different goal from Patrick Daly’s ‘custom‐ -bib’ package ‐‐ that is intended to create a BibTeX style -.bst file from scratch, and supports ‘url’ and ‘eprint’ -fields. This package, on the other hand, is intended for -the case where you already have a style file that works (or -at least, which you cannot or will not change), and edits it -to add the new webpage entry type, plus the url, lastchecked -and eprint fields. Fuller details are in the manual. - -11.. UUssaaggee - - uurrllbbsstt [[‐‐‐‐[[nnoo]]eepprriinntt]] [[‐‐‐‐[[nnoo]]ddooii]] [[‐‐‐‐[[nnoo]]ppuubbmmeedd]] - [[‐‐‐‐iinnlliinneelliinnkkss]] [[‐‐‐‐nnoohhyyppeerrlliinnkkss]] [[‐‐‐‐hhyyppeerrtteexx]] [[‐‐‐‐hhyyppeerr‐‐ - rreeff]] [[‐‐‐‐lliitteerraall kkeeyy==vvaalluuee]] [[iinnppuutt‐‐ffiillee [[oouuttppuutt‐‐ffiillee]]]] - - If either the input‐file or the output‐file is omitted, -they default to stdin and stdout respectively. If the input -file already has a URL entry type, then the script objects. -By default (in the current version), the output includes -support for eprint, doi and pubmed, but these can be dis‐ -abled by ‐‐‐‐nnooeepprriinntt , ‐‐‐‐nnooddooii and ‐‐‐‐nnooppuubbmmeedd , respectively. - - The added fields are: - -* uurrll and llaassttcchheecckkeedd , to associate a URL with a refer‐ - ence, along with the date at which the URL was last - checked to exist; - -* ddooii , for a reference’s DOI; - -* eepprriinntt , for an arXiv eprint reference; and - -* ppuubbmmeedd for a reference’s PubMed identifier (PMID). - - If either of the ‐‐‐‐hhyyppeerrtteexx or ‐‐‐‐hhyyppeerrrreeff options is -present, then the generated ..bbsstt file includes support for -hyperlinks in the generated eprint entries in the bibliogra‐ -phy, with the format being either HyperTeX (see arXiv, -again), supported by xdvi, dvips and others, or using the -support available from the hyperref package. These options -have no effect unless one of the ‐‐‐‐eepprriinntt or ‐‐‐‐ddooii options -is given: when URLs are included in the bibliography, they -are written out using the rrll{{......}} command, and hyperref -automatically processes that in the correct way to include a -hyperlink. - - The ‐‐‐‐iinnlliinneelliinnkkss option tells urlbst not to write out -the URL as text within the bibliography entry. Instead, -urlbst will produce a more conventional‐looking and compact -bibliography entry, but the entry’s title will now be a -hyperlink to that URL. This hyperlink may be useful to any‐ -one who reads your document online (this option can only be -used with ‐‐‐‐hhyyppeerrrreeff or ‐‐‐‐hhyyppeerrtteexx ). Any DOI or eprint -text which would be produced as a result of the appropriate -option will still appear in this mode. - - You may adjust various literal strings, either for the -purposes of internationalisation, or simply because you pre‐ -fer different text. To do this, give the ‐‐‐‐lliitteerraall option, -followed by a kkeeyy==vvaalluuee pair, for example ‐‐‐‐lliitteerraall -oonnlliinnee==""oonn tthh’’iinntteerrtt0000bbss"" , to replace the default UURRLL:: -text. The possible values, and their defaults, are below -(say ‐‐‐‐lliitteerraall hheellpp to get this list printed out): keyword‐ -defaultmeaning citedcitedindicator of citation, or "last -checked", date doiprefixdoi:text printed before DOI eprint‐ -prefixarXiv:text printed before eprint ref link‐ -text[link]fallback link text pubmedprefixPMID:text printed -before PUBMED reference onlineonlineindication that resource -is online urlintroURL:location of online resource (an alter‐ -native is "Available from:") - - The distribution includes preconverted versions of the -four standard BibTeX .bst style files. - - Only the style files which result from conversion of -the standard styles are checked in the regression tests. -Other style files which are known to work include acm.bst, -amsalpha.bst, amsplain.bst, apalike.bst, gerabbrv.bst, ger‐ -alpha.bst, gerapali.bst, gerplain.bst, gerunsrt.bst, -ieeetr.bst, siam.bst, mla.bst - - Style files which are known to fail: - -* Currently (as of at least v0.5), there exists a style - aacchhiiccaaggoo..bbsstt which seems to fox uurrllbbsstt ; it turns out - that there’s a simpler but almost equivalent style - cchhiiccaaggoo..bbsstt which works. - -* Some APA‐like styles, including at least aappaaggeerr..bbsstt , - seem to be sufficiently different from the most common - styles, that they confuse uurrllbbsstt completely. - -* The _k_o_m_a_‐_s_c_r_i_p_t styles and the _r_e_f_e_r styles are not - designed to produce conventional ..bbbbll files, and uurrllbbsstt - does not aim to produce anything useful from these. - - This might be a good time for me to revisit the rather -convoluted logic within the script, to make it a little more -robust in the face of variants like these, but don’t hold -your breath. The logic within the script is pretty hideous -(it essentially works by spotting patterns in the input -style file, and replacing or extending bits of BibTeX style‐ -file code. This is a fragile technique, and is probably at -the limits of its usefulness, therefore I’d take some per‐ -suading to add significant extra functionality to the -script. - - The natbib and revtex style files already have URL -fields. If you have a BibTeX style file which you think -ought to work, but with which the script fails, send it to -me, and I’ll try to work out what I’ve missed (no promises, -though). - - Note that the command to invoke the script changed from -‘urlbst.pl’ to plain ‘urlbst’ between versions 0.3 and 0.4. - -22.. FFoorr eexxaammppllee...... - - To add URL support to the standard ssiiaamm..bbsstt file, you -can give the command - - %% uurrllbbsstt //ppaatthh//ttoo//oorriiggiinnaall//ssiiaamm..bbsstt ssiiaammuurrll..bbsstt - - Your TeX installation will likely have some way of -helping you find where the original ..bbsstt files are. On -teTeX‐based systems, for example, the command kkppsseewwhhiicchh -ssiiaamm..bbsstt returns the full path of the ssiiaamm..bbsstt file which -BibTeX would find. - - The distributed files aabbbbrrvvuurrll..bbsstt , aallpphhaauurrll..bbsstt , -ppllaaiinnuurrll..bbsstt and uunnssrrttuurrll..bbsstt are versions of the standard -style files which have been pre‐converted. - - There is more general discussion of including URLs in -bibliographies in the UK TeX FAQ. - -33.. DDoowwnnllooaadd aanndd iinnssttaallllaattiioonn - - Download the file as a tarball or zip file and unpack -it. Or you can clone the source repository at bit‐ -bucket.org. - - To install, you should simply copy the distributed -uurrllbbsstt script to someplace on the path (such as -//uussrr//llooccaall//bbiinn , or ~~//llooccaall//bbiinn , depending on your privi‐ -leges and tastes). - - If you (might) want to use the pre‐converted standard -..bbsstt files, then you’ll need to copy these to somewhere in -the BibTeX search path. Type kpsepath bst on Unix to find -out the list of places BibTeX searches, and pick either one -of the user‐local locations, or a system‐wide one. If -you’re installing in a system‐wide location, you’ll need -admin privileges, obviously, and you will probably need to -use tteexxhhaasshh , mmkktteexxllssrr or its equivalent, to update LaTeX’s -filename cache. For further hints here, see the TeX FAQ -entries on installing a package and where LaTeX puts files. - - That should be all you have to do. - - The urlbst script is distributed with a path which -should just work, as long as the Perl binary is in your -path, but if you have problems here, then you might want to -change the first line to something like - - ##!! //uussrr//llooccaall//bbiinn//ppeerrll - - if that’s where your Perl binary is. - - You can also use the conventional ..//ccoonnffiigguurree;; mmaakkee;; -mmaakkee iinnssttaallll to configure and install the package (as root, -or using ssuuddoo if you’re installing it in a system location), -though you still have to install the ..bbsstt files by hand. -This is rather heavyweight for the trivial amount of config‐ -uration required, so it’s almost always simpler just to do -things by hand. - - If you need to change some of the uurrllbbsstt defaults, how‐ -ever, or if your fingers type ..//ccoonnffiigguurree spontaneously, -then you can be reassured that the configure script supports -the standard ‐‐‐‐pprreeffiixx option, plus the following options -setting defaults: - - ‐‐‐‐wwiitthh‐‐eepprriinnttss==uurrll , ‐‐‐‐wwiitthhoouutt‐‐eepprriinnttss This makes the - ‐‐‐‐eepprriinnttss option to urlbst available by default, and - allows you to optionally specify a prefix for creating - URLs from eprint numbers. The default for this URL is - hhttttpp::////aarrxxiivv..oorrgg//aabbss// ‐‐ this is appropriate for arXiv, - obviously, but there are now a variety of other pre‐ - print archives appearing, for which this might be inap‐ - propriate. If you have comments on this default, or - alternatives, please let me know. This option is - enabled by default; if you have some reason for dis‐ - abling the ‐‐‐‐eepprriinnttss option for urlbst, the give the - configure option ‐‐‐‐wwiitthhoouutt‐‐eepprriinnttss - - ‐‐‐‐wwiitthh‐‐ddooii==uurrll , ‐‐‐‐wwiitthhoouutt‐‐ddooii This makes available the - ‐‐‐‐ddooii option to urlbst and, as with the ‐‐‐‐wwiitthh‐‐eepprriinnttss - option, allows you to customise the DOI resolver URL. - The ‐‐‐‐ddooii option to urlbst is on by default. - - ‐‐‐‐wwiitthh‐‐hhrreeff==00//11//22 This allows you to specify the type - of hyperlinks which are inserted in the bibliography. - Values 0, 1 and 2, indicating no hyperlinks, hypertex‐ - style links, and hyperref‐style links, respectively. - The default is ‐‐‐‐wwiitthh‐‐hhrreeff==00 &. The hhyyppeerrrreeff ‐style - option is intended to complement the increasingly stan‐ - dard hhyyppeerrrreeff package. - - The first two options simply change defaults, and if -you never use the new eepprriinnttss or ddooii fields, then the -defaults don’t matter to you. - - Since the modified style generates URLs wrapped in the -rrll{{}} macro, it is useful to use the resulting bibliography -style alongside the uurrll package. Since this tends to work -with hhyyppeerrrreeff anyway, where possible, you don’t get any -extra goodness by changing the ‐‐‐‐wwiitthh‐‐hhrreeff default at con‐ -figuration time. - -33..11.. DDooccuummeennttaattiioonn - - Basic documentation is in the file uurrllbbsstt..tteexx &. This -is distributed as a PDF file, but if you want to regenerate -it, use - - %% llaatteexx uurrllbbsstt %% bbiibbtteexx uurrllbbsstt %% llaatteexx uurrllbbsstt %% llaatteexx - uurrllbbsstt - -44.. FFuurrtthheerr IInnffoorrmmaattiioonn aanndd aacckknnoowwlleeddggeemmeennttss - - uurrllbbsstt is archived on CTAN at bbiibblliioo//bbiibbtteexx//ccoonn‐‐ -ttrriibb//uurrllbbsstt// , and discussed in the TeX FAQ. - - The source code for the package is maintained at bit‐ -bucket.org, which also includes an issue tracker, where you -can report bugs (or just mail me). - - The home page of urlbst might possibly have more recent -versions than the one you’re looking at now. - - Thanks are due to many people for suggestions and -requests, and to ’ijvm’ for code contributions. - - Copyright 2002‐11, Norman Gray. Released under the -terms of the GNU General Public Licence. - -55.. VVeerrssiioonn hhiissttoorryy - - _0_._7_, Add ‐‐nodoi, ‐‐noeprints and ‐‐nopubmed options - (which defaulted on, and couldn’t otherwise be turned - off) - - 00..77bb11,, 22001111 MMaarrcchh 1177 Allow parameterisation of literal - strings, with option ‐‐‐‐lliitteerraall &. - - 00..66‐‐55,, 22001111 MMaarrcchh 88 Adjust support for inline links - (should now work for arXiv, DOI and Pubmed) - - 00..66‐‐44,, 22000099 AApprriill 2288 Work around BibTeX linebreaking - bug (thanks to Andras Salamon for the bug report). - - 00..66‐‐33,, 22000099 AApprriill 1199 Fix inline link generation (thanks - to Eric Chamberland for the bug report). - - 00..66‐‐22,, 22000088 NNoovveemmbbeerr 1177 We now turn on inlinelinks when - we spot format.vol.num.pages, which means we include - links for those styles which don’t include a title in - the citation (common for articles in physical science - styles, such as aip.sty). - - 00..66‐‐11,, 22000088 JJuunnee 1166 Fixed some broken links to the var‐ - ious citation standards (I think in this context this - should probably _n_o_t be happening, yes?). The distrib‐ - uted **uurrll..bbsstt no longer have the ‐‐‐‐iinnlliinneelliinnkkss option - turned on by default. - - _0_._6_, _2_0_0_7 _M_a_r_c_h _2_6 - - Added the option ‐‐‐‐iinnlliinneelliinnkkss , which adds inline -hyperlinks to any bibliography entries which have URLs, but -does so inline, rather than printing the URL explicitly in -the bibliography. This is (primarily) useful if you’re pre‐ -paring a version of a document which will be read on‐screen. -Thanks to Jason Eisner for the suggestion, and much testing. - - Incorporate hyperref bugfixes from PaweÅ Widera. - - 00..66bb33 Further reworkings of the inlinelinks support, so - that it’s now fired by a format.title (or format.bti‐ - tle) line, with a fallback in fin.entry. This should - be more robust, and allows me to delete some of the - previous version’s gymnastics. - - 00..66bb22 Reworked iinnlliinneelliinnkkss support; should now be more - robust. Incorporate hyperref bugfixes from PaweÅ - Widera. - - 00..66bb11 Added the option iinnlliinneelliinnkkss , which adds inline - hyperlinks to any bibliography entries which have URLs, - but does so inline, rather than printing the URL - explicitly in the bibliography. This is (only) useful - if you’re preparing a version of a document which will - be read on‐screen. - - 00..55..22,, 22000066 SSeepptteemmbbeerr 66 Another set of documentation‐ - only changes, hopefully clarifying installation. - - 00..55..11,, 22000066 JJaannuuaarryy 1100 No functionality changes. Docu‐ - mentation and webpage changes only, hopefully clarify‐ - ing usage and configuration - - _0_._5_, _2_0_0_5 _J_u_n_e _3 Added support for Digital Object Iden‐ - tifiers (DOI) fields in bibliographies. - - 00..44‐‐11,, 22000055 AApprriill 1122 Documentation improvements ‐‐ - there are now examples in the help text! - - _0_._4_, _2_0_0_4 _D_e_c_e_m_b_e_r _1 Bug fixes: now compatible with - mla.bst and friends. Now uses ..//ccoonnffiigguurree (option‐ - ally). Assorted reorganisation. - - _0_._3_, _2_0_0_3 _J_u_n_e _4 Added ‐‐eprint, ‐‐hypertex and - ‐‐hyperref options. - - _0_._2_, _2_0_0_2 _O_c_t_o_b_e_r _2_3 The ‘editor’ field is now sup‐ - ported in the webpage entry type. Basic documentation - added. - - _0_._1_, _2_0_0_2 _A_p_r_i_l Initial version - - Norman Gray 2011 July 20 - +urlbst -- add @webpage entry and url/doi/eprint/pubmed fields to BibTeX +======================================================================= + +Version 0.8, 2019 July 1. + +The urlbst package consists of a Perl script which edits BibTeX style +files (.bst) to add a `@webpage` entry type, and which adds a few new +fields -- notably including 'url' -- to all other entry types. The +distribution includes preconverted versions of the four standard +BibTeX .bst style files. + +It has a different goal from Patrick Daly's 'custom-bib' package -- +that is intended to create a BibTeX style .bst file from scratch, and +supports 'url' and 'eprint' fields. This package, on the other hand, +is intended for the case where you already have a style file that +works (or at least, which you cannot or will not change), and edits it +to add the new `@webpage` entry type, plus the new fields. + +The added fields are: + + * 'url' and 'lastchecked', to associate a URL with a reference, + along with the date at which the URL was last checked to exist; + * 'doi', for a reference's DOI (see https://doi.org); + * 'eprint', for an arXiv eprint reference (see http://arxiv.org); and + * 'pubmed' for a reference's PubMed identifier (PMID, see http://pubmed.gov). + +Licences +-------- + +The copyright and licence position for the modified `.bst` files seems +slightly muddy to me. On the grounds that any licence is better than +no licence, I therefore assert that the _modifications_ which the +`urlbst` program makes to these files are copyright 2002-03, 2005-12, 2014, 2019, +Norman Gray, and that these modifications are available for +distribution under the terms of the LaTeX Project Public Licence. + +The original `.bst` files are copyright Howard Trickey and Oren +Patashnik, with a set of permissions, in text at the top of the files, +which state that "Unlimited copying and redistribution of this file +are permitted as long as it is unmodified" (see the files for the +complete text). The distribution terms above therefore appear to be +compatible with -- in the sense of being morally equivalent to -- +these terms in the `.bst` file. If anyone disagrees with the logic +here, I'd be very happy to discuss that. + +The `urlbst` script itself is distributed under the GPL, version 2.0. + +See the files `LICENCE-lppl.txt` and `LICENCE-gpl-2.0.txt` in the +distribution, for the relevant licence text. + + +Norman Gray +http://nxg.me.uk diff --git a/Master/texmf-dist/doc/bibtex/urlbst/VERSION b/Master/texmf-dist/doc/bibtex/urlbst/VERSION index a404769b324..e2effdb0802 100644 --- a/Master/texmf-dist/doc/bibtex/urlbst/VERSION +++ b/Master/texmf-dist/doc/bibtex/urlbst/VERSION @@ -1 +1 @@ -urlbst-0.7 +urlbst-0.8 diff --git a/Master/texmf-dist/doc/bibtex/urlbst/urlbst.bib b/Master/texmf-dist/doc/bibtex/urlbst/urlbst.bib index 53001b96787..c51ed5d2221 100644 --- a/Master/texmf-dist/doc/bibtex/urlbst/urlbst.bib +++ b/Master/texmf-dist/doc/bibtex/urlbst/urlbst.bib @@ -11,6 +11,7 @@ @Manual{apastyle, title = {Publication Manual of the American Psychological Association}, organization = {{American Psychological Association}}, + key = "APA", edition = {6th}, year = 2009, lastchecked = {17 March 2011}, @@ -24,17 +25,7 @@ lastchecked = {17 March 2011} } -% This one appears to be dead -@Webpage{gone:classroom96, - title = {Citing Internet Addresses: how students should - reference online sources in their bibliographies}, - year = 1996, - month = mar, - key = {Classroom}, - url = "http://www.classroom.net/classroom/CitingNetResources.html" -} - -@XXXWebpage{emory95, +Webpage{emory95, author = {{Goizueta Business Library}}, title = "Citation Formats", date = {1997}, @@ -161,7 +152,6 @@ } % Article with a DOI -% an underscore @article{test:gray00c, author = "Norman Gray", title = "Automatic Reduction of Elliptic Integrals using @@ -172,6 +162,17 @@ year = 2002, doi = {10.1090/S0025-5718-01-01333-3} } + +% Article with a DOI and a URL which refers to the same resource as the DOI +% (we shouldn't get both in the output) +@Article{test:doi2, + author = {A N Other}, + title = {Fun with {DOIs}}, + journal = {Journal of Indirection}, + year = 1999, + doi = {10.1234/5678}, + url = {https://doi.org/10.1234/5678} +} % Article with a PUBMED reference diff --git a/Master/texmf-dist/doc/bibtex/urlbst/urlbst.html b/Master/texmf-dist/doc/bibtex/urlbst/urlbst.html index c057564bd63..1edeadcf3a0 100644 --- a/Master/texmf-dist/doc/bibtex/urlbst/urlbst.html +++ b/Master/texmf-dist/doc/bibtex/urlbst/urlbst.html @@ -4,8 +4,7 @@ <head> <title>Urlbst</title> <link href="http://nxg.me.uk/" rev="author"/> -<link type="text/css" rel="stylesheet" - href="http://nxg.me.uk/style/base.css"/> +<link type="text/css" rel="stylesheet" href="/style/base.css"/> </head> <body> @@ -18,9 +17,11 @@ basic support for <code>eprint</code>, <code>doi</code> and <code>pubmed</code> hypertex/hyperref support.</p> <p>The Persistent URL for this page is -<code>http://purl.org/nxg/dist/urlbst</code>.</p> +<code>http://purl.org/nxg/dist/urlbst</code>. +The code (and bugparade) is on +<a href='https://bitbucket.org/nxg/urlbst/'>bitbucket.org</a>.</p> -<p>Version 0.7, 2011 July 20.</p> +<p>Version 0.8, 2019 July 1.</p> </div> <p>Contents</p> @@ -28,8 +29,9 @@ hypertex/hyperref support.</p> <li><a href='#usage'>Usage</a></li> <li><a href='#example'>For example...</a></li> <li><a href='#download'>Download and installation</a></li> +<li><a href='#licences'>Licences</a></li> <li><a href='#information'>Further Information</a></li> -<li><a href='#history'>Version history</a></li> +<li><a href='#history'>Version history, and release notes</a></li> </ul> <p>The standard BibTeX styles have no explicit support for the web, in @@ -70,9 +72,9 @@ by <code>--noeprint</code>, <code>--nodoi</code> and <li><code>url</code> and <code>lastchecked</code>, to associate a URL with a reference, along with the date at which the URL was last checked to exist;</li> -<li><code>doi</code>, for a reference's <a href='http://doi.org'>DOI</a>;</li> +<li><code>doi</code>, for a reference's <a href='https://doi.org'>DOI</a>;</li> <li><code>eprint</code>, for an <a href='http://arxiv.org'>arXiv</a> eprint reference; and</li> -<li><code>pubmed</code> for a reference's +<li><code>pubmed</code> for a reference's <a href='http://pubmed.gov'>PubMed</a> identifier (PMID).</li> </ul> @@ -186,10 +188,10 @@ FAQ</a>.</p> <h2><a name='download'>Download and installation</a></h2> <p>Download the file as a -<a href="urlbst-0.7.tar.gz" >tarball</a> +<a href="urlbst-0.8.tar.gz" >tarball</a> or -<a href="urlbst-0.7.zip" >zip file</a> -and unpack it. Or you can clone the source repository at +<a href="urlbst-0.8.zip" >zip file</a> +and unpack it. Or you can clone the source repository at <a href='http://bitbucket.org/nxg/urlbst/'>bitbucket.org</a>.</p> <p>To install, you should simply copy the distributed @@ -201,11 +203,11 @@ your privileges and tastes).</p> <code>.bst</code> files, then you'll need to copy these to somewhere in the BibTeX search path. Type <kbd>kpsepath bst</kbd> on Unix to find out the list of places BibTeX searches, and pick either one of -the user-local locations, or a system-wide one. If you're installing +the user-local locations, or a system-wide one. If you're installing in a system-wide location, you'll need admin privileges, obviously, and you will probably need to use <code>texhash</code>, <code>mktexlsr</code> or its equivalent, to update LaTeX's filename -cache. For further hints here, see +cache. For further hints here, see the TeX FAQ entries on <a href='http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instpackages' >installing a package</a> and <a @@ -289,16 +291,41 @@ is distributed as a PDF file, but if you want to regenerate it, use</p> % latex urlbst </pre> +<h2><a name='licences'>Licences</a></h2> + +<!-- this text copied from the README.md --> +<p>The copyright and licence position for the modified <code>.bst</code> files seems +slightly muddy to me. On the grounds that any licence is better than +no licence, I therefore assert that the <em>modifications</em> which the +<code>urlbst</code> program makes to these files are copyright 2002-03, 2005-12, 2014, 2019, +Norman Gray, and that these modifications are available for +distribution under the terms of the LaTeX Project Public Licence.</p> + +<p>The original <code>.bst</code> files are copyright Howard Trickey and Oren +Patashnik, with a set of permissions, in text at the top of the files, +which state that "Unlimited copying and redistribution of this file +are permitted as long as it is unmodified" (see the files for the +complete text). The distribution terms above therefore appear to be +compatible with -- in the sense of being morally equivalent to -- +these terms in the <code>.bst</code> file. If anyone disagrees with +the logic here, I'd be very happy to discuss that.</p> + +<p>The <code>urlbst</code> script itself is distributed under the GPL, version 2.0.</p> + +<p>See the files <code>LICENCE-lppl.txt</code> and <code>LICENCE-gpl-2.0.txt</code> in the +distribution, for the relevant licence text.</p> + + <h2><a name='information'>Further Information and acknowledgements</a></h2> -<p><code>urlbst</code> is archived on CTAN at <a -href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/urlbst/" -><code>biblio/bibtex/contrib/urlbst/</code></a>, and discussed in the +<p><code>urlbst</code> is archived <a +href='https://ctan.org/pkg/urlbst' +>on CTAN</a>, and discussed in the <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=citeURL" >TeX FAQ</a>.</p> -<p>The source code for the package is maintained at -<a href='http://bitbucket.org/nxg/urlbst/'>bitbucket.org</a>, +<p>The source code for the package is maintained at +<a href='http://bitbucket.org/nxg/urlbst/'>bitbucket.org</a>, which also includes an issue tracker, where you can report bugs (or just mail me).</p> @@ -306,16 +333,39 @@ just mail me).</p> >home page of urlbst</a> might possibly have more recent versions than the one you're looking at now.</p> -<p>Thanks are due to many people for suggestions and requests, -and to 'ijvm' for code contributions.</p> -<p>Copyright 2002-11, Norman Gray. Released under the terms of the GNU -General Public Licence.</p> +<h2><a name='history'>Acknowledgements, and release notes</a></h2> + +<!-- include:release-notes.html --> +<div xmlns='http://www.w3.org/1999/xhtml'> + +<p>Thanks are due to many people for suggestions and requests: +to Jason Eisner for suggesting the <code>--inlinelinks</code> option; +to ‘ijvm’ for code contributions in the <code>urlbst</code> script; +to Paweł Widera for the suggestion to use <code>\path</code> when formatting DOIs; +to Michael Giffin for the suggestion to include PubMed URLs; +to Katrin Leinweber for the pull request which fixed the format of DOI +references.</p> -<h2><a name='history'>Version history</a></h2> <dl> -<dt><strong>0.7, </strong></dt> -<dd>Add --nodoi, --noeprints and --nopubmed options (which defaulted +<dt><strong>0.8, 2019 July 1</strong></dt> +<dd><ul> +<li>The presence of a preexisting <code>format.doi</code>, +<code>format.eprint</code> or <code>format.pubmed</code> function is +now detected, and warned about. The resulting <code>.bst</code> file +might still require some manual editing. +Resolves <a href='https://bitbucket.org/nxg/urlbst/issue/8'>issue 8</a>.</li> +<li>Clarified licences (I hope).</li> +<li>Adjust format of DOI resolver. +Resolves <a href='https://bitbucket.org/nxg/urlbst/issue/11'>issue 11</a>, +thanks to +<a href='https://bitbucket.org/nxg/urlbst/pull-requests/1/' +>code contributed by Katrin Leinweber</a>.</li> +</ul> +</dd> + +<dt>0.7, 2011 July 20</dt> +<dd>Add <code>--nodoi</code>, <code>--noeprints</code> and <code>--nopubmed</code> options (which defaulted on, and couldn't otherwise be turned off)</dd> <dt>0.7b1, 2011 March 17</dt> @@ -338,35 +388,34 @@ such as aip.sty).</dd> <dt>0.6-1, 2008 June 16</dt> <dd>Fixed some broken links to the various citation standards -(I think in this context this should probably <em>not</em> be happening, yes?). +(I think in this context this should probably <em>not</em> be happening, yes?). The distributed <code>*url.bst</code> no longer have the <code>--inlinelinks</code> option turned on by default.</dd> <dt><strong>0.6, 2007 March 26</strong></dt> -<dd><p>Added the option <code>--inlinelinks</code>, which adds inline hyperlinks +<dd><ul> +<li>Added the option <code>--inlinelinks</code>, which adds inline hyperlinks to any bibliography entries which have URLs, but does so inline, rather than printing the URL explicitly in the bibliography. This is (primarily) useful if you're preparing a version of a document which will be read -on-screen. Thanks to Jason Eisner for the suggestion, and much testing.</p> -<p>Incorporate hyperref bugfixes from Paweł Widera.</p> -<dl> -<dt>0.6b3</dt> -<dd>Further reworkings of the inlinelinks support, so that it's now -fired by a format.title (or format.btitle) line, with a fallback in -fin.entry. This should be more robust, and allows me to delete some -of the previous version's gymnastics.</dd> - -<dt>0.6b2</dt> -<dd>Reworked <code>inlinelinks</code> support; should now be more -robust. Incorporate hyperref bugfixes from Paweł Widera.</dd> - -<dt>0.6b1</dt> -<dd>Added the option <code>inlinelinks</code>, which adds inline hyperlinks +on-screen. Thanks to Jason Eisner for the suggestion, and much testing.</li> + +<li>Incorporate hyperref bugfixes from Paweł Widera.</li> + +<li>Further reworkings of the inlinelinks support, so that it's now +fired by a <code>format.title</code> (or <code>format.btitle</code>) line, with a fallback in +<code>fin.entry</code>. This should be more robust, and allows me to delete some +of the previous version's gymnastics.</li> + +<li>Reworked <code>inlinelinks</code> support; should now be more +robust. Incorporate hyperref bugfixes from Paweł Widera.</li> + +<li>Added the option <code>inlinelinks</code>, which adds inline hyperlinks to any bibliography entries which have URLs, but does so inline, rather than printing the URL explicitly in the bibliography. This is (only) useful if you're preparing a version of a document which will be read -on-screen.</dd> -</dl> +on-screen.</li> +</ul> </dd> <dt>0.5.2, 2006 September 6</dt> @@ -389,7 +438,7 @@ bibliographies.</dd> Now uses <code>./configure</code> (optionally). Assorted reorganisation.</dd> <dt><strong>0.3, 2003 June 4</strong></dt> -<dd>Added --eprint, --hypertex and --hyperref options.</dd> +<dd>Added <code>--eprint</code>, <code>--hypertex</code> and <code>--hyperref</code> options.</dd> <dt><strong>0.2, 2002 October 23</strong></dt> <dd>The `editor' field is now supported in the webpage entry type. Basic @@ -397,14 +446,16 @@ documentation added.</dd> <dt><strong>0.1, 2002 April</strong></dt> <dd>Initial version</dd> - </dl> +</div> +<p>Copyright 2002-03, 2005-12, 2014, 2019, Norman Gray. Released under the terms of the GNU +General Public Licence.</p> <div class="signature"> <a href="http://nxg.me.uk" >Norman Gray</a><br/> -2011 July 20 +2019 July 1 </div> </body> diff --git a/Master/texmf-dist/doc/bibtex/urlbst/urlbst.html.in b/Master/texmf-dist/doc/bibtex/urlbst/urlbst.html.in deleted file mode 100644 index 68a725cc017..00000000000 --- a/Master/texmf-dist/doc/bibtex/urlbst/urlbst.html.in +++ /dev/null @@ -1,411 +0,0 @@ -<?xml version="1.0"?> - -<html xmlns="http://www.w3.org/1999/xhtml"> -<head> -<title>Urlbst</title> -<link href="http://nxg.me.uk/" rev="author"/> -<link type="text/css" rel="stylesheet" - href="http://nxg.me.uk/style/base.css"/> -</head> - -<body> -<h1>Urlbst</h1> -<div class="abstract"> -<p>A script to add a <code>webpage</code> BibTeX entry type, and add -support for general <code>url</code> and <code>lastchecked</code> -fields, to (most) BibTeX <code>.bst</code> files. Optionally adds -basic support for <code>eprint</code>, <code>doi</code> and <code>pubmed</code> fields, and -hypertex/hyperref support.</p> - -<p>The Persistent URL for this page is -<code>http://purl.org/nxg/dist/urlbst</code>.</p> - -<p>Version @PACKAGE_VERSION@, @RELEASEDATE@.</p> -</div> - -<p>Contents</p> -<ul> -<li><a href='#usage'>Usage</a></li> -<li><a href='#example'>For example...</a></li> -<li><a href='#download'>Download and installation</a></li> -<li><a href='#information'>Further Information</a></li> -<li><a href='#history'>Version history</a></li> -</ul> - -<p>The standard BibTeX styles have no explicit support for the web, in -that they include no `webpage' type, and have no support for adding -URLs to references. There are rumours that such support might appear -in BibTeX 1.0, but there is no estimate of when that is likely to arrive.</p> - -<p>The Perl script <code>urlbst</code> can be used to add this support to an -arbitrary <code>.bst</code> file which has a reasonably `conventional' -structure. The result is meant to be robust rather than pretty.</p> - -<p>It has a different goal from Patrick Daly's `custom-bib' package -- -that is intended to create a BibTeX style .bst file from scratch, and -supports `url' and `eprint' fields. This package, on the other hand, -is intended for the case where you already have a style file that -works (or at least, which you cannot or will not change), and edits it -to add the new webpage entry type, plus the url, lastchecked and -eprint fields. Fuller details are in the <a href="urlbst.pdf" ->manual</a>.</p> - -<h2><a name='usage'>Usage</a></h2> -<pre> -urlbst [--[no]eprint] [--[no]doi] [--[no]pubmed] - [--inlinelinks] [--nohyperlinks] [--hypertex] [--hyperref] - [--literal key=value] - [input-file [output-file]] -</pre> -<p>If either the input-file or the output-file is omitted, they -default to stdin and stdout respectively. If the input file already -has a URL entry type, then the script objects. -By default (in the current version), the output -includes support for eprint, doi and pubmed, but these can be disabled -by <code>--noeprint</code>, <code>--nodoi</code> and -<code>--nopubmed</code>, respectively.</p> - -<p>The added fields are:</p> -<ul> -<li><code>url</code> and <code>lastchecked</code>, to associate a URL with - a reference, along with the date at which the URL was last checked - to exist;</li> -<li><code>doi</code>, for a reference's <a href='http://doi.org'>DOI</a>;</li> -<li><code>eprint</code>, for an <a href='http://arxiv.org'>arXiv</a> eprint reference; and</li> -<li><code>pubmed</code> for a reference's - <a href='http://pubmed.gov'>PubMed</a> identifier (PMID).</li> -</ul> - -<p>If either of the <code>--hypertex</code> or <code>--hyperref</code> -options is present, then the generated <code>.bst</code> file includes -support for hyperlinks in the generated eprint entries in the -bibliography, with the format being either HyperTeX (see <a -href="http://arxiv.org/hypertex/#implementation" >arXiv, again</a>), -supported by xdvi, dvips and others, or using the support available -from the hyperref package. These options have no effect unless one of -the <code>--eprint</code> or <code>--doi</code> options is given: when -URLs are included in the bibliography, they are written out using the -<code>\url{...}</code> command, and hyperref automatically processes -that in the correct way to include a hyperlink.</p> - -<p>The <code>--inlinelinks</code> option tells urlbst not to write out -the URL as text within the bibliography entry. Instead, urlbst will -produce a more conventional-looking and compact bibliography entry, -but the entry's title will now be a hyperlink to that URL. This -hyperlink may be useful to anyone who reads your document online -(this option can only be used with <code>--hyperref</code> or -<code>--hypertex</code>). Any DOI or eprint text which would be -produced as a result of the appropriate option will still appear in -this mode.</p> - -<p>You may adjust various literal strings, either for the purposes of -internationalisation, or simply because you prefer different text. To -do this, give the <code>--literal</code> option, followed by a -<code>key=value</code> pair, for example <code>--literal online="on -th'intert00bs"</code>, to replace the default <code>URL:</code> text. -The possible values, and their defaults, are below (say -<code>--literal help</code> to get this list printed out):</p> -<table> -<tr><th>keyword</th><th>default</th><th>meaning</th></tr> -<tr><td>cited</td><td>cited</td><td>indicator of citation, or "last checked", date</td></tr> -<tr><td>doiprefix</td><td>doi:</td><td>text printed before DOI</td></tr> -<tr><td>eprintprefix</td><td>arXiv:</td><td>text printed before eprint -ref</td></tr> -<tr><td>linktext</td><td>[link]</td><td>fallback link text</td></tr> -<tr><td>pubmedprefix</td><td>PMID:</td><td>text printed before PUBMED reference</td></tr> -<tr><td>online</td><td>online</td><td>indication that resource is online</td></tr> -<tr><td>urlintro</td><td>URL:</td><td>location of online resource (an -alternative is "Available from:")</td></tr> -</table> - -<p>The distribution includes preconverted versions of the four -standard BibTeX .bst style files.</p> - -<p>Only the style files which result from conversion of the standard -styles are checked in the regression tests. Other style files which -are known to work include</p> -<blockquote> -acm.bst, amsalpha.bst, amsplain.bst, apalike.bst, gerabbrv.bst, -geralpha.bst, gerapali.bst, gerplain.bst, gerunsrt.bst, ieeetr.bst, -siam.bst, mla.bst -</blockquote> - -<p>Style files which are known to fail:</p> -<ul> -<li>Currently (as of at least v0.5), there exists a style <code>achicago.bst</code> -which seems to fox <code>urlbst</code>; it turns out that there's a -simpler but almost equivalent style <code>chicago.bst</code> which -works.</li> - -<li>Some APA-like styles, including at least <code>apager.bst</code>, -seem to be sufficiently different from the most common styles, that -they confuse <code>urlbst</code> completely.</li> - -<li>The <em>koma-script</em> styles and the <em>refer</em> styles are -not designed to produce conventional <code>.bbl</code> files, and -<code>urlbst</code> does not aim to produce anything useful from these.</li> -</ul> -<p>This might be a good time for me to revisit the rather -convoluted logic within the script, to make it a little more robust in -the face of variants like these, but don't hold your breath. The -logic within the script is pretty hideous (it essentially works by -spotting patterns in the input style file, and replacing or extending -bits of BibTeX style-file code. This is a fragile technique, and is -probably at the limits of its usefulness, therefore I'd take some -persuading to add significant extra functionality to the script.</p> - -<p>The natbib and revtex style files already have URL fields. If you have a -BibTeX style file which you think ought to work, but with which the -script fails, send it to me, and I'll try to work out what I've -missed (no promises, though).</p> - -<p>Note that the command to invoke the script changed from `urlbst.pl' -to plain `urlbst' between versions 0.3 and 0.4.</p> - -<h2><a name='example'>For example...</a></h2> -<p>To add URL support to the standard <code>siam.bst</code> file, you -can give the command</p> -<pre> -% urlbst /path/to/original/siam.bst siamurl.bst -</pre> -<p>Your TeX installation will likely have some way of helping you find where -the original <code>.bst</code> files are. On teTeX-based systems, for -example, the command <code>kpsewhich siam.bst</code> returns the full -path of the <code>siam.bst</code> file which BibTeX would find.</p> - -<p>The distributed files <code>abbrvurl.bst</code>, -<code>alphaurl.bst</code>, <code>plainurl.bst</code> and -<code>unsrturl.bst</code> are versions of the standard style files -which have been pre-converted.</p> - -<p>There is more general discussion of including URLs in -bibliographies in the <a -href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=citeURL" >UK TeX -FAQ</a>.</p> - -<h2><a name='download'>Download and installation</a></h2> - -<p>Download the file as a -<a href="urlbst-@PACKAGE_VERSION@.tar.gz" >tarball</a> -or -<a href="urlbst-@PACKAGE_VERSION@.zip" >zip file</a> -and unpack it. Or you can clone the source repository at -<a href='http://bitbucket.org/nxg/urlbst/'>bitbucket.org</a>.</p> - -<p>To install, you should simply copy the distributed -<code>urlbst</code> script to someplace on the path (such as -<code>/usr/local/bin</code>, or <code>~/local/bin</code>, depending on -your privileges and tastes).</p> - -<p>If you (might) want to use the pre-converted standard -<code>.bst</code> files, then you'll need to copy these to somewhere -in the BibTeX search path. Type <kbd>kpsepath bst</kbd> on Unix to -find out the list of places BibTeX searches, and pick either one of -the user-local locations, or a system-wide one. If you're installing -in a system-wide location, you'll need admin privileges, obviously, -and you will probably need to use <code>texhash</code>, -<code>mktexlsr</code> or its equivalent, to update LaTeX's filename -cache. For further hints here, see -the TeX FAQ entries on <a -href='http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instpackages' ->installing a package</a> and <a -href='http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wherefiles' ->where LaTeX puts files</a>.</p> - -<p>That should be all you have to do.</p> - -<p>The urlbst script is distributed with a path which should just work, -as long as the Perl binary is in your path, but if you have problems -here, then you might want to change the first line to something like</p> -<pre> -#! /usr/local/bin/perl -</pre> -<p>if that's where your Perl binary is.</p> - -<p>You can also use the conventional <code>./configure; make; make -install</code> to configure and install the package (as root, or using -<code>sudo</code> if you're installing it in a system location), -though you still have to install the <code>.bst</code> files by hand. -This is rather heavyweight for the trivial amount of configuration -required, so it's almost always simpler just to do things by hand.</p> - -<p>If you need to change some of the <code>urlbst</code> defaults, -however, or if your fingers type <code>./configure</code> -spontaneously, then you can be reassured that the configure script -supports the standard <code>--prefix</code> option, plus the following -options setting defaults:</p> -<dl> - -<dt><code>--with-eprints=url</code>, <code>--without-eprints</code></dt> - -<dd>This makes the <code>--eprints</code> option to urlbst available -by default, and allows you to optionally specify a prefix for creating -URLs from eprint numbers. The default for this URL is -<code>http://arxiv.org/abs/</code> -- this is appropriate for arXiv, -obviously, but there are now a variety of other preprint archives -appearing, for which this might be inappropriate. If you have -comments on this default, or alternatives, please let me know. This -option is enabled by default; if you have some reason for disabling -the <code>--eprints</code> option for urlbst, the give the configure -option <code>--without-eprints</code></dd> - -<dt><code>--with-doi=url</code>, <code>--without-doi</code></dt> - -<dd>This makes available the <code>--doi</code> option to urlbst and, -as with the <code>--with-eprints</code> option, allows you to -customise the DOI resolver URL. The <code>--doi</code> option to -urlbst is on by default.</dd> - -<dt><code>--with-href=0/1/2</code></dt> - -<dd>This allows you to specify the type of hyperlinks which are -inserted in the bibliography. Values 0, 1 and 2, indicating no -hyperlinks, hypertex-style links, and hyperref-style links, -respectively. The default is <code>--with-href=0</code>. The -<code>hyperref</code>-style option is intended to complement the -increasingly standard <code>hyperref</code> package.</dd> - -</dl> - -<p>The first two options simply change defaults, and if you never use -the new <code>eprints</code> or <code>doi</code> fields, then the -defaults don't matter to you. </p> - -<p>Since the modified style generates URLs wrapped in the -<code>\url{}</code> macro, it is useful to use the resulting -bibliography style alongside the <code>url</code> package. Since this -tends to work with <code>hyperref</code> anyway, where possible, you -don't get any extra goodness by changing the <code>--with-href</code> -default at configuration time.</p> - -<h3>Documentation</h3> - -<p>Basic documentation is in the file <code>urlbst.tex</code>. This -is distributed as a PDF file, but if you want to regenerate it, use</p> -<pre> -% latex urlbst -% bibtex urlbst -% latex urlbst -% latex urlbst -</pre> - -<h2><a name='information'>Further Information and acknowledgements</a></h2> - -<p><code>urlbst</code> is archived on CTAN at <a -href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/urlbst/" -><code>biblio/bibtex/contrib/urlbst/</code></a>, and discussed in the -<a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=citeURL" >TeX -FAQ</a>.</p> - -<p>The source code for the package is maintained at -<a href='http://bitbucket.org/nxg/urlbst/'>bitbucket.org</a>, -which also includes an issue tracker, where you can report bugs (or -just mail me).</p> - -<p>The <a href="http://purl.org/nxg/dist/urlbst" ->home page of urlbst</a> might possibly have more recent versions than the -one you're looking at now.</p> - -<p>Thanks are due to many people for suggestions and requests, -and to 'ijvm' for code contributions.</p> - -<p>Copyright 2002-11, Norman Gray. Released under the terms of the GNU -General Public Licence.</p> - -<h2><a name='history'>Version history</a></h2> -<dl> -<dt><strong>0.7, </strong></dt> -<dd>Add --nodoi, --noeprints and --nopubmed options (which defaulted -on, and couldn't otherwise be turned off)</dd> - -<dt>0.7b1, 2011 March 17</dt> -<dd>Allow parameterisation of literal strings, with option <code>--literal</code>.</dd> - -<dt>0.6-5, 2011 March 8</dt> -<dd>Adjust support for inline links (should now work for arXiv, DOI and Pubmed)</dd> - -<dt>0.6-4, 2009 April 28</dt> -<dd>Work around BibTeX linebreaking bug (thanks to Andras Salamon for the bug report).</dd> - -<dt>0.6-3, 2009 April 19</dt> -<dd>Fix inline link generation (thanks to Eric Chamberland for the bug report).</dd> - -<dt>0.6-2, 2008 November 17</dt> -<dd>We now turn on inlinelinks when we spot format.vol.num.pages, -which means we include links for those styles which don't include a -title in the citation (common for articles in physical science styles, -such as aip.sty).</dd> - -<dt>0.6-1, 2008 June 16</dt> -<dd>Fixed some broken links to the various citation standards -(I think in this context this should probably <em>not</em> be happening, yes?). -The distributed <code>*url.bst</code> no longer have the -<code>--inlinelinks</code> option turned on by default.</dd> - -<dt><strong>0.6, 2007 March 26</strong></dt> -<dd><p>Added the option <code>--inlinelinks</code>, which adds inline hyperlinks -to any bibliography entries which have URLs, but does so inline, rather -than printing the URL explicitly in the bibliography. This is (primarily) -useful if you're preparing a version of a document which will be read -on-screen. Thanks to Jason Eisner for the suggestion, and much testing.</p> -<p>Incorporate hyperref bugfixes from Paweł Widera.</p> -<dl> -<dt>0.6b3</dt> -<dd>Further reworkings of the inlinelinks support, so that it's now -fired by a format.title (or format.btitle) line, with a fallback in -fin.entry. This should be more robust, and allows me to delete some -of the previous version's gymnastics.</dd> - -<dt>0.6b2</dt> -<dd>Reworked <code>inlinelinks</code> support; should now be more -robust. Incorporate hyperref bugfixes from Paweł Widera.</dd> - -<dt>0.6b1</dt> -<dd>Added the option <code>inlinelinks</code>, which adds inline hyperlinks -to any bibliography entries which have URLs, but does so inline, rather -than printing the URL explicitly in the bibliography. This is (only) -useful if you're preparing a version of a document which will be read -on-screen.</dd> -</dl> -</dd> - -<dt>0.5.2, 2006 September 6</dt> -<dd>Another set of documentation-only changes, hopefully clarifying -installation.</dd> - -<dt>0.5.1, 2006 January 10</dt> -<dd>No functionality changes. Documentation and webpage changes only, -hopefully clarifying usage and configuration</dd> - -<dt><strong>0.5, 2005 June 3</strong></dt> -<dd>Added support for Digital Object Identifiers (DOI) fields in -bibliographies.</dd> - -<dt>0.4-1, 2005 April 12</dt> -<dd>Documentation improvements -- there are now examples in the help text!</dd> - -<dt><strong>0.4, 2004 December 1</strong></dt> -<dd>Bug fixes: now compatible with mla.bst and friends. -Now uses <code>./configure</code> (optionally). Assorted reorganisation.</dd> - -<dt><strong>0.3, 2003 June 4</strong></dt> -<dd>Added --eprint, --hypertex and --hyperref options.</dd> - -<dt><strong>0.2, 2002 October 23</strong></dt> -<dd>The `editor' field is now supported in the webpage entry type. Basic -documentation added.</dd> - -<dt><strong>0.1, 2002 April</strong></dt> -<dd>Initial version</dd> - -</dl> - - -<div class="signature"> -<a href="http://nxg.me.uk" - >Norman Gray</a><br/> -@RELEASEDATE@ -</div> - -</body> -</html> diff --git a/Master/texmf-dist/doc/bibtex/urlbst/urlbst.in b/Master/texmf-dist/doc/bibtex/urlbst/urlbst.in index 460649331ae..1039dfb6c5a 100644 --- a/Master/texmf-dist/doc/bibtex/urlbst/urlbst.in +++ b/Master/texmf-dist/doc/bibtex/urlbst/urlbst.in @@ -8,7 +8,13 @@ # # See http://purl.org/nxg/dist/urlbst for documentation # -# $Id$ +# Copyright @COPYRIGHTYEARS@, Norman Gray <http://nxg.me.uk> +# +# This program is distributed under the terms of the +# GNU General Public Licence, v2.0. +# The modifications to the input .bst files are asserted as Copyright @COPYRIGHTYEARS@, Norman Gray, +# and distributed under the terms of the LaTeX Project Public Licence. +# See the package README for further dicussion of licences. $version = '@PACKAGE_VERSION@'; ($progname = $0) =~ s/.*\///; @@ -195,6 +201,9 @@ open (OUT, ">$outfile") || die "Can't open $outfile to write"; print OUT "%%% Modification of BibTeX style file ", ($infile eq '-' ? '<stdin>' : $infile), "\n"; print OUT "%%% ... by $progname, version $version (marked with \"$mymarker\")\n%%% See <$myurl>\n"; +print OUT "%%% Modifications Copyright @COPYRIGHTYEARS@, Norman Gray,\n"; +print OUT "%%% and distributed under the terms of the LPPL; see README for discussion.\n"; +print OUT "%%%\n"; print OUT "%%% Added webpage entry type, and url and lastchecked fields.\n"; print OUT "%%% Added eprint support.\n" if ($addeprints); print OUT "%%% Added DOI support.\n" if ($adddoiresolver); @@ -211,6 +220,11 @@ $found{finentry} = 0; $found{formatdate} = 0; $found{formattitle} = 0; $found{newblock} = 0; +# The following are initialised negative, which Perl treats as true, +# so the simple test 'if ($found{formateprint}) ...' will be true. +$found{formateprint} = -1; +$found{formatdoi} = -1; +$found{formatpubmed} = -1; while (<IN>) { /^ *%/ && do { @@ -331,6 +345,24 @@ EOD $found{newblock} = 1; }; + /^ *FUNCTION *\{format.doi\}/ && do { + #print STDERR "$progname: style file $infile already supports DOIs; urlbst format.doi disabled\n(see generated .bst style: you may need to make edits near \$adddoiresolver)\n"; + $found{formatdoi} = 1; + $adddoiresolver = 0; + }; + + /^ *FUNCTION *\{format.eprint\}/ && do { + #print STDERR "$progname: style file $infile already supports eprints; urlbst format.eprint disabled\n(see generated .bst style: you may need to make edits near \$addeprints)\n"; + $found{formateprint} = 1; + $addeprints = 0; + }; + + /^ *FUNCTION *\{format.pubmed\}/ && do { + #print STDERR "$progname: style file $infile already supports Pubmed; urlbst format.pubmed disabled\n(see generated .bst style: you may need to make edits near \$addpubmedresolver)\n"; + $found{formatpubmed} = 1; + $addpubmedresolver = 0; + }; + /^ *FUNCTION *{output\.nonnull}/ && do { print OUT "$mymarker\n"; print OUT "FUNCTION {output.nonnull.original}\n"; @@ -585,28 +617,48 @@ FUNCTION {format.url} } if$ } +EOD + $formateprintfunction = <<'EOD'; FUNCTION {format.eprint} { eprint empty$ { "" } { eprintprefix eprint * eprinturl eprint * make.href } if$ } +EOD + output_replacement_function($found{formateprint}, + 'format.eprint', + 'addeprints', + $formateprintfunction); + $formatdoifunction = <<'EOD'; FUNCTION {format.doi} { doi empty$ { "" } { doiprefix doi * doiurl doi * make.href } if$ } +EOD + output_replacement_function($found{formatdoi}, + 'format.doi', + 'adddoiresolver', + $formatdoifunction); + $formatpubmedfunction = <<'EOD'; FUNCTION {format.pubmed} { pubmed empty$ { "" } { pubmedprefix pubmed * pubmedurl pubmed * make.href } if$ } +EOD + output_replacement_function($found{formatpubmed}, + 'format.pubmed', + 'addpubmedresolver', + $formatpubmedfunction); + print OUT <<'EOD'; % Output a URL. We can't use the more normal idiom (something like % `format.url output'), because the `inbrackets' within % format.lastchecked applies to everything between calls to `output', @@ -627,8 +679,17 @@ FUNCTION {output.web.refs} new.block inlinelinks 'skip$ % links were inline -- don't repeat them - { - output.url + { % If the generated DOI will be the same as the URL, + % then don't print the URL (thanks to Joseph Wright for this code, + % at http://tex.stackexchange.com/questions/5660) + adddoiresolver + doiurl doi empty$ { "X" } { doi } if$ * % DOI URL to be generated + url empty$ { "Y" } { url } if$ % the URL, or "Y" if empty + = % are the strings equal? + and + 'skip$ + { output.url } + if$ addeprints eprint empty$ not and { format.eprint output.nonnull } 'skip$ @@ -718,6 +779,30 @@ EOD } +sub output_replacement_function { + my $emit_function = $_[0]; + my $function_name = $_[1]; + my $disabling_variable = $_[2]; + my $function_definition_string = $_[3]; + + if ($emit_function > 0) { + print OUT <<"EOD"; +%%% The style file $infile already supports $function_name, +%%% but it might not do so in the same way as urlbst expects. +%%% I've therefore left $infile 's function unchanged, +%%% and disabled urlbst's version; proceed with some caution. +EOD + + print STDERR "$progname: WARNING: style file $infile already includes a $function_name function;\nyou may need to disable the urlbst version by setting \$$disabling_variable to zero.\nYou might want to edit the output file (search for $function_name).\n"; + + ($t = $function_definition_string) =~ s/\n/\n%%% /g; + print OUT "%%% " . $t . "$mymarker\n"; + } else { + print OUT $function_definition_string; + } + print OUT "\n"; +} + sub print_missing_functions { # We've got to the bit of the file which handles the entry # types, so write out the webpage entry handler. This uses diff --git a/Master/texmf-dist/doc/bibtex/urlbst/urlbst.pdf b/Master/texmf-dist/doc/bibtex/urlbst/urlbst.pdf Binary files differindex cb142b1efbb..d3955eef1fb 100644 --- a/Master/texmf-dist/doc/bibtex/urlbst/urlbst.pdf +++ b/Master/texmf-dist/doc/bibtex/urlbst/urlbst.pdf diff --git a/Master/texmf-dist/doc/bibtex/urlbst/urlbst.tex b/Master/texmf-dist/doc/bibtex/urlbst/urlbst.tex index 4cbf3910dd2..7743ce05641 100644 --- a/Master/texmf-dist/doc/bibtex/urlbst/urlbst.tex +++ b/Master/texmf-dist/doc/bibtex/urlbst/urlbst.tex @@ -2,7 +2,7 @@ \title{The \texttt{urlbst} package} \author{Norman Gray\\\texttt{<http://nxg.me.uk>}} -\date{Version 0.7, 2011 July 20} +\date{Version 0.8, 2019 July 1} %\usepackage{times} \usepackage{url} @@ -52,7 +52,7 @@ The added fields are: a reference, along with the date at which the URL was last checked to exist; \item \btfield{doi}, for a reference's DOI - (see \url{http://doi.org}); + (see \url{https://doi.org}); \item \btfield{eprint}, for an arXiv eprint reference (see \url{http://arxiv.org}); and \item \btfield{pubmed} for a reference's PubMed identifier @@ -62,7 +62,7 @@ The added fields are: Usage is simple: \begin{verbatim} % urlbst [--eprint] [--doi] [--pubmed] - [--nohyperlinks] [--inlinelinks] [--hypertex] [--hyperref] + [--nohyperlinks] [--inlinelinks] [--hypertex] [--hyperref] [input-file [output-file]] \end{verbatim} where the |input-file| is an existing |.bst| file, and @@ -134,7 +134,7 @@ output, however, then the script encloses the |\url| command in an appropriate Hyper\TeX\ special. When the style file generates a link for DOIs, it does so by -prepending the string \texttt{http://dx.doi.org/} to the DOI. This is +prepending the string \texttt{https://doi.org/} to the DOI. This is generally reasonable, but some DOIs have characters in them which are illegal in URLs, with the result that the resulting \texttt{dx.doi.org} URL doesn't work. The only real way of resolving @@ -228,7 +228,7 @@ not appear to materially disagree. ISO-690~\cite{url:iso690} is a formal standard for this stuff. Walker and Taylor's \emph{Columbia Guide to Online Style}~\cite{walker06} provides extensive coverage (but is only available on dead trees). -There are two style guides associated with the APA, namely +There are two style guides associated with the APA, namely the published APA style guide~\cite{apastyle} (a paper-only publication, so should be ignored by all, if there's any justice in the world), and what appears @@ -271,10 +271,126 @@ generated bibliographies. See also the URL entry in the UK \TeX\ FAQ~\cite{texfaq}, and references therein. -\textbf{Acknowledgements:} Thanks to Jason Eisner for suggesting -the |--inlinelinks| option, to Pawe\l{} Widera for the -suggestion to use |\path| when formatting DOIs and to Michael Giffin -for the suggestion to include PubMed URLs. +%% \textbf{Acknowledgements:} Thanks +%% to Jason Eisner for suggesting the |--inlinelinks| option; +%% to `ijvm' for code contributions in the |urlbst| script; +%% to Pawe\l{} Widera for the suggestion to use |\path| when formatting DOIs; +%% to Michael Giffin for the suggestion to include PubMed URLs; +%% to Katrin Leinweber for the pull request which fixed the format of DOI +%% references. + +\section{Acknowledgements, and release notes} + +%%% include:release-notes.tex + + +Thanks are due to many people for suggestions and requests: +to Jason Eisner for suggesting the |--inlinelinks| option; +to ‘ijvm’ for code contributions in the |urlbst| script; +to Paweł Widera for the suggestion to use |\path| when formatting DOIs; +to Michael Giffin for the suggestion to include PubMed URLs; +to Katrin Leinweber for the pull request which fixed the format of DOI +references. + +\begin{description} +\item[\textbf{0.8, 2019 July 1}]\relax +\begin{itemize} +\item The presence of a preexisting |format.doi|, +|format.eprint| or |format.pubmed| function is +now detected, and warned about. The resulting |.bst| file +might still require some manual editing. +Resolves issue 8\footnote{\url{https://bitbucket.org/nxg/urlbst/issue/8}}. +\item Clarified licences (I hope). +\item Adjust format of DOI resolver. +Resolves issue 11\footnote{\url{https://bitbucket.org/nxg/urlbst/issue/11}}, +thanks to +code contributed by Katrin Leinweber\footnote{\url{https://bitbucket.org/nxg/urlbst/pull-requests/1/}}. +\end{itemize} + + +\item[0.7, 2011 July 20]\relax +Add |--nodoi|, |--noeprints| and |--nopubmed| options (which defaulted +on, and couldn't otherwise be turned off) + +\item[0.7b1, 2011 March 17]\relax +Allow parameterisation of literal strings, with option |--literal|. + +\item[0.6-5, 2011 March 8]\relax +Adjust support for inline links (should now work for arXiv, DOI and Pubmed) + +\item[0.6-4, 2009 April 28]\relax +Work around BibTeX linebreaking bug (thanks to Andras Salamon for the bug report). + +\item[0.6-3, 2009 April 19]\relax +Fix inline link generation (thanks to Eric Chamberland for the bug report). + +\item[0.6-2, 2008 November 17]\relax +We now turn on inlinelinks when we spot format.vol.num.pages, +which means we include links for those styles which don't include a +title in the citation (common for articles in physical science styles, +such as aip.sty). + +\item[0.6-1, 2008 June 16]\relax +Fixed some broken links to the various citation standards +(I think in this context this should probably \emph{not} be happening, yes?). +The distributed |*url.bst| no longer have the +|--inlinelinks| option turned on by default. + +\item[\textbf{0.6, 2007 March 26}]\relax +\begin{itemize} +\item Added the option |--inlinelinks|, which adds inline hyperlinks +to any bibliography entries which have URLs, but does so inline, rather +than printing the URL explicitly in the bibliography. This is (primarily) +useful if you're preparing a version of a document which will be read +on-screen. Thanks to Jason Eisner for the suggestion, and much testing. + +\item Incorporate hyperref bugfixes from Paweł Widera. + +\item Further reworkings of the inlinelinks support, so that it's now +fired by a |format.title| (or |format.btitle|) line, with a fallback in +|fin.entry|. This should be more robust, and allows me to delete some +of the previous version's gymnastics. + +\item Reworked |inlinelinks| support; should now be more +robust. Incorporate hyperref bugfixes from Paweł Widera. + +\item Added the option |inlinelinks|, which adds inline hyperlinks +to any bibliography entries which have URLs, but does so inline, rather +than printing the URL explicitly in the bibliography. This is (only) +useful if you're preparing a version of a document which will be read +on-screen. +\end{itemize} + + +\item[0.5.2, 2006 September 6]\relax +Another set of documentation-only changes, hopefully clarifying +installation. + +\item[0.5.1, 2006 January 10]\relax +No functionality changes. Documentation and webpage changes only, +hopefully clarifying usage and configuration + +\item[\textbf{0.5, 2005 June 3}]\relax +Added support for Digital Object Identifiers (DOI) fields in +bibliographies. + +\item[0.4-1, 2005 April 12]\relax +Documentation improvements -- there are now examples in the help text! + +\item[\textbf{0.4, 2004 December 1}]\relax +Bug fixes: now compatible with mla.bst and friends. +Now uses |./configure| (optionally). Assorted reorganisation. + +\item[\textbf{0.3, 2003 June 4}]\relax +Added |--eprint|, |--hypertex| and |--hyperref| options. + +\item[\textbf{0.2, 2002 October 23}]\relax +The `editor' field is now supported in the webpage entry type. Basic +documentation added. + +\item[\textbf{0.1, 2002 April}]\relax +Initial version +\end{description} \bibliography{urlbst} \bibliographystyle{plainurl} diff --git a/Master/texmf-dist/doc/bibtex/urlbst/urlbst.tex.in b/Master/texmf-dist/doc/bibtex/urlbst/urlbst.tex.in deleted file mode 100644 index 9ed281023cc..00000000000 --- a/Master/texmf-dist/doc/bibtex/urlbst/urlbst.tex.in +++ /dev/null @@ -1,282 +0,0 @@ -\documentclass[a4paper]{article} - -\title{The \texttt{urlbst} package} -\author{Norman Gray\\\texttt{<http://nxg.me.uk>}} -\date{Version @PACKAGE_VERSION@, @RELEASEDATE@} - -%\usepackage{times} -\usepackage{url} -\usepackage{hyperref} - -% Not long enough to make it useful to number sections -\setcounter{secnumdepth}{0} - -% Squeeze a bit more on to the page -%\addtolength\textwidth{1cm} -%\addtolength\oddsidemargin{-0.5cm} - -\makeatletter -% Easy verbatim mode -\catcode`\|=\active -\def|{\begingroup \let\do\@makeother \dospecials \verbatim@font \doverb} -\def\doverb#1|{#1\endgroup} - -\renewcommand{\verbatim@font}{\normalfont\small\ttfamily} -\makeatother - -\newcommand{\ub}{\package{urlbst}} -\newcommand{\BibTeX}{Bib\TeX} -\newcommand{\package}[1]{\texttt{#1}} -\newcommand{\btfield}[1]{\textsf{#1}} - -\begin{document} -\maketitle - -The \ub\ package consists of a Perl script which edits \BibTeX\ style -files (|.bst|) to add a \btfield{webpage} entry type, and which adds a -few new fields -- notably including \btfield{url} -- -to all other entry types. The distribution includes preconverted -versions of the four standard \BibTeX\ |.bst| style files. - -It has a different goal from Patrick Daly's \package{custom-bib} -package~\cite{url:daly} -- that is intended to create a \BibTeX\ style -|.bst| file from scratch, and supports \btfield{url} and -\btfield{eprint} fields. This package, on the other hand, is intended -for the case where you already have a style file that works (or at -least, which you cannot or will not change), and edits it to add the -new \btfield{webpage} entry type, plus the new fields. - -The added fields are: -\begin{itemize} -\item \btfield{url} and \btfield{lastchecked}, to associate a URL with - a reference, along with the date at which the URL was last checked - to exist; -\item \btfield{doi}, for a reference's DOI - (see \url{http://doi.org}); -\item \btfield{eprint}, for an arXiv eprint reference - (see \url{http://arxiv.org}); and -\item \btfield{pubmed} for a reference's PubMed identifier - (\textsc{PMID}, see \url{http://pubmed.gov}). -\end{itemize} - -Usage is simple: -\begin{verbatim} -% urlbst [--eprint] [--doi] [--pubmed] - [--nohyperlinks] [--inlinelinks] [--hypertex] [--hyperref] - [input-file [output-file]] -\end{verbatim} -where the |input-file| is an existing |.bst| file, and -the |output-file| is the name of the new style file to be -created. If either file name is missing, the default is the -standard input or standard output respectively. -For example: -\begin{verbatim} -% urlbst --eprint bibstyle.bst -\end{verbatim} -would convert the style file \texttt{bibstyle.bst}, including support -for e-prints, and sending the result to the standard output (ie, the -screen, so it would more useful if you were to either redirect this to -a file or supply the output-file argument). - -If the option |--eprint| is present, then we switch on support for -\texttt{eprint} fields in the modified .bst file, with a citation -format matching that recommended in -\url{http://arxiv.org/help/faq/references}. If the option -|--doi| is present, we include support for a |doi| field, referring -to a Digital Object Identifier (DOI) as standardised by -\url{http://www.doi.org/}. And if |--pubmed| is present, we include -support for a |pubmed| field, referring to a PubMed identifier as -supported at \url{http://www.pubmed.gov}. - -If either of the |--hypertex| or |--hyperref| options is present, then -the generated .bst file includes support for hyperlinks in the -generated eprint entries in the bibliography, with the format being -either Hyper\TeX\ (see -\url{http://arxiv.org/hypertex/#implementation}), supported by xdvi, -dvips and others, or using the support available from the -\package{hyperref} package. These options have no effect unless one -of the |--eprint|, |--doi|, |--pubmed| or |--inlinelinks| options is given: -when URLs are included -in the bibliography, they are written out using the |\url{...}| -command. The \package{hyperref} support is more generic, and more -generally supported, and so you should choose this unless you have a -particular need for the Hyper\TeX\ support. The |--nohyperlinks| -option, which is present by default, suppresses all hyperlinking. - -By default, any URL field is displayed as part of the bibliography -entry, linked to the corresponding URL via the mechanism managed by -the |--hypertex| and |--hyperref| options. If the |--inlinelinks| -option is present, however, then the URL is not displayed in the -printed entry, but instead a hyperlink is created, linked to suitable -text within the bibliography entry, such as the citation title. This -option does not affect the display of eprints, DOI or PubMed fields. It makes -no sense to specify |--inlinelinks| with |--nohyperlinks|, and the -script warns you if you do that, for example by failing to specify one -of the link-style options. This option is (primarily) useful if -you're preparing a version of a document which will be read on-screen; -the point of it is that the resulting bibliography is substantially -more compact than it would otherwise be. - -The support for all the above behaviours is always included in the -output file. The options instead control only whether the various -behaviours are enabled or disabled, and if you need to alter these, -you may do so by editing the generated |.bst| file and adjusting -values in the |{init.urlbst.variables}| function, where indicated. - -The generated references have URLs inside |\url{...}|. The best -way to format this this is with the \package{url} package -(see~\cite{texfaq} for pointers), but as a poor alternative, you can -try |\newcommand{\url}[1]{\texttt{#1}}|. The \package{hyperref} -package automatically processes |\url{...}| in the correct way to -include a hyperlink, and if you have selected \package{hyperref} -output, then nothing more need be done. If you selected Hyper\TeX\ -output, however, then the script encloses the |\url| command in an -appropriate Hyper\TeX\ special. - -When the style file generates a link for DOIs, it does so by -prepending the string \texttt{http://dx.doi.org/} to the DOI. This is -generally reasonable, but some DOIs have characters in them which are -illegal in URLs, with the result that the resulting -\texttt{dx.doi.org} URL doesn't work. The only real way of resolving -this is to write a URL-encoding function in the style-file -implementation language, but while that would doubtless be feasible in -principle, it would be hard and very, very, ugly. The only advice I -can offer in this case is to rely on the fact that the DOI will still -appear in the typeset bibliography, and that users who would want to -take advantage of the DOI will frequently (or usually?) know how to -resolve the DOI when then need to. As a workaround, you could include -a URL-encoded DOI URL in the \btfield{url} field of the entry (thanks -to Eric Chamberland for this suggestion). - -The \ub\ script works by spotting patterns and characteristic function -names in the input |.bst| file. It works as-is in the case of the -four standard \BibTeX\ style files |plain.bst|, |unsrt.bst|, -|alpha.bst| and |abbrv.bst|. It also works straightforwardly for -many other style files -- since many of these are derived from, or at -least closely inspired by, the standard ones -- but it does not -pretend that it can do so for all of them. In some cases, such as the -style files for the \package{refer} or \package{koma-script} packages, -the style files are not intended to be used for formatting; others are -sufficiently different from the standard files that a meaningful edit -becomes impossible. For the large remainder, however, the result of -this script should need only relatively minor edits before being -perfectly usable. - -\section{New \texttt{.bib} entry and field types} - -The new entry type \btfield{webpage} has required fields -\btfield{title} and \btfield{url}, and optional fields -\btfield{author}, \btfield{editor}, \btfield{note}, \btfield{year}, -\btfield{month} and \btfield{lastchecked}. The \btfield{url} and -\btfield{lastchecked} fields are new, and are -valid in other entry types as well: the first, obviously, is the URL -which is being cited, or which is being quoted as an auxiliary source -for an article perhaps; the second is the date when you last checked -that the URL was there, in the state you quoted it; this is necessary -since some people, heedless of the archival importance of preserving -the validity of URLs, indulge in the vicious practice of reorganising -web pages and destroying links. For the case of the \btfield{webpage} entry -type, the \btfield{editor} field should be used for the `maintainer' -of a web page. - -For example, in Figure~\ref{f:ex} we illustrate two potential |.bib| -file entries. The \texttt{@webpage} entry type is the new type -provided by this package, and provides reference information for a -webpage; it includes the new \texttt{url} and \texttt{lastchecked} -fields. There is also an example of the standard \texttt{@book} entry -type, which now includes the \texttt{url} and \texttt{lastchecked} -fields as well. The difference between the two references is that in -the \texttt{@book} case it is the book being cited, so that the -\texttt{url} provides extra information; in the \texttt{@webpage} case -it is the page itself which is of interest. You use the new |eprint|, -|doi| and |pubmed| fields similarly, if the bibliographic item in -question has an e-print, DOI or PubMed reference. -\begin{figure} -\begin{verbatim} -@Manual{w3chome, - url = {http://www.w3.org}, - title = {The World Wide Web Consortium}, - year = 2009, - lastchecked = {26 August 2009}} - -@Book{schutz, - author = {Bernard Schutz}, - title = {Gravity from the GroundUp}, - publisher = {Cambridge University Press}, - year = {2003}, - url = {http://www.gravityfromthegroundup.org/}, - lastchecked = {2008 June 16}} -\end{verbatim} -\caption{\label{f:ex}The new \texttt{@webpage} entry type, and the \texttt{url} - field in action} -\end{figure} - -How do you use this in a document? To use the the -\texttt{alphaurl.bst} style -- which is a pre-converted version of the -standard \texttt{alpha.bst} style, included in the \texttt{urlbst} -distribution -- you simply make sure that \texttt{alphaurl.bst} is in -your BibTeX search path (use the command \texttt{kpsepath bst} to find -this path and \texttt{kpsewhich alphaurl.bst} to confirm that BibTeX -can find it) and add |\bibliographystyle{alphaurl}| to your \LaTeX\ document. - -\section{Sources} - -There are various sources which suggest how to format references to -web pages. I have followed none specifically, but fortunately they do -not appear to materially disagree. - -ISO-690~\cite{url:iso690} is a formal standard for this stuff. Walker -and Taylor's \emph{Columbia Guide to Online Style}~\cite{walker06} -provides extensive coverage (but is only available on dead trees). -There are two style guides associated with the APA, namely -the published APA style -guide~\cite{apastyle} (a paper-only publication, so should be -ignored by all, if there's any justice in the world), and what appears -to be the 1998 web-citation proposal for that~\cite{url:weapas}, which -also includes some useful links. -The TeX FAQ~\cite{texfaq} has both practical advice and pointers to other sources.% -\footnote{Emory University's Goizueta Business Library once had a collection of -useful links on this topic, but they've whimsically changed the URL at least twice -since I first distributed \ub, and I've got fed up fixing their broken link.} - -\section{Hints} - -If you use Emacs' \BibTeX\ mode, you can insert the following in your -|.emacs| file to add knowledge of the new \btfield{webpage} entry: -\begin{verbatim} -(defun my-bibtex-hook () - (setq bibtex-mode-user-optional-fields '("location" "issn")) ; e.g. - (setq bibtex-entry-field-alist - (cons - '("Webpage" - ((("url" "The URL of the page") - ("title" "The title of the resource")) - (("author" "The author of the webpage") - ("editor" "The editor/maintainer of the webpage") - ("year" "Year of publication of the page") - ("month" "Month of publication of the page") - ("lastchecked" "Date when you last verified the page was there") - ("note" "Remarks to be put at the end of the entry")))) - bibtex-entry-field-alist))) -(add-hook 'bibtex-mode-hook 'my-bibtex-hook) -\end{verbatim} -After that, you can add a \btfield{webpage} entry by typing |C-c C-b webpage| -(or |M-x bibtex-entry|). - -It is a \emph{very} good idea to use the \package{url} package: it deals with -the problem of line-breaking long URLs, and with the problem that -\BibTeX{} creates, of occasionally inserting \%-signs into URLs in -generated bibliographies. - -See also the URL entry in the UK \TeX\ FAQ~\cite{texfaq}, and -references therein. - -\textbf{Acknowledgements:} Thanks to Jason Eisner for suggesting -the |--inlinelinks| option, to Pawe\l{} Widera for the -suggestion to use |\path| when formatting DOIs and to Michael Giffin -for the suggestion to include PubMed URLs. - -\bibliography{urlbst} -\bibliographystyle{plainurl} - -\end{document} |