GSP/Panel
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Added Cyg-Win

Browse source
This commit is contained in:
Frank Harris 2026-06-06 18:46:40 -04:00
parent 82cbc206eb
commit 413c315806
10586 changed files with 3806249 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

674
Agent-Windows/OGP64/usr/share/doc/groff/COPYING Normal file
View file

@ -0,0 +1,674 @@
GNU GENERAL PUBLIC LICENSE
Version 3, 29 June 2007
Copyright (C) 2007 Free Software Foundation, Inc. <https://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
Source.
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
measures.
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.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.
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
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <https://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:
<program> Copyright (C) <year> <name of author>
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
<https://www.gnu.org/licenses/>.
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
<https://www.gnu.org/licenses/why-not-lgpl.html>.

25072
Agent-Windows/OGP64/usr/share/doc/groff/ChangeLog Normal file
View file

File diff suppressed because it is too large Load diff

574
Agent-Windows/OGP64/usr/share/doc/groff/HACKING Normal file
View file

@ -0,0 +1,574 @@
Copyright 2022-2026 G. Branden Robinson
Copying and distribution of this file, with or without
modification, are permitted in any medium without royalty provided
the copyright notice and this notice are preserved.
This file contains advice on developing and contributing to groff. It
assumes that developers will install the 'git' revision control
system and build groff using the instructions in 'INSTALL.REPO'.
Familiarize yourself with the structure of the source tree by studying
its 'MANIFEST' file at the top level.
Implementation languages
------------------------
Beyond what is said under "Dependencies" in 'INSTALL.extra',
contributors should note that due to the age of the code base, much of
the C++ dialect employed by groff components, while standard, is older
than C++98--closer to Annotated Reference Manual C++ (Ellis, Stroustrup;
Addison-Wesley, 1990). groff implements its own string class and the
Standard Template Library is little used. A modest effort is underway
to update the code to more idiomatic C++98. Where a C++11 feature
promises to be advantageous, it may be annotated in a code comment.
Portability notes:
* `std::size` is not available in C++98. Use `countof()`, which is
provided by the gnulib module `stdcountof-h` and expected to be
standardized in C2y, instead of `sizeof` and dividing.
* C++98 lacks value initialization for array types.
https://cplusplus.github.io/CWG/issues/178.html
Use `memset()` after allocating an array from the stack or the heap
unless you are sure that every path through subsequent logic
determines the contents of every array element.
Automake
--------
A document explaining the basics of GNU Automake and its usage in groff
is available in 'doc/automake.mom'; peruse a PDF rendering in
'doc/automake.pdf' in your build tree.
Tips:
* Don't define macros, including those ending in `_srcdir` or
`_builddir`, unless Automake itself demands them or you need to
interpolate them elsewhere in the *.am file.
* If you need to define a `_builddir` macro, give it a plain literal
value; do _not_ lead it with an interpolation of `top_builddir` or
anything else. Failure to heed this advice leads to out-of-tree build
failures with BSD Make.
Testing
-------
Running the test suite with 'make check' after building any substantive
change to groff logic is encouraged. You should certainly do so, and
confirm that the tests pass, before submitting patches to the groff
mailing list <groff@gnu.org> or Savannah issue tracker.
If you find a defect in a test script, that can be reported via Savannah
like any other bug.
Documenting changes
-------------------
The groff project has a long history and a large, varied audience.
Changes may need to be documented in up to three places depending on
their impact.
1. Changes should of course be documented in the Git commit message.
If a change alters only comments or formatting of source code, or
makes editorial changes to documentation or a test script, and does
not resolve a Savannah ticket, you can stop at that.
2. The 'ChangeLog' file follows the format and practices documented in
the GNU Coding Standards.
https://www.gnu.org/prep/standards/html_node/Change-Logs.html
The sub-projects in the 'contrib' directory each have their own
dedicated ChangeLog files. The file specifications documented there
are relative to the sub-project, not the root of the groff source
tree. When converted to a commit message, add 'contrib/$SUBPROJECT'
to the entries.
Apart from 'contrib', groff uses a single (current) 'ChangeLog' file
for the rest of its source tree.
It is convenient to write the ChangeLog entry or entries first, then
construct a commit message from it (or them).
3. The 'NEWS' file documents changes to groff that a user, not just a
developer, would notice, not including the resolution of defects.
As a hypothetical example, correcting a rendering error in tbl(1)
such that any table with more than 20 rows no longer had the text
"FOOBAR" spuriously added to some entries would not be a 'NEWS'
item, because the appearance of such text in the first place is a
surprising deviation from tbl's ideal and historical behavior. In
contrast, adding a command-line option to tbl, or changing the
meaning of its "expand" region option such that it no longer
horizontally compresses tables as well, _would_ be 'NEWS'-worthy.
Incorporating changes by others
-------------------------------
When committing a change largely authored by someone else, and that
person has not elected to remain anonymous, we want to credit their work
appropriately.
1. Report their name and email address in the ChangeLog entry alongside
the date they submitted the change.
2. Use the `--author` and `--date` command-line options to `git commit`
to record the same information.
3. If the contributor also proposed a ChangeLog entry or commit
message, editorially revise it if necessary to fit our conventions.
If you feel that substanial additional commentary is warranted, add
it between square brackets and mark it with your initials. For
example, "[I added a parallel change to foobar(). -- JRH]".
4. In a separate (and likely immediately subsequent) commit,
acknowledge the contributor in the "ANNOUNCE" file if they're not
already listed there.
Updating copyright notices
--------------------------
Background
..........
* A lay person's views and opinion follow; they are not legal advice.
If you require legal advice, consult a licensed attorney competent in
copyright law in your jurisdiction. The following discussion attempts
to establish a coherent basis from which to make consistent decisions
about the inclusion and maintenance of copyright notices in groff.
* Copyright notices in groff generally look as follows...
Copyright YYYY-ZZZZ Umbrella Organization, Inc.
QQQQ J. Random Hacker
WWWW-XXXX S. O. Gui
...where the repeated sequences of a capital letter are replaced by
(an) applicable Gregorian calendar year(s).
An exception is made for copyright notices applicable to "foreign"
code and files incorporated from other projects, which generally
retain the forms extant at their time of incorporation. Where these
files are supplemented with contributions by groff developers and meet
the originality and significance criteria discussed below, we add
copyright notices in the form shown above.
In files not encoded in UTF-8, we avoid use of the copyright sign
(Unicode U+00A9). See below regarding "ersatz" copyright symbols.
* The purpose of a copyright notice is to record legal facts about a
work. It is not to express acknowledgement of, gratitude about, or
appreciation for the efforts of contributors, past or present, which
is better done in documentation--and with explicit expression!
* Copyright protection is a legal monopoly of limited duration and an
economic policy scheme for the purpose of promoting, as the U.S.
Constitution puts it, "science and the useful arts". Over decades,
the scope of copyright (the nature of the works to which it can be
applied), the ease of its attachment, and the measure of its limited
duration, have all increased dramatically. (An economist might
observe that this is a progression characteristic of rentierism.)
* In U.S. statutory law, copyright protection extends to portions of a
work that constitute "original expression" (see below) and that are
"fixed in a tangible medium" (such as paper or a non-volatile memory
device) at some point in time. The copyright notice records the year
corresponding to that point in time. A notice should declare a list
of one or more such years reflecting the initial "fixation" and
further alterations to the work constituting original expression in
later years. An exception can be made for portions of the work whose
copyright durations have elapsed. But these durations are so lengthy
that, in the United States as of 2025, no work of computer software or
documentation has ever yet even _partially_ aged into the public
domain. (Some has been placed into the public domain deliberately,
and some never enjoyed copyright protection at all.)
Historically--decades ago, and before digital computing was commonly
undertaken in the home or even in small- to medium-scale business--a
copyright notice also asserted a legal claim. (It remains useful to
establish a basis for recovery of damages in U.S. civil copyright
infringement cases.) But copyright notices have not constituted
"assertions" of copyright for factual or criminal infringement
purposes (in the United States) for around 50 years as of 2026.
Removing a party's name from a copyright notice (as might happen
consequent to code deletion or wholesale rewriting of documentation)
is not a challenge or insult to an affected person or organization,
and does not deprive them of legitimate legal rights, when and where
doing so _makes the copyright notice more accurate_.
Software developers relying upon copyright protection are responsible
for maintaining accurate copyright notices. In the U.S., making a
claim of copyright fraudulently can be a criminal offense (17 USC
§506(c)). Making an overbroad claim of copyright, by naming parties
who don't legitimately have copyright in a work or by deliberately
overstating the recency of their efforts is, in the lay opinion of the
maintainer as of this writing, neglectful of responsibility.
* For a deeper treatment of the subject from a domain expert, please see
Jessica D. Litman's monograph, _Digital Copyright_, freely available
on the Web at <https://repository.law.umich.edu/books/1/>.
What To Do
..........
* Update the overall copyright notice for groff as a work of software
at release time. See the 'FOR-RELEASE' file in the Git repository.
* Update a _file_'s copyright notice in a year when committing a change
to it that is "original expression" and would thus merit copyright
protection. This is a subjective and arguable matter, so it's not
necessarily offensive to apply an expansive interpretation, but
"bumping" the copyright notice when _no_ change has been made, or when
the alterations are trivial by another standard (code style changes
that don't require regression testing; editorial changes to text that
are _invisible_ to the lay reader without technological assistance--
like trailing tab/space removal) abuses the principle, as noted above.
The GNU Maintainers' Guide's threshold for a "legally significant"
change is 15 lines.
"A change of just a few lines (less than 15 or so) is not legally
significant for copyright."
https://www.gnu.org/prep/maintain/html_node/Legally-Significant.html
Conversely, >= 15 lines would be. This guidance is vague, as it makes
no claim of an expected, typical, or mean line length, and different
file formats and stylistic practices in code and documentation
production exhibit different typical line lengths. Bearing in mind
that the 15 lines must constitute "original expression", and lacking
further guidance from that manual, in groff we ignore the issue of
line length and interpret "15 lines" as requiring a _net increase_ in
a file's line count of at least that magnitude, as calculated by
taking the output of "git diff --stat" on the file (or "git log
--stat" on a relevant commit to it) and subtracting lines removed from
lines added, a procedure that can result in a nonpositive number.
This rule has the advantage that it tends to exclude voluminous but
robotic changes, as one might make with "sed -i", which seldom
constitute "original expression".
Where a change produces a net increase of 15 lines or more but _still_
seems robotic or unoriginal, consider (1) applying the annotation
"Copyright-paperwork-exempt: yes" to the Git commit log message, and
(2) recording, in the corresponding commit log message, the robotic
procedure that produced the change.
If a change contains what would otherwise be legally significant
original expression that gets "swamped" by removal of other material--
falsely appearing to fall below the significance threshold using the
simple computation above--consider splitting the commit into two: one
that removes material and another that adds the new material.
Regarding "original expression", see section 308 of
<https://www.copyright.gov/comp3/chap300/
ch300-copyrightable-authorship.pdf>.
* If you forget the foregoing step, or contributions to a file seem to
accrete original status and legal significance over time or a series
of commits, it's fine to later update the notice to include the
relevant (hopefully current) year in a stand-alone commit. Use "git
log --oneline" on a file to gather commit IDs and change summaries
that justify the update and put them in the commit message so that
other people understand the basis of your claim.
* Similarly, it is also virtuous to correct existing copyright notices
that apply overbroad principles of update as described above. Doing
so demands careful study of a file's history, and one must be mindful
of file renames and relocations of content, neither of which have any
impact on copyright. When revising a copyright notice thus, document
your research procedure (for example, by recording in the commit log
the exact Git commands you used) so that anyone can reproduce it.
* It's okay to simply report a range of years in the copyright notice
instead of a comma-separated list. As far as the current maintainer
knows, there is no hard rule that such ranges are interpreted
exhaustively, and unless someone has a chronological record of changes
to the file--which is present in groff's Git commit repository going
back to about 2014, but absent from distribution archives--a broken
sequence of copyright coverage years makes little difference.
Prior to 2014, groff's Git history is coarser, being reconstructed
from CVS, and prior to February 2000, each commit is a snapshot of a
distribution archive.
https://lists.gnu.org/archive/html/groff/2013-12/msg00033.html
https://lists.gnu.org/archive/html/groff/2013-12/msg00005.html
* When adding a new file to groff, include a copyright notice only if it
is "legally significant" per the 15-line threshold. But even a new
file of legally significant size does not merit a copyright notice if
it does not constitute original, non-robotic expression as discussed
above. In that case, include "Copyright-paperwork-exempt: yes" in the
Git commit log message. To summarize, the same rules apply to new
files as to changes to existing ones.
* In UTF-8-encoded files, it is fine to use a true copyright sign
(Unicode U+00A9). Place it in the notice between the word "Copyright"
and the year (or year range) with one space on each side of it.
In other files, avoid use of the ersatz copyright sign "(C)".
Software developers have long labored under the no-longer-correct
misconception that omitting a copyright symbol from one's notice was a
fatal defect that effectively placed the work in the public domain.
That stopped being true as of 1 March 1989. Further, prior to
guidance issued by the U.S. Copyright Office in the decades since, the
use of "(C)" as a substitute for a copyright sign _may not have
sufficed_ to prevent the copyright notice from being regarded as
defective. The Copyright Office, then and now, prefers the
abbreviation "copr." when a true copyright sign is typographically
unavailable. Nowadays, its advice is that "c" (note lowercase) is an
"acceptable variant", that _may_ retain the efficacy of the copyright
notice. The word "copyright", spelled out in full, also suffices per
that resource.
See <https://www.copyright.gov/circs/circ03.pdf>.
Adding or removing components
-----------------------------
Changing the set of discrete modules that comprises groff requires
updates in multiple places.
* Update "Makefile.am" to add or remove the inclusion of the
component's "*.am" Automake file.
* Update the "MANIFEST" file.
* Update the "NEWS" file.
Adding a component in the "contrib" directory demands further change.
* Add a "COPYRIGHT" file in its directory. If that file makes reference
to a separate license text that is _not_ the GPLv3 under which all
files in groff are distributed (sometimes in conjuction with other
licenses), such as GPLv2, also include a copy of that license in the
same directory.
* Add the aforementioned "COPYRIGHT" file and any separate license
text files it mentions to the `EXTRA_DIST` macro in the component's
"*.am" file.
Writing tests
-------------
Here is some advice on writing portable automated test scripts.
* Write to the POSIX standard for the shell and utilities where
possible. Issue 4 from 1994 is old enough that no contemporary system
has a good reason for not conforming. A copy of the standard is
available at the Open Group's web site.
https://pubs.opengroup.org/onlinepubs/009656399/toc.pdf
* The GNU coreutils "seq" command is handy but not standardized by
POSIX. Replace it with a while loop.
# emulate "seq 53"
n=1; while [ $n -le 53 ]; do echo $n; n=$(( n + 1 )); done; unset n
* The "wc" command on macOS can prefix the numeric count in its output
with spaces, which can be undesirable when storing that output to
variable that is later expanded within double quotes in the shell.
Here is a workaround.
res=$(whatever | wc -l)
res=$(( res + 0 )) || exit 99
If for some reason we get unacceptable non-integer garbage from "wc",
we exit the test script with the code reserved for "hard errors".
Shell arithmetic is unfortunately one of the many POSIX shell features
that Solaris 10's /bin/sh does not implement; see the "PROBLEMS" file.
* The "od" command on macOS can put extra space characters (i.e., spaces
that don't correspond to the input) at the ends of lines when using
the "-t c" format; GNU od does not.
So a regex like this that works with GNU od:
grep -Eqx '0000000 +A +\\b +B +\\b +C D +\\n'
might need to be weakened to the following to work on macOS.
grep -Eqx '0000000 +A +\\b +B +\\b +C D +\\n *'
* The "od" command on macOS, NetBSD, and OpenBSD puts extra space
characters between the hexadecimal values when using the "-t x1"
format; GNU od does not.
So a regex like this that works with GNU od:
grep -q '81 30 55 81 30 56 81 6c e2'
might need to be weakened to the following to work on macOS/[NO]*BSD.
grep -q '81 *30 *55 *81 *30 *56 *81 *6c *e2'
* The "od" command on FreeBSD 14.0 and 15.0, NetBSD 10.0, and OpenBSD
7.8 (at least) pad out the line length with spaces to 73 columns; GNU
od does not.
So a regex like this that works with GNU od:
grep -q '0000040 .* *e2 *94 *a4 *0.$'
likely must be weakened to the following.
grep -q '0000040 .* *e2 *94 *a4 *0. *$'
* The "od" command on macOS does not respect the environment variable
assignment "LC_ALL=C" when processing byte values 127<x<256 decimal
and using the "character" output format (option "-t c"). An
alternative output must be used, like bytewise octal (option "-t o1").
(macOS od may be non-conforming here, despite the claim of its man
page. POSIX Issue 4 od's description says "The type specifier
character c specifies that bytes will be interpreted as characters
specified by the current setting of the LC_CTYPE locale category. ...
Other non-printable characters will be written as one three-digit
octal number for each byte in the character." (p. 538) The language
in Issue 7 (2018) appears unchanged.
https://pubs.opengroup.org/onlinepubs/9699919799/utilities/od.html )
* Prior to POSIX.1-2024, the meaning of the sequence `\]` in a basic or
extended regular expression is undefined. Spell it as `]` instead.
* macOS sed requires semicolons after commands even if they are followed
immediately by a closing brace.
Rewrite
sed -n '/Foo\./{n;s/^$/FAILURE/;p}'
as follows.
sed -n '/Foo\./{n;s/^$/FAILURE/;p;}'
But see below regarding the opening braces.
* POSIX doesn't say that sed has to accept semicolons as command
separators after label (':') and test ('t') commands, or after brace
commands, so macOS sed doesn't. GNU sed does.
So rewrite tidy, compact sed scripts like this:
sed -n '/Foo\./{n;s/^$/FAILURE/;tA;s/.*/SUCCESS/;:A;p}'
as this more cumbersome alternative.
sed -n \
-e '/Foo\./{n;s/^$/FAILURE/;tA;' \
-e 's/.*/SUCCESS/;:A;' \
-e 'p;}')
But see below regarding the opening braces.
Similarly, a brace sequence as shown in this partial sed script:
/f1/p}}}}}}
must be rewritten as follows (or with '-e' expressions).
/f1/p;}
}
}
}
}
}
* macOS and GNU sed don't require newlines (or '-e' expression endings)
after _opening_ braces, but Solaris 11 sed does.
So the sed script
/i/{N;/Table of Contents/{N;/Foo[. ][. ]*1/p;};}
must be rewritten as follows (or with '-e' expressions).
/i/{
N;/Table of Contents/{
N;/Foo[. ][. ]*1/p;
};
}
* Solaris 10's /usr/bin/cksum output is non-conforming with XPG4. It
uses tabs as field delimiters instead of spaces.
* Solaris 10's /usr/bin/grep is non-conforming with XPG4; it lacks
support for the `-E`, `-F`, `-q`, and `-x` options.
* Solaris 10's /bin/sh is non-conforming with XPG4; it does not support
POSIX parameter expansion syntax.
* Solaris 10's /usr/bin/tr exits with an error if you try to use a POSIX
character class (such as "[:cntrl:]") in any locale but "C".
* Solaris 10's /usr/xpg4/bin/sh is non-conforming with XPG4.
(Good job, guys!)
Its "unset" builtin is buggy. (The /usr/bin/sh in Solaris 11 does not
have this problem.)
We sometimes must use the "unset" shell builtin command to prevent
environment variables from confounding test results.
POSIX says "[u]nsetting a variable ... that was not previously set is
not considered an error and will not cause the shell to abort."
Nevertheless this builtin returns an error exit status in this
circumstance.
$ /usr/xpg4/bin/sh -c 'unset _NON_EXISTENT_XYZ; echo $?'
1
You may want to check for this misbehavior and skip the test if
running under an afflicted shell.
if ! unset VARIABLE_OF_INTEREST
then
echo "unable to clear environment; skipping" >&2
exit 77 # skip
fi
Updating gnulib
---------------
Here's how to update the submodule, using that project's "stable-202501"
branch as an example. Run the commands below from the root directory
of your working copy.
$ cd gnulib
$ git pull
$ git checkout -b stable-202501 --track origin/stable-202501
$ cd ..
$ git add gnulib
$ editor ChangeLog # log it
$ git add ChangeLog
$ git commit
It's likely a good idea to update the "bootstrap" script at the same
time (not necessarily in the same commit, however).
$ ./bootstrap --bootstrap-sync
$ git add bootstrap
$ editor ChangeLog # log it
$ git add ChangeLog
$ git commit
Theory of operation
-------------------
groff language parser
.....................
The "troff" program in "src/roff/troff" parses the groff input language.
There, "input.cpp" implements the main loop and tokenizes input. Input
tokens are transformed into nodes (a GNU troff internal data structure)
by "env.cpp" and "node.cpp". Routines in the latter file generate the
page description language from lists of nodes.
page description language parser
................................
The parser for the page description language produced by troff is
implemented in "src/libs/libdriver/input.cpp". This is used by all
groff output drivers written in C++. ("gropdf", written in Perl,
performs its own parsing.)
##### Editor settings
Local Variables:
fill-column: 72
mode: text
End:
vim: set autoindent textwidth=72:

4650
Agent-Windows/OGP64/usr/share/doc/groff/NEWS Normal file
View file

File diff suppressed because it is too large Load diff

132
Agent-Windows/OGP64/usr/share/doc/groff/README Normal file
View file

@ -0,0 +1,132 @@
Copyright 1989-2020 Free Software Foundation, Inc.
2022-2025 G. Branden Robinson
Copying and distribution of this file, with or without
modification, are permitted in any medium without royalty provided
the copyright notice and this notice are preserved.
This is the "groff" document formatting system, a reimplementation and
extension of the AT&T "troff" typesetting system for Unix operating
systems. The version number is given in the file ".tarball-version" if
you are building from a distribution archive; otherwise, building from
its Git repository stores it in the file ".version".
The groff system includes original implementations (not derived from
AT&T code) of the "troff", "nroff", "pic", "eqn", "tbl", "refer", and
"soelim" programs; the "man" and "ms" macro packages; and output drivers
for PostScript, PDF, and TeX DVI file formats, HP LaserJet 4- and Canon
CaPSL-compatible printers, HTML and XHTML (in beta status), and
typewriter/terminal devices.
It also provides modified versions of BSD Unix additions to AT&T troff:
the "grn" preprocessor, and the "mdoc" and "me" macro packages.
"gxditview", an enhanced version of the X11 "xditview" previewer for
"troff" device-independent output, originates in X11R5.
Contributed components feature Joergen Haegg's reimplementation and
extension of the DWB troff "mm" macro package, Peter Schaffter's "mom"
macro package, and Bernd Warken's reimplementation of the "chem"
preprocessor in Perl.
See the file "INSTALL.extra" for instructions on how to install from a
distribution archive, such as a release or release candidate.
The file "INSTALL.REPO" contains supplementary instructions for building
directly from a clone of the Git repository.
The file "NEWS" contains a history of user-visible changes to groff.
groff is free software. See the file "COPYING" for overall copying
permissions, and "LICENSES" for further detail.
The file "PROBLEMS" describes various issues that users have encountered
in compiling, installing, and running groff.
The file "MORE.STUFF" describes some third-party programming and
documentary resources useful with groff.
Current and historical releases of groff are available via HTTPS and
anonymous FTP from the host "ftp.gnu.org" in the directory "gnu/groff".
groff has a home page at the GNU Project.
https://www.gnu.org/software/groff/
Administration of the project is done through GNU Savannah.
https://savannah.gnu.org/git/?group=groff
groff is developed at its Git repository, which has a web interface.
https://git.savannah.gnu.org/cgit/groff.git
You can view any commit in isolation, and browse the entire source tree
corresponding to its state as of that commit. Click the summary line of
the commit message to expose these options.
The files "INSTALL.extra" and "INSTALL.REPO" files noted above discuss
build requirements. groff also has runtime dependencies.
Creation of PDF and (X)HTML output requires Ghostscript. Production of
(X)HTML furthermore demands tools from the Netpbm package.
Production of PDF output using the "gropdf" output driver requires Perl.
(You can alternatively produce PostScript with "grops" and convert that
to PDF using Ghostscript.) The "chem", "gperl", and "gpinyin"
preprocessors, and several utilities, such as "grog", are also written
in Perl.
If groff is configured with "lp" or "lpr" support, the corresponding
program must remain available on the system for the groff command's
"-l" option to work. Similarly, build-time detection of development
headers for the "uchardet", "Xaw", and "Xmu" libraries (and their
dependencies) assumes that their runtime counterparts remain installed
to support the groff that is built.
You can view or add to groff's bug database via its issue tracker on the
Savannah site (also linked from the groff home page).
http://savannah.gnu.org/bugs/?group=groff
To report a problem, you may use the form in the file "BUG-REPORT"; its
purpose is to make sure that groff's developers have the information
they need to fix the bug. At least read the "BUG-REPORT" file and
supply all the information that it asks for. Even if you are not sure
that something is a bug, please report it so we can determine whether it
is a software defect, or an omission from our documentation.
If you'd like to modify groff or participate in its development, files
"HACKING" and "MANIFEST" can familiarize you with the structure of the
code and the project's conventions for maintaining it.
Four mailing lists are available.
bug-groff@gnu.org a read-only list for following bug reports
groff@gnu.org for general discussion of groff
groff-commit@gnu.org a read-only list for following commits
to the Git repository
info-groff@gnu.org a moderated list for groff-related
announcements
To subscribe, send a mail to <list>-request@<domain> (example:
groff-request@gnu.org for the groff list) with the word "subscribe"
in either the subject or body of the email (don't include the quotes).
Alternatively, subscribe via our web pages by completing an HTML form.
https://lists.gnu.org/mailman/listinfo/bug-groff
https://lists.gnu.org/mailman/listinfo/groff
https://lists.gnu.org/mailman/listinfo/groff-commit
https://lists.gnu.org/mailman/listinfo/info-groff
Each of these web pages also provides a link to a browseable archive of
postings to the corresponding mailing list.
groff was originally written by James Clark <jjc@jclark.com>.
##### Editor settings
Local Variables:
fill-column: 72
mode: text
End:
vim: set textwidth=72:

41
Agent-Windows/OGP64/usr/share/doc/groff/TODO Normal file
View file

@ -0,0 +1,41 @@
# Copyright (C) 2000-2020 Free Software Foundation, Inc.
#
# This file is part of groff, the GNU roff typesetting system.
#
# groff is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 2 of the License, or
# (at your option) any later version.
#
# groff is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program. If not, see
# <http://www.gnu.org/licenses/gpl-2.0.html>.
Unicode input:
Making groff 21bit input-clean.
Make -Tlj4 work with -X.
Guess man5ext and man7ext variables.
Provide man.sun implementing .TX.
Improve GROFF_PRINT macro in aclocal.m4.
Provide a `bindist' target.
Implement tmac.bib in terms of tmac.s.
Support long options using GNU getopt.
Catch the following error in -me:
.(z
.(l C
.)z
Arrows for next/previous page from R5 xditview.