texlive[43091] Master: oplotsymbl (30jan17)

commits+karl at tug.org commits+karl at tug.org
Tue Jan 31 00:30:01 CET 2017

Revision: 43091
Author:   karl
Date:     2017-01-31 00:30:01 +0100 (Tue, 31 Jan 2017)
Log Message:
oplotsymbl (30jan17)

Modified Paths:

Added Paths:

Removed Paths:

Deleted: trunk/Master/texmf-dist/doc/latex/oplotsymbl/LICENSE
--- trunk/Master/texmf-dist/doc/latex/oplotsymbl/LICENSE	2017-01-30 01:05:32 UTC (rev 43090)
+++ trunk/Master/texmf-dist/doc/latex/oplotsymbl/LICENSE	2017-01-30 23:30:01 UTC (rev 43091)
@@ -1,674 +0,0 @@
-                    GNU GENERAL PUBLIC LICENSE
-                       Version 3, 29 June 2007
- Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-                            Preamble
-  The GNU General Public License is a free, copyleft license for
-software and other kinds of works.
-  The licenses for most software and other practical works are designed
-to take away your freedom to share and change the works.  By contrast,
-the GNU General Public License is intended to guarantee your freedom to
-share and change all versions of a program--to make sure it remains free
-software for all its users.  We, the Free Software Foundation, use the
-GNU General Public License for most of our software; it applies also to
-any other work released this way by its authors.  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
-them 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 prevent others from denying you
-these rights or asking you to surrender the rights.  Therefore, you have
-certain responsibilities if you distribute copies of the software, or if
-you modify it: responsibilities to respect the freedom of others.
-  For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must pass on to the recipients the same
-freedoms that you received.  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.
-  Developers that use the GNU GPL protect your rights with two steps:
-(1) assert copyright on the software, and (2) offer you this License
-giving you legal permission to copy, distribute and/or modify it.
-  For the developers' and authors' protection, the GPL clearly explains
-that there is no warranty for this free software.  For both users' and
-authors' sake, the GPL requires that modified versions be marked as
-changed, so that their problems will not be attributed erroneously to
-authors of previous versions.
-  Some devices are designed to deny users access to install or run
-modified versions of the software inside them, although the manufacturer
-can do so.  This is fundamentally incompatible with the aim of
-protecting users' freedom to change the software.  The systematic
-pattern of such abuse occurs in the area of products for individuals to
-use, which is precisely where it is most unacceptable.  Therefore, we
-have designed this version of the GPL to prohibit the practice for those
-products.  If such problems arise substantially in other domains, we
-stand ready to extend this provision to those domains in future versions
-of the GPL, as needed to protect the freedom of users.
-  Finally, every program is threatened constantly by software patents.
-States should not allow patents to restrict development and use of
-software on general-purpose computers, but in those that do, we wish to
-avoid the special danger that patents applied to a free program could
-make it effectively proprietary.  To prevent this, the GPL assures that
-patents cannot be used to render the program non-free.
-  The precise terms and conditions for copying, distribution and
-modification follow.
-                       TERMS AND CONDITIONS
-  0. Definitions.
-  "This License" refers to version 3 of the GNU General Public License.
-  "Copyright" also means copyright-like laws that apply to other kinds of
-works, such as semiconductor masks.
-  "The Program" refers to any copyrightable work licensed under this
-License.  Each licensee is addressed as "you".  "Licensees" and
-"recipients" may be individuals or organizations.
-  To "modify" a work means to copy from or adapt all or part of the work
-in a fashion requiring copyright permission, other than the making of an
-exact copy.  The resulting work is called a "modified version" of the
-earlier work or a work "based on" the earlier work.
-  A "covered work" means either the unmodified Program or a work based
-on the Program.
-  To "propagate" a work means to do anything with it that, without
-permission, would make you directly or secondarily liable for
-infringement under applicable copyright law, except executing it on a
-computer or modifying a private copy.  Propagation includes copying,
-distribution (with or without modification), making available to the
-public, and in some countries other activities as well.
-  To "convey" a work means any kind of propagation that enables other
-parties to make or receive copies.  Mere interaction with a user through
-a computer network, with no transfer of a copy, is not conveying.
-  An interactive user interface displays "Appropriate Legal Notices"
-to the extent that it includes a convenient and prominently visible
-feature that (1) displays an appropriate copyright notice, and (2)
-tells the user that there is no warranty for the work (except to the
-extent that warranties are provided), that licensees may convey the
-work under this License, and how to view a copy of this License.  If
-the interface presents a list of user commands or options, such as a
-menu, a prominent item in the list meets this criterion.
-  1. Source Code.
-  The "source code" for a work means the preferred form of the work
-for making modifications to it.  "Object code" means any non-source
-form of a work.
-  A "Standard Interface" means an interface that either is an official
-standard defined by a recognized standards body, or, in the case of
-interfaces specified for a particular programming language, one that
-is widely used among developers working in that language.
-  The "System Libraries" of an executable work include anything, other
-than the work as a whole, that (a) is included in the normal form of
-packaging a Major Component, but which is not part of that Major
-Component, and (b) serves only to enable use of the work with that
-Major Component, or to implement a Standard Interface for which an
-implementation is available to the public in source code form.  A
-"Major Component", in this context, means a major essential component
-(kernel, window system, and so on) of the specific operating system
-(if any) on which the executable work runs, or a compiler used to
-produce the work, or an object code interpreter used to run it.
-  The "Corresponding Source" for a work in object code form means all
-the source code needed to generate, install, and (for an executable
-work) run the object code and to modify the work, including scripts to
-control those activities.  However, it does not include the work's
-System Libraries, or general-purpose tools or generally available free
-programs which are used unmodified in performing those activities but
-which are not part of the work.  For example, Corresponding Source
-includes interface definition files associated with source files for
-the work, and the source code for shared libraries and dynamically
-linked subprograms that the work is specifically designed to require,
-such as by intimate data communication or control flow between those
-subprograms and other parts of the work.
-  The Corresponding Source need not include anything that users
-can regenerate automatically from other parts of the Corresponding
-  The Corresponding Source for a work in source code form is that
-same work.
-  2. Basic Permissions.
-  All rights granted under this License are granted for the term of
-copyright on the Program, and are irrevocable provided the stated
-conditions are met.  This License explicitly affirms your unlimited
-permission to run the unmodified Program.  The output from running a
-covered work is covered by this License only if the output, given its
-content, constitutes a covered work.  This License acknowledges your
-rights of fair use or other equivalent, as provided by copyright law.
-  You may make, run and propagate covered works that you do not
-convey, without conditions so long as your license otherwise remains
-in force.  You may convey covered works to others for the sole purpose
-of having them make modifications exclusively for you, or provide you
-with facilities for running those works, provided that you comply with
-the terms of this License in conveying all material for which you do
-not control copyright.  Those thus making or running the covered works
-for you must do so exclusively on your behalf, under your direction
-and control, on terms that prohibit them from making any copies of
-your copyrighted material outside their relationship with you.
-  Conveying under any other circumstances is permitted solely under
-the conditions stated below.  Sublicensing is not allowed; section 10
-makes it unnecessary.
-  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
-  No covered work shall be deemed part of an effective technological
-measure under any applicable law fulfilling obligations under article
-11 of the WIPO copyright treaty adopted on 20 December 1996, or
-similar laws prohibiting or restricting circumvention of such
-  When you convey a covered work, you waive any legal power to forbid
-circumvention of technological measures to the extent such circumvention
-is effected by exercising rights under this License with respect to
-the covered work, and you disclaim any intention to limit operation or
-modification of the work as a means of enforcing, against the work's
-users, your or third parties' legal rights to forbid circumvention of
-technological measures.
-  4. Conveying Verbatim Copies.
-  You may convey 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;
-keep intact all notices stating that this License and any
-non-permissive terms added in accord with section 7 apply to the code;
-keep intact all notices of the absence of any warranty; and give all
-recipients a copy of this License along with the Program.
-  You may charge any price or no price for each copy that you convey,
-and you may offer support or warranty protection for a fee.
-  5. Conveying Modified Source Versions.
-  You may convey a work based on the Program, or the modifications to
-produce it from the Program, in the form of source code under the
-terms of section 4, provided that you also meet all of these conditions:
-    a) The work must carry prominent notices stating that you modified
-    it, and giving a relevant date.
-    b) The work must carry prominent notices stating that it is
-    released under this License and any conditions added under section
-    7.  This requirement modifies the requirement in section 4 to
-    "keep intact all notices".
-    c) You must license the entire work, as a whole, under this
-    License to anyone who comes into possession of a copy.  This
-    License will therefore apply, along with any applicable section 7
-    additional terms, to the whole of the work, and all its parts,
-    regardless of how they are packaged.  This License gives no
-    permission to license the work in any other way, but it does not
-    invalidate such permission if you have separately received it.
-    d) If the work has interactive user interfaces, each must display
-    Appropriate Legal Notices; however, if the Program has interactive
-    interfaces that do not display Appropriate Legal Notices, your
-    work need not make them do so.
-  A compilation of a covered work with other separate and independent
-works, which are not by their nature extensions of the covered work,
-and which are not combined with it such as to form a larger program,
-in or on a volume of a storage or distribution medium, is called an
-"aggregate" if the compilation and its resulting copyright are not
-used to limit the access or legal rights of the compilation's users
-beyond what the individual works permit.  Inclusion of a covered work
-in an aggregate does not cause this License to apply to the other
-parts of the aggregate.
-  6. Conveying Non-Source Forms.
-  You may convey a covered work in object code form under the terms
-of sections 4 and 5, provided that you also convey the
-machine-readable Corresponding Source under the terms of this License,
-in one of these ways:
-    a) Convey the object code in, or embodied in, a physical product
-    (including a physical distribution medium), accompanied by the
-    Corresponding Source fixed on a durable physical medium
-    customarily used for software interchange.
-    b) Convey the object code in, or embodied in, a physical product
-    (including a physical distribution medium), accompanied by a
-    written offer, valid for at least three years and valid for as
-    long as you offer spare parts or customer support for that product
-    model, to give anyone who possesses the object code either (1) a
-    copy of the Corresponding Source for all the software in the
-    product that is covered by this License, on a durable physical
-    medium customarily used for software interchange, for a price no
-    more than your reasonable cost of physically performing this
-    conveying of source, or (2) access to copy the
-    Corresponding Source from a network server at no charge.
-    c) Convey individual copies of the object code with a copy of the
-    written offer to provide the Corresponding Source.  This
-    alternative is allowed only occasionally and noncommercially, and
-    only if you received the object code with such an offer, in accord
-    with subsection 6b.
-    d) Convey the object code by offering access from a designated
-    place (gratis or for a charge), and offer equivalent access to the
-    Corresponding Source in the same way through the same place at no
-    further charge.  You need not require recipients to copy the
-    Corresponding Source along with the object code.  If the place to
-    copy the object code is a network server, the Corresponding Source
-    may be on a different server (operated by you or a third party)
-    that supports equivalent copying facilities, provided you maintain
-    clear directions next to the object code saying where to find the
-    Corresponding Source.  Regardless of what server hosts the
-    Corresponding Source, you remain obligated to ensure that it is
-    available for as long as needed to satisfy these requirements.
-    e) Convey the object code using peer-to-peer transmission, provided
-    you inform other peers where the object code and Corresponding
-    Source of the work are being offered to the general public at no
-    charge under subsection 6d.
-  A separable portion of the object code, whose source code is excluded
-from the Corresponding Source as a System Library, need not be
-included in conveying the object code work.
-  A "User Product" is either (1) a "consumer product", which means any
-tangible personal property which is normally used for personal, family,
-or household purposes, or (2) anything designed or sold for incorporation
-into a dwelling.  In determining whether a product is a consumer product,
-doubtful cases shall be resolved in favor of coverage.  For a particular
-product received by a particular user, "normally used" refers to a
-typical or common use of that class of product, regardless of the status
-of the particular user or of the way in which the particular user
-actually uses, or expects or is expected to use, the product.  A product
-is a consumer product regardless of whether the product has substantial
-commercial, industrial or non-consumer uses, unless such uses represent
-the only significant mode of use of the product.
-  "Installation Information" for a User Product means any methods,
-procedures, authorization keys, or other information required to install
-and execute modified versions of a covered work in that User Product from
-a modified version of its Corresponding Source.  The information must
-suffice to ensure that the continued functioning of the modified object
-code is in no case prevented or interfered with solely because
-modification has been made.
-  If you convey an object code work under this section in, or with, or
-specifically for use in, a User Product, and the conveying occurs as
-part of a transaction in which the right of possession and use of the
-User Product is transferred to the recipient in perpetuity or for a
-fixed term (regardless of how the transaction is characterized), the
-Corresponding Source conveyed under this section must be accompanied
-by the Installation Information.  But this requirement does not apply
-if neither you nor any third party retains the ability to install
-modified object code on the User Product (for example, the work has
-been installed in ROM).
-  The requirement to provide Installation Information does not include a
-requirement to continue to provide support service, warranty, or updates
-for a work that has been modified or installed by the recipient, or for
-the User Product in which it has been modified or installed.  Access to a
-network may be denied when the modification itself materially and
-adversely affects the operation of the network or violates the rules and
-protocols for communication across the network.
-  Corresponding Source conveyed, and Installation Information provided,
-in accord with this section must be in a format that is publicly
-documented (and with an implementation available to the public in
-source code form), and must require no special password or key for
-unpacking, reading or copying.
-  7. Additional Terms.
-  "Additional permissions" are terms that supplement the terms of this
-License by making exceptions from one or more of its conditions.
-Additional permissions that are applicable to the entire Program shall
-be treated as though they were included in this License, to the extent
-that they are valid under applicable law.  If additional permissions
-apply only to part of the Program, that part may be used separately
-under those permissions, but the entire Program remains governed by
-this License without regard to the additional permissions.
-  When you convey a copy of a covered work, you may at your option
-remove any additional permissions from that copy, or from any part of
-it.  (Additional permissions may be written to require their own
-removal in certain cases when you modify the work.)  You may place
-additional permissions on material, added by you to a covered work,
-for which you have or can give appropriate copyright permission.
-  Notwithstanding any other provision of this License, for material you
-add to a covered work, you may (if authorized by the copyright holders of
-that material) supplement the terms of this License with terms:
-    a) Disclaiming warranty or limiting liability differently from the
-    terms of sections 15 and 16 of this License; or
-    b) Requiring preservation of specified reasonable legal notices or
-    author attributions in that material or in the Appropriate Legal
-    Notices displayed by works containing it; or
-    c) Prohibiting misrepresentation of the origin of that material, or
-    requiring that modified versions of such material be marked in
-    reasonable ways as different from the original version; or
-    d) Limiting the use for publicity purposes of names of licensors or
-    authors of the material; or
-    e) Declining to grant rights under trademark law for use of some
-    trade names, trademarks, or service marks; or
-    f) Requiring indemnification of licensors and authors of that
-    material by anyone who conveys the material (or modified versions of
-    it) with contractual assumptions of liability to the recipient, for
-    any liability that these contractual assumptions directly impose on
-    those licensors and authors.
-  All other non-permissive additional terms are considered "further
-restrictions" within the meaning of section 10.  If the Program as you
-received it, or any part of it, contains a notice stating that it is
-governed by this License along with a term that is a further
-restriction, you may remove that term.  If a license document contains
-a further restriction but permits relicensing or conveying under this
-License, you may add to a covered work material governed by the terms
-of that license document, provided that the further restriction does
-not survive such relicensing or conveying.
-  If you add terms to a covered work in accord with this section, you
-must place, in the relevant source files, a statement of the
-additional terms that apply to those files, or a notice indicating
-where to find the applicable terms.
-  Additional terms, permissive or non-permissive, may be stated in the
-form of a separately written license, or stated as exceptions;
-the above requirements apply either way.
-  8. Termination.
-  You may not propagate or modify a covered work except as expressly
-provided under this License.  Any attempt otherwise to propagate or
-modify it is void, and will automatically terminate your rights under
-this License (including any patent licenses granted under the third
-paragraph of section 11).
-  However, if you cease all violation of this License, then your
-license from a particular copyright holder is reinstated (a)
-provisionally, unless and until the copyright holder explicitly and
-finally terminates your license, and (b) permanently, if the copyright
-holder fails to notify you of the violation by some reasonable means
-prior to 60 days after the cessation.
-  Moreover, your license from a particular copyright holder is
-reinstated permanently if the copyright holder notifies you of the
-violation by some reasonable means, this is the first time you have
-received notice of violation of this License (for any work) from that
-copyright holder, and you cure the violation prior to 30 days after
-your receipt of the notice.
-  Termination of your rights under this section does not terminate the
-licenses of parties who have received copies or rights from you under
-this License.  If your rights have been terminated and not permanently
-reinstated, you do not qualify to receive new licenses for the same
-material under section 10.
-  9. Acceptance Not Required for Having Copies.
-  You are not required to accept this License in order to receive or
-run a copy of the Program.  Ancillary propagation of a covered work
-occurring solely as a consequence of using peer-to-peer transmission
-to receive a copy likewise does not require acceptance.  However,
-nothing other than this License grants you permission to propagate or
-modify any covered work.  These actions infringe copyright if you do
-not accept this License.  Therefore, by modifying or propagating a
-covered work, you indicate your acceptance of this License to do so.
-  10. Automatic Licensing of Downstream Recipients.
-  Each time you convey a covered work, the recipient automatically
-receives a license from the original licensors, to run, modify and
-propagate that work, subject to this License.  You are not responsible
-for enforcing compliance by third parties with this License.
-  An "entity transaction" is a transaction transferring control of an
-organization, or substantially all assets of one, or subdividing an
-organization, or merging organizations.  If propagation of a covered
-work results from an entity transaction, each party to that
-transaction who receives a copy of the work also receives whatever
-licenses to the work the party's predecessor in interest had or could
-give under the previous paragraph, plus a right to possession of the
-Corresponding Source of the work from the predecessor in interest, if
-the predecessor has it or can get it with reasonable efforts.
-  You may not impose any further restrictions on the exercise of the
-rights granted or affirmed under this License.  For example, you may
-not impose a license fee, royalty, or other charge for exercise of
-rights granted under this License, and you may not initiate litigation
-(including a cross-claim or counterclaim in a lawsuit) alleging that
-any patent claim is infringed by making, using, selling, offering for
-sale, or importing the Program or any portion of it.
-  11. Patents.
-  A "contributor" is a copyright holder who authorizes use under this
-License of the Program or a work on which the Program is based.  The
-work thus licensed is called the contributor's "contributor version".
-  A contributor's "essential patent claims" are all patent claims
-owned or controlled by the contributor, whether already acquired or
-hereafter acquired, that would be infringed by some manner, permitted
-by this License, of making, using, or selling its contributor version,
-but do not include claims that would be infringed only as a
-consequence of further modification of the contributor version.  For
-purposes of this definition, "control" includes the right to grant
-patent sublicenses in a manner consistent with the requirements of
-this License.
-  Each contributor grants you a non-exclusive, worldwide, royalty-free
-patent license under the contributor's essential patent claims, to
-make, use, sell, offer for sale, import and otherwise run, modify and
-propagate the contents of its contributor version.
-  In the following three paragraphs, a "patent license" is any express
-agreement or commitment, however denominated, not to enforce a patent
-(such as an express permission to practice a patent or covenant not to
-sue for patent infringement).  To "grant" such a patent license to a
-party means to make such an agreement or commitment not to enforce a
-patent against the party.
-  If you convey a covered work, knowingly relying on a patent license,
-and the Corresponding Source of the work is not available for anyone
-to copy, free of charge and under the terms of this License, through a
-publicly available network server or other readily accessible means,
-then you must either (1) cause the Corresponding Source to be so
-available, or (2) arrange to deprive yourself of the benefit of the
-patent license for this particular work, or (3) arrange, in a manner
-consistent with the requirements of this License, to extend the patent
-license to downstream recipients.  "Knowingly relying" means you have
-actual knowledge that, but for the patent license, your conveying the
-covered work in a country, or your recipient's use of the covered work
-in a country, would infringe one or more identifiable patents in that
-country that you have reason to believe are valid.
-  If, pursuant to or in connection with a single transaction or
-arrangement, you convey, or propagate by procuring conveyance of, a
-covered work, and grant a patent license to some of the parties
-receiving the covered work authorizing them to use, propagate, modify
-or convey a specific copy of the covered work, then the patent license
-you grant is automatically extended to all recipients of the covered
-work and works based on it.
-  A patent license is "discriminatory" if it does not include within
-the scope of its coverage, prohibits the exercise of, or is
-conditioned on the non-exercise of one or more of the rights that are
-specifically granted under this License.  You may not convey a covered
-work if you are a party to an arrangement with a third party that is
-in the business of distributing software, under which you make payment
-to the third party based on the extent of your activity of conveying
-the work, and under which the third party grants, to any of the
-parties who would receive the covered work from you, a discriminatory
-patent license (a) in connection with copies of the covered work
-conveyed by you (or copies made from those copies), or (b) primarily
-for and in connection with specific products or compilations that
-contain the covered work, unless you entered into that arrangement,
-or that patent license was granted, prior to 28 March 2007.
-  Nothing in this License shall be construed as excluding or limiting
-any implied license or other defenses to infringement that may
-otherwise be available to you under applicable patent law.
-  12. No Surrender of Others' Freedom.
-  If 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 convey a
-covered work so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you may
-not convey it at all.  For example, if you agree to terms that obligate you
-to collect a royalty for further conveying from those to whom you convey
-the Program, the only way you could satisfy both those terms and this
-License would be to refrain entirely from conveying the Program.
-  13. Use with the GNU Affero General Public License.
-  Notwithstanding any other provision of this License, you have
-permission to link or combine any covered work with a work licensed
-under version 3 of the GNU Affero General Public License into a single
-combined work, and to convey the resulting work.  The terms of this
-License will continue to apply to the part which is the covered work,
-but the special requirements of the GNU Affero General Public License,
-section 13, concerning interaction through a network will apply to the
-combination as such.
-  14. Revised Versions of this License.
-  The Free Software Foundation may publish revised and/or new versions of
-the GNU 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 that a certain numbered version of the GNU General
-Public License "or any later version" applies to it, you have the
-option of following the terms and conditions either of that numbered
-version or of any later version published by the Free Software
-Foundation.  If the Program does not specify a version number of the
-GNU General Public License, you may choose any version ever published
-by the Free Software Foundation.
-  If the Program specifies that a proxy can decide which future
-versions of the GNU General Public License can be used, that proxy's
-public statement of acceptance of a version permanently authorizes you
-to choose that version for the Program.
-  Later license versions may give you additional or different
-permissions.  However, no additional obligations are imposed on any
-author or copyright holder as a result of your choosing to follow a
-later version.
-  15. Disclaimer of Warranty.
-  16. Limitation of Liability.
-  17. Interpretation of Sections 15 and 16.
-  If the disclaimer of warranty and limitation of liability provided
-above cannot be given local legal effect according to their terms,
-reviewing courts shall apply local law that most closely approximates
-an absolute waiver of all civil liability in connection with the
-Program, unless a warranty or assumption of liability accompanies a
-copy of the Program in return for a fee.
-                     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
-state 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 3 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
-    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, see <http://www.gnu.org/licenses/>.
-Also add information on how to contact you by electronic and paper mail.
-  If the program does terminal interaction, make it output a short
-notice like this when it starts in an interactive mode:
-    {project}  Copyright (C) {year}  {fullname}
-    This program 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, your program's commands
-might be different; for a GUI interface, you would use an "about box".
-  You should also get your employer (if you work as a programmer) or school,
-if any, to sign a "copyright disclaimer" for the program, if necessary.
-For more information on this, and how to apply and follow the GNU GPL, see
-  The GNU 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.  But first, please read

Added: trunk/Master/texmf-dist/doc/latex/oplotsymbl/LICENSE.md
--- trunk/Master/texmf-dist/doc/latex/oplotsymbl/LICENSE.md	                        (rev 0)
+++ trunk/Master/texmf-dist/doc/latex/oplotsymbl/LICENSE.md	2017-01-30 23:30:01 UTC (rev 43091)
@@ -0,0 +1,415 @@
+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.
+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.
+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.
+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'.
+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.
+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.
+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.
+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
+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.

Deleted: trunk/Master/texmf-dist/doc/latex/oplotsymbl/README.TEXLIVE
--- trunk/Master/texmf-dist/doc/latex/oplotsymbl/README.TEXLIVE	2017-01-30 01:05:32 UTC (rev 43090)
+++ trunk/Master/texmf-dist/doc/latex/oplotsymbl/README.TEXLIVE	2017-01-30 23:30:01 UTC (rev 43091)
@@ -1,7 +0,0 @@
-The following files have been removed in the TeX Live installation of
-the current package, typically due to duplication, lack of space, or
-missing source code.  You can find these files on CTAN at
-	http://mirror.ctan.org/macros/latex/contrib/oplotsymbl
-If questions or concerns, email tex-live at tug.org.
-	oPlotSymbl-Manual-en.pdf

Modified: trunk/Master/texmf-dist/doc/latex/oplotsymbl/README.md
--- trunk/Master/texmf-dist/doc/latex/oplotsymbl/README.md	2017-01-30 01:05:32 UTC (rev 43090)
+++ trunk/Master/texmf-dist/doc/latex/oplotsymbl/README.md	2017-01-30 23:30:01 UTC (rev 43091)
@@ -1,2 +1,25 @@
-# oPlotSymbl-LaTeX
+# oPlotSymbl - A LaTeX Package for Symbols for Scientific Plots
 This package is named oPlotSymbl and it includes symbols, which are not easily available. Especially, these symbols are used in scientific plots, but the potential user is allowed to use in another way. 
+It exists a manual for this package. Please read this first. To install this LaTeX package manually, follow these steps (all steps are for my preferred LaTeX distribution „Tex Live“!):
+### For installing on Windows 7 (and above): 
+__Windows 7:__ C:\Users\<user name>\texmf\tex\latex\local\
+I’m not able to test this for Windows 7 and especially for the new Windows 10. If this directory is wrong, it would be really nice to inform me! 
+Perhaps it is necessary to reload LaTeX database which includes a list of all installed packages. To tell LaTeX/TeX Live that there is a new package, I would recommend this thread: 
+### For installing on Mac (Mac OS X and macOS): 
+__For Mac:__ /Users/<user name>/Library/texmf/tex/latex/local/
+This should work for 10.9 and above. If not, then be so kind to inform me. As I know it is not necessary to reload database. It should work automatically after restart.
+Thanks in advance for telling any problems to make this work even better!
\ No newline at end of file

Added: trunk/Master/texmf-dist/doc/latex/oplotsymbl/literatur.bib
--- trunk/Master/texmf-dist/doc/latex/oplotsymbl/literatur.bib	                        (rev 0)
+++ trunk/Master/texmf-dist/doc/latex/oplotsymbl/literatur.bib	2017-01-30 23:30:01 UTC (rev 43091)
@@ -0,0 +1,58 @@
+% This file was created with JabRef 2.7b.
+% Encoding: UTF8
+%====================Beginn der Messwerte-/Internetquellen=========================%
+ at MISC{xcolor,
+	author = {Uwe Kern},
+	title = {xcolor},
+	edition = {2.11},
+	editor = {},
+	publisher = {},
+	howpublished = {CTAN},
+	year = {2007},
+	urldate = {13.02.2016},
+	note = {time: 12:42},
+	url = {https://www.ctan.org/pkg/xcolor?lang=de}
+ at MISC{tikz,
+	author = {Christian Feuersänger and Till Tantau},
+	title = {TikZ},
+	edition = {3.0.1a},
+	editor = {},
+	publisher = {},
+	howpublished = {CTAN},
+	year = {2015},
+	urldate = {13.02.2016},
+	note = {time: 12:43},
+	url = {https://www.ctan.org/pkg/pgf}
+ at MISC{ctan,
+	author = {CTAN},
+	title = {CTAN},
+	edition = {},
+	editor = {},
+	publisher = {},
+	howpublished = {},
+	year = {2016},
+	urldate = {13.02.2016},
+	note = {time: 12:44},
+	url = {https://www.ctan.org}
+ at MISC{texlive,
+	author = {TeXLive},
+	title = {TeXLive},
+	edition = {},
+	editor = {},
+	publisher = {},
+	howpublished = {},
+	year = {2016},
+	urldate = {13.02.2016},
+	note = {time: 12:45},
+	url = {https://www.tug.org/texlive/}

Added: trunk/Master/texmf-dist/doc/latex/oplotsymbl/oPlotSymbl-Manual-en.pdf
(Binary files differ)

Index: trunk/Master/texmf-dist/doc/latex/oplotsymbl/oPlotSymbl-Manual-en.pdf
--- trunk/Master/texmf-dist/doc/latex/oplotsymbl/oPlotSymbl-Manual-en.pdf	2017-01-30 01:05:32 UTC (rev 43090)
+++ trunk/Master/texmf-dist/doc/latex/oplotsymbl/oPlotSymbl-Manual-en.pdf	2017-01-30 23:30:01 UTC (rev 43091)

Property changes on: trunk/Master/texmf-dist/doc/latex/oplotsymbl/oPlotSymbl-Manual-en.pdf
Added: svn:mime-type
## -0,0 +1 ##
\ No newline at end of property
Added: trunk/Master/texmf-dist/doc/latex/oplotsymbl/oPlotSymbl-Manual-en.tex
--- trunk/Master/texmf-dist/doc/latex/oplotsymbl/oPlotSymbl-Manual-en.tex	                        (rev 0)
+++ trunk/Master/texmf-dist/doc/latex/oplotsymbl/oPlotSymbl-Manual-en.tex	2017-01-30 23:30:01 UTC (rev 43091)
@@ -0,0 +1,476 @@
+pdftitle={oPlotSymbl Package Introduction}, 
+pdfauthor={B. Michel Döhring, JLU Gießen},
+%%%% colours for listings %%%%
+%%%% Style settings for listings %%%%
+    backgroundcolor=\color{backcolour},   
+    commentstyle=\color{codegreen},
+    keywordstyle=\color{magenta},
+    numberstyle=\tiny\color{codegray},
+    stringstyle=\color{codepurple},
+    basicstyle=\footnotesize,
+    breakatwhitespace=false,         
+    breaklines=true,                 
+    captionpos=b,                    
+    keepspaces=true,                 
+    numbers=left,                    
+    numbersep=5pt,                  
+    showspaces=false,                
+    showstringspaces=false,
+    showtabs=false,                  
+    tabsize=2
+\newcommand{\linia}{\rule{\linewidth}{0.5pt} \rule{\linewidth}{0.5pt}}
+% my own titles
+{\huge \textsc{\@title}}
+E-Mail: \href{mailto:micheld.93@ gmail.com}{micheld.93 at gmail.com}\\
+% custom footers and headers
+\rfoot{Page \thepage\ /\ \pageref*{LastPage}}
+\title{{\color[HTML]{FF0000} oPlotSymbl Package Introduction}}
+\author{B. Michel Döhring}
+\date{28/01/2017 (V1.2)}
+%%% Table of Contents %%%
+% 1 1/2 line space
+% \clearpage
+This package is named "\textit{oPlotSymbl}" and it includes symbols, which are not easily available. Especially, these symbols are used in scientific plots, but the potential user is allowed to use in another way. The idea came to my mind during writing my bachelor thesis, where I needed many plots with many different symbols. 
+This package can be loaded with the following command: 
+There are no additional options implemented yet. Now, it is important to me to mention the used packages. \textit{oPlotSymbl} uses \textit{TikZ} \cite{tikz} and so it loads the \textit{xcolor} package automatically. That means it is possible to use the whole beauty of \textit{xcolor}'s \cite{xcolor} colour palette.
+\section{Version History}
+I will collect all changes in this chapter, here. 
+\subsection{Version 1.2 (28.01.2017)}
+    \item make the manuals's tex file available for everybody
+    \item hope the final release for tex live is possible now
+    \item some people ask to change the name to oPlotSymbol, but I don't see any advantages in it. Sorry.
+    \item share the links on CTAN and GitHub
+    \item some changes on the code itself but NO, absolutely NO changes for the user 
+\section{Repository and Contact}
+The repository/this package is available on GitHub and through CTAN \cite{ctan} and TeXLive \cite{texlive}. You will find it here:
+    \item \url{https://www.ctan.org/pkg/oplotsymbl}
+    \item \url{https://github.com/micheld93/oPlotSymbl-LaTeX/}  
+If you have suggestions, problems or you only want to say "Hi", then contact me at \href{mailto:micheld.93@ gmail.com}{micheld.93 at gmail.com}.
+\section{Symbols and Commands}
+The following sub-sections include all defined symbols sorted in categories. The names are chosen to work with other packages which includes symbols. If you want to use these symbols in the running text, you will use two curved brackets directly after the command to have space between symbol and the following word. I tried to make this package as easy as possible to understand and use. This is why the commands are as close as possible to each other.  
+Symbol            & Command                       & Suffix & Explanation & Description                                       \\ \hline \hline
+\trianglepa       & \lstinline!\trianglepa!     & pa     & peak above   & none                                              \\ \hline
+\trianglepafill   & \lstinline!\trianglepafill! & pa     & peak above   & filled triangle                                   \\ \hline
+\trianglepadot    & \lstinline!\trianglepadot!                & pa     & peak above   & triangle with dot                                 \\ \hline
+\trianglepalinev  & \lstinline!\trianglepalinev!              & pa     & peak above   & triangle with vertical line                       \\ \hline
+\trianglepalineh  & \lstinline!\trianglepalineh!              & pa     & peak above   & triangle with horizontal line                     \\ \hline
+\trianglepalinevh & \lstinline!\trianglepalinevh!             & pa     & peak above   & triangle with both lines \\ \hline
+\trianglepacross  & \lstinline!\trianglepacross!              & pa     & peak above   & triangle with cross                               \\ \hline
+\trianglepafillha & \lstinline!\trianglepafillha!             & pa     & peak above   & half filled triangle (above)                      \\ \hline
+\trianglepafillhb & \lstinline!\trianglepafillhb!             & pa     & peak above   & half filled triangle (below)                      \\ \hline
+\trianglepafillhr & \lstinline!\trianglepafillhr!             & pa     & peak above   & half filled triangle (right)                      \\ \hline
+\trianglepafillhl & \lstinline!\trianglepafillhl!             & pa     & peak above   & half filled triangle (left)                       \\ \hline
+\subsubsection{Additional Triangles}
+All other triangles follow the syntax shown above. It's always 
+	\triangle-suffixDESCRIPTION
+"DESCRIPTION" is to exchange with terms like "cross" or "dot" etc. "-suffix" means the orientation of the triangle's highest peak. 
+Other orientations are shown in the table below:
+Suffix	&	Explanation	   \\ \hline \hline
+pa & peak above \\ \hline
+pb & peak below \\ \hline
+pr & peak right \\ \hline
+pl & peak left \\ \hline
+\subsection{Circle (here: Circlet)}
+Some other packages use \lstinline{\circle} or \lstinline{\circ} for circles, so I decided to use \lstinline{\circlet} instead of other cryptic abbreviations.    
+Symbol            & Command  &  Description            \\ \hline \hline
+\circlet       & \lstinline!\circlet!        & none                                              \\ \hline
+\circletfill   & \lstinline!\circletfill!     & filled circle(let)                                   \\ \hline
+\circletdot    & \lstinline!\circletdot!                    & circle(let) with dot                                 \\ \hline
+\circletlinev  & \lstinline!\circletlinev!                  & circle(let) with vertical line                       \\ \hline
+\circletlineh  & \lstinline!\circletlineh!                  & circle(let) with horizontal line                     \\ \hline
+\circletlinevh & \lstinline!\circletlinevh!                 & circle(let) with both lines \\ \hline
+\circletcross  & \lstinline!\circletcross!                  & circle(let) with cross                               \\ \hline
+\circletfillha & \lstinline!\circletfillha!                 & half filled circle(let) (above)                      \\ \hline
+\circletfillhb & \lstinline!\circletfillhb!                 & half filled circle(let) (below)                      \\ \hline
+\circletfillhr & \lstinline!\circletfillhr!                 & half filled circle(let) (right)                      \\ \hline
+\circletfillhl & \lstinline!\circletfillhl!                 & half filled circle(let) (left)                       \\ \hline
+\subsection{Pentagon (here: Pentago)}
+The same problem as we know from circle/circlet happens with pentagon. I decided to use "pentago", so it's near enough to pentagon. 
+Symbol            & Command  &  Description            \\ \hline \hline
+\pentago       & \lstinline!\pentago!        & none                                              \\ \hline
+\pentagofill   & \lstinline!\pentagofill!     & filled pentago                                   \\ \hline
+\pentagodot    & \lstinline!\pentagodot!                    & pentago with dot                                 \\ \hline
+\pentagolinev  & \lstinline!\pentagolinev!                  & pentago with vertical line                       \\ \hline
+\pentagolineh  & \lstinline!\pentagolineh!                  & pentago with horizontal line                     \\ \hline
+\pentagolinevh & \lstinline!\pentagolinevh!                 & pentago with both lines \\ \hline
+\pentagocross  & \lstinline!\pentagocross!                  & pentago with cross                               \\ \hline
+\pentagofillha & \lstinline!\pentagofillha!                 & half filled pentago (above)                      \\ \hline
+\pentagofillhb & \lstinline!\pentagofillhb!                 & half filled pentago (below)                      \\ \hline
+\pentagofillhr & \lstinline!\pentagofillhr!                 & half filled pentago (right)                      \\ \hline
+\pentagofillhl & \lstinline!\pentagofillhl!                 & half filled pentago (left)                       \\ \hline
+\subsection{Star (here: Starlet)}
+Symbol            & Command  &  Description            \\ \hline \hline
+\starlet       & \lstinline!\starlet!        & none                                              \\ \hline
+\starletfill   & \lstinline!\starletfill!     & filled starlet                                   \\ \hline
+\starletdot    & \lstinline!\starletdot!                    & starlet with dot                                 \\ \hline
+\starletlinev  & \lstinline!\starletlinev!                  & starlet with vertical line                       \\ \hline
+\starletlineh  & \lstinline!\starletlineh!                  & starlet with horizontal line                     \\ \hline
+\starletlinevh & \lstinline!\starletlinevh!                 & starlet with both lines \\ \hline
+\starletcross  & \lstinline!\starletcross!                  & starlet with cross                               \\ \hline
+\starletfillha & \lstinline!\starletfillha!                 & half filled starlet (above)                      \\ \hline
+\starletfillhb & \lstinline!\starletfillhb!                 & half filled starlet (below)                      \\ \hline
+\starletfillhr & \lstinline!\starletfillhr!                 & half filled starlet (right)                      \\ \hline
+\starletfillhl & \lstinline!\starletfillhl!                 & half filled starlet (left)                       \\ \hline
+Symbol            & Command  &  Description            \\ \hline \hline
+\rhombus       & \lstinline!\rhombus!        & none                                              \\ \hline
+\rhombusfill   & \lstinline!\rhombusfill!     & filled rhombus                                   \\ \hline
+\rhombusdot    & \lstinline!\rhombusdot!                    & rhombus with dot                                 \\ \hline
+\rhombuslinev  & \lstinline!\rhombuslinev!                  & rhombus with vertical line                       \\ \hline
+\rhombuslineh  & \lstinline!\rhombuslineh!                  & rhombus with horizontal line                     \\ \hline
+\rhombuslinevh & \lstinline!\rhombuslinevh!                 & rhombus with both lines \\ \hline
+\rhombuscross  & \lstinline!\rhombuscross!                  & rhombus with cross                               \\ \hline
+\rhombusfillha & \lstinline!\rhombusfillha!                 & half filled rhombus (above)                      \\ \hline
+\rhombusfillhb & \lstinline!\rhombusfillhb!                 & half filled rhombus (below)                      \\ \hline
+\rhombusfillhr & \lstinline!\rhombusfillhr!                 & half filled rhombus (right)                      \\ \hline
+\rhombusfillhl & \lstinline!\rhombusfillhl!                 & half filled rhombus (left)                       \\ \hline
+\subsection{Hexagon (here: Hexago)}
+Well, we already know it. Hexagon is used in other packages, so there is a necessity to use different words. 
+Symbol            & Command  &  Description            \\ \hline \hline
+\hexago       & \lstinline!\hexago!        & none                                              \\ \hline
+\hexagofill   & \lstinline!\hexagofill!     & filled hexago                                   \\ \hline
+\hexagodot    & \lstinline!\hexagodot!                    & hexago with dot                                 \\ \hline
+\hexagolinev  & \lstinline!\hexagolinev!                  & hexago with vertical line                       \\ \hline
+\hexagolineh  & \lstinline!\hexagolineh!                  & hexago with horizontal line                     \\ \hline
+\hexagolinevh & \lstinline!\hexagolinevh!                 & hexago with both lines \\ \hline
+\hexagocross  & \lstinline!\hexagocross!                  & hexago with cross                               \\ \hline
+\hexagofillha & \lstinline!\hexagofillha!                 & half filled hexago (above)                      \\ \hline
+\hexagofillhb & \lstinline!\hexagofillhb!                 & half filled hexago (below)                      \\ \hline
+\hexagofillhr & \lstinline!\hexagofillhr!                 & half filled hexago (right)                      \\ \hline
+\hexagofillhl & \lstinline!\hexagofillhl!                 & half filled hexago (left)                       \\ \hline
+To avoid problems with other commands, I decided to use the frankenword \textbf{"squad"} (it's a composition of english \textit{square} and german or non-mathematical \textit{quadrat}).
+Symbol            & Command  &  Description            \\ \hline \hline
+\squad       & \lstinline!\squad!        & none                                              \\ \hline
+\squadfill   & \lstinline!\squadfill!     & filled square                                   \\ \hline
+\squaddot    & \lstinline!\squaddot!                    & square with dot                                 \\ \hline
+\squadlinev  & \lstinline!\squadlinev!                  & square with vertical line                       \\ \hline
+\squadlineh  & \lstinline!\squadlineh!                  & square with horizontal line                     \\ \hline
+\squadlinevh & \lstinline!\squadlinevh!                 & square with both lines \\ \hline
+\squadcross  & \lstinline!\squadcross!                  & square with cross                               \\ \hline
+\squadfillha & \lstinline!\squadfillha!                 & half filled square (above)                      \\ \hline
+\squadfillhb & \lstinline!\squadfillhb!                 & half filled square (below)                      \\ \hline
+\squadfillhr & \lstinline!\squadfillhr!                 & half filled square (right)                      \\ \hline
+\squadfillhl & \lstinline!\squadfillhl!                 & half filled square (left)                       \\ \hline
+\subsection{Other Symbols}
+Symbol            & Command  &  Description            \\ \hline \hline
+\linev       & \lstinline!\linev!        & vertical line                                              \\ \hline
+\lineh   & \lstinline!\lineh!     & horizontal line                                   \\ \hline
+\scross    & \lstinline!\scross!                    & single cross                                 \\ \hline
+\linevh  & \lstinline!\linevh!                  & vertical and horizontal line                       \\ \hline
+\scrossvh  & \lstinline!\scrossvh!                  & single cross with lines                     \\ \hline
+\section{Font Size}
+All symbols use relative units for scaling. \LaTeX{} provides the unit "em" that means the width of the capital letter "M" in current font. \textit{oPlotSymbl} scales every symbol for you automatically and correctly. No need to worry. If you like to increase symbol size, then it's done with normal behavior for increasing font size. That's it.     
+\textit{oPlotSymbl} uses the \textit{xcolor} package so it is possible to use all pre-defined colours from \textit{xcolor} \cite{xcolor}. 
+You can colour the symbols very easily like this:
+There, you get a purple half filled pentagon. You can define own colours with the following command:
+\definecolor{colour's name}{colour palette}{specific code}
+There, you can define your own name for a missing colour. I recommend to use RGB or HTML as "colour palette". Between the last brackets you have to put your specific code that is determined trough your picked  "colour palette". I will give an example to make the start with \textit{oPlotSymbl} as easy as possible. 
+	\definecolor{black}{HTML}{000000}
+This listing gives us black. It uses a custom name, followed by the "colour palette" and then the colour code for chosen option. As shown above \textit{oPlotSymbl} follows normal \textit{xcolor} \cite{xcolor} commands.
+In addition, some colours are pre-defined for my own needs. These colours are:
+Colour                   & Colour Name   & Colour Name for Command & RGB Code \\ \hline \hline
+\cellcolor[RGB]{0,0,0} & black         & oblack                  & 0,0,0    \\ \hline
+\cellcolor[RGB]{255,0,0} & red           & ored                    & 255,0,0    \\ \hline
+\cellcolor[RGB]{0,255,0} & green         & ogreen                  & 0,255,0    \\ \hline
+\cellcolor[RGB]{0,0,255} & blue          & oblue                   & 0,0,255    \\ \hline
+\cellcolor[RGB]{0,255,255} & cyan          & ocyan                   & 0,255,255    \\ \hline
+\cellcolor[RGB]{255,0,255} & magenta       & omagenta                & 255,0,255    \\ \hline
+\cellcolor[RGB]{255,255,0} & yellow        & oyellow                 & 255,255,0    \\ \hline
+\cellcolor[RGB]{128,128,0} & dark yellow   & odyellow                & 128,128,0    \\ \hline
+\cellcolor[RGB]{0,0,128} & mariner blue  & omblue                  & 0,0,128    \\ \hline
+\cellcolor[RGB]{128,0,128} & purple        & opurple                 & 128,0,128    \\ \hline
+\cellcolor[RGB]{128,0,0} & brown         & obrown                  & 128,0,0    \\ \hline
+\cellcolor[RGB]{0,128,0} & olive green   & oolive                  & 0,128,0    \\ \hline
+\cellcolor[RGB]{0,128,128} & dark cyan     & odcyan                  & 0,128,128    \\ \hline
+\cellcolor[RGB]{0,0,160} & royel blue    & orblue                  & 0,0,160    \\ \hline
+\cellcolor[RGB]{255,128,0} & orange        & oorange                 & 255,128,0   \\ \hline
+\cellcolor[RGB]{128,0,255} & violet        & oviolet                 & 128,0,255    \\ \hline
+\cellcolor[RGB]{255,0,128} & pink          & opink                   & 255,0,128    \\ \hline
+\cellcolor[RGB]{255,255,255} & white         & owhite                  & 255,255,255    \\ \hline
+\cellcolor[RGB]{192,192,192} & light grey    & olgrey                  & 192,192,192    \\ \hline
+\cellcolor[RGB]{128,128,128} & grey          & ogrey                   & 128,128,128    \\ \hline
+\cellcolor[RGB]{255,255,128} & light yellow  & olyellow                & 255,255,128    \\ \hline
+\cellcolor[RGB]{128,255,255} & light cyan    & olcyan                  & 128,255,255    \\ \hline
+\cellcolor[RGB]{255,128,255} & light magenta & olmagenta               & 255,128,255    \\ \hline
+\cellcolor[RGB]{64,64,64} & dark grey     & odgrey                  & 64,64,64    \\ \hline
+% #####################
+% # Table of listings #
+% #####################
+% \lstlistoflistings
+% ##########################
+% # Literature with BibTeX #
+% ##########################
+    \cleardoublepage
+    \bibliography{literatur}
+    \bibliographystyle{babunsrt-fl}

Deleted: trunk/Master/texmf-dist/doc/latex/oplotsymbl/readmefirst.rtf
--- trunk/Master/texmf-dist/doc/latex/oplotsymbl/readmefirst.rtf	2017-01-30 01:05:32 UTC (rev 43090)
+++ trunk/Master/texmf-dist/doc/latex/oplotsymbl/readmefirst.rtf	2017-01-30 23:30:01 UTC (rev 43091)
@@ -1,31 +0,0 @@
-{\fonttbl\f0\fswiss\fcharset0 Helvetica;}
-{\author Michel D\'f6hring}
-{\*\copyright Michel D\'f6hring}}\paperw11900\paperh16840\margl1440\margr1440\vieww14840\viewh9640\viewkind0
-\f0\fs60 \cf0 oPlotSymbl Package
-\fs24 \
-\fs40 \
-It exists a manual for this package. Please read this first. To install this LaTeX package manually, follow these steps (all steps are for my preferred LaTeX distribution \'84TexLive\'93!):\
-Windows 7: C:\\Users\\<user name>\\texmf\\tex\\latex\\local\\\
-I\'92m not able to test this for Windows 7 and especially for the new Windows 10. If this directory is wrong, it would be really nice to inform me! Perhaps it is necessary to reload LaTeX database which includes a list of all installed packages. To tell LateX/TeXLive that there is a new package, I would recommend this thread: \
-{\field{\*\fldinst{HYPERLINK "http://tex.stackexchange.com/questions/20160/how-to-register-my-own-packages-or-classes-in-a-separate-drive-to-tex-live-insta"}}{\fldrslt http://tex.stackexchange.com/questions/20160/how-to-register-my-own-packages-or-classes-in-a-separate-drive-to-tex-live-insta}}\
-Thanks in advance!\
-For Mac: /Users/<user name>/Library/texmf/tex/latex/local/\
-This should work for 10.9 and above. If not, then be so kind to inform me. As I know it is not necessary to reload database. It should work automatically after restart.\
\ No newline at end of file

Modified: trunk/Master/texmf-dist/tex/latex/oplotsymbl/oplotsymbl.sty
--- trunk/Master/texmf-dist/tex/latex/oplotsymbl/oplotsymbl.sty	2017-01-30 01:05:32 UTC (rev 43090)
+++ trunk/Master/texmf-dist/tex/latex/oplotsymbl/oplotsymbl.sty	2017-01-30 23:30:01 UTC (rev 43091)
@@ -5,15 +5,15 @@
 %	Those symbols are used by some plotting tools etc.
 % --------------------------------------------------------------------------
-% Michel Döhring
+% B. Michel Döhring
 % --------------------------------------------------------------------------
-% GitHub: 
-% CTAN: 
+% GitHub: https://github.com/micheld93/oPlotSymbl-LaTeX/ 
+% CTAN: https://www.ctan.org/pkg/oplotsymbl 
 % --------------------------------------------------------------------------
 % If you have any questions, bugs or suggestions to report, please
 % feel free to get in touch.
-% Copyright 2016 Michel Döhring
+% Copyright 2017 B. Michel Döhring
 % This work may be distributed and/or modified under the
 % conditions of the LaTeX Project Public License, either version 1.3
@@ -30,12 +30,15 @@
 % The oplotsymbl package consists of the following files
 %  - oplotsymbl.sty
 %  - oplotsymbl-Manual-en.tex
-%  - readmefirst.rtf
+%  - literatur.bib
+%  - oplotsymbl-Manual-en.pdf
+%  - README.md
+%  - LICENSE.md
 % package information:
-\ProvidesPackage{oplotsymbl}[2015/12/12 Symbols, that are used in plots]
+\ProvidesPackage{oplotsymbl}[2017/01/28 Symbols, that are used in plots]
@@ -973,4 +976,5 @@
 2015/12/12 - first symbols added
 2016/01/15 - colours added 
 2016/02/12 - last symbols added
+2017/01/28 - minor changes on the manual, final release

Modified: trunk/Master/tlpkg/libexec/ctan2tds
--- trunk/Master/tlpkg/libexec/ctan2tds	2017-01-30 01:05:32 UTC (rev 43090)
+++ trunk/Master/tlpkg/libexec/ctan2tds	2017-01-30 23:30:01 UTC (rev 43091)
@@ -2966,7 +2966,6 @@
  'math-into-latex-4' => 'video.*zip|S.*\.pdf',          # nonfree
  'numericplots'  => '.*\.m',                            # matlab
  'oinuit'        => 'cmssbxo10.tfm',                    # should not be here
- 'oplotsymbl'	 => '\.pdf$',				# no source
  'padauk'	 => '\.pdf$',				# no source
  'pas-cours'     => '\.pdf$',                           # no source
  'pas-tableur'   => '\.pdf$',                           # no source

More information about the tex-live-commits mailing list