GSP/GSP-Agent-Windows
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Initial Windows agent repository

Browse source
This commit is contained in:
Frank Harris 2026-06-08 10:45:20 -05:00
commit a0db0c2e5b
10589 changed files with 3844063 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

57
OGP64/usr/share/doc/gettext/AUTHORS Normal file
View file

@ -0,0 +1,57 @@
Authors of GNU gettext.
The following contributions warranted legal paper exchanges with the
Free Software Foundation. Also see files ChangeLog and THANKS.
GETTEXT Ulrich Drepper
Assigns program and future changes.
GETTEXT Peter Miller
Assigns past and future changes.
GETTEXT François Pinard
Assigns past and future changes.
GETTEXT Ben Kasmin Bullock
Disclaims changes to manual.
GETTEXT Bruno Haible
Assigns past and future changes.
GETTEXT Tim Van Holder
Assigns past and future changes.
GETTEXT Tommy Johansson
Assigns changes. (changed: xgettext.c, configure.in; added: x-java.[lh])
GETTEXT Karl Eichwalder
Assigns past and future changes.
GETTEXT SuSE Linux AG 2002-07-03
Disclaimer for Karl Eichwalder, in the past and for the next 5 years.
GETTEXT Alexandre Duret-Lutz
Assigns past and future changes.
GETTEXT Guido Flohr
Assigns past and future changes.
GETTEXT Michele Cicciotti alias KJK::Hyperion
Assigns past and future changes.
GETTEXT Noritada Kobayashi
Assigns past and future changes.
GETTEXT KO Myung-Hun
Assigns Past and Future Changes
GETTEXT Lubomir Remak
Assigns Past and Future Changes
GETTEXT Daiki Ueno
Assigns Past and Future Changes
GETTEXT Miguel Angel Arruga Vivas
Assigns past and future Changes
GETTEXT FutreLAB, AG
Assigns past and future changes

674
OGP64/usr/share/doc/gettext/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/philosophy/why-not-lgpl.html>.

516
OGP64/usr/share/doc/gettext/COPYING.LIB Normal file
View file

@ -0,0 +1,516 @@
GNU LESSER GENERAL PUBLIC LICENSE
Version 2.1, February 1999
Copyright (C) 1991, 1999 Free Software Foundation, Inc.
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
[This is the first released version of the Lesser GPL. It also counts
as the successor of the GNU Library Public License, version 2, hence
the version number 2.1.]
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
Licenses are intended to guarantee your freedom to share and change
free software--to make sure the software is free for all its users.
This license, the Lesser General Public License, applies to some
specially designated software packages--typically libraries--of the
Free Software Foundation and other authors who decide to use it. You
can use it too, but we suggest you first think carefully about whether
this license or the ordinary General Public License is the better
strategy to use in any particular case, based on the explanations
below.
When we speak of free software, we are referring to freedom of use,
not price. Our General Public Licenses are designed to make sure that
you have the freedom to distribute copies of free software (and charge
for this service if you wish); that you receive source code or can get
it if you want it; that you can change the software and use pieces of
it in new free programs; and that you are informed that you can do
these things.
To protect your rights, we need to make restrictions that forbid
distributors to deny you these rights or to ask you to surrender these
rights. These restrictions translate to certain responsibilities for
you if you distribute copies of the library or if you modify it.
For example, if you distribute copies of the library, whether gratis
or for a fee, you must give the recipients all the rights that we gave
you. You must make sure that they, too, receive or can get the source
code. If you link other code with the library, you must provide
complete object files to the recipients, so that they can relink them
with the library after making changes to the library and recompiling
it. And you must show them these terms so they know their rights.
We protect your rights with a two-step method: (1) we copyright the
library, and (2) we offer you this license, which gives you legal
permission to copy, distribute and/or modify the library.
To protect each distributor, we want to make it very clear that
there is no warranty for the free library. Also, if the library is
modified by someone else and passed on, the recipients should know
that what they have is not the original version, so that the original
author's reputation will not be affected by problems that might be
introduced by others.
^L
Finally, software patents pose a constant threat to the existence of
any free program. We wish to make sure that a company cannot
effectively restrict the users of a free program by obtaining a
restrictive license from a patent holder. Therefore, we insist that
any patent license obtained for a version of the library must be
consistent with the full freedom of use specified in this license.
Most GNU software, including some libraries, is covered by the
ordinary GNU General Public License. This license, the GNU Lesser
General Public License, applies to certain designated libraries, and
is quite different from the ordinary General Public License. We use
this license for certain libraries in order to permit linking those
libraries into non-free programs.
When a program is linked with a library, whether statically or using
a shared library, the combination of the two is legally speaking a
combined work, a derivative of the original library. The ordinary
General Public License therefore permits such linking only if the
entire combination fits its criteria of freedom. The Lesser General
Public License permits more lax criteria for linking other code with
the library.
We call this license the "Lesser" General Public License because it
does Less to protect the user's freedom than the ordinary General
Public License. It also provides other free software developers Less
of an advantage over competing non-free programs. These disadvantages
are the reason we use the ordinary General Public License for many
libraries. However, the Lesser license provides advantages in certain
special circumstances.
For example, on rare occasions, there may be a special need to
encourage the widest possible use of a certain library, so that it
becomes
a de-facto standard. To achieve this, non-free programs must be
allowed to use the library. A more frequent case is that a free
library does the same job as widely used non-free libraries. In this
case, there is little to gain by limiting the free library to free
software only, so we use the Lesser General Public License.
In other cases, permission to use a particular library in non-free
programs enables a greater number of people to use a large body of
free software. For example, permission to use the GNU C Library in
non-free programs enables many more people to use the whole GNU
operating system, as well as its variant, the GNU/Linux operating
system.
Although the Lesser General Public License is Less protective of the
users' freedom, it does ensure that the user of a program that is
linked with the Library has the freedom and the wherewithal to run
that program using a modified version of the Library.
The precise terms and conditions for copying, distribution and
modification follow. Pay close attention to the difference between a
"work based on the library" and a "work that uses the library". The
former contains code derived from the library, whereas the latter must
be combined with the library in order to run.
^L
GNU LESSER GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License Agreement applies to any software library or other
program which contains a notice placed by the copyright holder or
other authorized party saying it may be distributed under the terms of
this Lesser General Public License (also called "this License").
Each licensee is addressed as "you".
A "library" means a collection of software functions and/or data
prepared so as to be conveniently linked with application programs
(which use some of those functions and data) to form executables.
The "Library", below, refers to any such software library or work
which has been distributed under these terms. A "work based on the
Library" means either the Library or any derivative work under
copyright law: that is to say, a work containing the Library or a
portion of it, either verbatim or with modifications and/or translated
straightforwardly into another language. (Hereinafter, translation is
included without limitation in the term "modification".)
"Source code" for a work means the preferred form of the work for
making modifications to it. For a library, complete source code means
all the source code for all modules it contains, plus any associated
interface definition files, plus the scripts used to control
compilation
and installation of the library.
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running a program using the Library is not restricted, and output from
such a program is covered only if its contents constitute a work based
on the Library (independent of the use of the Library in a tool for
writing it). Whether that is true depends on what the Library does
and what the program that uses the Library does.
1. You may copy and distribute verbatim copies of the Library's
complete source code as you receive it, in any medium, provided that
you conspicuously and appropriately publish on each copy an
appropriate copyright notice and disclaimer of warranty; keep intact
all the notices that refer to this License and to the absence of any
warranty; and distribute a copy of this License along with the
Library.
You may charge a fee for the physical act of transferring a copy,
and you may at your option offer warranty protection in exchange for a
fee.
2. You may modify your copy or copies of the Library or any portion
of it, thus forming a work based on the Library, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) The modified work must itself be a software library.
b) You must cause the files modified to carry prominent notices
stating that you changed the files and the date of any change.
c) You must cause the whole of the work to be licensed at no
charge to all third parties under the terms of this License.
d) If a facility in the modified Library refers to a function or a
table of data to be supplied by an application program that uses
the facility, other than as an argument passed when the facility
is invoked, then you must make a good faith effort to ensure that,
in the event an application does not supply such function or
table, the facility still operates, and performs whatever part of
its purpose remains meaningful.
(For example, a function in a library to compute square roots has
a purpose that is entirely well-defined independent of the
application. Therefore, Subsection 2d requires that any
application-supplied function or table used by this function must
be optional: if the application does not supply it, the square
root function must still compute square roots.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Library,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Library, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote
it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Library.
In addition, mere aggregation of another work not based on the Library
with the Library (or with a work based on the Library) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may opt to apply the terms of the ordinary GNU General Public
License instead of this License to a given copy of the Library. To do
this, you must alter all the notices that refer to this License, so
that they refer to the ordinary GNU General Public License, version 2,
instead of to this License. (If a newer version than version 2 of the
ordinary GNU General Public License has appeared, then you can specify
that version instead if you wish.) Do not make any other change in
these notices.
^L
Once this change is made in a given copy, it is irreversible for
that copy, so the ordinary GNU General Public License applies to all
subsequent copies and derivative works made from that copy.
This option is useful when you wish to copy part of the code of
the Library into a program that is not a library.
4. You may copy and distribute the Library (or a portion or
derivative of it, under Section 2) in object code or executable form
under the terms of Sections 1 and 2 above provided that you accompany
it with the complete corresponding machine-readable source code, which
must be distributed under the terms of Sections 1 and 2 above on a
medium customarily used for software interchange.
If distribution of object code is made by offering access to copy
from a designated place, then offering equivalent access to copy the
source code from the same place satisfies the requirement to
distribute the source code, even though third parties are not
compelled to copy the source along with the object code.
5. A program that contains no derivative of any portion of the
Library, but is designed to work with the Library by being compiled or
linked with it, is called a "work that uses the Library". Such a
work, in isolation, is not a derivative work of the Library, and
therefore falls outside the scope of this License.
However, linking a "work that uses the Library" with the Library
creates an executable that is a derivative of the Library (because it
contains portions of the Library), rather than a "work that uses the
library". The executable is therefore covered by this License.
Section 6 states terms for distribution of such executables.
When a "work that uses the Library" uses material from a header file
that is part of the Library, the object code for the work may be a
derivative work of the Library even though the source code is not.
Whether this is true is especially significant if the work can be
linked without the Library, or if the work is itself a library. The
threshold for this to be true is not precisely defined by law.
If such an object file uses only numerical parameters, data
structure layouts and accessors, and small macros and small inline
functions (ten lines or less in length), then the use of the object
file is unrestricted, regardless of whether it is legally a derivative
work. (Executables containing this object code plus portions of the
Library will still fall under Section 6.)
Otherwise, if the work is a derivative of the Library, you may
distribute the object code for the work under the terms of Section 6.
Any executables containing that work also fall under Section 6,
whether or not they are linked directly with the Library itself.
^L
6. As an exception to the Sections above, you may also combine or
link a "work that uses the Library" with the Library to produce a
work containing portions of the Library, and distribute that work
under terms of your choice, provided that the terms permit
modification of the work for the customer's own use and reverse
engineering for debugging such modifications.
You must give prominent notice with each copy of the work that the
Library is used in it and that the Library and its use are covered by
this License. You must supply a copy of this License. If the work
during execution displays copyright notices, you must include the
copyright notice for the Library among them, as well as a reference
directing the user to the copy of this License. Also, you must do one
of these things:
a) Accompany the work with the complete corresponding
machine-readable source code for the Library including whatever
changes were used in the work (which must be distributed under
Sections 1 and 2 above); and, if the work is an executable linked
with the Library, with the complete machine-readable "work that
uses the Library", as object code and/or source code, so that the
user can modify the Library and then relink to produce a modified
executable containing the modified Library. (It is understood
that the user who changes the contents of definitions files in the
Library will not necessarily be able to recompile the application
to use the modified definitions.)
b) Use a suitable shared library mechanism for linking with the
Library. A suitable mechanism is one that (1) uses at run time a
copy of the library already present on the user's computer system,
rather than copying library functions into the executable, and (2)
will operate properly with a modified version of the library, if
the user installs one, as long as the modified version is
interface-compatible with the version that the work was made with.
c) Accompany the work with a written offer, valid for at
least three years, to give the same user the materials
specified in Subsection 6a, above, for a charge no more
than the cost of performing this distribution.
d) If distribution of the work is made by offering access to copy
from a designated place, offer equivalent access to copy the above
specified materials from the same place.
e) Verify that the user has already received a copy of these
materials or that you have already sent this user a copy.
For an executable, the required form of the "work that uses the
Library" must include any data and utility programs needed for
reproducing the executable from it. However, as a special exception,
the materials to be distributed need not include anything that is
normally distributed (in either source or binary form) with the major
components (compiler, kernel, and so on) of the operating system on
which the executable runs, unless that component itself accompanies
the executable.
It may happen that this requirement contradicts the license
restrictions of other proprietary libraries that do not normally
accompany the operating system. Such a contradiction means you cannot
use both them and the Library together in an executable that you
distribute.
^L
7. You may place library facilities that are a work based on the
Library side-by-side in a single library together with other library
facilities not covered by this License, and distribute such a combined
library, provided that the separate distribution of the work based on
the Library and of the other library facilities is otherwise
permitted, and provided that you do these two things:
a) Accompany the combined library with a copy of the same work
based on the Library, uncombined with any other library
facilities. This must be distributed under the terms of the
Sections above.
b) Give prominent notice with the combined library of the fact
that part of it is a work based on the Library, and explaining
where to find the accompanying uncombined form of the same work.
8. You may not copy, modify, sublicense, link with, or distribute
the Library except as expressly provided under this License. Any
attempt otherwise to copy, modify, sublicense, link with, or
distribute the Library is void, and will automatically terminate your
rights under this License. However, parties who have received copies,
or rights, from you under this License will not have their licenses
terminated so long as such parties remain in full compliance.
9. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Library or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Library (or any work based on the
Library), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Library or works based on it.
10. Each time you redistribute the Library (or any work based on the
Library), the recipient automatically receives a license from the
original licensor to copy, distribute, link with or modify the Library
subject to these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties with
this License.
^L
11. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Library at all. For example, if a patent
license would not permit royalty-free redistribution of the Library by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Library.
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply, and the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
12. If the distribution and/or use of the Library is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Library under this License
may add an explicit geographical distribution limitation excluding those
countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.
13. The Free Software Foundation may publish revised and/or new
versions of the Lesser 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 Library
specifies a version number of this License which applies to it and
"any later version", you have the option of following the terms and
conditions either of that version or of any later version published by
the Free Software Foundation. If the Library does not specify a
license version number, you may choose any version ever published by
the Free Software Foundation.
^L
14. If you wish to incorporate parts of the Library into other free
programs whose distribution conditions are incompatible with these,
write to the author to ask for permission. For software which is
copyrighted by the Free Software Foundation, write to the Free
Software Foundation; we sometimes make exceptions for this. Our
decision will be guided by the two goals of preserving the free status
of all derivatives of our free software and of promoting the sharing
and reuse of software generally.
NO WARRANTY
15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
OTHER PARTIES PROVIDE THE LIBRARY "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
LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
AND/OR REDISTRIBUTE THE LIBRARY 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
LIBRARY (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 LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
END OF TERMS AND CONDITIONS
^L
How to Apply These Terms to Your New Libraries
If you develop a new library, and you want it to be of the greatest
possible use to the public, we recommend making it free software that
everyone can redistribute and change. You can do so by permitting
redistribution under these terms (or, alternatively, under the terms
of the ordinary General Public License).
To apply these terms, attach the following notices to the library.
It is safest to attach them to the start of each source file to most
effectively convey the exclusion of warranty; and each file should
have at least the "copyright" line and a pointer to where the full
notice is found.
<one line to give the library's name and a brief idea of what it
does.>
Copyright (C) <year> <name of author>
This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; either
version 2 of the License, or (at your option) any later version.
This library 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
Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public
License along with this library; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
MA 02110-1301, USA
Also add information on how to contact you by electronic and paper
mail.
You should also get your employer (if you work as a programmer) or
your
school, if any, to sign a "copyright disclaimer" for the library, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the
library `Frob' (a library for tweaking knobs) written by James
Random Hacker.
<signature of Ty Coon>, 1 April 1990
Ty Coon, President of Vice
That's all there is to it!

10918
OGP64/usr/share/doc/gettext/ChangeLog Normal file
View file

File diff suppressed because it is too large Load diff

259
OGP64/usr/share/doc/gettext/DEPENDENCIES Normal file
View file

@ -0,0 +1,259 @@
The following packages should be installed before GNU gettext is installed
(runtime dependencies that are also build dependencies):
* GNU libiconv
+ Not needed on systems with glibc, on macOS, and NetBSD.
But highly recommended on all other systems.
Needed for character set conversion of PO files from/to Unicode
and for the iconv_ostream class of libtextstyle.
+ Homepage:
https://www.gnu.org/software/libiconv/
+ Download:
https://ftp.gnu.org/gnu/libiconv/
+ Pre-built package name:
- On Debian and Debian-based systems: --,
- On Red Hat distributions: --.
- Other: https://repology.org/project/libiconv/versions
+ If it is installed in a nonstandard directory, pass the option
--with-libiconv-prefix=DIR to 'configure'.
* GNU ncurses (preferred)
or libtermcap (discouraged) or a curses library (legacy).
+ Highly recommended.
Needed for styling of terminal output (libtextstyle and the --color
option of the 'msgcat' program).
+ Homepage:
https://www.gnu.org/software/ncurses/
+ Download:
https://ftp.gnu.org/gnu/ncurses/
+ Pre-built package name:
- On Debian and Debian-based systems: libncurses-dev,
- On Red Hat distributions: ncurses-devel.
- Other: https://repology.org/project/ncurses/versions
+ If it is installed in a nonstandard directory, pass the option
--with-ncurses-prefix=DIR or --with-libtermcap-prefix to 'configure'.
* libxml2
+ Recommended.
Needed for 'xgettext' and 'msgfmt', so that it can parse XML
files. Also needed for the --color option of the various
programs.
If not present, a subset of libxml2 (included in this package) will be
compiled into libgettextlib.
+ Homepage:
http://xmlsoft.org/
+ Download:
ftp://xmlsoft.org/libxml2/
+ Pre-built package name:
- On Debian and Debian-based systems: libxml2-dev,
- On Red Hat distributions: libxml2-devel.
- Other: https://repology.org/project/libxml2/versions
+ If it is installed in a nonstandard directory, pass the option
--with-libxml2-prefix=DIR to 'configure'.
* libacl
+ Recommended.
Needed so that the creation of backup files respects the access control
lists (ACLs) set on the original files.
+ Homepage:
https://savannah.nongnu.org/projects/acl/
+ Download:
https://download.savannah.nongnu.org/releases/acl/
+ Pre-built package name:
- On Debian and Debian-based systems: acl, libacl1-dev,
- On Red Hat distributions: acl, libacl-devel.
- Other: https://repology.org/project/acl/versions
* A Java runtime and compiler (e.g. OpenJDK, AdoptOpenJDK, or kaffe).
+ Recommended.
Needed for building libintl.jar. Also needed for 'msgfmt' and
'msgunfmt', so that they can handle Java classes and properties files.
+ Homepage:
http://openjdk.java.net/
http://www.kaffe.org/
+ Download:
http://openjdk.java.net/install/index.html
https://github.com/kaffe/kaffe
+ Pre-built package name:
- On Debian and Debian-based systems:
openjdk-11-jdk or openjdk-8-jdk or openjdk-7-jdk,
- On Red Hat distributions:
java-11-openjdk or java-1.8.0-openjdk or java-1.7.0-openjdk.
- Other: https://repology.org/project/openjdk/versions
* A C# runtime and compiler (e.g. mono).
+ Recommended.
Needed for building GNU.Gettext.dll. Also needed for 'msgfmt' and
'msgunfmt', so that they can handle C# resources and assemblies.
+ Homepage:
http://www.mono-project.com/
+ Download:
http://www.mono-project.com/download/
+ Pre-built package name:
- On Debian and Debian-based systems: mono-runtime,
- On Red Hat distributions: mono.
- Other: https://repology.org/project/mono/versions
+ If more than one C# is installed, pass the option --enable-csharp=IMPL
to 'configure', to disambiguate.
* git 1.6 or newer
+ Recommended.
Needed by the 'autopoint' program, if not configured with --without-git
or --with-cvs.
+ Homepage:
https://git-scm.com/
+ Download:
https://www.kernel.org/pub/software/scm/git/
+ Pre-built package name:
- On Debian and Debian-based systems: git,
- On Red Hat distributions: git.
- Other: https://repology.org/project/git/versions
* The archiving utility 'tar'.
+ Recommended.
Needed for the 'autopoint' program.
Either the platform's native tar, or GNU tar.
+ Homepage:
https://www.gnu.org/software/tar/
+ Download:
https://ftp.gnu.org/gnu/tar/
+ Pre-built package name:
- On Debian and Debian-based systems: tar,
- On Red Hat distributions: tar.
- Other: https://repology.org/project/tar/versions
* The GNU compression utility 'gzip'.
+ Recommended.
Needed for the 'autopoint' program.
+ Homepage:
https://www.gnu.org/software/gzip/
+ Download:
https://ftp.gnu.org/gnu/gzip/
+ Pre-built package name:
- On Debian and Debian-based systems: gzip,
- On Red Hat distributions: gzip.
- Other: https://repology.org/project/gzip/versions
* The compression utility 'bzip2'.
+ Recommended.
Needed for the 'autopoint' program, if not configured with --without-bzip2.
+ Homepage:
http://www.bzip.org/
+ Download:
http://www.bzip.org/downloads.html
+ Pre-built package name:
- On Debian and Debian-based systems: bzip2,
- On Red Hat distributions: bzip2.
- Other: https://repology.org/project/bzip2/versions
* The compression utility 'xz'.
+ Recommended.
Needed for the 'autopoint' program, if not configured with --without-xz.
+ Homepage:
https://tukaani.org/xz/
+ Download:
https://tukaani.org/xz/
+ Pre-built package name:
- On Debian and Debian-based systems: xz-utils,
- On Red Hat distributions: xz.
- Other: https://repology.org/project/xz/versions
* GNU libunistring
+ Optional.
Needed for the line breaking in PO files and for xgettext.
If not present, a subset of libunistring (included in this package) will
be compiled into libgettextlib.
+ Homepage:
https://www.gnu.org/software/libunistring/
+ Download:
https://ftp.gnu.org/gnu/libunistring/
+ Pre-built package name:
- On Debian and Debian-based systems: libunistring-dev,
- On Red Hat distributions: libunistring-devel.
- Other: https://repology.org/project/libunistring/versions
+ If it is installed in a nonstandard directory, pass the option
--with-libunistring-prefix=DIR to 'configure'.
* CVS 1.11 or newer
+ Optional but deprecated.
Needed by the 'autopoint' program, if configured with --with-cvs.
+ Homepage:
https://www.nongnu.org/cvs/
+ Download:
https://ftp.gnu.org/non-gnu/cvs/
+ Pre-built package name:
- On Debian and Debian-based systems: cvs,
- On Red Hat distributions: cvs.
- Other: https://repology.org/project/cvs/versions
The following packages should be installed when GNU gettext is installed
(runtime dependencies, but not build dependencies):
None.
The following should be installed when GNU gettext is built, but are not
needed later, once it is installed (build dependencies, but not runtime
dependencies):
* A C runtime, compiler, linker, etc.
+ Mandatory.
Either the platform's native 'cc', or GCC 3.1 or newer.
+ GCC Homepage:
https://gcc.gnu.org/
+ Download:
https://ftp.gnu.org/gnu/gcc/
* A 'make' utility.
+ Mandatory.
Either the platform's native 'make' (for in-tree builds only),
or GNU Make 3.79.1 or newer.
+ GNU Make Homepage:
https://www.gnu.org/software/make/
+ Download:
https://ftp.gnu.org/gnu/make/
* A shell
+ Mandatory.
Either the platform's native 'sh', or Bash.
+ Homepage:
https://www.gnu.org/software/bash/
+ Download:
https://ftp.gnu.org/gnu/bash/
* Core POSIX utilities, including:
[ basename cat chgrp chmod chown cp dd echo expand expr
false hostname install kill ln ls md5sum mkdir mkfifo
mknod mv printenv pwd rm rmdir sleep sort tee test touch
true uname
+ Mandatory.
Either the platform's native utilities, or GNU coreutils.
+ Homepage:
https://www.gnu.org/software/coreutils/
+ Download:
https://ftp.gnu.org/gnu/coreutils/
* The comparison utilities 'cmp' and 'diff'.
+ Mandatory.
Either the platform's native utilities, or GNU diffutils.
+ Homepage:
https://www.gnu.org/software/diffutils/
+ Download:
https://ftp.gnu.org/gnu/diffutils/
* Grep.
+ Mandatory.
Either the platform's native grep, or GNU grep.
+ Homepage:
https://www.gnu.org/software/grep/
+ Download:
https://ftp.gnu.org/gnu/grep/
* Awk.
+ Mandatory.
Either the platform's native awk, mawk, or nawk, or GNU awk.
+ Homepage:
https://www.gnu.org/software/gawk/
+ Download:
https://ftp.gnu.org/gnu/gawk/

864
OGP64/usr/share/doc/gettext/FAQ.html Normal file
View file

@ -0,0 +1,864 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<!--
Copyright (C) 2004-2005, 2007-2008, 2010, 2012, 2014, 2019-2020 Free Software Foundation, Inc.
Written by Bruno Haible <bruno@clisp.org>, 2004.
This manual is free documentation. It is dually licensed under the
GNU FDL and the GNU GPL. This means that you can redistribute this
manual under either of these two licenses, at your choice.
This manual is covered by the GNU FDL. Permission is granted to copy,
distribute and/or modify this document under the terms of the
GNU Free Documentation License (FDL), either version 1.2 of the
License, or (at your option) any later version published by the
Free Software Foundation (FSF); with no Invariant Sections, with no
Front-Cover Text, and with no Back-Cover Texts.
A copy of the license is at
<https://www.gnu.org/licenses/old-licenses/fdl-1.2>.
This manual is covered by the GNU GPL. You can redistribute it and/or
modify it under the terms of the GNU General Public License (GPL), either
version 2 of the License, or (at your option) any later version published
by the Free Software Foundation (FSF).
A copy of the license is at
<https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html>.
-->
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<title>GNU gettext FAQ</title>
</head>
<body>
<h1 style="text-align: center;">Frequently Asked Questions<br>
for GNU gettext
</h1>
<h1 style="text-align: center;">Questions</h1>
<h3>General</h3>
<ul>
<li><a href="#general_mailinglist">Where is the mailing list?</a></li>
<li><a href="#general_source">Where is the newest gettext source?</a></li>
<li><a href="#general_announce">I want to be notified of new gettext
releases.</a></li>
</ul>
<h3>Problems building GNU gettext</h3>
<ul>
<li><a href="#building_solaris_libasprintf">On Solaris, I get a build
error “text relocations remain” in the <span
style="font-family: monospace;">libasprintf</span> subdirectory</a></li>
<li><a href="#building_install">“make install” fails</a></li>
</ul>
<h3>Problems integrating GNU gettext</h3>
<ul>
<li><a href="#integrating_howto">How do I make use of <span
style="font-family: monospace;">gettext()</span> in my package?</a></li>
<li><a href="#integrating_undefined">I get a linker error “undefined
reference to libintl_gettext”</a></li>
<li><a href="#integrating_abuse_gettextize">gettextize adds multiple
references to the same directories/files
to <span style="font-family: monospace;">Makefile.am</span> and </a><span
style="font-family: monospace;"><a href="#integrating_abuse_gettextize">configure.ac</a><br>
</span></li>
<li><a href="#integrating_noop">My program compiles and links fine,
but doesn't output translated
strings.</a><br>
</li>
</ul>
<h3>GNU gettext on Windows</h3>
<ul>
<li><a href="#windows_woe32">What does Woe32 mean?</a></li>
<li><a href="#windows_howto">How do I compile, link and run a program
that uses the gettext()
function?</a><br>
</li>
<li><a href="#windows_setenv">Setting the <span
style="font-family: monospace;">LANG</span>
environment variable doesn't have any effect</a></li>
</ul>
<h3>Other</h3>
<ul>
<li><a href="#newline">What does this mean: “'msgid' and 'msgstr'
entries do not both
end with '\n'”</a></li>
<li><a href="#translit">German umlauts are displayed like “ge"andert”
instead of
“geändert”</a></li>
<li><a href="#localename">The <span style="font-family: monospace;">LANGUAGE</span>
environment variable is ignored after I set <span
style="font-family: monospace;">LANG=en</span></a></li>
<li><a href="#nonascii_strings">I use accented characters in my
source code. How do I tell the
C/C++ compiler in which encoding it is (like <span
style="font-family: monospace;">xgettext</span>'s <span
style="font-family: monospace;">--from-code</span> option)?</a></li>
</ul>
<h1 style="text-align: center;">Answers</h1>
<h3>General</h3>
<h4><a name="general_mailinglist"></a>Where is the mailing list?</h4>
Three mailing lists are available: <br>
<ul>
<li><span style="font-family: monospace;">bug-gettext@gnu.org</span><br>
This mailing list is for discussion of features and bugs of the GNU
gettext <span style="font-style: italic;">software</span>, including
libintl, the gettext-tools, and its autoconf macros. The archive and subscription instructions can be found at <a href="https://lists.gnu.org/mailman/listinfo/bug-gettext">the information page</a>.</li>
<li><span style="font-family: monospace;">translation-i18n@lists.sourceforge.net</span><br>
This mailing list is for methodology questions around
internationalization, and for discussions of translator tools,
including but not limited to GNU gettext.</li>
<li><span style="font-family: monospace;">coordinator@translationproject.org</span><br>
This is the email address of the <a
href="https://translationproject.org/">Translation Project</a>,
that is the project which manages the translated message
catalogs for many free software packages. Note that KDE and GNOME
packages are not part of this project; they have their own translation
projects: <a href="https://l10n.kde.org/">l10n.kde.org</a> and <a
href="https://wiki.gnome.org/TranslationProject/">GNOME Translation Project</a>.<br>
</li>
</ul>
The <span style="font-family: monospace;">bug-gettext</span> list
is archived <a href="https://lists.gnu.org/archive/html/bug-gettext/">here</a>.
You may occasionally also see
<span style="font-family: monospace;">bug-gnu-gettext</span>; this is an alias
of <span style="font-family: monospace;">bug-gettext</span>.<br>
<h4><a name="general_source"></a>Where is the newest gettext source?</h4>
The newest gettext release is available on <span
style="font-family: monospace;">ftp.gnu.org</span> and its mirrors, in
<a href="https://ftp.gnu.org/gnu/gettext/">https://ftp.gnu.org/gnu/gettext/</a>.<br>
<br>
Prereleases are announced on the <a
href="https://lists.gnu.org/mailman/listinfo/autotools-announce"><span
style="font-family: monospace;">autotools-announce</span> mailing list</a>.
Note that prereleases are meant for testing and not meant for use in
production environments. Please don't use the “gettextize” program of a
prerelease on projects which you share with other programmers via CVS.<br>
<br>
If you want to live on the bleeding edge, you can also use the
development sources. Instructions for retrieving the gettext CVS are
found <a href="https://savannah.gnu.org/projects/gettext">here</a>.
Note that building from CVS requires special tools (autoconf, automake,
m4, groff, bison, etc.) and requires that you pay attention to the <span
style="font-family: monospace;">README-alpha</span> and <span
style="font-family: monospace;">autogen.sh</span> files in the CVS.<br>
<h4><a name="general_announce"></a>I want to be notified of new gettext
releases.</h4>
If you are interested in stable gettext releases, you can follow the <a
href="https://lists.gnu.org/mailman/listinfo/info-gnu"><span
style="font-family: monospace;">info-gnu</span> mailing list</a>. It
is also available as a newsgroup <a
href="nntp://news.gmane.org/gmane.org.fsf.announce"><span
style="font-family: monospace;">gmane.org.fsf.announce</span></a>
through <a href="https://www.gmane.org/"><span
style="font-family: monospace;">gmane.org</span></a>.<br>
<br>
You can also periodically check the download location.<br>
<br>
If you are interested in testing prereleases as well, you can subscribe
to the <a href="://lists.gnu.org/mailman/listinfo/autotools-announce"><span
style="font-family: monospace;">autotools-announce</span> mailing
list</a>.<br>
<h3>Problems building GNU gettext</h3>
<h4><a name="building_solaris_libasprintf"></a>On Solaris, I get a
build error “text relocations remain” in the <span
style="font-family: monospace;">libasprintf</span> subdirectory</h4>
libtool (or more precisely, the version of libtool that was available
at the time the gettext release waas made) doesn't support linking C++
libraries with some versions of GCC. As a workaround, you can configure
gettext with the option <span style="font-family: monospace;">--disable-libasprintf</span>.<br>
<h4><a name="building_install"></a>“make install” fails</h4>
“<span style="font-family: monospace;">make install DESTDIR=<span
style="font-style: italic;">/some/tempdir</span></span>” can fail with
an error message relating to <span style="font-family: monospace;">libgettextlib</span>
or <span style="font-family: monospace;">libgettextsrc</span>, or can
silently fail to install <span style="font-family: monospace;">libgettextsrc</span>.
On some platforms, this is due to limitations of libtool regarding <span
style="font-family: monospace;">DESTDIR</span>. On other platforms, it
is due to the way the system handles shared libraries, and libtool
cannot work around it. Fortunately, on Linux and other glibc based
systems, <span style="font-family: monospace;">DESTDIR</span> is
supported if no different version of gettext is already installed (i.e.
it works if you uninstall the older gettext before building and
installing the newer one, or if you do a plain “<span
style="font-family: monospace;">make install</span>” before “<span
style="font-family: monospace;">make install DESTDIR=<span
style="font-style: italic;">/some/tempdir</span></span>”). On other
systems, when&nbsp; <span style="font-family: monospace;">DESTDIR</span>
does not work, you can still do “<span style="font-family: monospace;">make
install</span>” and copy the installed files to <span
style="font-family: monospace;"><span style="font-style: italic;">/some/tempdir</span></span>
afterwards.<br>
<br>
If “<span style="font-family: monospace;">make install</span>” without <span
style="font-family: monospace;">DESTDIR</span> fails, it's a bug which
you are welcome to report to the usual bug report address.
<h3>Problems integrating GNU gettext</h3>
<h4><a name="integrating_howto"></a>How do I make use of <span
style="font-family: monospace;">gettext()</span> in my package?</h4>
It's not as difficult as it sounds. Here's the recipe for C or C++
based packages.<br>
<ul>
<li>Add an invocation of <span style="font-family: monospace;">AM_GNU_GETTEXT([external])</span>
to the package's <span style="font-family: monospace;">configure.{ac,in}</span>
file.</li>
<li>Invoke “<span style="font-family: monospace;">gettextize --copy</span>”.
It will do most of the autoconf/automake related work for you.</li>
<li>Add the <span style="font-family: monospace;">gettext.h</span>
file to the package's source directory, and include it in all source
files that contain translatable strings or do output via <span
style="font-family: monospace;">printf</span> or <span
style="font-family: monospace;">fprintf</span>.</li>
<li>In the source file defining the main() function of the program,
add these lines to the header<br>
<div style="margin-left: 40px;"><code><span
style="font-family: monospace;">#include &lt;locale.h&gt;</span><br
style="font-family: monospace;">
<span style="font-family: monospace;">#include "gettext.h"</span></code><br>
</div>
and these lines near the beginning of the main() function:<br>
<div style="margin-left: 40px;"><code><span
style="font-family: monospace;">setlocale (LC_ALL, "");</span><br
style="font-family: monospace;">
<span style="font-family: monospace;">bindtextdomain (PACKAGE,
LOCALEDIR);</span><br style="font-family: monospace;">
<span style="font-family: monospace;">textdomain (PACKAGE);</span></code><br>
</div>
</li>
<li>Mark all strings that should be translated with _(), like this: <span
style="font-family: monospace;">_("No errors found.")</span>. While
doing this, try to turn the strings into good English, one entire
sentence per string, not more than one paragraph per string, and use
format strings instead of string concatenation. This is needed so that
the translators can provide accurate translations.</li>
<li>In every source file containing translatable strings, add these lines
to the header:<br>
<div style="margin-left: 40px;"><code><span
style="font-family: monospace;">#include "gettext.h"</span><br
style="font-family: monospace;">
<span style="font-family: monospace;">#define _(string) gettext (string)</span></code><br>
</div>
</li>
<li>In the freshly created <span style="font-family: monospace;">po/</span>
directory, set up the <span style="font-family: monospace;">POTFILES.in</span>
file, and do a “<span style="font-family: monospace;">make update-po</span>”.
Then distribute the generated <span style="font-family: monospace;">.pot</span>
file to your nearest translation project.</li>
<li>Shortly before a release, integrate the translators' <span
style="font-family: monospace;">.po</span> files into the <span
style="font-family: monospace;">po/</span> directory and do “<span
style="font-family: monospace;">make update-po</span>” again.<br>
</li>
</ul>
You find detailed descriptions of how this all works in the GNU gettext
manual, chapters “The Maintainer's View” and “Preparing Program
Sources”.
<h4><a name="integrating_undefined"></a>I get a linker error “undefined
reference to libintl_gettext”</h4>
This error means that the program uses the <span
style="font-family: monospace;">gettext()</span> function after having
included the <span style="font-family: monospace;">&lt;libintl.h&gt;</span>
file from GNU gettext (which remaps it to <span
style="font-family: monospace;">libintl_gettext()</span>), however at
link time a function of this name could not be linked in. (It is
expected to come from the <span style="font-family: monospace;">libintl</span>
library, installed by GNU gettext.)<br>
<br>
There are many possible reasons for this error, but in any case you
should consider the <span style="font-family: monospace;">-I</span>, <span
style="font-family: monospace;">-L</span> and <span
style="font-family: monospace;">-l</span> options passed to the
compiler. In packages using <span style="font-family: monospace;">autoconf</span>
generated configure scripts, <span style="font-family: monospace;">-I</span>
options come from the <span style="font-family: monospace;">CFLAGS</span>
and <span style="font-family: monospace;">CPPFLAGS</span> variables
(in Makefiles also <span style="font-family: monospace;">DEFS</span>
and <span style="font-family: monospace;">INCLUDES</span>), <span
style="font-family: monospace;">-L</span> options come from the <span
style="font-family: monospace;">LDFLAGS</span> variable, and <span
style="font-family: monospace;">-l</span> options come from the <span
style="font-family: monospace;">LIBS</span> variable. The first thing
you should check are the values of these variables in your environment
and in the&nbsp; package's <span style="font-family: monospace;">config.status</span>
autoconfiguration result.<br>
<br>
To find the cause of the error, a little analysis is needed. Does the
program's final link command contains the option “-lintl”?<br>
<ul>
<li>If yes:<br>
Find out where the <span style="font-family: monospace;">libintl</span>
comes from. To do this, you have to check for <span
style="font-family: monospace;">libintl.a</span> and <span
style="font-family: monospace;">libintl.so*</span> (<span
style="font-family: monospace;">libintl.dylib</span> on MacOS X) in
each directory given as a -L option, as well as in the compiler's
implicit search directories. (You get these implicit search directories
for gcc by using “<span style="font-family: monospace;">gcc -v</span>”
instead of “<span style="font-family: monospace;">gcc</span>” in the
final link command line; compilers other than GCC usually look in <span
style="font-family: monospace;">/usr/lib</span> and <span
style="font-family: monospace;">/lib</span>.) A shell command like<br>
<div style="margin-left: 40px;"><code>$ for d in /usr/local/lib
/usr/lib /lib; do ls -l $d/libintl.*; done</code><br>
</div>
will show where the <span style="font-family: monospace;">libintl</span>
comes from. By looking at the dates and whether each library defines <span
style="font-family: monospace;">libintl_gettext</span> (via “<span
style="font-family: monospace;">nm <span style="font-style: italic;">path</span>/libintl.so
| grep libintl_gettext</span>”) you can now distinguish three possible
causes of the error:<br>
<ul>
<li>Some older libintl is used instead of the newer one. The fix
is to remove the old library or to reorganize your -L options.</li>
<li>The used libintl is the new one, and it doesn't contain
libintl_gettext. This would be a bug in gettext. If this is the case,
please report it to the usual bug report address.</li>
<li>The used libintl is a static library (libintl.a), there are
no uses of gettext in .o files before the “-lintl” but there are some
after the “-lintl”. In this case the fix is to move the “-lintl” to the
end or near the end of the link command line. The only libintl
dependency that needs to be mentioned after “-lintl” is “-liconv”.</li>
</ul>
</li>
<li>If no:<br>
In this case it's likely a bug in the package you are building: The
package's Makefiles should make sure that “-lintl” is used where needed.<br>
Test whether libintl was found by configure. You can check this by doing<br>
<div style="margin-left: 40px;"><code>$ grep
'\(INTLLIBS\|LIBINTL\)' config.status</code><br>
</div>
and looking whether the value of this autoconf variable is non-empty.<br>
<ul>
<li>If yes: It should be the responsibility of the Makefile to
use the value of this variable in the link command line. Does the
Makefile.in rule for linking the program use <span
style="font-family: monospace;">@INTLLIBS@</span> or <span
style="font-family: monospace;">@LIBINTL@</span>?<br>
<ul>
<li>If no: It's a Makefile.am/in bug.</li>
<li>If yes: Something strange is going on. You need to dig
deeper.</li>
</ul>
Note that <span style="font-family: monospace;">@INTLLIBS@</span> is
for <span style="font-family: monospace;">gettext.m4</span> versions
&lt;= 0.10.40 and <span style="font-family: monospace;">@LIBINTL@</span>
is for <span style="font-family: monospace;">gettext.m4</span>
versions &gt;= 0.11, depending on which <span
style="font-family: monospace;">gettext.m4</span> was used to build
the package's <span style="font-family: monospace;">configure</span> -
regardless of which gettext you have now installed.</li>
<li>If no: So libintl was not found.<br>
Take a look at the package's <span style="font-family: monospace;">configure.in/ac</span>.
Does it invoke AM_GNU_GETTEXT?<br>
<ul>
<li>If no: The gettext maintainers take no responsibilities for
lookalikes named CY_GNU_GETTEXT, AM_GLIB_GNU_GETTEXT, AM_GNOME_GETTEXT
and similar, or for homebrewn autoconf checks. Complain to the package
maintainer.</li>
<li>If yes: It looks like the <span
style="font-family: monospace;">-I</span> and <span
style="font-family: monospace;">-L</span> options were inconsistent.
You should have a <span style="font-family: monospace;">-I<span
style="font-style: italic;">somedir</span>/include</span> in the <span
style="font-family: monospace;">CFLAGS</span> or <span
style="font-family: monospace;">CPPFLAGS</span> if and only if you
also have a <span style="font-family: monospace;">-L<span
style="font-style: italic;">somedir</span>/lib</span> in the <span
style="font-family: monospace;">LDFLAGS</span>. And <span
style="font-family: monospace;"><span style="font-style: italic;">somedir</span>/include</span>
should contain a <span style="font-family: monospace;">libintl.h</span>
if and only if <span style="font-family: monospace;"><span
style="font-style: italic;">somedir</span>/lib</span> contains <span
style="font-family: monospace;">libintl.{a,so}</span>.<br>
This case can also happen if you have configured a GCC &lt; 3.2 with
the same <span style="font-family: monospace;">--prefix</span> option
as you used for GNU libiconv or GNU gettext. This is fatal, because
these versions of GCC implicitly use <span
style="font-family: monospace;">-L<span style="font-style: italic;">prefix</span>/lib</span>
but <span style="font-weight: bold; font-style: italic;">not</span><br
style="font-weight: bold; font-style: italic;">
<span style="font-family: monospace;">-I<span
style="font-style: italic;">prefix</span>/include</span>. The
workaround is to use a different <span style="font-family: monospace;">--prefix</span>
for GCC.<br>
</li>
</ul>
</li>
</ul>
</li>
</ul>
<h4><a name="integrating_abuse_gettextize"></a>gettextize adds multiple
references to the same directories/files
to <span style="font-family: monospace;">Makefile.am</span> and <span
style="font-family: monospace;">configure.ac</span></h4>
If <span style="font-family: monospace;">gettextize</span> is used on
a package, then the <span style="font-family: monospace;">po/</span>, <span
style="font-family: monospace;">intl/</span>, <span
style="font-family: monospace;">m4/</span> directories of the package
are removed, and then <span style="font-family: monospace;">gettextize</span>
is invoked on the package again, it will re-add the <span
style="font-family: monospace;">po/</span>, <span
style="font-family: monospace;">intl/</span>, <span
style="font-family: monospace;">m4/</span> directories and change <span
style="font-family: monospace;">Makefile.am</span>, <span
style="font-family: monospace;">configure.ac</span> and <span
style="font-family: monospace;">ChangeLog</span> accordingly. This is
normal. The second use of <span style="font-family: monospace;">gettextize</span>
here is an abuse of the program. <span style="font-family: monospace;">gettextize</span>
is a wizard intended to transform a <span style="font-style: italic;">working
source package</span> into a <span style="font-style: italic;">working
source package</span> that uses the newest version of gettext. If you
start out from a nonfunctional source package (it is nonfunctional
since you have omitted some directories), you cannot expect that <span
style="font-family: monospace;">gettextize</span> corrects it.<br>
<br>
Often this question arises in packages that use CVS. See the section
“CVS Issues / Integrating with CVS” of the GNU gettext documentation.
This section mentions a program <span style="font-family: monospace;">autopoint</span>
which is designed to reconstruct those files and directories created by
<span style="font-family: monospace;">gettextize</span> that can be
omitted from a CVS repository.<br>
<h4><a name="integrating_noop"></a>My program compiles and links fine,
but doesn't output translated
strings.</h4>
There are several possible reasons. Here is a checklist that allows you
to determine the cause.<br>
<ol>
<li>Check that the environment variables LC_ALL, LC_MESSAGES,
LC_CTYPE, LANG, LANGUAGE together specify a valid locale and language.<br>
To check this, run the commands<br>
<div style="margin-left: 40px;"><code>$ gettext --version</code><br>
<code>$ gettext --help</code><br>
</div>
You should see at least some output in your desired language. If not,
either<br>
<ul>
<li>You have chosen a too exotic language. <span
style="font-family: monospace;">gettext</span> is localized to 33
languages. Choose a less exotic language, such as Galician or
Ukrainian. Or<br>
</li>
<li>There is a problem with your environment variables. Possibly
LC_ALL points to a locale that is not installed, or LC_MESSAGES and
LC_CTYPE are inconsistent.</li>
</ul>
</li>
<li>Check that your program contains a <span
style="font-family: monospace;">setlocale</span> call.<br>
To check this, run your program under ltrace. For example,<br>
<div style="margin-left: 40px;"><code>$ ltrace ./myprog</code><br>
<code>...</code><br>
<code>setlocale(6,
"")&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
= "de_DE.UTF-8"</code><br>
</div>
If you have no ltrace, you can also do this check by running your
program under the debugger. For example,<br>
<div style="margin-left: 40px;"><code>$ gdb ./myprog</code><br>
<code>(gdb) break main</code><br>
<code>(gdb) run</code><br>
<code>Breakpoint 1, main ()</code><br>
<code>(gdb) break setlocale</code><br>
<code>(gdb) continue</code><br>
<code>Breakpoint 2, setlocale ()</code><br>
<code>;; OK, the breakpoint has been hit, setlocale() is being
called.</code><br>
</div>
Either way, check that the return value of <span
style="font-family: monospace;">setlocale()</span> is non-NULL. A NULL
return value indicates a failure.&nbsp;</li>
<li>Check that your program contains a <span
style="font-family: monospace;">textdomain</span> call, a <span
style="font-family: monospace;">bindtextdomain</span> call referring
to the same message domain, and then really calls the <span
style="font-family: monospace;">gettext</span>, <span
style="font-family: monospace;">dgettext</span> or <span
style="font-family: monospace;">dcgettext</span> function.<br>
To check this, run the program under ltrace. For example,<br>
<div style="margin-left: 40px;"><code>$ ltrace ./myprog</code><br>
<code>...</code><br>
<code>textdomain("hello-c")&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
= "hello-c"</code><br>
<code>bindtextdomain("hello-c", "/opt/share"...) = "/opt/share"...</code><br>
<code>dcgettext(0, 0x08048691, 5, 0x0804a200, 0x08048689) =
0x4001721f</code><br>
</div>
If you have no ltrace, you can also do this check by running your
program under the debugger. For example,<br>
<div style="margin-left: 40px;"><code>$ gdb ./myprog</code><br>
<code>(gdb) break main</code><br>
<code>(gdb) run</code><br>
<code>Breakpoint 1, main ()</code><br>
<code>(gdb) break textdomain</code><br>
<code>(gdb) break bindtextdomain</code><br>
<code>(gdb) break gettext</code><br>
<code>(gdb) break dgettext</code><br>
<code>(gdb) break dcgettext</code><br>
<code>(gdb) continue</code><br>
<code>Breakpoint 2, textdomain ()</code><br>
<code>(gdb) continue</code><br>
<code>Breakpoint 3, bindtextdomain ()</code><br>
<code>(gdb) continue</code><br>
<code>Breakpoint 6, dcgettext ()</code><br>
</div>
Note that here <span style="font-family: monospace;">dcgettext()</span>
is called instead of the <span style="font-family: monospace;">gettext()</span>
function mentioned in the source code; this is due to an optimization
in <span style="font-family: monospace;">&lt;libintl.h&gt;</span>.<br>
When using libintl on a non-glibc system, you have to add a prefix “<span
style="font-family: monospace;">libintl_</span>” to all the function
names mentioned here, because that's what the functions are really
named, under the hood.<br>
If <span style="font-family: monospace;">gettext</span>/<span
style="font-family: monospace;">dgettext</span>/<span
style="font-family: monospace;">dcgettext</span> is not called at all,
the possible cause might be that some autoconf or Makefile macrology
has turned off internationalization entirely (like the <span
style="font-family: monospace;">--disable-nls</span> configuration
option usually does).<br>
</li>
<li>Check that the <span style="font-family: monospace;">.mo</span>
file that contains the translation is really there where the program
expects it.<br>
To check this, run the program under strace and look at the <span
style="font-family: monospace;">open()</span> calls. For example,<br>
<div style="margin-left: 40px;"><code>$ strace ./myprog 2&gt;&amp;1
| grep '^open('</code><br>
<code>open("/etc/ld.so.preload", O_RDONLY)&nbsp;&nbsp;&nbsp; = -1
ENOENT (No such file or directory)</code><br>
<code>open("/etc/ld.so.cache",
O_RDONLY)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = 5</code><br>
<code>open("/lib/libc.so.6",
O_RDONLY)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = 5</code><br>
<code>open("/usr/lib/locale/locale-archive", O_RDONLY|O_LARGEFILE)
= 5</code><br>
<code>open("/usr/share/locale/locale.alias", O_RDONLY) = 5</code><br>
<code>open("/opt/share/locale/de/LC_MESSAGES/hello-c.mo", O_RDONLY)
= 5</code><br>
<code>...</code><br>
</div>
A nonnegative <span style="font-family: monospace;">open()</span>
return value means that the file has been found.<br>
If you have no strace, you can also guess the <span
style="font-family: monospace;">.mo</span> file's location: it is<br>
<div style="margin-left: 40px;"><span
style="font-family: monospace;"><span style="font-style: italic;">localedir</span>/<span
style="font-style: italic;">lang</span>/LC_MESSAGES/<span
style="font-style: italic;">domain</span>.mo</span><br>
</div>
where <span style="font-style: italic;">domain</span> is the argument
passed to <span style="font-family: monospace;">textdomain()</span>, <span
style="font-style: italic;">localedir</span> is the second argument
passed to <span style="font-family: monospace;">bindtextdomain()</span>,
and <span style="font-style: italic;">lang</span> is the language (<span
style="font-style: italic;">LL</span>) or language and territory (<span
style="font-style: italic;">LL</span>_<span style="font-style: italic;">CC</span>),
depending on the environment variables checked in step 1.</li>
<li>Check that the .mo file contains a translation for the string
that is being asked for.<br>
To do this, you need to convert the .mo file back to PO file format,
through the command<br>
<div style="margin-left: 40px;"><code>$ msgunfmt </code><span
style="font-family: monospace;"><span style="font-style: italic;">localedir</span>/<span
style="font-style: italic;">lang</span>/LC_MESSAGES/<span
style="font-style: italic;">domain</span>.mo</span><br>
<code></code></div>
and look for an <span style="font-family: monospace;">msgid</span>
that matches the given string.<br>
</li>
</ol>
<h3>GNU gettext on Windows</h3>
<h4><a name="windows_woe32"></a>What does Woe32 mean?</h4>
“Woe32” denotes the Windows 32-bit operating systems for x86: Windows
NT/2000/XP/Vista and Windows 95/98/ME. Microsoft uses the term “Win32” to
denote these; this is a psychological trick in order to make everyone
believe that these OSes are a “win” for the user. However, for most
users and developers, they are a source of woes, which is why I call
them “Woe32”.<br>
<h4><a name="windows_howto"></a>How do I compile, link and run a
program that uses the gettext()
function?</h4>
When you use RedHat's cygwin environment, it's as on Unix:<br>
<ul>
<li>You need to add an <span style="font-family: monospace;">-I</span>
option to the compilation command line, so that the compiler finds the <span
style="font-family: monospace;">libintl.h</span> include file, and</li>
<li>You need to add an <span style="font-family: monospace;">-L</span>
option to the link command line, so that the linker finds the <span
style="font-family: monospace;">libintl</span> library.</li>
</ul>
When you use the Mingw environment (either from within cygwin, with <span
style="font-family: monospace;">CC="gcc -mno-cygwin"</span>, or from
MSYS, with <span style="font-family: monospace;">CC="gcc"</span>), I
don't know the details.<br>
<br>
When you use the Microsoft Visual C/C++ (MSVC) compiler, you will
likely use the precompiled Woe32 binaries. For running a program that
uses gettext(), one needs the <span style="font-family: monospace;">.bin.woe32.zip</span>
packages of <span style="font-family: monospace;">gettext-runtime</span>
and <span style="font-family: monospace;">libiconv</span>. As a
developer, you'll also need the <span style="font-family: monospace;">xgettext</span>
and <span style="font-family: monospace;">msgfmt</span> programs that
are contained in the <span style="font-family: monospace;">.bin.woe32.zip</span>
package of <span style="font-family: monospace;">gettext-tools</span>.
Then<br>
<ul>
<li>You need to add an <span style="font-family: monospace;">-MD</span>
option to all compilation and link command lines. MSVC has six
different, mutually incompatible, compilation models (<span
style="font-family: monospace;">-ML</span>, <span
style="font-family: monospace;">-MT</span>, <span
style="font-family: monospace;">-MD</span>, <span
style="font-family: monospace;">-MLd</span>, <span
style="font-family: monospace;">-MTd</span>, <span
style="font-family: monospace;">-MDd</span>); the default is <span
style="font-family: monospace;">-ML</span>. <span
style="font-family: monospace;">intl.dll</span> uses the <span
style="font-family: monospace;">-MD</span> model, therefore the rest
of the program must use <span style="font-family: monospace;">-MD</span>
as well.<br>
</li>
<li>You need to add an <span style="font-family: monospace;">-I</span>
option to the compilation command line, so that the compiler finds the <span
style="font-family: monospace;">libintl.h</span> include file.<br>
</li>
<li>You need to add an <span style="font-family: monospace;">-L</span>
option to the link command line, so that the linker finds the <span
style="font-family: monospace;">intl.lib</span> library.</li>
<li>You need to copy the <span style="font-family: monospace;">intl.dll</span>
and <span style="font-family: monospace;">iconv.dll</span> to the
directory where your <span style="font-family: monospace;">.exe</span>
files are created, so that they will be found at runtime.<br>
</li>
</ul>
<h4><a name="windows_setenv"></a>Setting the <span
style="font-family: monospace;">LANG</span>
environment variable doesn't have any effect</h4>
If neither LC_ALL, LC_MESSAGES nor LANGUAGES is set, it's the LANG
environment variable which determines the language into which gettext()
translates the messages.<br>
<br>
You can test your program by setting the LANG environment variable from
outside the program. In a Windows command interpreter:<br>
<div style="margin-left: 40px;"><code>set LANG=de_DE</code><br>
<code>.\myprog.exe</code><br>
</div>
Or in a Cygwin shell:<br>
<div style="margin-left: 40px;"><code>$ env LANG=de_DE ./myprog.exe</code><br>
</div>
<br>
If this test fails, look at the question “My program compiles and links
fine, but doesn't output translated
strings.” above.<br>
<br>
If this test succeeds, the problem is related in the way you set the
environment variable. Here is a checklist:<br>
<ul>
<li>Check that you are using the <span
style="font-family: monospace;">-MD</span> option in all compilation
and link command lines. Otherwise you might end up calling the <span
style="font-family: monospace;">putenv()</span> function from
Microsoft's <span style="font-family: monospace;">libc.lib</span>,
whereas <span style="font-family: monospace;">intl.dll</span> is using
the <span style="font-family: monospace;">getenv()</span> function
from Mictosoft's <span style="font-family: monospace;">msvcrt.lib</span>.</li>
<li>Check that you set the environment variable using <span
style="font-style: italic;">both</span> <span
style="font-family: monospace;">SetEnvironmentVariable()</span> and <span
style="font-family: monospace;">putenv()</span>. A convenient way to
do so, and to deal with the fact that some Unix systems have <span
style="font-family: monospace;">setenv()</span> and some don't, is the
following function.<br>
<br>
<div style="margin-left: 40px;"><code>#include &lt;string.h&gt;</code><br>
<code>#include &lt;stdlib.h&gt;</code><br>
<code>#if defined _WIN32</code><br>
<code># include &lt;windows.h&gt;</code><br>
<code>#endif</code><br>
<code></code><br>
<code>int my_setenv (const char * name, const char * value) {</code><br>
<code>&nbsp; size_t namelen = strlen(name);</code><br>
<code>&nbsp; size_t valuelen = (value==NULL ? 0 : strlen(value));</code><br>
<code>#if defined _WIN32</code><br>
<code>&nbsp; /* On Woe32, each process has two copies of the
environment variables,</code><br>
<code>&nbsp;&nbsp;&nbsp;&nbsp; one managed by the OS and one
managed by the C library. We set</code><br>
<code>&nbsp;&nbsp;&nbsp;&nbsp; the value in both locations, so that
other software that looks in</code><br>
<code>&nbsp;&nbsp;&nbsp;&nbsp; one place or the other is guaranteed
to see the value. Even if it's</code><br>
<code>&nbsp;&nbsp;&nbsp;&nbsp; a bit slow. See also</code><br>
<code>&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a
href="https://article.gmane.org/gmane.comp.gnu.mingw.user/8272">https://article.gmane.org/gmane.comp.gnu.mingw.user/8272</a>&gt;</code><br>
<code>&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a
href="https://article.gmane.org/gmane.comp.gnu.mingw.user/8273">https://article.gmane.org/gmane.comp.gnu.mingw.user/8273</a>&gt;</code><br>
<code>&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a
href="https://www.cygwin.com/ml/cygwin/1999-04/msg00478.html">https://www.cygwin.com/ml/cygwin/1999-04/msg00478.html</a>&gt;
*/</code><br>
<code>&nbsp; if (!SetEnvironmentVariableA(name,value))</code><br>
<code>&nbsp;&nbsp;&nbsp; return -1; </code><br>
<code>#endif</code><br>
<code>#if defined(HAVE_PUTENV)</code><br>
<code>&nbsp; char* buffer = (char*)malloc(namelen+1+valuelen+1);</code><br>
<code>&nbsp; if (!buffer)</code><br>
<code>&nbsp;&nbsp;&nbsp; return -1; /* no need to set errno =
ENOMEM */</code><br>
<code>&nbsp; memcpy(buffer,name,namelen);</code><br>
<code>&nbsp; if (value != NULL) {</code><br>
<code>&nbsp;&nbsp;&nbsp; buffer[namelen] = '=';</code><br>
<code>&nbsp;&nbsp;&nbsp; memcpy(buffer+namelen+1,value,valuelen);</code><br>
<code>&nbsp;&nbsp;&nbsp; buffer[namelen+1+valuelen] = 0;</code><br>
<code>&nbsp; } else</code><br>
<code>&nbsp;&nbsp;&nbsp; buffer[namelen] = 0;</code><br>
<code>&nbsp; return putenv(buffer);</code><br>
<code>#elif defined(HAVE_SETENV)</code><br>
<code>&nbsp; return setenv(name,value,1);</code><br>
<code>#else</code><br>
<code>&nbsp; /* Uh oh, neither putenv() nor setenv() ... */</code><br>
<code>&nbsp; return -1;</code><br>
<code>#endif</code><br>
<code>}</code><br>
<code></code></div>
<br>
</li>
</ul>
<h3>Other</h3>
<h4><a name="newline"></a>What does this mean: “'msgid' and 'msgstr'
entries do not both end
with '\n'”</h4>
It means that when the original string ends in a newline, your
translation must also end in a newline. And if the original string does
not end in a newline, then your translation should likewise not have a
newline at the end.<br>
<h4><a name="translit"></a>German umlauts are displayed like
“ge"andert” instead of “geändert”</h4>
This symptom occurs when the <span style="font-family: monospace;">LC_CTYPE</span>
facet of the locale is not set; then gettext() doesn't know which
character set to use, and converts all messages to ASCII, as far as
possible.<br>
<br>
If the program is doing<br>
<code><br>
setlocale (LC_MESSAGES, "");<br>
<br>
</code>then change it to<br>
<code><br>
setlocale (LC_CTYPE, "");<br>
setlocale (LC_MESSAGES, "");<br>
</code><br>
or do both of these in a single call:<br>
<code><br>
setlocale (LC_ALL, "");<br>
</code><br>
If the program is already doing<br>
<code><br>
setlocale (LC_ALL, "");<br>
</code><br>
then the symptom can still occur if the user has not set <span
style="font-family: monospace;">LANG</span>, but instead has set <span
style="font-family: monospace;">LC_MESSAGES</span> to a valid locale
and has set <span style="font-family: monospace;">LC_CTYPE</span> to
nothing or an invalid locale. The fix for the user is then to set <span
style="font-family: monospace;">LANG</span> instead of <span
style="font-family: monospace;">LC_MESSAGES</span>.<br>
<h4><a name="localename"></a>The <span style="font-family: monospace;">LANGUAGE</span>
environment variable is ignored after I set <span
style="font-family: monospace;">LANG=en</span></h4>
This is because “en” is a language name, but not a valid locale name.
The <a href="https://www.gnu.org/software/gettext/manual/html_node/The-LANGUAGE-variable.html">documentation</a> says:<br>
<blockquote>
In the <span style="font-family: monospace;">LANGUAGE</span>
environment variable, but not in the <span
style="font-family: monospace;">LANG</span> environment variable, <span
style="font-style: italic;">LL</span>_<span style="font-style: italic;">CC</span><span
style="font-family: monospace;"> </span>combinations can be
abbreviated as&nbsp;<span style="font-style: italic;">LL</span> to
denote the language's main dialect.</blockquote>
Why is <span style="font-family: monospace;">LANG=en</span> not
allowed? Because <span style="font-family: monospace;">LANG</span> is
a setting for the entire locale, including monetary information, and
this depends on the country: en_GB, en_AU, en_ZA all have different
currencies.<br>
<h4><a name="nonascii_strings"></a>I use accented characters in my
source code. How do I tell the
C/C++ compiler in which encoding it is (like <span
style="font-family: monospace;">xgettext</span>'s <span
style="font-family: monospace;">--from-code</span> option)?</h4>
Short answer: If you want your program to be useful to other people,
then <span style="font-style: italic;">don't use accented characters</span>
(or other non-ASCII characters) in string literals <span
style="font-style: italic;">in the source code</span>. Instead, use
only ASCII for string literals, and use <span
style="font-family: monospace;">gettext()</span> to retrieve their
display-ready form.<br>
<br>
Long explanation:<br>
The reason is that the ISO C standard specifies that the character set
at compilation time can be different from the character set at
execution time.<br>
The character encoding at compilation time is the one which determines
how the source files are interpreted and also how string literals are
stored in the compiled code. This character encoding is generally
unspecified; for recent versions of GCC, it depends on the LC_CTYPE
locale in effect during the compilation process.<br>
The character encoding at execution time is the one which determines
how standard functions like <span style="font-family: monospace;">isprint()</span>,
<span style="font-family: monospace;">wcwidth()</span> etc. work and
how strings written to standard output should be encoded. This
character encoding is specified by POSIX to depend on the LC_CTYPE
locale in effect when the program is executed; see also the description
in the <a href="https://www.gnu.org/software/gettext/manual/html_node/Locale-Names.html">documentation</a>.<br>
Strings in the compiled code are not magically converted between the
time the program is compiled and the time it is run.<br>
<br>
Therefore what could you do to get accented characters to work?<br>
<br>
Can you ensure that the execution character set is the same as the
compilation character set? Even if your program is to be used only in a
single country, this is not realistically possible. For example, in
Germany there are currently three character encodings in use: UTF-8,
ISO-8859-15 and ISO-8859-1. Therefore you would have to explicitly
convert the accented strings from the compilation character set to the
execution character set at runtime, for example through iconv().<br>
<br>
Can you ensure that the compilation character set is the one in which
your source files are stored? This is not realistically possible
either: For compilers other than GCC, there is no way to specify the
compilation character set. So let's assume for a moment that everyone
uses GCC; then you will specify the LC_CTYPE or LC_ALL environment
variable in the Makefile. But for this you have to assume that everyone
has a locale in a given encoding. Be it UTF-8 or ISO-8859-1 - this is
not realistic. People often have no locale installed besides the one
they use.<br>
<br>
Use of wide strings <span style="font-family: monospace;">L"..."</span>
doesn't help solving the problem, because on systems like FreeBSD or
Solaris, the way how wide string literals are stored in compiled code
depends on the compilation&nbsp; character set, just as it does for
narrow strings <span style="font-family: monospace;">"..."</span>.
Moreover, wide strings have problems of their own.<br>
<br>
Use of ISO C 99 Unicode escapes "\u<span style="font-style: italic;">xxxx</span>"
doesn't help either because these characters are converted to the
compilation character set at compile time; so again, since you can't
guarantee that the compilation character set is not ASCII, you're
risking compilation errors just as if the real character had been used
in the source instead of the Unicode escape.<br>
<br>
So, in summary, there is no way to make accented characters in string
literals work in C/C++.<br>
<br>
You might then wonder what <span style="font-family: monospace;">xgettext</span>'s
<span style="font-family: monospace;">--from-code</span> option is good
for. The answer is<br>
<ol>
<li>For the comments in C/C++ source code. The compiler ignores them.<br>
</li>
<li>For other programming languages like Java, for which the compiler
converts all string literals to UTF-8.</li>
</ol>
<br>
<hr style="width: 100%; height: 2px;">
<address>GNU gettext FAQ<br>
Bruno Haible &lt;<a href="mailto:bruno@clisp.org">bruno@clisp.org</a>&gt;</address>
<p>Last modified: 6 June 2020
</p>
</body>
</html>

391
OGP64/usr/share/doc/gettext/HACKING Normal file
View file

@ -0,0 +1,391 @@
All you need to know when hacking (modifying) GNU gettext or when building
it off the git repository.
Requirements
============
You will need reasonably recent versions of the build tools:
* A C compiler; on Cygwin or mingw also a C++ compiler. Such as GNU GCC.
+ Homepage:
https://gcc.gnu.org/
+ Pre-built package name:
- On Debian and Debian-based systems: gcc, gcc-doc,
- On Red Hat distributions: gcc.
- Other: https://repology.org/project/gcc/versions
* GNU automake 1.13 or newer
+ Homepage:
https://www.gnu.org/software/automake/
+ Pre-built package name:
- On Debian and Debian-based systems: automake,
- On Red Hat distributions: automake.
- Other: https://repology.org/project/automake/versions
* GNU autoconf
+ Homepage:
https://www.gnu.org/software/autoconf/
+ Pre-built package name:
- On Debian and Debian-based systems: autoconf, autoconf-doc,
- On Red Hat distributions: autoconf.
- Other: https://repology.org/project/autoconf/versions
* GNU m4
+ Homepage:
https://www.gnu.org/software/m4/
+ Pre-built package name:
- On Debian and Debian-based systems: m4, m4-doc,
- On Red Hat distributions: m4.
- Other: https://repology.org/project/m4/versions
* GNU bison 3.0 or newer
+ Homepage:
https://www.gnu.org/software/bison/
+ Pre-built package name:
- On Debian and Debian-based systems: bison, bison-doc,
- On Red Hat distributions: bison.
- Other: https://repology.org/project/bison/versions
* GNU gperf
+ Homepage:
https://www.gnu.org/software/gperf/
+ Pre-built package name:
- On Debian and Debian-based systems: gperf,
- On Red Hat distributions: gperf.
- Other: https://repology.org/project/gperf/versions
* GNU groff 1.17 or newer
+ Homepage:
https://www.gnu.org/software/groff/
+ Pre-built package name:
- On Debian and Debian-based systems: groff,
- On Red Hat distributions: groff.
- Other: https://repology.org/project/groff/versions
* GNU texinfo
+ Homepage:
https://www.gnu.org/software/texinfo/
+ Pre-built package name:
- On Debian and Debian-based systems: texinfo,
- On Red Hat distributions: texinfo.
- Other: https://repology.org/project/texinfo/versions
* GNU emacs or XEmacs
+ Homepage:
https://www.gnu.org/software/emacs/
https://www.xemacs.org/
+ Pre-built package name:
- On Debian and Debian-based systems: emacs,
- On Red Hat distributions: emacs.
- Other: https://repology.org/project/emacs/versions
* Perl
+ Homepage:
https://www.perl.org/
+ Pre-built package name:
- On Debian and Debian-based systems: perl, perl-doc,
- On Red Hat distributions: perl.
- Other: https://repology.org/project/perl/versions
* TeX (for making the doc in .dvi, .ps or .pdf format)
+ Homepage:
https://tug.org/texlive/
+ Pre-built package name:
- On Debian and Debian-based systems: texlive-base, texlive-latex-base,
- On Red Hat distributions: texlive-base.
- Other: https://repology.org/project/texlive/versions
* Either an internet connection or a recent copy of GNU gnulib.
+ Homepage:
https://www.gnu.org/software/gnulib/
* GNU tar (for creating distributable tarballs)
+ Homepage:
https://www.gnu.org/software/tar/
+ Pre-built package name:
- On Debian and Debian-based systems: tar, tar-doc,
- On Red Hat distributions: tar.
- Other: https://repology.org/project/tar/versions
* GNU Wget
+ Homepage:
https://www.gnu.org/software/wget/
+ Pre-built package name:
- On Debian and Debian-based systems: wget,
- On Red Hat distributions: wget.
- Other: https://repology.org/project/wget/versions
* XZ Utils
+ Homepage:
https://tukaani.org/xz/
+ Pre-built package name:
- On Debian and Debian-based systems: xz-utils,
- On Red Hat distributions: xz.
- Other: https://repology.org/project/xz/versions
* Lzip
+ Homepage:
https://www.nongnu.org/lzip/
+ Pre-built package name:
- On Debian and Debian-based systems: lzip,
- On Red Hat distributions: lzip (EPEL).
- Other: https://repology.org/project/lzip/versions
And, of course, the packages listed in the DEPENDENCIES file.
Additional requirements for maintainers
---------------------------------------
If you are a maintainer, you will want to minimize the number of tests that
are skipped. To this effect, you need to install also:
* A C++ compiler
+ Homepage: https://gcc.gnu.org/
+ Pre-built package name:
- On Debian and Debian-based systems: g++,
- On Red Hat distributions: gcc-c++.
- Other: https://repology.org/project/gcc/versions
* An Objective C compiler
+ Homepage: https://gcc.gnu.org/
+ Pre-built package name:
- On Debian and Debian-based systems: gobjc,
- On Red Hat distributions: gcc-objc.
- Other: https://repology.org/project/gcc/versions
* Python
+ Homepage: https://www.python.org/
+ Pre-built package name:
- On Debian and Debian-based systems: python3, python3-doc,
- On Red Hat distributions: python3.
- Other: https://repology.org/project/python/versions
* GNU clisp
+ Homepage: http://clisp.org/
+ Pre-built package name:
- On Debian and Debian-based systems: clisp, clisp-doc,
- On Red Hat distributions: --.
- Other: https://repology.org/project/clisp/versions
* librep
+ Homepage: http://librep.sourceforge.net/
+ Pre-built package name:
- On Debian and Debian-based systems: rep, rep-doc,
- On Red Hat distributions: --.
- Other: https://repology.org/project/librep/versions
* GNU guile
+ Homepage: https://www.gnu.org/software/guile/
+ Pre-built package name:
- On Debian and Debian-based systems: guile-2.2, guile-2.2-doc,
or: guile-3.0, guile-3.0-doc,
- On Red Hat distributions: guile.
- Other: https://repology.org/project/guile/versions
* GNU smalltalk
+ Homepage: http://smalltalk.gnu.org/
+ Pre-built package name:
- On Debian and Debian-based systems: gnu-smalltalk, gnu-smalltalk-doc,
- On Red Hat distributions: gnu-smalltalk (EPEL).
- Other: https://repology.org/project/smalltalk/versions
* A Java compiler
+ Homepage: http://openjdk.java.net/
+ Pre-built package name:
- On Debian and Debian-based systems:
openjdk-11-jdk or openjdk-8-jdk or openjdk-7-jdk, default-jdk,
- On Red Hat distributions:
java-11-openjdk or java-1.8.0-openjdk or java-1.7.0-openjdk.
- Other: https://repology.org/project/openjdk/versions
* A C# compiler
+ Homepage: https://www.mono-project.com/
+ Pre-built package name:
- On Debian and Debian-based systems: mono-mcs,
- On Red Hat distributions: mono-devel (EPEL).
- Other: https://repology.org/project/mono/versions
* GNU awk
+ Homepage: https://www.gnu.org/software/gawk/
+ Pre-built package name:
- On Debian and Debian-based systems: gawk, gawk-doc,
- On Red Hat distributions: gawk.
- Other: https://repology.org/project/gawk/versions
* The Free Pascal compiler ppc386 or ppcx64
+ Homepage: https://www.freepascal.org/
+ Pre-built package name:
- On Debian and Debian-based systems: fp-compiler, fp-docs,
- On Red Hat distributions: fpc (EPEL).
- Other: https://repology.org/project/fpc/versions
* The Free Pascal Free Component Library
+ Homepage: https://www.freepascal.org/fcl/fcl.var
+ Pre-built package name:
- On Debian and Debian-based systems: fp-units-fcl,
- On Red Hat distributions: --.
- Other: https://repology.org/project/fpc/versions
* Tcl
+ Homepage: https://www.tcl.tk/
+ Pre-built package name:
- On Debian and Debian-based systems: tcl, tcl-doc,
- On Red Hat distributions: tcl.
- Other: https://repology.org/project/tcl/versions
* Perl
+ Homepage: https://www.perl.org/
+ Pre-built package name:
- On Debian and Debian-based systems: perl, perl-doc,
- On Red Hat distributions: perl.
- Other: https://repology.org/project/perl/versions
* The Perl packages Locale::Messages and libintl-perl
+ Homepage: http://search.cpan.org/~guido/libintl-perl/
+ Pre-built package name:
- On Debian and Debian-based systems: libintl-perl,
- On Red Hat distributions: perl-libintl.
- Other: https://repology.org/project/perl:libintl-perl/versions
* php
+ Homepage: http://www.php.net/
+ Pre-built package name:
- On Debian and Debian-based systems: php,
- On Red Hat distributions: php.
- Other: https://repology.org/project/php/versions
* Ruby
+ Homepage: https://www.ruby-lang.org/en/
+ Pre-built package name:
- On Debian and Debian-based systems: ruby,
- On Red Hat distributions: ruby.
- Other: https://repology.org/project/ruby/versions
* The ruby-gettext package
+ Homepage: https://ruby-gettext.github.io/
+ Pre-built package name:
- On Debian and Debian-based systems: ruby-gettext,
- On Red Hat distributions: ruby-gettext.
- Other: https://repology.org/project/ruby:gettext/versions
* lua
+ Homepage: https://www.lua.org/
+ Pre-built package name:
- On Debian and Debian-based systems: lua5.3 or lua5.2 or lua5.1,
- On Red Hat distributions: lua.
- Other: https://repology.org/project/lua/versions
* The lua-gettext package
+ Homepage: https://gitlab.com/sukhichev/lua-gettext/blob/master/README.us.md
+ Debian and Ubuntu packages:
Download, then install through
$ sudo dpkg -i lua-gettext_0.0_amd64.deb
+ Pre-built package name:
- On Debian and Debian-based systems: --,
- On Red Hat distributions: --.
- Other: https://repology.org/project/lua:gettext/versions
* The GNOME/Mozilla JavaScript interpreter
+ Homepage: https://wiki.gnome.org/Projects/Gjs
+ Pre-built package name:
- On Debian and Debian-based systems: gjs, gir1.2-gtk-3.0,
- On Red Hat distributions: gjs.
- Other: https://repology.org/project/gjs/versions
* The GNOME Vala compiler
+ Homepage: https://wiki.gnome.org/Projects/Vala
+ Pre-built package name:
- On Debian and Debian-based systems: valac,
- On Red Hat distributions: vala.
- Other: https://repology.org/project/vala/versions
If you want to exercise the sample programs in gettext-tools/examples/, you
also need to install:
* The Qt GUI toolkit library
+ Homepage: https://www.qt.io/
+ Pre-built package name:
- On Debian and Debian-based systems: libqt5gui5, qt5-doc-html,
or: libqt4-dev,
- On Red Hat distributions: --.
- Other: https://repology.org/project/qt/versions
* The wxWidgets GUI toolkit library
+ Homepage: https://www.wxwidgets.org/
+ Pre-built package name:
- On Debian and Debian-based systems: libwxgtk3.0-gtk3-dev, wx3.0-doc,
or: libwxgtk3.0-dev,
- On Red Hat distributions: --.
- Other: https://repology.org/project/wxwidgets/versions
* The GNUstep toolkit and development environment
+ Homepage: http://www.gnustep.org/
+ Pre-built package name:
- On Debian and Debian-based systems: gnustep-devel,
- On Red Hat distributions: gnustep-base (EPEL).
- Other: https://repology.org/project/gnustep-base/versions
* The C# System.Windows.Forms implementation
+ Homepage: https://www.mono-project.com/
+ Pre-built package name:
- On Debian and Debian-based systems: libmono-system-windows-forms4.0-cil,
- On Red Hat distributions: mono-winforms (EPEL).
- Other: https://pkgs.org/search/?q=mono-winforms
And you need to install a couple of locales, used by the tests.
By default, only those enabled in /etc/locale.gen are preinstalled.
$ sudo localedef -i de_DE -f ISO-8859-1 de_DE.ISO-8859-1
$ sudo localedef -i de_DE -f UTF-8 de_DE.UTF-8
$ sudo localedef -i fa_IR -f UTF-8 fa_IR
$ sudo localedef -i fr_FR -f ISO-8859-1 fr_FR.ISO-8859-1
$ sudo localedef -i fr_FR -f UTF-8 fr_FR.UTF-8
$ sudo localedef -i ja_JP -f EUC-JP ja_JP.EUC-JP
$ sudo localedef -i tr_TR -f UTF-8 tr_TR.UTF-8
$ sudo localedef -i zh_CN -f GB18030 zh_CN.GB18030
Building off the Git repository
===============================
Access to the Git repository is described at
https://savannah.gnu.org/git/?group=gettext .
After fetching the sources from the Git repository, peek at the comments in
autogen.sh, then run
./autopull.sh
./autogen.sh
Then you can proceed with "./configure" as usual.
Each time you want to update the source, do not only "git pull". Instead do
git pull && ./autopull.sh
./autogen.sh
Continuous integration
======================
The package is built automatically, at regular intervals. You find the latest
build results here:
https://gitlab.com/gnu-gettext/ci-distcheck/pipelines
https://gitlab.com/gnu-gettext/ci-distcheck/-/jobs?scope=finished
Submitting patches
==================
Patches should be sent to bug-gettext@gnu.org, the bug/feature mailing
list. You can subscribe to the mailing list, or see the list
archives, by following links from
https://savannah.gnu.org/mail/?group=gettext .
To email a patch you can use a shell command like 'git format-patch
-1' to create a file, and then attach the file to your email.
GNU gettext development no longer stores descriptions of new changes
in ChangeLog files. Instead, a single ChangeLog file is generated
from the commit messages when a release is prepared. So changes you
commit should not touch any of the ChangeLog files in the repository,
but instead should contain the log entries in the commit message.
For the style of a ChangeLog entry, see the "Change Logs" section of
the GNU coding standards:
https://www.gnu.org/prep/standards/html_node/Change-Logs.html

1464
OGP64/usr/share/doc/gettext/NEWS Normal file
View file

File diff suppressed because it is too large Load diff

65
OGP64/usr/share/doc/gettext/README Normal file
View file

@ -0,0 +1,65 @@
This is the GNU gettext package. It is interesting for authors or
maintainers of other packages or programs which they want to see
internationalized. As one step the handling of messages in different
languages should be implemented. For this task GNU gettext provides
the needed tools and library functions.
It is also interesting for translators, because GNU gettext provides
the 'msgmerge' program, which prepares a message catalog before a
translation update.
Users of GNU packages should also install GNU gettext because some
other GNU packages will use the gettext program included in this
package to internationalize the messages given by shell scripts.
The homepage of this package is at
https://www.gnu.org/software/gettext/
The primary FTP site for its distribution is
https://ftp.gnu.org/pub/gnu/gettext/
Report bugs
- in the bug tracker at <https://savannah.gnu.org/projects/gettext>
- or by email to <bug-gettext@gnu.org>.
The configure script provides a non-standard option. It is also
available in other packages that use the functionality of GNU gettext.
Use
--disable-nls
if you absolutely don't want to have messages handling code. You will
always get the original messages (mostly English). You could consider
using NLS support even when you do not need other tongues. If you do
not install any messages catalogs or do not specify to use another but
the C locale you will not get translations.
The set of languages for which catalogs should be installed can also be
specified while configuring. Of course they must be available but the
intersection of these two sets are computed automatically. You could
once and for all define in your profile/cshrc the variable LINGUAS:
(Bourne Shell) LINGUAS="de fr nl"; export LINGUAS
(C Shell) setenv LINGUAS "de fr nl"
or specify it directly while configuring
env LINGUAS="de fr nl" ./configure
Consult the manual for more information on language names.
Other files you might look into:
COPYING - copying conditions
DEPENDENCIES - list of prerequisite packages, to be installed before this one
INSTALL - general compilation and installation rules
NEWS - major changes in the current version
THANKS - list of contributors
JOIN-GNU - invitation to join the GNU project

380
OGP64/usr/share/doc/gettext/THANKS Normal file
View file

@ -0,0 +1,380 @@
The GNU gettext package is the first full featured package
directed to NLS support in the GNU packages. It has its roots in the
GNU C Library development and of course the (never officially
released) GNU locale package, mostly written by Jim Meyering.
Therefore a lot of people participated in the process of creating this
software.
Written in April-June 1995 by
Ulrich Drepper drepper@ipd.info.uni-karlsruhe.de
Special thanks to François Pinard <pinard@iro.umontreal.ca>, who did a
major part of the testing, provided the Emacs PO mode, and wrote major
parts of the manual.
Peter Miller <millerp@canb.auug.org.au> invested a lot of his time in making
gettext usable in other GNU projects and wrote the msgmerge, msgcmp, and
msgunfmt programs.
Guido Flohr <guido@imperia.net> wrote the Perl backend of xgettext and
the libintl-perl package.
Gora Mohanty <gora_mohanty@yahoo.co.in> wrote the tutorial.
Thanks to all of the following for their valuable
hints/fixes/discussions/contributions:
Aaron Stone aaron@serendipity.cx
Aaron Williams aaron_williams@net.com
Abel Cheung abelcheung@gmail.com
Adam Heath doogie@debian.org
Adrian Bunk bunk@fs.tum.de
Akim Demaille akim@epita.fr
Alain Bench messtic@oreka.com
Alain Guibert derogaton+bggt@oreka.com, alguibert@free.fr
Albert Chin-A-Young china@thewrittenword.com
Alex Henrie alexhenrie24@gmail.com
Alexander Potashev aspotashev@gmail.com
Alexander V. Lukyanov lav@yars.free.net
Alexander Turbov AVTurbov@gwise.eltech.ru
Alexandre Duret-Lutz aduret@enst.fr
Alfred M. Szmidt ams@kemisten.nu
Alfredo alfredio@ciaoweb.it
Amos Batto amosbatto@yahoo.com
Andreas Buening andreas.buening@nexgo.de
Andreas Fischer a.fischer@asentics.de
Andreas Schwab schwab@issan.informatik.uni-dortmund.de
Andreas Stricker astricker@futurelab.ch
Andrew Suffield asuffield@debian.org
Andrew V. Samoilov kai@cmail.ru
Andrew Walrond andrew@walrond.org
Andrew Zabolotny zap@cobra.ru
Andries Brouwer andries.brouwer@cwi.nl
Andriy Gapon avg@icyb.net.ua
Arkadiusz Miśkiewicz arekm@pld-linux.org
Arpad Biro biro_arpad@yahoo.com
Artem Vakhitov temcat@mail.ru
Arto C. Nirkko anirkko@insel.ch
Asgeir Frimannsson asgeirf@redhat.com
A. Sopicki a.sopicki@gmx.de
? atras-ch@mail.msiu.ru
Bang Jun Young bangjy@nownuri.nowcom.co.kr
Barry A. Warsaw barry@zope.com
Behdad Esfahbod behdad@cs.toronto.edu
Ben Elliston bje@redhat.com
Benno Schulenberg bensberg@justemail.net
Benoît Sibaud benoit.sibaud@rd.francetelecom.com
Bernard Massot bmassot@free.fr
Bernhard Herzog bernhard@users.sourceforge.net
Bernhard Voelker mail@bernhard-voelker.de
Bethor bethor@gmx.li
Bill Perry wmperry@aventail.com
Bjoern Voigt bjoern@cs.tu-berlin.de
Bob Rossi bob_rossi@cox.net
Bram Moolenaar bram@moolenaar.net
Bruno Haible haible@ma2s2.mathematik.uni-karlsruhe.de
Carl Fürstenberg azatoth@gmail.com
Carlo Wood carlo@alinoe.com
Carlos O'Donell carlos@redhat.com
Carlos Perelló Marín carlos@gnome.org
Cary Farah cfarah@jjkeller.com
Charles Wilson cwilson@ece.gatech.edu
Chris Pickett chris.pickett@mail.mcgill.ca
Chris Zubrzycki beren@mac.com
Christian Casteyde casteyde.christian@free.fr
Christian Neumair chris@gnome-de.org
Christian von Roques roques@pond.sub.org
Christoph Thielecke u15119@hs-harz.de
Christopher Seip chris.seip@hp.com
Chuck Berg chuckhberg@yahoo.com
Chusslove Illich (Часлав Илић) caslav.ilic@gmx.net
Claudio Fontana claudio@gnu.org
Clytie Siddall clytie@riverland.net.au
Colin Marquardt colin@marquardt-home.de
Colin Watson cjwatson@debian.org
Crispin Flowerday cflowerday@zeus.com
Daiki Ueno ueno@gnu.org
Dalibor Topic robilad@kaffe.org
Daniel Burr dburr@dburr.net
Daniel Burrows dburrows@debian.org
Daniel Leidert daniel.leidert@wgdd.de
Daniel Schepler schepler@math.berkeley.edu
Danilo Šegan (Данило Шеган) danilo@gnome.org
Dave Patton dpatton@confluence.org
David Faure faure@kde.org
David Fraser davidf@sjsoft.com
David Shea dshea@redhat.com
Denis Barbier barbier@linuxfr.org
Denis Excoffier Denis.Excoffier@free.fr
Deniz Akkus deniz@arayan.com
Dennis Bjorklund db@zigo.dhs.org
Dennis Schridde devurandom@gmx.net
Derek Clegg derek_clegg@next.com
Derek Robert Price derek@ximbiot.com
Dwayne Bailey dwayne@obsidian.co.za
Earnie Boyd earnie_boyd@yahoo.com
Ed Avis avised@kbcfp.com
Eddy Petrişor eddy.petrisor@gmail.com
Edmund Grimley Evans edmundo@rano.org
Egmont Koblinger egmont@uhulinux.hu
Eli Zaretskii eliz@is.elta.co.il
Enrico Scholz enrico.scholz@informatik.tu-chemnitz.de
Enrique Melero Gómez justine@iprolink.ch
Eric Backus ericb@lsid.hp.com
Eric Blake ebb9@byu.net
Eric Botcazou ebotcazou@libertysurf.fr
Erik Sigra sigra@home.se
Farzaneh Sarafraz farzaneh@farsiweb.info
Fatih Demir kabalak@gtranslator.org
Felipe Contreras al593181@mail.mty.itesm.mx
Felix Natter f.natter@ndh.net
Finlay Dobbie finlay.dobbie@gmail.com
Francesco Potortì pot@fly.cnuce.cnr.it
Frank Donahoe fdonahoe@wilkes1.wilkes.edu
Frédéric L. W. Meunier 0@pervalidus.tk
Gabor Kelemen kelemeng@gnome.hu
Gabriele Stilli superenzima@libero.it
Gaëtan Frenoy gaetan@frenoy.net
Gary V. Vaughan gary@gnu.org
Gerald Combs gerald@ethereal.com
Glenn Popelka gpp@mail.gpopelka.com
Golubev I. N. gin@mo.msk.ru
Greg McGary gkm@magilla.cichlid.com
Göran Uddeborg gvran@uddeborg.pp.se
Guillem Jover guillem@hadrons.org
Hagen Fritsch itooktheredpill@gmx.de
Haibin Zhang dragzhb@yahoo.com.cn
Han Boetes han@mijncomputer.nl
Hanno Boeck hanno@gentoo.org
Hans Ulrich Niedermann debian@n-dimensional.de
Henry Nelson netb@yuba.ne.jp
H. J. Lu hjl@lucon.org
Hrvoje Niksic hniksic@srce.hr
Igor Brezac igor@ipass.net
Ivailo xakepa10@gmail.com
I. Thomas Cundiff tcundiff@eclipse.net
Jacob (=Jouk) Jansen joukj@hrem.stm.tudelft.nl
Jakub Bogusz qboosh@pld-linux.org
Jakub Jelinek jj@sunsite.ms.mff.cuni.cz
Jakub Wilk jwilk@debian.org
James A Baker jabaker@mac.com
James Henstridge james@daa.com.au
James Youngman jay@gnu.org
Jan Djärv jan.djarv@mbox200.swipnet.se
Jan-Marek Glogowski glogow@stud.fbi.fh-darmstadt.de
Jan Schneider jan@horde.org
Jason Keltz jas@cs.yorku.ca
Javier Fernández-Sanguino Peña jfs@computer.org
Javier Jardón jjardon@gnome.org
Jeff Bonggren jbon@cfl.rr.com
Jeff Rizzo riz@netbsd.org
Jens A. Tkotz jens@peino.de
Jens Petersen petersen@redhat.com
Jesper Fehrlund jesper@prisjakt.nu
Jiang Xin worldhello.net@gmail.com
Jim Meyering meyering@na-net.ornl.gov
Jochen Hein jochen@jochen.org
Joel Reicher joel@panacea.null.org
Johan Liljegren johan@johanliljegren.se
Jonas 'Sortie' Termansen sortie@maxsi.org
Jörg Schilling schilling@fokus.fraunhofer.de
Joey Hess joeyh@debian.org
Jonas Koch Bentzen jonas@understroem.dk
Joosep-Georg Järvemaa joosep-georg.jarvemaa_4898@eesti.ee
Jorn Baayen jbaayen@dds.nl
Josep Puigdemont baldrick@terra.es
Joshua R. Poulson jrp@plaza.ds.adp.com
Jouko Orava joorava@pcu.helsinki.fi
Jozef Riha jose1711@gmail.com
Juan Manuel Guerrero st001906@hrz1.hrz.tu-darmstadt.de
Jürgen A. Erhard jae+debian@jerhard.org
Julien Chiron julien.chiron@univ.u-3mrs.fr
Jun Sawataishi jsawa@attglobal.net
Kalle Niemitalo tosi@ees2.oulu.fi
Karl Berry kb@cs.umb.edu
Karl Chen quarl@hkn.eecs.berkeley.edu
Karl Eichwalder ke@suse.de
Kaveh R. Ghazi ghazi@caip.rutgers.edu
Kenichi Handa handa@etl.go.jp
Ken Y. Clark kclark@logsoft.com
Kevin Ryde user42@zip.com.au
Kingpin mthurn@copper.dulles.tasc.com
Kiyotaka Sakai ksakai@isr.co.jp
Kouichi Hashikawa z01a7ksy@cs.ecip.tohoku.ac.jp
Larry Schwimmer rosebud@cyclone.stanford.edu
Lars Hecking lhecking@nmrc.ie
Lars Wendler polynomial-c@gentoo.org
Laurent Bourbeau bourbeau@progiciels-bpi.ca
Len Makin len@hpc.csiro.au
Leonard den Ottolander leonard@den.ottolander.nl
Leonardo Fontenelle leo.fontenelle@gmail.com
Liu Garfield jackliu9999@hotmail.com
Lorenzo Gil Sanchez lgs@sicem.biz
Luke Schierer lschiere@rackspace.com
Maciej W. Rozycki macro@ds2.pg.gda.pl
Mads Martin Joergensen mmj@suse.de
Manuel Uberti manuel@boccaperta.com
Marc Prior MarcPrior@compuserve.com
Marcel Telka marcel@telka.sk
Marcus Daniels marcus@sysc.pdx.edu
Marcus Meissner meissner@suse.de
Marin Purgar pmc@asgard.hr
Marius Schamschula mschamschula@gmail.com
Mark A. Wicks mwicks@kettering.edu
Mark D. Baushke mdb@cvshome.org
Mark Detrick Mark.Detrick@mcdata.com
Mark Eichin eichin@thok.org
Mark Junker mjscod@gmx.de
Martin Mokrejš mmokrejs@natur.cuni.cz
Martin Pitt mpitt@debian.org
Martin Quinson martin.quinson@ens-lyon.fr
Martin v. Löwis martin@loewis.home.cs.tu-berlin.de
Maryam Aly maryam@foursquare.com
Masanori Ogino masanori.ogino@gmail.com
Matt Dreezer matthew.dreezer@edl.uk.eds.com
Matthew Behrens askedrelic@gmail.com
Matthew McGillis matthew@jenika.com
Matthias Clasen mclasen@redhat.com
Mattias Ellert mattias.ellert@tsl.uu.se
Matthias Kiefer kiefer@kde.org
Max de Mendizabal max@acer.com.mx
Max Lin mlin@suse.com
Michael C. Toren mct@toren.net
Michael Felt aixtools@gmail.com
Michael Opdenacker m-opdenacker@ti.com
Michael Pyne mpyne@kde.org
Michael Schloh von Bennewitz michael.schloh@cw.com
Michael Stather michaelstather@nuzi.de
Michal Černoevič Michal.Cernoevic@pvt.cz
Michel Robitaille robitail@iro.umontreal.ca
Michele Locati michele@locati.it
Michelle Konzack linux4michelle@freenet.de
Miguel Ángel Arruga Vivas rosen644835@gmail.com
Mike Frysinger vapier@gentoo.org
Miroslaw Dobrzanski-Neumann mne@mosaic-ag.com
? mus1876@gmx.info
Nelson H. F. Beebe beebe@math.utah.edu
Nick Clifton nickc@redhat.com
Nicolas François nicolas.francois@centraliens.net
Niki Waibel niki.waibel@newlogic.com
Nils Magnus Larsgard nmlarsgaard@atmel.no
Nils Naumann naumann@unileoben.ac.at
Nina Kusnetsova nina@ns.kinetics.nsc.ru
Noah Friedman friedman@splode.com
Noah Slater nslater@gmail.com
Olly Betts olly@survex.com
O'Riva oriva@earthlink.net
Owen Taylor otaylor@redhat.com
Pablo Saratxaga pablo@mandrakesoft.com
Paolo Bonzini bonzini@gnu.org
Paul D. Smith psmith@gnu.org
Paul Eggert eggert@twinsun.com
Paul Jarc prj@po.cwru.edu
Paul Martinolich martinol@nrlssc.navy.mil
Paul Zimmermann Paul.Zimmermann@inria.fr
Pavel Kharitonov ineiev@gnu.org
Pavel Raiskup praiskup@redhat.com
Pavel Roskin proski@gnu.org
Pekka Järveläinen pj@csc.fi
Pepa cerna.zelva@seznam.cz
Perry Rapp prapp@erols.com, lifelines_3_0_18@hotmail.com
Perry Smith pedz@easesoftware.com
Peter Breitenlohner peb@mppmu.mpg.de
Peter Eisentraut peter@eisentraut.org
Pierre pierre42d@9online.fr
Philip Withnall philip@tecnocode.co.uk
Philipp Thomas pthomas@suse.de
Primoz Peterlin primoz.peterlin@biofiz.mf.uni-lj.si
Rafał Maszkowski rzm@icm.edu.pl
Ralf Corsepius rc040203@freenet.de
Ralf Menzel menzel@ls6.cs.uni-dortmund.de
Ralf Wildenhues Ralf.Wildenhues@gmx.de
Raphaël Zhou xzhou@tlmcom.fr
Recai Oktaş roktas@omu.edu.tr
Reinout van Schouwen reinout@cs.vu.nl
Reuben Thomas rrt@sc3d.org
Rhys Weatherley rweather@zip.com.au
Richard Hughes hughsient@gmail.com
Richard Lloyd richard.lloyd@connectinternetsolutions.com
Richard S. Blake blakers@presence-group.com
Richard Stallman rms@gnu.org
Rob Landley rob@landley.net
Rob Leslie rob@mars.org
Robert Millan rmh@aybabtu.com
Robert Vock RobertVock@gmx.de
Roberto Bagnara bagnara@cs.unipr.it
Rodrigo Stulzer Lopes rodrigo@conectiva.com.br
Roger Leigh rl117@york.ac.uk
Roland McGrath roland@gnu.ai.mit.edu
Ron Lee ron@debian.org
Roozbeh Pournader roozbeh@sharif.edu
Ross Golder ross@golder.org
Roumen Petrov bugtrack@roumenpetrov.info
Ryan Anderson ryan@autoweb.net
Ryan Schmidt gettext-2007b@ryandesign.com
Sakai Kiyotaka ksakai@netwk.ntt-at.co.jp
Sam Hocevar sam@zoy.org
Sam Steingold sds@gnu.org
Santiago Vila Doncel sanvila@unex.es
Sebastian Günther sguenther@gmx.de
Sergey Poznyakoff gray@mirddin.farlep.net
Sergio Talens-Oliag sto@debian.org
Shaun McCance shaunm@gnome.org
Siddhesh Poyarekar siddhesh@redhat.com
Simon Josefsson jas@extundo.com
Simon Watts swatts@ngms.eu.com
Simos Xenitellis simos74@gmx.net
Stanislav Brabec sbrabec@suse.cz
Stanislav Visnovsky visnovsky@nenya.ms.mff.cuni.cz
Stefan Hundhammer sh@suse.de
Stefan Kost kost@imn.htwk-leipzig.de
Stefan Kowski stefan.kowski@parks-informatik.de
Stefan Nordhausen nordhaus@informatik.hu-berlin.de
Stefano Lattarini stefano.lattarini@gmail.com
Steffen Macke sdteffen@gmail.com
Stepan Kasal kasal@math.cas.cz
Stephan Kulow coolo@kde.org
Stephane Matamontero stephane.matamontero@gemodek.de
Stephen Cartwright sgcartwr@ucalgary.ca
Stephen Gildea gildea@stop.mail-abuse.org
Steve Ellcey sellcey@mips.com
Steven Edwards Steven_Ed4153@yahoo.com
Svante Seleborg svante@axantum.com
Sven Joachim sven_joachim@web.de
Sven Utcke utcke@informatik.uni-hamburg.de
Sylvain Beucler beuc@gnu.org
Thomas E. Dickey dickey@clark.net
Thomas Vander Stichele thomas@apestaart.org
Thorsten Kukuk kukuk@suse.de
Thorsten Maerz torte@netztorte.de
Tim Mooney mooney@dogbert.cc.ndsu.nodak.edu
Tim Van Holder tim.van.holder@pandora.be
Tom Tromey tromey@cygnus.com
Tommy mesilliac@gmail.com
Tommy Johansson tommy@kanalen.org
Tor Lillqvist tml@iki.fi
Trond Eivind Glomsrød teg@redhat.com
Uwe Ohse uwe@tirka.gun.de
Vaclav Haisman V.Haisman@sh.cvut.cz
Václav Slavík vaclav@slavik.io
Valery Beaud valery.beaud@art.alcatel.fr
Vera Mickael vera.mickael@free.fr
Veronica Loell info@nakawe.se
Vincent Torri vtorri@univ-evry.fr
Volodymyr M. Lisivka lvm@mystery.lviv.net
Wang Jian lark@linux.net.cn
Warren L Dodge warrend@mdhost.cse.tek.com
Werner Koch wk@gnupg.org
Werner Lemberg wl@gnu.org
Wesley J. Landaker wjl@icecavern.net
William J Poser wjposer@ldc.upenn.edu
Will Newton will.newton@linaro.org
Wojciech Polak polak@gnu.org
Xiong Jiang jxiong@offtopic.org
Yann Dirson ydirson@altern.org
Yaakov Selkowitz yselkowi@redhat.com
Yves Codet ycodet@club-internet.fr
Thanks to all members of the translation teams for the different
languages.

450
OGP64/usr/share/doc/gettext/fdl.texi Normal file
View file

@ -0,0 +1,450 @@
@c The GNU Free Documentation License.
@center Version 1.2, November 2002
@c This file is intended to be included within another document,
@c hence no sectioning command or @node.
@display
Copyright @copyright{} 2000,2001,2002 Free Software Foundation, Inc.
51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
@end display
@enumerate 0
@item
PREAMBLE
The purpose of this License is to make a manual, textbook, or other
functional and useful document @dfn{free} in the sense of freedom: to
assure everyone the effective freedom to copy and redistribute it,
with or without modifying it, either commercially or noncommercially.
Secondarily, this License preserves for the author and publisher a way
to get credit for their work, while not being considered responsible
for modifications made by others.
This License is a kind of ``copyleft'', which means that derivative
works of the document must themselves be free in the same sense. It
complements the GNU General Public License, which is a copyleft
license designed for free software.
We have designed this License in order to use it for manuals for free
software, because free software needs free documentation: a free
program should come with manuals providing the same freedoms that the
software does. But this License is not limited to software manuals;
it can be used for any textual work, regardless of subject matter or
whether it is published as a printed book. We recommend this License
principally for works whose purpose is instruction or reference.
@item
APPLICABILITY AND DEFINITIONS
This License applies to any manual or other work, in any medium, that
contains a notice placed by the copyright holder saying it can be
distributed under the terms of this License. Such a notice grants a
world-wide, royalty-free license, unlimited in duration, to use that
work under the conditions stated herein. The ``Document'', below,
refers to any such manual or work. Any member of the public is a
licensee, and is addressed as ``you''. You accept the license if you
copy, modify or distribute the work in a way requiring permission
under copyright law.
A ``Modified Version'' of the Document means any work containing the
Document or a portion of it, either copied verbatim, or with
modifications and/or translated into another language.
A ``Secondary Section'' is a named appendix or a front-matter section
of the Document that deals exclusively with the relationship of the
publishers or authors of the Document to the Document's overall
subject (or to related matters) and contains nothing that could fall
directly within that overall subject. (Thus, if the Document is in
part a textbook of mathematics, a Secondary Section may not explain
any mathematics.) The relationship could be a matter of historical
connection with the subject or with related matters, or of legal,
commercial, philosophical, ethical or political position regarding
them.
The ``Invariant Sections'' are certain Secondary Sections whose titles
are designated, as being those of Invariant Sections, in the notice
that says that the Document is released under this License. If a
section does not fit the above definition of Secondary then it is not
allowed to be designated as Invariant. The Document may contain zero
Invariant Sections. If the Document does not identify any Invariant
Sections then there are none.
The ``Cover Texts'' are certain short passages of text that are listed,
as Front-Cover Texts or Back-Cover Texts, in the notice that says that
the Document is released under this License. A Front-Cover Text may
be at most 5 words, and a Back-Cover Text may be at most 25 words.
A ``Transparent'' copy of the Document means a machine-readable copy,
represented in a format whose specification is available to the
general public, that is suitable for revising the document
straightforwardly with generic text editors or (for images composed of
pixels) generic paint programs or (for drawings) some widely available
drawing editor, and that is suitable for input to text formatters or
for automatic translation to a variety of formats suitable for input
to text formatters. A copy made in an otherwise Transparent file
format whose markup, or absence of markup, has been arranged to thwart
or discourage subsequent modification by readers is not Transparent.
An image format is not Transparent if used for any substantial amount
of text. A copy that is not ``Transparent'' is called ``Opaque''.
Examples of suitable formats for Transparent copies include plain
@sc{ascii} without markup, Texinfo input format, La@TeX{} input
format, @acronym{SGML} or @acronym{XML} using a publicly available
@acronym{DTD}, and standard-conforming simple @acronym{HTML},
PostScript or @acronym{PDF} designed for human modification. Examples
of transparent image formats include @acronym{PNG}, @acronym{XCF} and
@acronym{JPG}. Opaque formats include proprietary formats that can be
read and edited only by proprietary word processors, @acronym{SGML} or
@acronym{XML} for which the @acronym{DTD} and/or processing tools are
not generally available, and the machine-generated @acronym{HTML},
PostScript or @acronym{PDF} produced by some word processors for
output purposes only.
The ``Title Page'' means, for a printed book, the title page itself,
plus such following pages as are needed to hold, legibly, the material
this License requires to appear in the title page. For works in
formats which do not have any title page as such, ``Title Page'' means
the text near the most prominent appearance of the work's title,
preceding the beginning of the body of the text.
A section ``Entitled XYZ'' means a named subunit of the Document whose
title either is precisely XYZ or contains XYZ in parentheses following
text that translates XYZ in another language. (Here XYZ stands for a
specific section name mentioned below, such as ``Acknowledgements'',
``Dedications'', ``Endorsements'', or ``History''.) To ``Preserve the Title''
of such a section when you modify the Document means that it remains a
section ``Entitled XYZ'' according to this definition.
The Document may include Warranty Disclaimers next to the notice which
states that this License applies to the Document. These Warranty
Disclaimers are considered to be included by reference in this
License, but only as regards disclaiming warranties: any other
implication that these Warranty Disclaimers may have is void and has
no effect on the meaning of this License.
@item
VERBATIM COPYING
You may copy and distribute the Document in any medium, either
commercially or noncommercially, provided that this License, the
copyright notices, and the license notice saying this License applies
to the Document are reproduced in all copies, and that you add no other
conditions whatsoever to those of this License. You may not use
technical measures to obstruct or control the reading or further
copying of the copies you make or distribute. However, you may accept
compensation in exchange for copies. If you distribute a large enough
number of copies you must also follow the conditions in section 3.
You may also lend copies, under the same conditions stated above, and
you may publicly display copies.
@item
COPYING IN QUANTITY
If you publish printed copies (or copies in media that commonly have
printed covers) of the Document, numbering more than 100, and the
Document's license notice requires Cover Texts, you must enclose the
copies in covers that carry, clearly and legibly, all these Cover
Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
the back cover. Both covers must also clearly and legibly identify
you as the publisher of these copies. The front cover must present
the full title with all words of the title equally prominent and
visible. You may add other material on the covers in addition.
Copying with changes limited to the covers, as long as they preserve
the title of the Document and satisfy these conditions, can be treated
as verbatim copying in other respects.
If the required texts for either cover are too voluminous to fit
legibly, you should put the first ones listed (as many as fit
reasonably) on the actual cover, and continue the rest onto adjacent
pages.
If you publish or distribute Opaque copies of the Document numbering
more than 100, you must either include a machine-readable Transparent
copy along with each Opaque copy, or state in or with each Opaque copy
a computer-network location from which the general network-using
public has access to download using public-standard network protocols
a complete Transparent copy of the Document, free of added material.
If you use the latter option, you must take reasonably prudent steps,
when you begin distribution of Opaque copies in quantity, to ensure
that this Transparent copy will remain thus accessible at the stated
location until at least one year after the last time you distribute an
Opaque copy (directly or through your agents or retailers) of that
edition to the public.
It is requested, but not required, that you contact the authors of the
Document well before redistributing any large number of copies, to give
them a chance to provide you with an updated version of the Document.
@item
MODIFICATIONS
You may copy and distribute a Modified Version of the Document under
the conditions of sections 2 and 3 above, provided that you release
the Modified Version under precisely this License, with the Modified
Version filling the role of the Document, thus licensing distribution
and modification of the Modified Version to whoever possesses a copy
of it. In addition, you must do these things in the Modified Version:
@enumerate A
@item
Use in the Title Page (and on the covers, if any) a title distinct
from that of the Document, and from those of previous versions
(which should, if there were any, be listed in the History section
of the Document). You may use the same title as a previous version
if the original publisher of that version gives permission.
@item
List on the Title Page, as authors, one or more persons or entities
responsible for authorship of the modifications in the Modified
Version, together with at least five of the principal authors of the
Document (all of its principal authors, if it has fewer than five),
unless they release you from this requirement.
@item
State on the Title page the name of the publisher of the
Modified Version, as the publisher.
@item
Preserve all the copyright notices of the Document.
@item
Add an appropriate copyright notice for your modifications
adjacent to the other copyright notices.
@item
Include, immediately after the copyright notices, a license notice
giving the public permission to use the Modified Version under the
terms of this License, in the form shown in the Addendum below.
@item
Preserve in that license notice the full lists of Invariant Sections
and required Cover Texts given in the Document's license notice.
@item
Include an unaltered copy of this License.
@item
Preserve the section Entitled ``History'', Preserve its Title, and add
to it an item stating at least the title, year, new authors, and
publisher of the Modified Version as given on the Title Page. If
there is no section Entitled ``History'' in the Document, create one
stating the title, year, authors, and publisher of the Document as
given on its Title Page, then add an item describing the Modified
Version as stated in the previous sentence.
@item
Preserve the network location, if any, given in the Document for
public access to a Transparent copy of the Document, and likewise
the network locations given in the Document for previous versions
it was based on. These may be placed in the ``History'' section.
You may omit a network location for a work that was published at
least four years before the Document itself, or if the original
publisher of the version it refers to gives permission.
@item
For any section Entitled ``Acknowledgements'' or ``Dedications'', Preserve
the Title of the section, and preserve in the section all the
substance and tone of each of the contributor acknowledgements and/or
dedications given therein.
@item
Preserve all the Invariant Sections of the Document,
unaltered in their text and in their titles. Section numbers
or the equivalent are not considered part of the section titles.
@item
Delete any section Entitled ``Endorsements''. Such a section
may not be included in the Modified Version.
@item
Do not retitle any existing section to be Entitled ``Endorsements'' or
to conflict in title with any Invariant Section.
@item
Preserve any Warranty Disclaimers.
@end enumerate
If the Modified Version includes new front-matter sections or
appendices that qualify as Secondary Sections and contain no material
copied from the Document, you may at your option designate some or all
of these sections as invariant. To do this, add their titles to the
list of Invariant Sections in the Modified Version's license notice.
These titles must be distinct from any other section titles.
You may add a section Entitled ``Endorsements'', provided it contains
nothing but endorsements of your Modified Version by various
parties---for example, statements of peer review or that the text has
been approved by an organization as the authoritative definition of a
standard.
You may add a passage of up to five words as a Front-Cover Text, and a
passage of up to 25 words as a Back-Cover Text, to the end of the list
of Cover Texts in the Modified Version. Only one passage of
Front-Cover Text and one of Back-Cover Text may be added by (or
through arrangements made by) any one entity. If the Document already
includes a cover text for the same cover, previously added by you or
by arrangement made by the same entity you are acting on behalf of,
you may not add another; but you may replace the old one, on explicit
permission from the previous publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this License
give permission to use their names for publicity for or to assert or
imply endorsement of any Modified Version.
@item
COMBINING DOCUMENTS
You may combine the Document with other documents released under this
License, under the terms defined in section 4 above for modified
versions, provided that you include in the combination all of the
Invariant Sections of all of the original documents, unmodified, and
list them all as Invariant Sections of your combined work in its
license notice, and that you preserve all their Warranty Disclaimers.
The combined work need only contain one copy of this License, and
multiple identical Invariant Sections may be replaced with a single
copy. If there are multiple Invariant Sections with the same name but
different contents, make the title of each such section unique by
adding at the end of it, in parentheses, the name of the original
author or publisher of that section if known, or else a unique number.
Make the same adjustment to the section titles in the list of
Invariant Sections in the license notice of the combined work.
In the combination, you must combine any sections Entitled ``History''
in the various original documents, forming one section Entitled
``History''; likewise combine any sections Entitled ``Acknowledgements'',
and any sections Entitled ``Dedications''. You must delete all
sections Entitled ``Endorsements.''
@item
COLLECTIONS OF DOCUMENTS
You may make a collection consisting of the Document and other documents
released under this License, and replace the individual copies of this
License in the various documents with a single copy that is included in
the collection, provided that you follow the rules of this License for
verbatim copying of each of the documents in all other respects.
You may extract a single document from such a collection, and distribute
it individually under this License, provided you insert a copy of this
License into the extracted document, and follow this License in all
other respects regarding verbatim copying of that document.
@item
AGGREGATION WITH INDEPENDENT WORKS
A compilation of the Document or its derivatives with other separate
and independent documents or works, in or on a volume of a storage or
distribution medium, is called an ``aggregate'' if the copyright
resulting from the compilation is not used to limit the legal rights
of the compilation's users beyond what the individual works permit.
When the Document is included in an aggregate, this License does not
apply to the other works in the aggregate which are not themselves
derivative works of the Document.
If the Cover Text requirement of section 3 is applicable to these
copies of the Document, then if the Document is less than one half of
the entire aggregate, the Document's Cover Texts may be placed on
covers that bracket the Document within the aggregate, or the
electronic equivalent of covers if the Document is in electronic form.
Otherwise they must appear on printed covers that bracket the whole
aggregate.
@item
TRANSLATION
Translation is considered a kind of modification, so you may
distribute translations of the Document under the terms of section 4.
Replacing Invariant Sections with translations requires special
permission from their copyright holders, but you may include
translations of some or all Invariant Sections in addition to the
original versions of these Invariant Sections. You may include a
translation of this License, and all the license notices in the
Document, and any Warranty Disclaimers, provided that you also include
the original English version of this License and the original versions
of those notices and disclaimers. In case of a disagreement between
the translation and the original version of this License or a notice
or disclaimer, the original version will prevail.
If a section in the Document is Entitled ``Acknowledgements'',
``Dedications'', or ``History'', the requirement (section 4) to Preserve
its Title (section 1) will typically require changing the actual
title.
@item
TERMINATION
You may not copy, modify, sublicense, or distribute the Document except
as expressly provided for under this License. Any other attempt to
copy, modify, sublicense or distribute the Document is void, and will
automatically terminate your rights under this License. However,
parties who have received copies, or rights, from you under this
License will not have their licenses terminated so long as such
parties remain in full compliance.
@item
FUTURE REVISIONS OF THIS LICENSE
The Free Software Foundation may publish new, revised versions
of the GNU Free Documentation 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. See
@uref{https://www.gnu.org/copyleft/}.
Each version of the License is given a distinguishing version number.
If the Document specifies that a particular numbered version of this
License ``or any later version'' applies to it, you have the option of
following the terms and conditions either of that specified version or
of any later version that has been published (not as a draft) by the
Free Software Foundation. If the Document does not specify a version
number of this License, you may choose any version ever published (not
as a draft) by the Free Software Foundation.
@end enumerate
@page
@heading ADDENDUM: How to use this License for your documents
To use this License in a document you have written, include a copy of
the License in the document and put the following copyright and
license notices just after the title page:
@smallexample
@group
Copyright (C) @var{year} @var{your name}.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
Texts. A copy of the license is included in the section entitled ``GNU
Free Documentation License''.
@end group
@end smallexample
If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
replace the ``with@dots{}Texts.'' line with this:
@smallexample
@group
with the Invariant Sections being @var{list their titles}, with
the Front-Cover Texts being @var{list}, and with the Back-Cover Texts
being @var{list}.
@end group
@end smallexample
If you have Invariant Sections without Cover Texts, or some other
combination of the three, merge those two alternatives to suit the
situation.
If your document contains nontrivial examples of program code, we
recommend releasing these examples in parallel under your choice of
free software license, such as the GNU General Public License,
to permit their use in free software.
@c Local Variables:
@c ispell-local-pdict: "ispell-dict"
@c End:

745
OGP64/usr/share/doc/gettext/tutorial.html Normal file
View file

@ -0,0 +1,745 @@
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML i18n//EN">
<!--
Copyright (C) 2004-2005, 2012 Gora Mohanty.
Written by Gora Mohanty <gora_mohanty@yahoo.co.in>, 2004.
This manual is covered by the GNU FDL. Permission is granted to copy,
distribute and/or modify this document under the terms of the
GNU Free Documentation License (FDL), version 1.2.
A copy of the license is at
<https://www.gnu.org/licenses/old-licenses/fdl-1.2>.
-->
<!--Converted with jLaTeX2HTML 2002-2-1 (1.70) JA patch-1.4
patched version by: Kenshi Muto, Debian Project.
LaTeX2HTML 2002-2-1 (1.70),
original version by: Nikos Drakos, CBLU, University of Leeds
* revised and updated by: Marcus Hennecke, Ross Moore, Herb Swan
* with significant contributions from:
Jens Lippmann, Marek Rouchal, Martin Wilck and others -->
<HTML>
<HEAD>
<TITLE>A tutorial on Native Language Support using GNU gettext</TITLE>
<META NAME="description" CONTENT="A tutorial on Native Language Support using GNU gettext">
<META NAME="keywords" CONTENT="memo">
<META NAME="resource-type" CONTENT="document">
<META NAME="distribution" CONTENT="global">
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="jLaTeX2HTML v2002-2-1 JA patch-1.4">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
<!--
<LINK REL="STYLESHEET" HREF="memo.css">
-->
</HEAD>
<BODY >
<!--Navigation Panel
<DIV CLASS="navigation">
<IMG WIDTH="81" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next_inactive"
SRC="file:/usr/share/latex2html/icons/nx_grp_g.png">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up"
SRC="file:/usr/share/latex2html/icons/up_g.png">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous"
SRC="file:/usr/share/latex2html/icons/prev_g.png">
<BR>
<BR><BR></DIV>
End of Navigation Panel-->
<H1 ALIGN="CENTER">A tutorial on Native Language Support using GNU gettext</H1><DIV CLASS="author_info">
<P ALIGN="CENTER"><STRONG>G.&nbsp;Mohanty</STRONG></P>
<P ALIGN="CENTER"><STRONG>Revision 0.3: 24 July 2004</STRONG></P>
</DIV>
<H3>Abstract:</H3>
<DIV CLASS="ABSTRACT">
The use of the GNU <TT>gettext</TT> utilities to implement support for native
languages is described here. Though, the language to be supported is
considered to be Oriya, the method is generally applicable. Likewise, while
Linux was used as the platform here, any system using GNU <TT>gettext</TT> should work
in a similar fashion.
<P>
We go through a step-by-step description of how to make on-screen messages
from a toy program to appear in Oriya instead of English; starting from the
programming and ending with the user's viewpoint. Some discussion is also made
of how to go about the task of translation.
</DIV>
<P>
<H1><A NAME="SECTION00010000000000000000">
Introduction</A>
</H1>
Currently, both commercial and free computer software is typically written and
documented in English. Till recently, little effort was expended towards
allowing them to interact with the user in languages other than English, thus
leaving the non-English speaking world at a disadvantage. However, that
changed with the release of the GNU <TT>gettext</TT> utilities, and nowadays most GNU
programs are written within a framework that allows easy translation of the
program message to languages other than English. Provided that translations
are available, the language used by the program to interact with the user can
be set at the time of running it. <TT>gettext</TT> manages to achieve this seemingly
miraculous task in a manner that simplifies the work of both the programmer
and the translator, and, more importantly, allows them to work independently
of each other.
<P>
This article describes how to support native languages under a system using
the GNU <TT>gettext</TT> utilities. While it should be applicable to other versions of
<TT>gettext</TT>, the one actually used for the examples here is version
0.12.1. Another system, called <TT>catgets</TT>, described in the X/Open
Portability Guide, is also in use, but we shall not discuss that here.
<P>
<H1><A NAME="SECTION00020000000000000000">
A simple example</A>
</H1>
<A NAME="sec:simple"></A>Our first example of using <TT>gettext</TT> will be the good old Hello World program,
whose sole function is to print the phrase “Hello, world!” to the terminal.
The internationalized version of this program might be saved in hello.c as:
<PRE>
1 #include &lt;libintl.h&gt;
2 #include &lt;locale.h&gt;
3 #include &lt;stdio.h&gt;
4 #include &lt;stdlib.h&gt;
5 int main(void)
6 {
7 setlocale( LC_ALL, "" );
8 bindtextdomain( "hello", "/usr/share/locale" );
9 textdomain( "hello" );
10 printf( gettext( "Hello, world!\n" ) );
11 exit(0);
12 }
</PRE>
Of course, a real program would check the return values of the functions and
try to deal with any errors, but we have omitted that part of the code for
clarity. Compile as usual with <TT>gcc -o hello hello.c</TT>. The program should
be linked to the GNU libintl library, but as this is part of the GNU C
library, this is done automatically for you under Linux, and other systems
using glibc.
<H2><A NAME="SECTION00021000000000000000">
The programmer's viewpoint</A>
</H2>
As expected, when the <TT>hello</TT> executable is run under the default locale
(usually the C locale) it prints “Hello, world!” in the terminal. Besides
some initial setup work, the only additional burden faced by the programmer is
to replace any string to be printed with <TT>gettext(string)</TT>, i.e., to
instead pass the string as an argument to the <TT>gettext</TT> function. For lazy
people like myself, the amount of extra typing can be reduced even further by
a CPP macro, e.g., put this at the beginning of the source code file,
<PRE>
#define _(STRING) gettext(STRING)
</PRE>
and then use <TT>_(string)</TT> instead of <TT>gettext(string)</TT>.
<P>
Let us dissect the program line-by-line.
<OL>
<LI><TT>locale.h</TT> defines C data structures used to hold locale
information, and is needed by the <TT>setlocale</TT> function. <TT>libintl.h</TT>
prototypes the GNU text utilities functions, and is needed here by
<TT>bindtextdomain</TT>, <TT>gettext</TT>, and <TT>textdomain</TT>.
</LI>
<LI>The call to <TT>setlocale</TT> () on line 7, with LC_ALL as the first argument
and an empty string as the second one, initializes the entire current locale
of the program as per environment variables set by the user. In other words,
the program locale is initialized to match that of the user. For details see
“man <TT>setlocale</TT>.”
</LI>
<LI>The <TT>bindtextdomain</TT> function on line 8 sets the base directory for the
message catalogs for a given message domain. A message domain is a set of
translatable messages, with every software package typically having its own
domain. Here, we have used “hello” as the name of the message domain for
our toy program. As the second argument, /usr/share/locale, is the default
system location for message catalogs, what we are saying here is that we are
going to place the message catalog in the default system directory. Thus, we
could have dispensed with the call to <TT>bindtextdomain</TT> here, and this
function is useful only if the message catalogs are installed in a
non-standard place, e.g., a packaged software distribution might have
the catalogs under a po/ directory under its own main directory. See “man
<TT>bindtextdomain</TT>” for details.
</LI>
<LI>The <TT>textdomain</TT> call on line 9 sets the message domain of the current
program to “hello,” i.e., the name that we are using for our example
program. “man textdomain” will give usage details for the function.
</LI>
<LI>Finally, on line 10, we have replaced what would normally have been,
<PRE>
printf( "Hello, world!\n" );
</PRE>
with,
<PRE>
printf( gettext( "Hello, world!\n" ) );
</PRE>
(If you are unfamiliar with C, the <!-- MATH
$\backslash$
-->
<SPAN CLASS="MATH">&#92;</SPAN>n at the end of the string
produces a newline at the end of the output.) This simple modification to all
translatable strings allows the translator to work independently from the
programmer. <TT>gettextize</TT> eases the task of the programmer in adapting a
package to use GNU <TT>gettext</TT> for the first time, or to upgrade to a newer
version of <TT>gettext</TT>.
</LI>
</OL>
<H2><A NAME="SECTION00022000000000000000">
Extracting translatable strings</A>
</H2>
Now, it is time to extract the strings to be translated from the program
source code. This is achieved with <TT>xgettext</TT>, which can be invoked as follows:
<PRE><FONT color="red">
xgettext -d hello -o hello.pot hello.c
</FONT></PRE>
This processes the source code in hello.c, saving the output in hello.pot (the
argument to the -o option).
The message domain for the program should be specified as the argument
to the -d option, and should match the domain specified in the call to
<TT>textdomain</TT> (on line 9 of the program source). Other details on how to use
<TT>gettext</TT> can be found from “man gettext.”
<P>
A .pot (portable object template) file is used as the basis for translating
program messages into any language. To start translation, one can simply copy
hello.pot to oriya.po (this preserves the template file for later translation
into a different language). However, the preferred way to do this is by
use of the <TT>msginit</TT> program, which takes care of correctly setting up some
default values,
<PRE><FONT color="red">
msginit -l or_IN -o oriya.po -i hello.pot
</FONT></PRE>
Here, the -l option defines the locale (an Oriya locale should have been
installed on your system), and the -i and -o options define the input and
output files, respectively. If there is only a single .pot file in the
directory, it will be used as the input file, and the -i option can be
omitted. For me, the oriya.po file produced by <TT>msginit</TT> would look like:
<PRE>
# Oriya translations for PACKAGE package.
# Copyright (C) 2004 THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
# Gora Mohanty &lt;gora_mohanty@yahoo.co.in&gt;, 2004.
#
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2004-06-22 02:22+0530\n"
"PO-Revision-Date: 2004-06-22 02:38+0530\n"
"Last-Translator: Gora Mohanty &lt;gora_mohanty@yahoo.co.in&gt;\n"
"Language-Team: Oriya\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: hello.c:10
msgid "Hello, world!\n"
msgstr ""
</PRE>
<TT>msginit</TT> prompted for my email address, and probably obtained my real name
from the system password file. It also filled in values such as the revision
date, language, character set, presumably using information from the or_IN
locale.
<P>
It is important to respect the format of the entries in the .po (portable
object) file. Each entry has the following structure:
<PRE>
WHITE-SPACE
# TRANSLATOR-COMMENTS
#. AUTOMATIC-COMMENTS
#: REFERENCE...
#, FLAG...
msgid UNTRANSLATED-STRING
msgstr TRANSLATED-STRING
</PRE>
where, the initial white-space (spaces, tabs, newlines,...), and all
comments might or might not exist for a particular entry. Comment lines start
with a '#' as the first character, and there are two kinds: (i) manually
added translator comments, that have some white-space immediately following the
'#,' and (ii) automatic comments added and maintained by the <TT>gettext</TT> tools,
with a non-white-space character after the '#.' The <TT>msgid</TT> line contains
the untranslated (English) string, if there is one for that PO file entry, and
the <TT>msgstr</TT> line is where the translated string is to be entered. More on
this later. For details on the format of PO files see gettext::Basics::PO
Files:: in the Emacs info-browser (see Appdx.&nbsp;<A HREF="#sec:emacs-info">A</A> for an
introduction to using the info-browser in Emacs).
<H2><A NAME="SECTION00023000000000000000">
Making translations</A>
</H2>
The oriya.po file can then be edited to add the translated Oriya
strings. While the editing can be carried out in any editor if one is careful
to follow the PO file format, there are several editors that ease the task of
editing PO files, among them being po-mode in Emacs, <TT>kbabel</TT>, gtranslator,
poedit, etc. Appdx.&nbsp;<A HREF="#sec:pofile-editors">B</A> describes features of some of
these editors.
<P>
The first thing to do is fill in the comments at the beginning and the header
entry, parts of which have already been filled in by <TT>msginit</TT>. The lines in
the header entry are pretty much self-explanatory, and details can be found in
the gettext::Creating::Header Entry:: info node. After that, the remaining
work consists of typing the Oriya text that is to serve as translations for
the corresponding English string. For the <TT>msgstr</TT> line in each of the
remaining entries, add the translated Oriya text between the double quotes;
the translation corresponding to the English phrase in the <TT>msgid</TT> string
for the entry. For example, for the phrase “Hello world!<!-- MATH
$\backslash$
-->
<SPAN CLASS="MATH">&#92;</SPAN>n” in
oriya.po, we could enter “&#x0b28;&#x0b2e;&#x0b38;&#x0b4d;&#x0b15;&#x0b3e;&#x0b30;<!-- MATH
$\backslash$
-->
<SPAN CLASS="MATH">&#92;</SPAN>n”. The final
oriya.po file might look like:
<PRE>
# Oriya translations for hello example package.
# Copyright (C) 2004 Gora Mohanty
# This file is distributed under the same license as the hello example package.
# Gora Mohanty &lt;gora_mohanty@yahoo.co.in&gt;, 2004.
#
msgid ""
msgstr ""
"Project-Id-Version: oriya\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2004-06-22 02:22+0530\n"
"PO-Revision-Date: 2004-06-22 10:54+0530\n"
"Last-Translator: Gora Mohanty &lt;gora_mohanty@yahoo.co.in&gt;\n"
"Language-Team: Oriya\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: KBabel 1.3\n"
#: hello.c:10
msgid "Hello, world!\n"
msgstr "&#x0b28;&#x0b2e;&#x0b38;&#x0b4d;&#x0b15;&#x0b3e;&#x0b30;\n"
</PRE>
<P>
For editing PO files, I have found the <TT>kbabel</TT> editor suits me the best. The
only problem is that while Oriya text can be entered directly into <TT>kbabel</TT>
using the xkb Oriya keyboard layouts&nbsp;[<A
HREF="memo.html#xkb-oriya-layout">1</A>] and the entries
are saved properly, the text is not displayed correctly in the <TT>kbabel</TT> window
if it includes conjuncts. Emacs po-mode is a little restrictive, but strictly
enforces conformance with the PO file format. The main problem with it is that
it does not seem currently possible to edit Oriya text in Emacs. <TT>yudit</TT>
is the best at editing Oriya text, but does not ensure that the PO file format
is followed. You can play around a bit with these editors to find one that
suits your personal preferences. One possibility might be to first edit the
header entry with <TT>kbabel</TT> or Emacs po-mode, and then use <TT>yudit</TT> to enter
the Oriya text on the <TT>msgstr</TT> lines.
<H2><A NAME="SECTION00024000000000000000">
Message catalogs</A>
</H2>
<A NAME="sec:catalog"></A>After completing the translations in the oriya.po file, it must be compiled to
a binary format that can be quickly loaded by the <TT>gettext</TT> tools. To do that,
use:
<PRE><FONT color="red">
msgfmt -c -v -o hello.mo oriya.po
</FONT></PRE>
The -c option does detailed checking of the PO file format, -v makes the
program verbose, and the output filename is given by the argument to the -o
option. Note that the base of the output filename should match the message
domain given in the first arguments to <TT>bindtextdomain</TT> and <TT>textdomain</TT> on
lines 8 and 9 of the example program in Sec.&nbsp;<A HREF="#sec:simple">2</A>. The .mo
(machine object) file should be stored in the location whose base directory is
given by the second argument to <TT>bindtextdomain</TT>. The final location of the
file will be in the sub-directory LL/LC_MESSAGES or LL_CC/LC_MESSAGES under
the base directory, where LL stands for a language, and CC for a country. For
example, as we have chosen the standard location, /usr/share/locale, for our
base directory, and for us the language and country strings are “or” and
“IN,” respectively, we will place hello.mo in /usr/share/locale/or_IN. Note
that you will need super-user privilege to copy hello.mo to this system
directory. Thus,
<PRE><FONT color="red">
mkdir -p /usr/share/locale/or_IN/LC_MESSAGES
cp hello.mo /usr/share/locale/or_IN/LC_MESSAGES
</FONT></PRE>
<H2><A NAME="SECTION00025000000000000000">
The user's viewpoint</A>
</H2>
Once the message catalogs have been properly installed, any user on the system
can use the Oriya version of the Hello World program, provided an Oriya locale
is available. First, change your locale with,
<PRE><FONT color="red">
echo $LANG
export LANG=or_IN
</FONT></PRE>
The first statement shows you the current setting of your locale (this is
usually en_US, and you will need it to reset the default locale at the end),
while the second one sets it to an Oriya locale.
<P>
A Unicode-capable terminal emulator is needed to view Oriya output
directly. The new versions of both gnome-terminal and konsole (the KDE
terminal emulator) are Unicode-aware. I will focus on gnome-terminal as it
seems to have better support for internationalization. gnome-terminal needs to
be told that the bytes arriving are UTF-8 encoded multibyte sequences. This
can be done by (a) choosing Terminal <TT>-&gt;</TT> Character Coding <TT>-&gt;</TT>
Unicode (UTF-8), or (b) typing “/bin/echo -n -e
'<!-- MATH
$\backslash$
-->
<SPAN CLASS="MATH">&#92;</SPAN>033%<!-- MATH
$\backslash$
-->
<SPAN CLASS="MATH">&#92;</SPAN>G'” in the terminal, or (c) by running
/bin/unicode_start. Likewise, you can revert to the default locale by (a)
choosing Terminal <TT>-&gt;</TT> Character Coding <TT>-&gt;</TT> Current Locale
(ISO-8859-1), or (b) “/bin/echo -n -e '<!-- MATH
$\backslash$
-->
<SPAN CLASS="MATH">&#92;</SPAN>033%<!-- MATH
$\backslash$
-->
<SPAN CLASS="MATH">&#92;</SPAN>@',” or
(c) by running /bin/unicode_stop. Now, running the example program (after
compiling with gcc as described in Sec.&nbsp;<A HREF="#sec:simple">2</A>) with,
<PRE><FONT color="red">
./hello
</FONT></PRE>
should give you output in Oriya. Please note that conjuncts will most likely
be displayed with a “halant” as the terminal probably does not render Indian
language fonts correctly. Also, as most terminal emulators assume fixed-width
fonts, the results are hardly likely to be aesthetically appealing.
<P>
An alternative is to save the program output in a file, and view it with
<TT>yudit</TT> which will render the glyphs correctly. Thus,
<PRE><FONT color="red">
./hello &gt; junk
yudit junk
</FONT></PRE>
Do not forget to reset the locale before resuming usual work in the
terminal. Else, your English characters might look funny.
<P>
While all this should give the average user some pleasure in being able to see
Oriya output from a program without a whole lot of work, it should be kept in
mind that we are still far from our desired goal. Hopefully, one day the
situation will be such that rather than deriving special pleasure from it,
users take it for granted that Oriya should be available and are upset
otherwise.
<P>
<H1><A NAME="SECTION00030000000000000000">
Adding complications: program upgrade</A>
</H1>
The previous section presented a simple example of how Oriya language support
could be added to a C program. Like all programs, we might now wish to further
enhance it. For example, we could include a greeting to the user by adding
another <TT>printf</TT> statement after the first one. Our new hello.c source
code might look like this:
<PRE>
1 #include &lt;libintl.h&gt;
2 #include &lt;locale.h&gt;
3 #include &lt;stdio.h&gt;
4 #include &lt;stdlib.h&gt;
5 int main(void)
6 {
7 setlocale( LC_ALL, "" );
8 bindtextdomain( "hello", "/usr/share/locale" );
9 textdomain( "hello" );
10 printf( gettext( "Hello, world!\n" ) );
11 printf( gettext( "How are you\n" ) );
12 exit(0);
13 }
</PRE>
For such a small change, it would be simple enough to just repeat the above
cycle of extracting the relevant English text, translating it to Oriya, and
preparing a new message catalog. We can even simplify the work by cutting and
pasting most of the old oriya.po file into the new one. However, real programs
will have thousands of such strings, and we would like to be able to translate
only the changed strings, and have the <TT>gettext</TT> utilities handle the drudgery
of combining the new translations with the old ones. This is indeed possible.
<H2><A NAME="SECTION00031000000000000000">
Merging old and new translations</A>
</H2>
As before, extract the translatable strings from hello.c to a new portable
object template file, hello-new.pot, using <TT>xgettext</TT>,
<PRE><FONT color="red">
xgettext -d hello -o hello-new.pot hello.c
</FONT></PRE>
Now, we use a new program, <TT>msgmerge</TT>, to merge the existing .po file with
translations into the new template file, viz.,
<PRE><FONT color="red">
msgmerge -U oriya.po hello-new.pot
</FONT></PRE>
The -U option updates the existing
.po file, oriya.po. We could have chosen to instead create a new .po file by
using “-o <SPAN CLASS="MATH">&lt;</SPAN>filename<SPAN CLASS="MATH">&gt;</SPAN>” instead of -U. The updated .po file will still
have the old translations embedded in it, and new entries with untranslated
<TT>msgid</TT> lines. For us, the new lines in oriya.po will look like,
<PRE>
#: hello.c:11
msgid "How are you?\n"
msgstr ""
</PRE>
For the new translation, we could use, “&#x0b06;&#x0b2a;&#x0b23;
&#x0b15;&#x0b3f;&#x0b2a;&#x0b30;&#x0b3f; &#x0b05;&#x0b1b;&#x0b28;&#x0b4d;&#x0b24;&#x0b3f;?” in
place of the English phrase “How are you?” The updated oriya.po file,
including the translation might look like:
<PRE>
# Oriya translations for hello example package.
# Copyright (C) 2004 Gora Mohanty
# This file is distributed under the same license as the hello examplepackage.
# Gora Mohanty &lt;gora_mohanty@yahoo.co.in&gt;, 2004.
#
msgid ""
msgstr ""
"Project-Id-Version: oriya\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2004-06-23 14:30+0530\n"
"PO-Revision-Date: 2004-06-22 10:54+0530\n"
"Last-Translator: Gora Mohanty &lt;gora_mohanty@yahoo.co.in&gt;\n"
"Language-Team: Oriya\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: KBabel 1.3\n"
#: hello.c:10
msgid "Hello, world!\n"
msgstr "&#x0b28;&#x0b2e;&#x0b38;&#x0b4d;&#x0b15;&#x0b3e;&#x0b30;\n"
#: hello.c:11
msgid "How are you?\n"
msgstr "&#x0b06;&#x0b2a;&#x0b23; &#x0b15;&#x0b3f;&#x0b2a;&#x0b30;&#x0b3f; &#x0b05;&#x0b1b;&#x0b28;&#x0b4d;&#x0b24;&#x0b3f;?\n"
</PRE>
<P>
Compile oriya.po to a machine object file, and install in the appropriate
place as in Sec.&nbsp;<A HREF="#sec:catalog">2.4</A>. Thus,
<PRE><FONT color="red">
msgfmt -c -v -o hello.mo oriya.po
mkdir -p /usr/share/locale/or_IN/LC_MESSAGES
cp hello.mo /usr/share/locale/or_IN/LC_MESSAGES
</FONT></PRE>
You can test the Oriya output as above, after recompiling hello.c and running
it in an Oriya locale.
<P>
<H1><A NAME="SECTION00040000000000000000">
More about <TT>gettext</TT> </A>
</H1>
The GNU <TT>gettext</TT> info pages provide a well-organized and complete description
of the <TT>gettext</TT> utilities and their usage for enabling Native Language
Support. One should, at the very least, read the introductory material at
gettext::Introduction::, and the suggested references in
gettext::Conclusion::References::. Besides the <TT>gettext</TT> utilities described in
this document, various other programs to manipulate .po files are discussed in
gettext:Manipulating::. Finally, support for programming languages other than
C/C++ is discussed in gettext::Programming Languages::.
<P>
<H1><A NAME="SECTION00050000000000000000">
The work of translation</A>
</H1>
Besides the obvious program message strings that have been the sole focus of
our discussion here, there are many other things that require translation,
including GUI messages, command-line option strings, configuration files,
program documentation, etc. Besides these obvious aspects, there are a
significant number of programs and/or scripts that are automatically generated
by other programs. These generated programs might also themselves require
translation. So, in any effort to provide support for a given native language,
carrying out the translation and keeping up with program updates becomes a
major part of the undertaking, requiring a continuing commitment from the
language team. A plan has been outlined for the Oriya localization
project&nbsp;[<A
HREF="memo.html#url:oriya-trans-plan">2</A>].
<P>
<H1><A NAME="SECTION00060000000000000000">
Acknowledgments</A>
</H1>
Extensive use has obviously been made of the GNU <TT>gettext</TT> manual in preparing
this document. I have also been helped by an article in the Linux
Journal&nbsp;[<A
HREF="memo.html#url:lj-translation">3</A>].
<P>
This work is part of the project for enabling the use of Oriya under Linux. I
thank my uncle, N.&nbsp;M.&nbsp;Pattnaik, for conceiving of the project. We have all
benefited from the discussions amidst the group of people working on this
project. On the particular issue of translation, the help of H.&nbsp;R.&nbsp;Pansari,
A.&nbsp;Nayak, and M.&nbsp;Chand is much appreciated.
<H1><A NAME="SECTION00070000000000000000">
The Emacs info browser</A>
</H1>
<A NAME="sec:emacs-info"></A>You can start up Emacs from the command-line by typing “emacs,” or “emacs
<SPAN CLASS="MATH">&lt;</SPAN>filename<SPAN CLASS="MATH">&gt;</SPAN>.” It can be started from the menu in some desktops, e.g., on
my GNOME desktop, it is under Main Menu <TT>-&gt;</TT> Programming <TT>-&gt;</TT>
Emacs. If you are unfamiliar with Emacs, a tutorial can be started by typing
“C-h t” in an Emacs window, or from the Help item in the menubar at the
top. Emacs makes extensive use of the Control (sometimes labelled as “CTRL”
or “CTL”) and Meta (sometimes labelled as “Edit” or “Alt”) keys. In
Emacs parlance, a hyphenated sequence, such as “C-h” means to press the
Control and ‘h’ key simultaneously, while “C-h t” would mean to press the
Control and ‘h’ key together, release them, and press the ‘t’ key. Similarly,
“M-x” is used to indicate that the Meta and ‘x’ keys should be pressed at
the same time.
<P>
The info browser can be started by typing “C-h i” in Emacs. The first time
you do this, it will briefly list some commands available inside the info
browser, and present you with a menu of major topics. Each menu item, or
cross-reference is hyperlinked to the appropriate node, and you can visit that
node either by moving the cursor to the item and pressing Enter, or by
clicking on it with the middle mouse button. To get to the <TT>gettext</TT> menu items,
you can either scroll down to the line,
<PRE>
* gettext: (gettext). GNU gettext utilities.
</PRE>
and visit that node. Or, as it is several pages down, you can locate it using
“I-search.” Type “C-s” to enter “I-search” which will then prompt you
for a string in the mini-buffer at the bottom of the window. This is an
incremental search, so that Emacs will keep moving you forward through the
buffer as you are entering your search string. If you have reached the last
occurrence of the search string in the current buffer, you will get a message
saying “Failing I-search: ...” on pressing “C-s.” At that point, press
“C-s” again to resume the search at the beginning of the buffer. Likewise,
“C-r” incrementally searches backwards from the present location.
<P>
Info nodes are listed in this document with a “::” separator, so
that one can go to the gettext::Creating::Header Entry:: by visiting the
“gettext” node from the main info menu, navigating to the “Creating”
node, and following that to the “Header Entry” node.
<P>
A stand-alone info browser, independent of Emacs, is also available on many
systems. Thus, the <TT>gettext</TT> info page can also be accessed by typing
“info gettext” in a terminal. <TT>xinfo</TT> is an X application serving as an
info browser, so that if it is installed, typing “xinfo gettext” from the
command line will open a new browser window with the <TT>gettext</TT> info page.
<P>
<H1><A NAME="SECTION00080000000000000000">
PO file editors</A>
</H1>
<A NAME="sec:pofile-editors"></A>While the <TT>yudit</TT> editor is adequate for our present purposes, and we are
planning on using that as it is platform-independent, and currently the best
at rendering Oriya. This section describes some features of some editors that
are specialized for editing PO files under Linux. This is still work in
progress, as I am in the process of trying out different editors before
settling on one. The ones considered here are: Emacs in po-mode, <TT>poedit</TT>,
<TT>kbabel</TT>, and <TT>gtranslator</TT>.
<H2><A NAME="SECTION00081000000000000000">
Emacs PO mode</A>
</H2>
Emacs should automatically enter po-mode when you load a .po file, as
indicated by “PO” in the modeline at the bottom. The window is made
read-only, so that you can edit the .po file only through special commands. A
description of Emacs po-mode can be found under the gettext::Basics info node,
or type ‘h’ or ‘?’ in a po-mode window for a list of available commands. While
I find Emacs po-mode quite restrictive, this is probably due to unfamiliarity
with it. Its main advantage is that it imposes rigid conformance to the PO
file format, and checks the file format when closing the .po file
buffer. Emacs po-mode is not useful for Oriya translation, as I know of no way
to directly enter Oriya text under Emacs.
<H2><A NAME="SECTION00082000000000000000">
poedit</A>
</H2>
XXX: in preparation.
<H2><A NAME="SECTION00083000000000000000">
KDE: the kbabel editor</A>
</H2>
<TT>kbabel</TT>&nbsp;[<A
HREF="memo.html#url:kbabel">4</A>] is a more user-friendly and configurable editor than
either of Emacs po-mode or <TT>poedit</TT>. It is integrated into KDE, and offers
extensive contextual help. Besides support for various PO file features, it
has a plugin framework for dictionaries, that allows consistency checks and
translation suggestions.
<H2><A NAME="SECTION00084000000000000000">
GNOME: the gtranslator editor</A>
</H2>
XXX: in preparation.
<H2><A NAME="SECTION00090000000000000000">
Bibliography</A>
</H2><DL COMPACT><DD><P></P><DT><A NAME="xkb-oriya-layout">1</A>
<DD>
G.&nbsp;Mohanty,
<BR>A practical primer for using Oriya under Linux, v0.3,
<BR><TT><A NAME="tex2html1"
HREF="http://oriya.sarovar.org/docs/getting_started/index.html">http://oriya.sarovar.org/docs/getting_started/index.html</A></TT>, 2004,
<BR>Sec.&nbsp;6.2 describes the xkb layouts for Oriya.
<P></P><DT><A NAME="url:oriya-trans-plan">2</A>
<DD>
G.&nbsp;Mohanty,
<BR>A plan for Oriya localization, v0.1,
<BR><TT><A NAME="tex2html2"
HREF="http://oriya.sarovar.org/docs/translation_plan/index.html">http://oriya.sarovar.org/docs/translation_plan/index.html</A></TT>,
2004.
<P></P><DT><A NAME="url:lj-translation">3</A>
<DD>
Linux Journal article on internationalization,
<BR><TT><A NAME="tex2html3"
HREF="https://www.linuxjournal.com/article/3023">https://www.linuxjournal.com/article/3023</A></TT>.
<P></P><DT><A NAME="url:kbabel">4</A>
<DD>
Features of the kbabel editor,
<BR><TT><A NAME="tex2html4"
HREF="http://i18n.kde.org/tools/kbabel/features.html">http://i18n.kde.org/tools/kbabel/features.html</A></TT>.
</DL>
<H1><A NAME="SECTION000100000000000000000">
About this document ...</A>
</H1>
<STRONG>A tutorial on Native Language Support using GNU gettext</STRONG><P>
This document was generated using the
<A HREF="http://www.latex2html.org/"><STRONG>LaTeX</STRONG>2<tt>HTML</tt></A> translator Version 2002-2-1 (1.70)
<P>
Copyright &#169; 1993, 1994, 1995, 1996,
<A HREF="http://cbl.leeds.ac.uk/nikos/personal.html">Nikos Drakos</A>,
Computer Based Learning Unit, University of Leeds.
<BR>Copyright &#169; 1997, 1998, 1999,
<A HREF="http://www.maths.mq.edu.au/~ross/">Ross Moore</A>,
Mathematics Department, Macquarie University, Sydney.
<P>
The command line arguments were: <BR>
<STRONG>latex2html</STRONG> <TT>-no_math -html_version 4.0,math,unicode,i18n,tables -split 0 memo</TT>
<P>
The translation was initiated by Gora Mohanty on 2004-07-24
<DIV CLASS="navigation"><HR>
<!--Navigation Panel
<IMG WIDTH="81" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next_inactive"
SRC="file:/usr/share/latex2html/icons/nx_grp_g.png">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up"
SRC="file:/usr/share/latex2html/icons/up_g.png">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous"
SRC="file:/usr/share/latex2html/icons/prev_g.png">
<BR></DIV>
End of Navigation Panel-->
<ADDRESS>
Gora Mohanty
2004-07-24
</ADDRESS>
</BODY>
</HTML>