texlive[55423] Master/texmf-dist: vancouver (5jun20)
commits+karl at tug.org
commits+karl at tug.org
Fri Jun 5 23:47:56 CEST 2020
Revision: 55423
http://tug.org/svn/texlive?view=revision&revision=55423
Author: karl
Date: 2020-06-05 23:47:56 +0200 (Fri, 05 Jun 2020)
Log Message:
-----------
vancouver (5jun20)
Modified Paths:
--------------
trunk/Master/texmf-dist/bibtex/bst/vancouver/vancouver.bst
trunk/Master/texmf-dist/doc/bibtex/vancouver/README
trunk/Master/texmf-dist/doc/bibtex/vancouver/vancouver.pdf
trunk/Master/texmf-dist/doc/bibtex/vancouver/vancouver.tex
Added Paths:
-----------
trunk/Master/texmf-dist/doc/bibtex/vancouver/LICENSE
Modified: trunk/Master/texmf-dist/bibtex/bst/vancouver/vancouver.bst
===================================================================
--- trunk/Master/texmf-dist/bibtex/bst/vancouver/vancouver.bst 2020-06-05 21:03:29 UTC (rev 55422)
+++ trunk/Master/texmf-dist/bibtex/bst/vancouver/vancouver.bst 2020-06-05 21:47:56 UTC (rev 55423)
@@ -1,17 +1,18 @@
-%%
%% This `vancouver.bst' bibliographic style file (for LaTeX/BibTeX) is
%% generated with the docstrip utility and modified manually to meet the
%% ``Uniform Requirements for Manuscripts Submitted to Biomedical Journals''
%% as published in N Engl J Med 1997;336:309-315.
%% (also known as the Vancouver style)
-%% This specification may be found on the web page of the
-%% International Committe of Medical Journal Editors:
+%% The standards are summarized in:
+%% https://www.nlm.nih.gov/bsd/uniform_requirements.html
+%% and detailed in:
+%% https://www.ncbi.nlm.nih.gov/books/NBK7256/
%%
-%% http://www.icmje.org
-%%
%%-------------------------------------------------------------------
%%
-%% Copyright 2004 Folkert van der Beek
+%% Author: Folkert van der Beek <folkertvanderbeek at gmail.com>
+%% Version: 0.8
+%% URL: https://gitlab.com/fvdbeek/vancouver.bst
%%
%% This work may be distributed and/or modified under the
%% conditions of the LaTeX Project Public License, either version 1.3
@@ -21,14 +22,6 @@
%% 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 Folkert van der Beek.
-%%
-%% Complaints, suggestions and comments may be sent to
-%%
-%% Folkert van der Beek <folkertvanderbeek at gmail dot com>
-%%
%%-------------------------------------------------------------------
%%
%% This bibliography style file is intended for texts in ENGLISH
@@ -105,7 +98,7 @@
#0 'adddoiresolver := % 0=no DOI resolver; 1=include it
#0 'hrefform := % 0=no crossrefs; 1=hypertex xrefs; 2=hyperref refs
}
-INTEGERS {
+INTEGERS {
bracket.state
outside.brackets
open.brackets
@@ -176,14 +169,14 @@
bracket.state open.brackets =
{ " [" * }
{ ", " * } % bracket.state will be within.brackets
- if$
- s *
+ if$
+ s *
close.brackets 'bracket.state :=
}
if$
}
-% Call this function just before adding something which should be presented in
+% Call this function just before adding something which should be presented in
% brackets. bracket.state is handled specially within output.nonnull.
FUNCTION {inbrackets}
{ bracket.state close.brackets =
@@ -220,7 +213,7 @@
}
FUNCTION {fin.entry}
-{
+{
bracket.state close.brackets = % urlbst
{ "]" * }
'skip$
@@ -262,6 +255,12 @@
no.blank.or.punct
}
+FUNCTION {add.colon}
+{
+ ":" *
+ no.blank.or.punct
+}
+
FUNCTION {date.block}
{
"." *
@@ -434,7 +433,7 @@
* % concatenates the last 2 literals, i.e. every character, even a dot, following a "\" will be printed
}
{ duplicate$ "." = % pushes 1 if the last character is ".", otherwise 0
- 'pop$ % pushes the pop$ function
+ 'pop$ % pushes the pop$ function
{ * } % concatenates the last 2 literals
if$ % pops the last character if it is a dot, otherwise concatenates it with the string on top of the stack
}
@@ -456,7 +455,7 @@
STRINGS {replace find text}
INTEGERS {find_length}
FUNCTION {find.replace}
-{
+{
'replace :=
'find :=
'text :=
@@ -817,7 +816,7 @@
}
FUNCTION {format.authors}
-{
+{
author "author" format.names
%%"." " " "author" find.replace format.names
}
@@ -991,7 +990,7 @@
FUNCTION {format.date}
{
no.blank.or.punct
- ";"
+ ";"
duplicate$ empty$
year "year" bibinfo.check duplicate$ empty$
{ swap$ 'skip$
@@ -1168,19 +1167,16 @@
}
FUNCTION {format.journal.pages}
-{ pages duplicate$ empty$ 'pop$
- { swap$ duplicate$ empty$
- { pop$ pop$ format.pages }
- {
- ":" *
- swap$
- n.dashify
- "pages" bibinfo.check
- *
- }
- if$
- }
+{ pages empty$ 'skip$
+ { add.colon }
if$
+ pages duplicate$ empty$ 'pop$
+ {
+ n.dashify
+ "pages" bibinfo.check
+ *
+ }
+ if$
}
FUNCTION {format.vol.num}
@@ -1203,7 +1199,11 @@
}
FUNCTION {format.vol.num.pages}
-{ volume field.or.null
+{ volume empty$ number empty$ and
+ 'skip$
+ { add.semicolon }
+ if$
+ volume field.or.null
duplicate$ empty$ 'skip$
{
"volume" bibinfo.check
@@ -1355,7 +1355,7 @@
}
% make hypertex specials
FUNCTION {make.href.hypertex}
-{
+{
"\special {html:<a href=" quote$ *
swap$ * quote$ * "> }" * swap$ *
"\special {html:</a>}" *
@@ -1362,7 +1362,7 @@
}
% make hyperref specials
FUNCTION {make.href.hyperref}
-{
+{
"\href {" swap$ * "} {" * swap$ * "}" *
}
FUNCTION {make.href}
@@ -1409,10 +1409,10 @@
% the URL and the lastchecked in brackets.
FUNCTION {output.url}
{ url empty$
- 'skip$
- { new.block
+ 'skip$
+ { new.block
format.url output
- format.lastchecked output
+ format.lastchecked output
}
if$
}
@@ -1528,7 +1528,6 @@
{ format.type "type" output.check }
%%{ inbrackets type output }
if$
- new.block
format.publisher.address output
format.date "year" output.check
new.block
@@ -1570,7 +1569,6 @@
"journal" bibinfo.check
"journal" output.check
format.journal.date "year" output.check
- add.semicolon
format.vol.num.pages output
new.block
format.note output
@@ -1585,7 +1583,7 @@
{ format.organizations "organization" output.check }
{ format.editors "author and editor" output.check }
if$
- }
+ }
{ format.authors output.nonnull
"author and editor" editor either.or.check
}
Added: trunk/Master/texmf-dist/doc/bibtex/vancouver/LICENSE
===================================================================
--- trunk/Master/texmf-dist/doc/bibtex/vancouver/LICENSE (rev 0)
+++ trunk/Master/texmf-dist/doc/bibtex/vancouver/LICENSE 2020-06-05 21:47:56 UTC (rev 55423)
@@ -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.
+
Modified: trunk/Master/texmf-dist/doc/bibtex/vancouver/README
===================================================================
--- trunk/Master/texmf-dist/doc/bibtex/vancouver/README 2020-06-05 21:03:29 UTC (rev 55422)
+++ trunk/Master/texmf-dist/doc/bibtex/vancouver/README 2020-06-05 21:47:56 UTC (rev 55423)
@@ -1,41 +1,43 @@
-This `vancouver.bst' bibliographic style file (for LaTeX/BibTeX) is generated with the docstrip utility and modified manually to meet the ``Uniform Requirements for Manuscripts Submitted to Biomedical Journals'' as published in N Engl J Med 1997;336:309-315. (also known as the Vancouver style)
-This specification may be found on the web page of the International Committe of Medical Journal Editors:
+This `vancouver.bst' bibliographic style file (for LaTeX/BibTeX) is
+generated with the docstrip utility and modified manually to meet the
+``Uniform Requirements for Manuscripts Submitted to Biomedical
+Journals'' as published in N Engl J Med 1997;336:309-315. (also known
+as the Vancouver style)
-http://www.icmje.org
+The standards are summarized in:
+https://www.nlm.nih.gov/bsd/uniform_requirements.html and detailed in:
+https://www.ncbi.nlm.nih.gov/books/NBK7256/
-------------------------------------------------------------------
-Copyright 2004 Folkert van der Beek
+To follow or contribute to vancouver.bst development, you can browse
+or clone the Git repository on GitLab:
-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.
+https://gitlab.com/fvdbeek/vancouver.bst
-This work has the LPPL maintenance status `maintained'.
+Complaints, suggestions and comments can be made by creating an issue
+on GitLab.
-The Current Maintainer of this work is Folkert van der Beek.
+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.
-Complaints, suggestions and comments may be sent to
+-------------------------------------------------------------------
-Folkert van der Beek <folkertvanderbeek at gmail dot com>
+This bibliography style file is intended for texts in ENGLISH This is
+a numerical citation style, and as such is standard LaTeX. It requires
+no extra package to interface to the main text. The form of the
+\bibitem entries is \bibitem{key}... Usage of \cite is as follows:
+\cite{key} ==>> [#] \cite[chap. 2]{key} ==>> [#, chap. 2] where # is a
+number determined by the ordering in the reference list. The order in
+the reference list is that by which the works were originally cited in
+the text, or that in the database.
--------------------------------------------------------------------
-This bibliography style file is intended for texts in ENGLISH
-This is a numerical citation style, and as such is standard LaTeX.
-It requires no extra package to interface to the main text.
-The form of the \bibitem entries is
- \bibitem{key}...
-Usage of \cite is as follows:
- \cite{key} ==>> [#]
- \cite[chap. 2]{key} ==>> [#, chap. 2]
-where # is a number determined by the ordering in the reference list.
-The order in the reference list is that by which the works were originally
- cited in the text, or that in the database.
+To change the reference numbering system from [1] to 1, put the
+following code in the preamble: \makeatletter % Reference list option
+change \renewcommand\@biblabel[1]{#1} % from [1] to 1 \makeatother %
-To change the reference numbering system from [1] to 1,
-put the following code in the preamble:
-\makeatletter % Reference list option change
-\renewcommand\@biblabel[1]{#1} % from [1] to 1
-\makeatother %
---------------------------------------------------------------------
Modified: trunk/Master/texmf-dist/doc/bibtex/vancouver/vancouver.pdf
===================================================================
(Binary files differ)
Modified: trunk/Master/texmf-dist/doc/bibtex/vancouver/vancouver.tex
===================================================================
--- trunk/Master/texmf-dist/doc/bibtex/vancouver/vancouver.tex 2020-06-05 21:03:29 UTC (rev 55422)
+++ trunk/Master/texmf-dist/doc/bibtex/vancouver/vancouver.tex 2020-06-05 21:47:56 UTC (rev 55423)
@@ -25,12 +25,12 @@
\subsection{Standard journal article}
List the first six authors followed by et al. (Note: NLM now lists all authors.)
-\linebreak
+\linebreak
Halpern SD, Ubel PA, Caplan AL. Solid-organ transplantation in HIV-infected patients. N Engl J Med. 2002 Jul 25;347(4):284-7.\cite{halpern.ubel.ea:solid-organ*2}
As an option, if a journal carries continuous pagination throughout a volume (as many medical journals do) the month and issue number may be omitted.
-\linebreak
+\linebreak
Halpern SD, Ubel PA, Caplan AL. Solid-organ transplantation in HIV-infected patients. N Engl J Med. 2002;347:284-7.\cite{halpern.ubel.ea:solid-organ}
\subsubsection{Optional addition of a database's unique identifier for the citation:}
@@ -56,7 +56,7 @@
\subsection{Article not in English}
(Note: NLM translates the title into English, encloses the translation in square brackets, and adds an abbreviated language designator.)
-\linebreak
+\linebreak
Ellingsen AE, Wilhelmsen I. Sykdomsangst blant medisin- og jusstudenter. Tidsskr Nor Laegeforen. 2002;122(8):785-7.\cite{ellingsen.wilhelmsen:sykdomsangst}
\subsection{Volume with supplement}
@@ -90,7 +90,7 @@
\subsection{Type of article indicated as needed}
Tor M, Turker H. International approaches to the prescription of long-term oxygen therapy [letter]. Eur Respir J. 2002;20(1):242.\cite{tor.turker:international}
-\linebreak
+\linebreak
Lofwall MR, Strain EC, Brooner RK, Kindbom KA, Bigelow GE. Characteristics of older methadone maintenance (MM) patients [abstract]. Drug Alcohol Depend. 2002;66 Suppl 1:S105.\cite{lofwall.strain.ea:characteristics}
\subsection{Article containing retraction}
@@ -198,7 +198,7 @@
\subsection{In press}
(Note: NLM prefers "forthcoming" because not all items will be printed.)
-\linebreak
+\linebreak
Tian D, Araki H, Stahl E, Bergelson J, Kreitman M. Signature of balancing selection in Arabidopsis. Proc Natl Acad Sci U S A. In press 2002.\cite{ tian.araki.ea:signature}
\section{Electronic Material}
@@ -234,5 +234,5 @@
\subsubsection{Part of a database on the Internet}
MeSH Browser [database on the Internet]. Bethesda (MD): National Library of Medicine (US); 2002 - [cited 2003 Jun 10]. Meta-analysis; unique ID: D015201; [about 3 p.]. Available from: http://www.nlm.nih.gov/mesh/MBrowser.html\cite{mesh}
\bibliography{vancouver}
-\bibliographystyle{/home/folkert/scripts/vancouver}
+\bibliographystyle{vancouver}
\end{document}
More information about the tex-live-commits
mailing list.