diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/INSTALL b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/INSTALL new file mode 100644 index 0000000000000000000000000000000000000000..4797fdff83866d880da2b4dc78ffbcb3a18f695d --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/INSTALL @@ -0,0 +1,12 @@ +This example relies on: + - Tk (wish and libtk) + - Tcl (tclsh and libtcl) + +Installation: + ./autogen.sh + ./configure --prefix=/some/prefix + make + make install +Cleanup: + make distclean + ./autoclean.sh diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/Makefile.am b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/Makefile.am new file mode 100644 index 0000000000000000000000000000000000000000..b76e71d94a2fe75afa8bf3b55bef12edf344ed34 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/Makefile.am @@ -0,0 +1,17 @@ +# Example for use of GNU gettext. +# This file is in the public domain. +# +# Makefile configuration - processed by automake. + +# General automake options. +AUTOMAKE_OPTIONS = foreign +ACLOCAL_AMFLAGS = -I m4 + +# The list of subdirectories containing Makefiles. +SUBDIRS = m4 po + +# The list of programs that are built. +bin_SCRIPTS = hello + +# Additional files to be distributed. +EXTRA_DIST = autogen.sh autoclean.sh diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/autoclean.sh b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/autoclean.sh new file mode 100644 index 0000000000000000000000000000000000000000..6f5fa67d4e91a07146b82aa11acf28ff8ce0e205 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/autoclean.sh @@ -0,0 +1,30 @@ +#!/bin/sh +# Example for use of GNU gettext. +# This file is in the public domain. +# +# Script for cleaning all autogenerated files. + +test ! -f Makefile || make distclean +rm -rf autom4te.cache + +# Brought in by explicit copy. +rm -f m4/nls.m4 +rm -f m4/po.m4 +rm -f m4/progtest.m4 +rm -f po/remove-potcdate.sed + +# Generated by aclocal. +rm -f aclocal.m4 + +# Generated by autoconf. +rm -f configure + +# Generated or brought in by automake. +rm -f Makefile.in +rm -f m4/Makefile.in +rm -f po/Makefile.in +rm -f install-sh +rm -f missing +rm -f po/*.pot +rm -f po/stamp-po +rm -f po/*.msg diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/autogen.sh b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/autogen.sh new file mode 100644 index 0000000000000000000000000000000000000000..98187f3b21038db0c74e6b8ec9e289695adae7b7 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/autogen.sh @@ -0,0 +1,44 @@ +#!/bin/sh +# Example for use of GNU gettext. +# This file is in the public domain. +# +# Script for regenerating all autogenerated files. + +if test -r ../Makefile.am; then + # Inside the gettext source directory. + GETTEXT_TOPSRCDIR=../../.. +else + if test -r ../Makefile; then + # Inside a gettext build directory. + GETTEXT_TOOLS_SRCDIR=`sed -n -e 's,^top_srcdir *= *\(.*\)$,\1,p' ../Makefile` + # Adjust a relative top_srcdir. + case $GETTEXT_TOOLS_SRCDIR in + /*) ;; + *) GETTEXT_TOOLS_SRCDIR=../$GETTEXT_TOOLS_SRCDIR ;; + esac + GETTEXT_TOPSRCDIR=$GETTEXT_TOOLS_SRCDIR/../.. + else + # Installed under ${prefix}/share/doc/gettext/examples. + . ../installpaths + fi +fi + +cp -p ${ACLOCALDIR-$GETTEXT_TOPSRCDIR/gettext-runtime/m4}/nls.m4 m4/nls.m4 +cp -p ${ACLOCALDIR-$GETTEXT_TOPSRCDIR/gettext-runtime/m4}/po.m4 m4/po.m4 +cp -p ${ACLOCALDIR-$GETTEXT_TOPSRCDIR/gettext-runtime/m4}/progtest.m4 m4/progtest.m4 +cp -p ${GETTEXTSRCPODIR-$GETTEXT_TOPSRCDIR/gettext-runtime/po}/remove-potcdate.sed po/remove-potcdate.sed + +aclocal -I m4 + +autoconf + +automake -a -c + +cd po +for f in *.po; do + if test -r "$f"; then + lang=`echo $f | sed -e 's,\.po$,,'` + msgfmt -c --tcl -d . -l $lang $lang.po + fi +done +cd .. diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/configure.ac b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/configure.ac new file mode 100644 index 0000000000000000000000000000000000000000..7d95739dee3b2a1d810b0e58ecbf518f5fef696a --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/configure.ac @@ -0,0 +1,44 @@ +dnl Example for use of GNU gettext. +dnl This file is in the public domain. +dnl +dnl Configuration file - processed by autoconf. + +AC_INIT([hello-tcl-tk], [0]) +AC_CONFIG_SRCDIR([hello.tcl]) +AM_INIT_AUTOMAKE([1.11]) + +dnl Check for availability of the Tcl/Tk interpreter. +AC_PATH_PROG([WISH], [wish]) +if test -z "$WISH"; then + echo "*** Essential program wish not found" 1>&2 + exit 1 +fi +AC_SUBST([WISH]) + +dnl The installed program must know where to find its message catalogs. +dnl Unfortunately, prefix gets only finally determined at the end of configure. +if test "X$prefix" = "XNONE"; then + final_prefix="$ac_default_prefix" +else + final_prefix="$prefix" +fi +save_prefix="$prefix" +prefix="$final_prefix" +save_datarootdir="$datarootdir" +eval "datarootdir=\"${datarootdir}\"" +save_datadir="$datadir" +eval "datadir=\"${datadir}\"" +pkgdatadir="${datadir}/${PACKAGE}" +datadir="$save_datadir" +datarootdir="$save_datarootdir" +prefix="$save_prefix" +AC_SUBST([pkgdatadir]) + +dnl Support for the po directory. +AM_PO_SUBDIRS + +AC_CONFIG_FILES([Makefile]) +AC_CONFIG_FILES([hello:hello.tcl], [chmod a+x hello]) +AC_CONFIG_FILES([m4/Makefile]) +AC_CONFIG_FILES([po/Makefile], [AM_POSTPROCESS_PO_MAKEFILE]) +AC_OUTPUT diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/hello.tcl b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/hello.tcl new file mode 100644 index 0000000000000000000000000000000000000000..4dfee53a084fb0818c2c19e66e4fab031f7d25b3 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/hello.tcl @@ -0,0 +1,19 @@ +#!@WISH@ +# Example for use of GNU gettext. +# This file is in the public domain. +# +# Source code of the Tcl/Tk program. + +package require msgcat +::msgcat::mcload [file join "@pkgdatadir@" "msgs"] +proc _ {s} {return [::msgcat::mc $s]} + +frame .my +button .my.button \ + -text [_ "Hello, world!"] \ + -command exit +label .my.label \ + -text [format [_ "This program is running as process number %d."] [pid]] +pack .my.button -side top +pack .my.label -side bottom +pack .my diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/m4/Makefile.am b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/m4/Makefile.am new file mode 100644 index 0000000000000000000000000000000000000000..8a841b31f12ff3bd59428fbba049f50825d91510 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/m4/Makefile.am @@ -0,0 +1,2 @@ +EXTRA_DIST = \ + nls.m4 po.m4 diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/LINGUAS b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/LINGUAS new file mode 100644 index 0000000000000000000000000000000000000000..dc4a82afbad945018082c22f2061a43ef436dd68 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/LINGUAS @@ -0,0 +1,5 @@ +# Example for use of GNU gettext. +# This file is in the public domain. +# +# Set of available languages. +af ast bg ca cs da de el eo es fi fr ga gl hr hu id it ja ka ky lv ms mt nb nl nn pl pt pt_BR ro ru sk sl sq sr sv ta tr uk vi zh_CN zh_HK zh_TW diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/Makefile.am b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/Makefile.am new file mode 100644 index 0000000000000000000000000000000000000000..1f123a933b34025f18c9e2b00be6154f5e66b12f --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/Makefile.am @@ -0,0 +1,367 @@ +# Example for use of GNU gettext. +# This file is in the public domain. +# +# Makefile configuration - processed by automake. + +# List of files which contain translatable strings. +POTFILES = \ + hello.tcl + +# Usually the message domain is the same as the package name. +DOMAIN = $(PACKAGE) + +# These options get passed to xgettext. +XGETTEXT_OPTIONS = --keyword=_ --flag=_:1:pass-tcl-format + +# This is the copyright holder that gets inserted into the header of the +# $(DOMAIN).pot file. Set this to the copyright holder of the surrounding +# package. (Note that the msgid strings, extracted from the package's +# sources, belong to the copyright holder of the package.) Translators are +# expected to transfer the copyright for their translations to this person +# or entity, or to disclaim their copyright. The empty string stands for +# the public domain; in this case the translators are expected to disclaim +# their copyright. +COPYRIGHT_HOLDER = Yoyodyne, Inc. + +# This tells whether or not to prepend "GNU " prefix to the package +# name that gets inserted into the header of the $(DOMAIN).pot file. +# Possible values are "yes", "no", or empty. If it is empty, try to +# detect it automatically by scanning the files in $(top_srcdir) for +# "GNU packagename" string. +PACKAGE_GNU = no + +# This is the email address or URL to which the translators shall report +# bugs in the untranslated strings: +# - Strings which are not entire sentences, see the maintainer guidelines +# in the GNU gettext documentation, section 'Preparing Strings'. +# - Strings which use unclear terms or require additional context to be +# understood. +# - Strings which make invalid assumptions about notation of date, time or +# money. +# - Pluralisation problems. +# - Incorrect English spelling. +# - Incorrect formatting. +# It can be your email address, or a mailing list address where translators +# can write to without being subscribed, or the URL of a web page through +# which the translators can contact you. +MSGID_BUGS_ADDRESS = bug-gettext@gnu.org + +# These options get passed to msgmerge. +# Useful options are in particular: +# --previous to keep previous msgids of translated messages +MSGMERGE_OPTIONS = + +# These options get passed to msginit. +# If you want to disable line wrapping when writing PO files, add +# --no-wrap to MSGMERGE_OPTIONS, XGETTEXT_OPTIONS, and +# MSGINIT_OPTIONS. +MSGINIT_OPTIONS = + +MSGMERGE = @MSGMERGE@ +MSGMERGE_UPDATE = @MSGMERGE@ --update +MSGMERGE_FOR_MSGFMT_OPTION = @MSGMERGE_FOR_MSGFMT_OPTION@ +MSGINIT = msginit +MSGCONV = msgconv +MSGFILTER = msgfilter + +# This is computed as $(foreach file, $(POTFILES), $(top_srcdir)/$(file)) +POTFILES_DEPS != for file in $(POTFILES); do echo $(top_srcdir)/$$file; done + +# The set of available translations. +ALL_LINGUAS != if test -f $(srcdir)/LINGUAS; then \ + sed -e '/^\#/d' < $(srcdir)/LINGUAS; \ + else \ + echo $(LINGUAS); \ + fi +# This is computed as $(foreach lang, $(ALL_LINGUAS), $(srcdir)/$(lang).po) +POFILES != for lang in $(ALL_LINGUAS); do echo $(srcdir)/$$lang.po; done +# This is computed as $(foreach lang, $(ALL_LINGUAS), $(lang).po-update) +UPDATEPOFILES != for lang in $(ALL_LINGUAS); do echo $$lang.po-update; done +# This is computed as $(foreach lang, $(ALL_LINGUAS), $(lang).nop) +DUMMYPOFILES != for lang in $(ALL_LINGUAS); do echo $$lang.nop; done +# This is computed as $(foreach lang, $(ALL_LINGUAS), $(srcdir)/$(frob $(lang)).msg) +# It also creates the .tcl-rules file. +MSGFILES != tab=`printf '\t'`; \ + for lang in $(ALL_LINGUAS); do \ + frobbedlang=`echo $$lang | sed -e 's/\..*$$//' -e 'y/ABCDEFGHIJKLMNOPQRSTUVWXYZ/abcdefghijklmnopqrstuvwxyz/'`; \ + echo 1>&3 "$$frobbedlang.msg: $$lang.po"; \ + echo 1>&3 "$${tab}@echo \"\$$(MSGFMT) -c --tcl -d \$$(srcdir) -l $$lang \$$(srcdir)/$$lang.po\"; \\"; \ + echo 1>&3 "$${tab}\$$(MSGFMT) -c --tcl -d \"\$$(srcdir)\" -l $$lang \$$(srcdir)/$$lang.po || { rm -f \"\$$(srcdir)/$$frobbedlang.msg\"; exit 1; }"; \ + echo $(srcdir)/$$frobbedlang.msg; \ + done 3> .tcl-rules +# Include the generated rules that cannot be formulated as a simple rule. +-include .tcl-rules + +# The set of desired translations, as specified by the installer or distributor. +DESIRED_LINGUAS = @DESIRED_LINGUAS@ +# The set of translations to install. This is computed based on $(ALL_LINGUAS) +# and $(DESIRED_LINGUAS). It is a subset of $(ALL_LINGUAS). +# We use the presentlang catalog if desiredlang is +# a. equal to presentlang, or +# b. a variant of presentlang (because in this case, presentlang can be used +# as a fallback for messages which are not translated in the desiredlang +# catalog). +INST_LINGUAS != for presentlang in $(ALL_LINGUAS); do \ + useit=false; \ + for desiredlang in $(DESIRED_LINGUAS); do \ + case "$$desiredlang" in \ + "$$presentlang" | "$$presentlang"_* | "$$presentlang".* | "$$presentlang"@*) \ + useit=true ;; \ + esac; \ + done; \ + if $$useit; then echo $$presentlang; fi; \ + done +# This is computed as $(foreach lang, $(INST_LINGUAS), $(frob $(lang)).msg) +CATALOGS != for lang in $(INST_LINGUAS); do \ + frobbedlang=`echo $$lang | sed -e 's/\..*$$//' -e 'y/ABCDEFGHIJKLMNOPQRSTUVWXYZ/abcdefghijklmnopqrstuvwxyz/'`; \ + echo $$frobbedlang.gmo; \ + done + +SUFFIXES = .nop .po-create .po-update + +# The .pot file, stamp-po, .po files, and .msg files appear in release tarballs. +# The GNU Coding Standards say in +# : +# "GNU distributions usually contain some files which are not source files +# ... . Since these files normally appear in the source directory, they +# should always appear in the source directory, not in the build directory. +# So Makefile rules to update them should put the updated files in the +# source directory." +# Therefore we put these files in the source directory, not the build directory. + + +all-local: all-local-@USE_NLS@ + +all-local-yes: $(srcdir)/stamp-po +all-local-no: + +# $(srcdir)/$(DOMAIN).pot is only created when needed. When xgettext finds no +# internationalized messages, no $(srcdir)/$(DOMAIN).pot is created (because +# we don't want to bother translators with empty POT files). We assume that +# LINGUAS is empty in this case, i.e. $(POFILES) and $(MSGFILES) are empty. +# In this case, $(srcdir)/stamp-po is a nop (i.e. a phony target). + +# $(srcdir)/stamp-po is a timestamp denoting the last time at which the CATALOGS +# have been loosely updated. Its purpose is that when a developer or translator +# checks out the package from a version control system, and the $(DOMAIN).pot +# file is not under version control, "make" will update the $(DOMAIN).pot and +# the $(CATALOGS), but subsequent invocations of "make" will do nothing. This +# timestamp would not be necessary if updating the $(CATALOGS) would always +# touch them; however, the rule for $(POFILES) has been designed to not touch +# files that don't need to be changed. +$(srcdir)/stamp-po: $(srcdir)/$(DOMAIN).pot + test ! -f $(srcdir)/$(DOMAIN).pot || \ + test -z "$(MSGFILES)" || $(MAKE) $(MSGFILES) + @test ! -f $(srcdir)/$(DOMAIN).pot || { \ + echo "touch $(srcdir)/stamp-po" && \ + echo timestamp > $(srcdir)/stamp-poT && \ + mv $(srcdir)/stamp-poT $(srcdir)/stamp-po; \ + } + +# This target rebuilds $(DOMAIN).pot; it is an expensive operation. +# Note that $(DOMAIN).pot is not touched if it doesn't need to be changed. +# The determination of whether the package xyz is a GNU one is based on the +# heuristic whether some file in the top level directory mentions "GNU xyz". +# If GNU 'find' is available, we avoid grepping through monster files. +$(DOMAIN).pot-update: $(POTFILES_DEPS) + package_gnu="$(PACKAGE_GNU)"; \ + test -n "$$package_gnu" || { \ + if { if (LC_ALL=C find --version) 2>/dev/null | grep GNU >/dev/null; then \ + LC_ALL=C find -L $(top_srcdir) -maxdepth 1 -type f -size -10000000c -exec grep -i 'GNU $(PACKAGE)' /dev/null '{}' ';' 2>/dev/null; \ + else \ + LC_ALL=C grep -i 'GNU $(PACKAGE)' $(top_srcdir)/* 2>/dev/null; \ + fi; \ + } | grep -v 'libtool:' >/dev/null; then \ + package_gnu=yes; \ + else \ + package_gnu=no; \ + fi; \ + }; \ + if test "$$package_gnu" = "yes"; then \ + package_prefix='GNU '; \ + else \ + package_prefix=''; \ + fi; \ + if test -n '$(MSGID_BUGS_ADDRESS)'; then \ + msgid_bugs_address='$(MSGID_BUGS_ADDRESS)'; \ + else \ + msgid_bugs_address='$(PACKAGE_BUGREPORT)'; \ + fi; \ + case `$(XGETTEXT) --version | sed 1q | sed -e 's,^[^0-9]*,,'` in \ + '' | 0.[0-9] | 0.[0-9].* | 0.1[0-5] | 0.1[0-5].* | 0.16 | 0.16.[0-1]*) \ + $(XGETTEXT) --default-domain=$(DOMAIN) --directory=$(top_srcdir) \ + --add-comments=TRANSLATORS: \ + --copyright-holder='$(COPYRIGHT_HOLDER)' \ + --msgid-bugs-address="$$msgid_bugs_address" \ + $(XGETTEXT_OPTIONS) @XGETTEXT_EXTRA_OPTIONS@ \ + $(POTFILES) \ + ;; \ + *) \ + $(XGETTEXT) --default-domain=$(DOMAIN) --directory=$(top_srcdir) \ + --add-comments=TRANSLATORS: \ + --copyright-holder='$(COPYRIGHT_HOLDER)' \ + --package-name="$${package_prefix}$(PACKAGE)" \ + --package-version='$(VERSION)' \ + --msgid-bugs-address="$$msgid_bugs_address" \ + $(XGETTEXT_OPTIONS) @XGETTEXT_EXTRA_OPTIONS@ \ + $(POTFILES) \ + ;; \ + esac + test ! -f $(DOMAIN).po || { \ + if test -f $(srcdir)/$(DOMAIN).pot-header; then \ + sed -e '1,/^#$$/d' < $(DOMAIN).po > $(DOMAIN).1po && \ + cat $(srcdir)/$(DOMAIN).pot-header $(DOMAIN).1po > $(DOMAIN).po && \ + rm -f $(DOMAIN).1po \ + || exit 1; \ + fi; \ + if test -f $(srcdir)/$(DOMAIN).pot; then \ + sed -f $(srcdir)/remove-potcdate.sed < $(srcdir)/$(DOMAIN).pot > $(DOMAIN).1po && \ + sed -f $(srcdir)/remove-potcdate.sed < $(DOMAIN).po > $(DOMAIN).2po && \ + if cmp $(DOMAIN).1po $(DOMAIN).2po >/dev/null 2>&1; then \ + rm -f $(DOMAIN).1po $(DOMAIN).2po $(DOMAIN).po; \ + else \ + rm -f $(DOMAIN).1po $(DOMAIN).2po $(srcdir)/$(DOMAIN).pot && \ + mv $(DOMAIN).po $(srcdir)/$(DOMAIN).pot; \ + fi; \ + else \ + mv $(DOMAIN).po $(srcdir)/$(DOMAIN).pot; \ + fi; \ + } + +# This rule has no dependencies: we don't need to update $(DOMAIN).pot at +# every "make" invocation, only create it when it is missing. +# Only "make $(DOMAIN).pot-update" or "make dist" will force an update. +$(srcdir)/$(DOMAIN).pot: + $(MAKE) $(DOMAIN).pot-update + +# This target rebuilds a PO file if $(DOMAIN).pot has changed. +# Note that a PO file is not touched if it doesn't need to be changed. +$(POFILES): $(srcdir)/$(DOMAIN).pot + @lang=`echo $@ | sed -e 's,.*/,,' -e 's/\.po$$//'`; \ + if test -f "$(srcdir)/$${lang}.po"; then \ + test "$(srcdir)" = . && cdcmd="" || cdcmd="cd $(srcdir) && "; \ + echo "$${cdcmd}$(MSGMERGE_UPDATE) --quiet $(MSGMERGE_OPTIONS) --lang=$${lang} --previous $${lang}.po $(DOMAIN).pot"; \ + cd $(srcdir) \ + && { case `$(MSGMERGE_UPDATE) --version | sed 1q | sed -e 's,^[^0-9]*,,'` in \ + '' | 0.[0-9] | 0.[0-9].* | 0.10 | 0.10.*) \ + $(MSGMERGE_UPDATE) $(MSGMERGE_OPTIONS) $${lang}.po $(DOMAIN).pot;; \ + 0.1[1-5] | 0.1[1-5].*) \ + $(MSGMERGE_UPDATE) --quiet $(MSGMERGE_OPTIONS) $${lang}.po $(DOMAIN).pot;; \ + 0.1[6-7] | 0.1[6-7].*) \ + $(MSGMERGE_UPDATE) --quiet $(MSGMERGE_OPTIONS) --previous $${lang}.po $(DOMAIN).pot;; \ + *) \ + $(MSGMERGE_UPDATE) --quiet $(MSGMERGE_OPTIONS) --lang=$${lang} --previous $${lang}.po $(DOMAIN).pot;; \ + esac; \ + }; \ + else \ + $(MAKE) $${lang}.po-create; \ + fi + + +install-data-local: install-data-local-@USE_NLS@ +install-data-local-no: all-local +install-data-local-yes: all-local + $(MKDIR_P) $(DESTDIR)$(pkgdatadir)/msgs + @catalogs='$(CATALOGS)'; \ + for cat in $$catalogs; do \ + cat=`basename $$cat`; \ + if test -r $$cat; then realcat=$$cat; else realcat=$(srcdir)/$$cat; fi; \ + $(INSTALL_DATA) $$realcat $(DESTDIR)$(pkgdatadir)/msgs/$$cat; \ + echo "installing $$realcat as $(DESTDIR)$(pkgdatadir)/msgs/$$cat"; \ + done + +installdirs-local: installdirs-local-@USE_NLS@ +installdirs-local-no: +installdirs-local-yes: + $(MKDIR_P) $(DESTDIR)$(pkgdatadir)/msgs + +uninstall-local: uninstall-local-@USE_NLS@ +uninstall-local-no: +uninstall-local-yes: + catalogs='$(CATALOGS)'; \ + for cat in $$catalogs; do \ + cat=`basename $$cat`; \ + rm -f $(DESTDIR)$(pkgdatadir)/msgs/$$cat; \ + done + +html ID: + +DISTCLEANFILES = .tcl-rules + +MOSTLYCLEANFILES = +MOSTLYCLEANFILES += stamp-poT +MOSTLYCLEANFILES += core core.* *.stackdump $(DOMAIN).po $(DOMAIN).1po $(DOMAIN).2po *.new.po +MOSTLYCLEANFILES += *.o + +MAINTAINERCLEANFILES = $(DOMAIN).pot stamp-po $(MSGFILES) + +EXTRA_DIST = remove-potcdate.sed LINGUAS $(POFILES) $(MSGFILES) + +# Hidden from automake, but really activated. Works around an automake-1.5 bug. +#distdir: distdir1 +distdir1: + $(MAKE) update-po + $(MAKE) $(srcdir)/stamp-po + @if test -f $(srcdir)/$(DOMAIN).pot; then \ + for file in $(DOMAIN).pot stamp-po; do \ + if test -f $$file; then d=.; else d=$(srcdir); fi; \ + cp -p $$d/$$file $(distdir)/$$file || exit 1; \ + done; \ + else \ + case $(XGETTEXT) in \ + :) echo "Warning: Creating a tarball without '$(DOMAIN).pot', because a suitable 'xgettext' program was not found in PATH." 1>&2;; \ + *) echo "Warning: Creating a tarball without '$(DOMAIN).pot', because 'xgettext' found no strings to extract. Check the POTFILES and the XGETTEXT_OPTIONS in the Makefile.am file." 1>&2;; \ + esac; \ + fi + +update-po: Makefile + $(MAKE) $(DOMAIN).pot-update + test -z "$(UPDATEPOFILES)" || $(MAKE) $(UPDATEPOFILES) + $(MAKE) update-msg + +# General rule for creating PO files. + +.nop.po-create: + @lang=`echo $@ | sed -e 's/\.po-create$$//'`; \ + echo "File $$lang.po does not exist. If you are a translator, you can create it through 'msginit'." 1>&2; \ + exit 1 + +# General rule for updating PO files. + +.nop.po-update: + @lang=`echo $@ | sed -e 's/\.po-update$$//'`; \ + tmpdir=`pwd`; \ + echo "$$lang:"; \ + test "$(srcdir)" = . && cdcmd="" || cdcmd="cd $(srcdir) && "; \ + echo "$${cdcmd}$(MSGMERGE) --quiet $(MSGMERGE_OPTIONS) --lang=$$lang --previous $$lang.po $(DOMAIN).pot -o $$lang.new.po"; \ + cd $(srcdir); \ + if { case `$(MSGMERGE) --version | sed 1q | sed -e 's,^[^0-9]*,,'` in \ + '' | 0.[0-9] | 0.[0-9].* | 0.10 | 0.10.*) \ + $(MSGMERGE) $(MSGMERGE_OPTIONS) -o $$tmpdir/$$lang.new.po $$lang.po $(DOMAIN).pot;; \ + 0.1[1-5] | 0.1[1-5].*) \ + $(MSGMERGE) --quiet $(MSGMERGE_OPTIONS) -o $$tmpdir/$$lang.new.po $$lang.po $(DOMAIN).pot;; \ + 0.1[6-7] | 0.1[6-7].*) \ + $(MSGMERGE) --quiet $(MSGMERGE_OPTIONS) --previous -o $$tmpdir/$$lang.new.po $$lang.po $(DOMAIN).pot;; \ + *) \ + $(MSGMERGE) --quiet $(MSGMERGE_OPTIONS) --lang=$$lang --previous -o $$tmpdir/$$lang.new.po $$lang.po $(DOMAIN).pot;; \ + esac; \ + }; then \ + if cmp $$lang.po $$tmpdir/$$lang.new.po >/dev/null 2>&1; then \ + rm -f $$tmpdir/$$lang.new.po; \ + else \ + if mv -f $$tmpdir/$$lang.new.po $$lang.po; then \ + :; \ + else \ + echo "msgmerge for $$lang.po failed: cannot move $$tmpdir/$$lang.new.po to $$lang.po" 1>&2; \ + exit 1; \ + fi; \ + fi; \ + else \ + echo "msgmerge for $$lang.po failed!" 1>&2; \ + rm -f $$tmpdir/$$lang.new.po; \ + fi + +$(DUMMYPOFILES): + +update-msg: Makefile $(MSGFILES) + @: diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/af.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/af.po new file mode 100644 index 0000000000000000000000000000000000000000..54cd61067ff09f169d7113bc70aff21883b09630 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/af.po @@ -0,0 +1,26 @@ +# Afrikaans translation for Silky +# Copyright (C) 2004 Free Software Foundation, Inc. +# This file is distributed under the same license as the silky package. +# Hanlie Pretorius , 2004. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk-0.13.1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2003-12-31 10:30+2\n" +"Last-Translator: Ysbeer \n" +"Language-Team: Afrikaans \n" +"Language: af\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Hallo wêreld!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Hierdie program loop as prosesnommer %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/ast.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/ast.po new file mode 100644 index 0000000000000000000000000000000000000000..8ae95df3a47811bbe7e35ce22439e1ddc31b46f2 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/ast.po @@ -0,0 +1,29 @@ +# Asturian translation for hello-tcl-tk +# Copyright (C) 2018 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Marquinos , 2009. +# enolp , 2018. +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk 0.19.4.73\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2018-07-16 00:28+0100\n" +"Last-Translator: enolp \n" +"Language-Team: Asturian \n" +"Language: ast\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=n != 1;\n" +"X-Generator: Lokalize 2.0\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "¡Hola, mundu!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Esti programa ta executándose como procesu númberu %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/bg.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/bg.po new file mode 100644 index 0000000000000000000000000000000000000000..9547624bcd5d2f41ee9e6cad48e4312eecfd09ea --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/bg.po @@ -0,0 +1,26 @@ +# Bulgarian translations for hello-tcl-tk package. +# Copyright (C) 2010 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Roumen Petrov , 2010,2014,2015,2019,2023,2024.2025. +# +msgid "" +msgstr "" +"Project-Id-Version: GNU hello-tcl-tk 0.24-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-03-08 19:09+0200\n" +"Last-Translator: Roumen Petrov \n" +"Language-Team: Bulgarian \n" +"Language: bg\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Здравейте всички!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Програмата е пусната под процес номер %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/ca.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/ca.po new file mode 100644 index 0000000000000000000000000000000000000000..fd1c16f2653f844cd9acda8750bc28292401516e --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/ca.po @@ -0,0 +1,27 @@ +# Catalan messages for GNU hello-tcl-tk. +# Copyright (C) 2003, 2014, 2015 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Ivan Vilata i Balaguer , 2003, 2014, 2015, 2023. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk 0.22\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2023-07-07 08:36+0200\n" +"Last-Translator: Ivan Vilata i Balaguer \n" +"Language-Team: Catalan \n" +"Language: ca\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Hola, món!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Aquest programa està corrent amb el número de procés %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/cs.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/cs.po new file mode 100644 index 0000000000000000000000000000000000000000..79bb1126cdd97ebda7e572a3703a34a5a059d4a3 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/cs.po @@ -0,0 +1,29 @@ +# The Czech translation for the gettext package. +# Copyright (C) 2011 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Marek Černocký , 2011. +# Petr Písař , 2025. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-28 20:05+02:00\n" +"Last-Translator: Petr Pisar \n" +"Language-Team: Czech \n" +"Language: cs\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=3; plural=(n==1) ? 0 : (n>=2 && n<=4) ? 1 : 2;\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Ahoj světe!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Tento program běží jako proces číslo %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/da.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/da.po new file mode 100644 index 0000000000000000000000000000000000000000..d83982f508f8c23070786b162c8a97c73cc26bd1 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/da.po @@ -0,0 +1,28 @@ +# Danish messages for hello-tcl-tk. +# Copyright (C) 2015 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Jan Djærv , 2003, 2006. +# Keld Simonsen , 2011. +# Joe Hansen , 2015. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk 0.19.4.73\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2015-06-27 12:39+0100\n" +"Last-Translator: Joe Hansen \n" +"Language-Team: Danish \n" +"Language: da\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Hej verden!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Dette program kører som proces nummer %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/de.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/de.po new file mode 100644 index 0000000000000000000000000000000000000000..dd8c62e0742090aceacee4cf48e961f3c74cd8ec --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/de.po @@ -0,0 +1,32 @@ +# German messages for hello-tcl-tk. +# Copyright © 2003, 2013 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Bruno Haible , 2003. +# Karl Eichwalder , 2003. +# Jakob Kramer , 2013. +# Mario Blättermann , 2014, 2023, 2025. +# Philipp Thomas , 2015. +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-28 17:15+0200\n" +"Last-Translator: Mario Blättermann \n" +"Language-Team: German \n" +"Language: de\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"X-Generator: Lokalize 25.04.0\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Hallo Welt!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Dieses Programm läuft mit der Prozess-Nummer %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/el.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/el.po new file mode 100644 index 0000000000000000000000000000000000000000..bf79fd268419b49b78919c0c6c28e7c6bd15b966 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/el.po @@ -0,0 +1,26 @@ +# Greek translation of hello-tcl-tk +# Copyright (C) 2005 Free Software Foundation, Inc. +# Simos Xenitellis , 2005. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk 0.14.1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2005-01-06 18:50+0000\n" +"Last-Translator: Simos Xenitellis \n" +"Language-Team: Greek \n" +"Language: el\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: KBabel 1.3.1\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Γεια σου, κόσμε!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Αυτό το πρόγραμμα εκτελείται με αριθμό διεργασίας %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/eo.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/eo.po new file mode 100644 index 0000000000000000000000000000000000000000..432ae434af629b2c6ac769f7e72007e71f9fa40c --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/eo.po @@ -0,0 +1,28 @@ +# La teksto por la mesaĝoj de la programo "gettext". +# Copyright (C) 2006, 2016 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Edmund GRIMLEY EVANS , 2006. +# Felipe CASTRO , 2016, 2023. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk 0.22\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2023-06-23 19:00-0300\n" +"Last-Translator: Felipe Castro \n" +"Language-Team: Esperanto \n" +"Language: eo\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 2.4.2\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Saluton, mondo!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Ĉi tiu programo rulas kiel procez-numero %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/es.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/es.po new file mode 100644 index 0000000000000000000000000000000000000000..af3e2b1a197cff7eec68660387dbd0a0324d31aa --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/es.po @@ -0,0 +1,30 @@ +# Mensajes en español para GNU gettext. +# Copyright (C) 2014 Yoyodyne, Inc. (msgids) +# +# This file is distributed under the same license as the gettext package. +# +# Max de Mendizábal , 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004. +# Antonio Ceballos , 2014, 2015, 2023, 2025 +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk-0.24-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-02-23 17:01+0100\n" +"Last-Translator: Antonio Ceballos \n" +"Language-Team: Spanish \n" +"Language: es\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "¡Hola, mundo!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Este programa está corriendo como el proceso número %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/fi.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/fi.po new file mode 100644 index 0000000000000000000000000000000000000000..2f03f47ef2219d02a52c8e5c2ee0a34c06960996 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/fi.po @@ -0,0 +1,29 @@ +# Finnish messages for GNU Gettext examples. +# This file is distributed under the same license as the gettext package. +# Copyright © 2007, 2014, 2015 Yoyodyne, Inc. (msgids) +# Lauri Nurmi , 2007. +# Jorma Karvonen , 2014-2015. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk 0.19.4.73\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2015-09-01 16:59+0300\n" +"Last-Translator: Jorma Karvonen \n" +"Language-Team: Finnish \n" +"Language: fi\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 1.5.4\n" + +# Tämä nimenomainen käännös valittu GNU Hellon mukaisesti. +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Terve maailma!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Tämän ohjelman prosessinumero on %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/fr.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/fr.po new file mode 100644 index 0000000000000000000000000000000000000000..a8950698e1d2451744988e69103ce9505f3ba67d --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/fr.po @@ -0,0 +1,32 @@ +# Messages français pour GNU gettext. +# Copyright (C) 2006 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Michel Robitaille , 2006. +# Christophe Combelles , 2006 +# Stéphane Aulery , 2015 +# Christian Wiatr , 2023 +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk 0.22\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2023-06-28 16:25+0200\n" +"Last-Translator: Christian Wiatr \n" +"Language-Team: French \n" +"Language: fr\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=(n > 1);\n" +"X-Generator: Poedit 2.4.2\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Bonjour, le monde !" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Ce programme est exécuté en tant que processus numéro %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/ga.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/ga.po new file mode 100644 index 0000000000000000000000000000000000000000..ed36260d9caf6b652023914cb3380e5838cc73b5 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/ga.po @@ -0,0 +1,26 @@ +# Irish translations for hello-tcl-tk. +# Copyright (C) 2015 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Kevin Patrick Scannell , 2004, 2017. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk 0.19.4.73\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2017-01-10 12:09-0500\n" +"Last-Translator: Kevin Patrick Scannell \n" +"Language-Team: Irish \n" +"Language: ga\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Dia duit, a dhomhain!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Tá an clár seo ag rith mar phróiseas %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/gl.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/gl.po new file mode 100644 index 0000000000000000000000000000000000000000..72ff024e0f9e3496ad9b7ea04cee072c1396d48d --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/gl.po @@ -0,0 +1,31 @@ +# Galician translation for hello-tcl-tk package. +# Copyright (C) 2010 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Leandro Regueiro , 2010-2014. +# +# Proxecto Trasno - Adaptación do software libre á lingua galega: Se desexas +# colaborar connosco, podes atopar máis información en +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk 0.19-rc1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2014-05-10 16:34+0100\n" +"Last-Translator: Leandro Regueiro \n" +"Language-Team: Galician \n" +"Language: gl\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=(n!=1);\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Ola, mundo!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Este programa estase executando como o proceso número %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/hr.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/hr.po new file mode 100644 index 0000000000000000000000000000000000000000..5de6e85c3eebf7d17e1c358d9d7382b89801663d --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/hr.po @@ -0,0 +1,33 @@ +# Translation of hello-tcl-tk to Croatian. +# Copyright (C) 2003, 2004, 2014, 2015, 2019 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Permission is granted to freely copy and distribute +# this file and modified versions, provided that this +# header is not removed and modified versions are marked +# as such. +# +# Tomislav Krznar , 2012. +# Božidar Putanec , 2018-2025. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GNU hello-tcl-tk 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-28 10:15-0700\n" +"Last-Translator: Božidar Putanec \n" +"Language-Team: Croatian \n" +"Language: hr\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Pozdrav, svijete!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Ovaj program se izvršava kao proces broj %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/hu.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/hu.po new file mode 100644 index 0000000000000000000000000000000000000000..3ee94c934af8accdb2c7e4558a9da6d41e1e2353 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/hu.po @@ -0,0 +1,29 @@ +# Hungarian translation for hello-tcl-tk. +# This file is distributed under the same license as the gettext package. +# Copyright (C) 2014 Yoyodyne, Inc. (msgids) +# +# Tamás Kiss , 2005. +# Balázs Úr , 2014, 2015. +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk 0.19.4.73\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2015-06-23 20:31+0200\n" +"Last-Translator: Balázs Úr \n" +"Language-Team: Hungarian \n" +"Language: hu\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"X-Generator: Lokalize 1.2\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Hello, világ!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Ez a program a(z) %d folyamatazonosítóval fut." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/id.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/id.po new file mode 100644 index 0000000000000000000000000000000000000000..63447cccf8336cba066124c18beca3b993566e39 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/id.po @@ -0,0 +1,27 @@ +# translation of hello-tcl-tk-0.15-pre5.po to Indonesian +# Copyright (C) 2006 Yoyodyne, Inc. +# This file is distributed under the same license as the PACKAGE package. +# +# Tedi Heriyanto , 2006. +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk-0.15-pre5\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2006-09-27 20:19+0700\n" +"Last-Translator: Tedi Heriyanto \n" +"Language-Team: Indonesian \n" +"Language: id\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: KBabel 1.11.2\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Hello, world!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Program ini berjalan sebagai proses nomor %d" diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/it.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/it.po new file mode 100644 index 0000000000000000000000000000000000000000..13e2c291cae1d57eb81c6f2ae42d6ccad02fc06b --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/it.po @@ -0,0 +1,29 @@ +# Italian messages for hello-tcl-tk. +# Copyright (C) 2005, 2006 Yoyodyne, Inc. (msgids) +# Copyright (C) 2024 Free Software Foundation, Inc. +# This file is distributed under the same license as the gettext package. +# Marco Colombo , 2005, 2006, 2015. +# Michele Locati , 2024, 2025. +# +msgid "" +msgstr "" +"Project-Id-Version: GNU hello-tcl-tk 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-05-04 18:28+0200\n" +"Last-Translator: Michele Locati \n" +"Language-Team: Italian \n" +"Language: it\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Ciao, mondo!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Questo programma è in esecuzione con numero di processo %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/ja.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/ja.po new file mode 100644 index 0000000000000000000000000000000000000000..3dd2fb0cb6e101c39bede3a8cef40971bcb4202d --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/ja.po @@ -0,0 +1,26 @@ +# Translation of `hello-tcl-tk' messages to Japanese. +# Copyright (C) 2005, 2006, 2014, 2015, 2023, 2025 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Masahito Yamaga , 2025. +# +msgid "" +msgstr "" +"Project-Id-Version: GNU hello-tcl-tk 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-28 19:59+0900\n" +"Last-Translator: Masahito Yamaga \n" +"Language-Team: Japanese \n" +"Language: ja\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "世界よ, こんにちは!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "このプログラムはプロセス番号 %d で動いています." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/ka.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/ka.po new file mode 100644 index 0000000000000000000000000000000000000000..5c9f73c4e398a9bcb2e887bc1e7811d65a0a7080 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/ka.po @@ -0,0 +1,28 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2022 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Temuri Doghonadze , 2022. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk 0.20.2\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2022-05-22 05:04+0200\n" +"Last-Translator: Temuri Doghonadze \n" +"Language-Team: Georgian <(nothing)>\n" +"Language: ka\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"X-Generator: Poedit 3.0.1\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "გამარჯობა სამყაროვ!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "პროგრამა გაშვებულია პროცესის ნომრით %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/ky.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/ky.po new file mode 100644 index 0000000000000000000000000000000000000000..e382bf94643765d23c455094caf4b2ada356b59a --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/ky.po @@ -0,0 +1,28 @@ +# Translation of 'hello-tcl-tk' messages to Kirghiz. +# Copyright (C) 2004 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Ilyas Bakirov , 2007. +# Ilyas Bakirov , 2018. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk 0.19.4.73\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2018-02-15 18:26+0600\n" +"Last-Translator: Ilyas Bakirov \n" +"Language-Team: Kirghiz \n" +"Language: ky\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 2.0.6\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Салам дүйнө!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Бул программа %d процесс номери катары иштеп жатат." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/lv.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/lv.po new file mode 100644 index 0000000000000000000000000000000000000000..fa60566299bae4efbc1fe54edf6122878f63da40 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/lv.po @@ -0,0 +1,30 @@ +# Latvian translation of hello-tcl-tk +# Copyright (C) 2009 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Arvis Lācis , 2009. +# Rihards Priedītis , 2023, 2025. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk-0.24-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-03-09 11:44+0000\n" +"Last-Translator: Rihards Priedītis \n" +"Language-Team: Latvian \n" +"Language: lv\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n != 0 ? 1 : " +"2);\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 3.5\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Sveika, pasaule!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Šī programma darbojas ar procesa numuru %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/ms.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/ms.po new file mode 100644 index 0000000000000000000000000000000000000000..6cba564af4cc1f3206f8db4b508b7897e7312a85 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/ms.po @@ -0,0 +1,28 @@ +# hello-tcl-tk Bahasa Melayu (Malay) (ms). +# Copyright (C) 2006, 2015, 2023, 2025 Yoyodyne, Inc. (msgids) +# Copyright (C) 2006, 2015, 2023, 2025 Free Software Foundation, Inc. +# This file is distributed under the same license as the gettext package. +# Sharuzzaman Ahmat Raslan , 2006, 2015, 2023, 2025 +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-05-03 21:10+0800\n" +"Last-Translator: Sharuzzaman Ahmat Raslan \n" +"Language-Team: Malay \n" +"Language: ms\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 3.5\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Hello, dunia!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Program ini dilaksanakan sebagai proses bernombor %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/mt.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/mt.po new file mode 100644 index 0000000000000000000000000000000000000000..2fb6fc54551cf2c8fceef46200b9a2e99512bc2d --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/mt.po @@ -0,0 +1,27 @@ +# hello-tcl-tk-0.16.2-pre5. +# Copyright (C) 2008 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Clyde Meli , 2001-2008. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk 0.16.2-pre5\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2008-11-18 17:27+0100\n" +"Last-Translator: Clyde Meli \n" +"Language-Team: Maltese \n" +"Language: mt\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Hello, lil kulħadd!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Dal-programm qed jaħdem taħt il-proċess numru %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/nb.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/nb.po new file mode 100644 index 0000000000000000000000000000000000000000..58616853bdece6458f9f40b876b8dec9bafb444e --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/nb.po @@ -0,0 +1,29 @@ +# Norwegian Bokmal translations for hello-tcl-tk package. +# Copyright (C) 2012 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Johnny A. Solbu , 2012-2024 +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk 0.22\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2024-01-06 16:33+0100\n" +"Last-Translator: Johnny A. Solbu \n" +"Language-Team: Norwegian Bokmaal \n" +"Language: nb\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"X-Generator: Poedit 2.4.2\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Hallo verden!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Dette programmet kjører som prosess nummer %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/nl.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/nl.po new file mode 100644 index 0000000000000000000000000000000000000000..c279d19dc31e283823917248c915e81ba4e06819 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/nl.po @@ -0,0 +1,31 @@ +# Dutch translations for GNU hello-tcl-tk. +# Copyright (C) 2025 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# "There are three basic rules for writing a novel. +# Unfortunately nobody knows what they are." +# +# Benno Schulenberg , 2007, 2014, 2015, 2019, 2025. +# Elros Cyriatan , 2004. +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk-0.24-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-03-01 14:51+0100\n" +"Last-Translator: Benno Schulenberg \n" +"Language-Team: Dutch \n" +"Language: nl\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Hallo, wereld!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Dit programma draait als proces nummer %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/nn.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/nn.po new file mode 100644 index 0000000000000000000000000000000000000000..1fa402694401e791b3f4b99120aef0e033137a2e --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/nn.po @@ -0,0 +1,28 @@ +# Norwegian Nynorsk translation of GNU hello-tcl-tk +# Copyright (C) 2020 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Karl Ove Hufthammer , 2020. +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk-0.20.2\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2020-05-04 18:58+0200\n" +"Last-Translator: Karl Ove Hufthammer \n" +"Language-Team: Norwegian Nynorsk \n" +"Language: nn\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"X-Generator: Lokalize 20.04.0\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Hei, verda!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Dette programmet køyrer som prosess nummer %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/pl.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/pl.po new file mode 100644 index 0000000000000000000000000000000000000000..6615f16b4577af0a366760c6bf94dc3e6c7daff0 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/pl.po @@ -0,0 +1,27 @@ +# Polish translations for the GNU gettext messages, hello-tcl-tk domain +# Copyright (C) 2010, 2014, 2015, 2025 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Rafał Maszkowski , 2003, 2010, 2014, 2015, 2025 +msgid "" +msgstr "" +"Project-Id-Version: GNU hello-tcl-tk 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-25 17:16+0200\n" +"Last-Translator: Rafał Maszkowski \n" +"Language-Team: Polish \n" +"Language: pl\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8-bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=3; plural=(n==1 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 " +"|| n%100>=20) ? 1 : 2);\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Cześć, świecie!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Ten program działa jako proces o numerze %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/pt.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/pt.po new file mode 100644 index 0000000000000000000000000000000000000000..7a3c85e5908ab11f8c004e4285bc9057754fa5c8 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/pt.po @@ -0,0 +1,28 @@ +# Portuguese (Portugal) translation of 'hello-tcl-tk' package. +# Copyright (C) 2018 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Pedro Albuquerque , 2019, 2020, 2025. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-28 11:24+0100\n" +"Last-Translator: Pedro Albuquerque \n" +"Language-Team: Portuguese \n" +"Language: pt\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=n != 1;\\n;\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 3.6\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Olá mundo!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Este programa está em execução como processo nº %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/pt_BR.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/pt_BR.po new file mode 100644 index 0000000000000000000000000000000000000000..18f4ff78dbe98cf7a35a9f638ccfaace75d4fdec --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/pt_BR.po @@ -0,0 +1,31 @@ +# Brazilian Portuguese translations for gettext-example +# Traduções em português brasileiro para gettext-example +# Copyright (C) 2025 Yoyodyne, Inc. (msgids) +# Copyright (C) 2025 Free Software Foundation, Inc. +# This file is distributed under the same license as the gettext package. +# Rafael Fontenelle , 2013-2025. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-28 10:24-0300\n" +"Last-Translator: Rafael Fontenelle \n" +"Language-Team: Brazilian Portuguese \n" +"Language: pt_BR\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n > 1);\n" +"X-Generator: Gtranslator 48.0\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Olá, mundo!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Este programa está sendo executado com número de processo %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/ro.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/ro.po new file mode 100644 index 0000000000000000000000000000000000000000..3e35df3e90e4f5f1c2a9d6a30d715ab0407ad9d6 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/ro.po @@ -0,0 +1,50 @@ +# Translation of "hello-tcl-tk" messages to Romanian. +# Mesajele în limba română pentru pachetul hello-tcl-tk. +# Copyright © 2015, 2019, 2022, 2023, 2024, 2025 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Eugen Hoancă , 2003. +# Mihai Cristescu , 2015 - 2019. +# Remus-Gabriel Chelu , 2022 - 2025. +# +# Cronologia traducerii fișierului „hello-tcl-tk”: +# Traducerea inițială, făcută de EH, pentru versiunea hello-tcl-tk 0.12.1, 2003. +# Actualizare a traducerii pentru versiunea hello-tcl-tk 0.19.4-rc1, făcută de MC, mar-2015. +# Actualizare a traducerii pentru versiunea hello-tcl-tk 0.19.4.73, făcută de MC, iun-2015. +# Actualizare a traducerii pentru versiunea hello-tcl-tk 0.20-rc1, făcută de MC, apr-2019. +# Actualizare a mesajelor, de la fișierul „hello-tcl-tk-0.20.2.pot”. +# Actualizare a algoritmului formelor de plural (de la „trei-vechi” la „trei-actual”). +# NU și a mesajelor traduse (acestea au rămas neschimbate). +# Eliminare a mesajelor ce-au dispărut în ultima versiune. +# Actualizări realizate de Remus-Gabriel Chelu , 15.01.2022. +# Actualizare a traducerii pentru versiunea 0.20.2 făcută de R-GC, ian-2022. +# Actualizare a traducerii pentru versiunea 0.22 făcută de R-GC, iun-2023. +# Revizuire și corectare a traducerii pentru versiunea 0.23-pre1 făcută de R-GC, oct-2024. +# Actualizare a traducerii pentru versiunea 0.24-pre1 făcută de R-GC, feb-2025. +# Actualizare a traducerii pentru versiunea 0.25-pre1 făcută de R-GC, apr-2025. +# Actualizare a traducerii pentru versiunea Y, făcută de X, Z(luna-anul). +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-29 00:25+0200\n" +"Last-Translator: Remus-Gabriel Chelu \n" +"Language-Team: Romanian \n" +"Language: ro\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=3; plural=(n==1 ? 0 : (n==0 || (n%100 > 0 && n%100 < " +"20)) ? 1 : 2);\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 3.5\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Salutare, lume!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Acest program rulează ca procesul numărul %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/ru.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/ru.po new file mode 100644 index 0000000000000000000000000000000000000000..c4a8e9dab2de6cd0358e386056a29fa887dd4415 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/ru.po @@ -0,0 +1,30 @@ +# Translation of hello-tcl-tk-0.14.1.po to Russian +# Copyright (C) 2004 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Pavel Maryanov , 2004. +# SPDX-FileCopyrightText: 2014, 2015, 2023, 2025 Yuri Kozlov +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-05-02 09:17+0300\n" +"Last-Translator: Yuri Kozlov \n" +"Language-Team: Russian \n" +"Language: ru\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Lokalize 24.12.0\n" +"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && " +"n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Здравствуй, мир!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Эта программа выполняется как процесс под номером %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/sk.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/sk.po new file mode 100644 index 0000000000000000000000000000000000000000..143163efed72ce1b1780e66d93adaf79fc6cf060 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/sk.po @@ -0,0 +1,26 @@ +# Slovak translations GNU for hello-tcl-tk package. +# Copyright (C) 2003, 2004, 2014, 2023, 2025 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Marcel Telka , 2003, 2004, 2014, 2023, 2025. +# +msgid "" +msgstr "" +"Project-Id-Version: GNU hello-tcl-tk 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-28 13:53+0200\n" +"Last-Translator: Marcel Telka \n" +"Language-Team: Slovak \n" +"Language: sk\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Ahoj svet!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Tento program beží ako proces s číslom %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/sl.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/sl.po new file mode 100644 index 0000000000000000000000000000000000000000..3f45598290ccfdc3460ee2fcc853e198625bf761 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/sl.po @@ -0,0 +1,29 @@ +# -*- mode: po; coding: utf-8; -*- Slovenian message catalog for GNU gettext-example +# Copyright (C) 2005 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Primož Peterlin , 2005, 2014, 2015, 2024. +# $Id: hello-tcl-tk-0.22.sl.po,v 1.1 2024/03/28 17:02:19 peterlin Exp $ +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk 0.22\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2024-03-28 18:02+0100\n" +"Last-Translator: Primož Peterlin \n" +"Language-Team: Slovenian \n" +"Language: sl\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8-bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=4; plural=(n%100==1 ? 1 : n%100==2 ? 2 : n%100==3 || " +"n%100==4 ? 3 : 0);\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Pozdravljen, svet!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Ta program teče kot proces številka %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/sq.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/sq.po new file mode 100644 index 0000000000000000000000000000000000000000..3dc32f27cf988aa6278ae25b6625ad68b850f831 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/sq.po @@ -0,0 +1,28 @@ +# Albanian translation of gettext-example. +# Copyright (C) 2020 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Besnik Bleta , 2020,2023,2024,2025. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk-0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-28 19:56+0300\n" +"Last-Translator: Besnik Bleta \n" +"Language-Team: Albanian \n" +"Language: sq\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 3.2.2\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Tungjatjeta, botë!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Ky program po xhiron si procesi numër %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/sr.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/sr.po new file mode 100644 index 0000000000000000000000000000000000000000..6bf4701bdf0ddad42629c8284f15bc5ecb923162 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/sr.po @@ -0,0 +1,30 @@ +# Serbian translation of hello-tcl-tk. +# Copyright (C) 2014 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Aleksandar Jelenak , 2004. +# Мирослав Николић , 2014-2025. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk-0.24-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-03-02 16:51+0100\n" +"Last-Translator: Мирослав Николић \n" +"Language-Team: Serbian <(nothing)>\n" +"Language: sr\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && " +"n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 3.5\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Здраво, свима!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Овај програм се извршава као процес број %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/sv.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/sv.po new file mode 100644 index 0000000000000000000000000000000000000000..7f748f16c0b596fa4c5b7a9e43642c1a94c28f40 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/sv.po @@ -0,0 +1,30 @@ +# Swedish messages for hello-tcl-tk. +# Copyright © 2006, 2014, 2016, 2019, 2020, 2023, 2024, 2025 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Jan Djärv , 2003, 2006, 2014. +# Göran Uddeborg , 2016, 2019, 2020, 2023, 2024, 2025. +# Luna Jernberg , 2025. +# $Revision: 1.12 $ +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-28 12:18+0200\n" +"Last-Translator: Luna Jernberg \n" +"Language-Team: Swedish \n" +"Language: sv\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 3.5\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Hej världen!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Detta program kör som process nummer %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/ta.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/ta.po new file mode 100644 index 0000000000000000000000000000000000000000..e127992c42324ad99665aacffc28c984c566f8ff --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/ta.po @@ -0,0 +1,28 @@ +# Tamil messages for GNU gettext. +# Copyright (C) 2018 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# List of contributors follow: +# Poorajith , 2018. +# Arun Isaac , 2023. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk 0.22\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2023-06-19 00:06+0100\n" +"Last-Translator: Arun Isaac \n" +"Language-Team: Tamil \n" +"Language: ta\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "வணக்கம், உலகு!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "இந்நிரல் செயலாக்க எண் %d ஆக இயங்கிக்கொண்டிருக்கிறது." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/tr.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/tr.po new file mode 100644 index 0000000000000000000000000000000000000000..04d154fe26d8f21867e1bb6c7a53b13e2687b88d --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/tr.po @@ -0,0 +1,29 @@ +# Turkish translation for hello-tcl-tk. +# This file is distributed under the same license as the gettext package. +# Copyright (C) 2017 Yoyodyne, Inc. (msgids) +# Copyright (C) 2004 Free Software Foundation, Inc. +# Nilgün Belma Bugüner , 2003,2004 +# Mehmet Kececi , 2017, 2019, 2020. +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk 0.20.2\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2020-04-17 13:10+0300\n" +"Last-Translator: Mehmet Kececi \n" +"Language-Team: Turkish \n" +"Language: tr\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=1; plural=0;\n" +"X-Generator: Poedit 2.3\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Merhaba, dünya!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Bu yazılım %d işlem numarası ile çalışıyor." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/uk.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/uk.po new file mode 100644 index 0000000000000000000000000000000000000000..ba40eedf4c3576523914a2ece3293488bd5a3eb5 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/uk.po @@ -0,0 +1,30 @@ +# Ukrainian translation to hello-tcl-tk +# Copyright (C) 2014 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Maxim V. Dziumanenko , 2004-2007. +# Yuri Chornoivan , 2014, 2015, 2023, 2025. +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-28 13:56+0300\n" +"Last-Translator: Yuri Chornoivan \n" +"Language-Team: Ukrainian \n" +"Language: uk\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && " +"n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n" +"X-Generator: Lokalize 23.04.3\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Привіт, світе!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Ця програма виконується як процес з номером %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/vi.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/vi.po new file mode 100644 index 0000000000000000000000000000000000000000..6075f26127bd0b726c2596d2481ef08f8c8ff848 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/vi.po @@ -0,0 +1,30 @@ +# Vietnamese Translation for Gettext Examples. +# Bản dịch tiếng Việt dành cho các ví dụ của gói gettext. +# Copyright © 2015 Yoyodyne, Inc. (msgids) +# Copyright © 2015 Free Software Foundation, Inc. +# This file is distributed under the same license as the gettext package. +# Clytie Siddall , 2005-2010. +# Trần Ngọc Quân , 2012-2015, 2023. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk 0.22\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2023-06-24 09:10+0700\n" +"Last-Translator: Trần Ngọc Quân \n" +"Language-Team: Vietnamese \n" +"Language: vi\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=1; plural=0;\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "Chào thế giới!" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Chương trình này đang chạy với mã số tiến trình %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/zh_CN.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/zh_CN.po new file mode 100644 index 0000000000000000000000000000000000000000..f434a517e2705f157344a9b65cf75d66e4e53e51 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/zh_CN.po @@ -0,0 +1,29 @@ +# zh_CN translation for hello-tcl-tk. +# Copyright (C) 2015 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Funda Wang , 2003. +# Ji ZhengYu , 2015. +# Boyuan Yang <073plan@gmail.com>, 2019, 2023, 2025. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-29 15:56-0400\n" +"Last-Translator: Boyuan Yang <073plan@gmail.com>\n" +"Language-Team: Chinese (simplified) \n" +"Language: zh_CN\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 3.6\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "你好，世界！" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "此程序正以进程号 %d 运行。" diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/zh_HK.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/zh_HK.po new file mode 100644 index 0000000000000000000000000000000000000000..aa632d17dc364d4bf38db698ccd267844460b7be --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/zh_HK.po @@ -0,0 +1,25 @@ +# Chinese (Hong Kong) translation of hello-tcl-tk. +# Copyright (C) 2006 Yoyodyne, Inc. +# Abel Cheung , 2006. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk 0.15-pre5\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2006-07-05 15:40+0800\n" +"Last-Translator: Abel Cheung \n" +"Language-Team: Chinese (Hong Kong) \n" +"Language: zh_HK\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "你好！" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "本程式正在執行中，進程編號為 %d。" diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/zh_TW.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/zh_TW.po new file mode 100644 index 0000000000000000000000000000000000000000..5824dcc17d3715dec150c954a2561c0194ef4967 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl-tk/po/zh_TW.po @@ -0,0 +1,29 @@ +# Traditional Chinese translation of hello-tcl-tk. +# Copyright (C) 2009 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Abel Cheung , 2005. +# Wei-Lun Chao , 2013, 2015. +# Yi-Jyun Pan , 2024. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-tk 0.23-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2024-11-30 14:14+0800\n" +"Last-Translator: Yi-Jyun Pan \n" +"Language-Team: Chinese (traditional) \n" +"Language: zh_TW\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 3.5\n" + +#: hello.tcl:13 +msgid "Hello, world!" +msgstr "哈囉，大家好！" + +#: hello.tcl:16 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "本程式正在執行，行程編號為 %d。" diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/de.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/de.po new file mode 100644 index 0000000000000000000000000000000000000000..7e40cefdcfc0d4fd4bbac21e01a7755cc94ee67d --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/de.po @@ -0,0 +1,32 @@ +# German messages for hello-tcl. +# Copyright © 2003, 2013 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Bruno Haible , 2003. +# Karl Eichwalder , 2003. +# Jakob Kramer , 2013. +# Mario Blättermann , 2014, 2023, 2025. +# Philipp Thomas , 2015. +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-28 17:15+0200\n" +"Last-Translator: Mario Blättermann \n" +"Language-Team: German \n" +"Language: de\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"X-Generator: Lokalize 25.04.0\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Hallo Welt!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Dieses Programm läuft mit der Prozess-Nummer %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/el.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/el.po new file mode 100644 index 0000000000000000000000000000000000000000..8f53f431581ade39f20a76a65289fe88112edc9d --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/el.po @@ -0,0 +1,26 @@ +# Greek translation of hello-tcl +# Copyright (C) 2005 Free Software Foundation, Inc. +# Simos Xenitellis , 2005. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl 0.14.1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2005-01-06 18:50+0000\n" +"Last-Translator: Simos Xenitellis \n" +"Language-Team: Greek \n" +"Language: el\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: KBabel 1.3.1\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Γεια σου, κόσμε!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Αυτό το πρόγραμμα εκτελείται με αριθμό διεργασίας %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/eo.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/eo.po new file mode 100644 index 0000000000000000000000000000000000000000..42bcc2305c5198ca465f118e4a15ff59cfb6c43b --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/eo.po @@ -0,0 +1,28 @@ +# La teksto por la mesaĝoj de la programo "gettext". +# Copyright (C) 2006, 2016 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Edmund GRIMLEY EVANS , 2006. +# Felipe CASTRO , 2016, 2023. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl 0.22\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2023-06-23 19:00-0300\n" +"Last-Translator: Felipe Castro \n" +"Language-Team: Esperanto \n" +"Language: eo\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 2.4.2\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Saluton, mondo!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Ĉi tiu programo rulas kiel procez-numero %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/es.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/es.po new file mode 100644 index 0000000000000000000000000000000000000000..a533d0f2fec93737ce52f7c392c62793259011a0 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/es.po @@ -0,0 +1,30 @@ +# Mensajes en español para GNU gettext. +# Copyright (C) 2014 Yoyodyne, Inc. (msgids) +# +# This file is distributed under the same license as the gettext package. +# +# Max de Mendizábal , 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004. +# Antonio Ceballos , 2014, 2015, 2023, 2025 +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-0.24-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-02-23 17:01+0100\n" +"Last-Translator: Antonio Ceballos \n" +"Language-Team: Spanish \n" +"Language: es\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "¡Hola, mundo!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Este programa está corriendo como el proceso número %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/fi.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/fi.po new file mode 100644 index 0000000000000000000000000000000000000000..be600f499dac57e781bd435d8ff99185c58a49ac --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/fi.po @@ -0,0 +1,29 @@ +# Finnish messages for GNU Gettext examples. +# This file is distributed under the same license as the gettext package. +# Copyright © 2007, 2014, 2015 Yoyodyne, Inc. (msgids) +# Lauri Nurmi , 2007. +# Jorma Karvonen , 2014-2015. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl 0.19.4.73\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2015-09-01 16:59+0300\n" +"Last-Translator: Jorma Karvonen \n" +"Language-Team: Finnish \n" +"Language: fi\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 1.5.4\n" + +# Tämä nimenomainen käännös valittu GNU Hellon mukaisesti. +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Terve maailma!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Tämän ohjelman prosessinumero on %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/fr.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/fr.po new file mode 100644 index 0000000000000000000000000000000000000000..e91f52847eafbced40347870be948cd83da63140 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/fr.po @@ -0,0 +1,32 @@ +# Messages français pour GNU gettext. +# Copyright (C) 2006 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Michel Robitaille , 2006. +# Christophe Combelles , 2006 +# Stéphane Aulery , 2015 +# Christian Wiatr , 2023 +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl 0.22\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2023-06-28 16:25+0200\n" +"Last-Translator: Christian Wiatr \n" +"Language-Team: French \n" +"Language: fr\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=(n > 1);\n" +"X-Generator: Poedit 2.4.2\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Bonjour, le monde !" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Ce programme est exécuté en tant que processus numéro %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/ga.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/ga.po new file mode 100644 index 0000000000000000000000000000000000000000..a784406af8b3b7ae6ac4416803a5d3eeec45263a --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/ga.po @@ -0,0 +1,26 @@ +# Irish translations for hello-tcl. +# Copyright (C) 2015 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Kevin Patrick Scannell , 2004, 2017. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl 0.19.4.73\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2017-01-10 12:09-0500\n" +"Last-Translator: Kevin Patrick Scannell \n" +"Language-Team: Irish \n" +"Language: ga\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Dia duit, a dhomhain!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Tá an clár seo ag rith mar phróiseas %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/gl.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/gl.po new file mode 100644 index 0000000000000000000000000000000000000000..66300deef1d7db6ce5f018acf0cea49ec0c5c3ec --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/gl.po @@ -0,0 +1,31 @@ +# Galician translation for hello-tcl package. +# Copyright (C) 2010 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Leandro Regueiro , 2010-2014. +# +# Proxecto Trasno - Adaptación do software libre á lingua galega: Se desexas +# colaborar connosco, podes atopar máis información en +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl 0.19-rc1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2014-05-10 16:34+0100\n" +"Last-Translator: Leandro Regueiro \n" +"Language-Team: Galician \n" +"Language: gl\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=(n!=1);\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Ola, mundo!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Este programa estase executando como o proceso número %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/hr.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/hr.po new file mode 100644 index 0000000000000000000000000000000000000000..e57fa8db4c3285c93205a65820d066be94a43e19 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/hr.po @@ -0,0 +1,33 @@ +# Translation of hello-tcl to Croatian. +# Copyright (C) 2003, 2004, 2014, 2015, 2019 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Permission is granted to freely copy and distribute +# this file and modified versions, provided that this +# header is not removed and modified versions are marked +# as such. +# +# Tomislav Krznar , 2012. +# Božidar Putanec , 2018-2025. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GNU hello-tcl 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-28 10:15-0700\n" +"Last-Translator: Božidar Putanec \n" +"Language-Team: Croatian \n" +"Language: hr\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Pozdrav, svijete!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Ovaj program se izvršava kao proces broj %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/hu.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/hu.po new file mode 100644 index 0000000000000000000000000000000000000000..23a0a592f9519cb76e7f78abfdc6745ab539ab19 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/hu.po @@ -0,0 +1,29 @@ +# Hungarian translation for hello-tcl. +# This file is distributed under the same license as the gettext package. +# Copyright (C) 2014 Yoyodyne, Inc. (msgids) +# +# Tamás Kiss , 2005. +# Balázs Úr , 2014, 2015. +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl 0.19.4.73\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2015-06-23 20:31+0200\n" +"Last-Translator: Balázs Úr \n" +"Language-Team: Hungarian \n" +"Language: hu\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"X-Generator: Lokalize 1.2\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Hello, világ!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Ez a program a(z) %d folyamatazonosítóval fut." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/id.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/id.po new file mode 100644 index 0000000000000000000000000000000000000000..bdb7cecdd41d07f3cd6e66084d031345f03ce317 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/id.po @@ -0,0 +1,27 @@ +# translation of hello-tcl-0.15-pre5.po to Indonesian +# Copyright (C) 2006 Yoyodyne, Inc. +# This file is distributed under the same license as the PACKAGE package. +# +# Tedi Heriyanto , 2006. +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-0.15-pre5\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2006-09-27 20:19+0700\n" +"Last-Translator: Tedi Heriyanto \n" +"Language-Team: Indonesian \n" +"Language: id\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: KBabel 1.11.2\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Hello, world!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Program ini berjalan sebagai proses nomor %d" diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/it.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/it.po new file mode 100644 index 0000000000000000000000000000000000000000..b082649f05e5083a0a8b7513c3ecc4dd967a98b5 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/it.po @@ -0,0 +1,29 @@ +# Italian messages for hello-tcl. +# Copyright (C) 2005, 2006 Yoyodyne, Inc. (msgids) +# Copyright (C) 2024 Free Software Foundation, Inc. +# This file is distributed under the same license as the gettext package. +# Marco Colombo , 2005, 2006, 2015. +# Michele Locati , 2024, 2025. +# +msgid "" +msgstr "" +"Project-Id-Version: GNU hello-tcl 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-05-04 18:28+0200\n" +"Last-Translator: Michele Locati \n" +"Language-Team: Italian \n" +"Language: it\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Ciao, mondo!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Questo programma è in esecuzione con numero di processo %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/ja.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/ja.po new file mode 100644 index 0000000000000000000000000000000000000000..581b752fbdf1fa36c344ba1a532a253b6752598e --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/ja.po @@ -0,0 +1,26 @@ +# Translation of `hello-tcl' messages to Japanese. +# Copyright (C) 2005, 2006, 2014, 2015, 2023, 2025 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Masahito Yamaga , 2025. +# +msgid "" +msgstr "" +"Project-Id-Version: GNU hello-tcl 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-28 19:59+0900\n" +"Last-Translator: Masahito Yamaga \n" +"Language-Team: Japanese \n" +"Language: ja\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "世界よ, こんにちは!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "このプログラムはプロセス番号 %d で動いています." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/ka.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/ka.po new file mode 100644 index 0000000000000000000000000000000000000000..62fe0ac8b18fe09ebb0a6bff7f6b480814821a18 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/ka.po @@ -0,0 +1,28 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2022 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Temuri Doghonadze , 2022. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl 0.20.2\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2022-05-22 05:04+0200\n" +"Last-Translator: Temuri Doghonadze \n" +"Language-Team: Georgian <(nothing)>\n" +"Language: ka\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"X-Generator: Poedit 3.0.1\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "გამარჯობა სამყაროვ!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "პროგრამა გაშვებულია პროცესის ნომრით %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/ky.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/ky.po new file mode 100644 index 0000000000000000000000000000000000000000..8188cba0a9342dc065bea7fc2944e38b65fd434d --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/ky.po @@ -0,0 +1,28 @@ +# Translation of 'hello-tcl' messages to Kirghiz. +# Copyright (C) 2004 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Ilyas Bakirov , 2007. +# Ilyas Bakirov , 2018. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl 0.19.4.73\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2018-02-15 18:26+0600\n" +"Last-Translator: Ilyas Bakirov \n" +"Language-Team: Kirghiz \n" +"Language: ky\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 2.0.6\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Салам дүйнө!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Бул программа %d процесс номери катары иштеп жатат." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/lv.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/lv.po new file mode 100644 index 0000000000000000000000000000000000000000..229b5b79871ba4c5e83d3da67b28558ab6d6c0a7 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/lv.po @@ -0,0 +1,30 @@ +# Latvian translation of hello-tcl +# Copyright (C) 2009 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Arvis Lācis , 2009. +# Rihards Priedītis , 2023, 2025. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-0.24-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-03-09 11:44+0000\n" +"Last-Translator: Rihards Priedītis \n" +"Language-Team: Latvian \n" +"Language: lv\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n != 0 ? 1 : " +"2);\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 3.5\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Sveika, pasaule!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Šī programma darbojas ar procesa numuru %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/ms.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/ms.po new file mode 100644 index 0000000000000000000000000000000000000000..e3b69b0674417e4ee4c10ea0f7feb65494acc1fe --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/ms.po @@ -0,0 +1,28 @@ +# hello-tcl Bahasa Melayu (Malay) (ms). +# Copyright (C) 2006, 2015, 2023, 2025 Yoyodyne, Inc. (msgids) +# Copyright (C) 2006, 2015, 2023, 2025 Free Software Foundation, Inc. +# This file is distributed under the same license as the gettext package. +# Sharuzzaman Ahmat Raslan , 2006, 2015, 2023, 2025 +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-05-03 21:10+0800\n" +"Last-Translator: Sharuzzaman Ahmat Raslan \n" +"Language-Team: Malay \n" +"Language: ms\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 3.5\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Hello, dunia!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Program ini dilaksanakan sebagai proses bernombor %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/mt.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/mt.po new file mode 100644 index 0000000000000000000000000000000000000000..0674429db07d2cd9ed31326bee4a2241d3fd319c --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/mt.po @@ -0,0 +1,27 @@ +# hello-tcl-0.16.2-pre5. +# Copyright (C) 2008 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Clyde Meli , 2001-2008. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl 0.16.2-pre5\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2008-11-18 17:27+0100\n" +"Last-Translator: Clyde Meli \n" +"Language-Team: Maltese \n" +"Language: mt\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Hello, lil kulħadd!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Dal-programm qed jaħdem taħt il-proċess numru %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/nb.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/nb.po new file mode 100644 index 0000000000000000000000000000000000000000..c0b64169edb066337bea77a2cfefe329c5f21cab --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/nb.po @@ -0,0 +1,29 @@ +# Norwegian Bokmal translations for hello-tcl package. +# Copyright (C) 2012 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Johnny A. Solbu , 2012-2024 +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl 0.22\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2024-01-06 16:33+0100\n" +"Last-Translator: Johnny A. Solbu \n" +"Language-Team: Norwegian Bokmaal \n" +"Language: nb\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"X-Generator: Poedit 2.4.2\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Hallo verden!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Dette programmet kjører som prosess nummer %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/nl.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/nl.po new file mode 100644 index 0000000000000000000000000000000000000000..af64fc93c41ca1f0de6ec6ff86d35e11b1025b2b --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/nl.po @@ -0,0 +1,31 @@ +# Dutch translations for GNU hello-tcl. +# Copyright (C) 2025 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# "There are three basic rules for writing a novel. +# Unfortunately nobody knows what they are." +# +# Benno Schulenberg , 2007, 2014, 2015, 2019, 2025. +# Elros Cyriatan , 2004. +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-0.24-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-03-01 14:51+0100\n" +"Last-Translator: Benno Schulenberg \n" +"Language-Team: Dutch \n" +"Language: nl\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Hallo, wereld!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Dit programma draait als proces nummer %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/nn.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/nn.po new file mode 100644 index 0000000000000000000000000000000000000000..d2a765bed16fbdd23a8a4d7e92b115111b086e9a --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/nn.po @@ -0,0 +1,28 @@ +# Norwegian Nynorsk translation of GNU hello-tcl +# Copyright (C) 2020 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Karl Ove Hufthammer , 2020. +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-0.20.2\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2020-05-04 18:58+0200\n" +"Last-Translator: Karl Ove Hufthammer \n" +"Language-Team: Norwegian Nynorsk \n" +"Language: nn\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"X-Generator: Lokalize 20.04.0\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Hei, verda!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Dette programmet køyrer som prosess nummer %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/pl.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/pl.po new file mode 100644 index 0000000000000000000000000000000000000000..0d2caa7b50aa09cc7f8ed4b1a6536cd6eb3e2a98 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/pl.po @@ -0,0 +1,27 @@ +# Polish translations for the GNU gettext messages, hello-tcl domain +# Copyright (C) 2010, 2014, 2015, 2025 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Rafał Maszkowski , 2003, 2010, 2014, 2015, 2025 +msgid "" +msgstr "" +"Project-Id-Version: GNU hello-tcl 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-25 17:16+0200\n" +"Last-Translator: Rafał Maszkowski \n" +"Language-Team: Polish \n" +"Language: pl\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8-bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=3; plural=(n==1 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 " +"|| n%100>=20) ? 1 : 2);\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Cześć, świecie!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Ten program działa jako proces o numerze %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/pt.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/pt.po new file mode 100644 index 0000000000000000000000000000000000000000..9f9f869e753fd4e013eddfbf9d6294f7994126c1 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/pt.po @@ -0,0 +1,28 @@ +# Portuguese (Portugal) translation of 'hello-tcl' package. +# Copyright (C) 2018 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Pedro Albuquerque , 2019, 2020, 2025. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-28 11:24+0100\n" +"Last-Translator: Pedro Albuquerque \n" +"Language-Team: Portuguese \n" +"Language: pt\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=n != 1;\\n;\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 3.6\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Olá mundo!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Este programa está em execução como processo nº %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/pt_BR.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/pt_BR.po new file mode 100644 index 0000000000000000000000000000000000000000..21d6976134fade8815d3e42f6cd843a638169d3e --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/pt_BR.po @@ -0,0 +1,31 @@ +# Brazilian Portuguese translations for gettext-example +# Traduções em português brasileiro para gettext-example +# Copyright (C) 2025 Yoyodyne, Inc. (msgids) +# Copyright (C) 2025 Free Software Foundation, Inc. +# This file is distributed under the same license as the gettext package. +# Rafael Fontenelle , 2013-2025. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-28 10:24-0300\n" +"Last-Translator: Rafael Fontenelle \n" +"Language-Team: Brazilian Portuguese \n" +"Language: pt_BR\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n > 1);\n" +"X-Generator: Gtranslator 48.0\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Olá, mundo!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Este programa está sendo executado com número de processo %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/ro.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/ro.po new file mode 100644 index 0000000000000000000000000000000000000000..1a48aa47cf5fc1ce578403de35060b0f5831992b --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/ro.po @@ -0,0 +1,50 @@ +# Translation of "hello-tcl" messages to Romanian. +# Mesajele în limba română pentru pachetul hello-tcl. +# Copyright © 2015, 2019, 2022, 2023, 2024, 2025 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Eugen Hoancă , 2003. +# Mihai Cristescu , 2015 - 2019. +# Remus-Gabriel Chelu , 2022 - 2025. +# +# Cronologia traducerii fișierului „hello-tcl”: +# Traducerea inițială, făcută de EH, pentru versiunea hello-tcl 0.12.1, 2003. +# Actualizare a traducerii pentru versiunea hello-tcl 0.19.4-rc1, făcută de MC, mar-2015. +# Actualizare a traducerii pentru versiunea hello-tcl 0.19.4.73, făcută de MC, iun-2015. +# Actualizare a traducerii pentru versiunea hello-tcl 0.20-rc1, făcută de MC, apr-2019. +# Actualizare a mesajelor, de la fișierul „hello-tcl-0.20.2.pot”. +# Actualizare a algoritmului formelor de plural (de la „trei-vechi” la „trei-actual”). +# NU și a mesajelor traduse (acestea au rămas neschimbate). +# Eliminare a mesajelor ce-au dispărut în ultima versiune. +# Actualizări realizate de Remus-Gabriel Chelu , 15.01.2022. +# Actualizare a traducerii pentru versiunea 0.20.2 făcută de R-GC, ian-2022. +# Actualizare a traducerii pentru versiunea 0.22 făcută de R-GC, iun-2023. +# Revizuire și corectare a traducerii pentru versiunea 0.23-pre1 făcută de R-GC, oct-2024. +# Actualizare a traducerii pentru versiunea 0.24-pre1 făcută de R-GC, feb-2025. +# Actualizare a traducerii pentru versiunea 0.25-pre1 făcută de R-GC, apr-2025. +# Actualizare a traducerii pentru versiunea Y, făcută de X, Z(luna-anul). +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-29 00:25+0200\n" +"Last-Translator: Remus-Gabriel Chelu \n" +"Language-Team: Romanian \n" +"Language: ro\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=3; plural=(n==1 ? 0 : (n==0 || (n%100 > 0 && n%100 < " +"20)) ? 1 : 2);\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 3.5\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Salutare, lume!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Acest program rulează ca procesul numărul %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/ru.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/ru.po new file mode 100644 index 0000000000000000000000000000000000000000..ee2a0b0b57f57d31328939d66fc949cc86017493 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/ru.po @@ -0,0 +1,30 @@ +# Translation of hello-tcl-0.14.1.po to Russian +# Copyright (C) 2004 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Pavel Maryanov , 2004. +# SPDX-FileCopyrightText: 2014, 2015, 2023, 2025 Yuri Kozlov +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-05-02 09:17+0300\n" +"Last-Translator: Yuri Kozlov \n" +"Language-Team: Russian \n" +"Language: ru\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Lokalize 24.12.0\n" +"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && " +"n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Здравствуй, мир!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Эта программа выполняется как процесс под номером %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/sk.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/sk.po new file mode 100644 index 0000000000000000000000000000000000000000..01ee95569869d8fd27ebc170eb2321b3e434553b --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/sk.po @@ -0,0 +1,26 @@ +# Slovak translations GNU for hello-tcl package. +# Copyright (C) 2003, 2004, 2014, 2023, 2025 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Marcel Telka , 2003, 2004, 2014, 2023, 2025. +# +msgid "" +msgstr "" +"Project-Id-Version: GNU hello-tcl 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-28 13:53+0200\n" +"Last-Translator: Marcel Telka \n" +"Language-Team: Slovak \n" +"Language: sk\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Ahoj svet!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Tento program beží ako proces s číslom %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/sl.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/sl.po new file mode 100644 index 0000000000000000000000000000000000000000..cd127fc4a8d6646eecf0fef4a8532c917ff73f72 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/sl.po @@ -0,0 +1,29 @@ +# -*- mode: po; coding: utf-8; -*- Slovenian message catalog for GNU gettext-example +# Copyright (C) 2005 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Primož Peterlin , 2005, 2014, 2015, 2024. +# $Id: hello-tcl-0.22.sl.po,v 1.1 2024/03/28 17:02:19 peterlin Exp $ +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl 0.22\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2024-03-28 18:02+0100\n" +"Last-Translator: Primož Peterlin \n" +"Language-Team: Slovenian \n" +"Language: sl\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8-bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=4; plural=(n%100==1 ? 1 : n%100==2 ? 2 : n%100==3 || " +"n%100==4 ? 3 : 0);\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Pozdravljen, svet!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Ta program teče kot proces številka %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/sq.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/sq.po new file mode 100644 index 0000000000000000000000000000000000000000..ca4dcf86533541ccfb7392914707525519134d5b --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/sq.po @@ -0,0 +1,28 @@ +# Albanian translation of gettext-example. +# Copyright (C) 2020 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Besnik Bleta , 2020,2023,2024,2025. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-28 19:56+0300\n" +"Last-Translator: Besnik Bleta \n" +"Language-Team: Albanian \n" +"Language: sq\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 3.2.2\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Tungjatjeta, botë!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Ky program po xhiron si procesi numër %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/sr.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/sr.po new file mode 100644 index 0000000000000000000000000000000000000000..418099e8bd6a14aa8aab154c0d72b001fccc70f8 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/sr.po @@ -0,0 +1,30 @@ +# Serbian translation of hello-tcl. +# Copyright (C) 2014 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Aleksandar Jelenak , 2004. +# Мирослав Николић , 2014-2025. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl-0.24-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-03-02 16:51+0100\n" +"Last-Translator: Мирослав Николић \n" +"Language-Team: Serbian <(nothing)>\n" +"Language: sr\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && " +"n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 3.5\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Здраво, свима!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Овај програм се извршава као процес број %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/sv.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/sv.po new file mode 100644 index 0000000000000000000000000000000000000000..5f4d3eb950400854b0851d94f76a637c760dd238 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/sv.po @@ -0,0 +1,30 @@ +# Swedish messages for hello-tcl. +# Copyright © 2006, 2014, 2016, 2019, 2020, 2023, 2024, 2025 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Jan Djärv , 2003, 2006, 2014. +# Göran Uddeborg , 2016, 2019, 2020, 2023, 2024, 2025. +# Luna Jernberg , 2025. +# $Revision: 1.12 $ +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-28 12:18+0200\n" +"Last-Translator: Luna Jernberg \n" +"Language-Team: Swedish \n" +"Language: sv\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 3.5\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Hej världen!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Detta program kör som process nummer %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/ta.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/ta.po new file mode 100644 index 0000000000000000000000000000000000000000..e1efd416a9f60f4bf891f824fc946fc6659ad344 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/ta.po @@ -0,0 +1,28 @@ +# Tamil messages for GNU gettext. +# Copyright (C) 2018 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# List of contributors follow: +# Poorajith , 2018. +# Arun Isaac , 2023. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl 0.22\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2023-06-19 00:06+0100\n" +"Last-Translator: Arun Isaac \n" +"Language-Team: Tamil \n" +"Language: ta\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "வணக்கம், உலகு!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "இந்நிரல் செயலாக்க எண் %d ஆக இயங்கிக்கொண்டிருக்கிறது." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/tr.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/tr.po new file mode 100644 index 0000000000000000000000000000000000000000..8a5b0108c1566c209df86552b9fb7cce1c077626 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/tr.po @@ -0,0 +1,29 @@ +# Turkish translation for hello-tcl. +# This file is distributed under the same license as the gettext package. +# Copyright (C) 2017 Yoyodyne, Inc. (msgids) +# Copyright (C) 2004 Free Software Foundation, Inc. +# Nilgün Belma Bugüner , 2003,2004 +# Mehmet Kececi , 2017, 2019, 2020. +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl 0.20.2\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2020-04-17 13:10+0300\n" +"Last-Translator: Mehmet Kececi \n" +"Language-Team: Turkish \n" +"Language: tr\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=1; plural=0;\n" +"X-Generator: Poedit 2.3\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Merhaba, dünya!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Bu yazılım %d işlem numarası ile çalışıyor." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/uk.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/uk.po new file mode 100644 index 0000000000000000000000000000000000000000..4039ae571c440730ab9d629a23e5c59db28fc7cb --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/uk.po @@ -0,0 +1,30 @@ +# Ukrainian translation to hello-tcl +# Copyright (C) 2014 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Maxim V. Dziumanenko , 2004-2007. +# Yuri Chornoivan , 2014, 2015, 2023, 2025. +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-28 13:56+0300\n" +"Last-Translator: Yuri Chornoivan \n" +"Language-Team: Ukrainian \n" +"Language: uk\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && " +"n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n" +"X-Generator: Lokalize 23.04.3\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Привіт, світе!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Ця програма виконується як процес з номером %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/vi.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/vi.po new file mode 100644 index 0000000000000000000000000000000000000000..51029327c1b1b0272c29f45cc2817df420c0f386 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/vi.po @@ -0,0 +1,30 @@ +# Vietnamese Translation for Gettext Examples. +# Bản dịch tiếng Việt dành cho các ví dụ của gói gettext. +# Copyright © 2015 Yoyodyne, Inc. (msgids) +# Copyright © 2015 Free Software Foundation, Inc. +# This file is distributed under the same license as the gettext package. +# Clytie Siddall , 2005-2010. +# Trần Ngọc Quân , 2012-2015, 2023. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl 0.22\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2023-06-24 09:10+0700\n" +"Last-Translator: Trần Ngọc Quân \n" +"Language-Team: Vietnamese \n" +"Language: vi\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=1; plural=0;\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "Chào thế giới!" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "Chương trình này đang chạy với mã số tiến trình %d." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/zh_CN.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/zh_CN.po new file mode 100644 index 0000000000000000000000000000000000000000..9951941ef677da44a3745053a546c1b25a184268 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/zh_CN.po @@ -0,0 +1,29 @@ +# zh_CN translation for hello-tcl. +# Copyright (C) 2015 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Funda Wang , 2003. +# Ji ZhengYu , 2015. +# Boyuan Yang <073plan@gmail.com>, 2019, 2023, 2025. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-29 15:56-0400\n" +"Last-Translator: Boyuan Yang <073plan@gmail.com>\n" +"Language-Team: Chinese (simplified) \n" +"Language: zh_CN\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 3.6\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "你好，世界！" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "此程序正以进程号 %d 运行。" diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/zh_HK.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/zh_HK.po new file mode 100644 index 0000000000000000000000000000000000000000..c19166c773246e762d83580709ecc9283eb8bdd9 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/zh_HK.po @@ -0,0 +1,25 @@ +# Chinese (Hong Kong) translation of hello-tcl. +# Copyright (C) 2006 Yoyodyne, Inc. +# Abel Cheung , 2006. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl 0.15-pre5\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2006-07-05 15:40+0800\n" +"Last-Translator: Abel Cheung \n" +"Language-Team: Chinese (Hong Kong) \n" +"Language: zh_HK\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "你好！" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "本程式正在執行中，進程編號為 %d。" diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/zh_TW.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/zh_TW.po new file mode 100644 index 0000000000000000000000000000000000000000..ae8f2514173c8835364883f857a8c357ea654c76 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-tcl/po/zh_TW.po @@ -0,0 +1,29 @@ +# Traditional Chinese translation of hello-tcl. +# Copyright (C) 2009 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Abel Cheung , 2005. +# Wei-Lun Chao , 2013, 2015. +# Yi-Jyun Pan , 2024. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-tcl 0.23-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2024-11-30 14:14+0800\n" +"Last-Translator: Yi-Jyun Pan \n" +"Language-Team: Chinese (traditional) \n" +"Language: zh_TW\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 3.5\n" + +#: hello.tcl:11 +msgid "Hello, world!" +msgstr "哈囉，大家好！" + +#: hello.tcl:12 +#, tcl-format +msgid "This program is running as process number %d." +msgstr "本程式正在執行，行程編號為 %d。" diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/INSTALL b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/INSTALL new file mode 100644 index 0000000000000000000000000000000000000000..1aaff4e1655618a253ddf08b0e155f5bb396fd3b --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/INSTALL @@ -0,0 +1,16 @@ +This example relies on YaST2 (SuSE Linux: package yast2-core). + +Before "make install", you need to make the locale directory writable: + chmod a+w /usr/share/YaST2/locale + chmod a+w /usr/share/YaST2/locale/*/LC_MESSAGES +Unfortunately this directory is hardwired in YaST; there is no way to +put the message catalogs elsewhere. + +Installation: + ./autogen.sh + ./configure --prefix=/some/prefix + make + make install +Cleanup: + make distclean + ./autoclean.sh diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/Makefile.am b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/Makefile.am new file mode 100644 index 0000000000000000000000000000000000000000..ceeda90179c1456a5eb8d3814bc49d8e7f9d1a10 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/Makefile.am @@ -0,0 +1,30 @@ +# Example for use of GNU gettext. +# This file is in the public domain. +# +# Makefile configuration - processed by automake. + +# General automake options. +AUTOMAKE_OPTIONS = foreign +ACLOCAL_AMFLAGS = -I m4 + +# The list of subdirectories containing Makefiles. +SUBDIRS = m4 po + +# The list of programs that are built. +bin_SCRIPTS = hello +all-local: hello +CLEANFILES = hello + +# The YCP program is installed as data and invoked through a shell script. +pkgdata_DATA = hello.ycp +hello: + { echo '#!/bin/sh'; \ + echo 'if test -n "$$DISPLAY"; then'; \ + echo " exec /usr/lib/YaST2/bin/y2base '$(pkgdatadir)/hello.ycp' qt"; \ + echo 'else'; \ + echo " exec /usr/lib/YaST2/bin/y2base '$(pkgdatadir)/hello.ycp' ncurses"; \ + echo 'fi'; \ + } > $@ + +# Additional files to be distributed. +EXTRA_DIST = autogen.sh autoclean.sh diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/autoclean.sh b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/autoclean.sh new file mode 100644 index 0000000000000000000000000000000000000000..8655a871726b2a31a935332f3e7cbba7b36928e8 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/autoclean.sh @@ -0,0 +1,30 @@ +#!/bin/sh +# Example for use of GNU gettext. +# This file is in the public domain. +# +# Script for cleaning all autogenerated files. + +test ! -f Makefile || make distclean +rm -rf autom4te.cache + +# Brought in by explicit copy. +rm -f m4/nls.m4 +rm -f m4/po.m4 +rm -f m4/progtest.m4 +rm -f po/remove-potcdate.sed + +# Generated by aclocal. +rm -f aclocal.m4 + +# Generated by autoconf. +rm -f configure + +# Generated or brought in by automake. +rm -f Makefile.in +rm -f m4/Makefile.in +rm -f po/Makefile.in +rm -f install-sh +rm -f missing +rm -f po/*.pot +rm -f po/stamp-po +rm -f po/*.gmo diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/autogen.sh b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/autogen.sh new file mode 100644 index 0000000000000000000000000000000000000000..a972da8041799c1ddf0a23303c0660eb9fb827bc --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/autogen.sh @@ -0,0 +1,44 @@ +#!/bin/sh +# Example for use of GNU gettext. +# This file is in the public domain. +# +# Script for regenerating all autogenerated files. + +if test -r ../Makefile.am; then + # Inside the gettext source directory. + GETTEXT_TOPSRCDIR=../../.. +else + if test -r ../Makefile; then + # Inside a gettext build directory. + GETTEXT_TOOLS_SRCDIR=`sed -n -e 's,^top_srcdir *= *\(.*\)$,\1,p' ../Makefile` + # Adjust a relative top_srcdir. + case $GETTEXT_TOOLS_SRCDIR in + /*) ;; + *) GETTEXT_TOOLS_SRCDIR=../$GETTEXT_TOOLS_SRCDIR ;; + esac + GETTEXT_TOPSRCDIR=$GETTEXT_TOOLS_SRCDIR/../.. + else + # Installed under ${prefix}/share/doc/gettext/examples. + . ../installpaths + fi +fi + +cp -p ${ACLOCALDIR-$GETTEXT_TOPSRCDIR/gettext-runtime/m4}/nls.m4 m4/nls.m4 +cp -p ${ACLOCALDIR-$GETTEXT_TOPSRCDIR/gettext-runtime/m4}/po.m4 m4/po.m4 +cp -p ${ACLOCALDIR-$GETTEXT_TOPSRCDIR/gettext-runtime/m4}/progtest.m4 m4/progtest.m4 +cp -p ${GETTEXTSRCPODIR-$GETTEXT_TOPSRCDIR/gettext-runtime/po}/remove-potcdate.sed po/remove-potcdate.sed + +aclocal -I m4 + +autoconf + +automake -a -c + +cd po +for f in *.po; do + if test -r "$f"; then + lang=`echo $f | sed -e 's,\.po$,,'` + msgfmt -c -o $lang.gmo $lang.po + fi +done +cd .. diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/configure.ac b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/configure.ac new file mode 100644 index 0000000000000000000000000000000000000000..59b40837219d797f4c0c23b3078c71780862703f --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/configure.ac @@ -0,0 +1,27 @@ +dnl Example for use of GNU gettext. +dnl This file is in the public domain. +dnl +dnl Configuration file - processed by autoconf. + +AC_INIT([hello-ycp], [0]) +AC_CONFIG_SRCDIR([hello.ycp]) +AM_INIT_AUTOMAKE([1.11]) + +dnl Check for availability of YaST's engine. +test -f /usr/lib/YaST2/bin/y2base || { + echo "*** Essential program y2base not found" 1>&2 + exit 1 +} + +dnl The installed program must know where to find its message catalogs. +dnl Unfortunately, YaST hard codes the message catalog directory. +localedir=/usr/share/YaST2/locale +AC_SUBST([localedir]) + +dnl Support for the po directory. +AM_PO_SUBDIRS + +AC_CONFIG_FILES([Makefile]) +AC_CONFIG_FILES([m4/Makefile]) +AC_CONFIG_FILES([po/Makefile], [AM_POSTPROCESS_PO_MAKEFILE]) +AC_OUTPUT diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/hello.ycp b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/hello.ycp new file mode 100644 index 0000000000000000000000000000000000000000..0affb10e1b9b059a242a587ee6c50c449c942c03 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/hello.ycp @@ -0,0 +1,30 @@ +// Example for use of GNU gettext. +// This file is in the public domain. + +// Source code of the YCP program. + +UI(``{ + textdomain "hello-ycp"; + + map bash_out = SCR::Execute (.target.bash_output, "echo $PPID"); + integer pid = tointeger (bash_out["stdout"]:"99999"); + + OpenDialog ( + `VBox ( + `HBox ( + `Label (_("Hello, world!")), + `HStretch () + ), + `HBox ( + `Label (sformat (_("This program is running as process number %1."), pid)), + `HStretch () + ), + `HBox ( + `HStretch (), + `PushButton (`opt(`default), "&OK") + ) + ) + ); + UserInput(); + CloseDialog(); +}) diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/m4/Makefile.am b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/m4/Makefile.am new file mode 100644 index 0000000000000000000000000000000000000000..8a841b31f12ff3bd59428fbba049f50825d91510 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/m4/Makefile.am @@ -0,0 +1,2 @@ +EXTRA_DIST = \ + nls.m4 po.m4 diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/LINGUAS b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/LINGUAS new file mode 100644 index 0000000000000000000000000000000000000000..dc4a82afbad945018082c22f2061a43ef436dd68 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/LINGUAS @@ -0,0 +1,5 @@ +# Example for use of GNU gettext. +# This file is in the public domain. +# +# Set of available languages. +af ast bg ca cs da de el eo es fi fr ga gl hr hu id it ja ka ky lv ms mt nb nl nn pl pt pt_BR ro ru sk sl sq sr sv ta tr uk vi zh_CN zh_HK zh_TW diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/Makefile.am b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/Makefile.am new file mode 100644 index 0000000000000000000000000000000000000000..e13ef3a86647f2f33c182059cb551898d10f7d6b --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/Makefile.am @@ -0,0 +1,434 @@ +# Example for use of GNU gettext. +# This file is in the public domain. +# +# Makefile configuration - processed by automake. + +# List of files which contain translatable strings. +POTFILES = \ + hello.ycp + +# Usually the message domain is the same as the package name. +DOMAIN = $(PACKAGE) + +# These options get passed to xgettext. +XGETTEXT_OPTIONS = + +# This is the copyright holder that gets inserted into the header of the +# $(DOMAIN).pot file. Set this to the copyright holder of the surrounding +# package. (Note that the msgid strings, extracted from the package's +# sources, belong to the copyright holder of the package.) Translators are +# expected to transfer the copyright for their translations to this person +# or entity, or to disclaim their copyright. The empty string stands for +# the public domain; in this case the translators are expected to disclaim +# their copyright. +COPYRIGHT_HOLDER = Yoyodyne, Inc. + +# This tells whether or not to prepend "GNU " prefix to the package +# name that gets inserted into the header of the $(DOMAIN).pot file. +# Possible values are "yes", "no", or empty. If it is empty, try to +# detect it automatically by scanning the files in $(top_srcdir) for +# "GNU packagename" string. +PACKAGE_GNU = no + +# This is the email address or URL to which the translators shall report +# bugs in the untranslated strings: +# - Strings which are not entire sentences, see the maintainer guidelines +# in the GNU gettext documentation, section 'Preparing Strings'. +# - Strings which use unclear terms or require additional context to be +# understood. +# - Strings which make invalid assumptions about notation of date, time or +# money. +# - Pluralisation problems. +# - Incorrect English spelling. +# - Incorrect formatting. +# It can be your email address, or a mailing list address where translators +# can write to without being subscribed, or the URL of a web page through +# which the translators can contact you. +MSGID_BUGS_ADDRESS = bug-gettext@gnu.org + +# This is the list of locale categories, beyond LC_MESSAGES, for which the +# message catalogs shall be used. It is usually empty. +EXTRA_LOCALE_CATEGORIES = + +# These options get passed to msgmerge. +# Useful options are in particular: +# --previous to keep previous msgids of translated messages +MSGMERGE_OPTIONS = + +# These options get passed to msginit. +# If you want to disable line wrapping when writing PO files, add +# --no-wrap to MSGMERGE_OPTIONS, XGETTEXT_OPTIONS, and +# MSGINIT_OPTIONS. +MSGINIT_OPTIONS = + +MSGMERGE = @MSGMERGE@ +MSGMERGE_UPDATE = @MSGMERGE@ --update +MSGMERGE_FOR_MSGFMT_OPTION = @MSGMERGE_FOR_MSGFMT_OPTION@ +MSGINIT = msginit +MSGCONV = msgconv +MSGFILTER = msgfilter + +# This is computed as $(foreach file, $(POTFILES), $(top_srcdir)/$(file)) +POTFILES_DEPS != for file in $(POTFILES); do echo $(top_srcdir)/$$file; done + +# The set of available translations. +ALL_LINGUAS != if test -f $(srcdir)/LINGUAS; then \ + sed -e '/^\#/d' < $(srcdir)/LINGUAS; \ + else \ + echo $(LINGUAS); \ + fi +# This is computed as $(foreach lang, $(ALL_LINGUAS), $(srcdir)/$(lang).po) +POFILES != for lang in $(ALL_LINGUAS); do echo $(srcdir)/$$lang.po; done +# This is computed as $(foreach lang, $(ALL_LINGUAS), $(srcdir)/$(lang).gmo) +GMOFILES != for lang in $(ALL_LINGUAS); do echo $(srcdir)/$$lang.gmo; done +# This is computed as $(foreach lang, $(ALL_LINGUAS), $(lang).po-update) +UPDATEPOFILES != for lang in $(ALL_LINGUAS); do echo $$lang.po-update; done +# This is computed as $(foreach lang, $(ALL_LINGUAS), $(lang).nop) +DUMMYPOFILES != for lang in $(ALL_LINGUAS); do echo $$lang.nop; done + +# The set of desired translations, as specified by the installer or distributor. +DESIRED_LINGUAS = @DESIRED_LINGUAS@ +# The set of translations to install. This is computed based on $(ALL_LINGUAS) +# and $(DESIRED_LINGUAS). It is a subset of $(ALL_LINGUAS). +# We use the presentlang catalog if desiredlang is +# a. equal to presentlang, or +# b. a variant of presentlang (because in this case, presentlang can be used +# as a fallback for messages which are not translated in the desiredlang +# catalog). +INST_LINGUAS != for presentlang in $(ALL_LINGUAS); do \ + useit=false; \ + for desiredlang in $(DESIRED_LINGUAS); do \ + case "$$desiredlang" in \ + "$$presentlang" | "$$presentlang"_* | "$$presentlang".* | "$$presentlang"@*) \ + useit=true ;; \ + esac; \ + done; \ + if $$useit; then echo $$presentlang; fi; \ + done +# This is computed as $(foreach lang, $(INST_LINGUAS), $(lang).gmo) +CATALOGS != for lang in $(INST_LINGUAS); do echo $$lang.gmo; done + +SUFFIXES = .po .gmo .nop .po-create .po-update + +# The .pot file, stamp-po, .po files, and .gmo files appear in release tarballs. +# The GNU Coding Standards say in +# : +# "GNU distributions usually contain some files which are not source files +# ... . Since these files normally appear in the source directory, they +# should always appear in the source directory, not in the build directory. +# So Makefile rules to update them should put the updated files in the +# source directory." +# Therefore we put these files in the source directory, not the build directory. + +# During .po -> .gmo conversion, take into account the most recent changes to +# the .pot file. This eliminates the need to update the .po files when the +# .pot file has changed, which would be troublesome if the .po files are put +# under version control. +$(GMOFILES): $(srcdir)/$(DOMAIN).pot +.po.gmo: + @lang=`echo $* | sed -e 's,.*/,,'`; \ + test "$(srcdir)" = . && cdcmd="" || cdcmd="cd $(srcdir) && "; \ + echo "$${cdcmd}rm -f $${lang}.gmo && $(MSGMERGE) $(MSGMERGE_FOR_MSGFMT_OPTION) -o $${lang}.1po $${lang}.po $(DOMAIN).pot && $(GMSGFMT) -c --statistics --verbose -o $${lang}.gmo $${lang}.1po && rm -f $${lang}.1po"; \ + cd $(srcdir) && \ + rm -f $${lang}.gmo && \ + $(MSGMERGE) $(MSGMERGE_FOR_MSGFMT_OPTION) -o $${lang}.1po $${lang}.po $(DOMAIN).pot && \ + $(GMSGFMT) -c --statistics --verbose -o t-$${lang}.gmo $${lang}.1po && \ + mv t-$${lang}.gmo $${lang}.gmo && \ + rm -f $${lang}.1po + + +all-local: all-local-@USE_NLS@ + +all-local-yes: $(srcdir)/stamp-po +all-local-no: + +# $(srcdir)/$(DOMAIN).pot is only created when needed. When xgettext finds no +# internationalized messages, no $(srcdir)/$(DOMAIN).pot is created (because +# we don't want to bother translators with empty POT files). We assume that +# LINGUAS is empty in this case, i.e. $(POFILES) and $(GMOFILES) are empty. +# In this case, $(srcdir)/stamp-po is a nop (i.e. a phony target). + +# $(srcdir)/stamp-po is a timestamp denoting the last time at which the CATALOGS +# have been loosely updated. Its purpose is that when a developer or translator +# checks out the package from a version control system, and the $(DOMAIN).pot +# file is not under version control, "make" will update the $(DOMAIN).pot and +# the $(CATALOGS), but subsequent invocations of "make" will do nothing. This +# timestamp would not be necessary if updating the $(CATALOGS) would always +# touch them; however, the rule for $(POFILES) has been designed to not touch +# files that don't need to be changed. +$(srcdir)/stamp-po: $(srcdir)/$(DOMAIN).pot + test ! -f $(srcdir)/$(DOMAIN).pot || \ + test -z "$(GMOFILES)" || $(MAKE) $(GMOFILES) + @test ! -f $(srcdir)/$(DOMAIN).pot || { \ + echo "touch $(srcdir)/stamp-po" && \ + echo timestamp > $(srcdir)/stamp-poT && \ + mv $(srcdir)/stamp-poT $(srcdir)/stamp-po; \ + } + +# This target rebuilds $(DOMAIN).pot; it is an expensive operation. +# Note that $(DOMAIN).pot is not touched if it doesn't need to be changed. +# The determination of whether the package xyz is a GNU one is based on the +# heuristic whether some file in the top level directory mentions "GNU xyz". +# If GNU 'find' is available, we avoid grepping through monster files. +$(DOMAIN).pot-update: $(POTFILES_DEPS) + package_gnu="$(PACKAGE_GNU)"; \ + test -n "$$package_gnu" || { \ + if { if (LC_ALL=C find --version) 2>/dev/null | grep GNU >/dev/null; then \ + LC_ALL=C find -L $(top_srcdir) -maxdepth 1 -type f -size -10000000c -exec grep -i 'GNU $(PACKAGE)' /dev/null '{}' ';' 2>/dev/null; \ + else \ + LC_ALL=C grep -i 'GNU $(PACKAGE)' $(top_srcdir)/* 2>/dev/null; \ + fi; \ + } | grep -v 'libtool:' >/dev/null; then \ + package_gnu=yes; \ + else \ + package_gnu=no; \ + fi; \ + }; \ + if test "$$package_gnu" = "yes"; then \ + package_prefix='GNU '; \ + else \ + package_prefix=''; \ + fi; \ + if test -n '$(MSGID_BUGS_ADDRESS)'; then \ + msgid_bugs_address='$(MSGID_BUGS_ADDRESS)'; \ + else \ + msgid_bugs_address='$(PACKAGE_BUGREPORT)'; \ + fi; \ + case `$(XGETTEXT) --version | sed 1q | sed -e 's,^[^0-9]*,,'` in \ + '' | 0.[0-9] | 0.[0-9].* | 0.1[0-5] | 0.1[0-5].* | 0.16 | 0.16.[0-1]*) \ + $(XGETTEXT) --default-domain=$(DOMAIN) --directory=$(top_srcdir) \ + --add-comments=TRANSLATORS: \ + --copyright-holder='$(COPYRIGHT_HOLDER)' \ + --msgid-bugs-address="$$msgid_bugs_address" \ + $(XGETTEXT_OPTIONS) @XGETTEXT_EXTRA_OPTIONS@ \ + $(POTFILES) \ + ;; \ + *) \ + $(XGETTEXT) --default-domain=$(DOMAIN) --directory=$(top_srcdir) \ + --add-comments=TRANSLATORS: \ + --copyright-holder='$(COPYRIGHT_HOLDER)' \ + --package-name="$${package_prefix}$(PACKAGE)" \ + --package-version='$(VERSION)' \ + --msgid-bugs-address="$$msgid_bugs_address" \ + $(XGETTEXT_OPTIONS) @XGETTEXT_EXTRA_OPTIONS@ \ + $(POTFILES) \ + ;; \ + esac + test ! -f $(DOMAIN).po || { \ + if test -f $(srcdir)/$(DOMAIN).pot-header; then \ + sed -e '1,/^#$$/d' < $(DOMAIN).po > $(DOMAIN).1po && \ + cat $(srcdir)/$(DOMAIN).pot-header $(DOMAIN).1po > $(DOMAIN).po && \ + rm -f $(DOMAIN).1po \ + || exit 1; \ + fi; \ + if test -f $(srcdir)/$(DOMAIN).pot; then \ + sed -f $(srcdir)/remove-potcdate.sed < $(srcdir)/$(DOMAIN).pot > $(DOMAIN).1po && \ + sed -f $(srcdir)/remove-potcdate.sed < $(DOMAIN).po > $(DOMAIN).2po && \ + if cmp $(DOMAIN).1po $(DOMAIN).2po >/dev/null 2>&1; then \ + rm -f $(DOMAIN).1po $(DOMAIN).2po $(DOMAIN).po; \ + else \ + rm -f $(DOMAIN).1po $(DOMAIN).2po $(srcdir)/$(DOMAIN).pot && \ + mv $(DOMAIN).po $(srcdir)/$(DOMAIN).pot; \ + fi; \ + else \ + mv $(DOMAIN).po $(srcdir)/$(DOMAIN).pot; \ + fi; \ + } + +# This rule has no dependencies: we don't need to update $(DOMAIN).pot at +# every "make" invocation, only create it when it is missing. +# Only "make $(DOMAIN).pot-update" or "make dist" will force an update. +$(srcdir)/$(DOMAIN).pot: + $(MAKE) $(DOMAIN).pot-update + +# This target rebuilds a PO file if $(DOMAIN).pot has changed. +# Note that a PO file is not touched if it doesn't need to be changed. +$(POFILES): $(srcdir)/$(DOMAIN).pot + @lang=`echo $@ | sed -e 's,.*/,,' -e 's/\.po$$//'`; \ + if test -f "$(srcdir)/$${lang}.po"; then \ + test "$(srcdir)" = . && cdcmd="" || cdcmd="cd $(srcdir) && "; \ + echo "$${cdcmd}$(MSGMERGE_UPDATE) --quiet $(MSGMERGE_OPTIONS) --lang=$${lang} --previous $${lang}.po $(DOMAIN).pot"; \ + cd $(srcdir) \ + && { case `$(MSGMERGE_UPDATE) --version | sed 1q | sed -e 's,^[^0-9]*,,'` in \ + '' | 0.[0-9] | 0.[0-9].* | 0.10 | 0.10.*) \ + $(MSGMERGE_UPDATE) $(MSGMERGE_OPTIONS) $${lang}.po $(DOMAIN).pot;; \ + 0.1[1-5] | 0.1[1-5].*) \ + $(MSGMERGE_UPDATE) --quiet $(MSGMERGE_OPTIONS) $${lang}.po $(DOMAIN).pot;; \ + 0.1[6-7] | 0.1[6-7].*) \ + $(MSGMERGE_UPDATE) --quiet $(MSGMERGE_OPTIONS) --previous $${lang}.po $(DOMAIN).pot;; \ + *) \ + $(MSGMERGE_UPDATE) --quiet $(MSGMERGE_OPTIONS) --lang=$${lang} --previous $${lang}.po $(DOMAIN).pot;; \ + esac; \ + }; \ + else \ + $(MAKE) $${lang}.po-create; \ + fi + + +install-data-local: install-data-local-@USE_NLS@ +install-data-local-no: all-local +install-data-local-yes: all-local + @catalogs='$(CATALOGS)'; \ + for cat in $$catalogs; do \ + cat=`basename $$cat`; \ + lang=`echo $$cat | sed -e 's/\.gmo$$//'`; \ + dir=$(localedir)/$$lang/LC_MESSAGES; \ + $(MKDIR_P) $(DESTDIR)$$dir; \ + if test -r $$cat; then realcat=$$cat; else realcat=$(srcdir)/$$cat; fi; \ + $(INSTALL_DATA) $$realcat $(DESTDIR)$$dir/$(DOMAIN).mo; \ + echo "installing $$realcat as $(DESTDIR)$$dir/$(DOMAIN).mo"; \ + for lc in '' $(EXTRA_LOCALE_CATEGORIES); do \ + if test -n "$$lc"; then \ + if (cd $(DESTDIR)$(localedir)/$$lang && LC_ALL=C ls -l -d $$lc 2>/dev/null) | grep ' -> ' >/dev/null; then \ + link=`cd $(DESTDIR)$(localedir)/$$lang && LC_ALL=C ls -l -d $$lc | sed -e 's/^.* -> //'`; \ + mv $(DESTDIR)$(localedir)/$$lang/$$lc $(DESTDIR)$(localedir)/$$lang/$$lc.old; \ + mkdir $(DESTDIR)$(localedir)/$$lang/$$lc; \ + (cd $(DESTDIR)$(localedir)/$$lang/$$lc.old && \ + for file in *; do \ + if test -f $$file; then \ + ln -s ../$$link/$$file $(DESTDIR)$(localedir)/$$lang/$$lc/$$file; \ + fi; \ + done); \ + rm -f $(DESTDIR)$(localedir)/$$lang/$$lc.old; \ + else \ + if test -d $(DESTDIR)$(localedir)/$$lang/$$lc; then \ + :; \ + else \ + rm -f $(DESTDIR)$(localedir)/$$lang/$$lc; \ + mkdir $(DESTDIR)$(localedir)/$$lang/$$lc; \ + fi; \ + fi; \ + rm -f $(DESTDIR)$(localedir)/$$lang/$$lc/$(DOMAIN).mo; \ + ln -s ../LC_MESSAGES/$(DOMAIN).mo $(DESTDIR)$(localedir)/$$lang/$$lc/$(DOMAIN).mo 2>/dev/null || \ + ln $(DESTDIR)$(localedir)/$$lang/LC_MESSAGES/$(DOMAIN).mo $(DESTDIR)$(localedir)/$$lang/$$lc/$(DOMAIN).mo 2>/dev/null || \ + cp -p $(DESTDIR)$(localedir)/$$lang/LC_MESSAGES/$(DOMAIN).mo $(DESTDIR)$(localedir)/$$lang/$$lc/$(DOMAIN).mo; \ + echo "installing $$realcat link as $(DESTDIR)$(localedir)/$$lang/$$lc/$(DOMAIN).mo"; \ + fi; \ + done; \ + done + +installdirs-local: installdirs-local-@USE_NLS@ +installdirs-local-no: +installdirs-local-yes: + @catalogs='$(CATALOGS)'; \ + for cat in $$catalogs; do \ + cat=`basename $$cat`; \ + lang=`echo $$cat | sed -e 's/\.gmo$$//'`; \ + dir=$(localedir)/$$lang/LC_MESSAGES; \ + $(MKDIR_P) $(DESTDIR)$$dir; \ + for lc in '' $(EXTRA_LOCALE_CATEGORIES); do \ + if test -n "$$lc"; then \ + if (cd $(DESTDIR)$(localedir)/$$lang && LC_ALL=C ls -l -d $$lc 2>/dev/null) | grep ' -> ' >/dev/null; then \ + link=`cd $(DESTDIR)$(localedir)/$$lang && LC_ALL=C ls -l -d $$lc | sed -e 's/^.* -> //'`; \ + mv $(DESTDIR)$(localedir)/$$lang/$$lc $(DESTDIR)$(localedir)/$$lang/$$lc.old; \ + mkdir $(DESTDIR)$(localedir)/$$lang/$$lc; \ + (cd $(DESTDIR)$(localedir)/$$lang/$$lc.old && \ + for file in *; do \ + if test -f $$file; then \ + ln -s ../$$link/$$file $(DESTDIR)$(localedir)/$$lang/$$lc/$$file; \ + fi; \ + done); \ + rm -f $(DESTDIR)$(localedir)/$$lang/$$lc.old; \ + else \ + if test -d $(DESTDIR)$(localedir)/$$lang/$$lc; then \ + :; \ + else \ + rm -f $(DESTDIR)$(localedir)/$$lang/$$lc; \ + mkdir $(DESTDIR)$(localedir)/$$lang/$$lc; \ + fi; \ + fi; \ + fi; \ + done; \ + done + +uninstall-local: uninstall-local-@USE_NLS@ +uninstall-local-no: +uninstall-local-yes: + catalogs='$(CATALOGS)'; \ + for cat in $$catalogs; do \ + cat=`basename $$cat`; \ + lang=`echo $$cat | sed -e 's/\.gmo$$//'`; \ + for lc in LC_MESSAGES $(EXTRA_LOCALE_CATEGORIES); do \ + rm -f $(DESTDIR)$(localedir)/$$lang/$$lc/$(DOMAIN).mo; \ + done; \ + done + +html ID: + +MOSTLYCLEANFILES = +MOSTLYCLEANFILES += stamp-poT +MOSTLYCLEANFILES += core core.* *.stackdump $(DOMAIN).po $(DOMAIN).1po $(DOMAIN).2po *.new.po +MOSTLYCLEANFILES += *.o + +MAINTAINERCLEANFILES = $(DOMAIN).pot stamp-po $(GMOFILES) + +EXTRA_DIST = remove-potcdate.sed LINGUAS $(POFILES) $(GMOFILES) + +# Hidden from automake, but really activated. Works around an automake-1.5 bug. +#distdir: distdir1 +distdir1: + $(MAKE) update-po + $(MAKE) $(srcdir)/stamp-po + @if test -f $(srcdir)/$(DOMAIN).pot; then \ + for file in $(DOMAIN).pot stamp-po; do \ + if test -f $$file; then d=.; else d=$(srcdir); fi; \ + cp -p $$d/$$file $(distdir)/$$file || exit 1; \ + done; \ + else \ + case $(XGETTEXT) in \ + :) echo "Warning: Creating a tarball without '$(DOMAIN).pot', because a suitable 'xgettext' program was not found in PATH." 1>&2;; \ + *) echo "Warning: Creating a tarball without '$(DOMAIN).pot', because 'xgettext' found no strings to extract. Check the POTFILES and the XGETTEXT_OPTIONS in the Makefile.am file." 1>&2;; \ + esac; \ + fi + +update-po: Makefile + $(MAKE) $(DOMAIN).pot-update + test -z "$(UPDATEPOFILES)" || $(MAKE) $(UPDATEPOFILES) + $(MAKE) update-gmo + +# General rule for creating PO files. + +.nop.po-create: + @lang=`echo $@ | sed -e 's/\.po-create$$//'`; \ + echo "File $$lang.po does not exist. If you are a translator, you can create it through 'msginit'." 1>&2; \ + exit 1 + +# General rule for updating PO files. + +.nop.po-update: + @lang=`echo $@ | sed -e 's/\.po-update$$//'`; \ + tmpdir=`pwd`; \ + echo "$$lang:"; \ + test "$(srcdir)" = . && cdcmd="" || cdcmd="cd $(srcdir) && "; \ + echo "$${cdcmd}$(MSGMERGE) --quiet $(MSGMERGE_OPTIONS) --lang=$$lang --previous $$lang.po $(DOMAIN).pot -o $$lang.new.po"; \ + cd $(srcdir); \ + if { case `$(MSGMERGE) --version | sed 1q | sed -e 's,^[^0-9]*,,'` in \ + '' | 0.[0-9] | 0.[0-9].* | 0.10 | 0.10.*) \ + $(MSGMERGE) $(MSGMERGE_OPTIONS) -o $$tmpdir/$$lang.new.po $$lang.po $(DOMAIN).pot;; \ + 0.1[1-5] | 0.1[1-5].*) \ + $(MSGMERGE) --quiet $(MSGMERGE_OPTIONS) -o $$tmpdir/$$lang.new.po $$lang.po $(DOMAIN).pot;; \ + 0.1[6-7] | 0.1[6-7].*) \ + $(MSGMERGE) --quiet $(MSGMERGE_OPTIONS) --previous -o $$tmpdir/$$lang.new.po $$lang.po $(DOMAIN).pot;; \ + *) \ + $(MSGMERGE) --quiet $(MSGMERGE_OPTIONS) --lang=$$lang --previous -o $$tmpdir/$$lang.new.po $$lang.po $(DOMAIN).pot;; \ + esac; \ + }; then \ + if cmp $$lang.po $$tmpdir/$$lang.new.po >/dev/null 2>&1; then \ + rm -f $$tmpdir/$$lang.new.po; \ + else \ + if mv -f $$tmpdir/$$lang.new.po $$lang.po; then \ + :; \ + else \ + echo "msgmerge for $$lang.po failed: cannot move $$tmpdir/$$lang.new.po to $$lang.po" 1>&2; \ + exit 1; \ + fi; \ + fi; \ + else \ + echo "msgmerge for $$lang.po failed!" 1>&2; \ + rm -f $$tmpdir/$$lang.new.po; \ + fi + +$(DUMMYPOFILES): + +update-gmo: Makefile $(GMOFILES) + @: diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/af.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/af.po new file mode 100644 index 0000000000000000000000000000000000000000..398e1b3cb0183ca56f2cb9d108bfd747e8c86bf8 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/af.po @@ -0,0 +1,26 @@ +# Afrikaans translation for Silky +# Copyright (C) 2004 Free Software Foundation, Inc. +# This file is distributed under the same license as the silky package. +# Hanlie Pretorius , 2004. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp-0.13.1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2003-12-31 10:30+2\n" +"Last-Translator: Ysbeer \n" +"Language-Team: Afrikaans \n" +"Language: af\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Hallo wêreld!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Hierdie program loop as prosesnommer %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/ast.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/ast.po new file mode 100644 index 0000000000000000000000000000000000000000..dcb39c9e1181590e6b601bdb597035db4bb84d16 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/ast.po @@ -0,0 +1,29 @@ +# Asturian translation for hello-ycp +# Copyright (C) 2018 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Marquinos , 2009. +# enolp , 2018. +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp 0.19.4.73\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2018-07-16 00:28+0100\n" +"Last-Translator: enolp \n" +"Language-Team: Asturian \n" +"Language: ast\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=n != 1;\n" +"X-Generator: Lokalize 2.0\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "¡Hola, mundu!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Esti programa ta executándose como procesu númberu %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/bg.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/bg.po new file mode 100644 index 0000000000000000000000000000000000000000..139f2621059c5a64a839eb35ba94bf72d41b1e0b --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/bg.po @@ -0,0 +1,26 @@ +# Bulgarian translations for hello-ycp package. +# Copyright (C) 2010 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Roumen Petrov , 2010,2014,2015,2019,2023,2024.2025. +# +msgid "" +msgstr "" +"Project-Id-Version: GNU hello-ycp 0.24-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-03-08 19:09+0200\n" +"Last-Translator: Roumen Petrov \n" +"Language-Team: Bulgarian \n" +"Language: bg\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Здравейте всички!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Програмата е пусната под процес номер %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/ca.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/ca.po new file mode 100644 index 0000000000000000000000000000000000000000..61d058c093161eae10095a9a24da5ad52176780e --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/ca.po @@ -0,0 +1,27 @@ +# Catalan messages for GNU hello-ycp. +# Copyright (C) 2003, 2014, 2015 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Ivan Vilata i Balaguer , 2003, 2014, 2015, 2023. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp 0.22\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2023-07-07 08:36+0200\n" +"Last-Translator: Ivan Vilata i Balaguer \n" +"Language-Team: Catalan \n" +"Language: ca\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Hola, món!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Aquest programa està corrent amb el número de procés %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/cs.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/cs.po new file mode 100644 index 0000000000000000000000000000000000000000..07e4bb70381ed691abf4f4501eb47003338dc628 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/cs.po @@ -0,0 +1,29 @@ +# The Czech translation for the gettext package. +# Copyright (C) 2011 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Marek Černocký , 2011. +# Petr Písař , 2025. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-28 20:05+02:00\n" +"Last-Translator: Petr Pisar \n" +"Language-Team: Czech \n" +"Language: cs\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=3; plural=(n==1) ? 0 : (n>=2 && n<=4) ? 1 : 2;\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Ahoj světe!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Tento program běží jako proces číslo %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/da.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/da.po new file mode 100644 index 0000000000000000000000000000000000000000..023a81f029050cb50ba79ce1d8ec8e72864c3b0c --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/da.po @@ -0,0 +1,28 @@ +# Danish messages for hello-ycp. +# Copyright (C) 2015 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Jan Djærv , 2003, 2006. +# Keld Simonsen , 2011. +# Joe Hansen , 2015. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp 0.19.4.73\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2015-06-27 12:39+0100\n" +"Last-Translator: Joe Hansen \n" +"Language-Team: Danish \n" +"Language: da\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Hej verden!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Dette program kører som proces nummer %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/de.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/de.po new file mode 100644 index 0000000000000000000000000000000000000000..d40b1998fedaa4852a2d39ff3f212f960fb9c1ba --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/de.po @@ -0,0 +1,32 @@ +# German messages for hello-ycp. +# Copyright © 2003, 2013 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Bruno Haible , 2003. +# Karl Eichwalder , 2003. +# Jakob Kramer , 2013. +# Mario Blättermann , 2014, 2023, 2025. +# Philipp Thomas , 2015. +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-28 17:15+0200\n" +"Last-Translator: Mario Blättermann \n" +"Language-Team: German \n" +"Language: de\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"X-Generator: Lokalize 25.04.0\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Hallo Welt!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Dieses Programm läuft mit der Prozess-Nummer %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/el.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/el.po new file mode 100644 index 0000000000000000000000000000000000000000..8f6b01a086babce056876520982333dea8672a94 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/el.po @@ -0,0 +1,26 @@ +# Greek translation of hello-ycp +# Copyright (C) 2005 Free Software Foundation, Inc. +# Simos Xenitellis , 2005. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp 0.14.1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2005-01-06 18:50+0000\n" +"Last-Translator: Simos Xenitellis \n" +"Language-Team: Greek \n" +"Language: el\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: KBabel 1.3.1\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Γεια σου, κόσμε!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Αυτό το πρόγραμμα εκτελείται με αριθμό διεργασίας %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/eo.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/eo.po new file mode 100644 index 0000000000000000000000000000000000000000..3026fcea04f3920412fdaacd48149f6d3f25d579 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/eo.po @@ -0,0 +1,28 @@ +# La teksto por la mesaĝoj de la programo "gettext". +# Copyright (C) 2006, 2016 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Edmund GRIMLEY EVANS , 2006. +# Felipe CASTRO , 2016, 2023. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp 0.22\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2023-06-23 19:00-0300\n" +"Last-Translator: Felipe Castro \n" +"Language-Team: Esperanto \n" +"Language: eo\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 2.4.2\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Saluton, mondo!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Ĉi tiu programo rulas kiel procez-numero %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/es.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/es.po new file mode 100644 index 0000000000000000000000000000000000000000..5aa606cb2198b68c1bfb38ccfa977a876c505663 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/es.po @@ -0,0 +1,30 @@ +# Mensajes en español para GNU gettext. +# Copyright (C) 2014 Yoyodyne, Inc. (msgids) +# +# This file is distributed under the same license as the gettext package. +# +# Max de Mendizábal , 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004. +# Antonio Ceballos , 2014, 2015, 2023, 2025 +# +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp-0.24-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-02-23 17:01+0100\n" +"Last-Translator: Antonio Ceballos \n" +"Language-Team: Spanish \n" +"Language: es\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "¡Hola, mundo!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Este programa está corriendo como el proceso número %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/fi.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/fi.po new file mode 100644 index 0000000000000000000000000000000000000000..324404a43ce89f15d7bd667825a5037cba54f622 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/fi.po @@ -0,0 +1,29 @@ +# Finnish messages for GNU Gettext examples. +# This file is distributed under the same license as the gettext package. +# Copyright © 2007, 2014, 2015 Yoyodyne, Inc. (msgids) +# Lauri Nurmi , 2007. +# Jorma Karvonen , 2014-2015. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp 0.19.4.73\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2015-09-01 16:59+0300\n" +"Last-Translator: Jorma Karvonen \n" +"Language-Team: Finnish \n" +"Language: fi\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 1.5.4\n" + +# Tämä nimenomainen käännös valittu GNU Hellon mukaisesti. +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Terve maailma!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Tämän ohjelman prosessinumero on %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/fr.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/fr.po new file mode 100644 index 0000000000000000000000000000000000000000..3c3d150aa1e90d310afd0a9fc867f5b8be83675c --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/fr.po @@ -0,0 +1,32 @@ +# Messages français pour GNU gettext. +# Copyright (C) 2006 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Michel Robitaille , 2006. +# Christophe Combelles , 2006 +# Stéphane Aulery , 2015 +# Christian Wiatr , 2023 +# +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp 0.22\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2023-06-28 16:25+0200\n" +"Last-Translator: Christian Wiatr \n" +"Language-Team: French \n" +"Language: fr\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=(n > 1);\n" +"X-Generator: Poedit 2.4.2\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Bonjour, le monde !" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Ce programme est exécuté en tant que processus numéro %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/ga.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/ga.po new file mode 100644 index 0000000000000000000000000000000000000000..9cb27b9f934eda63f34f0c5442c80005b3511b96 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/ga.po @@ -0,0 +1,26 @@ +# Irish translations for hello-ycp. +# Copyright (C) 2015 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Kevin Patrick Scannell , 2004, 2017. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp 0.19.4.73\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2017-01-10 12:09-0500\n" +"Last-Translator: Kevin Patrick Scannell \n" +"Language-Team: Irish \n" +"Language: ga\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Dia duit, a dhomhain!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Tá an clár seo ag rith mar phróiseas %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/gl.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/gl.po new file mode 100644 index 0000000000000000000000000000000000000000..f029191a59e5ae0eadb284398001e36f72cb00b3 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/gl.po @@ -0,0 +1,31 @@ +# Galician translation for hello-ycp package. +# Copyright (C) 2010 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Leandro Regueiro , 2010-2014. +# +# Proxecto Trasno - Adaptación do software libre á lingua galega: Se desexas +# colaborar connosco, podes atopar máis información en +# +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp 0.19-rc1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2014-05-10 16:34+0100\n" +"Last-Translator: Leandro Regueiro \n" +"Language-Team: Galician \n" +"Language: gl\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=(n!=1);\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Ola, mundo!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Este programa estase executando como o proceso número %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/hr.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/hr.po new file mode 100644 index 0000000000000000000000000000000000000000..7984a2ae4ec089815b5d4cb60bebfaeba28bcb5b --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/hr.po @@ -0,0 +1,33 @@ +# Translation of hello-ycp to Croatian. +# Copyright (C) 2003, 2004, 2014, 2015, 2019 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Permission is granted to freely copy and distribute +# this file and modified versions, provided that this +# header is not removed and modified versions are marked +# as such. +# +# Tomislav Krznar , 2012. +# Božidar Putanec , 2018-2025. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GNU hello-ycp 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-28 10:15-0700\n" +"Last-Translator: Božidar Putanec \n" +"Language-Team: Croatian \n" +"Language: hr\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Pozdrav, svijete!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Ovaj program se izvršava kao proces broj %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/hu.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/hu.po new file mode 100644 index 0000000000000000000000000000000000000000..ad2c325616c4dcddece0329ea5db909b8a3b7800 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/hu.po @@ -0,0 +1,29 @@ +# Hungarian translation for hello-ycp. +# This file is distributed under the same license as the gettext package. +# Copyright (C) 2014 Yoyodyne, Inc. (msgids) +# +# Tamás Kiss , 2005. +# Balázs Úr , 2014, 2015. +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp 0.19.4.73\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2015-06-23 20:31+0200\n" +"Last-Translator: Balázs Úr \n" +"Language-Team: Hungarian \n" +"Language: hu\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"X-Generator: Lokalize 1.2\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Hello, világ!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Ez a program a(z) %1 folyamatazonosítóval fut." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/id.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/id.po new file mode 100644 index 0000000000000000000000000000000000000000..260962f985544b8a11d1716f3f812b39a2fdcf96 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/id.po @@ -0,0 +1,27 @@ +# translation of hello-ycp-0.15-pre5.po to Indonesian +# Copyright (C) 2006 Yoyodyne, Inc. +# This file is distributed under the same license as the PACKAGE package. +# +# Tedi Heriyanto , 2006. +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp-0.15-pre5\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2006-09-27 20:19+0700\n" +"Last-Translator: Tedi Heriyanto \n" +"Language-Team: Indonesian \n" +"Language: id\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: KBabel 1.11.2\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Hello, world!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Program ini berjalan sebagai proses nomor %1" diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/it.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/it.po new file mode 100644 index 0000000000000000000000000000000000000000..f20924c8a38c46ec812ff0b4ddba0dc5fce4af7a --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/it.po @@ -0,0 +1,29 @@ +# Italian messages for hello-ycp. +# Copyright (C) 2005, 2006 Yoyodyne, Inc. (msgids) +# Copyright (C) 2024 Free Software Foundation, Inc. +# This file is distributed under the same license as the gettext package. +# Marco Colombo , 2005, 2006, 2015. +# Michele Locati , 2024, 2025. +# +msgid "" +msgstr "" +"Project-Id-Version: GNU hello-ycp 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-05-04 18:28+0200\n" +"Last-Translator: Michele Locati \n" +"Language-Team: Italian \n" +"Language: it\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Ciao, mondo!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Questo programma è in esecuzione con numero di processo %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/ja.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/ja.po new file mode 100644 index 0000000000000000000000000000000000000000..1c5e6a7840517d7940de45bc273c11a8a4f9c302 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/ja.po @@ -0,0 +1,26 @@ +# Translation of `hello-ycp' messages to Japanese. +# Copyright (C) 2005, 2006, 2014, 2015, 2023, 2025 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Masahito Yamaga , 2025. +# +msgid "" +msgstr "" +"Project-Id-Version: GNU hello-ycp 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-28 19:59+0900\n" +"Last-Translator: Masahito Yamaga \n" +"Language-Team: Japanese \n" +"Language: ja\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "世界よ, こんにちは!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "このプログラムはプロセス番号 %1 で動いています." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/ka.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/ka.po new file mode 100644 index 0000000000000000000000000000000000000000..7908865ca8e575bd2d0312de6c3cbdec7ca489b6 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/ka.po @@ -0,0 +1,28 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2022 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Temuri Doghonadze , 2022. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp 0.20.2\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2022-05-22 05:04+0200\n" +"Last-Translator: Temuri Doghonadze \n" +"Language-Team: Georgian <(nothing)>\n" +"Language: ka\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"X-Generator: Poedit 3.0.1\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "გამარჯობა სამყაროვ!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "პროგრამა გაშვებულია პროცესის ნომრით %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/ky.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/ky.po new file mode 100644 index 0000000000000000000000000000000000000000..0e736d55686c13d01719cf1da19d58e686a3b91e --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/ky.po @@ -0,0 +1,28 @@ +# Translation of 'hello-ycp' messages to Kirghiz. +# Copyright (C) 2004 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Ilyas Bakirov , 2007. +# Ilyas Bakirov , 2018. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp 0.19.4.73\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2018-02-15 18:26+0600\n" +"Last-Translator: Ilyas Bakirov \n" +"Language-Team: Kirghiz \n" +"Language: ky\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 2.0.6\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Салам дүйнө!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Бул программа %1 процесс номери катары иштеп жатат." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/lv.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/lv.po new file mode 100644 index 0000000000000000000000000000000000000000..1f3c329e79edc3c2d790d666950413ed74432ded --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/lv.po @@ -0,0 +1,30 @@ +# Latvian translation of hello-ycp +# Copyright (C) 2009 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Arvis Lācis , 2009. +# Rihards Priedītis , 2023, 2025. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp-0.24-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-03-09 11:44+0000\n" +"Last-Translator: Rihards Priedītis \n" +"Language-Team: Latvian \n" +"Language: lv\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n != 0 ? 1 : " +"2);\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 3.5\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Sveika, pasaule!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Šī programma darbojas ar procesa numuru %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/ms.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/ms.po new file mode 100644 index 0000000000000000000000000000000000000000..7d579ce0e16714ddf3dbb7750cab40db7c2d73cf --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/ms.po @@ -0,0 +1,28 @@ +# hello-ycp Bahasa Melayu (Malay) (ms). +# Copyright (C) 2006, 2015, 2023, 2025 Yoyodyne, Inc. (msgids) +# Copyright (C) 2006, 2015, 2023, 2025 Free Software Foundation, Inc. +# This file is distributed under the same license as the gettext package. +# Sharuzzaman Ahmat Raslan , 2006, 2015, 2023, 2025 +# +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-05-03 21:10+0800\n" +"Last-Translator: Sharuzzaman Ahmat Raslan \n" +"Language-Team: Malay \n" +"Language: ms\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 3.5\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Hello, dunia!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Program ini dilaksanakan sebagai proses bernombor %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/mt.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/mt.po new file mode 100644 index 0000000000000000000000000000000000000000..0c5dec6763e51818729331e32947d1859d059969 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/mt.po @@ -0,0 +1,27 @@ +# hello-ycp-0.16.2-pre5. +# Copyright (C) 2008 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Clyde Meli , 2001-2008. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp 0.16.2-pre5\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2008-11-18 17:27+0100\n" +"Last-Translator: Clyde Meli \n" +"Language-Team: Maltese \n" +"Language: mt\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Hello, lil kulħadd!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Dal-programm qed jaħdem taħt il-proċess numru %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/nb.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/nb.po new file mode 100644 index 0000000000000000000000000000000000000000..10e9dac59dc0d2f1772a772b8302de71a7a6e847 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/nb.po @@ -0,0 +1,29 @@ +# Norwegian Bokmal translations for hello-ycp package. +# Copyright (C) 2012 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Johnny A. Solbu , 2012-2024 +# +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp 0.22\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2024-01-06 16:33+0100\n" +"Last-Translator: Johnny A. Solbu \n" +"Language-Team: Norwegian Bokmaal \n" +"Language: nb\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"X-Generator: Poedit 2.4.2\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Hallo verden!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Dette programmet kjører som prosess nummer %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/nl.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/nl.po new file mode 100644 index 0000000000000000000000000000000000000000..fcea17124c328d6fe5d07a17d98580ac8c9cb24c --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/nl.po @@ -0,0 +1,31 @@ +# Dutch translations for GNU hello-ycp. +# Copyright (C) 2025 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# "There are three basic rules for writing a novel. +# Unfortunately nobody knows what they are." +# +# Benno Schulenberg , 2007, 2014, 2015, 2019, 2025. +# Elros Cyriatan , 2004. +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp-0.24-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-03-01 14:51+0100\n" +"Last-Translator: Benno Schulenberg \n" +"Language-Team: Dutch \n" +"Language: nl\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Hallo, wereld!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Dit programma draait als proces nummer %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/nn.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/nn.po new file mode 100644 index 0000000000000000000000000000000000000000..05869344b557b5f392565893a521b238d8e8e1d3 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/nn.po @@ -0,0 +1,28 @@ +# Norwegian Nynorsk translation of GNU hello-ycp +# Copyright (C) 2020 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Karl Ove Hufthammer , 2020. +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp-0.20.2\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2020-05-04 18:58+0200\n" +"Last-Translator: Karl Ove Hufthammer \n" +"Language-Team: Norwegian Nynorsk \n" +"Language: nn\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"X-Generator: Lokalize 20.04.0\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Hei, verda!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Dette programmet køyrer som prosess nummer %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/pl.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/pl.po new file mode 100644 index 0000000000000000000000000000000000000000..fd376acbf3193ae971ade5095eb8f6295af52c6c --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/pl.po @@ -0,0 +1,27 @@ +# Polish translations for the GNU gettext messages, hello-ycp domain +# Copyright (C) 2010, 2014, 2015, 2025 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Rafał Maszkowski , 2003, 2010, 2014, 2015, 2025 +msgid "" +msgstr "" +"Project-Id-Version: GNU hello-ycp 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-25 17:16+0200\n" +"Last-Translator: Rafał Maszkowski \n" +"Language-Team: Polish \n" +"Language: pl\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8-bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=3; plural=(n==1 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 " +"|| n%100>=20) ? 1 : 2);\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Cześć, świecie!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Ten program działa jako proces o numerze %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/pt.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/pt.po new file mode 100644 index 0000000000000000000000000000000000000000..12403591f7089ee5941d5130a33cb28b5bf96270 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/pt.po @@ -0,0 +1,28 @@ +# Portuguese (Portugal) translation of 'hello-ycp' package. +# Copyright (C) 2018 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Pedro Albuquerque , 2019, 2020, 2025. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-28 11:24+0100\n" +"Last-Translator: Pedro Albuquerque \n" +"Language-Team: Portuguese \n" +"Language: pt\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=n != 1;\\n;\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 3.6\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Olá mundo!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Este programa está em execução como processo nº %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/pt_BR.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/pt_BR.po new file mode 100644 index 0000000000000000000000000000000000000000..445140e07e6c31179c6c56b821d11ae683210cb0 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/pt_BR.po @@ -0,0 +1,31 @@ +# Brazilian Portuguese translations for gettext-example +# Traduções em português brasileiro para gettext-example +# Copyright (C) 2025 Yoyodyne, Inc. (msgids) +# Copyright (C) 2025 Free Software Foundation, Inc. +# This file is distributed under the same license as the gettext package. +# Rafael Fontenelle , 2013-2025. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-28 10:24-0300\n" +"Last-Translator: Rafael Fontenelle \n" +"Language-Team: Brazilian Portuguese \n" +"Language: pt_BR\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n > 1);\n" +"X-Generator: Gtranslator 48.0\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Olá, mundo!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Este programa está executando com número de processo %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/ro.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/ro.po new file mode 100644 index 0000000000000000000000000000000000000000..08345f998d1dd1a7c9f1c4b09203e8c3db14cb69 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/ro.po @@ -0,0 +1,50 @@ +# Translation of "hello-ycp" messages to Romanian. +# Mesajele în limba română pentru pachetul hello-ycp. +# Copyright © 2015, 2019, 2022, 2023, 2024, 2025 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Eugen Hoancă , 2003. +# Mihai Cristescu , 2015 - 2019. +# Remus-Gabriel Chelu , 2022 - 2025. +# +# Cronologia traducerii fișierului „hello-ycp”: +# Traducerea inițială, făcută de EH, pentru versiunea hello-ycp 0.12.1, 2003. +# Actualizare a traducerii pentru versiunea hello-ycp 0.19.4-rc1, făcută de MC, mar-2015. +# Actualizare a traducerii pentru versiunea hello-ycp 0.19.4.73, făcută de MC, iun-2015. +# Actualizare a traducerii pentru versiunea hello-ycp 0.20-rc1, făcută de MC, apr-2019. +# Actualizare a mesajelor, de la fișierul „hello-ycp-0.20.2.pot”. +# Actualizare a algoritmului formelor de plural (de la „trei-vechi” la „trei-actual”). +# NU și a mesajelor traduse (acestea au rămas neschimbate). +# Eliminare a mesajelor ce-au dispărut în ultima versiune. +# Actualizări realizate de Remus-Gabriel Chelu , 15.01.2022. +# Actualizare a traducerii pentru versiunea 0.20.2 făcută de R-GC, ian-2022. +# Actualizare a traducerii pentru versiunea 0.22 făcută de R-GC, iun-2023. +# Revizuire și corectare a traducerii pentru versiunea 0.23-pre1 făcută de R-GC, oct-2024. +# Actualizare a traducerii pentru versiunea 0.24-pre1 făcută de R-GC, feb-2025. +# Actualizare a traducerii pentru versiunea 0.25-pre1 făcută de R-GC, apr-2025. +# Actualizare a traducerii pentru versiunea Y, făcută de X, Z(luna-anul). +# +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-29 00:25+0200\n" +"Last-Translator: Remus-Gabriel Chelu \n" +"Language-Team: Romanian \n" +"Language: ro\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=3; plural=(n==1 ? 0 : (n==0 || (n%100 > 0 && n%100 < " +"20)) ? 1 : 2);\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 3.5\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Salutare, lume!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Acest program rulează ca procesul numărul %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/ru.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/ru.po new file mode 100644 index 0000000000000000000000000000000000000000..b0a3861e0aec8a7ac8aafa3be4ec0bf80f52ff3e --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/ru.po @@ -0,0 +1,30 @@ +# Translation of hello-ycp-0.14.1.po to Russian +# Copyright (C) 2004 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Pavel Maryanov , 2004. +# SPDX-FileCopyrightText: 2014, 2015, 2023, 2025 Yuri Kozlov +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-05-02 09:17+0300\n" +"Last-Translator: Yuri Kozlov \n" +"Language-Team: Russian \n" +"Language: ru\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Lokalize 24.12.0\n" +"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && " +"n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Здравствуй, мир!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Эта программа выполняется как процесс под номером %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/sk.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/sk.po new file mode 100644 index 0000000000000000000000000000000000000000..4ea1615159b02e2594ea19d905dead176232748d --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/sk.po @@ -0,0 +1,26 @@ +# Slovak translations GNU for hello-ycp package. +# Copyright (C) 2003, 2004, 2014, 2023, 2025 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Marcel Telka , 2003, 2004, 2014, 2023, 2025. +# +msgid "" +msgstr "" +"Project-Id-Version: GNU hello-ycp 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-28 13:53+0200\n" +"Last-Translator: Marcel Telka \n" +"Language-Team: Slovak \n" +"Language: sk\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Ahoj svet!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Tento program beží ako proces s číslom %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/sl.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/sl.po new file mode 100644 index 0000000000000000000000000000000000000000..3f5d1aea6837355e281e11bff63348e52282c01d --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/sl.po @@ -0,0 +1,29 @@ +# -*- mode: po; coding: utf-8; -*- Slovenian message catalog for GNU gettext-example +# Copyright (C) 2005 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Primož Peterlin , 2005, 2014, 2015, 2024. +# $Id: hello-ycp-0.22.sl.po,v 1.1 2024/03/28 17:02:19 peterlin Exp $ +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp 0.22\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2024-03-28 18:02+0100\n" +"Last-Translator: Primož Peterlin \n" +"Language-Team: Slovenian \n" +"Language: sl\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8-bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=4; plural=(n%100==1 ? 1 : n%100==2 ? 2 : n%100==3 || " +"n%100==4 ? 3 : 0);\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Pozdravljen, svet!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Ta program teče kot proces številka %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/sq.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/sq.po new file mode 100644 index 0000000000000000000000000000000000000000..72904a29a949a6812b8ce859931e823a1c189fb9 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/sq.po @@ -0,0 +1,28 @@ +# Albanian translation of gettext-example. +# Copyright (C) 2020 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Besnik Bleta , 2020,2023,2024,2025. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp-0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-28 19:56+0300\n" +"Last-Translator: Besnik Bleta \n" +"Language-Team: Albanian \n" +"Language: sq\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 3.2.2\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Tungjatjeta, botë!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Ky program po xhiron si procesi numër %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/sr.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/sr.po new file mode 100644 index 0000000000000000000000000000000000000000..006de5d722f56b7e5674f5b78a7f58128a87b7ba --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/sr.po @@ -0,0 +1,30 @@ +# Serbian translation of hello-ycp. +# Copyright (C) 2014 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Aleksandar Jelenak , 2004. +# Мирослав Николић , 2014-2025. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp-0.24-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-03-02 16:51+0100\n" +"Last-Translator: Мирослав Николић \n" +"Language-Team: Serbian <(nothing)>\n" +"Language: sr\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && " +"n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 3.5\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Здраво, свима!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Овај програм се извршава као процес број %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/sv.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/sv.po new file mode 100644 index 0000000000000000000000000000000000000000..5f48c04f6f27b9910fbc7ae2ad9296e333baa564 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/sv.po @@ -0,0 +1,30 @@ +# Swedish messages for hello-ycp. +# Copyright © 2006, 2014, 2016, 2019, 2020, 2023, 2024, 2025 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Jan Djärv , 2003, 2006, 2014. +# Göran Uddeborg , 2016, 2019, 2020, 2023, 2024, 2025. +# Luna Jernberg , 2025. +# $Revision: 1.12 $ +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-28 12:18+0200\n" +"Last-Translator: Luna Jernberg \n" +"Language-Team: Swedish \n" +"Language: sv\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 3.5\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Hej världen!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Detta program kör som process nummer %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/ta.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/ta.po new file mode 100644 index 0000000000000000000000000000000000000000..0430ffd018774fd076a2630036c0aed56229c928 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/ta.po @@ -0,0 +1,28 @@ +# Tamil messages for GNU gettext. +# Copyright (C) 2018 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# List of contributors follow: +# Poorajith , 2018. +# Arun Isaac , 2023. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp 0.22\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2023-06-19 00:06+0100\n" +"Last-Translator: Arun Isaac \n" +"Language-Team: Tamil \n" +"Language: ta\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "வணக்கம், உலகு!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "இந்நிரல் செயலாக்க எண் %1 ஆக இயங்கிக்கொண்டிருக்கிறது." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/tr.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/tr.po new file mode 100644 index 0000000000000000000000000000000000000000..d92dbec2a6968d1a980c3787d39b753ce8a0d10f --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/tr.po @@ -0,0 +1,29 @@ +# Turkish translation for hello-ycp. +# This file is distributed under the same license as the gettext package. +# Copyright (C) 2017 Yoyodyne, Inc. (msgids) +# Copyright (C) 2004 Free Software Foundation, Inc. +# Nilgün Belma Bugüner , 2003,2004 +# Mehmet Kececi , 2017, 2019, 2020. +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp 0.20.2\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2020-04-17 13:10+0300\n" +"Last-Translator: Mehmet Kececi \n" +"Language-Team: Turkish \n" +"Language: tr\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=1; plural=0;\n" +"X-Generator: Poedit 2.3\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Merhaba, dünya!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Bu yazılım %1 süreç numarası ile çalışıyor." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/uk.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/uk.po new file mode 100644 index 0000000000000000000000000000000000000000..07536b5dcc1bd9e2f1b40a6f9bbf0e48f30d477e --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/uk.po @@ -0,0 +1,30 @@ +# Ukrainian translation to hello-ycp +# Copyright (C) 2014 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# +# Maxim V. Dziumanenko , 2004-2007. +# Yuri Chornoivan , 2014, 2015, 2023, 2025. +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-28 13:56+0300\n" +"Last-Translator: Yuri Chornoivan \n" +"Language-Team: Ukrainian \n" +"Language: uk\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && " +"n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n" +"X-Generator: Lokalize 23.04.3\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Привіт, світе!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Ця програма виконується як процес з номером %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/vi.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/vi.po new file mode 100644 index 0000000000000000000000000000000000000000..63530c040169e43f46fc5325de3dc26924bac040 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/vi.po @@ -0,0 +1,30 @@ +# Vietnamese Translation for Gettext Examples. +# Bản dịch tiếng Việt dành cho các ví dụ của gói gettext. +# Copyright © 2015 Yoyodyne, Inc. (msgids) +# Copyright © 2015 Free Software Foundation, Inc. +# This file is distributed under the same license as the gettext package. +# Clytie Siddall , 2005-2010. +# Trần Ngọc Quân , 2012-2015, 2023. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp 0.22\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2023-06-24 09:10+0700\n" +"Last-Translator: Trần Ngọc Quân \n" +"Language-Team: Vietnamese \n" +"Language: vi\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"Plural-Forms: nplurals=1; plural=0;\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "Chào thế giới!" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "Chương trình này đang chạy với mã số tiến trình %1." diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/zh_CN.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/zh_CN.po new file mode 100644 index 0000000000000000000000000000000000000000..fcdbf3ecdeb1ed94d59df714e1e77b24c0dbded6 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/zh_CN.po @@ -0,0 +1,29 @@ +# zh_CN translation for hello-ycp. +# Copyright (C) 2015 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Funda Wang , 2003. +# Ji ZhengYu , 2015. +# Boyuan Yang <073plan@gmail.com>, 2019, 2023, 2025. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp 0.25-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2025-04-29 15:56-0400\n" +"Last-Translator: Boyuan Yang <073plan@gmail.com>\n" +"Language-Team: Chinese (simplified) \n" +"Language: zh_CN\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 3.6\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "你好，世界！" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "此程序正以进程号 %1 运行。" diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/zh_HK.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/zh_HK.po new file mode 100644 index 0000000000000000000000000000000000000000..a667a68d9b5262807300582f9633d5d4ab7cc165 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/zh_HK.po @@ -0,0 +1,25 @@ +# Chinese (Hong Kong) translation of hello-ycp. +# Copyright (C) 2006 Yoyodyne, Inc. +# Abel Cheung , 2006. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp 0.15-pre5\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2006-07-05 15:40+0800\n" +"Last-Translator: Abel Cheung \n" +"Language-Team: Chinese (Hong Kong) \n" +"Language: zh_HK\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "你好！" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "本程式正在執行中，進程編號為 %1。" diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/zh_TW.po b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/zh_TW.po new file mode 100644 index 0000000000000000000000000000000000000000..ad4ab8e4ec4ed73fed49a28e7effa48a46e79c03 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/examples/hello-ycp/po/zh_TW.po @@ -0,0 +1,29 @@ +# Traditional Chinese translation of hello-ycp. +# Copyright (C) 2009 Yoyodyne, Inc. (msgids) +# This file is distributed under the same license as the gettext package. +# Abel Cheung , 2005. +# Wei-Lun Chao , 2013, 2015. +# Yi-Jyun Pan , 2024. +# +msgid "" +msgstr "" +"Project-Id-Version: hello-ycp 0.23-pre1\n" +"Report-Msgid-Bugs-To: bug-gettext@gnu.org\n" +"PO-Revision-Date: 2024-11-30 14:14+0800\n" +"Last-Translator: Yi-Jyun Pan \n" +"Language-Team: Chinese (traditional) \n" +"Language: zh_TW\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 3.5\n" + +#: hello.ycp:15 +msgid "Hello, world!" +msgstr "哈囉，大家好！" + +#: hello.ycp:19 +#, ycp-format +msgid "This program is running as process number %1." +msgstr "本程式正在執行，行程編號為 %1。" diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/allclasses-frame.html b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/allclasses-frame.html new file mode 100644 index 0000000000000000000000000000000000000000..a788935a8ba684267e77fa2662da9dfd4ef4d6e6 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/allclasses-frame.html @@ -0,0 +1,25 @@ + + + + + + +All Classes + + + + + +All Classes +
+ + + + + +
GettextResource +
+
+ + + diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/deprecated-list.html b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/deprecated-list.html new file mode 100644 index 0000000000000000000000000000000000000000..57a2b73782e699e3323498ec55f99a524d89c7cd --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/deprecated-list.html @@ -0,0 +1,87 @@ + + + + + + +: Deprecated List + + + + + + + + + + + + + + + + + +
+ + + + + + + + + +
Class  Tree   Deprecated  Index  Help 
+		 + +
+ PREV  + NEXT + FRAMES   + NO FRAMES
+ + +
+
+

+Deprecated API

+
+
+ + + + + + + + + + + + + +
+ + + + + + + + + +
Class  Tree   Deprecated  Index  Help 
+		 + +
+ PREV  + NEXT + FRAMES   + NO FRAMES
+ + +
+ + + diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/gnu/gettext/GettextResource.html b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/gnu/gettext/GettextResource.html new file mode 100644 index 0000000000000000000000000000000000000000..c1daa903a58a0f0556cdc209d43047e61f890cea --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/gnu/gettext/GettextResource.html @@ -0,0 +1,321 @@ + + + + + + +: Class GettextResource + + + + + + + + + + + + + + + + + + + + + +
+ + + + + + + + + +
 Class  Tree  Deprecated  Index  Help 
+		 + +
+ PREV CLASS  + NEXT CLASS + FRAMES   + NO FRAMES
+ SUMMARY:  INNER | FIELD | CONSTR | METHOD +DETAIL:  FIELD | CONSTR | METHOD
+ + +
+ +

+ +gnu.gettext +
+Class GettextResource

+
+java.lang.Object
+  |
+  +--java.util.ResourceBundle
+        |
+        +--gnu.gettext.GettextResource
+
+
+
+
public abstract class GettextResource
extends java.util.ResourceBundle
+ +

+This class implements the main GNU libintl functions in Java. +

+ Using the GNU gettext approach, compiled message catalogs are normal + Java ResourceBundle classes and are thus interoperable with standard + ResourceBundle based code. +

+ The main differences between the Sun ResourceBundle approach and the + GNU gettext approach are: +

    +
  • In the Sun approach, the keys are abstract textual shortcuts. + In the GNU gettext approach, the keys are the English/ASCII version + of the messages. +
  • In the Sun approach, the translation files are called + "Resource_locale.properties" and have non-ASCII + characters encoded in the Java + \unnnn syntax. Very few editors + can natively display international characters in this format. In the + GNU gettext approach, the translation files are called + "Resource.locale.po" + and are in the encoding the translator has chosen. Many editors + can be used. There are at least three GUI translating tools + (Emacs PO mode, KDE KBabel, GNOME gtranslator). +
  • In the Sun approach, the function + ResourceBundle.getString throws a + MissingResourceException when no translation is found. + In the GNU gettext approach, the gettext function + returns the (English) message key in that case. +
  • In the Sun approach, there is no support for plural handling. + Even the most elaborate MessageFormat strings cannot provide decent + plural handling. In the GNU gettext approach, we have the + ngettext function. +
+

+ To compile GNU gettext message catalogs into Java ResourceBundle classes, + the msgfmt program can be used. +

+

+ +

+ + + + + + + + + + + + + + +
+Field Summary
+static booleanverbose + +
+           
+  + + + + + + + +
Fields inherited from class java.util.ResourceBundle
parent
+  + + + + + + + + + + +
+Constructor Summary
GettextResource() + +
+           
+  + + + + + + + + + + + + + + + +
+Method Summary
+static java.lang.Stringgettext(java.util.ResourceBundle catalog, + java.lang.String msgid) + +
+          Returns the translation of msgid.
+static java.lang.Stringngettext(java.util.ResourceBundle catalog, + java.lang.String msgid, + java.lang.String msgid_plural, + long n) + +
+          Returns the plural form for n of the translation of + msgid.
+  + + + + + + + +
Methods inherited from class java.util.ResourceBundle
getBundle, getBundle, getBundle, getKeys, getLocale, getObject, getString, getStringArray, handleGetObject, setParent
+  + + + + + + + +
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
+  +

+ + + + + + + + +
+Field Detail
+ +

+verbose

+
+public static boolean verbose
+
+
+ + + + + + + + +
+Constructor Detail
+ +

+GettextResource

+
+public GettextResource()
+
+
+ + + + + + + + +
+Method Detail
+ +

+gettext

+
+public static java.lang.String gettext(java.util.ResourceBundle catalog,
+                                       java.lang.String msgid)
+
+
Returns the translation of msgid.
+
Parameters:
catalog - a ResourceBundle
msgid - the key string to be translated, an ASCII string
Returns:
the translation of msgid, or msgid if + none is found
+
+
+
+ +

+ngettext

+
+public static java.lang.String ngettext(java.util.ResourceBundle catalog,
+                                        java.lang.String msgid,
+                                        java.lang.String msgid_plural,
+                                        long n)
+
+
Returns the plural form for n of the translation of + msgid.
+
Parameters:
catalog - a ResourceBundle
msgid - the key string to be translated, an ASCII string
msgid_plural - its English plural form
Returns:
the translation of msgid depending on n, + or msgid or msgid_plural if none is found
+
+
+ +
+ + + + + + + + + + + + + + + + + +
+ + + + + + + + + +
 Class  Tree  Deprecated  Index  Help 
+		 + +
+ PREV CLASS  + NEXT CLASS + FRAMES   + NO FRAMES
+ SUMMARY:  INNER | FIELD | CONSTR | METHOD +DETAIL:  FIELD | CONSTR | METHOD
+ + +
+ + + diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/gnu/gettext/package-frame.html b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/gnu/gettext/package-frame.html new file mode 100644 index 0000000000000000000000000000000000000000..6e2f332a3909b40923a7af8a59c137fd7f76f6af --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/gnu/gettext/package-frame.html @@ -0,0 +1,26 @@ + + + + + + +: Package gnu.gettext + + + + + +gnu.gettext + + + + +
+Classes  + +
+GettextResource
+ + + + diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/gnu/gettext/package-summary.html b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/gnu/gettext/package-summary.html new file mode 100644 index 0000000000000000000000000000000000000000..d4909fa9b55263faa5f2950a98b91c9a0890f9b7 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/gnu/gettext/package-summary.html @@ -0,0 +1,103 @@ + + + + + + +: Package gnu.gettext + + + + + + + + + + + + + + + + + +
+ + + + + + + + + + +
 Package  Class  Tree  Deprecated  Index  Help 
+		 + +
+ PREV PACKAGE  + NEXT PACKAGE + FRAMES   + NO FRAMES
+ + +
+

+Package gnu.gettext +

+ + + + + + + + + +
+Class Summary
GettextResourceThis class implements the main GNU libintl functions in Java. +
+  + +

+

+ + + + + + + + + + + + + +
+ + + + + + + + + + +
 Package  Class  Tree  Deprecated  Index  Help 
+		 + +
+ PREV PACKAGE  + NEXT PACKAGE + FRAMES   + NO FRAMES
+ + +
+ + + diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/gnu/gettext/package-tree.html b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/gnu/gettext/package-tree.html new file mode 100644 index 0000000000000000000000000000000000000000..75a500368dc2f8c4fb857f3c6ed13c96076aa51b --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/gnu/gettext/package-tree.html @@ -0,0 +1,99 @@ + + + + + + +: gnu.gettext Class Hierarchy + + + + + + + + + + + + + + + + + +
+ + + + + + + + + + +
Package  Class   Tree  Deprecated  Index  Help 
+		 + +
+ PREV  + NEXT + FRAMES   + NO FRAMES
+ + +
+
+

+Hierarchy For Package gnu.gettext +

+
+

+Class Hierarchy +

+
    +
  • class java.lang.Object +
+
+ + + + + + + + + + + + + +
+ + + + + + + + + + +
Package  Class   Tree  Deprecated  Index  Help 
+		 + +
+ PREV  + NEXT + FRAMES   + NO FRAMES
+ + +
+ + + diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/help-doc.html b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/help-doc.html new file mode 100644 index 0000000000000000000000000000000000000000..8f09871e43157c67f0b64074942bfe2978984f5b --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/help-doc.html @@ -0,0 +1,136 @@ + + + + + + +: API Help + + + + + + + + + + + + + + + + + +
+ + + + + + + + + +
Class  Tree  Deprecated  Index   Help 
+		 + +
+ PREV  + NEXT + FRAMES   + NO FRAMES
+ + +
+
+

+How This API Document Is Organized

+
+This API (Application Programming Interface) document has pages corresponding to the items in the navigation bar, described as follows.

+Package

+
+ +

+Each package has a page that contains a list of its classes and interfaces, with a summary for each. This page can contain four categories:

    +
  • Interfaces (italic)
  • Classes
  • Exceptions
  • Errors
+
+

+Class/Interface

+
+ +

+Each class, interface, inner class and inner interface has its own separate page. Each of these pages has three sections consisting of a class/interface description, summary tables, and detailed member descriptions:

    +
  • Class inheritance diagram
  • Direct Subclasses
  • All Known Subinterfaces
  • All Known Implementing Classes
  • Class/interface declaration
  • Class/interface description +

    +

  • Inner Class Summary
  • Field Summary
  • Constructor Summary
  • Method Summary +

    +

  • Field Detail
  • Constructor Detail
  • Method Detail
+Each summary entry contains the first sentence from the detailed description for that item. The summary entries are alphabetical, while the detailed descriptions are in the order they appear in the source code. This preserves the logical groupings established by the programmer.
+

+Tree (Class Hierarchy)

+
+There is a Class Hierarchy page for all packages, plus a hierarchy for each package. Each hierarchy page contains a list of classes and a list of interfaces. The classes are organized by inheritance structure starting with java.lang.Object. The interfaces do not inherit from java.lang.Object.
    +
  • When viewing the Overview page, clicking on "Tree" displays the hierarchy for all packages.
  • When viewing a particular package, class or interface page, clicking "Tree" displays the hierarchy for only that package.
+
+

+Deprecated API

+
+The Deprecated API page lists all of the API that have been deprecated. A deprecated API is not recommended for use, generally due to improvements, and a replacement API is usually given. Deprecated APIs may be removed in future implementations.
+

+Index

+
+The Index contains an alphabetic list of all classes, interfaces, constructors, methods, and fields.
+

+Prev/Next

+These links take you to the next or previous class, interface, package, or related page.

+Frames/No Frames

+These links show and hide the HTML frames. All pages are available with or without frames. +

+

+Serialized Form

+Each serializable or externalizable class has a description of its serialization fields and methods. This information is of interest to re-implementors, not to developers using the API. While there is no link in the navigation bar, you can get to this information by going to any serialized class and clicking "Serialized Form" in the "See also" section of the class description. +

+ + +This help file applies to API documentation generated using the standard doclet. + +
+

+ + + + + + + + + + + + + +
+ + + + + + + + + +
Class  Tree  Deprecated  Index   Help 
+		 + +
+ PREV  + NEXT + FRAMES   + NO FRAMES
+ + +
+ + + diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/index-all.html b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/index-all.html new file mode 100644 index 0000000000000000000000000000000000000000..48ebc2e4767a92725ceb75583be1464a653a6311 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/index-all.html @@ -0,0 +1,111 @@ + + + + + + +: Index + + + + + + + + + + + + + + + + + +
+ + + + + + + + + +
Class  Tree  Deprecated   Index  Help 
+		 + +
+ PREV  + NEXT + FRAMES   + NO FRAMES
+ + +G N V
+

+G

+
+
gettext(ResourceBundle, String) - +Static method in class gnu.gettext.GettextResource +
Returns the translation of msgid. +
GettextResource - class gnu.gettext.GettextResource.
This class implements the main GNU libintl functions in Java. +
GettextResource() - +Constructor for class gnu.gettext.GettextResource +
  +
+
+

+N

+
+
ngettext(ResourceBundle, String, String, long) - +Static method in class gnu.gettext.GettextResource +
Returns the plural form for n of the translation of + msgid. +
+
+

+V

+
+
verbose - +Static variable in class gnu.gettext.GettextResource +
  +
+
+G N V + + + + + + + + + + + + +
+ + + + + + + + + +
Class  Tree  Deprecated   Index  Help 
+		 + +
+ PREV  + NEXT + FRAMES   + NO FRAMES
+ + +
+ + + diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/index.html b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/index.html new file mode 100644 index 0000000000000000000000000000000000000000..e3601570fd597ccc1f18242673b3ba952c0fc7ea --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/index.html @@ -0,0 +1,22 @@ + + + + + + +Generated Documentation (Untitled) + + + + + + + +<H2> +Frame Alert</H2> + +<P> +This document is designed to be viewed using the frames feature. If you see this message, you are using a non-frame-capable web client. +<BR> +Link to <A HREF="gnu/gettext/GettextResource.html">Non-frame version.</A> + diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/overview-tree.html b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/overview-tree.html new file mode 100644 index 0000000000000000000000000000000000000000..310db687c30bc614ba8601f6583f88cadc73af04 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/overview-tree.html @@ -0,0 +1,96 @@ + + + + + + +: Class Hierarchy + + + + + + + + + + + + + + + + + +
+ + + + + + + + + +
Class   Tree  Deprecated  Index  Help 
+		 + +
+ PREV  + NEXT + FRAMES   + NO FRAMES
+ + +
+
+

+Hierarchy For All Packages

+
+

+Class Hierarchy +

+
    +
  • class java.lang.Object +
+
+ + + + + + + + + + + + + +
+ + + + + + + + + +
Class   Tree  Deprecated  Index  Help 
+		 + +
+ PREV  + NEXT + FRAMES   + NO FRAMES
+ + +
+ + + diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/package-list b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/package-list new file mode 100644 index 0000000000000000000000000000000000000000..4820a252bfa90931c22cb0406cfb9328e5c1c6f3 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/package-list @@ -0,0 +1 @@ +gnu.gettext diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/packages.html b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/packages.html new file mode 100644 index 0000000000000000000000000000000000000000..4807ba261ffc567053f8286d2846217d4f370c8c --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/packages.html @@ -0,0 +1,26 @@ + + + + + + + + + + + + +
+ +
+ +
+
+The front page has been relocated.Please see: +
+          Frame version +
+          Non-frame version.
+ + + diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/serialized-form.html b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/serialized-form.html new file mode 100644 index 0000000000000000000000000000000000000000..6ce40bc5a2dedbe828b7812ca1a7290323f42c1c --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/serialized-form.html @@ -0,0 +1,87 @@ + + + + + + +Serialized Form + + + + + + + + + + + + + + + + + +
+ + + + + + + + + +
Class  Tree  Deprecated  Index  Help 
+		 + +
+ PREV  + NEXT + FRAMES   + NO FRAMES
+ + +
+
+

+Serialized Form

+
+
+ + + + + + + + + + + + + +
+ + + + + + + + + +
Class  Tree  Deprecated  Index  Help 
+		 + +
+ PREV  + NEXT + FRAMES   + NO FRAMES
+ + +
+ + + diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/stylesheet.css b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/stylesheet.css new file mode 100644 index 0000000000000000000000000000000000000000..95f57649867706e9a2c352c08694bddfcc53f2ca --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/gettext/javadoc2/stylesheet.css @@ -0,0 +1,29 @@ +/* Javadoc style sheet */ + +/* Define colors, fonts and other style attributes here to override the defaults */ + +/* Page background color */ +body { background-color: #FFFFFF } + +/* Table colors */ +.TableHeadingColor { background: #CCCCFF } /* Dark mauve */ +.TableSubHeadingColor { background: #EEEEFF } /* Light mauve */ +.TableRowColor { background: #FFFFFF } /* White */ + +/* Font used in left-hand frame lists */ +.FrameTitleFont { font-size: normal; font-family: normal } +.FrameHeadingFont { font-size: normal; font-family: normal } +.FrameItemFont { font-size: normal; font-family: normal } + +/* Example of smaller, sans-serif font in frames */ +/* .FrameItemFont { font-size: 10pt; font-family: Helvetica, Arial, sans-serif } */ + +/* Navigation bar fonts and colors */ +.NavBarCell1 { background-color:#EEEEFF;}/* Light mauve */ +.NavBarCell1Rev { background-color:#00008B;}/* Dark Blue */ +.NavBarFont1 { font-family: Arial, Helvetica, sans-serif; color:#000000;} +.NavBarFont1Rev { font-family: Arial, Helvetica, sans-serif; color:#FFFFFF;} + +.NavBarCell2 { font-family: Arial, Helvetica, sans-serif; background-color:#FFFFFF;} +.NavBarCell3 { font-family: Arial, Helvetica, sans-serif; background-color:#FFFFFF;} + diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/libtextstyle/libtextstyle_1.html b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/libtextstyle/libtextstyle_1.html new file mode 100644 index 0000000000000000000000000000000000000000..4703389e704b9c21bc674efbaef60cfd4588e690 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/libtextstyle/libtextstyle_1.html @@ -0,0 +1,186 @@ + + + + + +GNU libtextstyle: 1. Introduction + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

1. Introduction

+ +

Text is easier to read when it is accompanied with styling information, +such as color, font attributes (weight, posture), or underlining, and +this styling is customized appropriately for the output device. +

+

GNU libtextstyle provides an easy way to add styling to programs that +produce output to a console or terminal emulator window. It does this +in a way that allows the end user to customize the styling using the +industry standard, namely Cascading Style Sheets (CSS). +

+ + + + +

1.1 Style definitions

+ +

Let's look at the traditional way styling is done for specific programs. +

+

Browsers, when they render HTML, use CSS styling. +

+

The older approach to user-customizable text styling is that the user +associates patterns with escape sequences in an environment variable or a +command-line argument. This is the approach used, for example, by the +GNU ‘ls’ program in combination with the ‘dircolors’ program. +The processing is distributed across several steps: +

    +
  1. +There is default style definition that is hard-coded in the +‘dircolors’ program. The user can also define their own definitions +in a file such as ‘~/.dir_colors’. This style definition contains +explicit terminal escape sequences; thus, it can only be used with +consoles and terminal emulators, and each style definition applies only +to a certain class of mostly-compatible terminal emulators. +
  2. +The dircolors program, when invoked, translates such a style +definition to a sequence of shell statements that sets an environment +variable LS_COLORS. +
  3. +The shell executes these statements, and thus sets the environment +variable LS_COLORS. +
  4. +The program looks at the environment variable and emits the listed escape +sequences. +
+ +

In contrast, this library implements styling as follows: +

    +
  1. +There is a default style definition in a CSS file that is part of the +same package as the stylable program. The user can also define their own +definitions in a CSS file, and set an environment environment variable to +point to it. +
  2. +The program looks at the environment variable, parses the CSS file, +translates the styling specifications to the form that is appropriate for +the output device (escape sequences for terminal emulators, inline CSS +and <span> elements for HTML output), and emits it. +
+ +

Thus, with GNU libtextstyle, the styling has the following properties: +

    +
  • +It is easier for the user to define their own styling, because the file +format is standardized and supported by numerous syntax aware editors. +
  • +A styling file does not depend on the particular output device. An HTML +output and a black-on-white terminal emulator can use the same styling +file. A white-on-black (or even green-on-black) terminal emulator will +need different styling, though. +
  • +It is simpler: There is no need for a program that converts the style +specification from one format to another. +
+ + + + +

1.2 Built-in versus separate styling

+ +

There are generally two approaches for adding styling to text: +

    +
  • +The program that generates the text adds the styling. It does so through +interleaved statements that turn on or off specific attributes. +
  • +The styling gets added by a separate program, that postprocesses the +output. This separate program usually uses regular expressions to +determine which text regions to style with a certain set of text +attributes. +
+ +

The first approach produces a styling that is 100% correct, regardless of +the complexity of the text that is being output. This is the preferred +approach for example for JSON, XML, or programming language text. +

+

The second approach works well if the output has a simple, easy-to-parse +format. It may produce wrong styling in some cases when the text format +is more complex. This approach is often used for viewing log files. +

+

GNU libtextstyle supports both approaches; it includes an example program +for each of the two approaches. +

+ + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on June, 4 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/libtextstyle/libtextstyle_2.html b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/libtextstyle/libtextstyle_2.html new file mode 100644 index 0000000000000000000000000000000000000000..47074aebb08bea457b8bb218678f706def68825b --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/libtextstyle/libtextstyle_2.html @@ -0,0 +1,441 @@ + + + + + +GNU libtextstyle: 2. The end user's perspective + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

2. The end user's perspective

+ +

Styled output can viewed fine in a console or terminal emulator window. +

+

The stylable program will typically have the following options: +

+
--color
+

Use colors and other text attributes always. +

+
--color=when
+

Use colors and other text attributes if when. when may be +always, never, auto, or html. +

+
--style=style-file
+

Specify the CSS style rule file for --color. +

+
+ +

For more details, see the sections The --color option and +The --style option below. +

+

If the output does not fit on a screen, you can use ‘less -R’ to +scroll around in the styled output. For example: +

 
program --color arguments | less -R
+
+ + + + + +

2.1 The environment variable TERM

+ +

The environment variable TERM contains a identifier for the text +window's capabilities. You can get a detailed list of these cababilities +by using the ‘infocmp’ command (for example: infocmp -L1 xterm), +using ‘man 5 terminfo’ as a reference. +

+

When producing text with embedded color directives, a +libtextstyle-enabled program looks at the TERM variable. +Text windows today typically support at least 8 colors. Often, however, +the text window supports 16 or more colors, even though the TERM +variable is set to a identifier denoting only 8 supported colors. It +can be worth setting the TERM variable to a different value in +these cases. +

+

After setting TERM, you can verify how well it works by invoking +‘program --color=test’, where program is any +libtextstyle-enabled program, and seeing whether the output looks +like a reasonable color map. +

+ + + + +

2.1.1 Terminal emulator programs

+ +

The following terminal emulator programs support 256 colors and set +TERM=xterm-256color accordingly: +

+
    +
  • +In GNOME: gnome-terminal, tilda. +
  • +rxvt-unicode (sets TERM=rxvt-unicode-256color). +
  • +st (sets TERM=st-256color). +
  • +QTerminal. +
  • +On macOS: Terminal, iTerm2. +
+ +

The following terminal emulator programs support 256 colors. You only +need to set TERM=xterm-256color or similar; the programs by default +set TERM to a value that supports only 8 colors. +

+
    +
  • +xterm is in many cases built with support for 256 colors. But it +sets TERM=xterm. You need to set TERM=xterm-256color. +
  • +In GNOME: guake (sets TERM=xterm). You need to set +TERM=xterm-256color. +
  • +In KDE: konsole (sets TERM=xterm). You need to set +TERM=xterm-256color or TERM=konsole-256color. +
  • +In KDE: yakuake (sets TERM=xterm). You need to set +TERM=xterm-256color. +
  • +In Enlightenment: Eterm (sets TERM=Eterm). You need to set +TERM=Eterm-256color. +
  • +mlterm (sets TERM=mlterm). You need to set +TERM=mlterm-256color. +
  • +On Windows: PuTTY (sets TERM=xterm). You need to set +TERM=xterm-256color or TERM=putty-256color. +
  • +On Windows: TeraTerm (sets TERM=xterm). You need to set +TERM=xterm-256color. +
+ +

A couple of terminal emulator programs support even the entire RGB color +space (16 million colors). To get this to work, at this date (2019), you +need three things: +

    +
  • +The ncurses library version 6.1 or newer must be installed. +
  • +You need a recent version of the respective terminal emulator program. +See https://github.com/termstandard/colors for the most recent +developments in this area. +
  • +You need to set the TERM environment variable to the corresponding +value: +TERM=xterm-direct instead of +TERM=xterm or TERM=xterm-256color, +TERM=konsole-direct in konsole, +TERM=st-direct in st, +TERM=mlterm-direct in mlterm, +or TERM=iterm2-direct in iTerm2 on macOS. +
+ + + + +

2.1.2 Consoles

+ +

On OpenBSD 6 consoles, TERM=xterm produces better results than the +default TERM=vt220. +

+

On NetBSD 8 consoles, TERM=netbsd6 produces better results than the +default TERM=vt100. +

+

On Windows consoles, no TERM setting is needed. +

+ + + +

2.2 The environment variable NO_COLOR

+ +

The environment variable NO_COLOR can be used to suppress styling +in the textual output. When this environment variable is set (to any value), +libtextstyle-enabled programs will not emit colors and other text +styling. +

+

This environment variable can be overridden by passing the command-line option +‘--color=always’ (see The --color option). +

+ + + +

2.3 The environment variable NO_TERM_HYPERLINKS

+ +

The environment variable NO_TERM_HYPERLINKS can be used to suppress +hyperlinks in the textual output. When this environment variable is set +(to any value), libtextstyle-enabled programs will not emit +hyperlinks. This may be useful for terminal emulators which produce +garbage output when they receive the escape sequence for a hyperlink. +Currently (as of 2019), this affects some versions of +konsole, emacs, lxterminal, guake, yakuake, rxvt.

+ + + +

2.4 Emacs as a terminal emulator

+ +

Emacs has several terminal emulators: M-x shell and +M-x term. M-x term has good support for styling, whereas +in M-x shell most of the styling gets lost. +

+ + + +

2.5 The --color option

+ +

The ‘--color=when’ option specifies under which conditions +styled (colorized) output should be generated. The when part can +be one of the following: +

+
+
always
+
yes
+

The output will be colorized. +

+
+
never
+
no
+

The output will not be colorized. +

+
+
auto
+
tty
+

The output will be colorized if the output device is a tty, i.e. when +the output goes directly to a text screen or terminal emulator window. +

+
+
html
+

The output will be colorized and be in HTML format. This value is only +supported by some programs. +

+
+
test
+

This is a special value, understood only by some programs. It is +explained in the section (The environment variable TERM) above. +

+
+ +

‘--color’ is equivalent to ‘--color=yes’. The default is +‘--color=auto’. +

+

Thus, a command that invokes a libtextstyle-enabled program will +produce colorized output when called by itself in a command window. +Whereas in a pipe, such as ‘program arguments | less -R’, +it will not produce colorized output. To get colorized output in this +situation nevertheless, use the command +‘program --color arguments | less -R’. +

+

The ‘--color=html’ option will produce output that can be viewed in +a browser. This can be useful, for example, for Indic languages, +because the renderic of Indic scripts in browsers is usually better than +in terminal emulators. +

+

Note that the output produced with the --color option is +not consumable by programs that expect the raw text. It contains +additional terminal-specific escape sequences or HTML tags. For example, +an XML parser will give a syntax error when confronted with a colored XML +output. Except for the ‘--color=html’ case, you therefore normally +don't need to save output produced with the --color option in a +file. +

+ + + +

2.6 The --style option

+ +

The ‘--style=style_file’ option specifies the style file to +use when colorizing. It has an effect only when the --color +option is effective. +

+

If the --style option is not specified, the program may consider +the value of an environment variable. It is meant to point to the user's +preferred style for such output. The name of such an environment +variable, if supported, is documented in the documentation of the +libtextstyle-enabled program. +

+

You can also design your own styles. This is described in the next +section. +

+ + + + +

2.6.1 Creating your own style files

+ +

The same style file can be used for styling a certain type of output, for +terminal output and for HTML output. It is written in CSS +(Cascading Style Sheet) syntax. See +https://www.w3.org/TR/CSS2/ for a formal definition of +CSS. Many HTML authoring tutorials also contain explanations of CSS. +

+

In the case of HTML output, the style file is embedded in the HTML output. +In the case of text output, the style file is interpreted by the +libtextstyle-enabled program. +

+

You should avoid @import statements, because +

    +
  • - +In the case of HTML output, the files referenced by the @import +statements would not be embedded in the HTML output. In fact, relative +file names would be interpreted relative to the resulting HTML file. +
  • - +In the case of text output, @imports are not supported, due to a +limitation in libcroco. +
+ +

CSS rules are built up from selectors and declarations. The declarations +specify graphical properties; the selectors specify when they apply. +

+

GNU libtextstyle supports simple selectors based on "CSS classes", see +the CSS2 spec, section 5.8.3. The set of CSS classes that are supported +by a libtextstyle-enabled program are documented in the +documentation of that program. +

+

These selectors can be combined to hierarchical selectors. For example, +assume a program supports the CSS classes string (that matches a +string) and non-ascii (that matches a word with non-ASCII +characters), you could write +

+
 
.string .non-ascii { color: red; }
+
+ +

to highlight only the non-ASCII words inside strings. +

+

In text mode, pseudo-classes (CSS2 spec, section 5.11) and +pseudo-elements (CSS2 spec, section 5.12) are not supported. +

+

The declarations in HTML mode are not limited; any graphical attribute +supported by the browsers can be used. +

+

The declarations in text mode are limited to the following properties. +Other properties will be silently ignored. +

+
+
color (CSS2 spec, section 14.1)
+
background-color (CSS2 spec, section 14.2.1)
+

These properties are supported. Colors will be adjusted to match the +terminal's capabilities. Note that many terminals support only 8 colors. +

+
+
font-weight (CSS2 spec, section 15.2.3)
+

This property is supported, but most terminals can only render two +different weights: normal and bold. Values >= 600 are +rendered as bold. +

+
+
font-style (CSS2 spec, section 15.2.3)
+

This property is supported. The values italic and oblique +are rendered the same way. +

+
+
text-decoration (CSS2 spec, section 16.3.1)
+

This property is supported, limited to the values none and +underline. +

+
+ + + + +

2.6.2 Debugging style files

+ +

If you want to understand why the style rules in a style file produce +the output that you see, you can do so in three steps: +

+
    +
  1. +Run the program with the command-line option --color=html, +redirecting the output to a file. +
  2. +Open the resulting HTML file in a browser. +
  3. +Use the browser's built-in CSS debugging tool. +
      +
    • +In Firefox: From the pop-up menu, select "Inspect Element". +Click somewhere in the DOM tree ("Inspector" tab) and look at the +CSS declarations in the "Rules" tab. +
    • +In Chromium: From the pop-up menu, select "Inspect". +Click somewhere in the DOM tree ("Elements" tab) and look at the +CSS declarations in the "Styles" tab. +
    +
+ +

This technique allows you, in particular, to see which CSS declarations +override which other CSS declarations from other CSS rules. +

+ + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on June, 4 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/libtextstyle/libtextstyle_3.html b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/libtextstyle/libtextstyle_3.html new file mode 100644 index 0000000000000000000000000000000000000000..957e73e24a3908cd00790c39975234a5afc03556 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/libtextstyle/libtextstyle_3.html @@ -0,0 +1,1110 @@ + + + + + +GNU libtextstyle: 3. The programmer's perspective + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

3. The programmer's perspective

+ +

As a programmer, enabling styling consists of the following tasks: +

    +
  1. +Define the command-line options and environment variable that the user +can use to control the styling. +
  2. +Define the CSS classes that the user can use in the CSS file. Each CSS +class corresponds to a text role; each CSS class can be given a different +styling by the user. +
  3. +Change the output routines so that they take an ‘ostream_t’ object +as argument instead of a ‘FILE *’. +
  4. +Insert paired invocations to styled_ostream_begin_css_class, +styled_ostream_end_css_class around each run of text with a +specific text role. +
  5. +Link with libtextstyle. If your package is using GNU autoconf, +you can use the libtextstyle.m4 macro from Gnulib. +
  6. +Prepare a default style file. +
  7. +Update the documentation of your package. +
+ +

The following sections go into more detail. +

+ + + + +

3.1 Basic use of libtextstyle

+ +

Source code that makes use of GNU libtextstyle needs an include statement: +

+
 
#include <textstyle.h>
+
+ +

Basic use of GNU libtextstyle consists of statements like these: +

+
 
  styled_ostream_t stream =
+    styled_ostream_create (STDOUT_FILENO, "(stdout)", TTYCTL_AUTO,
+                           style_file_name);
+  ...
+  styled_ostream_begin_use_class (stream, css_class);
+  ...
+  ostream_write_str (stream, string);
+  ...
+  styled_ostream_end_use_class (stream, css_class);
+  ...
+  styled_ostream_free (stream);
+
+ +

Before this snippet, your code needs to determine the name of the style +file to use (style_file_name). If no styling is desired – the +precise condition depends on the value of color_mode but also on +your application logic –, you should set style_file_name to +NULL. +

+

An object of type styled_ostream_t is allocated. The function +styled_ostream_create allocates it; the function +styled_ostream_free deallocates it. +

+

Such styled_ostream_t supports output operations +(ostream_write_str), interleaved with adding and removing CSS +classes. The CSS class in effect when an output operation is performed +determines, through the style file, the text attributes associated with +that piece of text. +

+ + + + +

3.1.1 Hyperlinks

+ +

Text output may contain hyperlinks. These hyperlinks are encoded through +an escape sequence, specified at +Hyperlinks in terminal emulators. Currently (as of 2024), they are +displayed in many modern terminals, see +OSC8-Adoption. More +terminal emulators will support hyperlinks in the future. Terminal +emulators which don't support hyperlinks ignore it, except for a few +terminal emulators, for which users may need to disable the hyperlinks +(see The environment variable NO_TERM_HYPERLINKS) if the heuristic built into +libtextstyle does not already disable them. +

+

To emit a hyperlink, use code like this: +

+
 
  styled_ostream_t stream = ...
+  ...
+  /* Start a hyperlink.  */
+  styled_ostream_set_hyperlink (stream, url, NULL);
+  ...
+  /* Emit the anchor text.  This can be styled text.  */
+  ostream_write_str (stream, "Click here!");
+  ...
+  /* End the current hyperlink.  */
+  styled_ostream_set_hyperlink (stream, NULL, NULL);
+
+ +

The anchor text can be styled. But the hyperlinks themselves cannot be +styled; they behave as implemented by the terminal emulator. +

+ + + +

3.2 Include files

+ +

The include file <textstyle.h> declares all facilities defined by +the library. +

+ + + +

3.3 Link options

+ +

The library to link with is called libtextstyle, with a +system-dependent suffix. You link with it though link options of the +form -ltextstyle for a library installed in system locations, or +-Llibdir -ltextstyle for a static library installed in other +locations, or -Llibdir -ltextstyle -Wl,-rpath,libdir +for a shared library installed in other locations (assuming a GCC +compatible compiler and linker and no libtool), or +-Llibdir -ltextstyle -Rlibdir for a shared library +installed in other locations (with libtool). Additionally, the +link options may need to include the dependencies: -lm, and +-lncurses or (on NetBSD) -ltermcap or (on AIX) +-lxcurses or (on HP-UX) -lcurses, and on some systems also +-liconv. +

+

It is a bit complicated to determine the right link options in a portable +way. Therefore an Autoconf macro is provided in the file +libtextstyle.m4 in Gnulib, that makes this task easier. Assuming +the build system of your package is based on GNU Autoconf, you invoke it +through gl_LIBTEXTSTYLE. It searches for an installed +libtextstyle. If found, it sets and AC_SUBSTs +HAVE_LIBTEXTSTYLE=yes and the LIBTEXTSTYLE and +LTLIBTEXTSTYLE variables, and augments the CPPFLAGS +variable, and #defines HAVE_LIBTEXTSTYLE to 1. Otherwise, it sets +and AC_SUBSTs HAVE_LIBTEXTSTYLE=no and LIBTEXTSTYLE and +LTLIBTEXTSTYLE to empty. In link commands that use libtool, +use LTLIBTEXTSTYLE; in link commands that don't use libtool, +use LIBTEXTSTYLE. +

+

If you use GNU Automake, the proper place to use the link options is +program_LDADD for programs and library_LIBADD +for libraries. +

+ + + +

3.4 Command-line options

+ +

While you are free to provide any command-line option to enable the +styling of the output, it is good if different GNU programs use the same +command-line options for this purpose. These options are described in +the sections The --color option and The --style option. To +achieve this, use the following API (declared in <textstyle.h>): +

+
+
Variable: bool color_test_mode + +
+

True if a --color option with value test has been seen. +

+ +
+
Variable: enum color_option color_mode + +
+

Stores the value of the --color option. +

+ +
+
Variable: const char * style_file_name + +
+

Stores the value of the --style option. +

+ +

Note: These variables, like any variables exported from shared libraries, +can only be used in executable code. You cannot portably use +their address in initializers of global or static variables. This is a +restriction that is imposed by the Windows, Cygwin, and Android platforms. +

+
+
Function: bool handle_color_option (const char *option) + +
+

You invoke this function when, during argument parsing, you have +encountered a --color or --color=... option. The return +value is an error indicator: true means an invalid option. +

+ +
+
Function: void handle_style_option (const char *option) + +
+

You invoke this function when, during argument parsing, you have +encountered a --style or --style=... option. +

+ +
+
Function: void print_color_test (void) + +
+

Prints a color test page. You invoke this function after argument +parsing, when the color_test_mode variable is true. +

+ +
+
Function: void style_file_prepare (const char *style_file_envvar, const char *stylesdir_envvar, const char *stylesdir_after_install, const char *default_style_file) + +
+

Assigns a default value to style_file_name if necessary. You +invoke this function after argument parsing, when color_test_mode +is false. +

+

style_file_envvar is an environment variable that, when set +to a non-empty value, specifies the style file to use. This environment +variable is meant to be set by the user. +

+

stylesdir_envvar is an environment variable that, when set +to a non-empty value, specifies the directory with the style files, or +NULL. This is necessary for running the testsuite before +‘make install’. +

+

stylesdir_after_install is the directory with the style +files after ‘make install’. +

+

default_style_file is the file name of the default style +file, relative to stylesdir. +

+ + + + +

3.5 The output stream hierarchy

+ +

There are various classes of output streams, some of them with styling +support. These “classes” are defined in an object-oriented programming +style that resembles C++ or Java, but are actually implemented in C with +a little bit of object orientation syntax. These definitions are +preprocessed down to C. As a consequence, GNU libtextstyle is a C +library and does not need to link with the C++ standard library. +

+

All these classes are declared in <textstyle.h>. +

+

The base output stream type is ‘ostream_t’. It is a pointer type to +a (hidden) implementation type. Similarly for the subclasses. +

+

When we say that ‘some_ostream_t’ is a subclass of ‘ostream_t’, +what we mean is: +

    +
  • +Every ‘some_ostream_t’ object can be converted to an +‘ostream_t’, by virtue of a simple assignment. No cast is needed. +
  • +The opposite conversion, from ‘ostream_t’ to ‘some_ostream_t’, +can also be performed, provided that the object is actually an instance +of ‘some_ostream_t’. You can test whether an object is an instance +of ‘some_ostream_t’ by invoking the method +‘bool is_instance_of_some_ostream (ostream_t stream)’. + + + + + + + + + + +
  • +Every method ‘ostream_foobar’ exists also as a method +‘some_ostream_foobar’ with compatible argument types and a +compatible return type. +
+ + + + + +

3.5.1 The abstract ostream class

+ +

The base output stream type is ‘ostream_t’. +

+

It has the following methods: +

+
+
Function: void ostream_write_mem (ostream_t stream, const void *data, size_t len) + +
+

Writes a sequence of bytes to a stream. +

+ +
+
Function: void ostream_write_str (ostream_t stream, const char *string) + +
+

Writes a string's contents to a stream. +

+ +
+
Function: ptrdiff_t ostream_printf (ostream_t stream, const char *format, ...) + +
+
Function: ptrdiff_t ostream_vprintf (ostream_t stream, const char *format, va_list args) + +
+

Writes formatted output to a stream. +

+

These functions return the size of formatted output, or a negative value +in case of an error. +

+ +
+
Function: void ostream_flush (ostream_t stream, ostream_flush_scope_t scope) + +
+

Brings buffered data to its destination. +

+ +
+
Function: void ostream_free (ostream_t stream) + +
+

Closes and frees a stream. +

+ + + + +

3.5.2 The abstract styled_ostream class

+ +

The type for a styled output stream is ‘styled_ostream_t’. It is a +subclass of ‘ostream_t’ that adds the following methods: +

+
+
Function: void styled_ostream_begin_use_class (styled_ostream_t stream, const char *classname) + +
+

Starts a run of text belonging to classname. The +classname is the name of a CSS class. It can be chosen +arbitrarily and customized through the CSS file. +

+ +
+
Function: void styled_ostream_end_use_class (styled_ostream_t stream, const char *classname) + +
+

Ends a run of text belonging to classname. The +styled_ostream_begin_use_class / +styled_ostream_end_use_class calls must match properly. +

+ +
+
Function: const char * styled_ostream_get_hyperlink_ref (styled_ostream_t stream) + +
+

Returns the referred URL of the currently set hyperlink, or NULL +if no hyperlink attribute is currently set. +

+

Note: The returned string is only valid up to the next invocation of +styled_ostream_set_hyperlink. +

+ +
+
Function: const char * styled_ostream_get_hyperlink_id (styled_ostream_t stream) + +
+

Returns the id of the currently set hyperlink, or NULL if no +hyperlink attribute is currently set. +

+

Note: The returned string is only valid up to the next invocation of +styled_ostream_set_hyperlink. +

+ +
+
Function: void styled_ostream_set_hyperlink (styled_ostream_t stream, const char *ref, const char *id) + +
+

Sets or removes a hyperlink attribute. +

+

To set a hyperlink attribute, pass a non-NULL ref. +ref is an URL; it should be at most 2083 bytes long. Non-ASCII +characters should be URI-escaped (using the %nn syntax). id is +an optional identifier. On terminal output, multiple hyperlinks with +the same id will be highlighted together. If specified, id +should be at most 250 bytes long. +

+

To remove a hyperlink attribute, pass NULL for ref and id. +

+

Hyperlinks don't nest. That is, a hyperlink attribute is enabled only +up to the next invocation of styled_ostream_set_hyperlink. +

+ +
+
Function: void styled_ostream_flush_to_current_style (styled_ostream_t stream) + +
+

This function acts like ostream_flush (stream, FLUSH_THIS_STREAM), +except that it leaves the destination with the current text style enabled, +instead of with the default text style. +

+

After calling this function, you can output strings without newlines(!) to the +underlying stream, and they will be rendered like strings passed to +ostream_write_mem, ostream_write_str, or ostream_printf. +

+ + + + +

3.5.3 Concrete ostream subclasses without styling

+ + + + + +

3.5.3.1 The file_ostream class

+ +

The file_ostream class supports output to an <stdio.h> +FILE stream. Its type is ‘file_ostream_t’. It is a subclass +of ‘ostream_t’ that adds no methods. +

+

It can be instantiated through this function: +

+
+
Function: file_ostream_t file_ostream_create (FILE *fp) + +
+

Creates an output stream referring to fp. +

+

Note: The resulting stream must be closed before fp can be +closed. +

+ + + + +

3.5.3.2 The fd_ostream class

+ +

The file_ostream class supports output to a file descriptor. Its +type is ‘fd_ostream_t’. It is a subclass of ‘ostream_t’ that +adds no methods. +

+

It can be instantiated through this function: +

+
+
Function: fd_ostream_t fd_ostream_create (int fd, const char *filename, bool buffered) + +
+

Creates an output stream referring to the file descriptor fd. +

+

filename is used only for error messages. +

+

Note: The resulting stream must be closed before fd can be +closed. +

+ + + + +

3.5.3.3 The term_ostream class

+ +

The term_ostream class supports output to a file descriptor that +is connected to a terminal emulator or console. Its type is +‘term_ostream_t’. It is a subclass of ‘ostream_t’. +

+

It can be instantiated through this function: +

+
+
Function: term_ostream_t term_ostream_create (int fd, const char *filename, ttyctl_t tty_control) + +
+

Creates an output stream referring to the file descriptor fd. +

+

filename is used only for error messages. +

+

tty_control specifies the amount of control to take over the +underlying tty. +

+

The resulting stream will be line-buffered. +

+

Note: The resulting stream must be closed before fd can be +closed. +

+ +

The class adds the following methods: +

+
+
Function: term_color_t term_ostream_rgb_to_color (term_ostream_t stream, int red, int green, int blue) + +
+

Converts an RGB value +(red, green, blue in [0..255]) to +a color, valid for this stream only. +

+ +
+
Function: term_color_t term_ostream_get_color (term_ostream_t stream) + +
+
Function: void term_ostream_set_color (term_ostream_t stream, term_color_t color) + +
+

Gets/sets the text color. +

+ +
+
Function: term_color_t term_ostream_get_bgcolor (term_ostream_t stream) + +
+
Function: void term_ostream_set_bgcolor (term_ostream_t stream, term_color_t color) + +
+

Gets/sets the background color. +

+ +
+
Function: term_weight_t term_ostream_get_weight (term_ostream_t stream) + +
+
Function: void term_ostream_set_weight (term_ostream_t stream, term_weight_t weight) + +
+

Gets/sets the font weight. +

+ +
+
Function: term_posture_t term_ostream_get_posture (term_ostream_t stream) + +
+
Function: void term_ostream_set_posture (term_ostream_t stream, term_posture_t posture) + +
+

Gets/sets the font posture. +

+ +
+
Function: term_underline_t term_ostream_get_underline (term_ostream_t stream) + +
+
Function: void term_ostream_set_underline (term_ostream_t stream, term_underline_t underline) + +
+

Gets/sets the text underline decoration. +

+ +
+
Function: const char * term_ostream_get_hyperlink_ref (term_ostream_t stream) + +
+

Returns the referred URL of the currently set hyperlink, or NULL +if no hyperlink attribute is currently set. +

+

Note: The returned string is only valid up to the next invocation of +term_ostream_set_hyperlink. +

+ +
+
Function: const char * term_ostream_get_hyperlink_id (term_ostream_t stream) + +
+

Returns the id of the currently set hyperlink, or NULL if no +hyperlink attribute is currently set. +

+

Note: The returned string is only valid up to the next invocation of +term_ostream_set_hyperlink. +

+ +
+
Function: void term_ostream_set_hyperlink (term_ostream_t stream, const char *ref, const char *id) + +
+

Sets or removes a hyperlink attribute. +

+

To set a hyperlink attribute, pass a non-NULL ref. +ref is an URL; it should be at most 2083 bytes long. Non-ASCII +characters should be URI-escaped (using the %nn syntax). id is +an optional identifier. Multiple hyperlinks with the same id +will be highlighted together. If specified, id should be at most +250 bytes long. +

+

To remove a hyperlink attribute, pass NULL for ref and id. +

+

Hyperlinks don't nest. That is, a hyperlink attribute is enabled only +up to the next invocation of styled_ostream_set_hyperlink. +

+ +
+
Function: void term_ostream_flush_to_current_style (term_ostream_t stream) + +
+

This function acts like ostream_flush (stream, FLUSH_THIS_STREAM), +except that it leaves the terminal with the current text attributes enabled, +instead of with the default text attributes. +

+

After calling this function, you can output strings without newlines(!) to the +underlying file descriptor, and they will be rendered like strings passed to +ostream_write_mem, ostream_write_str, or ostream_printf. +

+ + + + +

3.5.3.4 The html_ostream class

+ +

The html_ostream class supports output to any destination, in HTML +syntax. Its type is ‘html_ostream_t’. It is a subclass of +‘ostream_t’. +

+

It can be instantiated through this function: +

+
+
Function: html_ostream_t html_ostream_create (ostream_t destination) + +
+

Creates an output stream that takes input in the UTF-8 encoding and +writes it in HTML form on destination. +

+

This stream produces a sequence of lines. The caller is responsible for +opening the <body><html> elements before and for closing them +after the use of this stream. +

+

Note: The resulting stream must be closed before destination +can be closed. +

+ +

The class adds the following methods: +

+
+
Function: void html_ostream_begin_span (html_ostream_t stream, const char *classname) + +
+

Starts a <span class="classname"> element. The +classname is the name of a CSS class. It can be chosen +arbitrarily and customized through the CSS file. +

+ +
+
Function: void html_ostream_end_span (html_ostream_t stream, const char *classname) + +
+

Ends a <span class="classname"> element. +

+

The html_ostream_begin_span / html_ostream_end_span calls +must match properly. +

+ +
+
Function: const char * html_ostream_get_hyperlink_ref (html_ostream_t stream) + +
+

Returns the referred URL of the currently set hyperlink, or NULL +if no hyperlink attribute is currently set. +

+

Note: The returned string is only valid up to the next invocation of +html_ostream_set_hyperlink_ref. +

+ +
+
Function: void html_ostream_set_hyperlink_ref (html_ostream_t stream, const char *ref) + +
+

Sets or removes a hyperlink attribute. +

+

To set a hyperlink attribute, pass a non-NULL ref. +ref is an URL; it should be at most 2083 bytes long. Non-ASCII +characters should be URI-escaped (using the %nn syntax). +

+

To remove a hyperlink attribute, pass NULL for ref. +

+

Hyperlinks don't nest. That is, a hyperlink attribute is enabled only +up to the next invocation of html_ostream_set_hyperlink_ref. +

+ +
+
Function: void html_ostream_flush_to_current_style (html_ostream_t stream) + +
+

This function acts like ostream_flush (stream, FLUSH_THIS_STREAM), +except that it leaves the destination with the current text style enabled, +instead of with the default text style. +

+

After calling this function, you can output strings without newlines(!) to the +underlying stream, and they will be rendered like strings passed to +ostream_write_mem, ostream_write_str, or ostream_printf. +

+ + + + +

3.5.3.5 The memory_ostream class

+ +

The memory_ostream class supports output to an in-memory buffer. +Its type is ‘memory_ostream_t’. It is a subclass of +‘ostream_t’. +

+

It can be instantiated through this function: +

+
+
Function: memory_ostream_t memory_ostream_create (void) + +
+

Creates an output stream that accumulates the output in a memory buffer. +

+ +

The class adds the following method: +

+
+
Function: void memory_ostream_contents (memory_ostream_t stream, const void **bufp, size_t *buflenp) + +
+

Returns a pointer to the output accumulated so far and its size. It +stores them in *bufp and *buflenp, respectively. +

+

Note: These two return values become invalid when more output is done to +the stream or when the stream is freed. +

+ + + + +

3.5.3.6 The iconv_ostream class

+ +

The iconv_ostream class supports output to any destination. Its +type is ‘iconv_ostream_t’. It is a subclass of ‘ostream_t’ +that adds no methods. +

+

It can be instantiated through this function: +

+
+
Function: iconv_ostream_t iconv_ostream_create (const char *from_encoding, const char *to_encoding, ostream_t destination) + +
+

Creates an output stream that converts from from_encoding to +to_encoding, writing the result to destination. +

+

Note: The resulting stream must be closed before destination +can be closed. +

+ + + + +

3.5.4 Concrete styled_ostream subclasses

+ + + + + +

3.5.4.1 The term_styled_ostream class

+ +

The term_styled_ostream class supports styled output to a file +descriptor that is connected to a terminal emulator or console. Its type +is ‘term_styled_ostream_t’. It is a subclass of +‘styled_ostream_t’. +

+

It can be instantiated through this function: +

+
+
Function: term_styled_ostream_t term_styled_ostream_create (int fd, const char *filename, ttyctl_t tty_control, const char *css_filename) + +
+

Creates an output stream referring to the file descriptor fd, +styled with the file css_filename. +

+

filename is used only for error messages. +

+

tty_control specifies the amount of control to take over the +underlying tty. +

+

Note: The resulting stream must be closed before fd can be +closed. +

+

Returns NULL upon failure. +

+ +

The following is a variant of this function. Upon failure, it does not +return NULL; instead, it returns a styled fd_stream on +which the styling operations exist but are no-ops. +

+
+
Function: styled_ostream_t styled_ostream_create (int fd, const char *filename, ttyctl_t tty_control, const char *css_filename) + +
+

Creates an output stream referring to the file descriptor fd, +styled with the file css_filename if possible. +

+

filename is used only for error messages. +

+

tty_control specifies the amount of control to take over the +underlying tty. +

+

Note: The resulting stream must be closed before fd can be +closed. +

+ + + + +

3.5.4.2 The html_styled_ostream class

+ +

The html_styled_ostream class supports styled output to any +destination, in HTML syntax. Its type is ‘html_styled_ostream_t’. +It is a subclass of ‘styled_ostream_t’. +

+

It can be instantiated through this function: +

+
+
Function: html_styled_ostream_t html_styled_ostream_create (ostream_t destination, const char *css_filename) + +
+

Creates an output stream that takes input in the UTF-8 encoding and +writes it in HTML form on destination, styled with the file +css_filename. +

+

Note: The resulting stream must be closed before destination +can be closed. +

+ + + + +

3.5.4.3 The noop_styled_ostream class

+ +

The noop_styled_ostream class supports the styled output operations +to any destination. The text is output to the given destination; the +styling operations, however, do nothing. Its type is +‘noop_styled_ostream_t’. It is a subclass of ‘styled_ostream_t’. +

+

It can be instantiated through this function: +

+
+
Function: noop_styled_ostream_t noop_styled_ostream_create (ostream_t destination, bool pass_ownership) + +
+

Creates an output stream that delegates to destination and +that supports the styling operations as no-ops. +

+

If pass_ownership is true, closing the resulting +stream will automatically close the destination. +

+

Note: If pass_ownership is false, the resulting stream +must be closed before destination can be closed. +

+ + + + +

3.5.5 Accessor functions

+ +

The various concrete stream classes have methods that allow you to retrieve +the arguments passed to the respective constructor function. +

+

Note: While these methods allow you to retrieve the underlying destination +stream of various kinds of stream, it is not recommended to operate on both +the stream and its underlying destination stream at the same time. Doing +so can lead to undesired interactions between the two streams. +

+

The file_ostream class has this accessor method: +

+
+
Function: FILE * file_ostream_get_stdio_stream (file_ostream_t stream) + +
+
+ +

The fd_ostream class has these accessor methods: +

+
+
Function: int fd_ostream_get_descriptor (fd_ostream_t stream) + +
+
+
+
Function: const char * fd_ostream_get_filename (fd_ostream_t stream) + +
+
+
+
Function: bool fd_ostream_is_buffered (fd_ostream_t stream) + +
+
+ +

The term_ostream class has these accessor methods: +

+
+
Function: int term_ostream_get_descriptor (term_ostream_t stream) + +
+
+
+
Function: const char * term_ostream_get_filename (term_ostream_t stream) + +
+
+
+
Function: ttyctl_t term_ostream_get_tty_control (term_ostream_t stream) + +
+
+
+
Function: ttyctl_t term_ostream_get_effective_tty_control (term_ostream_t stream) + +
+

Returns the effective tty control of the stream (not TTYCTL_AUTO). +

+ +

The iconv_ostream class has these accessor methods: +

+
+
Function: const char * iconv_ostream_get_from_encoding (iconv_ostream_t stream) + +
+
+
+
Function: const char * iconv_ostream_get_to_encoding (iconv_ostream_t stream) + +
+
+
+
Function: ostream_t iconv_ostream_get_destination (iconv_ostream_t stream) + +
+
+ +

The html_ostream class has this accessor method: +

+
+
Function: ostream_t html_ostream_get_destination (html_ostream_t stream) + +
+
+ +

The term_styled_ostream class has these accessor methods: +

+
+
Function: term_ostream_t term_styled_ostream_get_destination (term_styled_ostream_t stream) + +
+
+
+
Function: const char * term_styled_ostream_get_css_filename (term_styled_ostream_t stream) + +
+
+ +

The html_styled_ostream class has these accessor methods: +

+
+
Function: ostream_t html_styled_ostream_get_destination (html_styled_ostream_t stream) + +
+
+
+
Function: html_ostream_t html_styled_ostream_get_html_destination (html_styled_ostream_t stream) + +
+
+
+
Function: const char * html_styled_ostream_get_css_filename (html_styled_ostream_t stream) + +
+
+ +

The noop_styled_ostream class has these accessor methods: +

+
+
Function: ostream_t noop_styled_ostream_get_destination (noop_styled_ostream_t stream) + +
+
+
+
Function: bool noop_styled_ostream_is_owning_destination (noop_styled_ostream_t stream) + +
+
+ + + + +

3.6 Debugging the text styling support

+ +

If you want to understand which output of your program is associated with +which CSS classes, the simplest way is as follows: +

+
    +
  1. +Run the program with the command-line option --color=html, +redirecting the output to a file. +
  2. +Then inspect this output. Text regions associated with a CSS class are +surrounded by <span class="css-class">...</span>. +
+ + + + +

3.7 Documenting the text styling support

+ +

To make the text styling support available to the end user of your +package, the following need to be documented: +

    +
  • +The command-line options. This typically needs to be done in several +places: in the ‘--help’ output, in the man pages (if present), +and in the documentation. +
  • +Which programs support ‘--color=test’? +
  • +The list of CSS classes and their meaning. This is necessary, so that +the user can create their own style file; the CSS classes are part of the +selectors in the CSS rules. +
  • +The location of the default style file. This is a convenience, so that +the user, when creating their own style file, can start from the default +one. +
  • +The environment variable, called style_file_envvar above, +that, when set to a non-empty value, specifies the style file to use. +
+ + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on June, 4 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/libtextstyle/libtextstyle_4.html b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/libtextstyle/libtextstyle_4.html new file mode 100644 index 0000000000000000000000000000000000000000..a32f97003db6adcdd8d0f25f98f05fb60898f5ee --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/libtextstyle/libtextstyle_4.html @@ -0,0 +1,1334 @@ + + + + + +GNU libtextstyle: A. Licenses + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

A. Licenses

+ +

The files of this package are covered by the licenses indicated in each +particular file or directory. Here is a summary: +

+
    +
  • +The libtextstyle library and the example programs +are covered by the GNU General Public License (GPL). +A copy of the license is included in GNU GENERAL PUBLIC LICENSE. + +
  • +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 included in GNU Free Documentation License. +
    +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 3 of the License, or (at your option) any later version published +by the Free Software Foundation (FSF). +A copy of the license is included in GNU GENERAL PUBLIC LICENSE. +
+ + + + + + +

A.1 GNU GENERAL PUBLIC LICENSE

+

Version 3, 29 June 2007 +

+ +
 
Copyright © 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

+ +
    +
  1. 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. +

    +
  2. 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. +

    +
  3. 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. +

    +
  4. 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. +

    +
  5. 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. +

    +
  6. 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: +

    +
      +
    1. +The work must carry prominent notices stating that you modified it, +and giving a relevant date. + +
    2. +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”. + +
    3. +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. + +
    4. +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. +

    +
  7. 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: +

    +
      +
    1. +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. + +
    2. +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. + +
    3. +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. + +
    4. +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. + +
    5. +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. +

    +
  8. 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: +

    +
      +
    1. +Disclaiming warranty or limiting liability differently from the terms +of sections 15 and 16 of this License; or + +
    2. +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 + +
    3. +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 + +
    4. +Limiting the use for publicity purposes of names of licensors or +authors of the material; or + +
    5. +Declining to grant rights under trademark law for use of some trade +names, trademarks, or service marks; or + +
    6. +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. +

    +
  9. 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. +

    +
  10. 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. +

    +
  11. 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. +

    +
  12. 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. +

    +
  13. 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. +

    +
  14. 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. +

    +
  15. 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. +

    +
  16. 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. +

    +
  17. 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. +

    +
  18. Interpretation of Sections 15 and 16. + +

    If the disclaimer of warranty and limitation of liability provided +above cannot be given local legal effect according to their terms, +reviewing courts shall apply local law that most closely approximates +an absolute waiver of all civil liability in connection with the +Program, unless a warranty or assumption of liability accompanies a +copy of the Program in return for a fee. +

    +
+ + +

END OF TERMS AND CONDITIONS

+ + +

How to Apply These Terms to Your New Programs

+ +

If you develop a new program, and you want it to be of the greatest +possible use to the public, the best way to achieve this is to make it +free software which everyone can redistribute and change under these +terms. +

+

To do so, attach the following notices to the program. It is safest +to attach them to the start of each source file to most effectively +state the exclusion of warranty; and each file should have at least +the “copyright” line and a pointer to where the full notice is found. +

+
 
one line to give the program's name and a brief idea of what it does.
+Copyright (C) year name of author
+
+This program is free software: you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation, either version 3 of the License, or (at
+your option) any later version.
+
+This program is distributed in the hope that it will be useful, but
+WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with this program.  If not, see https://www.gnu.org/licenses/.
+
+ +

Also add information on how to contact you by electronic and paper mail. +

+

If the program does terminal interaction, make it output a short +notice like this when it starts in an interactive mode: +

+
 
program Copyright (C) year name of author
+This program comes with ABSOLUTELY NO WARRANTY; for details type ‘show w’.
+This is free software, and you are welcome to redistribute it
+under certain conditions; type ‘show c’ for details.
+
+ +

The hypothetical commands ‘show w’ and ‘show c’ should show +the appropriate parts of the General Public License. Of course, your +program's commands might be different; for a GUI interface, you would +use an “about box”. +

+

You should also get your employer (if you work as a programmer) or school, +if any, to sign a “copyright disclaimer” for the program, if necessary. +For more information on this, and how to apply and follow the GNU GPL, see +https://www.gnu.org/licenses/. +

+

The GNU General Public License does not permit incorporating your +program into proprietary programs. If your program is a subroutine +library, you may consider it more useful to permit linking proprietary +applications with the library. If this is what you want to do, use +the GNU Lesser General Public License instead of this License. But +first, please read https://www.gnu.org/licenses/why-not-lgpl.html. + +

+ + +

A.2 GNU Free Documentation License

+

Version 1.3, 3 November 2008 +

+ +
 
Copyright © 2000, 2001, 2002, 2007, 2008 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.
+
+ +
    +
  1. +PREAMBLE + +

    The purpose of this License is to make a manual, textbook, or other +functional and useful document 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. +

    +
  2. +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 +ASCII without markup, Texinfo input format, LaTeX input +format, SGML or XML using a publicly available +DTD, and standard-conforming simple HTML, +PostScript or PDF designed for human modification. Examples +of transparent image formats include PNG, XCF and +JPG. Opaque formats include proprietary formats that can be +read and edited only by proprietary word processors, SGML or +XML for which the DTD and/or processing tools are +not generally available, and the machine-generated HTML, +PostScript or 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. +

    +

    The “publisher” means any person or entity that distributes copies +of the Document to the public. +

    +

    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. +

    +
  3. +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. +

    +
  4. +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. +

    +
  5. +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: +

    +
      +
    1. +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. + +
    2. +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. + +
    3. +State on the Title page the name of the publisher of the +Modified Version, as the publisher. + +
    4. +Preserve all the copyright notices of the Document. + +
    5. +Add an appropriate copyright notice for your modifications +adjacent to the other copyright notices. + +
    6. +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. + +
    7. +Preserve in that license notice the full lists of Invariant Sections +and required Cover Texts given in the Document's license notice. + +
    8. +Include an unaltered copy of this License. + +
    9. +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. + +
    10. +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. + +
    11. +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. + +
    12. +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. + +
    13. +Delete any section Entitled “Endorsements”. Such a section +may not be included in the Modified Version. + +
    14. +Do not retitle any existing section to be Entitled “Endorsements” or +to conflict in title with any Invariant Section. + +
    15. +Preserve any Warranty Disclaimers. +
    + +

    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. +

    +
  6. +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.” +

    +
  7. +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. +

    +
  8. +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. +

    +
  9. +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. +

    +
  10. +TERMINATION + +

    You may not copy, modify, sublicense, or distribute the Document +except as expressly provided under this License. Any attempt +otherwise to copy, modify, sublicense, or distribute it is void, and +will automatically terminate your rights under this License. +

    +

    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, receipt of a copy of some or all of the same material does +not give you any rights to use it. +

    +
  11. +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 +https://www.gnu.org/licenses/. +

    +

    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. If the Document +specifies that a proxy can decide which future versions of this +License can be used, that proxy's public statement of acceptance of a +version permanently authorizes you to choose that version for the +Document. +

    +
  12. +RELICENSING + +

    “Massive Multiauthor Collaboration Site” (or “MMC Site”) means any +World Wide Web server that publishes copyrightable works and also +provides prominent facilities for anybody to edit those works. A +public wiki that anybody can edit is an example of such a server. A +“Massive Multiauthor Collaboration” (or “MMC”) contained in the +site means any set of copyrightable works thus published on the MMC +site. +

    +

    “CC-BY-SA” means the Creative Commons Attribution-Share Alike 3.0 +license published by Creative Commons Corporation, a not-for-profit +corporation with a principal place of business in San Francisco, +California, as well as future copyleft versions of that license +published by that same organization. +

    +

    “Incorporate” means to publish or republish a Document, in whole or +in part, as part of another Document. +

    +

    An MMC is “eligible for relicensing” if it is licensed under this +License, and if all works that were first published under this License +somewhere other than this MMC, and subsequently incorporated in whole +or in part into the MMC, (1) had no cover texts or invariant sections, +and (2) were thus incorporated prior to November 1, 2008. +

    +

    The operator of an MMC Site may republish an MMC contained in the site +under CC-BY-SA on the same site at any time before August 1, 2009, +provided the MMC is eligible for relicensing. +

    +
+ + + +

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: +

+
 
  Copyright (C)  year  your name.
+  Permission is granted to copy, distribute and/or modify this document
+  under the terms of the GNU Free Documentation License, Version 1.3
+  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''.
+
+ +

If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, +replace the “with…Texts.” line with this: +

+
 
    with the Invariant Sections being list their titles, with
+    the Front-Cover Texts being list, and with the Back-Cover Texts
+    being list.
+
+ +

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. +

+ + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on June, 4 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/libtextstyle/libtextstyle_5.html b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/libtextstyle/libtextstyle_5.html new file mode 100644 index 0000000000000000000000000000000000000000..4b93cae4e97c012e4b7715b05b72223ac157819b --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/libtextstyle/libtextstyle_5.html @@ -0,0 +1,222 @@ + + + + + +GNU libtextstyle: Function Index + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

Function Index

+ +
Jump to:   F +   +H +   +I +   +M +   +N +   +O +   +P +   +S +   +T +   +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Index Entry Section
F
fd_ostream_create3.5.3.2 The fd_ostream class
fd_ostream_get_descriptor3.5.5 Accessor functions
fd_ostream_get_filename3.5.5 Accessor functions
fd_ostream_is_buffered3.5.5 Accessor functions
file_ostream_create3.5.3.1 The file_ostream class
file_ostream_get_stdio_stream3.5.5 Accessor functions
H
handle_color_option3.4 Command-line options
handle_style_option3.4 Command-line options
html_ostream_begin_span3.5.3.4 The html_ostream class
html_ostream_create3.5.3.4 The html_ostream class
html_ostream_end_span3.5.3.4 The html_ostream class
html_ostream_flush_to_current_style3.5.3.4 The html_ostream class
html_ostream_get_destination3.5.5 Accessor functions
html_ostream_get_hyperlink_ref3.5.3.4 The html_ostream class
html_ostream_set_hyperlink_ref3.5.3.4 The html_ostream class
html_styled_ostream_create3.5.4.2 The html_styled_ostream class
html_styled_ostream_get_css_filename3.5.5 Accessor functions
html_styled_ostream_get_destination3.5.5 Accessor functions
html_styled_ostream_get_html_destination3.5.5 Accessor functions
I
iconv_ostream_create3.5.3.6 The iconv_ostream class
iconv_ostream_get_destination3.5.5 Accessor functions
iconv_ostream_get_from_encoding3.5.5 Accessor functions
iconv_ostream_get_to_encoding3.5.5 Accessor functions
is_instance_of_fd_ostream3.5 The output stream hierarchy
is_instance_of_file_ostream3.5 The output stream hierarchy
is_instance_of_html_ostream3.5 The output stream hierarchy
is_instance_of_html_styled_ostream3.5 The output stream hierarchy
is_instance_of_iconv_ostream3.5 The output stream hierarchy
is_instance_of_memory_ostream3.5 The output stream hierarchy
is_instance_of_noop_styled_ostream3.5 The output stream hierarchy
is_instance_of_styled_ostream3.5 The output stream hierarchy
is_instance_of_term_ostream3.5 The output stream hierarchy
is_instance_of_term_styled_ostream3.5 The output stream hierarchy
M
memory_ostream_contents3.5.3.5 The memory_ostream class
memory_ostream_create3.5.3.5 The memory_ostream class
N
noop_styled_ostream_create3.5.4.3 The noop_styled_ostream class
noop_styled_ostream_get_destination3.5.5 Accessor functions
noop_styled_ostream_is_owning_destination3.5.5 Accessor functions
O
ostream_flush3.5.1 The abstract ostream class
ostream_free3.5.1 The abstract ostream class
ostream_printf3.5.1 The abstract ostream class
ostream_vprintf3.5.1 The abstract ostream class
ostream_write_mem3.5.1 The abstract ostream class
ostream_write_str3.5.1 The abstract ostream class
P
print_color_test3.4 Command-line options
S
style_file_prepare3.4 Command-line options
styled_ostream_begin_use_class3.5.2 The abstract styled_ostream class
styled_ostream_create3.5.4.1 The term_styled_ostream class
styled_ostream_end_use_class3.5.2 The abstract styled_ostream class
styled_ostream_flush_to_current_style3.5.2 The abstract styled_ostream class
styled_ostream_get_hyperlink_id3.5.2 The abstract styled_ostream class
styled_ostream_get_hyperlink_ref3.5.2 The abstract styled_ostream class
styled_ostream_set_hyperlink3.5.2 The abstract styled_ostream class
T
term_ostream_create3.5.3.3 The term_ostream class
term_ostream_flush_to_current_style3.5.3.3 The term_ostream class
term_ostream_get_bgcolor3.5.3.3 The term_ostream class
term_ostream_get_color3.5.3.3 The term_ostream class
term_ostream_get_descriptor3.5.5 Accessor functions
term_ostream_get_effective_tty_control3.5.5 Accessor functions
term_ostream_get_filename3.5.5 Accessor functions
term_ostream_get_hyperlink_id3.5.3.3 The term_ostream class
term_ostream_get_hyperlink_ref3.5.3.3 The term_ostream class
term_ostream_get_posture3.5.3.3 The term_ostream class
term_ostream_get_tty_control3.5.5 Accessor functions
term_ostream_get_underline3.5.3.3 The term_ostream class
term_ostream_get_weight3.5.3.3 The term_ostream class
term_ostream_rgb_to_color3.5.3.3 The term_ostream class
term_ostream_set_bgcolor3.5.3.3 The term_ostream class
term_ostream_set_color3.5.3.3 The term_ostream class
term_ostream_set_hyperlink3.5.3.3 The term_ostream class
term_ostream_set_posture3.5.3.3 The term_ostream class
term_ostream_set_underline3.5.3.3 The term_ostream class
term_ostream_set_weight3.5.3.3 The term_ostream class
term_styled_ostream_create3.5.4.1 The term_styled_ostream class
term_styled_ostream_get_css_filename3.5.5 Accessor functions
term_styled_ostream_get_destination3.5.5 Accessor functions
+
Jump to:   F +   +H +   +I +   +M +   +N +   +O +   +P +   +S +   +T +   +
+ + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on June, 4 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/libtextstyle/libtextstyle_6.html b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/libtextstyle/libtextstyle_6.html new file mode 100644 index 0000000000000000000000000000000000000000..570a901a4e067eaccc1c1d153d173b5c9e717880 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/libtextstyle/libtextstyle_6.html @@ -0,0 +1,122 @@ + + + + + +GNU libtextstyle: Variable Index + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

Variable Index

+ +
Jump to:   C +   +N +   +S +   +T +   +
+ + + + + + + + + + + + + + + + + +
Index Entry Section
C
color_mode3.4 Command-line options
color_test_mode3.4 Command-line options
N
NO_COLOR, environment variable2.2 The environment variable NO_COLOR
NO_TERM_HYPERLINKS, environment variable2.3 The environment variable NO_TERM_HYPERLINKS
S
style_file_name3.4 Command-line options
T
TERM, environment variable2.1 The environment variable TERM
+
Jump to:   C +   +N +   +S +   +T +   +
+ + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on June, 4 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/libtextstyle/libtextstyle_7.html b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/libtextstyle/libtextstyle_7.html new file mode 100644 index 0000000000000000000000000000000000000000..36dbc1aff8214d64869030a88d897b34a7fe6008 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/libtextstyle/libtextstyle_7.html @@ -0,0 +1,147 @@ + + + + + +GNU libtextstyle: General Index + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

General Index

+ +
Jump to:   - +   +< +   +
+D +   +F +   +G +   +I +   +L +   +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Index Entry Section
-
--color option2.5 The --color option
--style option2.6 The --style option
<
<textstyle.h>3.2 Include files
D
Debugging2.6.2 Debugging style files
Debugging3.6 Debugging the text styling support
F
FDL, GNU Free Documentation LicenseA.2 GNU Free Documentation License
G
GPL, GNU General Public LicenseA.1 GNU GENERAL PUBLIC LICENSE
I
Include file3.2 Include files
L
License, GNU FDLA.2 GNU Free Documentation License
License, GNU GPLA.1 GNU GENERAL PUBLIC LICENSE
LicensesA. Licenses
+
Jump to:   - +   +< +   +
+D +   +F +   +G +   +I +   +L +   +
+ + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on June, 4 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/libtextstyle/libtextstyle_abt.html b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/libtextstyle/libtextstyle_abt.html new file mode 100644 index 0000000000000000000000000000000000000000..dd680b994250d8cc2232f7aa88b84c9ad0705cd6 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/libtextstyle/libtextstyle_abt.html @@ -0,0 +1,167 @@ + + + + + +GNU libtextstyle: About This Document + + + + + + + + + + + + + + + + + + + + +
[Top][Contents][Index][ ? ]
+

About This Document

+

+ This document was generated by Bruno Haible on June, 4 2025 using texi2html 1.78a. +

+

+ The buttons in the navigation panels have the following meaning: +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Button Name Go to From 1.2.3 go to
[ < ] BackPrevious section in reading order1.2.2
[ > ] ForwardNext section in reading order1.2.4
[ << ] FastBackBeginning of this chapter or previous chapter1
[ Up ] UpUp section1.2
[ >> ] FastForwardNext chapter2
[Top] TopCover (top) of document  
[Contents] ContentsTable of contents  
[Index] IndexIndex  
[ ? ] AboutAbout (help)  
+ +

+ where the Example assumes that the current position is at Subsubsection One-Two-Three of a document of the following structure: +

+ +
    +
  • 1. Section One +
      +
    • 1.1 Subsection One-One +
        +
      • ...
        • +
      +
      • +
    • 1.2 Subsection One-Two +
        +
      • 1.2.1 Subsubsection One-Two-One
        • +
      • 1.2.2 Subsubsection One-Two-Two
        • +
      • 1.2.3 Subsubsection One-Two-Three     + <== Current Position
        • +
      • 1.2.4 Subsubsection One-Two-Four
        • +
      +
      • +
    • 1.3 Subsection One-Three +
        +
      • ...
        • +
      +
      • +
    • 1.4 Subsection One-Four
      • +
    +
    • +
+ +
+ + + + + +
[Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on June, 4 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/libtextstyle/libtextstyle_toc.html b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/libtextstyle/libtextstyle_toc.html new file mode 100644 index 0000000000000000000000000000000000000000..ac441887396917a0a8a5dc506ec6240a5d73e943 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/doc/libtextstyle/libtextstyle_toc.html @@ -0,0 +1,146 @@ + + + + + +GNU libtextstyle: GNU libtextstyle + + + + + + + + + + + + + + + + + + + +
[Top][Contents][Index][ ? ]
+

GNU libtextstyle

+ +

Table of Contents

+
+ + +
+ + + + +

This manual documents the GNU libtextstyle library, version +0.25. +

+ + +
+ + + + + +
[Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on June, 4 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/GNOME/team-address b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/GNOME/team-address new file mode 100644 index 0000000000000000000000000000000000000000..0496b5d21c069d6f5c9e4773023468aba6946935 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/GNOME/team-address @@ -0,0 +1,47 @@ +#!/bin/sh +# +# Copyright (C) 2001, 2005, 2010 Free Software Foundation, Inc. +# Written by Bruno Haible , 2001. +# +# 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 . + +# Print the team's address (to stdout) and output additional instructions +# (to stderr). + +projectsdir="$1" +progdir="$2" +catalog="$3" # e.g. "pt_BR" +language="$4" # e.g. "pt" + +url=`cat "$projectsdir/GNOME/teams.url"` +html=`"$progdir/urlget" "$url" "$projectsdir/GNOME/teams.html"` +sed_addnl='s,,\ +,g' +sed_extract_address='s,^.*"/teams/'"$catalog"'">[^<>]*.*]*>\(.*\).*]*>.*.*,\1,p' +address=`echo "$html" | tr '\012' '|' | sed -e "$sed_addnl" | sed -n -e "$sed_extract_address"` +if test -n "$address"; then + (echo "Please consider joining your translation team, and visit" + echo " $address" + echo " https://l10n.gnome.org/" + ) 1>&2 +else + (echo "A translation team for your "`if test "$catalog" = "$language"; then echo "language ($language)"; else echo "local dialect ($catalog)"; fi` + echo "may not exist yet. Please visit" + echo " $url" + echo " https://l10n.gnome.org/" + echo "and decide whether you want to create a new translation team." + ) 1>&2 + address= +fi +exit 0 diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/GNOME/teams.html b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/GNOME/teams.html new file mode 100644 index 0000000000000000000000000000000000000000..6879bf23b2ef7c5c88d59f2559f8d186fe1d417d --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/GNOME/teams.html @@ -0,0 +1,1849 @@ + + + + + + + GNOME Translation Teams + + + + + + + + + + + + +
+ + +
+ +
+ + Log in + +
+ +
+
+ + + +
+ +

GNOME Translation Teams

+ + +

Select a team below to see more information about it:

+ + + +

If anything should be changed on this page, please submit a bug report.

+ + + +
+ +
+ + + +
+ + diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/GNOME/teams.url b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/GNOME/teams.url new file mode 100644 index 0000000000000000000000000000000000000000..0f85a4d931e7fc593a902cee88cb9e8d52641dcc --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/GNOME/teams.url @@ -0,0 +1 @@ +https://l10n.gnome.org/teams/ diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/GNOME/trigger b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/GNOME/trigger new file mode 100644 index 0000000000000000000000000000000000000000..0678561ba306dd626edbe77e264c82f21d490383 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/GNOME/trigger @@ -0,0 +1,55 @@ +#!/bin/sh +# +# Copyright (C) 2001, 2005 Free Software Foundation, Inc. +# Written by Bruno Haible , 2001. +# +# 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 . + +# Test whether the current package is a GNOME package. + +# NLS nuisances: Letter ranges are different in the Estonian locale. +LC_ALL=C + +while true; do + configfiles= + if test -f configure.in; then + configfiles="$configfiles configure.in" + fi + if test -f configure.ac; then + configfiles="$configfiles configure.ac" + fi + if test -n "$configfiles"; then + if grep '^GNOME_' $configfiles >/dev/null 2>&1 ; then + exit 0 + fi + exit 1 + fi + dir=`basename \`pwd\`` + case "$dir" in + i18n) + # This directory name, used in GNU make, is not the top level directory. + ;; + *[A-Za-z]*[0-9]*) + # Reached the top level directory. + exit 1 + esac + # Go to parent directory + last=`/bin/pwd` + cd .. + curr=`/bin/pwd` + if test "$last" = "$curr"; then + # Oops, didn't find the top level directory. + exit 1 + fi +done diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/KDE/team-address b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/KDE/team-address new file mode 100644 index 0000000000000000000000000000000000000000..00cf4e6656073bb42bfe010429b5869b46f58886 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/KDE/team-address @@ -0,0 +1,133 @@ +#!/bin/sh +# +# Copyright (C) 2001 Free Software Foundation, Inc. +# Written by Bruno Haible , 2001. +# +# 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 . + +# Print the team's address (to stdout) and output additional instructions +# (to stderr). + +projectsdir="$1" +progdir="$2" +catalog="$3" # e.g. "pt_BR" +language="$4" # e.g. "pt" + +url=`cat "$projectsdir/KDE/teams.url"` +html=`"$progdir/urlget" "$url" "$projectsdir/KDE/teams.html"` +# The HTML page says they are "presently switching from the 2-letter codes +# to the 3-letter codes". So it is safest to use the English name and +# translate ourselves... +case "$catalog" in + af) english=Afrikaans;; + ar) english=Arabic;; + az) english=Azerbaijani;; + bg) english=Bulgarian;; + bn) english=Bengali;; + bo) english=Tibetan;; + br) english=Breton;; + bs) english=Bosnian;; + ca) english=Catalan;; + cs) english=Czech;; + cy) english=Welsh;; + da) english=Danish;; + de) english=German;; + el) english=Greek;; + en_GB) english="British English";; + eo) english=Esperanto;; + es) english=Spanish;; + et) english=Estonian;; + eu) english=Basque;; + fa) english=Farsi;; + fi) english=Finnish;; + fo) english=Faroese;; + fr) english=French;; + ga) english=Irish;; + gl) english=Gallegan;; + gu) english=Gujarati;; + he) english=Hebrew;; + hi) english=Hindi;; + hr) english=Croatian;; + hu) english=Hungarian;; + id) english=Indonesian;; + is) english=Icelandic;; + it) english=Italian;; + ja) english=Japanese;; + km) english=Khmer;; + ko) english=Korean;; + ku) english=Kurdish;; + lt) english=Lithuanian;; + lv) english=Latvian;; + mi) english=Maori;; + mk) english=Macedonian;; + mr) english=Marathi;; + mt) english=Maltese;; + nl) english=Dutch;; + no) english="Norwegian (Bokm";; + nn) english="Norwegian (Nynorsk)";; + oc) english=Occitan;; + pl) english=Polish;; + pt) english=Portuguese;; + pt_BR) english="Brazilian Portuguese";; + ro) english=Romanian;; + ru) english=Russian;; + sk) english=Slovak;; + sl) english=Slovenian;; + sr) english=Serbian;; + sv) english=Swedish;; + ta) english=Tamil;; + tg) english=Tajik;; + th) english=Thai;; + tr) english=Turkish;; + uk) english=Ukrainian;; + vi) english=Vietnamese;; + # ??) english=Walloon;; + xh) english=Xhosa;; + zh_CN) english="Simplified Chinese";; + zh_TW) english="Traditional Chinese";; + *) english=;; +esac +if test -n "$english"; then + (echo "Please consider joining your translation team, and visit" + sed_addnl='s,,\ +,g' + anchor=`echo "$html" | tr '\012' '|' | sed -e "$sed_addnl" | sed -n -e 's,^.*.*>'"$english"'[^<>]*team<.*$,\1,p'` + if test -n "$anchor"; then + echo " $url#$anchor" + fi + echo " $url" + echo " https://l10n.kde.org/" + ) 1>&2 + address1=`echo "$html" | tr '\012' '|' | sed -n -e 's,^.*>'"$english"'[^<>]*team<\(.*\)$,\1,p' | sed -e "$sed_addnl" | sed -e 2q -e 1d | sed -n -e 's,^.*mailing list\(.*\)$,\1,p' | sed -e 's,.*,,' | sed -e 's,.*,,' | sed -n -e 's,^.*HREF="\([^"]*\)">[^<>]*.*$,\1,p'` + case "$address1" in + mailto:*) address1=`echo "$address1" | sed -e 's,^mailto:,<,' -e 's,$,>,'` ;; + esac + address1=`echo "$address1" | sed -e 's,-request@,@,'` + address2=`echo "$html" | tr '\012' '|' | sed -n -e 's,^.*>'"$english"'[^<>]*team<\(.*\)$,\1,p' | sed -e "$sed_addnl" | sed -e 2q -e 1d | sed -n -e 's,^.*web site\(.*\)$,\1,p' | sed -e 's,.*,,' | sed -e 's,.*,,' | sed -n -e 's,^.*HREF="\([^"]*\)">[^<>]*.*$,\1,p'` + if test -n "$address1" && test -n "$address2"; then + address="$address1 $address2" + else + address="$address1$address2" + fi + # address can be empty or contain 1 or more space separated URLs. +else + (echo "A translation team for your "`if test "$catalog" = "$language"; then echo "language ($language)"; else echo "local dialect ($catalog)"; fi` + echo "may not exist yet. Please visit" + echo " $url" + echo " https://l10n.kde.org/" + echo "and decide whether you want to create a new translation team." + ) 1>&2 + address= +fi +exit 0 diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/KDE/teams.html b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/KDE/teams.html new file mode 100644 index 0000000000000000000000000000000000000000..8924e91ee9afbaaa5ca3816f5da454f94209b877 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/KDE/teams.html @@ -0,0 +1,2036 @@ + + + + + The KDE Translation Teams + + +
+ + + + +
+

The KDE Translation Teams

+

Many KDE applications have been translated to more than 50 + languages already and the number of both the translated applications and + the supported languages is still growing. For information on how complete the + translation of the current KDE user interface to the individual languages + really is please see the respective statistics page. (Documentation translation is still in + its first stages for many teams.) The languages distributed with the last + official KDE version are listed on a separate + page.

+

Almost all language teams are looking for additional + translators. And, of course, there are still a lot of languages missing in KDE. + So if you have some spare time and a good knowledge of English, please consider + joining one of the teams and help translating KDE to your native language. Just + write to the appropriate team coordinator in the list below. If there's no + coordinator listed for your language, take a look at the + Translation HOWTO for more information on + how new languages are introduced to KDE and subscribe to the + mailinglist + for translators and documenters.

+

The team table below is sorted according to the official lists + of ISO 639 language codes. (See + http://lcweb.loc.g + ov/standards/iso639-2/englangn.html). We are + presently switching from the 2-letter codes to the 3-letter codes.) In addition + to the basic team data like the coordinator(s), the + mailing list, and the team's web site, the + list now contains links to:

+
    +
  • compressed archives of all GUI and documentation + files that were already translated by the respective language team; + these files are usually of the type ".po" (GNU gettext) and ".docbook" + (XML)
    • +
  • text files that contain all message strings of the + translated .po files -- these files are sometimes called + "compendia" and are used for instance by specialized + translation programs like KBabel (the + recommended one for KDE translation).
    • +
  • the "highscore list" for each team: an + overview which .po files were already translated but are in need of an + overhaul.
    • +
  • the doc statistics: an overview of the + current status if there are any doc translations available
    • +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
 
afAfrikaans team
  +
araArabic team
  +
azAzerbaijani team
  +
bgBulgarian team
  +
bnBengali team
  +
    +
  • team coordinator(s): + Ahmed, Taneem
    • +
  • mailing list: --
    • +
  • web site: --
    • +
  • .po and doc archive:--
    • +
  • .po messages translated: --
    • +
  • .po files in need of a revision: --
    • +
  • doc statistics: --
    • +
boTibetan team
  +
    +
  • team coordinator(s): Katrin Norbu
    • +
  • mailing list: --
    • +
  • web site: --
    • +
  • .po and doc archive:--
    • +
  • .po messages translated: --
    • +
  • .po files in need of a revision: --
    • +
  • doc statistics: --
    • +
brBreton team
  +
bsBosnian team
  +
caCatalan team
  +
csCzech team
  +
cyWelsh team
  +
daDanish team
  +
deGerman team
  +
elGreek team
  +
en_GBBritish English Team
  +
eoEsperanto team
  +
esSpanish team
  +
etEstonian team
  +
euBasque team
  +
faFarsi (Persian) team
  +
fiFinnish team
  +
foFaroese team
  +
    +
  • coordinator(s): Aki Nielsen
    • +
  • mailing list: --
    • +
  • web site: --
    • +
  • .po and doc archive: --
    • +
  • .po messages translated: --
    • +
  • .po files in need of a revision: --
    • +
  • doc statistics: --
    • +
frFrench team
  +
gaIrish Gaelic team
  +
glGallegan team
  +
guGujarati team
  +
    +
  • coordinator(s): Apu + Shah
    • +
  • mailing list: --
    • +
  • web site: --
    • +
  • .po and doc archive: --
    • +
  • .po messages translated: --
    • +
  • .po files in need of a revision: --
    • +
  • doc statistics: --
    • +
heHebrew team
  +
hiHindi team
  +
    +
  • coordinator(s): Harsh + Kumar
    • +
  • mailing list: --
    • +
  • web site: --
    • +
  • .po and doc archive: --
    • +
  • .po messages translated: --
    • +
  • .po files in need of a revision: --
    • +
  • doc statistics: --
    • +
hrCroatian team
  +
huHungarian team
  +
id/indIndonesian team
  +
isIcelandic team
  +
itItalian team
  +
jaJapanese team
  +
kmKhmer (Cambodian) team
  +
    +
  • coordinator(s): Neang, + Savun
    • +
  • mailing list: kdelist@khmermp3.com (no subscription info + available yet)
    • +
  • web site: kde.khmermp3.com
    • +
  • .po and doc archive: --
    • +
  • .po messages translated: --
    • +
  • .po files in need of a revision: --
    • +
  • doc statistics: --
    • +
koKorean team
  +
kurKurdish team
  +
ltLithuanian team
  +
lvLatvian team
  +
miMaori team
  +
mkMacedonian team
  +
mrMarathi team
  +
    +
  • coordinator(s): Rahul + Palkar
    • +
  • mailing list: --
    • +
  • web site: --
    • +
  • .po and doc archive: --
    • +
  • .po messages translated: --
    • +
  • .po files in need of a revision: --
    • +
  • doc statistics: --
    • +
mtMaltese team
  +
    +
  • coordinator(s): Ramon + Casha
    • +
  • mailing list: --
    • +
  • web site: --
    • +
  • .po and doc archive: --
    • +
  • .po messages translated: --
    • +
  • .po files in need of a revision: --
    • +
  • doc statistics: --
    • +
nlDutch team
  +
noNorwegian (Bokmål) team
  +
no_NYNorwegian (Nynorsk) team
  +
ocOccitan team
  +
plPolish team
  +
ptPortuguese team
  +
pt_BRBrazilian Portuguese team
  +
roRomanian team
  +
ruRussian team
  +
skSlovak team
  +
slSlovenian team
  +
srSerbian team
  +
svSwedish team
  +
taTamil team
  +
tgTajik team
  +
    +
  • coordinator(s): + Roger Kovacs
    • +
  • mailing list: --
    • +
  • web site: www.khujandcomptech.dyn.tj
    • +
  • .po and doc archive:--
    • +
  • .po messages translated: --
    • +
  • .po files in need of a revision: --
    • +
  • doc statistics: --
    • +
thThai team
  +
trTurkish team
  +
ukUkrainian team
  +
viVietnamese team
  +
waWalloon team
  +
xhXhosa team
  +
    +
  • team coordinator(s): Dwayne Bailey
    • +
  • mailing list: --
    • +
  • web site: translate.org.za
    • +
  • .po and doc archive: --
    • +
  • .po messages translated: --
    • +
  • .po files in need of a revision: --
    • +
  • doc statistics: --
    • +
zh_CN.GB2312Simplified Chinese team
  +
zh_TW.Big5Traditional Chinese team
  +
+
Page maintained by + Thomas Diehl. Last update 11 Oktober + 2001
+ diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/KDE/teams.url b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/KDE/teams.url new file mode 100644 index 0000000000000000000000000000000000000000..de9f64d844693b7de7fa994654ad30100a9dd339 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/KDE/teams.url @@ -0,0 +1 @@ +https://l10n.kde.org/teams-list.php diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/KDE/trigger b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/KDE/trigger new file mode 100644 index 0000000000000000000000000000000000000000..afffbf6e50680b558561b575c39ea9ad0e140f52 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/KDE/trigger @@ -0,0 +1,57 @@ +#!/bin/sh +# +# Copyright (C) 2001, 2005 Free Software Foundation, Inc. +# Written by Bruno Haible , 2001. +# +# 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 . + +# Test whether the current package is a KDE package. + +# NLS nuisances: Letter ranges are different in the Estonian locale. +LC_ALL=C + +while true; do + configfiles= + if test -f configure.in; then + configfiles="$configfiles configure.in" + fi + if test -f configure.ac; then + configfiles="$configfiles configure.ac" + fi + if test -n "$configfiles"; then + if grep '^KDE_' $configfiles >/dev/null 2>&1 || \ + grep '^AC_PATH_KDE' $configfiles >/dev/null 2>&1 || \ + grep '^AM_KDE_WITH_NLS' $configfiles >/dev/null 2>&1 ; then + exit 0 + fi + exit 1 + fi + dir=`basename \`pwd\`` + case "$dir" in + i18n) + # This directory name, used in GNU make, is not the top level directory. + ;; + *[A-Za-z]*[0-9]*) + # Reached the top level directory. + exit 1 + esac + # Go to parent directory + last=`/bin/pwd` + cd .. + curr=`/bin/pwd` + if test "$last" = "$curr"; then + # Oops, didn't find the top level directory. + exit 1 + fi +done diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/TP/team-address b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/TP/team-address new file mode 100644 index 0000000000000000000000000000000000000000..fc47e2a95760e8dd12945186de1228f17d82cc8a --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/TP/team-address @@ -0,0 +1,81 @@ +#!/bin/sh +# +# Copyright (C) 2001, 2007, 2019 Free Software Foundation, Inc. +# Written by Bruno Haible , 2001. +# +# 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 . + +# Print the team's address (to stdout) and output additional instructions +# (to stderr). + +projectsdir="$1" +progdir="$2" +catalog="$3" # e.g. "pt_BR" +language="$4" # e.g. "pt" + +url=`cat "$projectsdir/TP/teams.url"` +url_parent=`echo "$url" | sed -e 's,/[^/]*\$,/,'` +url_grandparent=`echo "$url" | sed -e 's,/[^/]*/[^/]*\$,/,'` +sed_absolute_dotdot_urls="s,href=\"\\.\\./,href=${url_grandparent},g" +html=`"$progdir/urlget" "$url" "$projectsdir/TP/teams.html" | sed -e "$sed_absolute_dotdot_urls"` +sed_addnl='s,,\ +,g' +address=`echo "$html" | tr '\012' '|' | sed -e "$sed_addnl" | sed -n -e "s,^.*$catalog[^<>]*[^<>]*.*\$,\\1,p" | sed 1q` +if test -n "$address"; then + case "$address" in + mailto:*) address=`echo "$address" | sed -e 's,^mailto:,<,' -e 's,$,>,'` ;; + esac + (echo "Please visit your translation team's homepage at" + echo " ${url_parent}"`echo "$html" | tr '\012' '|' | sed -e "$sed_addnl" | sed -n -e "s,^.*[^<>]*[^<>]*$catalog.*\$,\\1,p" | sed 1q` + echo " https://translationproject.org/team/index.html" + echo " https://translationproject.org/html/translators.html" + echo " https://translationproject.org/html/welcome.html" + echo "and consider joining your translation team's mailing list" + echo " $address" + ) 1>&2 + echo "$address" + exit 0 +fi +address=`echo "$html" | tr '\012' '|' | sed -e "$sed_addnl" | sed -n -e "s,^.*$language[^<>]*[^<>]*.*\$,\\1,p" | sed 1q` +if test -n "$address"; then + case "$address" in + mailto:*) address=`echo "$address" | sed -e 's,^mailto:,<,' -e 's,$,>,'` ;; + esac + (echo "A translation team exists for your language ($language) but not for" + echo "your local dialect ($catalog). You can either join the existing" + echo "translation team for $language or create a new translation team for $catalog." + echo + echo "Please visit the existing translation team's homepage at" + echo " ${url_parent}"`echo "$html" | tr '\012' '|' | sed -e "$sed_addnl" | sed -n -e "s,^.*[^<>]*[^<>]*$language.*\$,\\1,p" | sed 1q` + echo " https://translationproject.org/team/index.html" + echo " https://translationproject.org/html/translators.html" + echo " https://translationproject.org/html/welcome.html" + echo "and consider joining the translation team's mailing list" + echo " $address" + echo + echo "If you want to create a new translation team for $catalog, please visit" + echo " https://translationproject.org/team/index.html" + echo " https://translationproject.org/html/leaders.html" + echo " https://translationproject.org/html/welcome.html" + ) 1>&2 + echo "$address" + exit 0 +fi +(echo "A translation team for your language ($language) does not exist yet." + echo "If you want to create a new translation team for $language"`test "$catalog" = "$language" || echo " or $catalog"`", please visit" + echo " https://translationproject.org/team/index.html" + echo " https://translationproject.org/html/leaders.html" + echo " https://translationproject.org/html/welcome.html" +) 1>&2 +exit 0 diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/TP/teams.html b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/TP/teams.html new file mode 100644 index 0000000000000000000000000000000000000000..4d85aeb6ad560a626ccce32e066dfb1d34665c89 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/TP/teams.html @@ -0,0 +1,536 @@ + + + + + Translation teams + + + + + +
+ TP Translation Project + You code, we translate. +
+ + + +
+ + +
+

Translation teams

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
LanguageCodeTeam address
Afrikaansafi18n@af.org.za
Albaniansqtranslation-team-sq@lists.sourceforge.net
Amharicamlocales@geez.org
Arabicar(nothing)
Aragoneseansoftaragones@googlegroups.com
Armenianhytranslation-team-hy@lists.sourceforge.net
Assameseas(nothing)
Asturianastalministradores@softastur.org
Azerbaijaniaztranslation-team-az@lists.sourceforge.net
Basqueeutranslation-team-eu@googlegroups.com
Belarusianbedebian-l10n-belarusian@lists.debian.org
Bengalibn(nothing)
Bengali (India)bn_INdiscuss@lists.ankur.org.in
Bosnianbsmtodorov@alu.hr
Brazilian Portuguesept_BRldpbr-translation@lists.sourceforge.net
Bulgarianbgdict@ludost.net
Catalancaca@dodds.net
Chinese (Hong Kong)zh_HK(nothing)
Chinese (simplified)zh_CNi18n-zh@googlegroups.com
Chinese (traditional)zh_TWzh-l10n@lists.slat.org
Crimean Tatar (Crimean Turkish)crhtilde-birlik-tercime@lists.sourceforge.net
Croatianhrlokalizacija@linux.hr
Czechcstranslation-team-cs@lists.sourceforge.net
Danishdadansk@dansk-gruppen.dk
Dutchnlvertaling@vrijschrift.org
English (British)en_GB(nothing)
English (South African)en_ZA(nothing)
Esperantoeotranslation-team-eo@lists.sourceforge.net
Estonianetlinux-ee@lists.eenet.ee
Finnishfitranslation-team-fi@lists.sourceforge.net
Frenchfrtraduc@traduc.org
Friulianfurf.t.public@gmail.com
Galicianglproxecto@trasno.gal
Georgianka(nothing)
Germandetranslation-team-de@lists.sourceforge.net
Greekelteam@lists.gnome.gr
Gujaratiguindianoss-gujarati@lists.sourceforge.net
Hebrewheeliz@gnu.org
Hindihifedora-trans-hi@redhat.com
Hungarianhutranslation-team-hu@lists.sourceforge.net
Icelandicistranslation-team-is@lists.sourceforge.net
Indonesianidtranslation-team-id@lists.sourceforge.net
Interlinguaiatranslation-team-ia@lists.sourceforge.net
Irishgagaeilge-gnulinux@lists.sourceforge.net
Italianittp@lists.linux.it
Japanesejatranslation-team-ja@lists.sourceforge.net
Kannadakndebian-l10n-kannada@lists.debian.org
Kazakhkk(nothing)
Kinyarwandarwtranslation-team-rw@lists.sourceforge.net
Kirghizkyi18n-team-ky-kyrgyz@lists.sourceforge.net
Koreankotranslation-team-ko@googlegroups.com
Kurdishkutranslation-team-ku (at) ferheng.org
Laolo(nothing)
Latvianlvtranslation-team-lv@lists.sourceforge.net
Lithuanianltkomp_lt@konferencijos.lt
Lugandalgkbirabwa@yahoo.co.uk
Macedonianmkufo@linux.net.mk
Malaymstranslation-team-ms@lists.sourceforge.net
Malayalammlsmc-discuss@googlegroups.com
Maltesemttranslation-team-mt@lists.sourceforge.net
Mandarin Chinesecmnhant-l10n@freelists.org
Marathimrsshedmak@redhat.com
Mongolianmnopenmn-translation@lists.sourceforge.net
Nepalinetranslation-team-ne@lists.sourceforge.net
Norwegian Bokmaalnbi18n-nb@lister.ping.uio.no
Norwegian Nynorsknni18n-nn@lister.ping.uio.no
Oriyaortranslation-team-or@lists.sourceforge.net
Pashtopspathanisation@googlegroups.com
Persianfatranslation-team-fa@lists.sourceforge.net
Polishpltranslation-team-pl@lists.sourceforge.net
Portuguesepttranslation-team-pt@lists.sourceforge.net
Punjabipapunjabi-l10n@lists.sourceforge.net
Romanianrotranslation-team-ro@lists.sourceforge.net
Russianrugnu@d07.ru
Scottish Gaelicgdfios@foramnagaidhlig.net
Serbiansr(nothing)
Slovaksksk-i18n@lists.linux.sk
Sloveniansltranslation-team-sl@lists.sourceforge.net
Spanisheses@tp.org.es
Swahiliswtranslation-team-sw@lists.sourceforge.net
Swedishsvtp-sv@listor.tp-sv.se
Tajiktgrkovacs@khujand.org
Tamiltatamil@systemreboot.net
Telugute(nothing)
Thaiththai-l10n@googlegroups.com
Tibetanbotranslation-team-bo@lists.sourceforge.net
Turkishtrgnu-tr-u12a@lists.sourceforge.net
Ukrainianuktranslation-team-uk@lists.sourceforge.net
Urduurjessbody@gmail.com
Uzbekuzhamza.foziljonov@gmail.com
Vietnamesevitranslation-team-vi@lists.sourceforge.net
Walloonwalinux-wa@walon.org
Wolofwotranslation-team-wo@lists.sourceforge.net
+
+
+ +
+
Your comments are welcome.
+
Last updated on 2019-01-20 09:30 +0100.
+
+ + diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/TP/teams.url b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/TP/teams.url new file mode 100644 index 0000000000000000000000000000000000000000..9471a22a4771995f0267650ab2c0f6d73134d11f --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/TP/teams.url @@ -0,0 +1 @@ +https://translationproject.org/team/index.html diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/TP/trigger b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/TP/trigger new file mode 100644 index 0000000000000000000000000000000000000000..4486daf92a49fc2a07c5a1884fb71a1edfef085b --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/TP/trigger @@ -0,0 +1,3 @@ +#!/bin/sh +# All translations not belonging to other projects are welcome in the TP. +true diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/index b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/index new file mode 100644 index 0000000000000000000000000000000000000000..9b56e1303f825e2983865fc42646681dde6e2967 --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/index @@ -0,0 +1,3 @@ +KDE +GNOME +TP diff --git a/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/team-address b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/team-address new file mode 100644 index 0000000000000000000000000000000000000000..f6bc8af84ac308723d98db1607562ac3594b6acb --- /dev/null +++ b/miniconda3/pkgs/gettext-0.25.1-h92eb808_0/share/gettext/projects/team-address @@ -0,0 +1,34 @@ +#!/bin/sh +# +# Copyright (C) 2001 Free Software Foundation, Inc. +# Written by Bruno Haible , 2001. +# +# 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 . + +# Print the team's address (to stdout) and output additional instructions +# (to stderr). + +projectsdir="$1" +progdir="$2" +catalog="$3" # e.g. "pt_BR" +language="$4" # e.g. "pt" + +for project in `cat "$projectsdir/index"`; do + if /bin/sh "$projectsdir/$project/trigger"; then + /bin/sh "$projectsdir/$project/team-address" "$projectsdir" "$progdir" "$catalog" "$language" + exit $? + fi +done + +exit 0 diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/autopoint b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/autopoint new file mode 100644 index 0000000000000000000000000000000000000000..36d292ab993c7c4b9ef3cee710b7e851d950f85a --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/autopoint @@ -0,0 +1,853 @@ +#! /bin/sh +# +# Copyright (C) 2002-2025 Free Software Foundation, Inc. +# +# 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 . +# + +# This file is meant for authors, maintainers, co-maintainers or installers +# of packages which are internationalized with the help of GNU gettext. For +# further information how to use it consult the GNU gettext manual. + +progname=$0 +package=gettext-tools +version=0.25.1 +archive_version=0.25.1 + +# Set variables +# - gettext_datadir directory where the data files are stored. +prefix="/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho" +datarootdir="${prefix}/share" +: ${gettext_datadir="${datarootdir}/gettext"} +: ${AUTOM4TE=autom4te} + +# func_tmpdir +# creates a temporary directory. +# Sets variable +# - tmp pathname of freshly created temporary directory +func_tmpdir () +{ + # Use the environment variable TMPDIR, falling back to /tmp. This allows + # users to specify a different temporary directory, for example, if their + # /tmp is filled up or too small. + : ${TMPDIR=/tmp} + { + # Use the mktemp program if available. If not available, hide the error + # message. + tmp=`(umask 077 && mktemp -d "$TMPDIR/gtXXXXXX") 2>/dev/null` && + test -n "$tmp" && test -d "$tmp" + } || + { + # Use a simple mkdir command. It is guaranteed to fail if the directory + # already exists. $RANDOM is bash specific and expands to empty in shells + # other than bash, ksh and zsh. Its use does not increase security; + # rather, it minimizes the probability of failure in a very cluttered /tmp + # directory. + tmp=$TMPDIR/gt$$-$RANDOM + (umask 077 && mkdir "$tmp") + } || + { + echo "$0: cannot create a temporary directory in $TMPDIR" >&2 + { (exit 1); exit 1; } + } +} + +# Support for relocatability. +func_find_curr_installdir () +{ + # Determine curr_installdir, even taking into account symlinks. + curr_executable="$0" + case "$curr_executable" in + */* | *\\*) ;; + *) # Need to look in the PATH. + save_IFS="$IFS"; IFS="${PATH_SEPARATOR=':'}" + for dir in $PATH; do + IFS="$save_IFS" + test -z "$dir" && dir=. + for exec_ext in ''; do + if test -f "$dir/$curr_executable$exec_ext"; then + curr_executable="$dir/$curr_executable$exec_ext" + break 2 + fi + done + done + IFS="$save_IFS" + ;; + esac + # Make absolute. + case "$curr_executable" in + /* | ?:/* | ?:\\*) ;; + *) curr_executable=`pwd`/"$curr_executable" ;; + esac + # Resolve symlinks. + sed_dirname='s,/[^/]*$,,' + sed_linkdest='s,^.* -> \(.*\),\1,p' + while : ; do + lsline=`LC_ALL=C ls -l "$curr_executable"` + case "$lsline" in + *" -> "*) + linkdest=`echo "$lsline" | sed -n -e "$sed_linkdest"` + case "$linkdest" in + /* | ?:/* | ?:\\*) curr_executable="$linkdest" ;; + *) curr_executable=`echo "$curr_executable" | sed -e "$sed_dirname"`/"$linkdest" ;; + esac ;; + *) break ;; + esac + done + curr_installdir=`echo "$curr_executable" | sed -e 's,/[^/]*$,,'` + # Canonicalize. + curr_installdir=`cd "$curr_installdir" && pwd` +} +func_find_prefixes () +{ + # Compute the original/current installation prefixes by stripping the + # trailing directories off the original/current installation directories. + orig_installprefix="$orig_installdir" + curr_installprefix="$curr_installdir" + while true; do + orig_last=`echo "$orig_installprefix" | sed -n -e 's,^.*/\([^/]*\)$,\1,p'` + curr_last=`echo "$curr_installprefix" | sed -n -e 's,^.*/\([^/]*\)$,\1,p'` + if test -z "$orig_last" || test -z "$curr_last"; then + break + fi + if test "$orig_last" != "$curr_last"; then + break + fi + orig_installprefix=`echo "$orig_installprefix" | sed -e 's,/[^/]*$,,'` + curr_installprefix=`echo "$curr_installprefix" | sed -e 's,/[^/]*$,,'` + done +} +if test "no" = yes; then + exec_prefix="${prefix}" + bindir="${exec_prefix}/bin" + orig_installdir="$bindir" # see Makefile.am's *_SCRIPTS variables + func_find_curr_installdir # determine curr_installdir + func_find_prefixes + # Relocate the directory variables that we use. + gettext_datadir=`echo "$gettext_datadir/" | sed -e "s%^${orig_installprefix}/%${curr_installprefix}/%" | sed -e 's,/$,,'` +fi + +# func_trace_autoconf macro configure.ac +# traces an Autoconf macro call and outputs the arguments to stdout, +# using autom4te. +func_trace_autoconf () +{ + echo '\ +dnl replace macros which may abort autom4te with a no-op variant +m4_pushdef([m4_assert]) +m4_pushdef([m4_fatal]) +m4_pushdef([m4_warn]) +m4_pushdef([m4_errprintn]) +m4_pushdef([m4_exit]) +m4_pushdef([m4_include]) +m4_pushdef([m4_esyscmd]) +' \ + | "$AUTOM4TE" --no-cache --language=Autoconf-without-aclocal-m4 \ + --trace="$1":\$% - "$2" 2>/dev/null +} + +# func_trace_sed macro configure.ac +# traces an Autoconf macro call and outputs the arguments to stdout, +# using sed. For a macro call without arguments, print just a blank line. +func_trace_sed () +{ + sed_extract_arguments=' +s,#.*$,, +s,^dnl .*$,, +s, dnl .*$,, +/'"$1"'(/ { + ta + :a + s/)/)/ + tb + s/\\$// + N + ba + :b + s,^.*'"$1"'([[ ]*\([^]"$`\\)]*\).*$,\1,p +} +/'"$1"'[^A-Za-z0-9_(]/ s,^.*$,,p +/'"$1"'$/ s,^.*$,,p +d' + sed -e "$sed_extract_arguments" "$2" +} + +# func_usage +# outputs to stdout the --help usage message. +func_usage () +{ + echo "\ +Usage: autopoint [OPTION]... + +Copies standard gettext infrastructure files into a source package. + +Options: + --help print this help and exit + --version print version information and exit + -f, --force force overwriting of files that already exist + -n, --dry-run print modifications but don't perform them" +# echo "\ +# -V version copy the infrastructure of the specified gettext version +# (dangerous)" + echo " +Report bugs in the bug tracker at +or by email to ." +} + +# func_version include_config_details +# outputs to stdout the --version message. +# Inputs: +# - include_config_details true or false +func_version () +{ + echo "$progname (GNU $package) $version" + if $1; then + echo "This binary is configured to use a versions archive in dirxz format." + echo + fi + echo "Copyright (C) 2002-2025 Free Software Foundation, Inc. +License GPLv3+: GNU GPL version 3 or later +This is free software: you are free to change and redistribute it. +There is NO WARRANTY, to the extent permitted by law." + echo "Written by" "Bruno Haible" +} + +# func_fatal_error message +# outputs to stderr a fatal error message, and terminates the program. +func_fatal_error () +{ + echo "autopoint: *** $1" 1>&2 + echo "autopoint: *** Stop." 1>&2 + exit 1 +} + +# Nuisances. +(unset CDPATH) >/dev/null 2>&1 && unset CDPATH + +# Unset more variables known to interfere with behavior of common tools. +CLICOLOR_FORCE= GREP_OPTIONS= +unset CLICOLOR_FORCE GREP_OPTIONS + +# Command-line option processing. +# Removes the OPTIONS from the arguments. Sets the variables: +# - force yes if --force was given, empty otherwise +# - ver gettext version if -V was given, empty otherwise +# - doit false if --dry-run was given, : otherwise +{ + force= + ver= + doit=: + + while test $# -gt 0; do + case "$1" in + -n | --dry-run | --dry-ru | --dry-r | --dry- | --dry | --dr | --d ) + shift + doit=false ;; + -f | --force | --forc | --for | --fo | --f ) + shift + force=yes ;; + --help | --hel | --he | --h ) + func_usage; exit 0 ;; +# -V ) # Some people put a space between -V and the version number. +# shift +# if test $# = 0; then +# func_usage 1>&2 +# exit 1 +# fi +# ver=$1; +# shift ;; +# -V*) # Some people omit the space between -V and the version number. +# ver=`echo "X$1" | sed -e 's/^X-V//'` +# shift ;; + --version-without-config ) + # Print version output without build dependent details. + func_version false + exit 0 ;; + --version | --versio | --versi | --vers | --ver | --ve | --v ) + func_version true + exit 0 ;; + -- ) # Stop option prcessing + shift; break ;; + -* ) + echo "autopoint: unknown option $1" 1>&2 + echo "Try 'autopoint --help' for more information." 1>&2 + exit 1 ;; + * ) + break ;; + esac + done +} + +# Command-line argument processing. +# Analyzes the remaining arguments. +{ + if test $# -gt 0; then + func_usage 1>&2 + exit 1 + fi +} + +srcdir=`pwd` +# The current directory is now $srcdir. + +# Check integrity of package: A configure.in/ac must be present. Sets variable +# - configure_in name of configure.in/ac file. +if test -f configure.ac; then + configure_in=configure.ac +else + if test -f configure.in; then + configure_in=configure.in + else + # KDE specific convention: configure.in.in + if test -f configure.in.in; then + configure_in=configure.in.in + else + func_fatal_error "Missing configure.ac or configure.in, please cd to your package first." + fi + fi +fi + +# Select the method for Autoconf macro tracing. func_trace_autoconf +# is more accurate than func_trace_sed, but it only works with +# autoconf >= 2.69. +if echo "AC_PREREQ([2.69])" \ + | "$AUTOM4TE" --no-cache --language=Autoconf-without-aclocal-m4 - 2>&1; then + func_trace=func_trace_autoconf +else + func_trace=func_trace_sed +fi + +# func_version_prereq required_version version +# compares the required version and the latest archive version. +func_version_prereq () +{ + req="$1" + ver="$2" + echo "m4_if(m4_version_compare([$ver], [$req]), [-1], [m4_exit([1])])" \ + | "$AUTOM4TE" --language=M4sugar >/dev/null +} + +# If AM_GNU_GETTEXT_REQUIRE_VERSION is used and archive_version is newer than +# that, use archive_version. +xreq=`func_trace_sed AM_GNU_GETTEXT_REQUIRE_VERSION "$configure_in"` + +# Need to use func_trace_sed instead of $func_trace, since +# AM_GNU_GETTEXT_VERSION is not a standard Autoconf trace. +xver=`func_trace_sed AM_GNU_GETTEXT_VERSION "$configure_in"` + +# Prefer AM_GNU_GETTEXT_REQUIRE_VERSION over AM_GNU_GETTEXT_VERSION if both are +# specified. +if test -n "$xreq" && test -n "$xver"; then + echo "autopoint: using AM_GNU_GETTEXT_REQUIRE_VERSION instead of AM_GNU_GETTEXT_VERSION" +fi + +if test -n "$xreq"; then + if func_version_prereq "$xreq" "$archive_version"; then + ver="$archive_version" + else + func_fatal_error "gettext version $xreq or newer is required" + fi +else + if test -z "$xver" && test -f intl/VERSION; then + xver=`cat intl/VERSION | LC_ALL=C sed -n -e 's/^.*gettext-\([-+_.0-9A-Za-z]*\).*$/\1/p'` + fi + + # Check whether the -V option and the version number in configure.in match. + # At least one of the two must be given. If both are given, they must agree. + + if test -n "$xver"; then + if test -n "$ver"; then + if test "X$ver" != "X$xver"; then + func_fatal_error "Version mismatch: specified -V $ver but the package uses gettext version $xver" + fi + else + ver="$xver" + fi + fi +fi + +if test -z "$ver"; then + # The $configure_in does not specify an AM_GNU_GETTEXT_VERSION. + # This is OK in two cases: + # - The package uses an old gettext infrastructure (from 2024 or earlier). + # - The package merely uses AM_ICONV, not AM_GNU_GETTEXT. + # Use the last version whose po.m4 is nearly identical to the older ones. + ver=0.23.1 +fi + +# Check whether the version number is supported. +case "$ver" in + 0.10.35 | 0.10.36 | 0.10.37 | 0.10.38 | 0.10.39 | 0.10.40 | \ + 0.11 | 0.11.1 | 0.11.2 | 0.11.3 | 0.11.4 | 0.11.5 | \ + 0.12 | 0.12.1 | \ + 0.13 | 0.13.1 | \ + 0.14 | 0.14.1 | 0.14.2 | 0.14.3 | 0.14.4 | 0.14.5 | 0.14.6 | \ + 0.15 | \ + 0.16 | 0.16.1 | \ + 0.17 | \ + 0.18 | 0.18.1 | 0.18.2 | 0.18.3 | \ + 0.19 | 0.19.1 | 0.19.2 | 0.19.3 | 0.19.4 | 0.19.5 | 0.19.6 | 0.19.7 | 0.19.8 | \ + 0.20 | 0.20.2 | \ + 0.21 | 0.21.1 | \ + 0.22 | 0.22.1 | 0.22.2 | 0.22.3 | 0.22.4 | 0.22.5 | \ + 0.23 | 0.23.1 | 0.23.2 | \ + 0.24 | 0.24.1 | 0.24.2 | \ + 0.25 | 0.25.1 ) + ;; + *) + func_fatal_error "The AM_GNU_GETTEXT_VERSION declaration in your $configure_in + file requires the infrastructure from gettext-$ver but this version + is older. Please upgrade to gettext-$ver or newer." + ;; +esac + +# Check in which directory config.rpath, mkinstalldirs etc. belong. +auxdir=`"$func_trace" AC_CONFIG_AUX_DIR "$configure_in"` +if test -n "$auxdir"; then + auxdir="$auxdir/" +fi + +# Check in which directory the *.m4 macros belong. +macrodirs=`"$func_trace" AC_CONFIG_MACRO_DIR_TRACE "$configure_in"` +if test -z "$macrodirs"; then + macrodirs=`"$func_trace" AC_CONFIG_MACRO_DIR "$configure_in"` +fi +for arg in $macrodirs; do + m4dir="$arg" + break +done + +if test -z "$m4dir" && test -f Makefile.am; then + # A package using automake. + # Extract the macro directory name from Makefile.am. + aclocal_amflags=`grep '^ACLOCAL_AMFLAGS[ ]*=' Makefile.am | sed -e 's/^ACLOCAL_AMFLAGS[ ]*=\(.*\)$/\1/'` + m4dir_is_next= + for arg in $aclocal_amflags; do + if test -n "$m4dir_is_next"; then + m4dir="$arg" + break + else + if test "X$arg" = "X-I"; then + m4dir_is_next=yes + else + m4dir_is_next= + fi + fi + done +fi + +if test -z "$m4dir"; then + m4dir=m4 +fi + +# Check whether to omit the intl/ directory. +omitintl= +# Need to use func_trace_sed instead of $func_trace, since +# AM_GNU_GETTEXT is not a standard Autoconf trace. +if test `func_trace_sed AM_GNU_GETTEXT "$configure_in" | wc -l` = 0; then + # No AM_GNU_GETTEXT invocation. + omitintl=yes +else + xargs=`func_trace_sed AM_GNU_GETTEXT "$configure_in"` + save_IFS="$IFS"; IFS=: + for arg in $xargs; do + if test 'external' = "$arg"; then + omitintl=yes + break + fi + done + IFS="$save_IFS" +fi + +if test -z "$omitintl"; then + case "$ver" in + 0.1[0-9] | 0.1[0-9].* ) ;; + *) func_fatal_error "AM_GNU_GETTEXT without 'external' argument is no longer supported in version $ver" ;; + esac +fi + +# Check in which directory or directories the po/* infrastructure belongs. +configfiles=`"$func_trace" AC_CONFIG_FILES "$configure_in"` +# PO directories have a Makefile.in generated from Makefile.in.in. +# Treat a directory as a PO directory if and only if it has a +# POTFILES.in file. This allows packages to have multiple PO +# directories under different names or in different locations. +sed_remove_Makefile_in='s,/Makefile\.in$,,' +podirs=`for f in $configfiles; do case "$f" in */Makefile.in) echo $f;; esac; done | sed -e "$sed_remove_Makefile_in"` +if test -z "$podirs"; then + # If we cannot get the list of PO directories from configure.ac, assume the + # common default. + podirs="po" +fi + +# Set up a temporary checkout directory. +# Set variables +# - work_dir directory containing the temporary checkout +work_dir=tmpwrk$$ +mkdir "$work_dir" || { + if test -d "$work_dir"; then + func_fatal_error "directory $work_dir already exists" + else + func_fatal_error "cannot create directory $work_dir" + fi +} + +# We support three archive formats. +# +# Format | Size (KiB) for gettext-0.17 | Extra tools needed | +# -------+-----------------------------+--------------------+ +# dir | 3000 | -- | +# cvs | 356 | cvs | +# git | 484 | git | +# -------+-----------------------------+--------------------+ + +case "dirxz" in + dir*) + # The archive of different versions is very large (unless xz compression is + # used), but using it does not require special tools. + case "dirxz" in + dirgz) gzip -d -c < "$gettext_datadir/archive.dir.tar.gz" ;; + dirbz2) bzip2 -d -c < "$gettext_datadir/archive.dir.tar.bz2" ;; + dirxz) xz -d -c < "$gettext_datadir/archive.dir.tar.xz" ;; + esac \ + | (cd "$work_dir" && tar xf - "gettext-$ver") + if test `find "$work_dir" -type f -print | wc -l` = 0; then + rm -rf "$work_dir" + func_fatal_error "infrastructure files for version $ver not found; this is autopoint from GNU $package $version" + fi + mv "$work_dir/gettext-$ver" "$work_dir/archive" + ;; + + cvs) + # We distributed the many different versions of the files in a CVS + # repository. This guaranteed a good compression rate: + # + # Including version size in KB of + # "du autopoint-files/archive" + # 0.10.35 240 + # 0.10.36 428 + # 0.10.37 436 + # 0.10.38 488 + # 0.10.39 500 + # 0.10.40 528 + # 0.11 720 + # 0.11.1 740 + # 0.11.2 748 + # 0.11.3 804 + # 0.11.4 864 + # 0.11.5 880 + # 0.12 1032 + # 0.12.1 1032 + # 0.13 1220 + # 0.13.1 1236 + # 0.14 1296 + # 0.14.1 1300 + # 0.14.2 1420 + # 0.14.3 1428 + # 0.14.4 1464 + # 0.14.5 1508 + # 0.14.6 1580 + # 0.15 1760 + # 0.16 1808 + # 0.16.1 1812 + # 0.17 2128 + # 0.18 2656 + # + # The requirement that the user must have the CVS program available is not + # a severe restrictions, because most of the people who use autopoint are + # users of CVS. + # + # But the CVS format is now deprecated, because "cvs init" does not work in + # all circumstances + # (see ) + # and we are not allowed to distribute the cvs infrastructure files + # ourselves + # (see ). + # + # Check availability of the CVS program. + (cvs -v) >/dev/null 2>/dev/null || func_fatal_error "cvs program not found" + + # Set up a temporary CVS repository. + # We need the temporary CVS repository because any checkout needs write + # access to the CVSROOT/history file, so it cannot be under $gettext_datadir. + # We need the temporary checkout directory because when --force was not + # given, we need to compare the existing files with the checked out ones. + # Set variables + # - cvs_dir directory containing the temporary repository + cvs_dir=tmpcvs$$ + # Use an umask of 077, to avoid attacks that work by overwriting files in + # the "$CVSROOT"/CVSROOT directory. + (umask 077 && mkdir "$cvs_dir") || { + if test -d "$cvs_dir"; then + func_fatal_error "directory $cvs_dir already exists" + else + func_fatal_error "cannot create directory $cvs_dir" + fi + } + CVSROOT="$srcdir/$cvs_dir" + unset CVS_CLIENT_LOG + unset CVS_CLIENT_PORT + unset CVS_IGNORE_REMOTE_ROOT + unset CVS_LOCAL_BRANCH_NUM + unset CVS_NOBASES + unset CVS_PASSFILE + unset CVS_PASSWORD + unset CVS_PROXY_PORT + unset CVS_RCMD_PORT + unset CVS_RSH + unset CVS_SERVER + unset CVS_SERVER_SLEEP + CVS_SIGN_COMMITS= + export CVS_SIGN_COMMITS + unset CVS_SSH + unset CVS_VERIFY_CHECKOUTS + unset CVS_VERIFY_TEMPLATE + unset CVSIGNORE + unset CVSREAD + unset CVSREADONLYFS + unset CVSUMASK + unset CVSWRAPPERS + + # Need to pass -d "$CVSROOT", because there may be a CVS directory in the + # current directory. + cvs -d "$CVSROOT" init + gzip -d -c < "$gettext_datadir/archive.cvs.tar.gz" | (cd "$cvs_dir" && tar xf -) + + cd "$work_dir" + cvsver=gettext-`echo "$ver" | sed -e 's/\./_/g'` + (cvs -d "$CVSROOT" checkout -r"$cvsver" archive > /dev/null) 2>&1 | grep -v '^cvs checkout: Updating' + find archive -name CVS -type d -print | xargs rm -rf + cd .. + rm -rf "$cvs_dir" + # Check that really all CVS directories are gone, otherwise we would overwrite + # the contents of the user's CVS directories. + if test `find $work_dir/archive -name CVS -type d -print | wc -l` != 0; then + rm -rf "$work_dir" + func_fatal_error "failed to remove all CVS subdirectories" + fi + if test `find $work_dir/archive -type f -print | wc -l` = 0; then + rm -rf "$work_dir" + func_fatal_error "infrastructure files for version $ver not found; this is autopoint from GNU $package $version" + fi + ;; + + git) + # Check availability of the git program. + (git --version) >/dev/null 2>/dev/null || func_fatal_error "git program not found" + mkdir "$work_dir/archive" + gzip -d -c < "$gettext_datadir/archive.git.tar.gz" | (cd "$work_dir/archive" && tar xf -) + (unset GIT_CONFIG + unset XDG_CONFIG_HOME + unset HOME + GIT_CONFIG_NOSYSTEM=1; export GIT_CONFIG_NOSYSTEM + cd "$work_dir/archive" && git checkout -q "gettext-$ver" + ) || { + rm -rf "$work_dir" + func_fatal_error "infrastructure files for version $ver not found; this is autopoint from GNU $package $version" + } + (cd "$work_dir/archive" && rm -rf .git .gitignore) + ;; +esac + +# func_destfile file +# determines the destination file, relative to the package's top level +# directory, for a given file name, relative to archive. +# Sets variables +# - destfile relative destination file name, or +# empty if the file shall be omitted +# - sharedowner yes if the file is not only owned by GNU gettext but may +# be installed by automake or other tools, otherwise empty +# - allpodirs yes if the file is to be installed in every dir in $podirs +func_destfile () +{ + # There are five categories of files: + # ABOUT-NLS -> top level directory + # config.rpath mkinstalldirs -> $auxdir + # m4/* -> $m4dir/ + # intl/* -> intl/ + # po/* -> + sharedowner= + allpodirs= + case `echo "$1" | sed -e 's,[^/]*$,,'` in + "" ) + case "$1" in + config.rpath ) destfile="$auxdir$1" ;; + mkinstalldirs ) destfile="$auxdir$1" sharedowner=yes ;; + * ) destfile="$1" ;; + esac + ;; + m4/ ) destfile=`echo "$1" | sed -e "s,^m4/,$m4dir/,"` ;; + intl/ ) if test -n "$omitintl"; then destfile=""; else destfile="$1"; fi ;; + po/ ) destfile=`echo "$1" | sed -e "s,^po/,,"` allpodirs=yes ;; + * ) destfile="$1" ;; + esac +} + +# func_compare existingfile gettextfile +# compares the existing file and the file from gettext, and decides whether the +# existing file should be overwritten with the file from gettext. Returns 0 if +# it should be overwritten, or 1 if it should be skipped. +sed_extract_serial='s/^#.* serial \([^ ]*\).*/\1/p +1q' +func_compare () +{ + if cmp -s "$1" "$2"; then + false + else + case "$2" in + *.m4) + # For interoperability with gnulib. gnulib often has newer versions of + # the *.m4 files than the latest gettext release. Don't overwrite a + # newer version from gnulib with an older version from the gettext + # release. The version can be retrieved from the first line, which + # looks like this: # file.m4 serial NN ... + existing_serial=`sed -n -e "$sed_extract_serial" < "$1"` + gettext_serial=`sed -n -e "$sed_extract_serial" < "$2"` + if test -n "$existing_serial" && test -n "$gettext_serial" \ + && test "$existing_serial" -ge "$gettext_serial" 2> /dev/null; then + false + else + true + fi + ;; + *) + true + ;; + esac + fi +} + +# If some files have been locally modified and we have not been requested +# to overwrite them, then bail out. This is better than leaving a source +# package around where half of the files are locally modified and half are +# original - too great risk of version mismatch. +if test -z "$force"; then + mismatch= + func_tmpdir + mismatchfile="$tmp"/autopoint.diff + for file in `find "$work_dir/archive" -type f -print | sed -e "s,^$work_dir/archive/,," | LC_ALL=C sort`; do + func_destfile "$file" + if test -n "$destfile"; then + func_compare_to_destfile () + { + finaldestfile="$1" + if test -f "$finaldestfile"; then + if func_compare "$finaldestfile" "$work_dir/archive/$file"; then + if test -n "$sharedowner"; then + echo "autopoint: warning: File $finaldestfile has been locally modified." 1>&2 + else + echo "autopoint: File $finaldestfile has been locally modified." 1>&2 + mismatch=yes + diff -c "$work_dir/archive/$file" "$finaldestfile" | sed -e "1s,$work_dir/archive/,," >> "$mismatchfile" + fi + fi + fi + } + if test -n "$allpodirs"; then + for dir in $podirs; do + func_compare_to_destfile "$dir/$destfile" + done + else + func_compare_to_destfile "$destfile" + fi + fi + done + if test -n "$mismatch"; then + rm -rf "$work_dir" + func_fatal_error "Some files have been locally modified. Not overwriting them because --force has not been specified. For your convenience, you find the local modifications in the file '$mismatchfile'." + fi + rm -rf "$tmp" +fi + +# func_mkdir_for to +# ensures the directory that would the given file exists. +# 'to' is a relative pathname, relative to the current directory. +func_mkdir_for () +{ + base=`echo "$1" | sed -e 's,/[^/]*$,,'` + if test "X$base" != "X$1" && test -n "$base"; then + func_mkdir_for "$base" + # Recompute base. It was clobbered by the recursive call. + base=`echo "$1" | sed -e 's,/[^/]*$,,'` + test -d "$base" || { echo "Creating directory $base"; mkdir "$base"; } + fi +} + +# func_copy from to +# copies a file. +# 'from' is a relative pathname, relative to the current directory. +# 'to' is a relative pathname, relative to the current directory. +func_copy () +{ + if $doit; then + func_mkdir_for "$2" + rm -f "$2" + echo "Copying file $2" + cp "$1" "$2" + else + echo "Copy file $2" + fi +} + +# func_backup to +# makes a backup of a file that is about to be overwritten or replaced. +# 'to' is a relative pathname, relative to the current directory. +func_backup () +{ + if $doit; then + if test -f "$1"; then + rm -f "$1~" + cp -p "$1" "$1~" + fi + fi +} + +# Now copy the files. +for file in `find "$work_dir/archive" -type f -print | sed -e "s,^$work_dir/archive/,," | LC_ALL=C sort`; do + func_destfile "$file" + if test -n "$destfile"; then + func_copy_to_destfile () + { + finaldestfile="$1" + mustcopy= + if test -f "$finaldestfile"; then + if func_compare "$finaldestfile" "$work_dir/archive/$file"; then + if test -n "$force"; then + # Overwrite locally modified file. + mustcopy=yes + fi + # If --force is not specified, don't overwrite locally modified files + # for which GNU gettext is a shared owner. + fi + else + mustcopy=yes + fi + if test -n "$mustcopy"; then + func_backup "$finaldestfile" + func_copy "$work_dir/archive/$file" "$finaldestfile" + fi + } + if test -n "$allpodirs"; then + for dir in $podirs; do + func_copy_to_destfile "$dir/$destfile" + done + else + func_copy_to_destfile "$destfile" + fi + fi +done + +# That's it. +rm -rf "$work_dir" +exit 0 diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/envsubst b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/envsubst new file mode 100644 index 0000000000000000000000000000000000000000..e6a77242ee0d8b6d9637c1e9bc90179722760236 Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/envsubst differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/gettext b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/gettext new file mode 100644 index 0000000000000000000000000000000000000000..7a7287b283c13d0b979310c10521134b0594e5db Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/gettext differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/gettext.sh b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/gettext.sh new file mode 100644 index 0000000000000000000000000000000000000000..3c53e19543d5a2aaaff95d3c0d8b242a8cd179d8 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/gettext.sh @@ -0,0 +1,135 @@ +#! /bin/sh +# +# Copyright (C) 2003-2025 Free Software Foundation, Inc. +# +# This program 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.1 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 Lesser General Public License for more details. +# +# You should have received a copy of the GNU Lesser General Public License +# along with this program. If not, see . +# + +# Find a way to echo strings without interpreting backslash. +if test "X`(echo '\t') 2>/dev/null`" = 'X\t'; then + echo='echo' +else + if test "X`(printf '%s\n' '\t') 2>/dev/null`" = 'X\t'; then + echo='printf %s\n' + else + echo_func () { + cat < +This is free software: you are free to change and redistribute it. +There is NO WARRANTY, to the extent permitted by law." + echo "Written by" "Bruno Haible" + } + if test $# = 1; then + case "$1" in + --help | --hel | --he | --h ) + func_usage; exit 0 ;; + --version | --versio | --versi | --vers | --ver | --ve | --v ) + func_version; exit 0 ;; + esac + fi + func_usage 1>&2 + exit 1 + ;; + esac +fi + +# eval_gettext MSGID +# looks up the translation of MSGID and substitutes shell variables in the +# result. +eval_gettext () { + gettext "$1" | (export PATH `envsubst --variables "$1"`; envsubst "$1") +} + +# eval_ngettext MSGID MSGID-PLURAL COUNT +# looks up the translation of MSGID / MSGID-PLURAL for COUNT and substitutes +# shell variables in the result. +eval_ngettext () { + ngettext "$1" "$2" "$3" | (export PATH `envsubst --variables "$1 $2"`; envsubst "$1 $2") +} + +# eval_pgettext MSGCTXT MSGID +# looks up the translation of MSGID in the context MSGCTXT and substitutes +# shell variables in the result. +eval_pgettext () { + gettext --context="$1" "$2" | (export PATH `envsubst --variables "$2"`; envsubst "$2") +} + +# eval_npgettext MSGCTXT MSGID MSGID-PLURAL COUNT +# looks up the translation of MSGID / MSGID-PLURAL for COUNT in the context +# MSGCTXT and substitutes shell variables in the result. +eval_npgettext () { + ngettext --context="$1" "$2" "$3" "$4" | (export PATH `envsubst --variables "$2 $3"`; envsubst "$2 $3") +} + +# Note: This use of envsubst is much safer than using the shell built-in 'eval' +# would be. +# 1) The security problem with Chinese translations that happen to use a +# character such as \xe0\x60 is avoided. +# 2) The security problem with malevolent translators who put in command lists +# like "$(...)" or "`...`" is avoided. +# 3) The translations can only refer to shell variables that are already +# mentioned in MSGID or MSGID-PLURAL. +# +# Note: "export PATH" above is a dummy; this is for the case when +# `envsubst --variables ...` returns nothing. +# +# Note: In eval_ngettext above, "$1 $2" means a string whose variables set is +# the union of the variables set of "$1" and "$2". +# +# Note: The minimal use of backquote above ensures that trailing newlines are +# not dropped, not from the gettext invocation and not from the value of any +# shell variable. +# +# Note: Field splitting on the `envsubst --variables ...` result is desired, +# since envsubst outputs the variables, separated by newlines. Pathname +# wildcard expansion or tilde expansion has no effect here, since the words +# output by "envsubst --variables ..." consist solely of alphanumeric +# characters and underscore. diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/gettextize b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/gettextize new file mode 100644 index 0000000000000000000000000000000000000000..d1f6247931a845e92205f2a92cf6d314b07b586a --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/gettextize @@ -0,0 +1,1313 @@ +#! /bin/sh +# +# Copyright (C) 1995-2025 Free Software Foundation, Inc. +# +# 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 . +# + +# This file is meant for authors or maintainers which want to +# internationalize their package with the help of GNU gettext. For +# further information how to use it consult the GNU gettext manual. + +progname=$0 +package=gettext-tools +version=0.25.1 +archive_version=0.25.1 + +# Set variables +# - gettext_datadir directory where the data files are stored. +prefix="/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho" +datarootdir="${prefix}/share" +: ${gettext_datadir="${datarootdir}/gettext"} +: ${AUTOM4TE=autom4te} + +# func_tmpdir +# creates a temporary directory. +# Sets variable +# - tmp pathname of freshly created temporary directory +func_tmpdir () +{ + # Use the environment variable TMPDIR, falling back to /tmp. This allows + # users to specify a different temporary directory, for example, if their + # /tmp is filled up or too small. + : ${TMPDIR=/tmp} + { + # Use the mktemp program if available. If not available, hide the error + # message. + tmp=`(umask 077 && mktemp -d "$TMPDIR/gtXXXXXX") 2>/dev/null` && + test -n "$tmp" && test -d "$tmp" + } || + { + # Use a simple mkdir command. It is guaranteed to fail if the directory + # already exists. $RANDOM is bash specific and expands to empty in shells + # other than bash, ksh and zsh. Its use does not increase security; + # rather, it minimizes the probability of failure in a very cluttered /tmp + # directory. + tmp=$TMPDIR/gt$$-$RANDOM + (umask 077 && mkdir "$tmp") + } || + { + echo "$0: cannot create a temporary directory in $TMPDIR" >&2 + { (exit 1); exit 1; } + } +} + +# Support for relocatability. +func_find_curr_installdir () +{ + # Determine curr_installdir, even taking into account symlinks. + curr_executable="$0" + case "$curr_executable" in + */* | *\\*) ;; + *) # Need to look in the PATH. + save_IFS="$IFS"; IFS="${PATH_SEPARATOR=':'}" + for dir in $PATH; do + IFS="$save_IFS" + test -z "$dir" && dir=. + for exec_ext in ''; do + if test -f "$dir/$curr_executable$exec_ext"; then + curr_executable="$dir/$curr_executable$exec_ext" + break 2 + fi + done + done + IFS="$save_IFS" + ;; + esac + # Make absolute. + case "$curr_executable" in + /* | ?:/* | ?:\\*) ;; + *) curr_executable=`pwd`/"$curr_executable" ;; + esac + # Resolve symlinks. + sed_dirname='s,/[^/]*$,,' + sed_linkdest='s,^.* -> \(.*\),\1,p' + while : ; do + lsline=`LC_ALL=C ls -l "$curr_executable"` + case "$lsline" in + *" -> "*) + linkdest=`echo "$lsline" | sed -n -e "$sed_linkdest"` + case "$linkdest" in + /* | ?:/* | ?:\\*) curr_executable="$linkdest" ;; + *) curr_executable=`echo "$curr_executable" | sed -e "$sed_dirname"`/"$linkdest" ;; + esac ;; + *) break ;; + esac + done + curr_installdir=`echo "$curr_executable" | sed -e 's,/[^/]*$,,'` + # Canonicalize. + curr_installdir=`cd "$curr_installdir" && pwd` +} +func_find_prefixes () +{ + # Compute the original/current installation prefixes by stripping the + # trailing directories off the original/current installation directories. + orig_installprefix="$orig_installdir" + curr_installprefix="$curr_installdir" + while true; do + orig_last=`echo "$orig_installprefix" | sed -n -e 's,^.*/\([^/]*\)$,\1,p'` + curr_last=`echo "$curr_installprefix" | sed -n -e 's,^.*/\([^/]*\)$,\1,p'` + if test -z "$orig_last" || test -z "$curr_last"; then + break + fi + if test "$orig_last" != "$curr_last"; then + break + fi + orig_installprefix=`echo "$orig_installprefix" | sed -e 's,/[^/]*$,,'` + curr_installprefix=`echo "$curr_installprefix" | sed -e 's,/[^/]*$,,'` + done +} +if test "no" = yes; then + exec_prefix="${prefix}" + bindir="${exec_prefix}/bin" + orig_installdir="$bindir" # see Makefile.am's *_SCRIPTS variables + func_find_curr_installdir # determine curr_installdir + func_find_prefixes + # Relocate the directory variables that we use. + gettext_datadir=`echo "$gettext_datadir/" | sed -e "s%^${orig_installprefix}/%${curr_installprefix}/%" | sed -e 's,/$,,'` +fi + +# func_trace_autoconf macro configure.ac +# traces an Autoconf macro call and outputs the arguments to stdout, +# using autom4te. +func_trace_autoconf () +{ + echo '\ +dnl replace macros which may abort autom4te with a no-op variant +m4_pushdef([m4_assert]) +m4_pushdef([m4_fatal]) +m4_pushdef([m4_warn]) +m4_pushdef([m4_errprintn]) +m4_pushdef([m4_exit]) +m4_pushdef([m4_include]) +m4_pushdef([m4_esyscmd]) +' \ + | "$AUTOM4TE" --no-cache --language=Autoconf-without-aclocal-m4 \ + --trace="$1":\$% - "$2" 2>/dev/null +} + +# func_trace_sed macro configure.ac +# traces an Autoconf macro call and outputs the arguments to stdout, +# using sed. +func_trace_sed () +{ + sed_extract_arguments=' +s,#.*$,,; s,^dnl .*$,,; s, dnl .*$,,; +/'"$1"'(/ { + ta + :a + s/)/)/ + tb + s/\\$// + N + ba + :b + s,^.*'"$1"'([[ ]*\([^]"$`\\)]*\).*$,\1,p +} +d' + sed -e "$sed_extract_arguments" "$2" +} + +# func_usage +# outputs to stdout the --help usage message. +func_usage () +{ + echo "\ +Usage: gettextize [OPTION]... [package-dir] + +Prepares a source package to use gettext. + +Options: + --help print this help and exit + --version print version information and exit + -f, --force force writing of new files even if old exist + --po-dir=DIR specify directory with PO files + --no-changelog don't update or create ChangeLog files + --symlink make symbolic links instead of copying files + -n, --dry-run print modifications but don't perform them + +Report bugs in the bug tracker at +or by email to ." +} + +# func_version +# outputs to stdout the --version message. +func_version () +{ + echo "$progname (GNU $package) $version" + echo "Copyright (C) 1995-2025 Free Software Foundation, Inc. +License GPLv3+: GNU GPL version 3 or later +This is free software: you are free to change and redistribute it. +There is NO WARRANTY, to the extent permitted by law." + echo "Written by" "Ulrich Drepper" +} + +# func_fatal_error message +# outputs to stderr a fatal error message, and terminates the program. +func_fatal_error () +{ + echo "gettextize: *** $1" 1>&2 + echo "gettextize: *** Stop." 1>&2 + exit 1 +} + +# Nuisances. +(unset CDPATH) >/dev/null 2>&1 && unset CDPATH + +# Unset more variables known to interfere with behavior of common tools. +CLICOLOR_FORCE= GREP_OPTIONS= +unset CLICOLOR_FORCE GREP_OPTIONS + +# Command-line option processing. +# Removes the OPTIONS from the arguments. Sets the variables: +# - force 1 if --force was given, 0 otherwise +# - intldir yes if --intl was given, empty otherwise +# - podirs list of directories specified with --po-dir +# - try_ln_s : if --symlink was given, false otherwise +# - do_changelog false if --no-changelog was given, : otherwise +# - doit false if --dry-run was given, : otherwise +{ + force=0 + intldir= + podirs= + try_ln_s=false + do_changelog=: + doit=: + + while test $# -gt 0; do + case "$1" in + -c | --copy | --cop | --co | --c ) # accepted for backward compatibility + shift ;; + -n | --dry-run | --dry-ru | --dry-r | --dry- | --dry | --dr | --d ) + shift + doit=false ;; + -f | --force | --forc | --for | --fo | --f ) + shift + force=1 ;; + --help | --hel | --he | --h ) + func_usage; exit 0 ;; + --intl | --int | --in | --i ) + shift + intldir=yes ;; + --po-dir | --po-di | --po-d | --po- | --po | --p ) + shift + if test $# = 0; then + func_fatal_error "missing argument for --po-dir" + fi + case "$1" in + -*) func_fatal_error "missing argument for --po-dir" ;; + esac + podirs="$podirs $1" + shift ;; + --po-dir=* ) + arg=`echo "X$1" | sed -e 's/^X--po-dir=//'` + podirs="$podirs $arg" + shift ;; + --no-changelog | --no-changelo | --no-changel | --no-change | --no-chang | --no-chan | --no-cha | --no-ch | --no-c ) + shift + do_changelog=false ;; + --symlink | --symlin | --symli | --syml | --sym | --sy | --s ) + shift + try_ln_s=: ;; + --version | --versio | --versi | --vers | --ver | --ve | --v ) + func_version + exit 0 ;; + -- ) # Stop option prcessing + shift; break ;; + -* ) + echo "gettextize: unknown option $1" 1>&2 + echo "Try 'gettextize --help' for more information." 1>&2 + exit 1 ;; + * ) + break ;; + esac + done + # podirs defaults to "po". + test -n "$podirs" || podirs="po" +} + +# Warn about deprecated options. +if test -n "$intldir"; then + func_fatal_error "The option '--intl' is no longer available." +fi + +# Require automake 1.9 or newer. +have_automake19= +if (aclocal --version) >/dev/null 2>/dev/null; then + aclocal_version=`aclocal --version | sed -n -e 1p | sed -e 's/^[^0-9]*//'` + case $aclocal_version in + 1.9* | 1.[1-9][0-9]* | [2-9]*) have_automake19=yes ;; + esac +fi +if test -z "$have_automake19"; then + func_fatal_error "You need the 'aclocal' program from automake 1.9 or newer." +fi +min_automake_version=1.9 + +# Command-line argument processing. +# Analyzes the remaining arguments. +# Sets the variables +# - origdir to the original directory, +# - srcdir to the package directory, and cd-s into it. +{ + if test $# -gt 1; then + func_usage 1>&2 + exit 1 + fi + origdir=`pwd` + if test $# -eq 1; then + srcdir=$1 + if cd "$srcdir"; then + srcdir=`pwd` + else + func_fatal_error "Cannot change directory to '$srcdir'." + fi + else + srcdir=$origdir + fi +} + +# The current directory is now $srcdir. + +# Check integrity of package: A configure.in/ac must be present. Sets variable +# - configure_in name of configure.in/ac file. +test -f configure.in || test -f configure.ac || + func_fatal_error "Missing configure.in or configure.ac, please cd to your package first." +configure_in=NONE +if test -f configure.in; then + configure_in=configure.in +else + if test -f configure.ac; then + configure_in=configure.ac + fi +fi + +# Check whether the --force option is needed but has not been specified. +if test $force -eq 0; then + if test -d intl; then + func_fatal_error "intl/ subdirectory exists: use option -f if you really want to delete it." + fi + for podir in $podirs; do + if test -f "$podir/Makefile.in.in"; then + func_fatal_error "$podir/Makefile.in.in exists: use option -f if you really want to delete it." + fi + done + if test -f ABOUT-NLS; then + func_fatal_error "ABOUT-NLS exists: use option -f if you really want to delete it." + fi +fi + +# Select the method for Autoconf macro tracing. func_trace_autoconf +# is more accurate than func_trace_sed, but it only works with +# autoconf >= 2.69. +if echo "AC_PREREQ([2.69])" \ + | "$AUTOM4TE" --no-cache --language=Autoconf-without-aclocal-m4 - 2>&1; then + func_trace=func_trace_autoconf +else + func_trace=func_trace_sed +fi + +# Check in which directory config.rpath etc. belong. +auxdir=`"$func_trace" AC_CONFIG_AUX_DIR "$configure_in"` +if test -n "$auxdir"; then + auxdir="$auxdir/" +fi + +# Check in which directory gettext.m4 etc. belong. +macrodirs=`"$func_trace" AC_CONFIG_MACRO_DIR_TRACE "$configure_in"` +if test -z "$macrodirs"; then + macrodirs=`"$func_trace" AC_CONFIG_MACRO_DIR "$configure_in"` +fi +for arg in $macrodirs; do + m4dir="$arg" + break +done + +# For simplicity we change to the gettext source directory. +cd "$gettext_datadir" || + func_fatal_error "gettext source directory '${gettext_datadir}' doesn't exist" + +# Variables which keep track what has been modified. +added_directories= +removed_directory= +added_extradist= +added_acoutput= +removed_acoutput=" intl/intlh.inst" + +# Variable: +# - please accumulates instructions for the user. +please= + +# Variable: +# - date current date, for use in ChangeLog entries. +date=`date +%Y-%m-%d` + +# func_copy from to +# copies a file. +# 'from' is a relative pathname, relative to the current directory. +# 'to' is a relative pathname, relative to $srcdir. +func_copy () +{ + if $doit; then + rm -f "$srcdir/$2" + echo "Copying file $2" + cp "$1" "$srcdir/$2" + else + echo "Copy file $2" + fi +} + +# func_linkorcopy from absfrom to +# links or copies a file. +# 'from' is a relative pathname, relative to the current directory. +# 'absfrom' is the corresponding absolute pathname. +# 'to' is a relative pathname, relative to $srcdir. +func_linkorcopy () +{ + if $doit; then + rm -f "$srcdir/$3" + ($try_ln_s && ln -s "$2" "$srcdir/$3" && echo "Symlinking file $3") 2>/dev/null || + { echo "Copying file $3"; cp "$1" "$srcdir/$3"; } + else + if $try_ln_s; then + echo "Symlink file $3" + else + echo "Copy file $3" + fi + fi +} + +# func_backup to +# makes a backup of a file that is about to be overwritten or replaced. +# 'to' is a relative pathname, relative to $srcdir. +func_backup () +{ + if $doit; then + if test -f "$srcdir/$1"; then + rm -f "$srcdir/$1~" + cp -p "$srcdir/$1" "$srcdir/$1~" + fi + fi +} + +# func_remove to +# removes a file. +# 'to' is a relative pathname, relative to $srcdir. +func_remove () +{ + if $doit; then + echo "Removing $1" + rm -f "$srcdir/$1" + else + echo "Remove $1" + fi +} + +# func_ChangeLog_init +# func_ChangeLog_add_entry line +# func_ChangeLog_finish +# manage the ChangeLog file, relative to $srcdir. +func_ChangeLog_init () +{ + modified_ChangeLog= +} +func_ChangeLog_add_entry () +{ + if $doit; then + if test -z "$modified_ChangeLog"; then + echo "$date gettextize " > "$srcdir/ChangeLog.tmp" + echo >> "$srcdir/ChangeLog.tmp" + modified_ChangeLog=yes + fi + echo "$1" >> "$srcdir/ChangeLog.tmp" + else + modified_ChangeLog=yes + fi +} +func_ChangeLog_finish () +{ + if test -n "$modified_ChangeLog"; then + if $doit; then + echo >> "$srcdir/ChangeLog.tmp" + if test -f "$srcdir/ChangeLog"; then + echo "Adding an entry to ChangeLog (backup is in ChangeLog~)" + cat "$srcdir/ChangeLog" >> "$srcdir/ChangeLog.tmp" + rm -f "$srcdir/ChangeLog~" + cp -p "$srcdir/ChangeLog" "$srcdir/ChangeLog~" + else + echo "Creating ChangeLog" + fi + cp "$srcdir/ChangeLog.tmp" "$srcdir/ChangeLog" + rm -f "$srcdir/ChangeLog.tmp" + else + if test -f "$srcdir/ChangeLog"; then + echo "Add an entry to ChangeLog" + else + echo "Create ChangeLog" + fi + fi + fi +} + +# func_poChangeLog_init +# func_poChangeLog_add_entry line +# func_poChangeLog_finish +# manage the $podir/ChangeLog file, relative to $srcdir. +func_poChangeLog_init () +{ + modified_poChangeLog= +} +func_poChangeLog_add_entry () +{ + if $doit; then + if test -z "$modified_poChangeLog"; then + echo "$date gettextize " > "$srcdir/$podir/ChangeLog.tmp" + echo >> "$srcdir/$podir/ChangeLog.tmp" + modified_poChangeLog=yes + fi + echo "$1" >> "$srcdir/$podir/ChangeLog.tmp" + else + modified_poChangeLog=yes + fi +} +func_poChangeLog_finish () +{ + if test -n "$modified_poChangeLog"; then + if $doit; then + echo >> "$srcdir/$podir/ChangeLog.tmp" + if test -f "$srcdir/$podir/ChangeLog"; then + echo "Adding an entry to $podir/ChangeLog (backup is in $podir/ChangeLog~)" + cat "$srcdir/$podir/ChangeLog" >> "$srcdir/$podir/ChangeLog.tmp" + rm -f "$srcdir/$podir/ChangeLog~" + cp -p "$srcdir/$podir/ChangeLog" "$srcdir/$podir/ChangeLog~" + else + echo "Creating $podir/ChangeLog" + fi + cp "$srcdir/$podir/ChangeLog.tmp" "$srcdir/$podir/ChangeLog" + rm -f "$srcdir/$podir/ChangeLog.tmp" + else + if test -f "$srcdir/$podir/ChangeLog"; then + echo "Add an entry to $podir/ChangeLog" + else + echo "Create $podir/ChangeLog" + fi + fi + fi +} + +# func_m4ChangeLog_init +# func_m4ChangeLog_add_entry line +# func_m4ChangeLog_finish +# manage the $m4dir/ChangeLog file, relative to $srcdir. +func_m4ChangeLog_init () +{ + if test -n "$using_m4ChangeLog"; then + modified_m4ChangeLog= + created_m4ChangeLog= + fi +} +func_m4ChangeLog_add_entry () +{ + if test -n "$using_m4ChangeLog"; then + if $doit; then + if test -z "$modified_m4ChangeLog"; then + echo "$date gettextize " > "$srcdir/$m4dir/ChangeLog.tmp" + echo >> "$srcdir/$m4dir/ChangeLog.tmp" + modified_m4ChangeLog=yes + fi + echo "$1" >> "$srcdir/$m4dir/ChangeLog.tmp" + else + modified_m4ChangeLog=yes + fi + else + line="$1" + line=`echo "$line" | sed -e "s%^ \\* % * $m4dir/%"` + func_ChangeLog_add_entry "$line" + fi +} +func_m4ChangeLog_finish () +{ + if test -n "$using_m4ChangeLog"; then + if test -n "$modified_m4ChangeLog"; then + if $doit; then + echo >> "$srcdir/$m4dir/ChangeLog.tmp" + if test -f "$srcdir/$m4dir/ChangeLog"; then + echo "Adding an entry to $m4dir/ChangeLog (backup is in $m4dir/ChangeLog~)" + cat "$srcdir/$m4dir/ChangeLog" >> "$srcdir/$m4dir/ChangeLog.tmp" + rm -f "$srcdir/$m4dir/ChangeLog~" + cp -p "$srcdir/$m4dir/ChangeLog" "$srcdir/$m4dir/ChangeLog~" + else + echo "Creating $m4dir/ChangeLog" + created_m4ChangeLog=yes + fi + cp "$srcdir/$m4dir/ChangeLog.tmp" "$srcdir/$m4dir/ChangeLog" + rm -f "$srcdir/$m4dir/ChangeLog.tmp" + else + if test -f "$srcdir/$m4dir/ChangeLog"; then + echo "Add an entry to $m4dir/ChangeLog" + else + echo "Create $m4dir/ChangeLog" + created_m4ChangeLog=yes + fi + fi + fi + fi +} +using_m4ChangeLog=yes + +if test -f "$srcdir/intl/Makefile.in"; then + removed_acoutput="$removed_acoutput intl/Makefile" +fi +if test -d "$srcdir/intl"; then + # Remove everything inside intl except for RCS and CVS subdirs and invisible + # files. + if $doit; then + echo "Wiping out intl/ subdirectory" + (cd "$srcdir/intl" && + for f in *; do + if test CVS != "$f" && test RCS != "$f"; then + rm -rf "$f" + fi + done) + else + echo "Wipe out intl/ subdirectory" + fi + removed_directory=intl +fi + +$do_changelog && func_ChangeLog_init + +for podir in $podirs; do + test -d "$srcdir/$podir" || { + if $doit; then + echo "Creating $podir/ subdirectory" + mkdir "$srcdir/$podir" || func_fatal_error "failed to create $podir/ subdirectory" + else + echo "Create $podir/ subdirectory" + fi + added_directories="$added_directories $podir" + } +done + +# Create the directory for config.rpath, if needed. +# This is for consistency with autoreconf and automake. +# Note that $auxdir is either empty or ends in a slash. +test -d "$srcdir/$auxdir" || { + if $doit; then + echo "Creating $auxdir subdirectory" + mkdir "$srcdir/$auxdir" || func_fatal_error "failed to create $auxdir subdirectory" + else + echo "Create $auxdir subdirectory" + fi +} + +# Now copy all files. Take care for the destination directories. +for file in *; do + case $file in + ABOUT-NLS) + func_linkorcopy $file "$gettext_datadir/$file" $file + ;; + config.rpath) + func_linkorcopy $file "$gettext_datadir/$file" "$auxdir$file" + ;; + esac +done + +# Tell the user what to put into configure.ac, if it is not already there. +external= +# Need to use func_trace_sed instead of $func_trace, since +# AM_GNU_GETTEXT is not a standard Autoconf trace. +xargs=`func_trace_sed AM_GNU_GETTEXT "$srcdir/$configure_in"` +save_IFS="$IFS"; IFS=: +for arg in $xargs; do + if test 'external' = "$arg"; then + external=yes + break + fi +done +IFS="$save_IFS" +if test -z "$external"; then + please="$please +Please use AM_GNU_GETTEXT([external]) in order to cause autoconfiguration +to look for an external libintl. +" +fi + +# Tell the user to remove invocations of macros that no longer exist. +if sed -e 's,#.*$,,; s,^dnl .*$,,; s, dnl .*$,,' "$srcdir/$configure_in" | grep AM_GNU_GETTEXT_INTL_SUBDIR >/dev/null; then + please="$please +Please remove the invocation of AM_GNU_GETTEXT_INTL_SUBDIR. +" +fi + +# Copy files to po/ subdirectory. +cd po +for podir in $podirs; do + $do_changelog && func_poChangeLog_init + for file in Makefile.in.in; do + same=no + if test -f "$srcdir/$podir/$file"; then + if cmp -s $file "$srcdir/$podir/$file"; then + same=yes + fi + else + added_acoutput="$added_acoutput $podir/Makefile.in" + fi + if $do_changelog && test $same = no; then + if test -f "$srcdir/$podir/$file"; then + func_poChangeLog_add_entry " * $file: Upgrade to gettext-${version}." + else + func_poChangeLog_add_entry " * $file: New file, from gettext-${version}." + fi + fi + func_backup "$podir/$file" + func_linkorcopy $file "$gettext_datadir/po/$file" "$podir/$file" + done + for file in *; do + case $file in + Makefile.in.in) + # Already handled above. + ;; + Makevars.template) + func_linkorcopy Makevars.template "$gettext_datadir/po/Makevars.template" "$podir/Makevars.template" + if test -f "$srcdir/po/Makevars"; then + LC_ALL=C sed -n -e 's/[ ]*\([A-Za-z0-9_]*\)[ ]*=.*/\1/p' < "$srcdir/$podir/Makevars" | LC_ALL=C sort > "$srcdir/$podir/Makevars.tmp1" + LC_ALL=C sed -n -e 's/[ ]*\([A-Za-z0-9_]*\)[ ]*=.*/\1/p' < "$gettext_datadir/po/Makevars.template" | LC_ALL=C sort > "$srcdir/$podir/Makevars.tmp2" + missingvars=`LC_ALL=C comm -13 "$srcdir/$podir/Makevars.tmp1" "$srcdir/$podir/Makevars.tmp2"` + rm -f "$srcdir/$podir/Makevars.tmp1" "$srcdir/$podir/Makevars.tmp2" + if test -n "$missingvars"; then + please="$please +Please update $podir/Makevars so that it defines all the variables mentioned +in $podir/Makevars.template. +You can then remove $podir/Makevars.template. +" + fi + else + please="$please +Please create $podir/Makevars from the template in $podir/Makevars.template. +You can then remove $podir/Makevars.template. +" + fi + ;; + *) + same=no + if test -f "$srcdir/$podir/$file"; then + if cmp -s $file "$srcdir/$podir/$file"; then + same=yes + fi + fi + if $do_changelog && test $same = no; then + if test -f "$srcdir/$podir/$file"; then + func_poChangeLog_add_entry " * $file: Upgrade to gettext-${version}." + else + func_poChangeLog_add_entry " * $file: New file, from gettext-${version}." + fi + fi + func_backup "$podir/$file" + func_linkorcopy $file "$gettext_datadir/po/$file" "$podir/$file" + ;; + esac + done + if test -f "$srcdir/$podir/cat-id-tbl.c"; then + func_remove "$podir/cat-id-tbl.c" + $do_changelog && func_poChangeLog_add_entry " * cat-id-tbl.c: Remove file." + fi + if test -f "$srcdir/$podir/stamp-cat-id"; then + func_remove "$podir/stamp-cat-id" + $do_changelog && func_poChangeLog_add_entry " * stamp-cat-id: Remove file." + fi + if test ! -f "$srcdir/$podir/POTFILES.in"; then + if $doit; then + echo "Creating initial $podir/POTFILES.in" + echo '# List of source files which contain translatable strings.' > "$srcdir/$podir/POTFILES.in" + else + echo "Create initial $podir/POTFILES.in" + fi + $do_changelog && func_poChangeLog_add_entry " * POTFILES.in: New file." + please="$please +Please fill $podir/POTFILES.in as described in the documentation. +" + fi + $do_changelog && func_poChangeLog_finish +done + +m4filelist=' + build-to-host.m4 + gettext.m4 + host-cpu-c-abi.m4 + iconv.m4 + intlmacosx.m4 + lib-ld.m4 lib-link.m4 lib-prefix.m4 + nls.m4 + po.m4 progtest.m4' + +# All sorts of bugs could occur if the configure file was remade with the wrong +# version of gettext.m4 et al. (because then the configure and the po/Makefile.in.in +# don't fit together). It is therefore important that the package carries the +# right versions of gettext.m4 et al. with it. +if test -f "$srcdir/Makefile.am"; then + # A package using automake. + + # Determine whether it's using automake 1.8 or newer. + have_automake18= + if (aclocal --version) >/dev/null 2>/dev/null; then + aclocal_version=`aclocal --version | sed -n -e 1p | sed -e 's/^[^0-9]*//'` + case $aclocal_version in + 1.[8-9]* | 1.[1-9][0-9]* | [2-9]*) have_automake18=yes ;; + esac + fi + + if test -z "$m4dir"; then + # Extract the macro directory name from Makefile.am. + aclocal_amflags=`grep '^ACLOCAL_AMFLAGS[ ]*=' "$srcdir/Makefile.am" | sed -e 's/^ACLOCAL_AMFLAGS[ ]*=\(.*\)$/\1/'` + m4dir_is_next= + for arg in $aclocal_amflags; do + if test -n "$m4dir_is_next"; then + # Ignore absolute directory pathnames, like /usr/local/share/aclocal. + case "$arg" in + /*) ;; + *) + test -z "$m4dir" || m4dir="$arg" + macrodirs="$macrodirs $arg" + ;; + esac + m4dir_is_next= + else + if test "X$arg" = "X-I"; then + m4dir_is_next=yes + else + m4dir_is_next= + fi + fi + done + for arg in $macrodirs; do + m4dir="$arg" + break + done + fi + + if test -z "$m4dir"; then + m4dir=m4 + m4dir_defaulted=yes + fi + + # Decide whether to use $m4dir/ChangeLog, or to use ChangeLog instead. + if test -d "$srcdir/$m4dir" && test -f "$srcdir/ChangeLog" && test ! -f "$srcdir/$m4dir/ChangeLog"; then + # The programmer has no $m4dir/ChangeLog so far. Don't introduce one. + using_m4ChangeLog= + fi + + # Update the *.m4 files and the corresponding Makefile.am. + $do_changelog && func_m4ChangeLog_init + added_m4dir= + added_m4files= + if test -d "$srcdir/$m4dir"; then + : + else + if $doit; then + echo "Creating directory $m4dir" + mkdir "$srcdir/$m4dir" + else + echo "Create directory $m4dir" + fi + added_m4dir=yes + fi + for file in $m4filelist; do + same=no + if test -f "$srcdir/$m4dir/$file"; then + if cmp -s "${datarootdir}/gettext/m4/$file" "$srcdir/$m4dir/$file"; then + same=yes + fi + else + added_m4files="$added_m4files $file" + fi + if $do_changelog && test $same = no; then + if test -f "$srcdir/$m4dir/$file"; then + func_m4ChangeLog_add_entry " * $file: Upgrade to gettext-${version}." + else + func_m4ChangeLog_add_entry " * $file: New file, from gettext-${version}." + fi + fi + func_backup "$m4dir/$file" + func_linkorcopy "${datarootdir}/gettext/m4/$file" "${datarootdir}/gettext/m4/$file" "$m4dir/$file" + done + missing_m4Makefileam= + if test -n "$added_m4files"; then + if test -f "$srcdir/$m4dir/Makefile.am"; then + if $doit; then + echo "Updating EXTRA_DIST in $m4dir/Makefile.am (backup is in $m4dir/Makefile.am~)" + func_backup "$m4dir/Makefile.am" + rm -f "$srcdir/$m4dir/Makefile.am" + if grep '^EXTRA_DIST[ ]*=' "$srcdir/$m4dir/Makefile.am~" > /dev/null; then + sed -e "s%^\(EXTRA_DIST[ ]*=\) \\?%\\1$added_m4files %" < "$srcdir/$m4dir/Makefile.am~" > "$srcdir/$m4dir/Makefile.am" + $do_changelog && func_m4ChangeLog_add_entry " * Makefile.am (EXTRA_DIST): Add the new files." + else + (cat "$srcdir/$m4dir/Makefile.am~"; echo; echo "EXTRA_DIST =$added_m4files") > "$srcdir/$m4dir/Makefile.am" + $do_changelog && func_m4ChangeLog_add_entry " * Makefile.am (EXTRA_DIST): New variable." + fi + else + echo "Update EXTRA_DIST in $m4dir/Makefile.am" + $do_changelog && func_m4ChangeLog_add_entry " * Makefile.am (EXTRA_DIST)." + fi + else + # $m4dir/Makefile.am is not needed any more when aclocal 1.8 or newer + # is used. + if test -z "$have_automake18"; then + if $doit; then + echo "Creating $m4dir/Makefile.am" + echo "EXTRA_DIST =$added_m4files" > "$srcdir/$m4dir/Makefile.am" + else + echo "Create $m4dir/Makefile.am" + fi + $do_changelog && func_m4ChangeLog_add_entry " * Makefile.am: New file." + added_acoutput="$added_acoutput $m4dir/Makefile" + else + missing_m4Makefileam=yes + fi + fi + fi + if test -n "$added_m4dir" && test -z "$missing_m4Makefileam"; then + added_directories="$added_directories $m4dir" + fi + $do_changelog && func_m4ChangeLog_finish + # automake will arrange for $m4dir/ChangeLog to be distributed if a + # $m4dir/Makefile.am exists. If not, we need to add it to Makefile.am's + # EXTRA_DIST explicitly. + if test -n "$created_m4ChangeLog" && test -n "$missing_m4Makefileam"; then + added_extradist="$added_extradist $m4dir/ChangeLog" + fi + + # Update the top-level Makefile.am. + modified_Makefile_am= + # func_modify_Makefile_am changelog_comment + # assumes a modified copy of $srcdir/Makefile.am in $srcdir/Makefile.am.tmp + # and replaces the original Makefile.am file with the modified one if + # the two files differ. Then it removes the modified copy. + func_modify_Makefile_am () + { + if cmp -s "$srcdir/Makefile.am" "$srcdir/Makefile.am.tmp"; then + : + else + if test -z "$modified_Makefile_am"; then + if $doit; then + echo "Updating Makefile.am (backup is in Makefile.am~)" + func_backup Makefile.am + else + echo "Update Makefile.am" + fi + fi + if $doit; then + rm -f "$srcdir/Makefile.am" + cp "$srcdir/Makefile.am.tmp" "$srcdir/Makefile.am" + fi + if $do_changelog; then + if test -z "$modified_Makefile_am"; then + func_ChangeLog_add_entry " * Makefile.am $1" + else + func_ChangeLog_add_entry " $1" + fi + fi + modified_Makefile_am=yes + fi + rm -f "$srcdir/Makefile.am.tmp" + } + + if test -n "$added_directories"; then + if grep '^SUBDIRS[ ]*=' "$srcdir/Makefile.am" > /dev/null; then + sed -e "s%^\(SUBDIRS[ ]*=\) \\?%\\1$added_directories %" < "$srcdir/Makefile.am" > "$srcdir/Makefile.am.tmp" + added_directories_pretty=`echo $added_directories | sed -e 's/ /, /g'` + func_modify_Makefile_am "(SUBDIRS): Add $added_directories_pretty." + else + (cat "$srcdir/Makefile.am"; echo; echo "SUBDIRS =$added_directories") > "$srcdir/Makefile.am.tmp" + func_modify_Makefile_am "(SUBDIRS): New variable." + fi + fi + if test -n "$removed_directory"; then + sed -e '/^SUBDIRS[ ]*=/ { + :a + s%\([ ]\)'"$removed_directory"'[ ]%\1% + s%[ ]'"$removed_directory"'$%% + tb + :b + s%\\$%\\% + tc + bd + :c + n + ba + :d + }' < "$srcdir/Makefile.am" > "$srcdir/Makefile.am.tmp" + func_modify_Makefile_am "(SUBDIRS): Remove $removed_directory." + fi + if test -n "$added_directories"; then + if grep '^DIST_SUBDIRS[ ]*=' "$srcdir/Makefile.am" > /dev/null; then + sed -e "s%^\(DIST_SUBDIRS[ ]*=\) \\?%\\1$added_directories %" < "$srcdir/Makefile.am" > "$srcdir/Makefile.am.tmp" + added_directories_pretty=`echo $added_directories | sed -e 's/ /, /g'` + func_modify_Makefile_am "(DIST_SUBDIRS): Add $added_directories_pretty." + fi + fi + if test -n "$removed_directory"; then + sed -e '/^DIST_SUBDIRS[ ]*=/ { + :a + s%\([ ]\)'"$removed_directory"'[ ]%\1% + s%[ ]'"$removed_directory"'$%% + tb + :b + s%\\$%\\% + tc + bd + :c + n + ba + :d + }' < "$srcdir/Makefile.am" > "$srcdir/Makefile.am.tmp" + func_modify_Makefile_am "(DIST_SUBDIRS): Remove $removed_directory." + fi + if test -n "$m4dir_defaulted"; then + if grep '^ACLOCAL_AMFLAGS[ ]*=' "$srcdir/Makefile.am" > /dev/null; then + sed -e "s%^\(ACLOCAL_AMFLAGS[ ]*=\) \\?%\\1 -I $m4dir %" < "$srcdir/Makefile.am" > "$srcdir/Makefile.am.tmp" + func_modify_Makefile_am "(ACLOCAL_AMFLAGS): Add -I $m4dir." + else + (cat "$srcdir/Makefile.am"; echo; echo "ACLOCAL_AMFLAGS = -I $m4dir") > "$srcdir/Makefile.am.tmp" + func_modify_Makefile_am "(ACLOCAL_AMFLAGS): New variable." + fi + # Also update Makefile.in and, if existent, Makefile. Otherwise they + # would take into account the new flags only after a few rounds of + # "./configure", "make", "touch configure.in", "make distclean". + if $doit; then + for file in Makefile.in Makefile; do + if test -f "$srcdir/$file"; then + func_backup $file + rm -f "$srcdir/$file" + sed -e "s%(ACLOCAL)%(ACLOCAL) -I $m4dir%" < "$srcdir/$file~" > "$srcdir/$file" + fi + done + fi + fi + if test -n "$added_extradist"; then + if grep '^EXTRA_DIST[ ]*=' "$srcdir/Makefile.am" > /dev/null; then + sed -e "s%^\(EXTRA_DIST[ ]*=\)%\\1$added_extradist %" < "$srcdir/Makefile.am" > "$srcdir/Makefile.am.tmp" + added_extradist_pretty=`echo $added_extradist | sed -e 's/ /, /g'` + func_modify_Makefile_am "(EXTRA_DIST): Add $added_extradist_pretty." + else + (cat "$srcdir/Makefile.am"; echo; echo "EXTRA_DIST =$added_extradist") > "$srcdir/Makefile.am.tmp" + func_modify_Makefile_am "(EXTRA_DIST): New variable." + fi + fi + # Extract the aclocal options name from Makefile.am. + aclocal_options= + for arg in $macrodirs; do + aclocal_options="$aclocal_options -I $arg" + done + please="$please +Please run 'aclocal$aclocal_options' to regenerate the aclocal.m4 file. +You need aclocal from GNU automake $min_automake_version (or newer) to do this. +Then run 'autoconf' to regenerate the configure file. +" + + # Also create $m4dir/Makefile.in from $m4dir/Makefile.am, because automake + # doesn't do it by itself. + if $doit; then + case "$added_acoutput" in + *" $m4dir/Makefile") + (cd "$srcdir" && automake "$m4dir/Makefile") 2>/dev/null || + please="$please +Please run 'automake $m4dir/Makefile' to create $m4dir/Makefile.in +" + ;; + esac + fi +else + please="$please +Please add the files +$m4filelist +from the ${datarootdir}/gettext/m4 directory to your aclocal.m4 file. +" +fi + +modified_configure_in= +# func_modify_configure_in changelog_comment +# assumes a modified copy of $srcdir/$configure_in in $srcdir/$configure_in.tmp +# and replaces the original configure.in/ac file with the modified one if +# the two files differ. Then it removes the modified copy. +func_modify_configure_in () +{ + if cmp -s "$srcdir/$configure_in" "$srcdir/$configure_in.tmp"; then + : + else + if test -z "$modified_configure_in"; then + if $doit; then + echo "Updating $configure_in (backup is in $configure_in~)" + func_backup $configure_in + else + echo "Update $configure_in" + fi + fi + if $doit; then + rm -f "$srcdir/$configure_in" + cp "$srcdir/$configure_in.tmp" "$srcdir/$configure_in" + fi + if $do_changelog; then + if test -z "$modified_configure_in"; then + func_ChangeLog_add_entry " * $configure_in $1" + else + func_ChangeLog_add_entry " $1" + fi + fi + modified_configure_in=yes + fi + rm -f "$srcdir/$configure_in.tmp" +} + +if test -n "$added_acoutput"; then + if grep '^AC_CONFIG_FILES(' "$srcdir/$configure_in" > /dev/null; then + sedprog=' +ta +b +:a +n +ba' + sed -e "s%^\\(AC_CONFIG_FILES([^])\\,]*\\)%\\1$added_acoutput%$sedprog" < "$srcdir/$configure_in" > "$srcdir/$configure_in.tmp" + added_acoutput_pretty=`echo $added_acoutput | sed -e 's/ /, /g'` + func_modify_configure_in "(AC_CONFIG_FILES): Add $added_acoutput_pretty." + else + if grep '^AC_OUTPUT(' "$srcdir/$configure_in" > /dev/null; then + sed -e "s%^\\(AC_OUTPUT([^])\\,]*\\)%\\1$added_acoutput%" < "$srcdir/$configure_in" > "$srcdir/$configure_in.tmp" + added_acoutput_pretty=`echo $added_acoutput | sed -e 's/ /, /g'` + func_modify_configure_in "(AC_OUTPUT): Add $added_acoutput_pretty." + else + please="$please +Please add$added_acoutput to the AC_OUTPUT or AC_CONFIG_FILES invocation in the $configure_in file. +" + fi + fi +fi +if test -n "$removed_acoutput"; then + for file in $removed_acoutput; do + tag= + sedprog='{ + s%\([[ ]\)'"$file"'[ ]%\1% + s%\([[ ]\)'"$file"'\([]),]\)%\1\2% + s%[[ ]'"$file"'$%% + :a + tb + :b + s%\\$%\\% + tc + bd + :c + n + s%\([ ]\)'"$file"'[ ]%\1% + s%\([ ]\)'"$file"'\([]),]\)%\1\2% + s%[ ]'"$file"'$%% + ba + :d + }' + sed -e '/^AC_CONFIG_FILES(/'"$sedprog" < "$srcdir/$configure_in" > "$srcdir/$configure_in.tmp" + if cmp -s "$srcdir/$configure_in" "$srcdir/$configure_in.tmp"; then + sed -e '/^AC_OUTPUT(/'"$sedprog" < "$srcdir/$configure_in" > "$srcdir/$configure_in.tmp" + if cmp -s "$srcdir/$configure_in" "$srcdir/$configure_in.tmp"; then + : + else + tag=AC_OUTPUT + fi + else + tag=AC_CONFIG_FILES + fi + if test -n "$tag"; then + func_modify_configure_in "($tag): Remove $file." + else + rm -f "$srcdir/$configure_in.tmp" + if test "$file" != intl/intlh.inst; then + please="$please +Please remove $file from the AC_OUTPUT or AC_CONFIG_FILES invocation +in the $configure_in file. +" + fi + fi + done +fi +sed -e 's%sed -e "/POTFILES =/r po/POTFILES" po/Makefile\.in > po/Makefile *;* *%%' < "$srcdir/$configure_in" > "$srcdir/$configure_in.tmp" +func_modify_configure_in "(AC_OUTPUT): Remove command that created po/Makefile." +sed -e '/^\(dnl \|\)AC_LINK_FILES(\$nls_cv_header_libgt, \$nls_cv_header_intl)$/d' < "$srcdir/$configure_in" > "$srcdir/$configure_in.tmp" +func_modify_configure_in "(AC_LINK_FILES): Remove invocation." +# AM_GNU_GETTEXT_VERSION may not be present, when AM_GNU_GETTEXT_REQUIRE_VERSION is used. +if grep '^AM_GNU_GETTEXT_VERSION(' "$srcdir/$configure_in" >/dev/null; then + sed -e 's/^AM_GNU_GETTEXT_VERSION([^()]*)/AM_GNU_GETTEXT_VERSION(['"$archive_version"'])/' < "$srcdir/$configure_in" > "$srcdir/$configure_in.tmp" + func_modify_configure_in "(AM_GNU_GETTEXT_VERSION): Bump to $archive_version." +fi +$do_changelog && func_ChangeLog_finish + +# Recommend replacement for deprecated Makefile variables. +use_libtool=`cat "$srcdir/$configure_in" | grep '^A[CM]_PROG_LIBTOOL'` +for file in `(cd "$srcdir"; find . -name Makefile.am -print; find . -name Makefile.in -print) | sed -e 's,^\./,,'`; do + if test -f "$srcdir/$file"; then + if test `echo "$file" | sed -e 's,^.*/,,'` = Makefile.in && grep automake "$srcdir/$file" >/dev/null 2>&1; then + continue; + fi + # INTLLIBS is deprecated because it doesn't distinguish the two + # cases: with libtool, without libtool. + if grep '@''INTLLIBS''@' "$srcdir/$file" >/dev/null; then + if test -n "$use_libtool"; then + please="$please +Please change $file to use @""LTLIBINTL""@ or @""LIBINTL""@ instead of +@""INTLLIBS""@. Which one, depends whether it is used with libtool or not. +@""INTLLIBS""@ will go away. +" + else + please="$please +Please change $file to use @""LIBINTL""@ instead of @""INTLLIBS""@. +@""INTLLIBS""@ will go away. +" + fi + fi + # DATADIRNAME is deprecated because we install only .gmo files nowadays, + # which can be stored in the platform independent $prefix/share hierarchy. + if grep '@''DATADIRNAME''@' "$srcdir/$file" >/dev/null; then + please="$please +Please change $file to use the constant string \"share\" instead of +@""DATADIRNAME""@. @""DATADIRNAME""@ will go away. +" + fi + # INSTOBJEXT is deprecated because we install only .gmo files nowadays, + # no catgets .cat catalogs. + if grep '@''INSTOBJEXT''@' "$srcdir/$file" >/dev/null; then + please="$please +Please change $file to use the constant string \".mo\" instead of +@""INSTOBJEXT""@. @""INSTOBJEXT""@ will go away. +" + fi + # GENCAT is deprecated because we install no catgets catalogs anymore. + if grep '@''GENCAT''@' "$srcdir/$file" >/dev/null; then + please="$please +Please change $file to use the constant string \"gencat\" instead of +@""GENCAT""@. @""GENCAT""@ will go away. Maybe you don't even need it any more? +" + fi + # POSUB is deprecated because it causes "./configure --disable-nls", "make", + # "make dist" to create a buggy tarfile. + if grep '@''POSUB''@' "$srcdir/$file" >/dev/null; then + please="$please +Please change $file to use the constant string \"po\" instead of +@""POSUB""@. @""POSUB""@ will go away. +" + fi + fi +done + +# Recommend replacement for deprecated configure variables. +if grep '\$nls_cv_header_' "$srcdir/$configure_in" >/dev/null; then + please="$please +Please stop using \$nls_cv_header_intl or \$nls_cv_header_libgt in the +$configure_in file. Both will go away. Use or \"gettext.h\" instead. +" +fi + +# Recommend fetching config.guess and config.sub. +if test -f "$srcdir/$auxdir"config.guess && test -f "$srcdir/$auxdir"config.sub; then + : +else + please="$please +You will also need config.guess and config.sub, which you can get from the CVS +of the 'config' project at https://savannah.gnu.org/. The commands to fetch them +are +\$ wget 'https://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/config/config/config.guess' +\$ wget 'https://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/config/config/config.sub' +" +fi + +if $doit; then + echo "$please" + echo "You might also want to copy the convenience header file gettext.h" + echo "from the $gettext_datadir directory into your package." + echo "It is a wrapper around that implements the configure --disable-nls" + echo "option." + echo + count=`echo "$please" | grep '^$' | wc -l` + count=`echo "$count" | sed -e 's/[ ]//g'` + case "$count" in + 1) count="paragraph";; + 2) count="two paragraphs";; + 3) count="three paragraphs";; + 4) count="four paragraphs";; + 5) count="five paragraphs";; + *) count="$count paragraphs";; + esac + echo "Press Return to acknowledge the previous $count." + # Read from /dev/tty, not stdin, so that gettextize cannot be abused by + # non-interactive tools. + read dummy < /dev/tty +fi + +exit 0 diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msgattrib b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msgattrib new file mode 100644 index 0000000000000000000000000000000000000000..aaff3592837cd1ec287e968fe9a1821ea12bba54 Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msgattrib differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msgcat b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msgcat new file mode 100644 index 0000000000000000000000000000000000000000..ed11c3c6521da8efc1ef44539d9de6fe8fa8f020 Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msgcat differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msgcmp b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msgcmp new file mode 100644 index 0000000000000000000000000000000000000000..7aaf65720e180ae3b030c3f16e8a5817faa423cb Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msgcmp differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msgcomm b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msgcomm new file mode 100644 index 0000000000000000000000000000000000000000..b1555a40415c4b750d08b72f93dd10ba56f83856 Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msgcomm differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msgconv b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msgconv new file mode 100644 index 0000000000000000000000000000000000000000..f937d630a22dd06a95a441cd19d82d1fd8cd690c Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msgconv differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msgen b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msgen new file mode 100644 index 0000000000000000000000000000000000000000..390e61378ebb115e9ba1dc098d4385ad25f20262 Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msgen differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msgexec b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msgexec new file mode 100644 index 0000000000000000000000000000000000000000..cbfcb167e0a7d4ce15da7dccbe5996ff9434790e Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msgexec differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msgfilter b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msgfilter new file mode 100644 index 0000000000000000000000000000000000000000..592cbe13e5587fa99674363b1d1754f5648958fb Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msgfilter differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msginit b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msginit new file mode 100644 index 0000000000000000000000000000000000000000..1c54c4e3eeeeef089d7852861bdcaf09c29de348 Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msginit differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msgmerge b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msgmerge new file mode 100644 index 0000000000000000000000000000000000000000..c61dbf870580902de42c067b96f0459624ef07b0 Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msgmerge differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msgunfmt b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msgunfmt new file mode 100644 index 0000000000000000000000000000000000000000..6562e752280d6cfaac21233182ba4fb31c1075ff Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msgunfmt differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msguniq b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msguniq new file mode 100644 index 0000000000000000000000000000000000000000..6cbf313d5d372c1848b2eca5e9b675de612af145 Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/msguniq differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/ngettext b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/ngettext new file mode 100644 index 0000000000000000000000000000000000000000..5dcae05b42e3740602d427fe2c04c5210c73eb01 Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/ngettext differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/recode-sr-latin b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/recode-sr-latin new file mode 100644 index 0000000000000000000000000000000000000000..7f3ea279ab4e7aec3a7c51b706f746984315c52b Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/bin/recode-sr-latin differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/include/textstyle.h b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/include/textstyle.h new file mode 100644 index 0000000000000000000000000000000000000000..ce0bf6e019e43c6f12882f2b45f7d39b1eae6f58 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/include/textstyle.h @@ -0,0 +1,707 @@ +/* Public API of the libtextstyle library. + Copyright (C) 2006-2007, 2019-2021 Free Software Foundation, Inc. + + 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 . */ + +/* Written by Bruno Haible , 2006, 2019. */ + +#ifndef _TEXTSTYLE_H +#define _TEXTSTYLE_H + +#include +#include +#include +#include +#include + +/* Meta information. */ +#include + +/* ----------------------------- From ostream.h ----------------------------- */ + +/* Describes the scope of a flush operation. */ +typedef enum +{ + /* Flushes buffers in this ostream_t. + Use this value if you want to write to the underlying ostream_t. */ + FLUSH_THIS_STREAM = 0, + /* Flushes all buffers in the current process. + Use this value if you want to write to the same target through a + different file descriptor or a FILE stream. */ + FLUSH_THIS_PROCESS = 1, + /* Flushes buffers in the current process and attempts to flush the buffers + in the kernel. + Use this value so that some other process (or the kernel itself) + may write to the same target. */ + FLUSH_ALL = 2 +} ostream_flush_scope_t; + + +/* An output stream is an object to which one can feed a sequence of bytes. */ + +struct any_ostream_representation; +typedef struct any_ostream_representation * ostream_t; + +/* Functions that invoke the methods. */ +#ifdef __cplusplus +extern "C" { +#endif +extern void ostream_write_mem (ostream_t first_arg, const void *data, size_t len); +extern void ostream_flush (ostream_t first_arg, ostream_flush_scope_t scope); +extern void ostream_free (ostream_t first_arg); +#ifdef __cplusplus +} +#endif + +#ifdef __cplusplus +extern "C" { +#endif + +/* Write a string's contents to a stream. */ +extern void ostream_write_str (ostream_t stream, const char *string); + +/* Writes formatted output to a stream. + Returns the size of formatted output, or a negative value in case of an + error. */ +extern ptrdiff_t ostream_printf (ostream_t stream, const char *format, ...) +#if (__GNUC__ == 3 && __GNUC_MINOR__ >= 1) || __GNUC__ > 3 + __attribute__ ((__format__ (__printf__, 2, 3))) +#endif + ; +extern ptrdiff_t ostream_vprintf (ostream_t stream, + const char *format, va_list args) +#if (__GNUC__ == 3 && __GNUC_MINOR__ >= 1) || __GNUC__ > 3 + __attribute__ ((__format__ (__printf__, 2, 0))) +#endif + ; + +#ifdef __cplusplus +} +#endif + +/* ------------------------- From styled-ostream.h ------------------------- */ + +/* A styled output stream is an object to which one can feed a sequence of + bytes, marking some runs of text as belonging to specific CSS classes, + where the rendering of the CSS classes is defined through a CSS (cascading + style sheet). */ + +/* styled_ostream_t is a subtype of ostream_t. */ +typedef ostream_t styled_ostream_t; + +/* Functions that invoke the methods. */ +#ifdef __cplusplus +extern "C" { +#endif +extern void styled_ostream_write_mem (styled_ostream_t first_arg, const void *data, size_t len); +extern void styled_ostream_flush (styled_ostream_t first_arg, ostream_flush_scope_t scope); +extern void styled_ostream_free (styled_ostream_t first_arg); +extern void styled_ostream_begin_use_class (styled_ostream_t first_arg, const char *classname); +extern void styled_ostream_end_use_class (styled_ostream_t first_arg, const char *classname); +extern const char *styled_ostream_get_hyperlink_ref (styled_ostream_t first_arg); +extern const char *styled_ostream_get_hyperlink_id (styled_ostream_t first_arg); +extern void styled_ostream_set_hyperlink (styled_ostream_t first_arg, const char *ref, const char *id); +/* Like styled_ostream_flush (first_arg, FLUSH_THIS_STREAM), except that it + leaves the destination with the current text style enabled, instead + of with the default text style. + After calling this function, you can output strings without newlines(!) + to the underlying stream, and they will be rendered like strings passed + to 'ostream_write_mem', 'ostream_write_str', or 'ostream_write_printf'. */ +extern void styled_ostream_flush_to_current_style (styled_ostream_t stream); +#ifdef __cplusplus +} +#endif + +#ifdef __cplusplus +extern "C" { +#endif + + +/* Test whether a given output stream is a styled_ostream. */ +extern bool is_instance_of_styled_ostream (ostream_t stream); + + +#ifdef __cplusplus +} +#endif + +/* -------------------------- From file-ostream.h -------------------------- */ + +/* file_ostream_t is a subtype of ostream_t. */ +typedef ostream_t file_ostream_t; + +/* Functions that invoke the methods. */ +#ifdef __cplusplus +extern "C" { +#endif +extern void file_ostream_write_mem (file_ostream_t first_arg, const void *data, size_t len); +extern void file_ostream_flush (file_ostream_t first_arg, ostream_flush_scope_t scope); +extern void file_ostream_free (file_ostream_t first_arg); +/* Accessors. */ +extern FILE *file_ostream_get_stdio_stream (file_ostream_t stream); +#ifdef __cplusplus +} +#endif + +#ifdef __cplusplus +extern "C" { +#endif + + +/* Create an output stream referring to FP. + Note that the resulting stream must be closed before FP can be closed. */ +extern file_ostream_t file_ostream_create (FILE *fp); + + +/* Test whether a given output stream is a file_ostream. */ +extern bool is_instance_of_file_ostream (ostream_t stream); + + +#ifdef __cplusplus +} +#endif + +/* --------------------------- From fd-ostream.h --------------------------- */ + +/* fd_ostream_t is a subtype of ostream_t. */ +typedef ostream_t fd_ostream_t; + +/* Functions that invoke the methods. */ +#ifdef __cplusplus +extern "C" { +#endif +extern void fd_ostream_write_mem (fd_ostream_t first_arg, const void *data, size_t len); +extern void fd_ostream_flush (fd_ostream_t first_arg, ostream_flush_scope_t scope); +extern void fd_ostream_free (fd_ostream_t first_arg); +/* Accessors. */ +extern int fd_ostream_get_descriptor (fd_ostream_t stream); +extern const char *fd_ostream_get_filename (fd_ostream_t stream); +extern bool fd_ostream_is_buffered (fd_ostream_t stream); +#ifdef __cplusplus +} +#endif + +#ifdef __cplusplus +extern "C" { +#endif + + +/* Create an output stream referring to the file descriptor FD. + FILENAME is used only for error messages. + Note that the resulting stream must be closed before FD can be closed. */ +extern fd_ostream_t fd_ostream_create (int fd, const char *filename, + bool buffered); + + +/* Test whether a given output stream is a fd_ostream. */ +extern bool is_instance_of_fd_ostream (ostream_t stream); + + +#ifdef __cplusplus +} +#endif + +/* -------------------------- From term-ostream.h -------------------------- */ + +/* Querying and setting of text attributes. + The stream has a notion of the current text attributes; they apply + implicitly to all following output. The attributes are automatically + reset when the stream is closed. + Note: Not all terminal types can actually render all attributes adequately. + For example, xterm cannot render POSTURE_ITALIC nor the combination of + WEIGHT_BOLD and UNDERLINE_ON. */ + +/* Colors are represented by indices >= 0 in a stream dependent format. */ +typedef int term_color_t; +/* The value -1 denotes the default (foreground or background) color. */ +enum +{ + COLOR_DEFAULT = -1 /* unknown */ +}; + +typedef enum +{ + WEIGHT_NORMAL = 0, + WEIGHT_BOLD, + WEIGHT_DEFAULT = WEIGHT_NORMAL +} term_weight_t; + +typedef enum +{ + POSTURE_NORMAL = 0, + POSTURE_ITALIC, /* same as oblique */ + POSTURE_DEFAULT = POSTURE_NORMAL +} term_posture_t; + +typedef enum +{ + UNDERLINE_OFF = 0, + UNDERLINE_ON, + UNDERLINE_DEFAULT = UNDERLINE_OFF +} term_underline_t; + +/* The amount of control to take over the underlying tty in order to avoid + garbled output on the screen, due to interleaved output of escape sequences + and output from the kernel (such as when the kernel echoes user's input + or when the kernel prints '^C' after the user pressed Ctrl-C). */ +typedef enum +{ + TTYCTL_AUTO = 0, /* Automatic best-possible choice. */ + TTYCTL_NONE, /* No control. + Result: Garbled output can occur, and the terminal can + be left in any state when the program is interrupted. */ + TTYCTL_PARTIAL, /* Signal handling. + Result: Garbled output can occur, but the terminal will + be left in the default state when the program is + interrupted. */ + TTYCTL_FULL /* Signal handling and disabling echo and flush-upon-signal. + Result: No garbled output, and the the terminal will + be left in the default state when the program is + interrupted. */ +} ttyctl_t; + +/* term_ostream_t is a subtype of ostream_t. */ +typedef ostream_t term_ostream_t; + +/* Functions that invoke the methods. */ +#ifdef __cplusplus +extern "C" { +#endif +extern void term_ostream_write_mem (term_ostream_t first_arg, const void *data, size_t len); +extern void term_ostream_flush (term_ostream_t first_arg, ostream_flush_scope_t scope); +extern void term_ostream_free (term_ostream_t first_arg); +extern term_color_t term_ostream_rgb_to_color (term_ostream_t first_arg, int red, int green, int blue); +extern term_color_t term_ostream_get_color (term_ostream_t first_arg); +extern void term_ostream_set_color (term_ostream_t first_arg, term_color_t color); +extern term_color_t term_ostream_get_bgcolor (term_ostream_t first_arg); +extern void term_ostream_set_bgcolor (term_ostream_t first_arg, term_color_t color); +extern term_weight_t term_ostream_get_weight (term_ostream_t first_arg); +extern void term_ostream_set_weight (term_ostream_t first_arg, term_weight_t weight); +extern term_posture_t term_ostream_get_posture (term_ostream_t first_arg); +extern void term_ostream_set_posture (term_ostream_t first_arg, term_posture_t posture); +extern term_underline_t term_ostream_get_underline (term_ostream_t first_arg); +extern void term_ostream_set_underline (term_ostream_t first_arg, term_underline_t underline); +extern const char *term_ostream_get_hyperlink_ref (term_ostream_t first_arg); +extern const char *term_ostream_get_hyperlink_id (term_ostream_t first_arg); +extern void term_ostream_set_hyperlink (term_ostream_t first_arg, const char *ref, const char *id); +/* Like term_ostream_flush (first_arg, FLUSH_THIS_STREAM), except that it + leaves the terminal with the current text attributes enabled, instead of + with the default text attributes. + After calling this function, you can output strings without newlines(!) + to the underlying file descriptor, and they will be rendered like strings + passed to 'ostream_write_mem', 'ostream_write_str', or + 'ostream_write_printf'. */ +extern void term_ostream_flush_to_current_style (term_ostream_t first_arg); +/* Accessors. */ +extern int term_ostream_get_descriptor (term_ostream_t stream); +extern const char *term_ostream_get_filename (term_ostream_t stream); +extern ttyctl_t term_ostream_get_tty_control (term_ostream_t stream); +extern ttyctl_t term_ostream_get_effective_tty_control (term_ostream_t stream); +#ifdef __cplusplus +} +#endif + +#ifdef __cplusplus +extern "C" { +#endif + + +/* Create an output stream referring to the file descriptor FD. + FILENAME is used only for error messages. + TTY_CONTROL specifies the amount of control to take over the underlying tty. + The resulting stream will be line-buffered. + Note that the resulting stream must be closed before FD can be closed. */ +extern term_ostream_t + term_ostream_create (int fd, const char *filename, ttyctl_t tty_control); + + +/* Test whether a given output stream is a term_ostream. */ +extern bool is_instance_of_term_ostream (ostream_t stream); + + +#ifdef __cplusplus +} +#endif + +/* ------------------------- From memory-ostream.h ------------------------- */ + +/* memory_ostream_t is a subtype of ostream_t. */ +typedef ostream_t memory_ostream_t; + +/* Functions that invoke the methods. */ +#ifdef __cplusplus +extern "C" { +#endif +extern void memory_ostream_write_mem (memory_ostream_t first_arg, const void *data, size_t len); +extern void memory_ostream_flush (memory_ostream_t first_arg, ostream_flush_scope_t scope); +extern void memory_ostream_free (memory_ostream_t first_arg); +extern void memory_ostream_contents (memory_ostream_t first_arg, const void **bufp, size_t *buflenp); +#ifdef __cplusplus +} +#endif + +#ifdef __cplusplus +extern "C" { +#endif + + +/* Create an output stream that accumulates the output in a memory buffer. */ +extern memory_ostream_t memory_ostream_create (void); + + +/* Test whether a given output stream is a memory_ostream. */ +extern bool is_instance_of_memory_ostream (ostream_t stream); + + +#ifdef __cplusplus +} +#endif + +/* -------------------------- From iconv-ostream.h -------------------------- */ + +#if LIBTEXTSTYLE_USES_ICONV + +/* iconv_ostream_t is a subtype of ostream_t. */ +typedef ostream_t iconv_ostream_t; + +/* Functions that invoke the methods. */ +#ifdef __cplusplus +extern "C" { +#endif +extern void iconv_ostream_write_mem (iconv_ostream_t first_arg, const void *data, size_t len); +extern void iconv_ostream_flush (iconv_ostream_t first_arg, ostream_flush_scope_t scope); +extern void iconv_ostream_free (iconv_ostream_t first_arg); +/* Accessors. */ +extern const char *iconv_ostream_get_from_encoding (iconv_ostream_t stream); +extern const char *iconv_ostream_get_to_encoding (iconv_ostream_t stream); +extern ostream_t iconv_ostream_get_destination (iconv_ostream_t stream); +#ifdef __cplusplus +} +#endif + +#ifdef __cplusplus +extern "C" { +#endif + + +/* Create an output stream that converts from FROM_ENCODING to TO_ENCODING, + writing the result to DESTINATION. */ +extern iconv_ostream_t iconv_ostream_create (const char *from_encoding, + const char *to_encoding, + ostream_t destination); + + +/* Test whether a given output stream is an iconv_ostream. */ +extern bool is_instance_of_iconv_ostream (ostream_t stream); + + +#ifdef __cplusplus +} +#endif + +#endif /* LIBTEXTSTYLE_USES_ICONV */ + +/* -------------------------- From html-ostream.h -------------------------- */ + +/* html_ostream_t is a subtype of ostream_t. */ +typedef ostream_t html_ostream_t; + +/* Functions that invoke the methods. */ +#ifdef __cplusplus +extern "C" { +#endif +extern void html_ostream_write_mem (html_ostream_t first_arg, const void *data, size_t len); +extern void html_ostream_flush (html_ostream_t first_arg, ostream_flush_scope_t scope); +extern void html_ostream_free (html_ostream_t first_arg); +extern void html_ostream_begin_span (html_ostream_t first_arg, const char *classname); +extern void html_ostream_end_span (html_ostream_t first_arg, const char *classname); +extern const char *html_ostream_get_hyperlink_ref (html_ostream_t first_arg); +extern void html_ostream_set_hyperlink_ref (html_ostream_t first_arg, const char *ref); +/* Like html_ostream_flush (first_arg, FLUSH_THIS_STREAM), except that it + leaves the destination with the current text style enabled, instead + of with the default text style. + After calling this function, you can output strings without newlines(!) + to the underlying stream, and they will be rendered like strings passed + to 'ostream_write_mem', 'ostream_write_str', or 'ostream_write_printf'. */ +extern void html_ostream_flush_to_current_style (html_ostream_t stream); +/* Accessors. */ +extern ostream_t html_ostream_get_destination (html_ostream_t stream); +#ifdef __cplusplus +} +#endif + +#ifdef __cplusplus +extern "C" { +#endif + + +/* Create an output stream that takes input in the UTF-8 encoding and + writes it in HTML form on DESTINATION. + This stream produces a sequence of lines. The caller is responsible + for opening the elements before and for closing them after + the use of this stream. + Note that the resulting stream must be closed before DESTINATION can be + closed. */ +extern html_ostream_t html_ostream_create (ostream_t destination); + + +/* Test whether a given output stream is a html_ostream. */ +extern bool is_instance_of_html_ostream (ostream_t stream); + + +#ifdef __cplusplus +} +#endif + +/* ----------------------- From term-styled-ostream.h ----------------------- */ + +/* term_styled_ostream_t is a subtype of styled_ostream_t. */ +typedef styled_ostream_t term_styled_ostream_t; + +/* Functions that invoke the methods. */ +#ifdef __cplusplus +extern "C" { +#endif +extern void term_styled_ostream_write_mem (term_styled_ostream_t first_arg, const void *data, size_t len); +extern void term_styled_ostream_flush (term_styled_ostream_t first_arg, ostream_flush_scope_t scope); +extern void term_styled_ostream_free (term_styled_ostream_t first_arg); +extern void term_styled_ostream_begin_use_class (term_styled_ostream_t first_arg, const char *classname); +extern void term_styled_ostream_end_use_class (term_styled_ostream_t first_arg, const char *classname); +extern const char *term_styled_ostream_get_hyperlink_ref (term_styled_ostream_t first_arg); +extern const char *term_styled_ostream_get_hyperlink_id (term_styled_ostream_t first_arg); +extern void term_styled_ostream_set_hyperlink (term_styled_ostream_t first_arg, const char *ref, const char *id); +extern void term_styled_ostream_flush_to_current_style (term_styled_ostream_t first_arg); +/* Accessors. */ +extern term_ostream_t term_styled_ostream_get_destination (term_styled_ostream_t stream); +extern const char *term_styled_ostream_get_css_filename (term_styled_ostream_t stream); +#ifdef __cplusplus +} +#endif + +#ifdef __cplusplus +extern "C" { +#endif + + +/* Create an output stream referring to the file descriptor FD, styled with + the file CSS_FILENAME. + FILENAME is used only for error messages. + TTY_CONTROL specifies the amount of control to take over the underlying tty. + Note that the resulting stream must be closed before FD can be closed. + Return NULL upon failure. */ +extern term_styled_ostream_t + term_styled_ostream_create (int fd, const char *filename, + ttyctl_t tty_control, + const char *css_filename); + + +/* Test whether a given output stream is a term_styled_ostream. */ +extern bool is_instance_of_term_styled_ostream (ostream_t stream); + + +#ifdef __cplusplus +} +#endif + +/* ----------------------- From html-styled-ostream.h ----------------------- */ + +/* html_styled_ostream_t is a subtype of styled_ostream_t. */ +typedef styled_ostream_t html_styled_ostream_t; + +/* Functions that invoke the methods. */ +#ifdef __cplusplus +extern "C" { +#endif +extern void html_styled_ostream_write_mem (html_styled_ostream_t first_arg, const void *data, size_t len); +extern void html_styled_ostream_flush (html_styled_ostream_t first_arg, ostream_flush_scope_t scope); +extern void html_styled_ostream_free (html_styled_ostream_t first_arg); +extern void html_styled_ostream_begin_use_class (html_styled_ostream_t first_arg, const char *classname); +extern void html_styled_ostream_end_use_class (html_styled_ostream_t first_arg, const char *classname); +extern const char *html_styled_ostream_get_hyperlink_ref (html_styled_ostream_t first_arg); +extern const char *html_styled_ostream_get_hyperlink_id (html_styled_ostream_t first_arg); +extern void html_styled_ostream_set_hyperlink (html_styled_ostream_t first_arg, const char *ref, const char *id); +extern void html_styled_ostream_flush_to_current_style (html_styled_ostream_t first_arg); +/* Accessors. */ +extern ostream_t html_styled_ostream_get_destination (html_styled_ostream_t stream); +extern html_ostream_t html_styled_ostream_get_html_destination (html_styled_ostream_t stream); +extern const char *html_styled_ostream_get_css_filename (html_styled_ostream_t stream); +#ifdef __cplusplus +} +#endif + +#ifdef __cplusplus +extern "C" { +#endif + + +/* Create an output stream that takes input in the UTF-8 encoding and + writes it in HTML form on DESTINATION, styled with the file CSS_FILENAME. + Note that the resulting stream must be closed before DESTINATION can be + closed. */ +extern html_styled_ostream_t + html_styled_ostream_create (ostream_t destination, + const char *css_filename); + + +/* Test whether a given output stream is a html_styled_ostream. */ +extern bool is_instance_of_html_styled_ostream (ostream_t stream); + + +#ifdef __cplusplus +} +#endif + +/* ----------------------- From noop-styled-ostream.h ----------------------- */ + +/* noop_styled_ostream_t is a subtype of styled_ostream_t. */ +typedef styled_ostream_t noop_styled_ostream_t; + +/* Functions that invoke the methods. */ +#ifdef __cplusplus +extern "C" { +#endif +extern void noop_styled_ostream_write_mem (noop_styled_ostream_t first_arg, const void *data, size_t len); +extern void noop_styled_ostream_flush (noop_styled_ostream_t first_arg, ostream_flush_scope_t scope); +extern void noop_styled_ostream_free (noop_styled_ostream_t first_arg); +extern void noop_styled_ostream_begin_use_class (noop_styled_ostream_t first_arg, const char *classname); +extern void noop_styled_ostream_end_use_class (noop_styled_ostream_t first_arg, const char *classname); +extern const char *noop_styled_ostream_get_hyperlink_ref (noop_styled_ostream_t first_arg); +extern const char *noop_styled_ostream_get_hyperlink_id (noop_styled_ostream_t first_arg); +extern void noop_styled_ostream_set_hyperlink (noop_styled_ostream_t first_arg, const char *ref, const char *id); +extern void noop_styled_ostream_flush_to_current_style (noop_styled_ostream_t first_arg); +/* Accessors. */ +extern ostream_t noop_styled_ostream_get_destination (noop_styled_ostream_t stream); +extern bool noop_styled_ostream_is_owning_destination (noop_styled_ostream_t stream); +#ifdef __cplusplus +} +#endif + +#ifdef __cplusplus +extern "C" { +#endif + + +/* Create an output stream that delegates to DESTINATION and that supports + the styling operations as no-ops. + If PASS_OWNERSHIP is true, closing the resulting stream will automatically + close the DESTINATION. + Note that if PASS_OWNERSHIP is false, the resulting stream must be closed + before DESTINATION can be closed. */ +extern noop_styled_ostream_t + noop_styled_ostream_create (ostream_t destination, bool pass_ownership); + + +/* Test whether a given output stream is a noop_styled_ostream. */ +extern bool is_instance_of_noop_styled_ostream (ostream_t stream); + + +#ifdef __cplusplus +} +#endif + +/* ------------------------------ From color.h ------------------------------ */ + +#ifdef __cplusplus +extern "C" { +#endif + + +/* Whether to output a test page. */ +extern LIBTEXTSTYLE_DLL_VARIABLE bool color_test_mode; + +/* Color option. */ +enum color_option { color_no, color_tty, color_yes, color_html }; +extern LIBTEXTSTYLE_DLL_VARIABLE enum color_option color_mode; + +/* Style to use when coloring. */ +extern LIBTEXTSTYLE_DLL_VARIABLE const char *style_file_name; + +/* --color argument handling. Return an error indicator. */ +extern bool handle_color_option (const char *option); + +/* --style argument handling. */ +extern void handle_style_option (const char *option); + +/* Print a color test page. */ +extern void print_color_test (void); + +/* Assign a default value to style_file_name if necessary. + STYLE_FILE_ENVVAR is an environment variable that, when set to a non-empty + value, specifies the style file to use. This environment variable is meant + to be set by the user. + STYLESDIR_ENVVAR is an environment variable that, when set to a non-empty + value, specifies the directory with the style files, or NULL. This is + necessary for running the testsuite before "make install". + STYLESDIR_AFTER_INSTALL is the directory with the style files after + "make install". + DEFAULT_STYLE_FILE is the file name of the default style file, relative to + STYLESDIR. */ +extern void style_file_prepare (const char *style_file_envvar, + const char *stylesdir_envvar, + const char *stylesdir_after_install, + const char *default_style_file); + + +#ifdef __cplusplus +} +#endif + +/* ------------------------------ From misc.h ------------------------------ */ + +#ifdef __cplusplus +extern "C" { +#endif + +/* Create an output stream referring to the file descriptor FD, styled with + the file CSS_FILENAME if possible. + FILENAME is used only for error messages. + TTY_CONTROL specifies the amount of control to take over the underlying tty. + Note that the resulting stream must be closed before FD can be closed. */ +extern styled_ostream_t + styled_ostream_create (int fd, const char *filename, + ttyctl_t tty_control, + const char *css_filename); + +/* Set the exit value upon failure within libtextstyle. */ +extern void libtextstyle_set_failure_exit_code (int exit_code); + +#ifdef __cplusplus +} +#endif + +/* ----------------------- Exported gnulib overrides ----------------------- */ + +#if defined _WIN32 && ! defined __CYGWIN__ + +# include + +# ifdef __cplusplus +extern "C" { +# endif + +# if !((defined isatty && defined _GL_UNISTD_H) || defined GNULIB_overrides_isatty) /* don't override gnulib */ +extern int libtextstyle_isatty (int fd); +# undef isatty +# define isatty libtextstyle_isatty +# endif + +# ifdef __cplusplus +} +# endif + +#endif + +/* ------------------------------------------------------------------------- */ + +#endif /* _TEXTSTYLE_H */ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/include/textstyle/stdbool.h b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/include/textstyle/stdbool.h new file mode 100644 index 0000000000000000000000000000000000000000..20347b94b1eac39cf7269d5840014e85c28ecbb3 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/include/textstyle/stdbool.h @@ -0,0 +1,117 @@ +/* DO NOT EDIT! GENERATED AUTOMATICALLY! */ +#if !defined _GL_STDBOOL_H +#if (__GNUC__ > 2 || (__GNUC__ == 2 && __GNUC_MINOR__ >= 95)) +#include +#else +/* Copyright (C) 2001-2003, 2006-2017, 2019 Free Software Foundation, Inc. + Written by Bruno Haible , 2001. + + This program 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, 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 Lesser General Public License for more details. + + You should have received a copy of the GNU Lesser General Public License + along with this program; if not, see . */ + +#ifndef _TEXTSTYLE_STDBOOL_H +#define _TEXTSTYLE_STDBOOL_H + +/* ISO C 99 for platforms that lack it. */ + +/* Usage suggestions: + + Programs that use should be aware of some limitations + and standards compliance issues. + + Standards compliance: + + - must be #included before 'bool', 'false', 'true' + can be used. + + - You cannot assume that sizeof (bool) == 1. + + - Programs should not undefine the macros bool, true, and false, + as C99 lists that as an "obsolescent feature". + + Limitations of this substitute, when used in a C89 environment: + + - must be #included before the '_Bool' type can be used. + + - You cannot assume that _Bool is a typedef; it might be a macro. + + - Bit-fields of type 'bool' are not supported. Portable code + should use 'unsigned int foo : 1;' rather than 'bool foo : 1;'. + + - In C99, casts and automatic conversions to '_Bool' or 'bool' are + performed in such a way that every nonzero value gets converted + to 'true', and zero gets converted to 'false'. This doesn't work + with this substitute. With this substitute, only the values 0 and 1 + give the expected result when converted to _Bool' or 'bool'. + + - C99 allows the use of (_Bool)0.0 in constant expressions, but + this substitute cannot always provide this property. + + Also, it is suggested that programs use 'bool' rather than '_Bool'; + this isn't required, but 'bool' is more common. */ + + +/* 7.16. Boolean type and values */ + +#ifdef __cplusplus + /* Assume the compiler has 'bool' and '_Bool'. */ +#else + /* is known to exist and work with the following compilers: + - GNU C 3.0 or newer, on any platform, + - Intel C, + - MSVC 12 (Visual Studio 2013) or newer, + - Sun C, on Solaris, if _STDC_C99 is defined, + - AIX xlc, if _ANSI_C_SOURCE is defined, + - HP C, on HP-UX 11.31 or newer. + It is know not to work with: + - Sun C, on Solaris, if __C99FEATURES__ is defined but _STDC_C99 is not, + - MIPSpro C 7.30, on IRIX. */ +# if (__GNUC__ >= 3) \ + || defined __INTEL_COMPILER \ + || (_MSC_VER >= 1800) \ + || (defined __SUNPRO_C && defined _STDC_C99) \ + || (defined _AIX && !defined __GNUC__ && defined _ANSI_C_SOURCE) \ + || defined __HP_cc + /* Assume the compiler has . */ +# include +# else + /* Need to define _Bool ourselves. As 'signed char' or as an enum type? + Use of a typedef, with SunPRO C, leads to a stupid + "warning: _Bool is a keyword in ISO C99". + Use of an enum type, with IRIX cc, leads to a stupid + "warning(1185): enumerated type mixed with another type". + Even the existence of an enum type, without a typedef, + "Invalid enumerator. (badenum)" with HP-UX cc on Tru64. + The only benefit of the enum, debuggability, is not important + with these compilers. So use 'signed char' and no enum. */ +# define _Bool signed char +# define bool _Bool +# endif +#endif + +/* The other macros must be usable in preprocessor directives. */ +#ifdef __cplusplus +# define false false +# define true true +#else +# undef false +# define false 0 +# undef true +# define true 1 +#endif + +#define __bool_true_false_are_defined 1 + +#endif /* _TEXTSTYLE_STDBOOL_H */ +#endif +#endif diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/include/textstyle/version.h b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/include/textstyle/version.h new file mode 100644 index 0000000000000000000000000000000000000000..4b074b6ed6df75603480de0d302c03da958f97b5 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/include/textstyle/version.h @@ -0,0 +1,44 @@ +/* Meta information about GNU libtextstyle. + Copyright (C) 2009-2010, 2019 Free Software Foundation, Inc. + Written by Bruno Haible , 2009. + + This program 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 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 + Lesser General Public License for more details. + + You should have received a copy of the GNU Lesser General Public License + along with this program. If not, see . */ + +#ifndef _TEXTSTYLE_VERSION_H +#define _TEXTSTYLE_VERSION_H + +/* Get LIBTEXTSTYLE_DLL_VARIABLE. */ +#include + + +#ifdef __cplusplus +extern "C" { +#endif + + +/* Version number: (major<<16) + (minor<<8) + subminor. */ +#define _LIBTEXTSTYLE_VERSION 0x001900 +extern LIBTEXTSTYLE_DLL_VARIABLE const int _libtextstyle_version; /* Likewise */ + + +/* 1 if libtextstyle was built with iconv support, 0 if not. */ +#define LIBTEXTSTYLE_USES_ICONV 1 + + +#ifdef __cplusplus +} +#endif + + +#endif /* _TEXTSTYLE_VERSION_H */ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/include/textstyle/woe32dll.h b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/include/textstyle/woe32dll.h new file mode 100644 index 0000000000000000000000000000000000000000..195f897a1eab474af3f98d589b807ba749c15cc5 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/include/textstyle/woe32dll.h @@ -0,0 +1,30 @@ +/* Support for variables in shared libraries on Windows platforms. + Copyright (C) 2009, 2019 Free Software Foundation, Inc. + + This program 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 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 + Lesser General Public License for more details. + + You should have received a copy of the GNU Lesser General Public License + along with this program. If not, see . */ + +/* Written by Bruno Haible , 2009. */ + +#ifndef _TEXTSTYLE_WOE32DLL_H +#define _TEXTSTYLE_WOE32DLL_H + +#ifdef IN_LIBTEXTSTYLE +/* All code is collected in a single library, */ +# define LIBTEXTSTYLE_DLL_VARIABLE +#else +/* References from outside of libtextstyle. */ +# define LIBTEXTSTYLE_DLL_VARIABLE +#endif + +#endif /* _TEXTSTYLE_WOE32DLL_H */ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/about.json b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/about.json new file mode 100644 index 0000000000000000000000000000000000000000..c037908688558175c12f42dbf1cfa67cffb3ae91 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/about.json @@ -0,0 +1,184 @@ +{ + "channels": [ + "https://repo.anaconda.com/pkgs/main", + "https://repo.anaconda.com/pkgs/main" + ], + "conda_build_version": "26.1.0", + "conda_version": "26.1.0", + "env_vars": { + "CIO_TEST": "" + }, + "extra": { + "copy_test_source_files": true, + "feedstock-name": "gettext", + "final": true, + "parent_recipe": { + "name": "gettext-split", + "path": "/home/task_177204486800161/gettext-feedstock/recipe", + "version": "0.25.1" + }, + "pbp_graph_uuid": "3e8405fd-0d33-4442-9c6e-741a46b5c97d", + "recipe-maintainers": [ + "scopatz", + "ocefpaf", + "pkgw", + "xhochy" + ], + "remote_url": "https://github.com/AnacondaRecipes/gettext-feedstock", + "sha": "4bf3d3ea276e8ac4d8833cf6edee3f440fe7f401", + "task_id": "AU3TsZcCRaK9jiaCosfOMQ", + "task_run_id": "0" + }, + "home": "https://www.gnu.org/software/gettext", + "identifiers": [], + "keywords": [], + "license": "GPL-3.0-or-later", + "license_file": "COPYING", + "root_pkgs": [ + "_libgcc_mutex 0.1 main", + "ca-certificates 2025.12.2 h06a4308_0", + "ld_impl_linux-64 2.40 h12ee557_0", + "libstdcxx-ng 11.2.0 h1234567_1", + "nlohmann_json 3.11.2 h6a678d5_0", + "pybind11-abi 5 hd3eb1b0_0", + "tzdata 2025b h04d1e81_0", + "libgomp 11.2.0 h1234567_1", + "_openmp_mutex 5.1 1_gnu", + "libgcc-ng 11.2.0 h1234567_1", + "bzip2 1.0.8 h5eee18b_6", + "c-ares 1.19.1 h5eee18b_0", + "cpp-expected 1.1.0 hdb19cb5_0", + "expat 2.7.1 h6a678d5_0", + "fmt 9.1.0 hdb19cb5_1", + "icu 73.1 h6a678d5_0", + "libev 4.33 h7f8727e_1", + "libffi 3.4.4 h6a678d5_1", + "libuuid 1.41.5 h5eee18b_0", + "lz4-c 1.9.4 h6a678d5_1", + "ncurses 6.4 h6a678d5_0", + "libiconv 1.16 h5eee18b_3", + "pthread-stubs 0.3 h0ce48e5_1", + "reproc 14.2.4 h6a678d5_2", + "simdjson 3.10.1 hdb19cb5_0", + "xorg-libxau 1.0.12 h9b100fa_0", + "xorg-libxdmcp 1.1.5 h9b100fa_0", + "xorg-xorgproto 2024.1 h5eee18b_1", + "xz 5.6.4 h5eee18b_1", + "yaml-cpp 0.8.0 h6a678d5_1", + "zlib 1.2.13 h5eee18b_1", + "libedit 3.1.20230828 h5eee18b_0", + "libnghttp2 1.57.0 h2d74bed_0", + "libssh2 1.11.1 h251f7ec_0", + "libxcb 1.17.0 h9b100fa_0", + "libxml2 2.13.8 hfdd30dd_0", + "pcre2 10.42 hebb0a14_1", + "readline 8.2 h5eee18b_0", + "reproc-cpp 14.2.4 h6a678d5_2", + "spdlog 1.11.0 hdb19cb5_0", + "zstd 1.5.6 hc292b87_0", + "krb5 1.21.3 h8a1dbc1_1", + "libarchive 3.7.7 hfab0078_0", + "libsolv 0.7.30 he621ea3_1", + "sqlite 3.50.2 hb25bd0a_1", + "xorg-libx11 1.8.12 h9b100fa_1", + "patch 2.8 hb25bd0a_0", + "libmamba 2.0.5 haf1ee3a_1", + "python 3.12.11 h22baa00_0", + "menuinst 2.3.0 py312h06a4308_0", + "anaconda-anon-usage 0.7.1 py312hfc0e8ea_100", + "annotated-types 0.6.0 py312h06a4308_0", + "archspec 0.2.3 pyhd3eb1b0_0", + "boltons 25.0.0 py312h06a4308_0", + "charset-normalizer 3.3.2 pyhd3eb1b0_0", + "distro 1.9.0 py312h06a4308_0", + "frozendict 2.4.2 py312h06a4308_0", + "idna 3.7 py312h06a4308_0", + "jsonpointer 2.1 pyhd3eb1b0_0", + "libmambapy 2.0.5 py312hdb19cb5_1", + "mdurl 0.1.0 py312h06a4308_0", + "packaging 24.2 py312h06a4308_0", + "platformdirs 4.3.7 py312h06a4308_0", + "pluggy 1.5.0 py312h06a4308_0", + "pycosat 0.6.6 py312h5eee18b_2", + "pycparser 2.21 pyhd3eb1b0_0", + "pygments 2.19.1 py312h06a4308_0", + "pysocks 1.7.1 py312h06a4308_0", + "ruamel.yaml.clib 0.2.12 py312h5eee18b_0", + "setuptools 78.1.1 py312h06a4308_0", + "tqdm 4.67.1 py312he106c6f_0", + "truststore 0.10.0 py312h06a4308_0", + "typing_extensions 4.12.2 py312h06a4308_0", + "wheel 0.45.1 py312h06a4308_0", + "cffi 1.17.1 py312h1fdaa30_1", + "jsonpatch 1.33 py312h06a4308_1", + "markdown-it-py 2.2.0 py312h06a4308_1", + "pip 25.1 pyhc872135_2", + "ruamel.yaml 0.18.10 py312h5eee18b_0", + "typing-extensions 4.12.2 py312h06a4308_0", + "typing-inspection 0.4.0 py312h06a4308_0", + "brotlicffi 1.0.9.2 py312h6a678d5_1", + "cryptography 45.0.3 py312h2ccb017_0", + "pydantic-core 2.33.2 py312hc6f7160_0", + "rich 13.9.4 py312h06a4308_0", + "zstandard 0.23.0 py312h2c38b39_1", + "conda-content-trust 0.2.0 py312h06a4308_1", + "pydantic 2.11.7 py312h06a4308_0", + "urllib3 2.5.0 py312h06a4308_0", + "requests 2.32.4 py312h06a4308_0", + "conda-package-streaming 0.12.0 py312h06a4308_0", + "conda-package-handling 2.4.0 py312h06a4308_0", + "conda-anaconda-tos 0.2.1 py312h06a4308_0", + "libsodium 1.0.20 heac8642_0", + "libunistring 1.3 hb25bd0a_0", + "mbedtls 3.5.1 h6a678d5_1", + "openssl 3.0.18 hd6dcaed_0", + "patchelf 0.17.2 h6a678d5_0", + "perl 5.40.2 0_h5eee18b_perl5", + "yaml 0.2.5 h7b6447c_0", + "liblief 0.16.4 h6a678d5_0", + "gettext 0.21.0 hedfda30_2", + "libidn2 2.3.8 hf80d704_0", + "tk 8.6.15 h54e0aa7_0", + "libcurl 8.16.0 heebcbe5_0", + "git 2.51.0 pl5382h000ed5b_0", + "argcomplete 3.6.2 py312h06a4308_0", + "attrs 25.4.0 py312h06a4308_2", + "certifi 2026.01.04 py312h06a4308_0", + "chardet 5.2.0 py312h06a4308_0", + "click 8.2.1 py312h06a4308_1", + "evalidate 2.0.3 py312h06a4308_0", + "filelock 3.20.3 py312h06a4308_0", + "jmespath 1.1.0 py312h06a4308_0", + "markupsafe 3.0.2 py312h5eee18b_0", + "msgpack-python 1.1.1 py312h6a678d5_0", + "pkginfo 1.12.1.2 py312h06a4308_0", + "psutil 7.0.0 py312hee96239_1", + "py-lief 0.16.4 py312h6a678d5_0", + "python-libarchive-c 5.3 py312h06a4308_0", + "pytz 2025.2 py312h06a4308_0", + "pyyaml 6.0.2 py312h5eee18b_0", + "rpds-py 0.28.0 py312h498d7c9_0", + "six 1.17.0 py312h06a4308_0", + "soupsieve 2.5 py312h06a4308_0", + "tomlkit 0.13.3 py312h06a4308_0", + "xmltodict 1.0.2 py312h06a4308_0", + "jinja2 3.1.6 py312h06a4308_0", + "python-dateutil 2.9.0post0 py312h06a4308_2", + "referencing 0.37.0 py312h06a4308_0", + "yq 3.4.3 py312h06a4308_0", + "beautifulsoup4 4.14.3 py312h06a4308_0", + "jsonschema-specifications 2025.9.1 py312h06a4308_0", + "pynacl 1.6.0 py312h2630517_0", + "jsonschema 4.25.1 py312h06a4308_0", + "botocore 1.42.34 py312h06a4308_0", + "s3transfer 0.16.0 py312h06a4308_0", + "boto3 1.42.34 py312h06a4308_0", + "conda 26.1.0 py312h06a4308_0", + "conda-anaconda-telemetry 0.3.0 pyhd3eb1b0_1", + "conda-index 0.7.0 py312h06a4308_1", + "conda-libmamba-solver 25.11.0 pyhdf14ebd_0", + "conda-build 26.1.0 py312h76456e7_0" + ], + "summary": "Internationalization package (executable tools)", + "tags": [] +} \ No newline at end of file diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/files b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/files new file mode 100644 index 0000000000000000000000000000000000000000..8b914afaf81a56fc210d42f0247884c2d9c65026 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/files @@ -0,0 +1,271 @@ +bin/autopoint +bin/envsubst +bin/gettext +bin/gettext.sh +bin/gettextize +bin/msgattrib +bin/msgcat +bin/msgcmp +bin/msgcomm +bin/msgconv +bin/msgen +bin/msgexec +bin/msgfilter +bin/msgfmt +bin/msggrep +bin/msginit +bin/msgmerge +bin/msgunfmt +bin/msguniq +bin/ngettext +bin/recode-sr-latin +bin/xgettext +include/textstyle.h +include/textstyle/stdbool.h +include/textstyle/version.h +include/textstyle/woe32dll.h +lib/libgettextlib-0.25.1.so +lib/libgettextlib.so +lib/libgettextsrc-0.25.1.so +lib/libgettextsrc.so +lib/libtextstyle.so +lib/libtextstyle.so.0 +lib/libtextstyle.so.0.2.5 +lib/preloadable_libintl.so +libexec/gettext/cldr-plurals +libexec/gettext/hostname +libexec/gettext/project-id +libexec/gettext/urlget +libexec/gettext/user-email +share/aclocal/nls.m4 +share/doc/gettext/FAQ.html +share/doc/gettext/autopoint.1.html +share/doc/gettext/bind_textdomain_codeset.3.html +share/doc/gettext/bindtextdomain.3.html +share/doc/gettext/csharpdoc/GNU_Gettext.html +share/doc/gettext/csharpdoc/GNU_Gettext_GettextResourceManager.html +share/doc/gettext/csharpdoc/GNU_Gettext_GettextResourceSet.html +share/doc/gettext/csharpdoc/begin.html +share/doc/gettext/csharpdoc/index.html +share/doc/gettext/csharpdoc/namespaces.html +share/doc/gettext/envsubst.1.html +share/doc/gettext/gettext.1.html +share/doc/gettext/gettext.3.html +share/doc/gettext/gettext_1.html +share/doc/gettext/gettext_10.html +share/doc/gettext/gettext_11.html +share/doc/gettext/gettext_12.html +share/doc/gettext/gettext_13.html +share/doc/gettext/gettext_14.html +share/doc/gettext/gettext_15.html +share/doc/gettext/gettext_16.html +share/doc/gettext/gettext_17.html +share/doc/gettext/gettext_18.html +share/doc/gettext/gettext_19.html +share/doc/gettext/gettext_2.html +share/doc/gettext/gettext_20.html +share/doc/gettext/gettext_21.html +share/doc/gettext/gettext_22.html +share/doc/gettext/gettext_23.html +share/doc/gettext/gettext_24.html +share/doc/gettext/gettext_25.html +share/doc/gettext/gettext_26.html +share/doc/gettext/gettext_27.html +share/doc/gettext/gettext_28.html +share/doc/gettext/gettext_29.html +share/doc/gettext/gettext_3.html +share/doc/gettext/gettext_30.html +share/doc/gettext/gettext_4.html +share/doc/gettext/gettext_5.html +share/doc/gettext/gettext_6.html +share/doc/gettext/gettext_7.html +share/doc/gettext/gettext_8.html +share/doc/gettext/gettext_9.html +share/doc/gettext/gettext_abt.html +share/doc/gettext/gettext_fot.html +share/doc/gettext/gettext_toc.html +share/doc/gettext/gettextize.1.html +share/doc/gettext/msgattrib.1.html +share/doc/gettext/msgcat.1.html +share/doc/gettext/msgcmp.1.html +share/doc/gettext/msgcomm.1.html +share/doc/gettext/msgconv.1.html +share/doc/gettext/msgen.1.html +share/doc/gettext/msgexec.1.html +share/doc/gettext/msgfilter.1.html +share/doc/gettext/msgfmt.1.html +share/doc/gettext/msggrep.1.html +share/doc/gettext/msginit.1.html +share/doc/gettext/msgmerge.1.html +share/doc/gettext/msgunfmt.1.html +share/doc/gettext/msguniq.1.html +share/doc/gettext/ngettext.1.html +share/doc/gettext/ngettext.3.html +share/doc/gettext/recode-sr-latin.1.html +share/doc/gettext/textdomain.3.html +share/doc/gettext/tutorial.html +share/doc/gettext/xgettext.1.html +share/doc/libasprintf/autosprintf_all.html +share/gettext-0.25.1/its/docbook.loc +share/gettext-0.25.1/its/docbook4.its +share/gettext-0.25.1/its/docbook5.its +share/gettext-0.25.1/its/glade.loc +share/gettext-0.25.1/its/glade1.its +share/gettext-0.25.1/its/glade2.its +share/gettext-0.25.1/its/gsettings.its +share/gettext-0.25.1/its/gsettings.loc +share/gettext-0.25.1/its/gtkbuilder.its +share/gettext-0.25.1/its/metainfo.its +share/gettext-0.25.1/its/metainfo.loc +share/gettext/ABOUT-NLS +share/gettext/archive.dir.tar.xz +share/gettext/config.rpath +share/gettext/disclaim-translations.txt +share/gettext/gettext.h +share/gettext/javaversion.class +share/gettext/m4/build-to-host.m4 +share/gettext/m4/gettext.m4 +share/gettext/m4/host-cpu-c-abi.m4 +share/gettext/m4/iconv.m4 +share/gettext/m4/intlmacosx.m4 +share/gettext/m4/lib-ld.m4 +share/gettext/m4/lib-link.m4 +share/gettext/m4/lib-prefix.m4 +share/gettext/m4/nls.m4 +share/gettext/m4/po.m4 +share/gettext/m4/progtest.m4 +share/gettext/msgunfmt.tcl +share/gettext/po/Makefile.in.in +share/gettext/po/Makevars.template +share/gettext/po/Rules-quot +share/gettext/po/boldquot.sed +share/gettext/po/en@boldquot.header +share/gettext/po/en@quot.header +share/gettext/po/insert-header.sed +share/gettext/po/quot.sed +share/gettext/po/remove-potcdate.sed +share/gettext/schema/its-extensions.xsd +share/gettext/schema/its.xsd10 +share/gettext/schema/its.xsd11 +share/gettext/schema/locating-rules.xsd10 +share/gettext/schema/locating-rules.xsd11 +share/gettext/styles/po-default.css +share/gettext/styles/po-emacs-x.css +share/gettext/styles/po-emacs-xterm.css +share/gettext/styles/po-emacs-xterm16.css +share/gettext/styles/po-emacs-xterm256.css +share/gettext/styles/po-vim.css +share/info/autosprintf.info +share/info/gettext.info +share/info/libtextstyle.info +share/locale/ast/LC_MESSAGES/gettext-runtime.mo +share/locale/be/LC_MESSAGES/gettext-runtime.mo +share/locale/be/LC_MESSAGES/gettext-tools.mo +share/locale/bg/LC_MESSAGES/gettext-runtime.mo +share/locale/bg/LC_MESSAGES/gettext-tools.mo +share/locale/ca/LC_MESSAGES/gettext-runtime.mo +share/locale/ca/LC_MESSAGES/gettext-tools.mo +share/locale/cs/LC_MESSAGES/gettext-runtime.mo +share/locale/cs/LC_MESSAGES/gettext-tools.mo +share/locale/da/LC_MESSAGES/gettext-runtime.mo +share/locale/da/LC_MESSAGES/gettext-tools.mo +share/locale/de/LC_MESSAGES/gettext-runtime.mo +share/locale/de/LC_MESSAGES/gettext-tools.mo +share/locale/el/LC_MESSAGES/gettext-runtime.mo +share/locale/el/LC_MESSAGES/gettext-tools.mo +share/locale/en@boldquot/LC_MESSAGES/gettext-runtime.mo +share/locale/en@boldquot/LC_MESSAGES/gettext-tools.mo +share/locale/en@quot/LC_MESSAGES/gettext-runtime.mo +share/locale/en@quot/LC_MESSAGES/gettext-tools.mo +share/locale/eo/LC_MESSAGES/gettext-runtime.mo +share/locale/es/LC_MESSAGES/gettext-runtime.mo +share/locale/es/LC_MESSAGES/gettext-tools.mo +share/locale/et/LC_MESSAGES/gettext-runtime.mo +share/locale/et/LC_MESSAGES/gettext-tools.mo +share/locale/eu/LC_MESSAGES/gettext-tools.mo +share/locale/fi/LC_MESSAGES/gettext-runtime.mo +share/locale/fi/LC_MESSAGES/gettext-tools.mo +share/locale/fr/LC_MESSAGES/gettext-runtime.mo +share/locale/fr/LC_MESSAGES/gettext-tools.mo +share/locale/ga/LC_MESSAGES/gettext-runtime.mo +share/locale/gl/LC_MESSAGES/gettext-runtime.mo +share/locale/gl/LC_MESSAGES/gettext-tools.mo +share/locale/hr/LC_MESSAGES/gettext-runtime.mo +share/locale/hr/LC_MESSAGES/gettext-tools.mo +share/locale/hu/LC_MESSAGES/gettext-runtime.mo +share/locale/id/LC_MESSAGES/gettext-runtime.mo +share/locale/id/LC_MESSAGES/gettext-tools.mo +share/locale/it/LC_MESSAGES/gettext-runtime.mo +share/locale/it/LC_MESSAGES/gettext-tools.mo +share/locale/ja/LC_MESSAGES/gettext-runtime.mo +share/locale/ja/LC_MESSAGES/gettext-tools.mo +share/locale/ka/LC_MESSAGES/gettext-runtime.mo +share/locale/ka/LC_MESSAGES/gettext-tools.mo +share/locale/ko/LC_MESSAGES/gettext-runtime.mo +share/locale/ko/LC_MESSAGES/gettext-tools.mo +share/locale/nb/LC_MESSAGES/gettext-runtime.mo +share/locale/nb/LC_MESSAGES/gettext-tools.mo +share/locale/nl/LC_MESSAGES/gettext-runtime.mo +share/locale/nl/LC_MESSAGES/gettext-tools.mo +share/locale/nn/LC_MESSAGES/gettext-runtime.mo +share/locale/nn/LC_MESSAGES/gettext-tools.mo +share/locale/pa/LC_MESSAGES/gettext-tools.mo +share/locale/pl/LC_MESSAGES/gettext-runtime.mo +share/locale/pl/LC_MESSAGES/gettext-tools.mo +share/locale/pt/LC_MESSAGES/gettext-runtime.mo +share/locale/pt/LC_MESSAGES/gettext-tools.mo +share/locale/pt_BR/LC_MESSAGES/gettext-runtime.mo +share/locale/pt_BR/LC_MESSAGES/gettext-tools.mo +share/locale/ro/LC_MESSAGES/gettext-runtime.mo +share/locale/ro/LC_MESSAGES/gettext-tools.mo +share/locale/ru/LC_MESSAGES/gettext-runtime.mo +share/locale/ru/LC_MESSAGES/gettext-tools.mo +share/locale/sk/LC_MESSAGES/gettext-runtime.mo +share/locale/sk/LC_MESSAGES/gettext-tools.mo +share/locale/sl/LC_MESSAGES/gettext-runtime.mo +share/locale/sl/LC_MESSAGES/gettext-tools.mo +share/locale/sr/LC_MESSAGES/gettext-runtime.mo +share/locale/sr/LC_MESSAGES/gettext-tools.mo +share/locale/sv/LC_MESSAGES/gettext-runtime.mo +share/locale/sv/LC_MESSAGES/gettext-tools.mo +share/locale/tr/LC_MESSAGES/gettext-runtime.mo +share/locale/tr/LC_MESSAGES/gettext-tools.mo +share/locale/uk/LC_MESSAGES/gettext-runtime.mo +share/locale/uk/LC_MESSAGES/gettext-tools.mo +share/locale/vi/LC_MESSAGES/gettext-runtime.mo +share/locale/vi/LC_MESSAGES/gettext-tools.mo +share/locale/zh_CN/LC_MESSAGES/gettext-runtime.mo +share/locale/zh_CN/LC_MESSAGES/gettext-tools.mo +share/locale/zh_HK/LC_MESSAGES/gettext-runtime.mo +share/locale/zh_TW/LC_MESSAGES/gettext-runtime.mo +share/locale/zh_TW/LC_MESSAGES/gettext-tools.mo +share/man/man1/autopoint.1 +share/man/man1/envsubst.1 +share/man/man1/gettext.1 +share/man/man1/gettextize.1 +share/man/man1/msgattrib.1 +share/man/man1/msgcat.1 +share/man/man1/msgcmp.1 +share/man/man1/msgcomm.1 +share/man/man1/msgconv.1 +share/man/man1/msgen.1 +share/man/man1/msgexec.1 +share/man/man1/msgfilter.1 +share/man/man1/msgfmt.1 +share/man/man1/msggrep.1 +share/man/man1/msginit.1 +share/man/man1/msgmerge.1 +share/man/man1/msgunfmt.1 +share/man/man1/msguniq.1 +share/man/man1/ngettext.1 +share/man/man1/recode-sr-latin.1 +share/man/man1/xgettext.1 +share/man/man3/bind_textdomain_codeset.3 +share/man/man3/bindtextdomain.3 +share/man/man3/dcgettext.3 +share/man/man3/dcngettext.3 +share/man/man3/dgettext.3 +share/man/man3/dngettext.3 +share/man/man3/gettext.3 +share/man/man3/ngettext.3 +share/man/man3/textdomain.3 diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/git b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/git new file mode 100644 index 0000000000000000000000000000000000000000..e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/has_prefix b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/has_prefix new file mode 100644 index 0000000000000000000000000000000000000000..b233b50526fd795795b4f764d0a994e2aea93a7d --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/has_prefix @@ -0,0 +1,32 @@ +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho binary bin/envsubst +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho binary bin/gettext +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho binary bin/msgattrib +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho binary bin/msgcat +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho binary bin/msgcmp +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho binary bin/msgcomm +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho binary bin/msgconv +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho binary bin/msgen +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho binary bin/msgexec +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho binary bin/msgfilter +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho binary bin/msgfmt +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho binary bin/msggrep +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho binary bin/msginit +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho binary bin/msgmerge +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho binary bin/msgunfmt +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho binary bin/msguniq +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho binary bin/ngettext +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho binary bin/recode-sr-latin +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho binary bin/xgettext +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho binary lib/libgettextlib-0.25.1.so +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho binary lib/libgettextsrc-0.25.1.so +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho binary lib/preloadable_libintl.so +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho binary libexec/gettext/cldr-plurals +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho binary libexec/gettext/hostname +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho binary libexec/gettext/urlget +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho text bin/autopoint +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho text bin/gettextize +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho text libexec/gettext/user-email +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho text share/doc/gettext/gettext.1.html +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho text share/doc/gettext/ngettext.1.html +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho text share/man/man1/gettext.1 +/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho text share/man/man1/ngettext.1 diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/hash_input.json b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/hash_input.json new file mode 100644 index 0000000000000000000000000000000000000000..071aac62b3eda6b7c19d92a15c5562075e8356af --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/hash_input.json @@ -0,0 +1,13 @@ +{ + "c_stdlib_version": "2.28", + "cxx_compiler_version": "14.3.0", + "cxx_compiler": "gxx", + "channel_targets": "defaults", + "c_compiler_version": "14.3.0", + "libiconv": "1", + "c_stdlib": "sysroot", + "c_compiler": "gcc", + "target_platform": "linux-64", + "ncurses": "6", + "__glibc": "__glibc >=2.28,<3.0.a0" +} \ No newline at end of file diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/index.json b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/index.json new file mode 100644 index 0000000000000000000000000000000000000000..8953bee5e2c6186e809b9f19b716b654edc998f0 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/index.json @@ -0,0 +1,17 @@ +{ + "arch": "x86_64", + "build": "h6a67909_0", + "build_number": 0, + "depends": [ + "__glibc >=2.28,<3.0.a0", + "libgcc >=14", + "libiconv >=1.18,<2.0a0", + "ncurses >=6.5,<7.0a0" + ], + "license": "GPL-3.0-or-later", + "name": "gettext-tools", + "platform": "linux", + "subdir": "linux-64", + "timestamp": 1772045279414, + "version": "0.25.1" +} \ No newline at end of file diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/licenses/COPYING b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/licenses/COPYING new file mode 100644 index 0000000000000000000000000000000000000000..e60008693e017bec1b4eb49c84be3898e26fcf2a --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/licenses/COPYING @@ -0,0 +1,674 @@ + GNU GENERAL PUBLIC LICENSE + Version 3, 29 June 2007 + + Copyright (C) 2007 Free Software Foundation, Inc. + 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. + + + Copyright (C) + + 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 . + +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: + + Copyright (C) + This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. + This is free software, and you are welcome to redistribute it + under certain conditions; type `show c' for details. + +The hypothetical commands `show w' and `show c' should show the appropriate +parts of the General Public License. Of course, your program's commands +might be different; for a GUI interface, you would use an "about box". + + You should also get your employer (if you work as a programmer) or school, +if any, to sign a "copyright disclaimer" for the program, if necessary. +For more information on this, and how to apply and follow the GNU GPL, see +. + + The GNU General Public License does not permit incorporating your program +into proprietary programs. If your program is a subroutine library, you +may consider it more useful to permit linking proprietary applications with +the library. If this is what you want to do, use the GNU Lesser General +Public License instead of this License. But first, please read +. diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/paths.json b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/paths.json new file mode 100644 index 0000000000000000000000000000000000000000..f3bb2b5bee96cb75103e6cf55b072f09e3f237e8 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/paths.json @@ -0,0 +1,1695 @@ +{ + "paths": [ + { + "_path": "bin/autopoint", + "file_mode": "text", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "e206e49bb1163a52024727d80f81b19efe68db26cabf46b740be705b00e899e8", + "size_in_bytes": 28117 + }, + { + "_path": "bin/envsubst", + "file_mode": "binary", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "6343117f846be294b45e3558a49f21d7a644e1a00e6c114968cf10c128812f56", + "size_in_bytes": 43912 + }, + { + "_path": "bin/gettext", + "file_mode": "binary", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "912635ee0a76539f3d816ca4987802ee31912933d85c46bdf4db25d1868f305d", + "size_in_bytes": 43008 + }, + { + "_path": "bin/gettext.sh", + "path_type": "hardlink", + "sha256": "6779988c6457cf3afbc2c9e13c4f2b45f384c4a35cd0b7df9c5f3e97cbf7f608", + "size_in_bytes": 5167 + }, + { + "_path": "bin/gettextize", + "file_mode": "text", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "7b7467e2560a06542a624b606669e2e3ff9b094b733833ee4f8c6ac88f5e5a5e", + "size_in_bytes": 42543 + }, + { + "_path": "bin/msgattrib", + "file_mode": "binary", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "af42e60ec5727d6d7bae30fc22e236f31dd0cb97d0fc368ce6761ea74b9a58e2", + "size_in_bytes": 36960 + }, + { + "_path": "bin/msgcat", + "file_mode": "binary", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "1addb46abe5c0b75d0d8fc58acb9c8631e0a21733686657e9250928081f9fd97", + "size_in_bytes": 28848 + }, + { + "_path": "bin/msgcmp", + "file_mode": "binary", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "4269ab2b8d10539d3ddb52bc9507cb29c9f2760a9589e94aadc3fbdcff54410c", + "size_in_bytes": 33688 + }, + { + "_path": "bin/msgcomm", + "file_mode": "binary", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "b53d391ee3382581ce22c2a7aa48223ec4e0ceb15bef75df508c8a4eb2a3c826", + "size_in_bytes": 28864 + }, + { + "_path": "bin/msgconv", + "file_mode": "binary", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "857296bcb0358f5f1171e987f5e9e7ce76fdf08ca56b5c03fab8f20d6509ec9b", + "size_in_bytes": 28488 + }, + { + "_path": "bin/msgen", + "file_mode": "binary", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "6fb4876e9e945ed444958a0fa1715d53e5182f3bdb1eb7685e1154ae5a4dc2f7", + "size_in_bytes": 28736 + }, + { + "_path": "bin/msgexec", + "file_mode": "binary", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "484372e4b345c87c9c5fe7a872c6a59e88e370bc4cbbe6a3596e8d8f0d928424", + "size_in_bytes": 28488 + }, + { + "_path": "bin/msgfilter", + "file_mode": "binary", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "c0594c8c911250602ef23700b8f7c72eca580b2c133359030cb2497727a9d55e", + "size_in_bytes": 38152 + }, + { + "_path": "bin/msgfmt", + "file_mode": "binary", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "9755c44078f28be0f538a7c97bc9e7e29d603c6cf7ee68cae5b78bac78279065", + "size_in_bytes": 108568 + }, + { + "_path": "bin/msggrep", + "file_mode": "binary", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "b497a58566f2b7156e008ee87ce850ba0775851f6e38614b2c723b3c920b92cf", + "size_in_bytes": 133808 + }, + { + "_path": "bin/msginit", + "file_mode": "binary", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "4a5e54b5e07c6f3f37c5fb96337204414bbe0084c891ad533a92bed0d05580f2", + "size_in_bytes": 77752 + }, + { + "_path": "bin/msgmerge", + "file_mode": "binary", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "3efb25c583eb5b33fe35f41140317760f78cd21384b7c375342063426f2d42a9", + "size_in_bytes": 82928 + }, + { + "_path": "bin/msgunfmt", + "file_mode": "binary", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "ba1257a07052d732bb9c5234b30e5e3e9bf0978a97ddf48fe3bf0f928baf4444", + "size_in_bytes": 47304 + }, + { + "_path": "bin/msguniq", + "file_mode": "binary", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "6d8ffe71e5000f93a9853e23dbe3f856ec82cf48ae5395780e5717fdece0c270", + "size_in_bytes": 28736 + }, + { + "_path": "bin/ngettext", + "file_mode": "binary", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "d20b0ba70a8082d8a7e90de3d00221ad04ce2f7a1c00a40c4b6ec377258b88f0", + "size_in_bytes": 43112 + }, + { + "_path": "bin/recode-sr-latin", + "file_mode": "binary", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "13816b33726a19a3808c49befcaa16b743cd9bc9106d0f1a1c34cc9db995e0ce", + "size_in_bytes": 23800 + }, + { + "_path": "bin/xgettext", + "file_mode": "binary", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "752f249e3c5cc862f3d934a56025b8b660bbacf2c30c093f53948ad9a1200a11", + "size_in_bytes": 8543840 + }, + { + "_path": "include/textstyle.h", + "path_type": "hardlink", + "sha256": "df3c33c2b737a6bd66602fac40880e9bcc7027994915fe59e21c60ab7d6a2403", + "size_in_bytes": 25886 + }, + { + "_path": "include/textstyle/stdbool.h", + "path_type": "hardlink", + "sha256": "8000f4f1f223f770bc3d885c906783ab0ba8e3062bb1cc54802b90768531c026", + "size_in_bytes": 4315 + }, + { + "_path": "include/textstyle/version.h", + "path_type": "hardlink", + "sha256": "eac0611b4973352c0e311ae2f484e69eed792ac25e7e77521a5be4043913e3e1", + "size_in_bytes": 1348 + }, + { + "_path": "include/textstyle/woe32dll.h", + "path_type": "hardlink", + "sha256": "2aad32eeca2baea944b6ba8b44f26a2a5bf8b4930be0b6236b82a8b461657960", + "size_in_bytes": 1155 + }, + { + "_path": "lib/libgettextlib-0.25.1.so", + "file_mode": "binary", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "ce137c6d8552d92475f45e412401e720fb18476129b6ea952c5deb3c7780bf01", + "size_in_bytes": 2251296 + }, + { + "_path": "lib/libgettextlib.so", + "path_type": "softlink", + "sha256": "ce137c6d8552d92475f45e412401e720fb18476129b6ea952c5deb3c7780bf01", + "size_in_bytes": 2251296 + }, + { + "_path": "lib/libgettextsrc-0.25.1.so", + "file_mode": "binary", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "9e11d2154eb085f5fa7e2a74bb57ea89b90054a147ff37999ad1c25ce22ba3d1", + "size_in_bytes": 429952 + }, + { + "_path": "lib/libgettextsrc.so", + "path_type": "softlink", + "sha256": "9e11d2154eb085f5fa7e2a74bb57ea89b90054a147ff37999ad1c25ce22ba3d1", + "size_in_bytes": 429952 + }, + { + "_path": "lib/libtextstyle.so", + "path_type": "softlink", + "sha256": "9a4f3827bdd64bde94e59984403b6b1dfef3ec56b4c8f9fc60fc0d525d206c9e", + "size_in_bytes": 389896 + }, + { + "_path": "lib/libtextstyle.so.0", + "path_type": "softlink", + "sha256": "9a4f3827bdd64bde94e59984403b6b1dfef3ec56b4c8f9fc60fc0d525d206c9e", + "size_in_bytes": 389896 + }, + { + "_path": "lib/libtextstyle.so.0.2.5", + "path_type": "hardlink", + "sha256": "9a4f3827bdd64bde94e59984403b6b1dfef3ec56b4c8f9fc60fc0d525d206c9e", + "size_in_bytes": 389896 + }, + { + "_path": "lib/preloadable_libintl.so", + "file_mode": "binary", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "289da6e961521967ba317843a9a0faebd672e5ae741195fa399abb41d198c76d", + "size_in_bytes": 57736 + }, + { + "_path": "libexec/gettext/cldr-plurals", + "file_mode": "binary", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "9816786ff70721d03b88fc24fd6916f5a24e4d6ae8336669f2603f9e1d998158", + "size_in_bytes": 42088 + }, + { + "_path": "libexec/gettext/hostname", + "file_mode": "binary", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "13050f8fa9ece58c726d8c3032152814add6974c9f15ede917c472cd778bf498", + "size_in_bytes": 19512 + }, + { + "_path": "libexec/gettext/project-id", + "path_type": "hardlink", + "sha256": "d6ae3f511cc498740005918e41b64517c7cc69fb0259ac3ecd88919f0eae0173", + "size_in_bytes": 2740 + }, + { + "_path": "libexec/gettext/urlget", + "file_mode": "binary", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "e7eb5f8593cb8f825ee6c07a38743c2df7945d8f1f8f9a4178ef7bc5601b7208", + "size_in_bytes": 19576 + }, + { + "_path": "libexec/gettext/user-email", + "file_mode": "text", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "004f925c6c3e50b16bc57acb7c8b8e45a5d915a74aa5888c32cc7720634ae8ed", + "size_in_bytes": 14782 + }, + { + "_path": "share/aclocal/nls.m4", + "path_type": "hardlink", + "sha256": "6ee6943979f6f3cee4d66c330e8b577ad14a578605e3c617cb6266423ba8de2d", + "size_in_bytes": 1245 + }, + { + "_path": "share/doc/gettext/FAQ.html", + "path_type": "hardlink", + "sha256": "18bf217f9a2e1b3cd797a319e3bda6f33baf9496437d49172361d542838390b6", + "size_in_bytes": 45676 + }, + { + "_path": "share/doc/gettext/autopoint.1.html", + "path_type": "hardlink", + "sha256": "28517e77d3789ebc1fb165b903d35ec664a2cd0605bf48beaad7def89d86c382", + "size_in_bytes": 3424 + }, + { + "_path": "share/doc/gettext/bind_textdomain_codeset.3.html", + "path_type": "hardlink", + "sha256": "056cd31d84fcada7b39338325f6d530511c6c78d36888b58af5e4e916efa6d6f", + "size_in_bytes": 4494 + }, + { + "_path": "share/doc/gettext/bindtextdomain.3.html", + "path_type": "hardlink", + "sha256": "6cf6cd7cec90484a03c5df99135fd91fc9c41eb20f00d7df56a46789acaceeac", + "size_in_bytes": 4361 + }, + { + "_path": "share/doc/gettext/csharpdoc/GNU_Gettext.html", + "path_type": "hardlink", + "sha256": "5cea840376dd62d13c449af47fca645d03a92ebe64503b85c62c12e307bd4ca9", + "size_in_bytes": 271 + }, + { + "_path": "share/doc/gettext/csharpdoc/GNU_Gettext_GettextResourceManager.html", + "path_type": "hardlink", + "sha256": "9d93a12d18ebc1efe2af9d803d5353d81c03392c5f48e2a19dc82f72d0f6b6a0", + "size_in_bytes": 8634 + }, + { + "_path": "share/doc/gettext/csharpdoc/GNU_Gettext_GettextResourceSet.html", + "path_type": "hardlink", + "sha256": "707581285c5cd6158576e924d18c92450871785a6f0ef70464f7fbbb78c9f25a", + "size_in_bytes": 10026 + }, + { + "_path": "share/doc/gettext/csharpdoc/begin.html", + "path_type": "hardlink", + "sha256": "daacf888a29717a2110b68b7179fd66f8ef936b356c6e1f469e47757707b2a1a", + "size_in_bytes": 192 + }, + { + "_path": "share/doc/gettext/csharpdoc/index.html", + "path_type": "hardlink", + "sha256": "10e483a9c31e9f387fc88492e35094a18ab09e554b25c952c802d37f8763feaa", + "size_in_bytes": 268 + }, + { + "_path": "share/doc/gettext/csharpdoc/namespaces.html", + "path_type": "hardlink", + "sha256": "e0df32c5bad17a3341e5037e847a760e3eb75fa5963ee37f157632e6f4ff0d7a", + "size_in_bytes": 133 + }, + { + "_path": "share/doc/gettext/envsubst.1.html", + "path_type": "hardlink", + "sha256": "d7013a3d8aa58b715a1b7b4c4c03e7e6d84dd485ea3f6d8d027ed0f07dd7753e", + "size_in_bytes": 3734 + }, + { + "_path": "share/doc/gettext/gettext.1.html", + "file_mode": "text", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "408d221a3c29baa6cf225add942e8d6710878565a63dde997d10fdbea0c63f4f", + "size_in_bytes": 5077 + }, + { + "_path": "share/doc/gettext/gettext.3.html", + "path_type": "hardlink", + "sha256": "6e7f9d7620a4a7cf4d3c9fddb87228cfcee1646a4ed9a76b0f813abf80a98835", + "size_in_bytes": 6345 + }, + { + "_path": "share/doc/gettext/gettext_1.html", + "path_type": "hardlink", + "sha256": "5fce48dd17b81bda6a7cdb3ccb7c54f3c4cc0280adc677054c97d66c3784f73a", + "size_in_bytes": 34749 + }, + { + "_path": "share/doc/gettext/gettext_10.html", + "path_type": "hardlink", + "sha256": "b9bc9ad66a289bfed2abac486fcf2f32b10aaf8a4f8908ae180cb710d02a0968", + "size_in_bytes": 42014 + }, + { + "_path": "share/doc/gettext/gettext_11.html", + "path_type": "hardlink", + "sha256": "a998e182b12ca8a2faaedc57494b055aadee9aa249b668f64303ecbe47ee228c", + "size_in_bytes": 65911 + }, + { + "_path": "share/doc/gettext/gettext_12.html", + "path_type": "hardlink", + "sha256": "ff915dc68d597c62ffa30c87711013948c81c97693acb573333ebc375a9b23d9", + "size_in_bytes": 18928 + }, + { + "_path": "share/doc/gettext/gettext_13.html", + "path_type": "hardlink", + "sha256": "a129cdb1552d0dff211b5d93324a2709d379025d50529a0a3388ac591582ea28", + "size_in_bytes": 72305 + }, + { + "_path": "share/doc/gettext/gettext_14.html", + "path_type": "hardlink", + "sha256": "e2db9f3247c20227489d03ba85b0f2176afc0489f22da32d24be1845b5225c36", + "size_in_bytes": 6204 + }, + { + "_path": "share/doc/gettext/gettext_15.html", + "path_type": "hardlink", + "sha256": "fde56bd58116ce7e4fab9eb541ed4f52a22f91560e1fec6160e240a1b4429d1b", + "size_in_bytes": 162045 + }, + { + "_path": "share/doc/gettext/gettext_16.html", + "path_type": "hardlink", + "sha256": "333912ff4b799b7462c61f565ca4f8911f8aae54bf4e0dfa190f0d7807fa9c72", + "size_in_bytes": 23895 + }, + { + "_path": "share/doc/gettext/gettext_17.html", + "path_type": "hardlink", + "sha256": "38ed5bd897b4af84d34d780b6257c26b9514136ce1d950bd503faa9f99c8fbd4", + "size_in_bytes": 89550 + }, + { + "_path": "share/doc/gettext/gettext_18.html", + "path_type": "hardlink", + "sha256": "5ebf16e0d04cfbdba6a452554faa8a25d34f5ef9e75e3cfa92a652c5f2459cb9", + "size_in_bytes": 21590 + }, + { + "_path": "share/doc/gettext/gettext_19.html", + "path_type": "hardlink", + "sha256": "7935856006582954f3a08e9b8dc533b927d59d6925dd5db00d902fba8f949c6b", + "size_in_bytes": 21631 + }, + { + "_path": "share/doc/gettext/gettext_2.html", + "path_type": "hardlink", + "sha256": "222b05b2b9955d208aef9121ad0715b33aca86fe4628c2391a91343a3920e20d", + "size_in_bytes": 21442 + }, + { + "_path": "share/doc/gettext/gettext_20.html", + "path_type": "hardlink", + "sha256": "21d6721da4867dd779b831e2b5d0225bce2499a80463fd5e00d5738a2dee3b1a", + "size_in_bytes": 76170 + }, + { + "_path": "share/doc/gettext/gettext_21.html", + "path_type": "hardlink", + "sha256": "2d8106a00e989fadcb9c5e7b858d4d7f2a20f96ca6202c63f6512115ac12d49b", + "size_in_bytes": 11205 + }, + { + "_path": "share/doc/gettext/gettext_22.html", + "path_type": "hardlink", + "sha256": "57d6487d197fc516f55db78d62ad71b86f9fa6aa4eb24b0c87ee6ac37e3a3205", + "size_in_bytes": 156435 + }, + { + "_path": "share/doc/gettext/gettext_23.html", + "path_type": "hardlink", + "sha256": "1a9111dac346b91699c86f56cd1179e179ebf13cbd2b4931c8d61c474a16aabe", + "size_in_bytes": 16667 + }, + { + "_path": "share/doc/gettext/gettext_24.html", + "path_type": "hardlink", + "sha256": "7bee06539f420c38fbcdcafc1950be13c2242916c20958b18e2531f0ce82b1db", + "size_in_bytes": 43194 + }, + { + "_path": "share/doc/gettext/gettext_25.html", + "path_type": "hardlink", + "sha256": "9aefc69bb5ac83b6910340ea8a13fcb325ae7fd95102dae897a95d1a6c8e6668", + "size_in_bytes": 18564 + }, + { + "_path": "share/doc/gettext/gettext_26.html", + "path_type": "hardlink", + "sha256": "b39ae359cf9c364aa01d45d292f74f753e9640dc4b440555b2f41935133aeaec", + "size_in_bytes": 5805 + }, + { + "_path": "share/doc/gettext/gettext_27.html", + "path_type": "hardlink", + "sha256": "89021404fac316d0d16688a3ef20bead5b25da6fed8399365cdf2547e5ab69fd", + "size_in_bytes": 29545 + }, + { + "_path": "share/doc/gettext/gettext_28.html", + "path_type": "hardlink", + "sha256": "3b502b48920c1ae061be11e6ce3f816c5952ab35743dec21f314bb5b8cda1a21", + "size_in_bytes": 37261 + }, + { + "_path": "share/doc/gettext/gettext_29.html", + "path_type": "hardlink", + "sha256": "0b76c82c2089878a604a4b78b86df75a18442f577501615c1096d31366a8fdb5", + "size_in_bytes": 48196 + }, + { + "_path": "share/doc/gettext/gettext_3.html", + "path_type": "hardlink", + "sha256": "ccc38615fe58898cdb6d66c66ac615346996bb660f4bcd5672fbe132bba674cf", + "size_in_bytes": 24942 + }, + { + "_path": "share/doc/gettext/gettext_30.html", + "path_type": "hardlink", + "sha256": "01a2d639919497bbddf77003b352309bea14ca10de0052dd6dd7e85726690a8b", + "size_in_bytes": 26209 + }, + { + "_path": "share/doc/gettext/gettext_4.html", + "path_type": "hardlink", + "sha256": "0740d38146476ff60e3ca6b0f9f7321abcc03f83e7e7476bac3856f68a46bbe8", + "size_in_bytes": 66967 + }, + { + "_path": "share/doc/gettext/gettext_5.html", + "path_type": "hardlink", + "sha256": "046bdf785c5ddf6c916caff92ba9971539743f12384e63a5954aac8b37d10042", + "size_in_bytes": 42101 + }, + { + "_path": "share/doc/gettext/gettext_6.html", + "path_type": "hardlink", + "sha256": "1d26fb57debea1933cdaee220e4401a1899ea2b1a05c38b9891c2d456792f8bc", + "size_in_bytes": 23135 + }, + { + "_path": "share/doc/gettext/gettext_7.html", + "path_type": "hardlink", + "sha256": "b4a30ec52a5d03fe0371f7ff9aed391071433a07f364281d5952c5fc9fea99be", + "size_in_bytes": 15934 + }, + { + "_path": "share/doc/gettext/gettext_8.html", + "path_type": "hardlink", + "sha256": "8a43ca64c5a1c84e8a18ec129c46ba9a25d0408c39aa9cf63ad30ca536c240bd", + "size_in_bytes": 77924 + }, + { + "_path": "share/doc/gettext/gettext_9.html", + "path_type": "hardlink", + "sha256": "83f7c5bbb4926abe8c39df868688549dc591b0e7b6a6f9d20d531a1da3828664", + "size_in_bytes": 139139 + }, + { + "_path": "share/doc/gettext/gettext_abt.html", + "path_type": "hardlink", + "sha256": "268f783d58bb67a6a2bece93a4e05f4583258aa6aae343a52b25ae741b9fc73c", + "size_in_bytes": 5313 + }, + { + "_path": "share/doc/gettext/gettext_fot.html", + "path_type": "hardlink", + "sha256": "818d60ccfd977dd437a91a7171af0fafa5b87302cd91da34735044abc1789e84", + "size_in_bytes": 5018 + }, + { + "_path": "share/doc/gettext/gettext_toc.html", + "path_type": "hardlink", + "sha256": "42a25b7b335a93b4216f54e16a74e240738e5d61912e00fca1df2835db41fa88", + "size_in_bytes": 43804 + }, + { + "_path": "share/doc/gettext/gettextize.1.html", + "path_type": "hardlink", + "sha256": "f483ba459d92a7a80befe975b44f4832f1f94ee39686f5b6cd0eabd94eaf61df", + "size_in_bytes": 3819 + }, + { + "_path": "share/doc/gettext/msgattrib.1.html", + "path_type": "hardlink", + "sha256": "e084147dd722cf56d5961d2e166c1cecf8dbbf0e342101312777287afbd7f1c7", + "size_in_bytes": 8778 + }, + { + "_path": "share/doc/gettext/msgcat.1.html", + "path_type": "hardlink", + "sha256": "25b0ae590f2d5e43f8fa2b50c114099b15815535177b9b52820d040e2ad86027", + "size_in_bytes": 8080 + }, + { + "_path": "share/doc/gettext/msgcmp.1.html", + "path_type": "hardlink", + "sha256": "ddb3299d7d60e7255b992f9af5e7111d8ec78175c0c6bb092092cb995ba31fc8", + "size_in_bytes": 4878 + }, + { + "_path": "share/doc/gettext/msgcomm.1.html", + "path_type": "hardlink", + "sha256": "751ecc8d6791808b3a96ee861d7ad6a603f20c2ddf3f11cf74c3a3893fca28e0", + "size_in_bytes": 7712 + }, + { + "_path": "share/doc/gettext/msgconv.1.html", + "path_type": "hardlink", + "sha256": "be2727f334d7444ee4c388c7d6dfb626df93f62e7e914533a2a63d551bf33af7", + "size_in_bytes": 6615 + }, + { + "_path": "share/doc/gettext/msgen.1.html", + "path_type": "hardlink", + "sha256": "2db78af0bb87d174b1d92bfdee21ae7679dcde02799dadea83a0c6bea662270b", + "size_in_bytes": 6608 + }, + { + "_path": "share/doc/gettext/msgexec.1.html", + "path_type": "hardlink", + "sha256": "97b9b3237259e3a96553213d2a56e28c61c025973100898e986373e88c275038", + "size_in_bytes": 4413 + }, + { + "_path": "share/doc/gettext/msgfilter.1.html", + "path_type": "hardlink", + "sha256": "e2632b6de2204dbb9a00f169708b27fbffbb74007deb49566cf1884cf817d501", + "size_in_bytes": 7451 + }, + { + "_path": "share/doc/gettext/msgfmt.1.html", + "path_type": "hardlink", + "sha256": "53e837e9d52ce1ef59e4140a33f2776f7e5f8da6fe83c36bb5b6f2e3b8d526eb", + "size_in_bytes": 12144 + }, + { + "_path": "share/doc/gettext/msggrep.1.html", + "path_type": "hardlink", + "sha256": "228967bb7d65c99128319e9240ec419067feb0ab5d15abf18607fa4a9fd74317", + "size_in_bytes": 9614 + }, + { + "_path": "share/doc/gettext/msginit.1.html", + "path_type": "hardlink", + "sha256": "93185589f8934ecfeb6032ff8c085173556a981ba6e881f4e37d5e6245778e4f", + "size_in_bytes": 5456 + }, + { + "_path": "share/doc/gettext/msgmerge.1.html", + "path_type": "hardlink", + "sha256": "2312e75e4f9064b5947b1e0c688c30de6d6725c426f5f58a0d4afbde5f861744", + "size_in_bytes": 9695 + }, + { + "_path": "share/doc/gettext/msgunfmt.1.html", + "path_type": "hardlink", + "sha256": "5bf09192d6b7f547e5ff12787ccbc9045157b1e73deb92edc59bb5713d8d293b", + "size_in_bytes": 8022 + }, + { + "_path": "share/doc/gettext/msguniq.1.html", + "path_type": "hardlink", + "sha256": "b9865c4e53609070ce017ba4571116d51413cce05a870d4a0c785d3cb3077d4f", + "size_in_bytes": 7505 + }, + { + "_path": "share/doc/gettext/ngettext.1.html", + "file_mode": "text", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "b247fb9c76b86fb48e3adb002da5cb5274a801b967f06cacf99ee86afd89313a", + "size_in_bytes": 5275 + }, + { + "_path": "share/doc/gettext/ngettext.3.html", + "path_type": "hardlink", + "sha256": "0cfceedfc523557bbcbb84006b94118842fa8a3449bdd466d79986d95269e767", + "size_in_bytes": 4027 + }, + { + "_path": "share/doc/gettext/recode-sr-latin.1.html", + "path_type": "hardlink", + "sha256": "955986c5c41723a9d49f1c6462d7d8f75b6af62a7a301be149d337497a411921", + "size_in_bytes": 3024 + }, + { + "_path": "share/doc/gettext/textdomain.3.html", + "path_type": "hardlink", + "sha256": "fe638c6f16b9a63a64b93ed3025a6ec52a1d37253222d241677c8f3c467075d5", + "size_in_bytes": 3725 + }, + { + "_path": "share/doc/gettext/tutorial.html", + "path_type": "hardlink", + "sha256": "5456b6e0660de37b9de007bf225a46a76b11f3b798788861a27187fe27ee919a", + "size_in_bytes": 33361 + }, + { + "_path": "share/doc/gettext/xgettext.1.html", + "path_type": "hardlink", + "sha256": "028cce77e1b9a5c3426aded11706844707dd396eac2265190e7e29f57c6db558", + "size_in_bytes": 13504 + }, + { + "_path": "share/doc/libasprintf/autosprintf_all.html", + "path_type": "hardlink", + "sha256": "fce93c482946b827cc67de269eb423450f828f259fb9743c792c1470ec7e383f", + "size_in_bytes": 78366 + }, + { + "_path": "share/gettext-0.25.1/its/docbook.loc", + "path_type": "hardlink", + "sha256": "6e2dc809d5b4eec94f5102226bf1a11110d9946f1b8a116daaf602bac1b026d2", + "size_in_bytes": 2140 + }, + { + "_path": "share/gettext-0.25.1/its/docbook4.its", + "path_type": "hardlink", + "sha256": "8a1894caa324c9279529b18f5063b024ee42da080eb1b74745f39fce6b5fbeda", + "size_in_bytes": 13086 + }, + { + "_path": "share/gettext-0.25.1/its/docbook5.its", + "path_type": "hardlink", + "sha256": "153a63821d0de57e024ff7057685e7e34c886442ce837515d3be195b296fb896", + "size_in_bytes": 10466 + }, + { + "_path": "share/gettext-0.25.1/its/glade.loc", + "path_type": "hardlink", + "sha256": "daade8504367cd561b1e18933fef886705ead8dd833a8fefe4dd5e9937e6ed92", + "size_in_bytes": 1345 + }, + { + "_path": "share/gettext-0.25.1/its/glade1.its", + "path_type": "hardlink", + "sha256": "9a28208194abc393b17293a5853bed1bae0e2da4baf93278e72d7632ffa20dae", + "size_in_bytes": 1690 + }, + { + "_path": "share/gettext-0.25.1/its/glade2.its", + "path_type": "hardlink", + "sha256": "232891342015e19b3aa40e122d34703ee91bd0de1b8e6bd31eb0db2f11fc2168", + "size_in_bytes": 2281 + }, + { + "_path": "share/gettext-0.25.1/its/gsettings.its", + "path_type": "hardlink", + "sha256": "dd3027d732b108798fa12a72b0c41d6a665362b5c8419bce6684a7f70c72a234", + "size_in_bytes": 1578 + }, + { + "_path": "share/gettext-0.25.1/its/gsettings.loc", + "path_type": "hardlink", + "sha256": "6351981442f67956f82b74fa4fc0447b8bd859110a149110464fbebb740fd16c", + "size_in_bytes": 952 + }, + { + "_path": "share/gettext-0.25.1/its/gtkbuilder.its", + "path_type": "hardlink", + "sha256": "b5bea3e6fe727951b1802f36bdf76936e4d3a208a0d3f3a07e5588c15a7bb7bb", + "size_in_bytes": 2244 + }, + { + "_path": "share/gettext-0.25.1/its/metainfo.its", + "path_type": "hardlink", + "sha256": "92a200fc62abc4157ab6728f706370b956c8d39718952b291e04985717361a25", + "size_in_bytes": 2681 + }, + { + "_path": "share/gettext-0.25.1/its/metainfo.loc", + "path_type": "hardlink", + "sha256": "68fb6d68338c8626bc88b73f38e6bb8e80b4e39840ec3b5749b69af0a2f605f1", + "size_in_bytes": 1094 + }, + { + "_path": "share/gettext/ABOUT-NLS", + "path_type": "hardlink", + "sha256": "fbe8681a07eab3934d302edb4db8fbcea014b460232e3638e7f4cdb7da53e5aa", + "size_in_bytes": 67 + }, + { + "_path": "share/gettext/archive.dir.tar.xz", + "path_type": "hardlink", + "sha256": "73076986c0f6195c64698f6e595dc5d7762d344d5b6d4821462d94f06c2bc262", + "size_in_bytes": 606708 + }, + { + "_path": "share/gettext/config.rpath", + "path_type": "hardlink", + "sha256": "772c44d89098cbcc95b12cee420fd2f1833ac2da0338df99c5e590d1c1672234", + "size_in_bytes": 20196 + }, + { + "_path": "share/gettext/disclaim-translations.txt", + "path_type": "hardlink", + "sha256": "4aa0555c121f0e0cd61664083d68b4f8b8642d1d9d8d541b8633a0e066d58944", + "size_in_bytes": 2467 + }, + { + "_path": "share/gettext/gettext.h", + "path_type": "hardlink", + "sha256": "04ea98fa297a0acc412c7ed701e72b700d2d0458aa25b7e108262eff6b4da4d5", + "size_in_bytes": 10993 + }, + { + "_path": "share/gettext/javaversion.class", + "path_type": "hardlink", + "sha256": "2bee26b0b761a52a418a6488d94be8af824a30a3f87f50cb8d35f4b7a54a13a6", + "size_in_bytes": 510 + }, + { + "_path": "share/gettext/m4/build-to-host.m4", + "path_type": "hardlink", + "sha256": "b2261ee50f116d42c796b79593480a4368327d912bc63ef6cba145229358abff", + "size_in_bytes": 9242 + }, + { + "_path": "share/gettext/m4/gettext.m4", + "path_type": "hardlink", + "sha256": "add9e9fdb92b7cb31f9c2f8759c38f5534922c3a9fc5f0b4f9677c8d0677850c", + "size_in_bytes": 15027 + }, + { + "_path": "share/gettext/m4/host-cpu-c-abi.m4", + "path_type": "hardlink", + "sha256": "8e02be8975a966b8b8686edd57695b3fbe67d157e4c8bc8fc1c27cbde8105ea2", + "size_in_bytes": 17277 + }, + { + "_path": "share/gettext/m4/iconv.m4", + "path_type": "hardlink", + "sha256": "17135e2063589fb6a8112c37f295af3acd84c9ba31074cc36eb7cc9631ac6922", + "size_in_bytes": 11052 + }, + { + "_path": "share/gettext/m4/intlmacosx.m4", + "path_type": "hardlink", + "sha256": "648f2e2b1deef6cbf82b843e0283112a8f7c5f42fa7e4f8a86df8c156817bfe4", + "size_in_bytes": 3560 + }, + { + "_path": "share/gettext/m4/lib-ld.m4", + "path_type": "hardlink", + "sha256": "cb511decb9d8d2536ec5ebe8c8baa65d670460e6382c02f88c91731bce763a99", + "size_in_bytes": 5440 + }, + { + "_path": "share/gettext/m4/lib-link.m4", + "path_type": "hardlink", + "sha256": "3650b2e91890f6cc73ee7cd3467ec4a5626d16cf58b3c7e513cb08c9e74bbfc3", + "size_in_bytes": 35798 + }, + { + "_path": "share/gettext/m4/lib-prefix.m4", + "path_type": "hardlink", + "sha256": "bb39ef3b0e50a3b86d2643b977269786bc2d45656b6b5efad03faf77c203aadc", + "size_in_bytes": 12582 + }, + { + "_path": "share/gettext/m4/nls.m4", + "path_type": "hardlink", + "sha256": "6ee6943979f6f3cee4d66c330e8b577ad14a578605e3c617cb6266423ba8de2d", + "size_in_bytes": 1245 + }, + { + "_path": "share/gettext/m4/po.m4", + "path_type": "hardlink", + "sha256": "8243c65fe67e67d36e0cc4063f339a15d9a82c431c772c6d1401fc4e19c6f030", + "size_in_bytes": 6389 + }, + { + "_path": "share/gettext/m4/progtest.m4", + "path_type": "hardlink", + "sha256": "7c069f3061539bdd9078433e4d31f7860f7e3f02e9b3224468c6de8877c65fcb", + "size_in_bytes": 3128 + }, + { + "_path": "share/gettext/msgunfmt.tcl", + "path_type": "hardlink", + "sha256": "cb6c82ca8322b5456e354b70e78e22d500286fabf448cd60e7bd76055ef19453", + "size_in_bytes": 2490 + }, + { + "_path": "share/gettext/po/Makefile.in.in", + "path_type": "hardlink", + "sha256": "3410bb15a551157d0d132da267fdcfbab05ddc9fd69dacf1438defcf5fc48f47", + "size_in_bytes": 23422 + }, + { + "_path": "share/gettext/po/Makevars.template", + "path_type": "hardlink", + "sha256": "5cc9bff1a3b6e652e064d4f095e4d26c07e75d75e1a02ed212b996b0c69fae56", + "size_in_bytes": 3563 + }, + { + "_path": "share/gettext/po/Rules-quot", + "path_type": "hardlink", + "sha256": "ff0938a507a30899173bb116bcdf44f961ee810fb0d28d48b1be0a89f2f37351", + "size_in_bytes": 2483 + }, + { + "_path": "share/gettext/po/boldquot.sed", + "path_type": "hardlink", + "sha256": "c109dbd6b520bb784590fe4b3bbec28d4877b0e8618e180d0f53d695bee43fc7", + "size_in_bytes": 717 + }, + { + "_path": "share/gettext/po/en@boldquot.header", + "path_type": "hardlink", + "sha256": "80b9c9513f18b49d75e23f0e54e7a331a2ebda50eb0b28f82d48b012340ff5f7", + "size_in_bytes": 1771 + }, + { + "_path": "share/gettext/po/en@quot.header", + "path_type": "hardlink", + "sha256": "b277bf95b5e1c56f5d860ed3d479a20c37a41d3f965d0954531a8e907bb2f960", + "size_in_bytes": 1633 + }, + { + "_path": "share/gettext/po/insert-header.sed", + "path_type": "hardlink", + "sha256": "120513c5348e88d0f9f0381da50dfb5f2dc6557581f8ac76125f2f4d84ab0f45", + "size_in_bytes": 1019 + }, + { + "_path": "share/gettext/po/quot.sed", + "path_type": "hardlink", + "sha256": "a2a83b6f6c4d6a0c28828c81ff621f1d7cb703ed07b56d83bdafe86dcb4d316f", + "size_in_bytes": 608 + }, + { + "_path": "share/gettext/po/remove-potcdate.sed", + "path_type": "hardlink", + "sha256": "d582513385c800f75224f4041fbff207053d4229be6038c6810af382420ac362", + "size_in_bytes": 720 + }, + { + "_path": "share/gettext/schema/its-extensions.xsd", + "path_type": "hardlink", + "sha256": "38c4a1f45d0075e12d4e67b3073fc25f154cdb6491739ec5b2ade58abeb8ed5a", + "size_in_bytes": 3162 + }, + { + "_path": "share/gettext/schema/its.xsd10", + "path_type": "hardlink", + "sha256": "70c56338dc715130d9b982ca8af3b0928ed86acae70d1cddb469c0e3928673da", + "size_in_bytes": 5790 + }, + { + "_path": "share/gettext/schema/its.xsd11", + "path_type": "hardlink", + "sha256": "5d94dea6c1fe9092109e963e4617565a02f6fa3aa6f00f2f4a7079d37e1b3e90", + "size_in_bytes": 4620 + }, + { + "_path": "share/gettext/schema/locating-rules.xsd10", + "path_type": "hardlink", + "sha256": "98155afb8344bc1fe03f61c6d9f98f181a1a6a824392de9adc45831908cb62ee", + "size_in_bytes": 4093 + }, + { + "_path": "share/gettext/schema/locating-rules.xsd11", + "path_type": "hardlink", + "sha256": "57e757a156ca9991ee1e29227b6219a0d3d51ec18ea16c87a0ef8080637d259d", + "size_in_bytes": 4089 + }, + { + "_path": "share/gettext/styles/po-default.css", + "path_type": "hardlink", + "sha256": "4c3f0d8c49288353f95fec5cd9675fbb23e7eec13dda50a4228cd21b1ef4dd08", + "size_in_bytes": 1311 + }, + { + "_path": "share/gettext/styles/po-emacs-x.css", + "path_type": "hardlink", + "sha256": "bbfd4c7d510ca5480ef9611e11d5e5cbdfba8f7bfca0cac072167ddf7e74c0d3", + "size_in_bytes": 1161 + }, + { + "_path": "share/gettext/styles/po-emacs-xterm.css", + "path_type": "hardlink", + "sha256": "6d4aa3c7119fad86a0ae24266352edb2a876be4fd7c87fce6be526339bb91d67", + "size_in_bytes": 1125 + }, + { + "_path": "share/gettext/styles/po-emacs-xterm16.css", + "path_type": "hardlink", + "sha256": "96c1a853817ac29eeee1426bd01277f65130138901acd668592f82d5451d62e3", + "size_in_bytes": 1161 + }, + { + "_path": "share/gettext/styles/po-emacs-xterm256.css", + "path_type": "hardlink", + "sha256": "ec2728d0892eaae474a01e1ae7dfc71d6d665ee66037d3ab4f906a39843a3f92", + "size_in_bytes": 1163 + }, + { + "_path": "share/gettext/styles/po-vim.css", + "path_type": "hardlink", + "sha256": "a9d38bc9f7d2bb61bc5b2df71214bd0a62774a33ab841eeab4e98f9550b08c42", + "size_in_bytes": 1166 + }, + { + "_path": "share/info/autosprintf.info", + "path_type": "hardlink", + "sha256": "5db03a51d2f233c9368eb826df0e68b96b82f2692de3de38177d24279973a1eb", + "size_in_bytes": 79126 + }, + { + "_path": "share/info/gettext.info", + "path_type": "hardlink", + "sha256": "5efd635bf59dc66ae0bc7b594164ffface56eac884b7f3e40bf81e5271b49f35", + "size_in_bytes": 948242 + }, + { + "_path": "share/info/libtextstyle.info", + "path_type": "hardlink", + "sha256": "eac1606e753239334242d90043ad97d1230c27da390af1e3fd61137b809fd0c7", + "size_in_bytes": 130569 + }, + { + "_path": "share/locale/ast/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "44f58fb951f72ba7df526629871f519d8dd584eeb4c44438f254ec44c0282e1c", + "size_in_bytes": 5291 + }, + { + "_path": "share/locale/be/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "eea67ec7408975cd44811a779b372ca50c85251db18d9373bf05f35d62891af7", + "size_in_bytes": 2659 + }, + { + "_path": "share/locale/be/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "01b56e7458bcd60c6c2dbbea96aaf9e7c50a3270814962ffdf19b3093bcea217", + "size_in_bytes": 22555 + }, + { + "_path": "share/locale/bg/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "f95369d9952a84a5b17b9b09d697a5fe776b8cab28dcf2b027e2e08fc1fa0494", + "size_in_bytes": 10312 + }, + { + "_path": "share/locale/bg/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "4d9cacb276b87d041d6a56f2af9a4230b4ba72e9f3039ca64b53b2bc47dcf098", + "size_in_bytes": 159236 + }, + { + "_path": "share/locale/ca/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "f43ac2c39ccc5ca0f702a63129561bbad9719569eb5b9cdea4ae574e655dd38e", + "size_in_bytes": 8161 + }, + { + "_path": "share/locale/ca/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "c1a266277b9990818c67d6c2f90a47a0f0c685240891eff0d8ed97fdb380fae1", + "size_in_bytes": 125236 + }, + { + "_path": "share/locale/cs/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "1b19f82e6d767c376aade4d10154e726e7fc8916f2686e3f53c6e95c079c3cb6", + "size_in_bytes": 8308 + }, + { + "_path": "share/locale/cs/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "ea97a6df76b4ac90b60e2363052b9c8190a4ce6d3f050d90256002d9716258cf", + "size_in_bytes": 6123 + }, + { + "_path": "share/locale/da/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "3fd6b3a3280eba052152d1c1ac4dffdd9b7188d98d776f282804ae574b5c96c2", + "size_in_bytes": 5178 + }, + { + "_path": "share/locale/da/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "aa05fa5ba6af37ef1a0993a35274b3c7112187855edf36a2fba440b748017e53", + "size_in_bytes": 81579 + }, + { + "_path": "share/locale/de/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "40a37bee8d968e7d3d948ca6ed739b4cc4c677867da6551b5bcf839501a394ef", + "size_in_bytes": 8301 + }, + { + "_path": "share/locale/de/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "8cc3b57719ece713cd3b38c3df98ca7f96cd6e926cf76517964b5eeb7ca87e75", + "size_in_bytes": 138879 + }, + { + "_path": "share/locale/el/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "762b2ce3f89fd35b24d472874bc7e90810be51d03954b86da8dbf255ec318c8c", + "size_in_bytes": 892 + }, + { + "_path": "share/locale/el/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "f79bb62c7b19e1e5fc038676f86fc54913e564e7a85766ea7bac42978d94e7d3", + "size_in_bytes": 4322 + }, + { + "_path": "share/locale/en@boldquot/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "3cd490d9cce212eaa3593b8fdd1cad2a8c75a3605abb85371a7cad6029b92e62", + "size_in_bytes": 7705 + }, + { + "_path": "share/locale/en@boldquot/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "0d395ac50deb98755d17f3138887582ce0e1bf521ee02b9b1cdc338db79c802f", + "size_in_bytes": 131259 + }, + { + "_path": "share/locale/en@quot/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "d65f5c353344c13a85ccff6d7baddef57a738786c5079e561134558342099b09", + "size_in_bytes": 7677 + }, + { + "_path": "share/locale/en@quot/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "2e313d382d8c17dc0e9a66ce42d04647ed2cb99ddbcf6ad6909ef63dd23992b1", + "size_in_bytes": 129215 + }, + { + "_path": "share/locale/eo/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "94b1bfbc621f616ca0d3f1fa461e474b744aabedca2cde35a94c90efc1f8a759", + "size_in_bytes": 7818 + }, + { + "_path": "share/locale/es/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "182108270c7e8368ca475b746811a3c4ec32370d1bdd5d2153c3a90fb399552b", + "size_in_bytes": 8270 + }, + { + "_path": "share/locale/es/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "4453a019b246830630eeabafd5d8e7b337cb6b4e1cd95a456ad3938cfd1e6ea2", + "size_in_bytes": 132452 + }, + { + "_path": "share/locale/et/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "0d2d333f5669ba2d5a0fb34f4395a5c58218349fa7289453bf7ab79123485e00", + "size_in_bytes": 788 + }, + { + "_path": "share/locale/et/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "85b1690e1ad2173da9b285fc32036c685086567c93cfef0ef1b9f566567030ce", + "size_in_bytes": 5765 + }, + { + "_path": "share/locale/eu/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "4c053fa7894fb527030bf2f128562d09b64e64d3c5030562ca3ceb2e2a9b2d42", + "size_in_bytes": 46960 + }, + { + "_path": "share/locale/fi/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "9257daa48ad237f549d66e9bc105d91adb5a70bd90f0d5470548bc7e70f79703", + "size_in_bytes": 7981 + }, + { + "_path": "share/locale/fi/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "42b03123ca4d348f920ae4964860ea7d92f862d8c9012adec25c44560ccb1c24", + "size_in_bytes": 112581 + }, + { + "_path": "share/locale/fr/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "59c3c7b6d5a96852d42852d262895f0d6f6735a2d92060f51da95792de30146a", + "size_in_bytes": 7998 + }, + { + "_path": "share/locale/fr/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "ab5f4e999c1c06061aa5191e048ea778c2230ca3e40eaae336fd6fb0696949cd", + "size_in_bytes": 126157 + }, + { + "_path": "share/locale/ga/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "dca277fa20db3cbfaee7a01111801ff1f6db25a68c245892e971b72039a67482", + "size_in_bytes": 5290 + }, + { + "_path": "share/locale/gl/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "03d5311ea5aacccb1b373a6fb21a664c811fc8b163aaa6ad8b037b31715e7308", + "size_in_bytes": 5235 + }, + { + "_path": "share/locale/gl/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "bcea4b7d08e57df6b6c4a3da52911ba2dd140c8ba735dc36ed90380e4fc102b5", + "size_in_bytes": 18952 + }, + { + "_path": "share/locale/hr/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "e6ad41229a8ba0a55dc8d56e208b46e69b5dd93431d2818638c193b69c627207", + "size_in_bytes": 7885 + }, + { + "_path": "share/locale/hr/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "130202f8c47f4cb181a3f070326a8665955fd2027e13b1b04385f66ccb763055", + "size_in_bytes": 129882 + }, + { + "_path": "share/locale/hu/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "72ffe00c5838196730197b059e043d97e22e1182ee22a7fa4730e0f21a4a9984", + "size_in_bytes": 8454 + }, + { + "_path": "share/locale/id/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "c26532f38cccdddce4abe89ef2982c8b79a78e03ada22731c4970d5a36ff52c4", + "size_in_bytes": 4073 + }, + { + "_path": "share/locale/id/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "8528f3519ea5952a068c273ca0e6554bf8141bafb7f6c2d861358d2f3969387a", + "size_in_bytes": 83401 + }, + { + "_path": "share/locale/it/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "6e5e7f5c11ca41fffbae192e195ec3367fdb4ba6bfa1b802bd31b8bdc8aa7848", + "size_in_bytes": 8067 + }, + { + "_path": "share/locale/it/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "ea15b53838b009ce061d93c93019c9d06a33d511aee9f126117b7ab9ef2baca8", + "size_in_bytes": 133272 + }, + { + "_path": "share/locale/ja/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "4a1a4349fdf762ac64613d3840a11ca1ae875c56cc9f4989db3528287ac73246", + "size_in_bytes": 8619 + }, + { + "_path": "share/locale/ja/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "427303e93c8d60f239cd6ae369a66dbc8955fe7dd6ef57bfccb8650191b0a8d7", + "size_in_bytes": 141536 + }, + { + "_path": "share/locale/ka/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "8646d2763363daa5a33549aa92c894a73852edc3588dc0df93928b875bfaa735", + "size_in_bytes": 5742 + }, + { + "_path": "share/locale/ka/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "01778459c94f85b7dfb3540d41c19e00904f870c4da687ea3642d784fcd4b57d", + "size_in_bytes": 8159 + }, + { + "_path": "share/locale/ko/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "b07137af32c48896c192e47d997ff7d93f57ef85d2ed99d7484d6fd6debba9c2", + "size_in_bytes": 8104 + }, + { + "_path": "share/locale/ko/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "8b7979db8e4bea60858ec8ea201166b9d3f5c33b4a308eb382bcc55a4924199d", + "size_in_bytes": 139858 + }, + { + "_path": "share/locale/nb/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "5aa9db3ae9e6cbffcd7bf5c7a5d2724b3ebd5ff86d4105f79dee17a97c3835b2", + "size_in_bytes": 7742 + }, + { + "_path": "share/locale/nb/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "3aac68b2ba74a6ecb166efc53e3d00ad6ac2f259e1bf605ed428cf5b0761592c", + "size_in_bytes": 16283 + }, + { + "_path": "share/locale/nl/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "7f91eefe44045664ed331dd3e207d0e652840922c8d1e05d906ba1ebf1b916cb", + "size_in_bytes": 7994 + }, + { + "_path": "share/locale/nl/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "9d63619af5470b10bf4d6515494b5f0b437d0b2e2049c0f6862f9ac853eaa0d4", + "size_in_bytes": 46469 + }, + { + "_path": "share/locale/nn/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "2470a13eaa21c5d6f0dc6f609b992a79a0f04c15e6b96f25d0d00e30189adde5", + "size_in_bytes": 7744 + }, + { + "_path": "share/locale/nn/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "ba406937f4df6d680052166cbe2e432be780b78f2422615c4a6170e5c896357a", + "size_in_bytes": 10823 + }, + { + "_path": "share/locale/pa/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "39e335faed9bbdb1ab79d25de4fe2e310ac8f657ab343ce56031f2cde9a229ec", + "size_in_bytes": 24978 + }, + { + "_path": "share/locale/pl/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "476fccb2597365b38070931c9800e13fc34dc33a720dd87722c66115d0e69553", + "size_in_bytes": 8026 + }, + { + "_path": "share/locale/pl/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "681c509027b549349e0591ee5080ae69e6fd691131a6ac87003bdde0237098cd", + "size_in_bytes": 134369 + }, + { + "_path": "share/locale/pt/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "875dcf67b165816483a0400e7c87f29dc4ad00e77a6a456abb71b78a90607962", + "size_in_bytes": 8027 + }, + { + "_path": "share/locale/pt/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "4ea85c02434af8136e02a28292057ad807c2a2b6a1d2ad59eeabbadf89f548b9", + "size_in_bytes": 131722 + }, + { + "_path": "share/locale/pt_BR/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "fb338a1d1fa81b9e3f78eb3f1c750fa6888bffd3d9fe42b66eddf40373b63636", + "size_in_bytes": 8110 + }, + { + "_path": "share/locale/pt_BR/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "ff911789b717174f914aca234a8e109e72bd1551e4e89a597ee73652925c80d0", + "size_in_bytes": 135811 + }, + { + "_path": "share/locale/ro/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "9474eb80348ee58bf926639a702edce57b84e3b410236a58eb2cd92df8ccd413", + "size_in_bytes": 8400 + }, + { + "_path": "share/locale/ro/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "8a8bd298a83926558be91960e444f0061bd168079fded880ed681f6747bb9841", + "size_in_bytes": 139467 + }, + { + "_path": "share/locale/ru/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "680f1a93307397bc46343fa7c1be1500a6139e335c8f54b1861ad6c6e9077b79", + "size_in_bytes": 10345 + }, + { + "_path": "share/locale/ru/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "3c5cdce65771704a6063c9d7ba6a9600ed5e62c02ac5080bff031a75a18e4afb", + "size_in_bytes": 169930 + }, + { + "_path": "share/locale/sk/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "d3bdc67c75dc902e4c69837af56e0b12bb90774890c6d0e61486ce00933ade46", + "size_in_bytes": 8275 + }, + { + "_path": "share/locale/sk/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "3409d0f4fed0244dfcfe2c022b1e1701006df8dc8f2f738ef5a3f9be7dd8467b", + "size_in_bytes": 133123 + }, + { + "_path": "share/locale/sl/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "f9961b29db987fc424f6a10333f1913df61de87a1c773cbcfe5059e0abcbe05b", + "size_in_bytes": 5140 + }, + { + "_path": "share/locale/sl/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "b640ee3b2c6b2dcf36d56d2c387d7f304aa30bf4128961a5585fe130b26839c4", + "size_in_bytes": 102527 + }, + { + "_path": "share/locale/sr/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "f983d09c8f9a8d181fa8e87e1d9ddff72800ac3b9e0bce55dea0327b31f99c24", + "size_in_bytes": 10058 + }, + { + "_path": "share/locale/sr/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "00d1d1a90f25d893d79ad0b3579c2e43ce01f308c89c533c419bd57d1208284c", + "size_in_bytes": 155133 + }, + { + "_path": "share/locale/sv/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "e86fad6ccc5883053c11bf520b557d4a7dc4b896c8bcf47c23d46833d263b728", + "size_in_bytes": 7812 + }, + { + "_path": "share/locale/sv/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "afddf06839d2115ab2c7d3746aa788b1fdc5c4a923e41f59743a6fb4009e1822", + "size_in_bytes": 128210 + }, + { + "_path": "share/locale/tr/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "b3f3020566df77ce1cf35867d3021ec9ca0fe0a874ce25bbddf788ea8dbf40b1", + "size_in_bytes": 7869 + }, + { + "_path": "share/locale/tr/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "94f5f240502c334900720a67817da88885da5af5d9bfd0c969ceaeba1aaca3db", + "size_in_bytes": 77364 + }, + { + "_path": "share/locale/uk/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "b92f0be63c805f1c9618ceebc92dd92850cdb1e2616dba5f00b5ec9d796fa242", + "size_in_bytes": 10300 + }, + { + "_path": "share/locale/uk/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "4080ad68849253b05dfc3b744169414d6a86654f988c0a90cfafbf634b6ec987", + "size_in_bytes": 168142 + }, + { + "_path": "share/locale/vi/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "56b079f0ef41fa3ffa1600aded268c89335e3622e2d1f7cbc0a338abe1558795", + "size_in_bytes": 8768 + }, + { + "_path": "share/locale/vi/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "f1fe09cd7770020f32eeb2967116488ed04a15b253f5d4869541266a4d123bce", + "size_in_bytes": 132326 + }, + { + "_path": "share/locale/zh_CN/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "f6f1940b1ff662704231eca176cc4183de1d20140ea7b2ddc0d5d43ff32a3d9b", + "size_in_bytes": 7669 + }, + { + "_path": "share/locale/zh_CN/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "0214b9b2079392854084aa901aed95892c5f49514dba1e8a34612643772fad01", + "size_in_bytes": 124114 + }, + { + "_path": "share/locale/zh_HK/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "5d76a0789b007e5de06ec4821710ded3e28998fa45a5754a77f375862a7a6de8", + "size_in_bytes": 3936 + }, + { + "_path": "share/locale/zh_TW/LC_MESSAGES/gettext-runtime.mo", + "path_type": "hardlink", + "sha256": "0ae200a38b096d6382d83130aa620564b62925b2b3ed13105dd3688240f4df9e", + "size_in_bytes": 7461 + }, + { + "_path": "share/locale/zh_TW/LC_MESSAGES/gettext-tools.mo", + "path_type": "hardlink", + "sha256": "ed0d032beaea575e28cd5ac149b6fdf5ac362f45bf913c779a0985980177b3df", + "size_in_bytes": 118833 + }, + { + "_path": "share/man/man1/autopoint.1", + "path_type": "hardlink", + "sha256": "b16e80f4a834693131474580990103c75e7d6e5672db6d19ab21cbbde269aa6b", + "size_in_bytes": 1346 + }, + { + "_path": "share/man/man1/envsubst.1", + "path_type": "hardlink", + "sha256": "55a473331ebb59ec3b13d44a82d62235d5f48477fb1627475e81f01d335def24", + "size_in_bytes": 1933 + }, + { + "_path": "share/man/man1/gettext.1", + "file_mode": "text", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "ec1e330a9d7295622f6391f807d49fb5cfeeba20ed5c0806c4698fb075f25f66", + "size_in_bytes": 2600 + }, + { + "_path": "share/man/man1/gettextize.1", + "path_type": "hardlink", + "sha256": "31830c1ef47d8f8f13f7147e71513e430507579214e1b990308368742cc31e65", + "size_in_bytes": 1556 + }, + { + "_path": "share/man/man1/msgattrib.1", + "path_type": "hardlink", + "sha256": "a1df0e5b041628714a6bbb4379bd50c74e17c851c6b83e3c1ea1ff87e47ddec1", + "size_in_bytes": 4480 + }, + { + "_path": "share/man/man1/msgcat.1", + "path_type": "hardlink", + "sha256": "c3e1b373bf2b2f299da80f81a67461cdf18af42a782b1ca7014080ec8cdc6609", + "size_in_bytes": 4472 + }, + { + "_path": "share/man/man1/msgcmp.1", + "path_type": "hardlink", + "sha256": "a841ccd3aab8eeb718ca50830a1469ab847ca7cbca334398470c66001cc81d40", + "size_in_bytes": 2369 + }, + { + "_path": "share/man/man1/msgcomm.1", + "path_type": "hardlink", + "sha256": "ff2c4bf2c1d56bd6d78ac4ed03238110cb66059cc79b8c372ac5dceefbf669ca", + "size_in_bytes": 4208 + }, + { + "_path": "share/man/man1/msgconv.1", + "path_type": "hardlink", + "sha256": "44b30d206aa4d245b588362c5fcf76e7718d9640e6fc7795df5f65ce8896c0ee", + "size_in_bytes": 3318 + }, + { + "_path": "share/man/man1/msgen.1", + "path_type": "hardlink", + "sha256": "b1e13e2cf638e3d9d58749fe604f8a6354bd829edf71d4e816cf2d427491a8d6", + "size_in_bytes": 3368 + }, + { + "_path": "share/man/man1/msgexec.1", + "path_type": "hardlink", + "sha256": "24b2d12185699a893deb6f5089d9b8ef3f0f7656d18c3f5748edb64a47b17667", + "size_in_bytes": 2258 + }, + { + "_path": "share/man/man1/msgfilter.1", + "path_type": "hardlink", + "sha256": "1507879f2a26355dac2e69f2b1cac742f74f543b498834a90cf7fc22874c2228", + "size_in_bytes": 3895 + }, + { + "_path": "share/man/man1/msgfmt.1", + "path_type": "hardlink", + "sha256": "06e2444edfc3784e245caa9793309c96f62fc7777f224be60fba0ff30ccbd1ee", + "size_in_bytes": 6529 + }, + { + "_path": "share/man/man1/msggrep.1", + "path_type": "hardlink", + "sha256": "22e76016591c0d75cbd1748a80d1913ae30bc70ea3f39c3d0c4882f21ac60128", + "size_in_bytes": 5398 + }, + { + "_path": "share/man/man1/msginit.1", + "path_type": "hardlink", + "sha256": "468d9e8c776bac6ab5a5c9d4ee05781857357be413ce98abc63f42f467d0611b", + "size_in_bytes": 2788 + }, + { + "_path": "share/man/man1/msgmerge.1", + "path_type": "hardlink", + "sha256": "8964cdb88f8d06df0f72b0a19d8d26d45e3bf611956d4153900c5f42281f0b90", + "size_in_bytes": 5228 + }, + { + "_path": "share/man/man1/msgunfmt.1", + "path_type": "hardlink", + "sha256": "b9e36e4a467774bd9e63c1a324e49ae8c7a9dd90228a3ebbc64724406f6ed8ff", + "size_in_bytes": 4128 + }, + { + "_path": "share/man/man1/msguniq.1", + "path_type": "hardlink", + "sha256": "e6bcef10db10221deda6c211caf2775a6ba9d35134bcd521efc2a3e6338c6c75", + "size_in_bytes": 4080 + }, + { + "_path": "share/man/man1/ngettext.1", + "file_mode": "text", + "path_type": "hardlink", + "prefix_placeholder": "/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho", + "sha256": "6568bfebb87c24484b424200b764300dc8b034204cd5f3e10b9b9d5c505407e3", + "size_in_bytes": 2636 + }, + { + "_path": "share/man/man1/recode-sr-latin.1", + "path_type": "hardlink", + "sha256": "4c566938dca1aa8dd0fecdc16f3977b9e92cd076137848330a09c363786e23ed", + "size_in_bytes": 1371 + }, + { + "_path": "share/man/man1/xgettext.1", + "path_type": "hardlink", + "sha256": "a94d51b23a86a18cc9bbaf21a001b8a5d440ad2171856b033d1683fb3577f59c", + "size_in_bytes": 7626 + }, + { + "_path": "share/man/man3/bind_textdomain_codeset.3", + "path_type": "hardlink", + "sha256": "74d836fe09e4f74cd05d76dc6c5ef44da35089645ef5c769eed376f906581170", + "size_in_bytes": 2873 + }, + { + "_path": "share/man/man3/bindtextdomain.3", + "path_type": "hardlink", + "sha256": "6dafda3fe5d0a94f35a5f84d69d3aa890b92e657bf9004ff33eec7208026b86e", + "size_in_bytes": 2717 + }, + { + "_path": "share/man/man3/dcgettext.3", + "path_type": "hardlink", + "sha256": "d6dc9dbbf715594c24bf6e9e568c295855e823aa8e9f4d988985cd383436f007", + "size_in_bytes": 19 + }, + { + "_path": "share/man/man3/dcngettext.3", + "path_type": "hardlink", + "sha256": "615d969454613bc1e83b4eca5f9fed9014fe0c479eebc9be269deed60415017e", + "size_in_bytes": 20 + }, + { + "_path": "share/man/man3/dgettext.3", + "path_type": "hardlink", + "sha256": "d6dc9dbbf715594c24bf6e9e568c295855e823aa8e9f4d988985cd383436f007", + "size_in_bytes": 19 + }, + { + "_path": "share/man/man3/dngettext.3", + "path_type": "hardlink", + "sha256": "615d969454613bc1e83b4eca5f9fed9014fe0c479eebc9be269deed60415017e", + "size_in_bytes": 20 + }, + { + "_path": "share/man/man3/gettext.3", + "path_type": "hardlink", + "sha256": "ede97a2b3cff3a08b2438f72642839a6d97bfa8936981537523ce026624af1ba", + "size_in_bytes": 4786 + }, + { + "_path": "share/man/man3/ngettext.3", + "path_type": "hardlink", + "sha256": "cb6e743eef909dc53332c0a14331eaaf72a115350ee8a11820bb1ad8cd9d569f", + "size_in_bytes": 2731 + }, + { + "_path": "share/man/man3/textdomain.3", + "path_type": "hardlink", + "sha256": "f5ff454e91be12da33b416e1f445623ae1aac502699d0d171eedc2e1f246c96c", + "size_in_bytes": 2163 + } + ], + "paths_version": 1 +} \ No newline at end of file diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/conda_build_config.yaml b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/conda_build_config.yaml new file mode 100644 index 0000000000000000000000000000000000000000..866fa46f09fba8e319b30a24734242f16b15ff72 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/conda_build_config.yaml @@ -0,0 +1,35 @@ +c_compiler: gcc +c_compiler_version: 14.3.0 +c_stdlib: sysroot +c_stdlib_version: '2.28' +channel_targets: defaults +cpu_optimization_target: nocona +cran_mirror: https://cran.r-project.org +cxx_compiler: gxx +cxx_compiler_version: 14.3.0 +extend_keys: +- pin_run_as_build +- extend_keys +- ignore_version +- ignore_build_only_deps +fortran_compiler: gfortran +gettext: '0' +ignore_build_only_deps: +- numpy +- python +libiconv: '1' +lua: '5' +ncurses: '6' +numpy: '1.26' +perl: 5.26.2 +pin_run_as_build: + python: + max_pin: x.x + min_pin: x.x + r-base: + max_pin: x.x + min_pin: x.x +platform: linux-64 +python: '3.11' +r_base: '3.5' +target_platform: linux-64 diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/install-gettext.sh b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/install-gettext.sh new file mode 100644 index 0000000000000000000000000000000000000000..2e5aa8da882754b6dc65ad664b25031c80442991 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/install-gettext.sh @@ -0,0 +1,17 @@ +#!/bin/bash + +set -euxo pipefail + +make install + +if [[ "${PKG_NAME}" != "gettext" ]]; then + rm -rf ${PREFIX}/share/gettext/projects + rm -rf ${PREFIX}/share/doc/libtextstyle + rm -rf ${PREFIX}/share/doc/gettext/examples + rm -rf ${PREFIX}/share/doc/gettext/javadoc2 +fi + +# This overlaps with readline: +rm -rf ${PREFIX}/share/info/dir + +find $PREFIX -name '*.la' -delete diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/meta.yaml b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/meta.yaml new file mode 100644 index 0000000000000000000000000000000000000000..38ecec9ec4553b242bbc421761c79cb10698fcba --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/meta.yaml @@ -0,0 +1,83 @@ +# This file created by conda-build 26.1.0 +# ------------------------------------------------ + +package: + name: gettext-tools + version: 0.25.1 +source: + url: https://ftp.gnu.org/pub/gnu/gettext/gettext-0.25.1.tar.xz + sha256: 2c8294be238f03fb3fa65b8051057e5b68167f3e21f08008070cf40a7051ba22 + patches: null +build: + ignore_run_exports_from: + - gxx_linux-64 14.3.0.* + number: 0 + string: h6a67909_0 +requirements: + build: + - _libgcc_mutex 0.1 main + - _openmp_mutex 5.1 1_gnu + - binutils_impl_linux-64 2.44 h4b9a079_2 + - binutils_linux-64 2.44 hc03a8fd_2 + - gcc_impl_linux-64 14.3.0 h4943218_4 + - gcc_linux-64 14.3.0 hda73cce_12 + - gxx_impl_linux-64 14.3.0 he634eba_4 + - gxx_linux-64 14.3.0 hca8765c_12 + - kernel-headers_linux-64 4.18.0 h3108a97_1 + - ld_impl_linux-64 2.44 h153f514_2 + - libgcc 15.2.0 h69a1729_7 + - libgcc-devel_linux-64 14.3.0 he7458c1_104 + - libgcc-ng 15.2.0 h166f726_7 + - libgomp 15.2.0 h4751f2c_7 + - libltdl 2.6.0 h47b2149_0 + - libsanitizer 14.3.0 hd4faa28_4 + - libstdcxx 15.2.0 h39759b7_7 + - libstdcxx-devel_linux-64 14.3.0 he7458c1_104 + - libtool 2.6.0 h7354ed3_0 + - make 4.2.1 h1bed415_1 + - sysroot_linux-64 2.28 h3108a97_1 + - tzdata 2025c he532380_0 + host: + - _libgcc_mutex 0.1 main + - _openmp_mutex 5.1 1_gnu + - libasprintf 0.25.1 hf2ab22a_0 + - libasprintf-devel 0.25.1 hf2ab22a_0 + - libgcc 15.2.0 h69a1729_7 + - libgcc-ng 15.2.0 h166f726_7 + - libgettextpo 0.25.1 hf2ab22a_0 + - libgettextpo-devel 0.25.1 hf2ab22a_0 + - libgomp 15.2.0 h4751f2c_7 + - libiconv 1.18 h75a1612_0 + - libstdcxx 15.2.0 h39759b7_7 + - ncurses 6.5 h7934f7d_0 + run: + - __glibc >=2.28,<3.0.a0 + - libgcc >=14 + - libiconv >=1.18,<2.0a0 + - ncurses >=6.5,<7.0a0 +test: + files: + - an.po + requires: + - ncurses 6.* + commands: + - msgfmt -o an.gmo an.po +about: + home: https://www.gnu.org/software/gettext + license: GPL-3.0-or-later + license_file: COPYING + summary: Internationalization package (executable tools) +extra: + feedstock-name: gettext + recipe-maintainers: + - ocefpaf + - pkgw + - scopatz + - xhochy + final: true + copy_test_source_files: true + remote_url: https://github.com/AnacondaRecipes/gettext-feedstock + sha: 4bf3d3ea276e8ac4d8833cf6edee3f440fe7f401 + task_id: AU3TsZcCRaK9jiaCosfOMQ + task_run_id: '0' + pbp_graph_uuid: 3e8405fd-0d33-4442-9c6e-741a46b5c97d diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/.gitattributes b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/.gitattributes new file mode 100644 index 0000000000000000000000000000000000000000..2126fa4a1d6ca54c25a9f0f1403e56d58c72a041 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/.gitattributes @@ -0,0 +1,2 @@ +ar-lib text eol=lf +compile text eol=lf diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/an.po b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/an.po new file mode 100644 index 0000000000000000000000000000000000000000..ea2051bf913a94d6b2839d2cf5bba8a6d9acce56 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/an.po @@ -0,0 +1,145 @@ +# Aragonese translation for glib-networking. +# Copyright (C) 2013 glib-networking's COPYRIGHT HOLDER +# This file is distributed under the same license as the glib-networking package. +# FIRST AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: glib-networking master\n" +"Report-Msgid-Bugs-To: http://bugzilla.gnome.org/enter_bug.cgi?product=glib&keywords=I18N+L10N&component=network\n" +"POT-Creation-Date: 2013-02-19 13:01+0000\n" +"PO-Revision-Date: 2013-02-20 01:19+0100\n" +"Last-Translator: Daniel Martinez \n" +"Language-Team: Aragonese \n" +"Language: an\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../proxy/libproxy/glibproxyresolver.c:150 +msgid "Proxy resolver internal error." +msgstr "Error interna d'o proxy." + +#: ../tls/gnutls/gtlscertificate-gnutls.c:173 +#, c-format +msgid "Could not parse DER certificate: %s" +msgstr "No se podió analisar o certificau DER: %s" + +#: ../tls/gnutls/gtlscertificate-gnutls.c:194 +#, c-format +msgid "Could not parse PEM certificate: %s" +msgstr "No se podió analisar o certificau PEM: %s" + +#: ../tls/gnutls/gtlscertificate-gnutls.c:225 +#, c-format +msgid "Could not parse DER private key: %s" +msgstr "No se podió analisar a clau privada DER: %s" + +#: ../tls/gnutls/gtlscertificate-gnutls.c:256 +#, c-format +msgid "Could not parse PEM private key: %s" +msgstr "No se podió analisar a clau privada PEM: %s" + +#: ../tls/gnutls/gtlscertificate-gnutls.c:296 +msgid "No certificate data provided" +msgstr "No s'han proporcionau datos d'o certificau" + +#: ../tls/gnutls/gtlsclientconnection-gnutls.c:309 +msgid "Server required TLS certificate" +msgstr "O servidor requiere un certificau TLS" + +#: ../tls/gnutls/gtlsconnection-gnutls.c:258 +#, c-format +msgid "Could not create TLS connection: %s" +msgstr "No se podió creyar a connexión TLS: %s" + +#: ../tls/gnutls/gtlsconnection-gnutls.c:520 +msgid "Connection is closed" +msgstr "A connexión ye zarrada" + +#: ../tls/gnutls/gtlsconnection-gnutls.c:582 +#: ../tls/gnutls/gtlsconnection-gnutls.c:1419 +msgid "Operation would block" +msgstr "A operación se blocará" + +#: ../tls/gnutls/gtlsconnection-gnutls.c:712 +msgid "Peer failed to perform TLS handshake" +msgstr "O par falló en realizar a negociación TLS" + +#: ../tls/gnutls/gtlsconnection-gnutls.c:729 +msgid "Peer requested illegal TLS rehandshake" +msgstr "O par solicitó una renegociación TLS ilegal" + +#: ../tls/gnutls/gtlsconnection-gnutls.c:755 +msgid "TLS connection closed unexpectedly" +msgstr "A connexión TLS se zarró inasperadament" + +#: ../tls/gnutls/gtlsconnection-gnutls.c:765 +msgid "TLS connection peer did not send a certificate" +msgstr "O par d'a connexión TLS no ninvió un certificau" + +#: ../tls/gnutls/gtlsconnection-gnutls.c:1146 +#: ../tls/gnutls/gtlsconnection-gnutls.c:1165 +#, c-format +msgid "Error performing TLS handshake: %s" +msgstr "Error en realizar a negociación TLS: %s" + +#: ../tls/gnutls/gtlsconnection-gnutls.c:1175 +msgid "Server did not return a valid TLS certificate" +msgstr "O servidor no devolvió un certificau TLS valido" + +#: ../tls/gnutls/gtlsconnection-gnutls.c:1250 +msgid "Unacceptable TLS certificate" +msgstr "Certificau TLS inacceptable" + +#: ../tls/gnutls/gtlsconnection-gnutls.c:1442 +#, c-format +msgid "Error reading data from TLS socket: %s" +msgstr "Error en leyer datos d'o socket TLS: %s" + +#: ../tls/gnutls/gtlsconnection-gnutls.c:1471 +#, c-format +msgid "Error writing data to TLS socket: %s" +msgstr "Error en escribir datos en o socket TLS: %s" + +#: ../tls/gnutls/gtlsconnection-gnutls.c:1515 +msgid "Connection is already closed" +msgstr "A connexión ya ye zarrada" + +#: ../tls/gnutls/gtlsconnection-gnutls.c:1525 +#, c-format +msgid "Error performing TLS close: %s" +msgstr "Error en zarrar o TLS: %s" + +#: ../tls/gnutls/gtlsserverconnection-gnutls.c:103 +msgid "Certificate has no private key" +msgstr "O certificau no tiene clau privada" + +#: ../tls/pkcs11/gpkcs11pin.c:108 +msgid "This is the last chance to enter the PIN correctly before the token is locked." +msgstr "Ista ye a zaguera oportunidat ta introducir o PIN correctament antes que se bloque o \"token\"." + +#: ../tls/pkcs11/gpkcs11pin.c:110 +msgid "Several PIN attempts have been incorrect, and the token will be locked after further failures." +msgstr "Quantos intentos d'introducir o PIN han estau incorrectos y o \"token\" se blocará dimpués de mas fallos." + +#: ../tls/pkcs11/gpkcs11pin.c:112 +msgid "The PIN entered is incorrect." +msgstr "O PIN introduciu ye incorrecto." + +#: ../tls/pkcs11/gpkcs11slot.c:446 +msgid "Module" +msgstr "Modulo" + +#: ../tls/pkcs11/gpkcs11slot.c:447 +msgid "PKCS#11 Module Pointer" +msgstr "Puntero d'o modulo PKCS#11" + +#: ../tls/pkcs11/gpkcs11slot.c:454 +msgid "Slot ID" +msgstr "ID d'a ranura" + +#: ../tls/pkcs11/gpkcs11slot.c:455 +msgid "PKCS#11 Slot Identifier" +msgstr "Identificador d'a ranura de PKCS#11" + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/ar-lib b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/ar-lib new file mode 100644 index 0000000000000000000000000000000000000000..54c6bdbf7f1b314721a3af9996f6ed6dd7091619 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/ar-lib @@ -0,0 +1,275 @@ +#! /bin/sh +# Wrapper for Microsoft lib.exe + +me=ar-lib +scriptversion=2019-07-04.01; # UTC + +# Copyright (C) 2010-2022 Free Software Foundation, Inc. +# Written by Peter Rosin . +# +# 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 2, 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 . + +# As a special exception to the GNU General Public License, if you +# distribute this file as part of a program that contains a +# configuration script generated by Autoconf, you may include it under +# the same distribution terms that you use for the rest of that program. + +# This file is maintained in Automake, please report +# bugs to or send patches to +# . + + +# func_error message +func_error () +{ + echo "$me: $1" 1>&2 + exit 1 +} + +file_conv= + +# func_file_conv build_file +# Convert a $build file to $host form and store it in $file +# Currently only supports Windows hosts. +func_file_conv () +{ + file=$1 + case $file in + / | /[!/]*) # absolute file, and not a UNC file + if test -z "$file_conv"; then + # lazily determine how to convert abs files + case `uname -s` in + MINGW*) + file_conv=mingw + ;; + CYGWIN* | MSYS*) + file_conv=cygwin + ;; + *) + file_conv=wine + ;; + esac + fi + case $file_conv in + mingw) + file=`cmd //C echo "$file " | sed -e 's/"\(.*\) " *$/\1/'` + ;; + cygwin | msys) + file=`cygpath -m "$file" || echo "$file"` + ;; + wine) + file=`winepath -w "$file" || echo "$file"` + ;; + esac + ;; + esac +} + +# func_at_file at_file operation archive +# Iterate over all members in AT_FILE performing OPERATION on ARCHIVE +# for each of them. +# When interpreting the content of the @FILE, do NOT use func_file_conv, +# since the user would need to supply preconverted file names to +# binutils ar, at least for MinGW. +func_at_file () +{ + operation=$2 + archive=$3 + at_file_contents=`cat "$1"` + eval set x "$at_file_contents" + shift + + for member + do + $AR -NOLOGO $operation:"$member" "$archive" || exit $? + done +} + +case $1 in + '') + func_error "no command. Try '$0 --help' for more information." + ;; + -h | --h*) + cat <. +# +# 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 2, 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 . + +# As a special exception to the GNU General Public License, if you +# distribute this file as part of a program that contains a +# configuration script generated by Autoconf, you may include it under +# the same distribution terms that you use for the rest of that program. + +# This file is maintained in Automake, please report +# bugs to or send patches to +# . + +nl=' +' + +# We need space, tab and new line, in precisely that order. Quoting is +# there to prevent tools from complaining about whitespace usage. +IFS=" "" $nl" + +file_conv= + +# func_file_conv build_file lazy +# Convert a $build file to $host form and store it in $file +# Currently only supports Windows hosts. If the determined conversion +# type is listed in (the comma separated) LAZY, no conversion will +# take place. +func_file_conv () +{ + file=$1 + case $file in + / | /[!/]*) # absolute file, and not a UNC file + if test -z "$file_conv"; then + # lazily determine how to convert abs files + case `uname -s` in + MINGW*) + file_conv=mingw + ;; + CYGWIN* | MSYS*) + file_conv=cygwin + ;; + *) + file_conv=wine + ;; + esac + fi + case $file_conv/,$2, in + *,$file_conv,*) + ;; + mingw/*) + file=`cmd //C echo "$file " | sed -e 's/"\(.*\) " *$/\1/'` + ;; + cygwin/* | msys/*) + file=`cygpath -m "$file" || echo "$file"` + ;; + wine/*) + file=`winepath -w "$file" || echo "$file"` + ;; + esac + ;; + esac +} + +# func_cl_dashL linkdir +# Make cl look for libraries in LINKDIR +func_cl_dashL () +{ + func_file_conv "$1" + if test -z "$lib_path"; then + lib_path=$file + else + lib_path="$lib_path;$file" + fi + linker_opts="$linker_opts -LIBPATH:$file" +} + +# func_cl_dashl library +# Do a library search-path lookup for cl +func_cl_dashl () +{ + lib=$1 + found=no + save_IFS=$IFS + IFS=';' + for dir in $lib_path $LIB + do + IFS=$save_IFS + if $shared && test -f "$dir/$lib.dll.lib"; then + found=yes + lib=$dir/$lib.dll.lib + break + fi + if test -f "$dir/$lib.lib"; then + found=yes + lib=$dir/$lib.lib + break + fi + if test -f "$dir/lib$lib.a"; then + found=yes + lib=$dir/lib$lib.a + break + fi + done + IFS=$save_IFS + + if test "$found" != yes; then + lib=$lib.lib + fi +} + +# func_cl_wrapper cl arg... +# Adjust compile command to suit cl +func_cl_wrapper () +{ + # Assume a capable shell + lib_path= + shared=: + linker_opts= + for arg + do + if test -n "$eat"; then + eat= + else + case $1 in + -o) + # configure might choose to run compile as 'compile cc -o foo foo.c'. + eat=1 + case $2 in + *.o | *.[oO][bB][jJ]) + func_file_conv "$2" + set x "$@" -Fo"$file" + shift + ;; + *) + func_file_conv "$2" + set x "$@" -Fe"$file" + shift + ;; + esac + ;; + -I) + eat=1 + func_file_conv "$2" mingw + set x "$@" -I"$file" + shift + ;; + -I*) + func_file_conv "${1#-I}" mingw + set x "$@" -I"$file" + shift + ;; + -l) + eat=1 + func_cl_dashl "$2" + set x "$@" "$lib" + shift + ;; + -l*) + func_cl_dashl "${1#-l}" + set x "$@" "$lib" + shift + ;; + -L) + eat=1 + func_cl_dashL "$2" + ;; + -L*) + func_cl_dashL "${1#-L}" + ;; + -static) + shared=false + ;; + -Wl,*) + arg=${1#-Wl,} + save_ifs="$IFS"; IFS=',' + for flag in $arg; do + IFS="$save_ifs" + linker_opts="$linker_opts $flag" + done + IFS="$save_ifs" + ;; + -Xlinker) + eat=1 + linker_opts="$linker_opts $2" + ;; + -*) + set x "$@" "$1" + shift + ;; + *.cc | *.CC | *.cxx | *.CXX | *.[cC]++) + func_file_conv "$1" + set x "$@" -Tp"$file" + shift + ;; + *.c | *.cpp | *.CPP | *.lib | *.LIB | *.Lib | *.OBJ | *.obj | *.[oO]) + func_file_conv "$1" mingw + set x "$@" "$file" + shift + ;; + *) + set x "$@" "$1" + shift + ;; + esac + fi + shift + done + if test -n "$linker_opts"; then + linker_opts="-link$linker_opts" + fi + exec "$@" $linker_opts + exit 1 +} + +eat= + +case $1 in + '') + echo "$0: No command. Try '$0 --help' for more information." 1>&2 + exit 1; + ;; + -h | --h*) + cat <<\EOF +Usage: compile [--help] [--version] PROGRAM [ARGS] + +Wrapper for compilers which do not understand '-c -o'. +Remove '-o dest.o' from ARGS, run PROGRAM with the remaining +arguments, and rename the output as expected. + +If you are trying to build a whole package this is not the +right script to run: please start by reading the file 'INSTALL'. + +Report bugs to . +EOF + exit $? + ;; + -v | --v*) + echo "compile $scriptversion" + exit $? + ;; + cl | *[/\\]cl | cl.exe | *[/\\]cl.exe | \ + clang-cl | *[/\\]clang-cl | clang-cl.exe | *[/\\]clang-cl.exe | \ + icl | *[/\\]icl | icl.exe | *[/\\]icl.exe ) + func_cl_wrapper "$@" # Doesn't return... + ;; +esac + +ofile= +cfile= + +for arg +do + if test -n "$eat"; then + eat= + else + case $1 in + -o) + # configure might choose to run compile as 'compile cc -o foo foo.c'. + # So we strip '-o arg' only if arg is an object. + eat=1 + case $2 in + *.o | *.obj) + ofile=$2 + ;; + *) + set x "$@" -o "$2" + shift + ;; + esac + ;; + *.c) + cfile=$1 + set x "$@" "$1" + shift + ;; + *) + set x "$@" "$1" + shift + ;; + esac + fi + shift +done + +if test -z "$ofile" || test -z "$cfile"; then + # If no '-o' option was seen then we might have been invoked from a + # pattern rule where we don't need one. That is ok -- this is a + # normal compilation that the losing compiler can handle. If no + # '.c' file was seen then we are probably linking. That is also + # ok. + exec "$@" +fi + +# Name of file we expect compiler to create. +cofile=`echo "$cfile" | sed 's|^.*[\\/]||; s|^[a-zA-Z]:||; s/\.c$/.o/'` + +# Create the lock directory. +# Note: use '[/\\:.-]' here to ensure that we don't use the same name +# that we are using for the .o file. Also, base the name on the expected +# object file name, since that is what matters with a parallel build. +lockdir=`echo "$cofile" | sed -e 's|[/\\:.-]|_|g'`.d +while true; do + if mkdir "$lockdir" >/dev/null 2>&1; then + break + fi + sleep 1 +done +# FIXME: race condition here if user kills between mkdir and trap. +trap "rmdir '$lockdir'; exit 1" 1 2 15 + +# Run the compile. +"$@" +ret=$? + +if test -f "$cofile"; then + test "$cofile" = "$ofile" || mv "$cofile" "$ofile" +elif test -f "${cofile}bj"; then + test "${cofile}bj" = "$ofile" || mv "${cofile}bj" "$ofile" +fi + +rmdir "$lockdir" +exit $ret + +# Local Variables: +# mode: shell-script +# sh-indentation: 2 +# eval: (add-hook 'before-save-hook 'time-stamp) +# time-stamp-start: "scriptversion=" +# time-stamp-format: "%:y-%02m-%02d.%02H" +# time-stamp-time-zone: "UTC0" +# time-stamp-end: "; # UTC" +# End: diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-asprintf-devel.bat b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-asprintf-devel.bat new file mode 100644 index 0000000000000000000000000000000000000000..5c43f5c19c29354b2f3008a53e45dd8b67b49620 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-asprintf-devel.bat @@ -0,0 +1,17 @@ +@echo on + +if not exist %LIBRARY_PREFIX%\include md %LIBRARY_PREFIX%\include +if errorlevel 1 exit 1 + +copy gettext-runtime\libasprintf\autosprintf.h %LIBRARY_PREFIX%\include\autosprintf.h +if errorlevel 1 exit 1 + +if not exist %LIBRARY_PREFIX%\lib md %LIBRARY_PREFIX%\lib +if errorlevel 1 exit 1 + +copy gettext-runtime\libasprintf\.libs\asprintf.dll.lib %LIBRARY_PREFIX%\lib\asprintf.dll.lib +if errorlevel 1 exit 1 + +@rem Enforce dynamic linkage +copy gettext-runtime\libasprintf\.libs\asprintf.dll.lib %LIBRARY_PREFIX%\lib\asprintf.lib +if errorlevel 1 exit 1 diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-asprintf-devel.sh b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-asprintf-devel.sh new file mode 100644 index 0000000000000000000000000000000000000000..e790223a2fa1805856d95bcd9bcbb918a3738829 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-asprintf-devel.sh @@ -0,0 +1,16 @@ +#!/bin/bash + +set -euxo pipefail + +mkdir -p ${PREFIX}/include +cp ./gettext-runtime/libasprintf/autosprintf.h ${PREFIX}/include/autosprintf.h + +pushd ${PREFIX}/lib +if [[ "${target_platform}" == osx-* ]]; then + ln -s libasprintf.*.dylib libasprintf.dylib +else + test -f libasprintf.so.0 + ln -s libasprintf.so.0 libasprintf.so +fi +popd + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-asprintf.bat b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-asprintf.bat new file mode 100644 index 0000000000000000000000000000000000000000..e1a7182a201ae7a6fd580d15be4a359a540ad6fc --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-asprintf.bat @@ -0,0 +1,7 @@ +@echo on + +if not exist %LIBRARY_PREFIX%\bin md %LIBRARY_PREFIX%\bin +if errorlevel 1 exit 1 + +copy gettext-runtime\libasprintf\.libs\asprintf-0.dll %LIBRARY_PREFIX%\bin +if errorlevel 1 exit 1 diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-asprintf.sh b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-asprintf.sh new file mode 100644 index 0000000000000000000000000000000000000000..0a0defbb1601d5fdc7859cb3caa40cdfcd0d0623 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-asprintf.sh @@ -0,0 +1,11 @@ +#!/bin/bash + +set -euxo pipefail + +mkdir -p $PREFIX/lib + +if [[ "${target_platform}" == osx-* ]]; then + cp ./gettext-runtime/libasprintf/.libs/libasprintf.*.dylib $PREFIX/lib +else + cp ./gettext-runtime/libasprintf/.libs/libasprintf.so.* $PREFIX/lib +fi diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-gettext.bat b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-gettext.bat new file mode 100644 index 0000000000000000000000000000000000000000..d52472e49b7b7fe580071b8d2a6f269f67118e63 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-gettext.bat @@ -0,0 +1,25 @@ +:: Delegate to the Unix script. We need to translate the key path variables +:: to be Unix-y rather than Windows-y, though. + +copy "%RECIPE_DIR%\build.sh" . + +set MSYSTEM=MINGW%ARCH% +set MSYS2_PATH_TYPE=inherit +set CHERE_INVOKING=1 + +set "saved_recipe_dir=%RECIPE_DIR%" +FOR /F "delims=" %%i IN ('cygpath.exe -u -p "%PATH%"') DO set "PATH_OVERRIDE=%%i" +FOR /F "delims=" %%i IN ('cygpath.exe -u "%BUILD_PREFIX%"') DO set "BUILD_PREFIX=%%i" +FOR /F "delims=" %%i IN ('cygpath.exe -m "%LIBRARY_PREFIX%"') DO set "LIBRARY_PREFIX_M=%%i" +FOR /F "delims=" %%i IN ('cygpath.exe -u "%LIBRARY_PREFIX%"') DO set "LIBRARY_PREFIX_U=%%i" +FOR /F "delims=" %%i IN ('cygpath.exe -u "%PREFIX%"') DO set "PREFIX=%%i" +FOR /F "delims=" %%i IN ('cygpath.exe -u "%PYTHON%"') DO set "PYTHON=%%i" +FOR /F "delims=" %%i IN ('cygpath.exe -u "%RECIPE_DIR%"') DO set "RECIPE_DIR=%%i" +FOR /F "delims=" %%i IN ('cygpath.exe -u "%SP_DIR%"') DO set "SP_DIR=%%i" +FOR /F "delims=" %%i IN ('cygpath.exe -u "%SRC_DIR%"') DO set "SRC_DIR=%%i" +FOR /F "delims=" %%i IN ('cygpath.exe -u "%STDLIB_DIR%"') DO set "STDLIB_DIR=%%i" + +bash -lxc "${RECIPE_DIR}/install-gettext.sh" +if errorlevel 1 exit 1 +exit 0 + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-gettext.sh b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-gettext.sh new file mode 100644 index 0000000000000000000000000000000000000000..2e5aa8da882754b6dc65ad664b25031c80442991 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-gettext.sh @@ -0,0 +1,17 @@ +#!/bin/bash + +set -euxo pipefail + +make install + +if [[ "${PKG_NAME}" != "gettext" ]]; then + rm -rf ${PREFIX}/share/gettext/projects + rm -rf ${PREFIX}/share/doc/libtextstyle + rm -rf ${PREFIX}/share/doc/gettext/examples + rm -rf ${PREFIX}/share/doc/gettext/javadoc2 +fi + +# This overlaps with readline: +rm -rf ${PREFIX}/share/info/dir + +find $PREFIX -name '*.la' -delete diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-libgettextpo-devel.bat b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-libgettextpo-devel.bat new file mode 100644 index 0000000000000000000000000000000000000000..7da0a3cdfad6f437327187d069c6bfc67e06500c --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-libgettextpo-devel.bat @@ -0,0 +1,18 @@ +@echo on + +if not exist %LIBRARY_PREFIX%\include md %LIBRARY_PREFIX%\include +if errorlevel 1 exit 1 + +copy gettext-tools\libgettextpo\gettext-po.h %LIBRARY_PREFIX%\include +if errorlevel 1 exit 1 + +if not exist %LIBRARY_PREFIX%\lib md %LIBRARY_PREFIX%\lib +if errorlevel 1 exit 1 + +copy gettext-tools\libgettextpo\.libs\gettextpo.dll.lib %LIBRARY_PREFIX%\lib +if errorlevel 1 exit 1 + +@rem Enforce dynamic linkage +copy gettext-tools\libgettextpo\.libs\gettextpo.dll.lib %LIBRARY_PREFIX%\lib\gettextpo.lib +if errorlevel 1 exit 1 + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-libgettextpo-devel.sh b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-libgettextpo-devel.sh new file mode 100644 index 0000000000000000000000000000000000000000..c1239bb32ec550050e270853eeac43944d6b9562 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-libgettextpo-devel.sh @@ -0,0 +1,16 @@ +#!/bin/bash + +set -euxo pipefail + +mkdir -p ${PREFIX}/include +cp ./gettext-tools/libgettextpo/gettext-po.h ${PREFIX}/include/gettext-po.h + +pushd ${PREFIX}/lib +if [[ "${target_platform}" == osx-* ]]; then + ln -s libgettextpo.*.dylib libgettextpo.dylib +else + test -f libgettextpo.so.0 + ln -s libgettextpo.so.0 libgettextpo.so +fi +popd + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-libgettextpo.bat b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-libgettextpo.bat new file mode 100644 index 0000000000000000000000000000000000000000..962a85abda648c4eb9bcbc8581541cdfd550f31d --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-libgettextpo.bat @@ -0,0 +1,7 @@ +@echo on + +if not exist %LIBRARY_PREFIX%\bin md %LIBRARY_PREFIX%\bin +if errorlevel 1 exit 1 + +copy gettext-tools\libgettextpo\.libs\gettextpo-0.dll %LIBRARY_PREFIX%\bin +if errorlevel 1 exit 1 diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-libgettextpo.sh b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-libgettextpo.sh new file mode 100644 index 0000000000000000000000000000000000000000..9e2afdc5569cbbad2164cd670fddfece1d370b9d --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-libgettextpo.sh @@ -0,0 +1,11 @@ +#!/bin/bash + +set -euxo pipefail + +mkdir -p $PREFIX/lib + +if [[ "${target_platform}" == osx-* ]]; then + cp ./gettext-tools/libgettextpo/.libs/libgettextpo.*.dylib $PREFIX/lib +else + cp ./gettext-tools/libgettextpo/.libs/libgettextpo.so.* $PREFIX/lib +fi diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-libintl-devel.bat b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-libintl-devel.bat new file mode 100644 index 0000000000000000000000000000000000000000..e9bc3fef844f8162ffde23b8be8be837afa4c9e7 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-libintl-devel.bat @@ -0,0 +1,17 @@ +@echo on + +if not exist %LIBRARY_PREFIX%\include md %LIBRARY_PREFIX%\include +if errorlevel 1 exit 1 + +copy gettext-runtime\intl\libintl.h %LIBRARY_PREFIX%\include\libintl.h +if errorlevel 1 exit 1 + +if not exist %LIBRARY_PREFIX%\lib md %LIBRARY_PREFIX%\lib +if errorlevel 1 exit 1 + +copy gettext-runtime\intl\.libs\intl.dll.lib %LIBRARY_PREFIX%\lib +if errorlevel 1 exit 1 + +@rem Enforce dynamic linkage +copy gettext-runtime\intl\.libs\intl.dll.lib %LIBRARY_PREFIX%\lib\intl.lib +if errorlevel 1 exit 1 diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-libintl-devel.sh b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-libintl-devel.sh new file mode 100644 index 0000000000000000000000000000000000000000..dc72794436c2cc315b6b060b52ffea631257f5cf --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-libintl-devel.sh @@ -0,0 +1,16 @@ +#!/bin/bash + +set -euxo pipefail + +mkdir -p ${PREFIX}/include +cp ./gettext-runtime/intl/libintl.h ${PREFIX}/include/libintl.h + +pushd ${PREFIX}/lib +if [[ "${target_platform}" == osx-* ]]; then + ln -s libintl.*.dylib libintl.dylib +else + echo "This shouldn't be built on Linux" + exit 1 + # ln -s libintl.so.0 libintl.so +fi +popd diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-libintl.bat b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-libintl.bat new file mode 100644 index 0000000000000000000000000000000000000000..8a582c9db8eab8082a0cfb1fe1600e434aa3d0a3 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-libintl.bat @@ -0,0 +1,7 @@ +@echo on + +if not exist %LIBRARY_PREFIX%\bin md %LIBRARY_PREFIX%\bin +if errorlevel 1 exit 1 + +copy gettext-runtime\intl\.libs\intl-8.dll %LIBRARY_PREFIX%\bin +if errorlevel 1 exit 1 diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-libintl.sh b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-libintl.sh new file mode 100644 index 0000000000000000000000000000000000000000..864f86a3dd570c9d897fb92ec9d8d8f6dbe47d4f --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/install-libintl.sh @@ -0,0 +1,11 @@ +#!/bin/bash + +set -euxo pipefail + +mkdir -p $PREFIX/lib + +if [[ "${target_platform}" == osx-* ]]; then + cp ./gettext-runtime/intl/.libs/libintl.*.dylib $PREFIX/lib +else + cp ./gettext-runtime/intl/.libs/libintl.so.* $PREFIX/lib +fi diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/meta.yaml b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/meta.yaml new file mode 100644 index 0000000000000000000000000000000000000000..d31928cef7d7580f39bf191f7921ca3fd83401ca --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/meta.yaml @@ -0,0 +1,449 @@ +{% set version = "0.25.1" %} +{% set am_version = "1.15" %} # keep synchronized with build.sh +{% set posix = 'm2-' if win else '' %} +{% set native = 'm2w64-' if win else '' %} + +# Note: as of 0.23.1, we have given up on trying to build gettext on Windows +# with MSVC -- there are new patterns that may make it simply impossible due to +# the ways that some DLL-exported variables are used. See discussion in #35. It +# *is* possible to build gettext on Windows using MinGW/GCC -- see #34. But for +# now we would rather turn off the Windows build than undertake the major +# migration that a switch to GCC would entail. +# +# For the time being, we're not stripping out the Windows build files and +# configuration from this recipe, but they're not being used. + +package: + name: gettext-split + version: {{ version }} + +source: + url: https://ftp.gnu.org/pub/gnu/gettext/gettext-{{ version }}.tar.xz + sha256: 2c8294be238f03fb3fa65b8051057e5b68167f3e21f08008070cf40a7051ba22 + patches: + - patches/0001-Mark-v-snprintf-as-available.patch # [win] + - patches/0002-Prevent-libtool-from-worrying-about-dependent-librar.patch # [win] + - patches/0003-Fix-some-DLL-export-markings-in-libintl.patch # [win] + - patches/0004-Fix-quoting-when-invoking-windres.patch # [win] + - patches/0005-CXXLD-is-not-a-thing.patch # [win] + - patches/0006-Work-around-Unixisms-in-libgettextpo.patch # [win] + - patches/0007-Add-missing-extern-C-protectors.patch # [win] + - patches/0008-Declaration-ordering.patch # [win] + +build: + number: 0 + skip: true # [win] + +requirements: + build: + - posix # [win] + - {{ posix }}autoconf # [win] + - {{ posix }}automake{{ am_version }} # [win] + - {{ posix }}libtool + - {{ posix }}patch # [win] + - {{ posix }}sed # [win] + - {{ native }}binutils # [win] + - {{ native }}crt-git # [win] + - {{ stdlib('c') }} + - {{ compiler('c') }} + - {{ compiler('cxx') }} + - make # [unix] + host: + - libiconv {{ libiconv }} + - ncurses {{ ncurses }} # [not win] + +outputs: + - name: libintl + build: + skip: true # [linux] + run_exports: + # Seems pretty good: https://abi-laboratory.pro/tracker/timeline/gettext + - {{ pin_subpackage('libintl') }} + ignore_run_exports_from: + - {{ compiler('cxx') }} # [unix] + script: install-libintl.sh # [unix] + script: install-libintl.bat # [not unix] + requirements: + build: + - posix # [win] + - {{ posix }}autoconf # [win] + - {{ posix }}automake{{ am_version }} # [win] + - {{ posix }}libtool + - {{ posix }}patch # [win] + - {{ posix }}sed # [win] + - {{ native }}binutils # [win] + - {{ native }}crt-git # [win] + - {{ stdlib('c') }} # [not win] + - {{ compiler('c') }} # [not win] + - {{ compiler('cxx') }} # [not win] + - make # [unix] + host: + - libiconv {{ libiconv }} + test: + commands: + # Only the actual binary (versioned) variant should be in this package + - test -f ${PREFIX}/lib/libintl.*.dylib # [osx] + - test -f ${PREFIX}/lib/libintl.so.* # [linux] + - if not exist %PREFIX%\Library\bin\intl-*.dll exit /b 1 # [win] + # The unversioned variants as well as the lib on Windows should be in the main gettext package. + - test ! -f ${PREFIX}/lib/libintl$SHLIB_EXT # [not win] + - test ! -f ${PREFIX}/include/libintl.h # [osx] + - if exist %PREFIX%\Library\lib\intl.dll.lib exit /b 1 # [win] + - if exist %PREFIX%\Library\lib\intl.lib exit /b 1 # [win] + - if exist %PREFIX%\Library\include\libintl.h exit /b1 # [win] + about: + home: https://www.gnu.org/software/gettext + license: LGPL-2.1-or-later + license_file: COPYING + summary: library that provides native language support to programs + + - name: libintl-devel + build: + skip: true # [linux] + run_exports: + # Seems pretty good: https://abi-laboratory.pro/tracker/timeline/gettext + - {{ pin_subpackage('libintl') }} + ignore_run_exports_from: + - {{ compiler('cxx') }} # [unix] + script: install-libintl-devel.sh # [unix] + script: install-libintl-devel.bat # [not unix] + requirements: + build: + - posix # [win] + - {{ posix }}autoconf # [win] + - {{ posix }}automake{{ am_version }} # [win] + - {{ posix }}libtool + - {{ posix }}patch # [win] + - {{ posix }}sed # [win] + - {{ native }}binutils # [win] + - {{ native }}crt-git # [win] + - {{ stdlib('c') }} # [not win] + - {{ compiler('c') }} # [not win] + - {{ compiler('cxx') }} # [not win] + - make # [unix] + host: + - libiconv {{ libiconv }} + - {{ pin_subpackage('libintl', exact=true) }} + run: + - {{ pin_subpackage('libintl', exact=true) }} + test: + commands: + - test -f ${PREFIX}/lib/libintl${SHLIB_EXT} # [osx] + - test -f ${PREFIX}/include/libintl.h # [osx] + - if not exist %PREFIX%\Library\lib\intl.dll.lib exit /b 1 # [win] + - if not exist %PREFIX%\Library\lib\intl.lib exit /b 1 # [win] + - if not exist %PREFIX%\Library\include\libintl.h exit /b1 # [win] + about: + home: https://www.gnu.org/software/gettext + license: LGPL-2.1-or-later + license_file: COPYING + summary: library that provides native language support to programs + + - name: libasprintf + build: + run_exports: + # Seems pretty good: https://abi-laboratory.pro/tracker/timeline/gettext + - {{ pin_subpackage('libasprintf') }} + ignore_run_exports: + - libiconv + script: install-asprintf.sh # [unix] + script: install-asprintf.bat # [not unix] + requirements: + build: + - posix # [win] + - {{ posix }}autoconf # [win] + - {{ posix }}automake{{ am_version }} # [win] + - {{ posix }}libtool + - {{ posix }}patch # [win] + - {{ posix }}sed # [win] + - {{ native }}binutils # [win] + - {{ native }}crt-git # [win] + - {{ stdlib('c') }} # [not win] + - {{ compiler('c') }} # [not win] + - {{ compiler('cxx') }} # [not win] + - make # [unix] + host: + - libiconv {{ libiconv }} + test: + commands: + # Only the actual binary (versioned) variant should be in this package + - test -f ${PREFIX}/lib/libasprintf.*.dylib # [osx] + - test -f ${PREFIX}/lib/libasprintf.so.0 # [linux] + - if not exist %PREFIX%\Library\bin\asprintf-*.dll exit /b 1 # [win] + # The unversioned variants as well as the lib on Windows should be in the main gettext package. + - test ! -f ${PREFIX}/lib/libasprintf$SHLIB_EXT # [not win] + - if exist %PREFIX%\Library\lib\asprintf.dll.lib exit /b 1 # [win] + - if exist %PREFIX%\Library\lib\asprintf.lib exit /b 1 # [win] + about: + home: https://www.gnu.org/software/gettext + license: LGPL-2.1-or-later + license_file: COPYING + summary: C-style formatted output in C++ + + - name: libasprintf-devel + build: + run_exports: + # Seems pretty good: https://abi-laboratory.pro/tracker/timeline/gettext + - {{ pin_subpackage('libasprintf') }} + ignore_run_exports_from: + - {{ compiler('cxx') }} # [unix] + ignore_run_exports: + - libiconv + script: install-asprintf-devel.sh # [unix] + script: install-asprintf-devel.bat # [not unix] + requirements: + build: + - posix # [win] + - {{ posix }}autoconf # [win] + - {{ posix }}automake{{ am_version }} # [win] + - {{ posix }}libtool + - {{ posix }}patch # [win] + - {{ posix }}sed # [win] + - {{ native }}binutils # [win] + - {{ native }}crt-git # [win] + - {{ stdlib('c') }} # [not win] + - {{ compiler('c') }} # [not win] + - {{ compiler('cxx') }} # [not win] + - make # [unix] + host: + - libiconv {{ libiconv }} + - {{ pin_subpackage('libasprintf', exact=True) }} + run: + - {{ pin_subpackage('libasprintf', exact=True) }} + test: + commands: + - test -f ${PREFIX}/lib/libasprintf${SHLIB_EXT} # [not win] + - if not exist %PREFIX%\Library\lib\asprintf.dll.lib exit /b 1 # [win] + - if not exist %PREFIX%\Library\lib\asprintf.lib exit /b 1 # [win] + about: + home: https://www.gnu.org/software/gettext + license: LGPL-2.1-or-later + license_file: COPYING + summary: Decomposed printf argument list + + - name: libgettextpo + build: + run_exports: + # Seems pretty good: https://abi-laboratory.pro/tracker/timeline/gettext + - {{ pin_subpackage('libgettextpo') }} + ignore_run_exports_from: + - {{ compiler('cxx') }} # [unix] + script: install-libgettextpo.sh # [unix] + script: install-libgettextpo.bat # [not unix] + requirements: + build: + - posix # [win] + - {{ posix }}autoconf # [win] + - {{ posix }}automake{{ am_version }} # [win] + - {{ posix }}libtool + - {{ posix }}patch # [win] + - {{ posix }}sed # [win] + - {{ native }}binutils # [win] + - {{ native }}crt-git # [win] + - {{ stdlib('c') }} # [not win] + - {{ compiler('c') }} # [not win] + - {{ compiler('cxx') }} # [not win] + - make # [unix] + host: + - {{ pin_subpackage('libintl', exact=True) }} # [not linux] + - libiconv {{ libiconv }} + run: + - {{ pin_subpackage('libintl', exact=True) }} # [not linux] + test: + commands: + # Only the actual binary (versioned) variant should be in this package + - test -f ${PREFIX}/lib/libgettextpo.*.dylib # [osx] + - test -f ${PREFIX}/lib/libgettextpo.so.0 # [linux] + - if not exist %PREFIX%\Library\bin\gettextpo-*.dll exit /b 1 # [win] + # The unversioned variants as well as the lib on Windows should be in the main gettext package. + - test ! -f ${PREFIX}/lib/libgettextpo$SHLIB_EXT # [not win] + - if exist %PREFIX%\Library\lib\gettextpo.dll.lib exit /b 1 # [win] + - if exist %PREFIX%\Library\lib\gettextpo.lib exit /b 1 # [win] + about: + home: https://www.gnu.org/software/gettext + license: GPL-3.0-or-later + license_file: COPYING + summary: library for interfacing programmatically with GNU gettext .po files + + - name: libgettextpo-devel + build: + run_exports: + # Seems pretty good: https://abi-laboratory.pro/tracker/timeline/gettext + - {{ pin_subpackage('libgettextpo') }} + ignore_run_exports_from: + - {{ compiler('cxx') }} # [unix] + script: install-libgettextpo-devel.sh # [unix] + script: install-libgettextpo-devel.bat # [not unix] + requirements: + build: + - posix # [win] + - {{ posix }}autoconf # [win] + - {{ posix }}automake{{ am_version }} # [win] + - {{ posix }}libtool + - {{ posix }}patch # [win] + - {{ posix }}sed # [win] + - {{ native }}binutils # [win] + - {{ native }}crt-git # [win] + - {{ stdlib('c') }} # [not win] + - {{ compiler('c') }} # [not win] + - {{ compiler('cxx') }} # [not win] + - make # [unix] + host: + - {{ pin_subpackage('libintl', exact=True) }} # [not linux] + - {{ pin_subpackage('libgettextpo', exact=True) }} + - libiconv {{ libiconv }} + run: + - {{ pin_subpackage('libintl', exact=True) }} # [not linux] + - {{ pin_subpackage('libgettextpo', exact=True) }} + test: + commands: + - test -f ${PREFIX}/lib/libgettextpo$SHLIB_EXT # [not win] + - if not exist %PREFIX%\Library\lib\gettextpo.dll.lib exit /b 1 # [win] + - if not exist %PREFIX%\Library\lib\gettextpo.lib exit /b 1 # [win] + about: + home: https://www.gnu.org/software/gettext + license: GPL-3.0-or-later + license_file: COPYING + summary: library for interfacing programmatically with GNU gettext .po files + + - name: gettext-tools + script: install-gettext.sh # [unix] + script: install-gettext.bat # [not unix] + build: + ignore_run_exports_from: + - {{ compiler('cxx') }} + requirements: + build: + - posix # [win] + - {{ posix }}autoconf # [win] + - {{ posix }}automake{{ am_version }} # [win] + - {{ posix }}libtool + - {{ posix }}patch # [win] + - {{ posix }}sed # [win] + - {{ native }}binutils # [win] + - {{ native }}crt-git # [win] + - {{ stdlib('c') }} + - {{ compiler('c') }} + - {{ compiler('cxx') }} + - make # [unix] + host: + - libiconv {{ libiconv }} + - ncurses {{ ncurses }} # [not win] + - {{ pin_subpackage('libintl', exact=True) }} # [not linux] + - {{ pin_subpackage('libasprintf', exact=True ) }} + - {{ pin_subpackage('libgettextpo', exact=True ) }} + # Devel packages are included for deduplication-purposes only + - {{ pin_subpackage('libintl-devel', exact=True) }} # [not linux] + - {{ pin_subpackage('libasprintf-devel', exact=True ) }} + - {{ pin_subpackage('libgettextpo-devel', exact=True ) }} + run: + - {{ pin_subpackage('libintl', exact=True) }} # [not linux] + test: + files: + - an.po + requires: + - ncurses {{ ncurses }} # [not win] + commands: + - msgfmt.exe --help # [win] + - msgfmt.exe -o an.gmo an.po # [win] + - msgfmt -o an.gmo an.po # [not win] + about: + home: https://www.gnu.org/software/gettext + # The binaries of gettext are the GPL-3.0 licensed part. + license: GPL-3.0-or-later + license_file: COPYING + summary: Internationalization package (executable tools) + + - name: gettext + build: + # Required to make overdepending checks pass. + ignore_run_exports: + - libintl + - libasprintf + - libgettextpo + run_exports: + # Seems pretty good: https://abi-laboratory.pro/tracker/timeline/gettext + - {{ pin_subpackage('libintl') }} # [not linux] + - {{ pin_subpackage('libasprintf') }} + - {{ pin_subpackage('libgettextpo') }} + script: install-gettext.sh # [unix] + script: install-gettext.bat # [not unix] + requirements: + build: + - posix # [win] + - {{ posix }}autoconf # [win] + - {{ posix }}automake{{ am_version }} # [win] + - {{ posix }}libtool + - {{ posix }}patch # [win] + - {{ posix }}sed # [win] + - {{ native }}binutils # [win] + - {{ native }}crt-git # [win] + - {{ stdlib('c') }} # [not win] + - {{ compiler('c') }} # [not win] + - {{ compiler('cxx') }} # [not win] + - make # [unix] + host: + - libiconv {{ libiconv }} + - {{ pin_subpackage('gettext-tools', exact=True) }} + - {{ pin_subpackage('libintl-devel', exact=True) }} # [not linux] + - {{ pin_subpackage('libintl', exact=True) }} # [not linux] + - {{ pin_subpackage('libasprintf-devel', exact=True ) }} + - {{ pin_subpackage('libasprintf', exact=True ) }} + - {{ pin_subpackage('libgettextpo-devel', exact=True ) }} + - {{ pin_subpackage('libgettextpo', exact=True ) }} + run: + - {{ pin_subpackage('gettext-tools', exact=True) }} + - {{ pin_subpackage('libintl-devel', exact=True) }} # [not linux] + - {{ pin_subpackage('libintl', exact=True) }} # [not linux] + - {{ pin_subpackage('libasprintf-devel', exact=True ) }} + - {{ pin_subpackage('libasprintf', exact=True ) }} + - {{ pin_subpackage('libgettextpo-devel', exact=True ) }} + - {{ pin_subpackage('libgettextpo', exact=True ) }} + test: + commands: + # ===== gettextlib ===== + - test -f ${PREFIX}/lib/libgettextlib$SHLIB_EXT # [not win] + - test ! -f ${PREFIX}/lib/libgettextlib.a # [not win] + - if not exist %PREFIX%\Library\lib\gettextlib.dll.lib exit /b 1 # [win] + - if not exist %PREFIX%\Library\bin\gettextlib-*.dll exit /b 1 # [win] + # ===== gettextpo ===== + - test -f ${PREFIX}/lib/libgettextpo$SHLIB_EXT # [not win] + - test ! -f ${PREFIX}/lib/libgettextpo.a # [not win] + - if not exist %PREFIX%\Library\lib\gettextpo.dll.lib exit /b 1 # [win] + - if not exist %PREFIX%\Library\bin\gettextpo-*.dll exit /b 1 # [win] + # ===== gettextsrc ===== + - test -f ${PREFIX}/lib/libgettextsrc$SHLIB_EXT # [not win] + - test ! -f ${PREFIX}/lib/libgettextsrc.a # [not win] + - if not exist %PREFIX%\Library\lib\gettextsrc.dll.lib exit /b 1 # [win] + - if not exist %PREFIX%\Library\bin\gettextsrc-*.dll exit /b 1 # [win] + # ===== intl (not on linux) ===== + - test -f ${PREFIX}/lib/libintl$SHLIB_EXT # [not win and not linux] + - test ! -f ${PREFIX}/lib/libintl.a # [not win and not linux] + - if not exist %PREFIX%\Library\lib\intl.dll.lib exit /b 1 # [win] + - if not exist %PREFIX%\Library\bin\intl-*.dll exit /b 1 # [win] + about: + home: https://www.gnu.org/software/gettext + license: LGPL-2.1-or-later AND GPL-3.0-or-later + license_file: COPYING + summary: Internationalization package + +about: + home: https://www.gnu.org/software/gettext + license: LGPL-2.1-or-later AND GPL-3.0-or-later + license_file: COPYING + summary: Internationalization package + description: | + gettext utilities are a set of tools that provides a framework to help + other GNU packages produce multi-lingual messages. These tools include + a set of conventions about how programs should be written to support message + catalogs, a directory and file naming organization for the message catalogs themselves + dev_url: https://www.gnu.org/software/gettext + doc_url: https://www.gnu.org/software/gettext/manual + +extra: + feedstock-name: gettext + recipe-maintainers: + - scopatz + - ocefpaf + - pkgw + - xhochy diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/msvcpp.sh b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/msvcpp.sh new file mode 100644 index 0000000000000000000000000000000000000000..397e2e76a9dee4c89a2f4d51c8a74d7e5b8de44e --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/msvcpp.sh @@ -0,0 +1,4 @@ +#!/bin/sh +# Needed because "windres" can't handle a preprocesser whose invocation is +# more than one word. +exec cl -nologo -E -DRC_INVOKED "$@" diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/patches/0001-Mark-v-snprintf-as-available.patch b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/patches/0001-Mark-v-snprintf-as-available.patch new file mode 100644 index 0000000000000000000000000000000000000000..c956670a1931c785b1c504d4e67cb7b5c8e2cd9a --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/patches/0001-Mark-v-snprintf-as-available.patch @@ -0,0 +1,84 @@ +From 4fa8feff0af88fb3c7dd3fceb722dabe48b6dfa0 Mon Sep 17 00:00:00 2001 +From: Peter Williams +Date: Mon, 3 Sep 2018 17:28:40 -0400 +Subject: [PATCH 1/8] Mark (v)snprintf as available + +`configure` checks whether `snprintf` is available by attempting to link with +it. Windows didn't used to provide it at all. However, newer Windows does +provide it, but as an inline C implementation, so direct linking doesn't work. +For our purposes, the inline implementation is equivalent to a libc that +provides the functions, so hack our configure scripts to mark these functions +as available. +--- + configure.ac | 2 ++ + gettext-runtime/configure.ac | 2 ++ + gettext-runtime/libasprintf/configure.ac | 2 ++ + gettext-tools/configure.ac | 2 ++ + gettext-tools/examples/configure.ac | 2 ++ + 5 files changed, 10 insertions(+) + +diff --git a/configure.ac b/configure.ac +index f4e54ea..ef64e67 100644 +--- a/configure.ac ++++ b/configure.ac +@@ -22,6 +22,8 @@ AC_INIT([gettext], + [bug-gettext@gnu.org]) + AC_CONFIG_SRCDIR([gettext-tools/src/msgfmt.c]) + AC_CONFIG_AUX_DIR([build-aux]) ++ac_cv_func_snprintf=yes ++ac_cv_func_vsnprintf=yes + AM_INIT_AUTOMAKE([1.13 silent-rules parallel-tests tar-ustar]) + + dnl Override automake's tar command used for creating distributions. +diff --git a/gettext-runtime/configure.ac b/gettext-runtime/configure.ac +index 126d069..66f26fa 100644 +--- a/gettext-runtime/configure.ac ++++ b/gettext-runtime/configure.ac +@@ -22,6 +22,8 @@ AC_INIT([gettext-runtime], + [bug-gettext@gnu.org]) + AC_CONFIG_SRCDIR([intl/dcigettext.c]) + AC_CONFIG_AUX_DIR([../build-aux]) ++ac_cv_func_snprintf=yes ++ac_cv_func_vsnprintf=yes + AM_INIT_AUTOMAKE([1.11.1 silent-rules parallel-tests]) + AC_CONFIG_HEADERS([config.h]) + +diff --git a/gettext-runtime/libasprintf/configure.ac b/gettext-runtime/libasprintf/configure.ac +index 2fe76cf..31a06db 100644 +--- a/gettext-runtime/libasprintf/configure.ac ++++ b/gettext-runtime/libasprintf/configure.ac +@@ -20,6 +20,8 @@ AC_PREREQ([2.64]) + AC_INIT([libasprintf], [1.0]) + AC_CONFIG_SRCDIR([vasprintf.c]) + AC_CONFIG_AUX_DIR([../../build-aux]) ++ac_cv_func_snprintf=yes ++ac_cv_func_vsnprintf=yes + AM_INIT_AUTOMAKE([silent-rules]) + AC_CONFIG_HEADERS([config.h]) + +diff --git a/gettext-tools/configure.ac b/gettext-tools/configure.ac +index 3610ee3..6c75ccc 100644 +--- a/gettext-tools/configure.ac ++++ b/gettext-tools/configure.ac +@@ -22,6 +22,8 @@ AC_INIT([gettext-tools], + [bug-gettext@gnu.org]) + AC_CONFIG_SRCDIR([src/msgfmt.c]) + AC_CONFIG_AUX_DIR([../build-aux]) ++ac_cv_func_snprintf=yes ++ac_cv_func_vsnprintf=yes + AM_INIT_AUTOMAKE([1.11.1 silent-rules parallel-tests]) + AC_CONFIG_HEADERS([config.h]) + +diff --git a/gettext-tools/examples/configure.ac b/gettext-tools/examples/configure.ac +index 249fd14..4db994e 100644 +--- a/gettext-tools/examples/configure.ac ++++ b/gettext-tools/examples/configure.ac +@@ -22,6 +22,8 @@ AC_INIT([gettext-examples], + [bug-gettext@gnu.org]) + AC_CONFIG_SRCDIR([installpaths.in]) + AC_CONFIG_AUX_DIR([../../build-aux]) ++ac_cv_func_snprintf=yes ++ac_cv_func_vsnprintf=yes + AM_INIT_AUTOMAKE([silent-rules]) + + dnl Installation directories. diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/patches/0002-Prevent-libtool-from-worrying-about-dependent-librar.patch b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/patches/0002-Prevent-libtool-from-worrying-about-dependent-librar.patch new file mode 100644 index 0000000000000000000000000000000000000000..11fa4a51862263fe4b5370e4cc6a0d9551f8c9ef --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/patches/0002-Prevent-libtool-from-worrying-about-dependent-librar.patch @@ -0,0 +1,79 @@ +From e11f7bc727a6a3029c2f5b8f3002cd70817b2a8c Mon Sep 17 00:00:00 2001 +From: Peter Williams +Date: Mon, 3 Sep 2018 17:32:14 -0400 +Subject: [PATCH 2/8] Prevent libtool from worrying about dependent libraries + too much. + +Dependent libraries on Windows can take on a lot of names, depending on how +packagers mix and match "lib" prefixes, ".lib" vs. ".a" suffixes, and so on. +Libtool isn't great at guessing them. By hacking cache variables in the +`configure.ac` scripts, we can force it to just go ahead and pass everything +and not worry about it. +--- + configure.ac | 1 + + gettext-runtime/configure.ac | 1 + + gettext-runtime/libasprintf/configure.ac | 1 + + gettext-tools/configure.ac | 1 + + gettext-tools/examples/configure.ac | 1 + + 5 files changed, 5 insertions(+) + +diff --git a/configure.ac b/configure.ac +index ef64e67..05a7d18 100644 +--- a/configure.ac ++++ b/configure.ac +@@ -22,6 +22,7 @@ AC_INIT([gettext], + [bug-gettext@gnu.org]) + AC_CONFIG_SRCDIR([gettext-tools/src/msgfmt.c]) + AC_CONFIG_AUX_DIR([build-aux]) ++lt_cv_deplibs_check_method=pass_all + ac_cv_func_snprintf=yes + ac_cv_func_vsnprintf=yes + AM_INIT_AUTOMAKE([1.13 silent-rules parallel-tests tar-ustar]) +diff --git a/gettext-runtime/configure.ac b/gettext-runtime/configure.ac +index 66f26fa..7e914f8 100644 +--- a/gettext-runtime/configure.ac ++++ b/gettext-runtime/configure.ac +@@ -22,6 +22,7 @@ AC_INIT([gettext-runtime], + [bug-gettext@gnu.org]) + AC_CONFIG_SRCDIR([intl/dcigettext.c]) + AC_CONFIG_AUX_DIR([../build-aux]) ++lt_cv_deplibs_check_method=pass_all + ac_cv_func_snprintf=yes + ac_cv_func_vsnprintf=yes + AM_INIT_AUTOMAKE([1.11.1 silent-rules parallel-tests]) +diff --git a/gettext-runtime/libasprintf/configure.ac b/gettext-runtime/libasprintf/configure.ac +index 31a06db..3a89c61 100644 +--- a/gettext-runtime/libasprintf/configure.ac ++++ b/gettext-runtime/libasprintf/configure.ac +@@ -20,6 +20,7 @@ AC_PREREQ([2.64]) + AC_INIT([libasprintf], [1.0]) + AC_CONFIG_SRCDIR([vasprintf.c]) + AC_CONFIG_AUX_DIR([../../build-aux]) ++lt_cv_deplibs_check_method=pass_all + ac_cv_func_snprintf=yes + ac_cv_func_vsnprintf=yes + AM_INIT_AUTOMAKE([silent-rules]) +diff --git a/gettext-tools/configure.ac b/gettext-tools/configure.ac +index 6c75ccc..fa01857 100644 +--- a/gettext-tools/configure.ac ++++ b/gettext-tools/configure.ac +@@ -22,6 +22,7 @@ AC_INIT([gettext-tools], + [bug-gettext@gnu.org]) + AC_CONFIG_SRCDIR([src/msgfmt.c]) + AC_CONFIG_AUX_DIR([../build-aux]) ++lt_cv_deplibs_check_method=pass_all + ac_cv_func_snprintf=yes + ac_cv_func_vsnprintf=yes + AM_INIT_AUTOMAKE([1.11.1 silent-rules parallel-tests]) +diff --git a/gettext-tools/examples/configure.ac b/gettext-tools/examples/configure.ac +index 4db994e..6a59715 100644 +--- a/gettext-tools/examples/configure.ac ++++ b/gettext-tools/examples/configure.ac +@@ -22,6 +22,7 @@ AC_INIT([gettext-examples], + [bug-gettext@gnu.org]) + AC_CONFIG_SRCDIR([installpaths.in]) + AC_CONFIG_AUX_DIR([../../build-aux]) ++lt_cv_deplibs_check_method=pass_all + ac_cv_func_snprintf=yes + ac_cv_func_vsnprintf=yes + AM_INIT_AUTOMAKE([silent-rules]) diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/patches/0003-Fix-some-DLL-export-markings-in-libintl.patch b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/patches/0003-Fix-some-DLL-export-markings-in-libintl.patch new file mode 100644 index 0000000000000000000000000000000000000000..732eccd29ebdd82ac3252525b0e8f617d66090d2 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/patches/0003-Fix-some-DLL-export-markings-in-libintl.patch @@ -0,0 +1,110 @@ +From d7490b79ce621dc4d859c1a82712f2ffe7366593 Mon Sep 17 00:00:00 2001 +From: Peter Williams +Date: Mon, 3 Sep 2018 17:34:54 -0400 +Subject: [PATCH 3/8] Fix some DLL export markings in libintl. + +A few files had inconsistent labeling for DLL exporting, which I guess MSVC +might be pickier about than it used to be. Tidy them up. +--- + gettext-runtime/gnulib-lib/relocatable.c | 2 +- + gettext-runtime/intl/libgnuintl.in.h | 15 ++++++++++++--- + 2 files changed, 13 insertions(+), 4 deletions(-) + +diff --git a/gettext-runtime/gnulib-lib/relocatable.c b/gettext-runtime/gnulib-lib/relocatable.c +index 365c085..5f7fad6 100644 +--- a/gettext-runtime/gnulib-lib/relocatable.c ++++ b/gettext-runtime/gnulib-lib/relocatable.c +@@ -164,7 +164,7 @@ set_this_relocation_prefix (const char *orig_prefix_arg, + by the corresponding pathname with the current prefix instead. Both + prefixes should be directory names without trailing slash (i.e. use "" + instead of "/"). */ +-void ++RELOCATABLE_DLL_EXPORTED void + set_relocation_prefix (const char *orig_prefix_arg, const char *curr_prefix_arg) + { + set_this_relocation_prefix (orig_prefix_arg, curr_prefix_arg); +diff --git a/gettext-runtime/intl/libgnuintl.in.h b/gettext-runtime/intl/libgnuintl.in.h +index ae81ffe..487675d 100644 +--- a/gettext-runtime/intl/libgnuintl.in.h ++++ b/gettext-runtime/intl/libgnuintl.in.h +@@ -48,6 +48,15 @@ + # undef gettext + #endif + ++ ++#if HAVE_VISIBILITY && BUILDING_DLL ++# define DLL_EXPORTED __attribute__((__visibility__("default"))) ++#elif defined _MSC_VER && BUILDING_DLL ++# define DLL_EXPORTED __declspec(dllexport) ++#else ++# define DLL_EXPORTED ++#endif ++ + #ifdef __cplusplus + extern "C" { + #endif +@@ -1095,7 +1104,7 @@ char *setlocale (int __category, const char *__locale) + # undef setlocale + # define setlocale libintl_setlocale + # endif +-extern char *setlocale (int, const char *) ++extern DLL_EXPORTED char *setlocale (int, const char *) + _INTL_ASM (libintl_setlocale); + # if defined _INTL_REDIRECT_MACROS && defined __cplusplus && !defined _INTL_CXX_NO_CLOBBER_STD_NAMESPACE + namespace std { using ::libintl_setlocale; } +@@ -1123,7 +1132,7 @@ locale_t newlocale (int __category_mask, const char *__name, locale_t __base) + # undef newlocale + # define newlocale libintl_newlocale + # endif +-extern locale_t newlocale (int, const char *, locale_t) ++extern DLL_EXPORTED locale_t newlocale (int, const char *, locale_t) + _INTL_ASM (libintl_newlocale); + # if defined _INTL_REDIRECT_MACROS && defined __cplusplus && !defined _INTL_CXX_NO_CLOBBER_STD_NAMESPACE + namespace std { using ::libintl_newlocale; } +@@ -1144,7 +1153,7 @@ namespace std { using ::libintl_newlocale; } + prefixes should be directory names without trailing slash (i.e. use "" + instead of "/"). */ + #define libintl_set_relocation_prefix libintl_set_relocation_prefix +-extern void ++extern DLL_EXPORTED void + libintl_set_relocation_prefix (const char *orig_prefix, + const char *curr_prefix); + +diff --git a/gettext-tools/configure.ac b/gettext-tools/configure.ac +index dcbf1d7..47b0a1c 100644 +--- a/gettext-tools/configure.ac ++++ b/gettext-tools/configure.ac +@@ -392,8 +392,12 @@ AH_BOTTOM([ + the C macro DLL_EXPORT (together with PIC) when compiling for a shared + library (called DLL under Windows) and does not define it when compiling + an object file meant to be linked statically into some executable. */ +-#if (defined _WIN32 || defined __CYGWIN__) && defined DLL_EXPORT && !defined IN_RELOCWRAPPER +-# define DLL_VARIABLE __declspec (dllimport) ++#if (defined _WIN32 || defined __CYGWIN__) && !defined IN_RELOCWRAPPER ++# if defined DLL_EXPORT ++# define DLL_VARIABLE __declspec (dllexport) ++# else ++# define DLL_VARIABLE __declspec (dllimport) ++# endif + #else + # define DLL_VARIABLE + #endif +diff --git a/gettext-runtime/intl/configure.ac b/gettext-runtime/intl/configure.ac +index 749a700..a74c122 100755 +--- a/gettext-runtime/intl/configure.ac ++++ b/gettext-runtime/intl/configure.ac +@@ -235,8 +235,12 @@ AH_BOTTOM([ + the C macro DLL_EXPORT (together with PIC) when compiling for a shared + library (called DLL under Windows) and does not define it when compiling + an object file meant to be linked statically into some executable. */ +-#if (defined _MSC_VER && defined DLL_EXPORT) && !defined IN_RELOCWRAPPER +-# define DLL_VARIABLE __declspec (dllimport) ++#if defined _MSC_VER && !defined IN_RELOCWRAPPER ++# if defined DLL_EXPORT ++# define DLL_VARIABLE __declspec (dllexport) ++# else ++# define DLL_VARIABLE __declspec (dllimport) ++# endif + #else + # define DLL_VARIABLE + #endif diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/patches/0004-Fix-quoting-when-invoking-windres.patch b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/patches/0004-Fix-quoting-when-invoking-windres.patch new file mode 100644 index 0000000000000000000000000000000000000000..5318fefa1d760dd5016bad98c2693d27d67230ac --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/patches/0004-Fix-quoting-when-invoking-windres.patch @@ -0,0 +1,120 @@ +From 62972ab62dd216ef95df90187487d14bc86e5def Mon Sep 17 00:00:00 2001 +From: Peter Williams +Date: Mon, 3 Sep 2018 17:36:09 -0400 +Subject: [PATCH 4/8] Fix quoting when invoking "windres" + +Version strings were being quoted too much. I'm not sure why this wasn't a +problem elsewhere, but it's definitely a problem on Windows. +--- + gettext-runtime/intl/Makefile.am | 2 +- + gettext-runtime/libasprintf/Makefile.am | 2 +- + gettext-runtime/src/Makefile.am | 2 +- + gettext-tools/libgettextpo/Makefile.am | 2 +- + gettext-tools/src/Makefile.am | 2 +- + libtextstyle/lib/Makefile.am | 2 +- + 6 files changed, 6 insertions(+), 6 deletions(-) + +diff --git a/gettext-runtime/intl/Makefile.am b/gettext-runtime/intl/Makefile.am +index 2bed67b..ae4123e 100644 +--- a/gettext-runtime/intl/Makefile.am ++++ b/gettext-runtime/intl/Makefile.am +@@ -411,7 +411,7 @@ libintl.res.lo: $(srcdir)/libintl.rc + sed_extract_minor='/^[0-9][0-9]*[.][0-9]/{'$${nl}'s/^[0-9]*[.]\([0-9]*\).*/\1/p'$${nl}q$${nl}'}'$${nl}'c\'$${nl}0$${nl}q; \ + sed_extract_subminor='/^[0-9][0-9]*[.][0-9][0-9]*[.][0-9]/{'$${nl}'s/^[0-9]*[.][0-9]*[.]\([0-9]*\).*/\1/p'$${nl}q$${nl}'}'$${nl}'c\'$${nl}0$${nl}q; \ + $(LIBTOOL) --tag=RC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(RC) \ +- "-DPACKAGE_VERSION_STRING=\\\"$(VERSION)\\\"" \ ++ "-DPACKAGE_VERSION_STRING=\"$(VERSION)\"" \ + "-DPACKAGE_VERSION_MAJOR="`echo '$(VERSION)' | sed -n -e "$$sed_extract_major"` \ + "-DPACKAGE_VERSION_MINOR="`echo '$(VERSION)' | sed -n -e "$$sed_extract_minor"` \ + "-DPACKAGE_VERSION_SUBMINOR="`echo '$(VERSION)' | sed -n -e "$$sed_extract_subminor"` \ +diff --git a/gettext-runtime/libasprintf/Makefile.am b/gettext-runtime/libasprintf/Makefile.am +index c0eb406..4ca6b0a 100644 +--- a/gettext-runtime/libasprintf/Makefile.am ++++ b/gettext-runtime/libasprintf/Makefile.am +@@ -99,7 +99,7 @@ libasprintf.res.lo: $(srcdir)/libasprintf.rc + sed_extract_minor='/^[0-9][0-9]*[.][0-9]/{'$${nl}'s/^[0-9]*[.]\([0-9]*\).*/\1/p'$${nl}q$${nl}'}'$${nl}'c\'$${nl}0$${nl}q; \ + sed_extract_subminor='/^[0-9][0-9]*[.][0-9][0-9]*[.][0-9]/{'$${nl}'s/^[0-9]*[.][0-9]*[.]\([0-9]*\).*/\1/p'$${nl}q$${nl}'}'$${nl}'c\'$${nl}0$${nl}q; \ + $(LIBTOOL) --tag=RC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(RC) \ +- "-DPACKAGE_VERSION_STRING=\\\"$(VERSION)\\\"" \ ++ "-DPACKAGE_VERSION_STRING=\"$(VERSION)\"" \ + "-DPACKAGE_VERSION_MAJOR="`echo '$(VERSION)' | sed -n -e "$$sed_extract_major"` \ + "-DPACKAGE_VERSION_MINOR="`echo '$(VERSION)' | sed -n -e "$$sed_extract_minor"` \ + "-DPACKAGE_VERSION_SUBMINOR="`echo '$(VERSION)' | sed -n -e "$$sed_extract_subminor"` \ +diff --git a/gettext-runtime/src/Makefile.am b/gettext-runtime/src/Makefile.am +index e9974c4..9da1c7b 100644 +--- a/gettext-runtime/src/Makefile.am ++++ b/gettext-runtime/src/Makefile.am +@@ -70,7 +70,7 @@ RELOCATABLE_STRIP = : + if WOE32 + WOE32_LDADD = gettext.res + gettext.res : $(top_srcdir)/../windows/gettext.rc +- $(WINDRES) `$(SHELL) $(top_srcdir)/../windows/windres-options --escape $(VERSION)` -i $(top_srcdir)/../windows/gettext.rc -o gettext.res --output-format=coff ++ $(WINDRES) `$(SHELL) $(top_srcdir)/../windows/windres-options $(VERSION)` -i $(top_srcdir)/../windows/gettext.rc -o gettext.res --output-format=coff + MOSTLYCLEANFILES += gettext.res + else + WOE32_LDADD = +diff --git a/gettext-tools/libgettextpo/Makefile.am b/gettext-tools/libgettextpo/Makefile.am +index 5fc6708..98d65cc 100644 +--- a/gettext-tools/libgettextpo/Makefile.am ++++ b/gettext-tools/libgettextpo/Makefile.am +@@ -146,7 +146,7 @@ EXTRA_DIST += libgettextpo.rc + if WOE32 + WOE32_LIBADD = libgettextpo.res.lo + libgettextpo.res.lo : $(srcdir)/libgettextpo.rc +- $(LIBTOOL) --tag=RC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(RC) `$(SHELL) $(top_srcdir)/../windows/windres-options --escape $(VERSION)` -i $(srcdir)/libgettextpo.rc -o libgettextpo.res.lo --output-format=coff ++ $(LIBTOOL) --tag=RC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(RC) `$(SHELL) $(top_srcdir)/../windows/windres-options $(VERSION)` -i $(srcdir)/libgettextpo.rc -o libgettextpo.res.lo --output-format=coff + MOSTLYCLEANFILES += libgettextpo.res.lo + else + WOE32_LIBADD = +diff --git a/gettext-tools/src/Makefile.am b/gettext-tools/src/Makefile.am +index f77129d..0f77ee8 100644 +--- a/gettext-tools/src/Makefile.am ++++ b/gettext-tools/src/Makefile.am +@@ -756,7 +756,7 @@ RELOCATABLE_STRIP = : + if WOE32 + WOE32_LDADD = gettext.res + gettext.res : $(top_srcdir)/../windows/gettext.rc +- $(WINDRES) `$(SHELL) $(top_srcdir)/../windows/windres-options --escape $(VERSION)` -i $(top_srcdir)/../windows/gettext.rc -o gettext.res --output-format=coff ++ $(WINDRES) `$(SHELL) $(top_srcdir)/../windows/windres-options $(VERSION)` -i $(top_srcdir)/../windows/gettext.rc -o gettext.res --output-format=coff + MOSTLYCLEANFILES += gettext.res + else + WOE32_LDADD = +diff --git a/libtextstyle/lib/Makefile.am b/libtextstyle/lib/Makefile.am +index bf4b408..59810c1 100644 +--- a/libtextstyle/lib/Makefile.am ++++ b/libtextstyle/lib/Makefile.am +@@ -268,7 +268,7 @@ libtextstyle.res.lo: $(srcdir)/libtextstyle.rc + sed_extract_minor='/^[0-9][0-9]*[.][0-9]/{'$${nl}'s/^[0-9]*[.]\([0-9]*\).*/\1/p'$${nl}q$${nl}'}'$${nl}'c\'$${nl}0$${nl}q; \ + sed_extract_subminor='/^[0-9][0-9]*[.][0-9][0-9]*[.][0-9]/{'$${nl}'s/^[0-9]*[.][0-9]*[.]\([0-9]*\).*/\1/p'$${nl}q$${nl}'}'$${nl}'c\'$${nl}0$${nl}q; \ + $(LIBTOOL) --tag=RC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(RC) \ +- "-DPACKAGE_VERSION_STRING=\\\"$(VERSION)\\\"" \ ++ "-DPACKAGE_VERSION_STRING=\"$(VERSION)\"" \ + "-DPACKAGE_VERSION_MAJOR="`echo '$(VERSION)' | sed -n -e "$$sed_extract_major"` \ + "-DPACKAGE_VERSION_MINOR="`echo '$(VERSION)' | sed -n -e "$$sed_extract_minor"` \ + "-DPACKAGE_VERSION_SUBMINOR="`echo '$(VERSION)' | sed -n -e "$$sed_extract_subminor"` \ +diff --git a/gettext-tools/gnulib-lib/Makefile.am_orig b/gettext-tools/gnulib-lib/Makefile.am +index a7e7d88..7dc2e6b 100644 +--- a/gettext-tools/gnulib-lib/Makefile.am_orig ++++ b/gettext-tools/gnulib-lib/Makefile.am +@@ -76,7 +76,7 @@ libgettextlib.res.lo: $(srcdir)/libgettextlib.rc + sed_extract_minor='/^[0-9][0-9]*[.][0-9]/{'$${nl}'s/^[0-9]*[.]\([0-9]*\).*/\1/p'$${nl}q$${nl}'}'$${nl}'c\'$${nl}0$${nl}q; \ + sed_extract_subminor='/^[0-9][0-9]*[.][0-9][0-9]*[.][0-9]/{'$${nl}'s/^[0-9]*[.][0-9]*[.]\([0-9]*\).*/\1/p'$${nl}q$${nl}'}'$${nl}'c\'$${nl}0$${nl}q; \ + $(LIBTOOL) --tag=RC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(RC) \ +- "-DPACKAGE_VERSION_STRING=\\\"$(VERSION)\\\"" \ ++ "-DPACKAGE_VERSION_STRING=\"$(VERSION)\"" \ + "-DPACKAGE_VERSION_MAJOR="`echo '$(VERSION)' | sed -n -e "$$sed_extract_major"` \ + "-DPACKAGE_VERSION_MINOR="`echo '$(VERSION)' | sed -n -e "$$sed_extract_minor"` \ + "-DPACKAGE_VERSION_SUBMINOR="`echo '$(VERSION)' | sed -n -e "$$sed_extract_subminor"` \ +diff --git a/gettext-tools/src/Makefile.am b/gettext-tools/src/Makefile.am +index 607dcf0..23231cb 100644 +--- a/gettext-tools/src/Makefile.am ++++ b/gettext-tools/src/Makefile.am +@@ -372,7 +372,7 @@ libgettextsrc.res.lo: $(srcdir)/libgettextsrc.rc + sed_extract_minor='/^[0-9][0-9]*[.][0-9]/{'$${nl}'s/^[0-9]*[.]\([0-9]*\).*/\1/p'$${nl}q$${nl}'}'$${nl}'c\'$${nl}0$${nl}q; \ + sed_extract_subminor='/^[0-9][0-9]*[.][0-9][0-9]*[.][0-9]/{'$${nl}'s/^[0-9]*[.][0-9]*[.]\([0-9]*\).*/\1/p'$${nl}q$${nl}'}'$${nl}'c\'$${nl}0$${nl}q; \ + $(LIBTOOL) --tag=RC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(RC) \ +- "-DPACKAGE_VERSION_STRING=\\\"$(VERSION)\\\"" \ ++ "-DPACKAGE_VERSION_STRING=\"$(VERSION)\"" \ + "-DPACKAGE_VERSION_MAJOR="`echo '$(VERSION)' | sed -n -e "$$sed_extract_major"` \ + "-DPACKAGE_VERSION_MINOR="`echo '$(VERSION)' | sed -n -e "$$sed_extract_minor"` \ + "-DPACKAGE_VERSION_SUBMINOR="`echo '$(VERSION)' | sed -n -e "$$sed_extract_subminor"` \ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/patches/0005-CXXLD-is-not-a-thing.patch b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/patches/0005-CXXLD-is-not-a-thing.patch new file mode 100644 index 0000000000000000000000000000000000000000..0fe985162a8a225bd6c953411748c6bdd3bbcbf5 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/patches/0005-CXXLD-is-not-a-thing.patch @@ -0,0 +1,88 @@ +From 8538d082c870ef99bccb8c48acc0c40e525c07cb Mon Sep 17 00:00:00 2001 +From: Peter Williams +Date: Mon, 3 Sep 2018 17:37:12 -0400 +Subject: [PATCH 5/8] CXXLD is not a thing. + +Maybe it was at some point? But it isn't now. CCLD works fine on Windows since +CC and CXX (the C and C++ compilers) are the same thing. +--- + gettext-tools/gnulib-lib/Makefile.am | 2 +- + gettext-tools/src/Makefile.am | 22 +++++++++++----------- + 2 files changed, 12 insertions(+), 12 deletions(-) + +diff --git a/gettext-tools/gnulib-lib/Makefile.am b/gettext-tools/gnulib-lib/Makefile.am +index a7fa494..a7e7d88 100644 +--- a/gettext-tools/gnulib-lib/Makefile.am ++++ b/gettext-tools/gnulib-lib/Makefile.am +@@ -111,7 +111,7 @@ libgettextlib_la_LINK = $(LIBTOOL) $(AM_V_lt) --tag=CC \ + else + libgettextlib_la_LINK = $(LIBTOOL) $(AM_V_lt) --tag=CXX \ + $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=link \ +- $(CXXLD) $(AM_CXXFLAGS) $(CXXFLAGS) $(libgettextlib_la_LDFLAGS) $(LDFLAGS) \ ++ $(CCLD) $(AM_CXXFLAGS) $(CXXFLAGS) $(libgettextlib_la_LDFLAGS) $(LDFLAGS) \ + -o $@ + # Use the same definition of CXXLD as Automake generates in other Makefiles. + CXXLD = $(CXX) +diff --git a/gettext-tools/src/Makefile.am b/gettext-tools/src/Makefile.am +index 036ec64..607dcf0 100644 +--- a/gettext-tools/src/Makefile.am ++++ b/gettext-tools/src/Makefile.am +@@ -552,47 +552,47 @@ xgettext_LINK = $(LIBTOOL) $(AM_V_lt) --tag=CC \ + else + libgettextsrc_la_LINK = $(LIBTOOL) $(AM_V_lt) --tag=CXX \ + $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=link \ +- $(CXXLD) $(AM_CXXFLAGS) $(CXXFLAGS) $(libgettextsrc_la_LDFLAGS) $(LDFLAGS) \ ++ $(CCLD) $(AM_CXXFLAGS) $(CXXFLAGS) $(libgettextsrc_la_LDFLAGS) $(LDFLAGS) \ + -o $@ + msgattrib_LINK = $(LIBTOOL) $(AM_V_lt) --tag=CXX \ + $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=link \ +- $(CXXLD) $(AM_CXXFLAGS) $(CXXFLAGS) $(msgattrib_LDFLAGS) $(LDFLAGS) \ ++ $(CCLD) $(AM_CXXFLAGS) $(CXXFLAGS) $(msgattrib_LDFLAGS) $(LDFLAGS) \ + -o $@ + msgcat_LINK = $(LIBTOOL) $(AM_V_lt) --tag=CXX \ + $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=link \ +- $(CXXLD) $(AM_CXXFLAGS) $(CXXFLAGS) $(msgcat_LDFLAGS) $(LDFLAGS) \ ++ $(CCLD) $(AM_CXXFLAGS) $(CXXFLAGS) $(msgcat_LDFLAGS) $(LDFLAGS) \ + -o $@ + msgcomm_LINK = $(LIBTOOL) $(AM_V_lt) --tag=CXX \ + $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=link \ +- $(CXXLD) $(AM_CXXFLAGS) $(CXXFLAGS) $(msgcomm_LDFLAGS) $(LDFLAGS) \ ++ $(CCLD) $(AM_CXXFLAGS) $(CXXFLAGS) $(msgcomm_LDFLAGS) $(LDFLAGS) \ + -o $@ + msgconv_LINK = $(LIBTOOL) $(AM_V_lt) --tag=CXX \ + $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=link \ +- $(CXXLD) $(AM_CXXFLAGS) $(CXXFLAGS) $(msgconv_LDFLAGS) $(LDFLAGS) \ ++ $(CCLD) $(AM_CXXFLAGS) $(CXXFLAGS) $(msgconv_LDFLAGS) $(LDFLAGS) \ + -o $@ + msgen_LINK = $(LIBTOOL) $(AM_V_lt) --tag=CXX \ + $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=link \ +- $(CXXLD) $(AM_CXXFLAGS) $(CXXFLAGS) $(msgen_LDFLAGS) $(LDFLAGS) \ ++ $(CCLD) $(AM_CXXFLAGS) $(CXXFLAGS) $(msgen_LDFLAGS) $(LDFLAGS) \ + -o $@ + msgfilter_LINK = $(LIBTOOL) $(AM_V_lt) --tag=CXX \ + $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=link \ +- $(CXXLD) $(AM_CXXFLAGS) $(CXXFLAGS) $(msgfilter_LDFLAGS) $(LDFLAGS) \ ++ $(CCLD) $(AM_CXXFLAGS) $(CXXFLAGS) $(msgfilter_LDFLAGS) $(LDFLAGS) \ + -o $@ + msggrep_LINK = $(LIBTOOL) $(AM_V_lt) --tag=CXX \ + $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=link \ +- $(CXXLD) $(AM_CXXFLAGS) $(CXXFLAGS) $(msggrep_LDFLAGS) $(LDFLAGS) \ ++ $(CCLD) $(AM_CXXFLAGS) $(CXXFLAGS) $(msggrep_LDFLAGS) $(LDFLAGS) \ + -o $@ + msgmerge_LINK = $(LIBTOOL) $(AM_V_lt) --tag=CXX \ + $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=link \ +- $(CXXLD) $(msgmerge_CXXFLAGS) $(CXXFLAGS) $(msgmerge_LDFLAGS) $(LDFLAGS) \ ++ $(CCLD) $(msgmerge_CXXFLAGS) $(CXXFLAGS) $(msgmerge_LDFLAGS) $(LDFLAGS) \ + -o $@ + msguniq_LINK = $(LIBTOOL) $(AM_V_lt) --tag=CXX \ + $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=link \ +- $(CXXLD) $(AM_CXXFLAGS) $(CXXFLAGS) $(msguniq_LDFLAGS) $(LDFLAGS) \ ++ $(CCLD) $(AM_CXXFLAGS) $(CXXFLAGS) $(msguniq_LDFLAGS) $(LDFLAGS) \ + -o $@ + xgettext_LINK = $(LIBTOOL) $(AM_V_lt) --tag=CXX \ + $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=link \ +- $(CXXLD) $(AM_CXXFLAGS) $(CXXFLAGS) $(xgettext_LDFLAGS) $(LDFLAGS) \ ++ $(CCLD) $(AM_CXXFLAGS) $(CXXFLAGS) $(xgettext_LDFLAGS) $(LDFLAGS) \ + -o $@ + endif + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/patches/0006-Work-around-Unixisms-in-libgettextpo.patch b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/patches/0006-Work-around-Unixisms-in-libgettextpo.patch new file mode 100644 index 0000000000000000000000000000000000000000..1fae592458d921cf736ba4d89bf5d8349ceb9241 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/patches/0006-Work-around-Unixisms-in-libgettextpo.patch @@ -0,0 +1,40 @@ +From cf1eb94eb581d73c3079a71955f5d2d9a307a5ca Mon Sep 17 00:00:00 2001 +From: Peter Williams +Date: Mon, 3 Sep 2018 17:39:00 -0400 +Subject: [PATCH 6/8] Work around Unixisms in libgettextpo + +There's a complicated bit of shell magic here that relies on redirecting +program output to file descriptor #5. That seems not to work on Windows. Just +use a temporary file instead. +--- + gettext-tools/libgettextpo/Makefile.am | 6 +++--- + 1 file changed, 3 insertions(+), 3 deletions(-) + +diff --git a/gettext-tools/libgettextpo/Makefile.am b/gettext-tools/libgettextpo/Makefile.am +index 98d65cc..9cfb6ce 100644 +--- a/gettext-tools/libgettextpo/Makefile.am ++++ b/gettext-tools/libgettextpo/Makefile.am +@@ -174,7 +174,7 @@ config.h: $(BUILT_SOURCES) + echo '#endif /* GTPO_CONFIG_H */'; \ + } > config.h && \ + if test -n "$(HAVE_GLOBAL_SYMBOL_PIPE)"; then \ +- { \ ++ { rm -f CONFIG_H_LISTING.txt; \ + for f in $(libgettextpo_la_AUXSOURCES) $(libgnu_la_SOURCES) $(libgnu_la_LIBADD); do \ + case $$f in \ + *.c | *.$(OBJEXT) | *.lo ) \ +@@ -182,12 +182,12 @@ config.h: $(BUILT_SOURCES) + test -f $$sf || sf=$(srcdir)/$$sf; \ + of=`echo "$$f" | sed -e 's,^.*/,,' -e 's,\\.[^.]*$$,,'`.$(OBJEXT); \ + $(COMPILE) $(DEFS) $(GL_CFLAG_INHIBIT_WARNINGS) -c $$sf || { rm -f config.h; exit 1; }; \ +- sh ./exported.sh $$of 1>&5; \ ++ sh ./exported.sh $$of >>CONFIG_H_LISTING.txt; \ + rm -f $$of `echo "$$of" | sed -e 's,\\.$(OBJEXT)$$,.lo,'`; \ + ;; \ + esac; \ + done; \ +- } 5>&1 1>&2 \ ++ }; cat CONFIG_H_LISTING.txt \ + | sed -e 's,.* ,,' | grep -v '@' | LC_ALL=C sort | LC_ALL=C uniq \ + | sed -e 's,^obstack_free$$,__obstack_free,' \ + | sed -e 's,^\(.*\)$$,#define \1 libgettextpo_\1,' > config.h-t && \ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/patches/0007-Add-missing-extern-C-protectors.patch b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/patches/0007-Add-missing-extern-C-protectors.patch new file mode 100644 index 0000000000000000000000000000000000000000..68136ea8c5fe43f36403968dbae865e66ec028b3 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/patches/0007-Add-missing-extern-C-protectors.patch @@ -0,0 +1,40 @@ +From 7c58479500f1caf6085662ead8702cf06127deb0 Mon Sep 17 00:00:00 2001 +From: Peter Williams +Date: Mon, 3 Sep 2018 17:54:36 -0400 +Subject: [PATCH 7/8] Add missing 'extern "C"' protectors + +Various files are missing 'extern "C"' blocks around C declarations. + +The context here is that on Windows, some files are compiled as C++ code even +though they're written as pretty much straight C. The motivation seems to be +that MSVC doesn't fully support C99 or C11, specifically non-constant +initializers. But C++ allows this, so the code will come out fine if compiled +as C++. However, without proper 'extern "C"' protection, you get linkage +errors. +--- + gettext-tools/src/plural-table.h | 8 ++++++++ + +diff --git a/gettext-tools/src/plural-table.h b/gettext-tools/src/plural-table.h +index e6c52bb..d736ef0 100644 +--- a/gettext-tools/src/plural-table.h ++++ b/gettext-tools/src/plural-table.h +@@ -20,6 +20,10 @@ + + #include + ++#ifdef __cplusplus ++extern "C" { ++#endif ++ + struct plural_table_entry + { + const char *lang; +@@ -30,4 +34,8 @@ struct plural_table_entry + extern DLL_VARIABLE struct plural_table_entry plural_table[]; + extern DLL_VARIABLE const size_t plural_table_size; + ++#ifdef __cplusplus ++} ++#endif ++ + #endif /* _PLURAL_TABLE_H */ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/patches/0008-Declaration-ordering.patch b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/patches/0008-Declaration-ordering.patch new file mode 100644 index 0000000000000000000000000000000000000000..284901d912736be394ca5a676ce19ef206839758 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/recipe/parent/patches/0008-Declaration-ordering.patch @@ -0,0 +1,21 @@ +In gettext-tools, both `libgrep` and `gnulib-lib` provide their own versions of +headers like `stdlib.h`, but the two variants aren't the same. Some of the tools +want to use `unsetenv()` as provided by gnulib-lib, but the default include flag +ordering puts libgrep first, which doesn't define it. This is all pretty messy +but the most expedient thing is to reorder the includes to get the gnulib-lib +version first. + +diff --git a/gettext-tools/src/Makefile.am b/gettext-tools/src/Makefile.am +index 607dcf0..c641919 100644 +--- a/gettext-tools/src/Makefile.am ++++ b/gettext-tools/src/Makefile.am +@@ -109,8 +109,8 @@ schemadir = $(pkgdatadir)/schema + # The option -I$(top_srcdir) is needed so that woe32dll/export.h is found. + AM_CPPFLAGS = \ + -I$(top_srcdir) \ +- -I../libgrep -I$(top_srcdir)/libgrep \ + -I../gnulib-lib -I$(top_srcdir)/gnulib-lib \ ++ -I../libgrep -I$(top_srcdir)/libgrep \ + -I../../gettext-runtime/intl -I$(top_srcdir)/../gettext-runtime/intl + DEFS = \ + -DLOCALEDIR=$(localedir_c_make) \ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/repodata_record.json b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/repodata_record.json new file mode 100644 index 0000000000000000000000000000000000000000..e8ee9856dfc58c93e4e29966f0148acf9a27233c --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/repodata_record.json @@ -0,0 +1,24 @@ +{ + "arch": "x86_64", + "build": "h6a67909_0", + "build_number": 0, + "channel": "https://repo.anaconda.com/pkgs/main/linux-64/", + "constrains": [], + "depends": [ + "__glibc >=2.28,<3.0.a0", + "libgcc >=14", + "libiconv >=1.18,<2.0a0", + "ncurses >=6.5,<7.0a0" + ], + "fn": "gettext-tools-0.25.1-h6a67909_0.conda", + "license": "GPL-3.0-or-later", + "md5": "ac944526cc2d27ffa3c44a42cd86f46d", + "name": "gettext-tools", + "platform": "linux", + "sha256": "040af24b30b7928def70ffc1fb0deb502156796993a26d95aeb3df90b92b755c", + "size": 3777431, + "subdir": "linux-64", + "timestamp": 1772045279000, + "url": "https://repo.anaconda.com/pkgs/main/linux-64/gettext-tools-0.25.1-h6a67909_0.conda", + "version": "0.25.1" +} \ No newline at end of file diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/test/an.po b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/test/an.po new file mode 100644 index 0000000000000000000000000000000000000000..ea2051bf913a94d6b2839d2cf5bba8a6d9acce56 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/test/an.po @@ -0,0 +1,145 @@ +# Aragonese translation for glib-networking. +# Copyright (C) 2013 glib-networking's COPYRIGHT HOLDER +# This file is distributed under the same license as the glib-networking package. +# FIRST AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: glib-networking master\n" +"Report-Msgid-Bugs-To: http://bugzilla.gnome.org/enter_bug.cgi?product=glib&keywords=I18N+L10N&component=network\n" +"POT-Creation-Date: 2013-02-19 13:01+0000\n" +"PO-Revision-Date: 2013-02-20 01:19+0100\n" +"Last-Translator: Daniel Martinez \n" +"Language-Team: Aragonese \n" +"Language: an\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../proxy/libproxy/glibproxyresolver.c:150 +msgid "Proxy resolver internal error." +msgstr "Error interna d'o proxy." + +#: ../tls/gnutls/gtlscertificate-gnutls.c:173 +#, c-format +msgid "Could not parse DER certificate: %s" +msgstr "No se podió analisar o certificau DER: %s" + +#: ../tls/gnutls/gtlscertificate-gnutls.c:194 +#, c-format +msgid "Could not parse PEM certificate: %s" +msgstr "No se podió analisar o certificau PEM: %s" + +#: ../tls/gnutls/gtlscertificate-gnutls.c:225 +#, c-format +msgid "Could not parse DER private key: %s" +msgstr "No se podió analisar a clau privada DER: %s" + +#: ../tls/gnutls/gtlscertificate-gnutls.c:256 +#, c-format +msgid "Could not parse PEM private key: %s" +msgstr "No se podió analisar a clau privada PEM: %s" + +#: ../tls/gnutls/gtlscertificate-gnutls.c:296 +msgid "No certificate data provided" +msgstr "No s'han proporcionau datos d'o certificau" + +#: ../tls/gnutls/gtlsclientconnection-gnutls.c:309 +msgid "Server required TLS certificate" +msgstr "O servidor requiere un certificau TLS" + +#: ../tls/gnutls/gtlsconnection-gnutls.c:258 +#, c-format +msgid "Could not create TLS connection: %s" +msgstr "No se podió creyar a connexión TLS: %s" + +#: ../tls/gnutls/gtlsconnection-gnutls.c:520 +msgid "Connection is closed" +msgstr "A connexión ye zarrada" + +#: ../tls/gnutls/gtlsconnection-gnutls.c:582 +#: ../tls/gnutls/gtlsconnection-gnutls.c:1419 +msgid "Operation would block" +msgstr "A operación se blocará" + +#: ../tls/gnutls/gtlsconnection-gnutls.c:712 +msgid "Peer failed to perform TLS handshake" +msgstr "O par falló en realizar a negociación TLS" + +#: ../tls/gnutls/gtlsconnection-gnutls.c:729 +msgid "Peer requested illegal TLS rehandshake" +msgstr "O par solicitó una renegociación TLS ilegal" + +#: ../tls/gnutls/gtlsconnection-gnutls.c:755 +msgid "TLS connection closed unexpectedly" +msgstr "A connexión TLS se zarró inasperadament" + +#: ../tls/gnutls/gtlsconnection-gnutls.c:765 +msgid "TLS connection peer did not send a certificate" +msgstr "O par d'a connexión TLS no ninvió un certificau" + +#: ../tls/gnutls/gtlsconnection-gnutls.c:1146 +#: ../tls/gnutls/gtlsconnection-gnutls.c:1165 +#, c-format +msgid "Error performing TLS handshake: %s" +msgstr "Error en realizar a negociación TLS: %s" + +#: ../tls/gnutls/gtlsconnection-gnutls.c:1175 +msgid "Server did not return a valid TLS certificate" +msgstr "O servidor no devolvió un certificau TLS valido" + +#: ../tls/gnutls/gtlsconnection-gnutls.c:1250 +msgid "Unacceptable TLS certificate" +msgstr "Certificau TLS inacceptable" + +#: ../tls/gnutls/gtlsconnection-gnutls.c:1442 +#, c-format +msgid "Error reading data from TLS socket: %s" +msgstr "Error en leyer datos d'o socket TLS: %s" + +#: ../tls/gnutls/gtlsconnection-gnutls.c:1471 +#, c-format +msgid "Error writing data to TLS socket: %s" +msgstr "Error en escribir datos en o socket TLS: %s" + +#: ../tls/gnutls/gtlsconnection-gnutls.c:1515 +msgid "Connection is already closed" +msgstr "A connexión ya ye zarrada" + +#: ../tls/gnutls/gtlsconnection-gnutls.c:1525 +#, c-format +msgid "Error performing TLS close: %s" +msgstr "Error en zarrar o TLS: %s" + +#: ../tls/gnutls/gtlsserverconnection-gnutls.c:103 +msgid "Certificate has no private key" +msgstr "O certificau no tiene clau privada" + +#: ../tls/pkcs11/gpkcs11pin.c:108 +msgid "This is the last chance to enter the PIN correctly before the token is locked." +msgstr "Ista ye a zaguera oportunidat ta introducir o PIN correctament antes que se bloque o \"token\"." + +#: ../tls/pkcs11/gpkcs11pin.c:110 +msgid "Several PIN attempts have been incorrect, and the token will be locked after further failures." +msgstr "Quantos intentos d'introducir o PIN han estau incorrectos y o \"token\" se blocará dimpués de mas fallos." + +#: ../tls/pkcs11/gpkcs11pin.c:112 +msgid "The PIN entered is incorrect." +msgstr "O PIN introduciu ye incorrecto." + +#: ../tls/pkcs11/gpkcs11slot.c:446 +msgid "Module" +msgstr "Modulo" + +#: ../tls/pkcs11/gpkcs11slot.c:447 +msgid "PKCS#11 Module Pointer" +msgstr "Puntero d'o modulo PKCS#11" + +#: ../tls/pkcs11/gpkcs11slot.c:454 +msgid "Slot ID" +msgstr "ID d'a ranura" + +#: ../tls/pkcs11/gpkcs11slot.c:455 +msgid "PKCS#11 Slot Identifier" +msgstr "Identificador d'a ranura de PKCS#11" + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/test/run_test.sh b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/test/run_test.sh new file mode 100644 index 0000000000000000000000000000000000000000..8ff276b272672babbfc8f8dac84560f3855cfabb --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/test/run_test.sh @@ -0,0 +1,8 @@ + + +set -ex + + + +msgfmt -o an.gmo an.po +exit 0 diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/test/test_time_dependencies.json b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/test/test_time_dependencies.json new file mode 100644 index 0000000000000000000000000000000000000000..810d0fccf9a0aa6d04208cc9af02d75b35555491 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/info/test/test_time_dependencies.json @@ -0,0 +1 @@ +["ncurses 6.*"] \ No newline at end of file diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/lib/preloadable_libintl.so b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/lib/preloadable_libintl.so new file mode 100644 index 0000000000000000000000000000000000000000..d4e00b6041fe3f93ac7fa32d3906b23dc3b431cf Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/lib/preloadable_libintl.so differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/libexec/gettext/cldr-plurals b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/libexec/gettext/cldr-plurals new file mode 100644 index 0000000000000000000000000000000000000000..41a34db34d4a0df9286c677141630b67e33c4cb5 Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/libexec/gettext/cldr-plurals differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/libexec/gettext/hostname b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/libexec/gettext/hostname new file mode 100644 index 0000000000000000000000000000000000000000..3ef30754eb3decadc1ed8f9446081c4b6594c823 Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/libexec/gettext/hostname differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/libexec/gettext/project-id b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/libexec/gettext/project-id new file mode 100644 index 0000000000000000000000000000000000000000..e20bf11c45d63d3a8ce69caa1cad65baa404e9e6 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/libexec/gettext/project-id @@ -0,0 +1,86 @@ +#!/bin/sh +# Prints a package's identification PACKAGE VERSION or PACKAGE. +# +# Copyright (C) 2001-2003, 2005, 2014 Free Software Foundation, Inc. +# +# 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 . + +want_version="$1" + +# NLS nuisances: Letter ranges are different in the Estonian locale. +LC_ALL=C + +while true; do + if test -f configure; then + package=`(grep '^PACKAGE_NAME=' configure; grep '^ *PACKAGE=' configure) | grep -v '=[ ]*$' | sed -e '1q' | sed -e 's/^[^=]*=//' | sed -e "s/^'//" -e "s/'$//"` + case "$package" in + *[\"\$\`\{\}]*) + # Some packages (gcal) retrieve the package name dynamically. + package= + ;; + esac + if test -n "$package"; then + is_gnu=`LC_ALL=C grep "GNU $package" * 2>/dev/null | grep -v '^libtool:'` + if test -n "$is_gnu"; then + package="GNU $package" + fi + if test -n "$want_version"; then + version=`(grep '^PACKAGE_VERSION=' configure; grep '^ *VERSION=' configure) | grep -v '=[ ]*$' | sed -e '1q' | sed -e 's/^[^=]*=//' | sed -e "s/^'//" -e "s/'$//"` + case "$version" in + *[\"\$\`\{\}]*) + # Some packages (gcal, gcc, clisp) retrieve the version dynamically. + version= + ;; + esac + if test -n "$version"; then + echo "$package $version" + else + echo "$package" + fi + else + echo "$package" + fi + exit 0 + fi + fi + dir=`basename "\`pwd\`"` + case "$dir" in + i18n) + # This directory name, used in GNU make, is not the top level directory. + ;; + *[A-Za-z]*[0-9]*) + package=`echo "$dir" | sed -e 's/^\([^0-9]*\)[0-9].*$/\1/' -e 's/[-_]$//'` + if test -n "$want_version"; then + version=`echo "$dir" | sed -e 's/^[^0-9]*\([0-9].*\)$/\1/'` + echo "$package $version" + else + echo "$package" + fi + exit 0 + ;; + esac + # Go to parent directory + last=`/bin/pwd` + cd .. + curr=`/bin/pwd` + if test "$last" = "$curr"; then + # Oops, didn't find the package name. + if test -n "$want_version"; then + echo "PACKAGE VERSION" + else + echo "PACKAGE" + fi + exit 0 + fi +done diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/libexec/gettext/urlget b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/libexec/gettext/urlget new file mode 100644 index 0000000000000000000000000000000000000000..bf1ca53d53938750eb62c24ddbe758637963232a Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/libexec/gettext/urlget differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/libexec/gettext/user-email b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/libexec/gettext/user-email new file mode 100644 index 0000000000000000000000000000000000000000..aa1314e20b19965e9e6f4d9d2a9ea00b5f83d14b --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/libexec/gettext/user-email @@ -0,0 +1,435 @@ +#!/bin/sh +# Prints the user's email address, with confirmation from the user. +# +# Copyright (C) 2001-2003, 2005, 2013, 2023 Free Software Foundation, Inc. +# +# 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 . + +# Prerequisites for using ${exec_prefix}/libexec and ${datarootdir}/locale. +prefix="/home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho" +exec_prefix="${prefix}" +datarootdir="${prefix}/share" +datadir="${datarootdir}" +# Set variables libexecdir, localedir. +libexecdir="${exec_prefix}/libexec" +localedir="${datarootdir}/locale" + +# Support for relocatability. +if test "no" = yes; then + orig_installdir="$libexecdir"/gettext # see Makefile.am's install rule + # Determine curr_installdir without caring for symlinked callers. + curr_installdir=`echo "$0" | sed -e 's,/[^/]*$,,'` + curr_installdir=`cd "$curr_installdir" && pwd` + # Compute the original/current installation prefixes by stripping the + # trailing directories off the original/current installation directories. + while true; do + orig_last=`echo "$orig_installdir" | sed -n -e 's,^.*/\([^/]*\)$,\1,p'` + curr_last=`echo "$curr_installdir" | sed -n -e 's,^.*/\([^/]*\)$,\1,p'` + if test -z "$orig_last" || test -z "$curr_last"; then + break + fi + if test "$orig_last" != "$curr_last"; then + break + fi + orig_installdir=`echo "$orig_installdir" | sed -e 's,/[^/]*$,,'` + curr_installdir=`echo "$curr_installdir" | sed -e 's,/[^/]*$,,'` + done + # Now relocate the directory variables that we use. + libexecdir=`echo "$libexecdir/" | sed -e "s%^${orig_installdir}/%${curr_installdir}/%" | sed -e 's,/$,,'` + localedir=`echo "$localedir/" | sed -e "s%^${orig_installdir}/%${curr_installdir}/%" | sed -e 's,/$,,'` +fi + +# Internationalization. +. gettext.sh +TEXTDOMAIN=gettext-tools +export TEXTDOMAIN +TEXTDOMAINDIR="$localedir" +export TEXTDOMAINDIR + +# Redirect fileno 3 to interactive I/O. +exec 3>/dev/tty + +# Output a prompt. +if test $# != 0; then + echo "$1" 1>&3 +fi + +# Find the user name on the local machine. +user=`id -u -n 2>/dev/null` +if test -z "$user"; then + user="$USER" + if test -z "$user"; then + user="$LOGNAME" + if test -z "$user"; then + user=unknown + fi + fi +fi + +# Find the hostname. +# hostname on some systems (SVR3.2, old Linux) returns a bogus exit status, +# so uname gets run too, so we keep only the first line of output. +#host=`(hostname || uname -n) 2>/dev/null | sed 1q` +host=`"$libexecdir"/gettext/hostname --short 2>/dev/null | sed 1q` + +# Find the hostname. +hostfqdn=`"$libexecdir"/gettext/hostname --fqdn 2>/dev/null | sed 1q` + +# Find a list of email addresses from various mailer configuration files. +# All mailers use configuration files under $HOME. We handle them in a +# last-modified - first-priority order. +cd $HOME +files="" + +# ----------------------- BEGIN MAILER SPECIFIC CODE ----------------------- + +# Mozilla Thunderbird addresses +files="$files .thunderbird/*/prefs.js" + +# Mozilla addresses +files="$files .mozilla/*/prefs.js" + +# Netscape 4 addresses +files="$files .netscape/liprefs.js .netscape/preferences.js" + +# Netscape 3 addresses +files="$files .netscape/preferences" + +# Emacs/XEmacs rmail, Emacs/XEmacs gnus, XEmacs vm addresses +# XEmacs mew addresses +files="$files .emacs .emacs.el" + +# KDE2 addresses +files="$files .kde2/share/config/emaildefaults" + +# KDE kmail addresses +files="$files .kde2/share/config/kmailrc" + +# GNOME evolution 2 addresses +files="$files .gconf/apps/evolution/mail/%gconf.xml" + +# GNOME evolution 1 addresses +files="$files evolution/config.xmldb" + +# GNOME balsa addresses +files="$files .gnome/balsa" + +# StarOffice and OpenOffice addresses +sed_dos2unix='s/\r$//' +sed_soffice51='s,StarOffice 5\.1=\(.*\)$,\1/sofficerc,p' +sed_soffice52='s,StarOffice 5\.2=\(.*\)$,\1/user/sofficerc,p' +sed_ooffice='s,^OpenOffice[^=]*=\(.*\)$,\1/user/config/registry/instance/org/openoffice/UserProfile.xml,p' +files="$files Office51/sofficerc Office52/user/sofficerc "`sed -n -e "$sed_dos2unix" -e "$sed_soffice51" -e "$sed_soffice52" -e "$sed_ooffice" .sversionrc 2>/dev/null | sed -e 's,^file://*,/,'` + +# mutt addresses +files="$files .muttrc" + +# pine addresses +files="$files .pinerc" + +# xfmail addresses +files="$files .xfmail/.xfmailrc" + +# tkrat addresses +files="$files .ratatosk/ratatoskrc" + +# ----------------------- END MAILER SPECIFIC CODE ----------------------- + +# Expand wildcards and remove nonexistent files from the list. +nfiles="" +for file in $files; do + if test -r "$file" && test ! -d "$file"; then + nfiles="$nfiles $file" + fi +done +files="$nfiles" + +addresses="" + +if test -n "$files"; then + + for file in `ls -t $files`; do + + case "$file" in + +# ----------------------- BEGIN MAILER SPECIFIC CODE ----------------------- + + # Mozilla and Mozilla Thunderbird addresses + .mozilla/*/prefs.js | .thunderbird/*/prefs.js) + addresses="$addresses "`grep -h '^user_pref("mail\.identity\..*\.useremail", ".*");$' $file 2>/dev/null | sed -e 's/^user_pref("mail\.identity\..*\.useremail", "\(.*\)");$/\1/'` + ;; + + # Netscape 4 addresses + .netscape/liprefs.js | .netscape/preferences.js) + addresses="$addresses "`grep -h '^user_pref("mail\.identity\.useremail", ".*");$' $file 2>/dev/null | sed -e 's/^user_pref("mail\.identity\.useremail", "\(.*\)");$/\1/'` + ;; + + # Netscape 3 addresses + .netscape/preferences) + addresses="$addresses "`grep -h '^EMAIL_ADDRESS:' $file 2>/dev/null | sed -e 's/^EMAIL_ADDRESS:[ ]*//'` + ;; + + .emacs | .emacs.el) + # Emacs/XEmacs rmail, Emacs/XEmacs gnus, XEmacs vm addresses + addresses="$addresses "`grep -h '[ (]user-mail-address "[^"]*"' $file 2>/dev/null | sed -e 's/^.*[ (]user-mail-address "\([^"]*\)".*$/\1/'` + # XEmacs mew addresses + domains=`grep -h '[ (]mew-mail-domain "[^"]*"' $file 2>/dev/null | sed -e 's/^.*[ (]mew-mail-domain "\([^"]*\)".*$/\1/'` + if test -n "$domains"; then + for domain in $domains; do + addresses="$addresses ${user}@$domain" + done + fi + ;; + + # KDE2 addresses + .kde2/share/config/emaildefaults) + addresses="$addresses "`grep -h '^EmailAddress=' $file 2>/dev/null | sed -e 's/^EmailAddress=//'` + ;; + + # KDE kmail addresses + .kde2/share/config/kmailrc) + addresses="$addresses "`grep -h '^Email Address=' $file 2>/dev/null | sed -e 's/^Email Address=//'` + ;; + + # GNOME evolution 2 addresses + .gconf/apps/evolution/mail/%gconf.xml) + sedexpr0='s,^.*<addr-spec>\(.*\)</addr-spec>.*$,\1,p' + addresses="$addresses "`sed -n -e "$sedexpr0" < $file` + ;; + + # GNOME evolution 1 addresses + evolution/config.xmldb) + sedexpr0='s/^.*\(.*\).*$,\1,p' $file 2>/dev/null` + ;; + + # StarOffice addresses + # Not a typo. They really write "Adress" with a single d. + # German orthography... + */sofficerc) + addresses="$addresses "`grep -h '^User-Adress=' $file 2>/dev/null | sed -e 's/#[^#]*$//' -e 's/^.*#//'` + ;; + + # mutt addresses + .muttrc) + mutt_addresses=`grep -h '^set from="[^"]*"[ ]*$' $file 2>/dev/null | sed -e 's/^set from="\([^"]*\)"[ ]*$/\1/'` + if test -n "$mutt_addresses"; then + addresses="$addresses $mutt_addresses" + else + # mutt uses $EMAIL as fallback. + if test -n "$EMAIL"; then + addresses="$addresses $EMAIL" + fi + fi + ;; + + # pine addresses + .pinerc) + domains=`grep -h '^user-domain=' $file 2>/dev/null | sed -e 's/^user-domain=//'` + if test -n "$domains"; then + for domain in $domains; do + addresses="$addresses ${user}@$domain" + done + else + # The use-only-domain-name option is only used if the user-domain option is not present. + domains=`grep -h '^use-only-domain-name=' $file 2>/dev/null | sed -e 's/^use-only-domain-name=//'` + if test "Yes" = "$domains"; then + addresses="$addresses ${user}@"`echo "$hostfqdn" | sed -e 's/^[^.]*\.//'` + fi + fi + ;; + + # xfmail addresses + .xfmail/.xfmailrc) + addresses="$addresses "`grep -h '^from=.*<.*>' $file 2>/dev/null | sed -e 's/^.*<\([^<>]*\)>.*$/\1/'` + ;; + + # tkrat addresses + .ratatosk/ratatoskrc) + domains=`grep -h '^set option(masquerade_as) ' $file 2>/dev/null | sed -e 's/^set option(masquerade_as) //'` + if test -n "$domains"; then + for domain in $domains; do + addresses="$addresses ${user}@$domain" + done + else + # The domain option is used only if the masquerade_as option is not present. + domains=`grep -h '^set option(domain) ' $file 2>/dev/null | sed -e 's/^set option(domain) //'` + if test -n "$domains"; then + for domain in $domains; do + addresses="$addresses ${user}@${host}.$domain" + done + fi + fi + ;; + +# ----------------------- END MAILER SPECIFIC CODE ----------------------- + + esac + + done + +fi + +# Some Debian systems have a file /etc/mailname. +if test -r /etc/mailname; then + hostmailname=`cat /etc/mailname` + if test -n "$hostmailname"; then + addresses="$addresses ${user}@$hostmailname" + fi +fi + +# SuSE Linux >= 8.0 systems have a file /etc/sysconfig/mail. +if test -r /etc/sysconfig/mail; then + hostmailname=`. /etc/sysconfig/mail && echo "$FROM_HEADER"` + if test -n "$hostmailname"; then + addresses="$addresses ${user}@$hostmailname" + fi +fi + +# elm has no user-defined addresses. +# mailx has no user-defined addresses. +# mh has no user-defined addresses. +# They use the system default. +addresses="$addresses ${user}@$hostfqdn" + +# Normalize addresses: remove addresses without @, lowercase the part after @, +# and remove duplicates. +lowercase_sed='{ +h +s/^[^@]*@\(.*\)$/\1/ +y/ABCDEFGHIJKLMNOPQRSTUVWXYZ/abcdefghijklmnopqrstuvwxyz/ +x +s/^\([^@]*\)@.*/\1@/ +G +s/\n// +p +}' +naddresses="" +for addr in $addresses; do + case "$addr" in + "<"*">") addr=`echo "$addr" | sed -e 's/^$//'` ;; + esac + case "$addr" in + *@*) + addr=`echo "$addr" | sed -n -e "$lowercase_sed"` + case " $naddresses " in + *" $addr "*) ;; + *) naddresses="$naddresses $addr" ;; + esac + ;; + esac +done +addresses="$naddresses" + +# Now it's time to ask the user. +case "$addresses" in + " "*" "*) + # At least two addresses. + lines="" + i=0 + for addr in $addresses; do + i=`expr $i + 1` + lines="${lines}${i} ${addr} +" + done + while true; do + { gettext "Which is your email address?"; echo; } 1>&3 + echo "$lines" 1>&3 + { gettext "Please choose the number, or enter your email address."; echo; } 1>&3 + read answer < /dev/tty + case "$answer" in + *@*) ;; + [0-9]*) + i=0 + for addr in $addresses; do + i=`expr $i + 1` + if test "$i" = "$answer"; then + break 2 + fi + done + ;; + esac + case "$answer" in + "<"*">") answer=`echo "$answer" | sed -e 's/^$//'` ;; + esac + case "$answer" in + *" "*) { gettext "Invalid email address: invalid character."; echo; echo; } 1>&3 ; continue ;; + *@*.*) ;; + *@*) { gettext "Invalid email address: need a fully qualified host name or domain name."; echo; echo; } 1>&3 ; continue ;; + *) { gettext "Invalid email address: missing @"; echo; echo; } 1>&3 ; continue ;; + esac + addr=`echo "$answer" | sed -n -e "$lowercase_sed"` + break + done + ;; + " "*) + # One address. + while true; do + { gettext "Is the following your email address?"; echo; } 1>&3 + echo " $addresses" 1>&3 + { gettext "Please confirm by pressing Return, or enter your email address."; echo; } 1>&3 + read answer < /dev/tty + if test -z "$answer"; then + addr=`echo "$addresses" | sed -e 's/^ //'` + break + fi + case "$answer" in + "<"*">") answer=`echo "$answer" | sed -e 's/^$//'` ;; + esac + case "$answer" in + *" "*) { gettext "Invalid email address: invalid character."; echo; echo; } 1>&3 ; continue ;; + *@*.*) ;; + *@*) { gettext "Invalid email address: need a fully qualified host name or domain name."; echo; echo; } 1>&3 ; continue ;; + *) { gettext "Invalid email address: missing @"; echo; echo; } 1>&3 ; continue ;; + esac + addr=`echo "$answer" | sed -n -e "$lowercase_sed"` + break + done + ;; + "") + # No address. + { gettext "Couldn't find out about your email address."; echo; } 1>&3 + while true; do + { gettext "Please enter your email address."; echo; } 1>&3 + read answer < /dev/tty + case "$answer" in + "<"*">") answer=`echo "$answer" | sed -e 's/^$//'` ;; + esac + case "$answer" in + *" "*) { gettext "Invalid email address: invalid character."; echo; echo; } 1>&3 ; continue ;; + *@*.*) ;; + *@*) { gettext "Invalid email address: need a fully qualified host name or domain name."; echo; echo; } 1>&3 ; continue ;; + *) { gettext "Invalid email address: missing @"; echo; echo; } 1>&3 ; continue ;; + esac + addr=`echo "$answer" | sed -n -e "$lowercase_sed"` + break + done + ;; + *) echo "internal error" 1>&3 ; exit 1 ;; +esac + +# Print to standard output. +echo "$addr" diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/aclocal/nls.m4 b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/aclocal/nls.m4 new file mode 100644 index 0000000000000000000000000000000000000000..c4601415bb5589537a6e2e8816e5383536ca6e4c --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/aclocal/nls.m4 @@ -0,0 +1,33 @@ +# nls.m4 +# serial 6 (gettext-0.24) +dnl Copyright (C) 1995-2025 Free Software Foundation, Inc. +dnl This file is free software; the Free Software Foundation +dnl gives unlimited permission to copy and/or distribute it, +dnl with or without modifications, as long as this notice is preserved. +dnl This file is offered as-is, without any warranty. +dnl +dnl This file can be used in projects which are not available under +dnl the GNU General Public License or the GNU Lesser General Public +dnl License but which still want to provide support for the GNU gettext +dnl functionality. +dnl Please note that the actual code of the GNU gettext library is covered +dnl by the GNU Lesser General Public License, and the rest of the GNU +dnl gettext package is covered by the GNU General Public License. +dnl They are *not* in the public domain. + +dnl Authors: +dnl Ulrich Drepper , 1995-2000. +dnl Bruno Haible , 2000-2003. + +AC_PREREQ([2.50]) + +AC_DEFUN([AM_NLS], +[ + AC_MSG_CHECKING([whether NLS is requested]) + dnl Default is enabled NLS + AC_ARG_ENABLE([nls], + [ --disable-nls do not use Native Language Support], + USE_NLS=$enableval, USE_NLS=yes) + AC_MSG_RESULT([$USE_NLS]) + AC_SUBST([USE_NLS]) +]) diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/FAQ.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/FAQ.html new file mode 100644 index 0000000000000000000000000000000000000000..387db959a7a53c27847c2d8ec2c7f30e4050ab93 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/FAQ.html @@ -0,0 +1,864 @@ + + + + + + GNU gettext FAQ + + +

Frequently Asked Questions
+for GNU gettext +

+

Questions

+

General

+ +

Problems building GNU gettext

+ +

Problems integrating GNU gettext

+ +

GNU gettext on Windows

+ +

Other

+ +

Answers

+

General

+

Where is the mailing list?

+Three mailing lists are available:
+
    +
  • bug-gettext@gnu.org
    +This mailing list is for discussion of features and bugs of the GNU +gettext software, including +libintl, the gettext-tools, and its autoconf macros. The archive and subscription instructions can be found at the information page.
    • +
  • translation-i18n@lists.sourceforge.net
    +This mailing list is for methodology questions around +internationalization, and for discussions of translator tools, +including but not limited to GNU gettext.
    • +
  • coordinator@translationproject.org
    +This is the email address of the Translation Project, +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: l10n.kde.org and GNOME Translation Project.
    +
    • +
+The bug-gettext list +is archived here. +You may occasionally also see +bug-gnu-gettext; this is an alias +of bug-gettext.
+

Where is the newest gettext source?

+The newest gettext release is available on ftp.gnu.org and its mirrors, in +https://ftp.gnu.org/gnu/gettext/.
+
+Prereleases are announced on the autotools-announce mailing list. +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.
+
+If you want to live on the bleeding edge, you can also use the +development sources. Instructions for retrieving the gettext CVS are +found here. +Note that building from CVS requires special tools (autoconf, automake, +m4, groff, bison, etc.) and requires that you pay attention to the README-alpha and autogen.sh files in the CVS.
+

I want to be notified of new gettext +releases.

+If you are interested in stable gettext releases, you can follow the info-gnu mailing list. It +is also available as a newsgroup gmane.org.fsf.announce +through gmane.org.
+
+You can also periodically check the download location.
+
+If you are interested in testing prereleases as well, you can subscribe +to the autotools-announce mailing +list.
+

Problems building GNU gettext

+

On Solaris, I get a +build error “text relocations remain” in the libasprintf subdirectory

+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 --disable-libasprintf.
+

“make install” fails

+“make install DESTDIR=/some/tempdir” can fail with +an error message relating to libgettextlib +or libgettextsrc, or can +silently fail to install libgettextsrc. +On some platforms, this is due to limitations of libtool regarding DESTDIR. 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, DESTDIR 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 “make install” before “make install DESTDIR=/some/tempdir”). On other +systems, when  DESTDIR +does not work, you can still do “make +install” and copy the installed files to /some/tempdir +afterwards.
+
+If “make install” without DESTDIR fails, it's a bug which +you are welcome to report to the usual bug report address. +

Problems integrating GNU gettext

+

How do I make use of gettext() in my package?

+It's not as difficult as it sounds. Here's the recipe for C or C++ +based packages.
+
    +
  • Add an invocation of AM_GNU_GETTEXT([external]) +to the package's configure.{ac,in} +file.
    • +
  • Invoke “gettextize --copy”. +It will do most of the autoconf/automake related work for you.
    • +
  • Add the gettext.h +file to the package's source directory, and include it in all source +files that contain translatable strings or do output via printf or fprintf.
    • +
  • In the source file defining the main() function of the program, +add these lines to the header
    +
    #include <locale.h>
    + #include "gettext.h"
    +
    +and these lines near the beginning of the main() function:
    +
    setlocale (LC_ALL, "");
    + bindtextdomain (PACKAGE, +LOCALEDIR);
    + textdomain (PACKAGE);
    +
    +
    • +
  • Mark all strings that should be translated with _(), like this: _("No errors found."). 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.
    • +
  • In every source file containing translatable strings, add these lines +to the header:
    +
    #include "gettext.h"
    + #define _(string) gettext (string)
    +
    +
    • +
  • In the freshly created po/ +directory, set up the POTFILES.in +file, and do a “make update-po”. +Then distribute the generated .pot +file to your nearest translation project.
    • +
  • Shortly before a release, integrate the translators' .po files into the po/ directory and do “make update-po” again.
    +
    • +
+You find detailed descriptions of how this all works in the GNU gettext +manual, chapters “The Maintainer's View” and “Preparing Program +Sources”. +

I get a linker error “undefined +reference to libintl_gettext”

+This error means that the program uses the gettext() function after having +included the <libintl.h> +file from GNU gettext (which remaps it to libintl_gettext()), however at +link time a function of this name could not be linked in. (It is +expected to come from the libintl +library, installed by GNU gettext.)
+
+There are many possible reasons for this error, but in any case you +should consider the -I, -L and -l options passed to the +compiler. In packages using autoconf +generated configure scripts, -I +options come from the CFLAGS +and CPPFLAGS variables +(in Makefiles also DEFS +and INCLUDES), -L options come from the LDFLAGS variable, and -l options come from the LIBS variable. The first thing +you should check are the values of these variables in your environment +and in the  package's config.status +autoconfiguration result.
+
+To find the cause of the error, a little analysis is needed. Does the +program's final link command contains the option “-lintl”?
+
    +
  • If yes:
    +Find out where the libintl +comes from. To do this, you have to check for libintl.a and libintl.so* (libintl.dylib 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 “gcc -v” +instead of “gcc” in the +final link command line; compilers other than GCC usually look in /usr/lib and /lib.) A shell command like
    +
    $ for d in /usr/local/lib +/usr/lib /lib; do ls -l $d/libintl.*; done
    +
    +will show where the libintl +comes from. By looking at the dates and whether each library defines libintl_gettext (via “nm path/libintl.so +| grep libintl_gettext”) you can now distinguish three possible +causes of the error:
    +
      +
    • Some older libintl is used instead of the newer one. The fix +is to remove the old library or to reorganize your -L options.
      • +
    • 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.
      • +
    • 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”.
      • +
    +
    • +
  • If no:
    +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.
    +Test whether libintl was found by configure. You can check this by doing
    +
    $ grep +'\(INTLLIBS\|LIBINTL\)' config.status
    +
    +and looking whether the value of this autoconf variable is non-empty.
    +
      +
    • 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 @INTLLIBS@ or @LIBINTL@?
      +
        +
      • If no: It's a Makefile.am/in bug.
        • +
      • If yes: Something strange is going on. You need to dig +deeper.
        • +
      +Note that @INTLLIBS@ is +for gettext.m4 versions +<= 0.10.40 and @LIBINTL@ +is for gettext.m4 +versions >= 0.11, depending on which gettext.m4 was used to build +the package's configure - +regardless of which gettext you have now installed.
      • +
    • If no: So libintl was not found.
      +Take a look at the package's configure.in/ac. +Does it invoke AM_GNU_GETTEXT?
      +
        +
      • 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.
        • +
      • If yes: It looks like the -I and -L options were inconsistent. +You should have a -Isomedir/include in the CFLAGS or CPPFLAGS if and only if you +also have a -Lsomedir/lib in the LDFLAGS. And somedir/include +should contain a libintl.h +if and only if somedir/lib contains libintl.{a,so}.
        +This case can also happen if you have configured a GCC < 3.2 with +the same --prefix option +as you used for GNU libiconv or GNU gettext. This is fatal, because +these versions of GCC implicitly use -Lprefix/lib +but not
        + -Iprefix/include. The +workaround is to use a different --prefix +for GCC.
        +
        • +
      +
      • +
    +
    • +
+

gettextize adds multiple +references to the same directories/files +to Makefile.am and configure.ac

+If gettextize is used on +a package, then the po/, intl/, m4/ directories of the package +are removed, and then gettextize +is invoked on the package again, it will re-add the po/, intl/, m4/ directories and change Makefile.am, configure.ac and ChangeLog accordingly. This is +normal. The second use of gettextize +here is an abuse of the program. gettextize +is a wizard intended to transform a working +source package into a working +source package 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 gettextize corrects it.
+
+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 autopoint +which is designed to reconstruct those files and directories created by +gettextize that can be +omitted from a CVS repository.
+

My program compiles and links fine, +but doesn't output translated +strings.

+There are several possible reasons. Here is a checklist that allows you +to determine the cause.
+
    +
  1. Check that the environment variables LC_ALL, LC_MESSAGES, +LC_CTYPE, LANG, LANGUAGE together specify a valid locale and language.
    +To check this, run the commands
    +
    $ gettext --version
    + $ gettext --help
    +
    +You should see at least some output in your desired language. If not, +either
    +
      +
    • You have chosen a too exotic language. gettext is localized to 33 +languages. Choose a less exotic language, such as Galician or +Ukrainian. Or
      +
      • +
    • 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.
      • +
    +
    2. +
  2. Check that your program contains a setlocale call.
    +To check this, run your program under ltrace. For example,
    +
    $ ltrace ./myprog
    + ...
    + setlocale(6, +"")                  += "de_DE.UTF-8"
    +
    +If you have no ltrace, you can also do this check by running your +program under the debugger. For example,
    +
    $ gdb ./myprog
    + (gdb) break main
    + (gdb) run
    + Breakpoint 1, main ()
    + (gdb) break setlocale
    + (gdb) continue
    + Breakpoint 2, setlocale ()
    + ;; OK, the breakpoint has been hit, setlocale() is being +called.
    +
    +Either way, check that the return value of setlocale() is non-NULL. A NULL +return value indicates a failure. 
    3. +
  3. Check that your program contains a textdomain call, a bindtextdomain call referring +to the same message domain, and then really calls the gettext, dgettext or dcgettext function.
    +To check this, run the program under ltrace. For example,
    +
    $ ltrace ./myprog
    + ...
    + textdomain("hello-c")                             += "hello-c"
    + bindtextdomain("hello-c", "/opt/share"...) = "/opt/share"...
    + dcgettext(0, 0x08048691, 5, 0x0804a200, 0x08048689) = +0x4001721f
    +
    +If you have no ltrace, you can also do this check by running your +program under the debugger. For example,
    +
    $ gdb ./myprog
    + (gdb) break main
    + (gdb) run
    + Breakpoint 1, main ()
    + (gdb) break textdomain
    + (gdb) break bindtextdomain
    + (gdb) break gettext
    + (gdb) break dgettext
    + (gdb) break dcgettext
    + (gdb) continue
    + Breakpoint 2, textdomain ()
    + (gdb) continue
    + Breakpoint 3, bindtextdomain ()
    + (gdb) continue
    + Breakpoint 6, dcgettext ()
    +
    +Note that here dcgettext() +is called instead of the gettext() +function mentioned in the source code; this is due to an optimization +in <libintl.h>.
    +When using libintl on a non-glibc system, you have to add a prefix “libintl_” to all the function +names mentioned here, because that's what the functions are really +named, under the hood.
    +If gettext/dgettext/dcgettext is not called at all, +the possible cause might be that some autoconf or Makefile macrology +has turned off internationalization entirely (like the --disable-nls configuration +option usually does).
    +
    4. +
  4. Check that the .mo +file that contains the translation is really there where the program +expects it.
    +To check this, run the program under strace and look at the open() calls. For example,
    +
    $ strace ./myprog 2>&1 +| grep '^open('
    + open("/etc/ld.so.preload", O_RDONLY)    = -1 +ENOENT (No such file or directory)
    + open("/etc/ld.so.cache", +O_RDONLY)      = 5
    + open("/lib/libc.so.6", +O_RDONLY)        = 5
    + open("/usr/lib/locale/locale-archive", O_RDONLY|O_LARGEFILE) += 5
    + open("/usr/share/locale/locale.alias", O_RDONLY) = 5
    + open("/opt/share/locale/de/LC_MESSAGES/hello-c.mo", O_RDONLY) += 5
    + ...
    +
    +A nonnegative open() +return value means that the file has been found.
    +If you have no strace, you can also guess the .mo file's location: it is
    +
    localedir/lang/LC_MESSAGES/domain.mo
    +
    +where domain is the argument +passed to textdomain(), localedir is the second argument +passed to bindtextdomain(), +and lang is the language (LL) or language and territory (LL_CC), +depending on the environment variables checked in step 1.
    5. +
  5. Check that the .mo file contains a translation for the string +that is being asked for.
    +To do this, you need to convert the .mo file back to PO file format, +through the command
    +
    $ msgunfmt localedir/lang/LC_MESSAGES/domain.mo
    +
    +and look for an msgid +that matches the given string.
    +
    6. +
+

GNU gettext on Windows

+

What does Woe32 mean?

+“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”.
+

How do I compile, link and run a +program that uses the gettext() +function?

+When you use RedHat's cygwin environment, it's as on Unix:
+
    +
  • You need to add an -I +option to the compilation command line, so that the compiler finds the libintl.h include file, and
    • +
  • You need to add an -L +option to the link command line, so that the linker finds the libintl library.
    • +
+When you use the Mingw environment (either from within cygwin, with CC="gcc -mno-cygwin", or from +MSYS, with CC="gcc"), I +don't know the details.
+
+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 .bin.woe32.zip +packages of gettext-runtime +and libiconv. As a +developer, you'll also need the xgettext +and msgfmt programs that +are contained in the .bin.woe32.zip +package of gettext-tools. +Then
+
    +
  • You need to add an -MD +option to all compilation and link command lines. MSVC has six +different, mutually incompatible, compilation models (-ML, -MT, -MD, -MLd, -MTd, -MDd); the default is -ML. intl.dll uses the -MD model, therefore the rest +of the program must use -MD +as well.
    +
    • +
  • You need to add an -I +option to the compilation command line, so that the compiler finds the libintl.h include file.
    +
    • +
  • You need to add an -L +option to the link command line, so that the linker finds the intl.lib library.
    • +
  • You need to copy the intl.dll +and iconv.dll to the +directory where your .exe +files are created, so that they will be found at runtime.
    +
    • +
+

Setting the LANG +environment variable doesn't have any effect

+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.
+
+You can test your program by setting the LANG environment variable from +outside the program. In a Windows command interpreter:
+
set LANG=de_DE
+.\myprog.exe
+
+Or in a Cygwin shell:
+
$ env LANG=de_DE ./myprog.exe
+
+
+If this test fails, look at the question “My program compiles and links +fine, but doesn't output translated +strings.” above.
+
+If this test succeeds, the problem is related in the way you set the +environment variable. Here is a checklist:
+
    +
  • Check that you are using the -MD option in all compilation +and link command lines. Otherwise you might end up calling the putenv() function from +Microsoft's libc.lib, +whereas intl.dll is using +the getenv() function +from Mictosoft's msvcrt.lib.
    • +
  • Check that you set the environment variable using both SetEnvironmentVariable() and putenv(). A convenient way to +do so, and to deal with the fact that some Unix systems have setenv() and some don't, is the +following function.
    +
    +
    #include <string.h>
    + #include <stdlib.h>
    + #if defined _WIN32
    + # include <windows.h>
    + #endif
    +
    + int my_setenv (const char * name, const char * value) {
    +   size_t namelen = strlen(name);
    +   size_t valuelen = (value==NULL ? 0 : strlen(value));
    + #if defined _WIN32
    +   /* On Woe32, each process has two copies of the +environment variables,
    +      one managed by the OS and one +managed by the C library. We set
    +      the value in both locations, so that +other software that looks in
    +      one place or the other is guaranteed +to see the value. Even if it's
    +      a bit slow. See also
    +      <https://article.gmane.org/gmane.comp.gnu.mingw.user/8272>
    +      <https://article.gmane.org/gmane.comp.gnu.mingw.user/8273>
    +      <https://www.cygwin.com/ml/cygwin/1999-04/msg00478.html> +*/
    +   if (!SetEnvironmentVariableA(name,value))
    +     return -1;
    + #endif
    + #if defined(HAVE_PUTENV)
    +   char* buffer = (char*)malloc(namelen+1+valuelen+1);
    +   if (!buffer)
    +     return -1; /* no need to set errno = +ENOMEM */
    +   memcpy(buffer,name,namelen);
    +   if (value != NULL) {
    +     buffer[namelen] = '=';
    +     memcpy(buffer+namelen+1,value,valuelen);
    +     buffer[namelen+1+valuelen] = 0;
    +   } else
    +     buffer[namelen] = 0;
    +   return putenv(buffer);
    + #elif defined(HAVE_SETENV)
    +   return setenv(name,value,1);
    + #else
    +   /* Uh oh, neither putenv() nor setenv() ... */
    +   return -1;
    + #endif
    + }
    +
    +
    +
    • +
+

Other

+

What does this mean: “'msgid' and 'msgstr' +entries do not both end +with '\n'”

+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.
+

German umlauts are displayed like +“ge"andert” instead of “geändert”

+This symptom occurs when the LC_CTYPE +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.
+
+If the program is doing
+
+setlocale (LC_MESSAGES, "");
+
+then change it to
+
+setlocale (LC_CTYPE, "");
+setlocale (LC_MESSAGES, "");
+
+or do both of these in a single call:
+
+setlocale (LC_ALL, "");
+
+If the program is already doing
+
+setlocale (LC_ALL, "");
+
+then the symptom can still occur if the user has not set LANG, but instead has set LC_MESSAGES to a valid locale +and has set LC_CTYPE to +nothing or an invalid locale. The fix for the user is then to set LANG instead of LC_MESSAGES.
+

The LANGUAGE +environment variable is ignored after I set LANG=en

+This is because “en” is a language name, but not a valid locale name. +The documentation says:
+
+In the LANGUAGE +environment variable, but not in the LANG environment variable, LL_CC combinations can be +abbreviated as LL to +denote the language's main dialect.
+Why is LANG=en not +allowed? Because LANG 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.
+

I use accented characters in my +source code. How do I tell the +C/C++ compiler in which encoding it is (like xgettext's --from-code option)?

+Short answer: If you want your program to be useful to other people, +then don't use accented characters +(or other non-ASCII characters) in string literals in the source code. Instead, use +only ASCII for string literals, and use gettext() to retrieve their +display-ready form.
+
+Long explanation:
+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.
+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.
+The character encoding at execution time is the one which determines +how standard functions like isprint(), +wcwidth() 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 documentation.
+Strings in the compiled code are not magically converted between the +time the program is compiled and the time it is run.
+
+Therefore what could you do to get accented characters to work?
+
+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().
+
+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.
+
+Use of wide strings L"..." +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  character set, just as it does for +narrow strings "...". +Moreover, wide strings have problems of their own.
+
+Use of ISO C 99 Unicode escapes "\uxxxx" +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.
+
+So, in summary, there is no way to make accented characters in string +literals work in C/C++.
+
+You might then wonder what xgettext's +--from-code option is good +for. The answer is
+
    +
  1. For the comments in C/C++ source code. The compiler ignores them.
    +
    2. +
  2. For other programming languages like Java, for which the compiler +converts all string literals to UTF-8.
    3. +
+
+
+
GNU gettext FAQ
+Bruno Haible <bruno@clisp.org>
+

Last modified: 6 June 2020 +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/autopoint.1.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/autopoint.1.html new file mode 100644 index 0000000000000000000000000000000000000000..f7e4e9df9a03a6f4b4986ed1e0f7dd293d6dbe7f --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/autopoint.1.html @@ -0,0 +1,148 @@ + + + + + + + + +AUTOPOINT + + + + +

AUTOPOINT

+ +NAME
+SYNOPSIS
+DESCRIPTION
+OPTIONS
+AUTHOR
+REPORTING BUGS
+COPYRIGHT
+SEE ALSO
+ +
+ + +

NAME + +

+ + +

autopoint +- copies standard gettext infrastructure

+ +

SYNOPSIS + +

+ + + +

autopoint +[OPTION]...

+ +

DESCRIPTION + +

+ + +

Copies standard +gettext infrastructure files into a source package.

+ +

OPTIONS + +

+ + + + + + + + + +
+ + +

--help

 + + +

print this help and exit

 +
+ + +

--version

+ +

print version information and +exit

+ +

-f, +--force

+ +

force overwriting of files that +already exist

+ +

-n, +--dry-run

+ +

print modifications but +don’t perform them

+ +

AUTHOR + +

+ + +

Written by +Bruno Haible

+ +

REPORTING BUGS + +

+ + +

Report bugs in +the bug tracker at +<https://savannah.gnu.org/projects/gettext> or by +email to <bug-gettext@gnu.org>.

+ +

COPYRIGHT + +

+ + +

Copyright +© 2002-2025 Free Software Foundation, Inc. +License GPLv3+: GNU GPL version 3 or later +<https://gnu.org/licenses/gpl.html>
+This is free software: you are free to change and +redistribute it. There is NO WARRANTY, to the extent +permitted by law.

+ +

SEE ALSO + +

+ + +

The full +documentation for autopoint is maintained as a +Texinfo manual. If the info and autopoint +programs are properly installed at your site, the +command

+ +

info +autopoint

+ +

should give you +access to the complete manual.

+
+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/bind_textdomain_codeset.3.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/bind_textdomain_codeset.3.html new file mode 100644 index 0000000000000000000000000000000000000000..c6a5a96eeed709c90ccdce7e32cd97257bd6518f --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/bind_textdomain_codeset.3.html @@ -0,0 +1,158 @@ + + + + + + + + +BIND_TEXTDOMAIN_CODESET + + + + +

BIND_TEXTDOMAIN_CODESET

+ +NAME
+SYNOPSIS
+DESCRIPTION
+RETURN VALUE
+ERRORS
+BUGS
+SEE ALSO
+ +
+ + +

NAME + +

+ + + +

bind_textdomain_codeset +- set encoding of message translations

+ +

SYNOPSIS + +

+ + +

#include +<libintl.h>

+ +

char * +bind_textdomain_codeset (const char * +domainname,
+const char * codeset);

+ +

DESCRIPTION + +

+ + +

The +bind_textdomain_codeset function sets the output +codeset for message catalogs for domain +domainname.

+ +

A message +domain is a set of translatable msgid messages. +Usually, every software package has its own message +domain.

+ +

By default, the +gettext family of functions returns translated +messages in the locale’s character encoding, which can +be retrieved as nl_langinfo (CODESET). The need for +calling bind_textdomain_codeset arises for programs +which store strings in a locale independent way (e.g. UTF-8) +and want to avoid an extra character set conversion on the +returned translated messages.

+ + +

domainname +must be a non-empty string.

+ +

If +codeset is not NULL, it must be a valid encoding name +which can be used for the iconv_open function. The +bind_textdomain_codeset function sets the output +codeset for message catalogs belonging to domain +domainname to codeset. The function makes +copies of the argument strings as needed.

+ +

If +codeset is NULL, the function returns the previously +set codeset for domain domainname. The default is +NULL, denoting the locale’s character encoding.

+ +

RETURN VALUE + +

+ + +

If successful, +the bind_textdomain_codeset function returns the +current codeset for domain domainname, after possibly +changing it. The resulting string is valid until the next +bind_textdomain_codeset call for the same +domainname and must not be modified or freed. If a +memory allocation failure occurs, it sets errno to +ENOMEM and returns NULL. If no codeset has been set +for domain domainname, it returns NULL.

+ +

ERRORS + +

+ + +

The following +error can occur, among others:

+ + + + + + + + +
+ + +

ENOMEM

 + + +

Not enough memory available.

 +
+ +

BUGS + +

+ + +

The return type +ought to be const char *, but is char * to +avoid warnings in C code predating ANSI C.

+ +

SEE ALSO + +

+ + + +

gettext(3), +dgettext(3), dcgettext(3), ngettext(3), +dngettext(3), dcngettext(3), +textdomain(3), nl_langinfo(3), +iconv_open(3)

+
+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/bindtextdomain.3.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/bindtextdomain.3.html new file mode 100644 index 0000000000000000000000000000000000000000..622f2fdd6a556f35819461e1407f4adf2b9f5c28 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/bindtextdomain.3.html @@ -0,0 +1,154 @@ + + + + + + + + +BINDTEXTDOMAIN + + + + +

BINDTEXTDOMAIN

+ +NAME
+SYNOPSIS
+DESCRIPTION
+RETURN VALUE
+ERRORS
+BUGS
+SEE ALSO
+ +
+ + +

NAME + +

+ + +

bindtextdomain +- set directory containing message catalogs

+ +

SYNOPSIS + +

+ + +

#include +<libintl.h>

+ +

char * +bindtextdomain (const char * domainname, const +char * dirname);

+ +

DESCRIPTION + +

+ + +

The +bindtextdomain function sets the base directory of +the hierarchy containing message catalogs for a given +message domain.

+ +

A message +domain is a set of translatable msgid messages. +Usually, every software package has its own message domain. +The need for calling bindtextdomain arises because +packages are not always installed with the same prefix as +the <libintl.h> header and the libc/libintl +libraries.

+ +

Message +catalogs will be expected at the pathnames +dirname/locale/category/domainname.mo, +where locale is a locale name and category is +a locale facet such as LC_MESSAGES.

+ + +

domainname +must be a non-empty string.

+ +

If +dirname is not NULL, the base directory for message +catalogs belonging to domain domainname is set to +dirname. The function makes copies of the argument +strings as needed. If the program wishes to call the +chdir function, it is important that dirname +be an absolute pathname; otherwise it cannot be guaranteed +that the message catalogs will be found.

+ +

If +dirname is NULL, the function returns the previously +set base directory for domain domainname.

+ +

RETURN VALUE + +

+ + +

If successful, +the bindtextdomain function returns the current base +directory for domain domainname, after possibly +changing it. The resulting string is valid until the next +bindtextdomain call for the same domainname +and must not be modified or freed. If a memory allocation +failure occurs, it sets errno to ENOMEM and +returns NULL.

+ +

ERRORS + +

+ + +

The following +error can occur, among others:

+ + + + + + + + +
+ + +

ENOMEM

 + + +

Not enough memory available.

 +
+ +

BUGS + +

+ + +

The return type +ought to be const char *, but is char * to +avoid warnings in C code predating ANSI C.

+ +

SEE ALSO + +

+ + + +

gettext(3), +dgettext(3), dcgettext(3), ngettext(3), +dngettext(3), dcngettext(3), +textdomain(3), realpath(3)

+
+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/csharpdoc/GNU_Gettext.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/csharpdoc/GNU_Gettext.html new file mode 100644 index 0000000000000000000000000000000000000000..ec0ec953cbee166a342c3174634a8e9b8356203a --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/csharpdoc/GNU_Gettext.html @@ -0,0 +1,8 @@ + + +GNU.Gettext Namespace

+ +GettextResourceManager
+GettextResourceSet
+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/csharpdoc/GNU_Gettext_GettextResourceManager.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/csharpdoc/GNU_Gettext_GettextResourceManager.html new file mode 100644 index 0000000000000000000000000000000000000000..e23756724750388bba624936865101a1e66327d9 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/csharpdoc/GNU_Gettext_GettextResourceManager.html @@ -0,0 +1,305 @@ + + +GNU.Gettext.GettextResourceManager Class + + +

GNU.Gettext.GettextResourceManager Class

+ +
+ + +
public class GettextResourceManager: System.Resources.ResourceManager
+
+ +

Base Types

+ +
+System.Resources.ResourceManager
+  GettextResourceManager

+ +

+ +

Library

+ +
+GNU.Gettext +
+ +

Summary

+ +
+ +Each instance of this class can be used to lookup translations for a +given resource name. For each CultureInfo, it performs the lookup +in several assemblies, from most specific over territory-neutral to +language-neutral. +
+ +

See Also

+ +
+GNU.Gettext Namespace +
+ +

Members

+ +
+

+ +GettextResourceManager Constructors

+ +GettextResourceManager(System.String) Constructor
+GettextResourceManager(System.String, System.Reflection.Assembly) Constructor
+

+ +GettextResourceManager Methods

+ +GettextResourceManager.GetPluralString(System.String, System.String, long, System.Globalization.CultureInfo) Method
+GettextResourceManager.GetPluralString(System.String, System.String, long) Method
+GettextResourceManager.GetString(System.String, System.Globalization.CultureInfo) Method
+GettextResourceManager.GetString(System.String) Method
+

+ +
+ +

GettextResourceManager(System.String) Constructor

+ +
+ + +
public GettextResourceManager(System.String baseName);
+
+ +

Summary

+ +
+ +Constructor. +
+ +

Parameters

+ +
+
+
baseName
+
the resource name, also the assembly base + name
+
+
+ +

See Also

+ +
+GNU.Gettext.GettextResourceManager Class, GNU.Gettext Namespace +
+ +
+ +

GettextResourceManager(System.String, System.Reflection.Assembly) Constructor

+ +
+ + +
public GettextResourceManager(System.String baseName, System.Reflection.Assembly assembly);
+
+ +

Summary

+ +
+ +Constructor. +
+ +

Parameters

+ +
+
+
baseName
+
the resource name, also the assembly base + name
+
+
+ +

See Also

+ +
+GNU.Gettext.GettextResourceManager Class, GNU.Gettext Namespace +
+ +
+ +

GettextResourceManager.GetPluralString(System.String, System.String, long, System.Globalization.CultureInfo) Method

+ +
+ + +
public virtual System.String GetPluralString(System.String msgid, System.String msgidPlural, long n, System.Globalization.CultureInfo culture);
+
+ +

Summary

+ +
+ +Returns the translation of msgid and +msgidPlural in a given culture, choosing the right +plural form depending on the number n. +
+ +

Parameters

+ +
+
+
msgid
+
the key string to be translated, an ASCII + string
+
msgidPlural
+
the English plural of msgid, + an ASCII string
+
n
+
the number, should be >= 0
+
+
+ +

Return Value

+ +
+the translation, or msgid or + msgidPlural if none is found +
+ +

See Also

+ +
+GNU.Gettext.GettextResourceManager Class, GNU.Gettext Namespace +
+ +
+ +

GettextResourceManager.GetPluralString(System.String, System.String, long) Method

+ +
+ + +
public virtual System.String GetPluralString(System.String msgid, System.String msgidPlural, long n);
+
+ +

Summary

+ +
+ +Returns the translation of msgid and +msgidPlural in the current culture, choosing the +right plural form depending on the number n. +
+ +

Parameters

+ +
+
+
msgid
+
the key string to be translated, an ASCII + string
+
msgidPlural
+
the English plural of msgid, + an ASCII string
+
n
+
the number, should be >= 0
+
+
+ +

Return Value

+ +
+the translation, or msgid or + msgidPlural if none is found +
+ +

See Also

+ +
+GNU.Gettext.GettextResourceManager Class, GNU.Gettext Namespace +
+ +
+ +

GettextResourceManager.GetString(System.String, System.Globalization.CultureInfo) Method

+ +
+ + +
public override System.String GetString(System.String msgid, System.Globalization.CultureInfo culture);
+
+ +

Summary

+ +
+ +Returns the translation of msgid in a given culture. +
+ +

Parameters

+ +
+
+
msgid
+
the key string to be translated, an ASCII + string
+
+
+ +

Return Value

+ +
+the translation of msgid, or + msgid if none is found +
+ +

See Also

+ +
+GNU.Gettext.GettextResourceManager Class, GNU.Gettext Namespace +
+ +
+ +

GettextResourceManager.GetString(System.String) Method

+ +
+ + +
public override System.String GetString(System.String msgid);
+
+ +

Summary

+ +
+ +Returns the translation of msgid in the current +culture. +
+ +

Parameters

+ +
+
+
msgid
+
the key string to be translated, an ASCII + string
+
+
+ +

Return Value

+ +
+the translation of msgid, or + msgid if none is found +
+ +

See Also

+ +
+GNU.Gettext.GettextResourceManager Class, GNU.Gettext Namespace +
+ + + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/csharpdoc/GNU_Gettext_GettextResourceSet.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/csharpdoc/GNU_Gettext_GettextResourceSet.html new file mode 100644 index 0000000000000000000000000000000000000000..64869c9973a04a3d2e9c89c5680f690153e3225f --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/csharpdoc/GNU_Gettext_GettextResourceSet.html @@ -0,0 +1,356 @@ + + +GNU.Gettext.GettextResourceSet Class + + +

GNU.Gettext.GettextResourceSet Class

+ +
+ + +
public class GettextResourceSet: System.Resources.ResourceSet
+
+ +

Base Types

+ +
+System.Resources.ResourceSet
+  GettextResourceSet

+ +

+ +

Library

+ +
+GNU.Gettext +
+ +

Summary

+ +
+ +Each instance of this class encapsulates a single PO file. +

+ + +This API of this class is not meant to be used directly; use +GettextResourceManager instead. +

+ +

+ +

See Also

+ +
+GNU.Gettext Namespace +
+ +

Members

+ +
+

+ +GettextResourceSet Constructors

+ +GettextResourceSet() Constructor
+GettextResourceSet(System.Resources.IResourceReader) Constructor
+GettextResourceSet(System.IO.Stream) Constructor
+GettextResourceSet(System.String) Constructor
+

+ +GettextResourceSet Methods

+ +GettextResourceSet.GetPluralString Method
+GettextResourceSet.GetString(System.String) Method
+GettextResourceSet.GetString(System.String, bool) Method
+GettextResourceSet.PluralEval Method
+

+ +GettextResourceSet Properties

+ +GettextResourceSet.Keys Property
+

+ +
+ +

GettextResourceSet() Constructor

+ +
+ + +
protected GettextResourceSet();
+
+ +

Summary

+ +
+ +Creates a new message catalog. When using this constructor, you +must override the ReadResources method, in order to initialize +the Table property. The message catalog will support plural +forms only if the ReadResources method installs values of type +String[] and if the PluralEval method is overridden. +
+ +

See Also

+ +
+GNU.Gettext.GettextResourceSet Class, GNU.Gettext Namespace +
+ +
+ +

GettextResourceSet(System.Resources.IResourceReader) Constructor

+ +
+ + +
public GettextResourceSet(System.Resources.IResourceReader reader);
+
+ +

Summary

+ +
+ +Creates a new message catalog, by reading the string/value pairs from +the given reader. The message catalog will support +plural forms only if the reader can produce values of type +String[] and if the PluralEval method is overridden. +
+ +

See Also

+ +
+GNU.Gettext.GettextResourceSet Class, GNU.Gettext Namespace +
+ +
+ +

GettextResourceSet(System.IO.Stream) Constructor

+ +
+ + +
public GettextResourceSet(System.IO.Stream stream);
+
+ +

Summary

+ +
+ +Creates a new message catalog, by reading the string/value pairs from +the given stream, which should have the format of +a .resources file. The message catalog will not support plural +forms. +
+ +

See Also

+ +
+GNU.Gettext.GettextResourceSet Class, GNU.Gettext Namespace +
+ +
+ +

GettextResourceSet(System.String) Constructor

+ +
+ + +
public GettextResourceSet(System.String fileName);
+
+ +

Summary

+ +
+ +Creates a new message catalog, by reading the string/value pairs from +the file with the given fileName. The file should +be in the format of a .resources file. The message catalog will +not support plural forms. +
+ +

See Also

+ +
+GNU.Gettext.GettextResourceSet Class, GNU.Gettext Namespace +
+ +
+ +

GettextResourceSet.GetPluralString Method

+ +
+ + +
public virtual System.String GetPluralString(System.String msgid, System.String msgidPlural, long n);
+
+ +

Summary

+ +
+ +Returns the translation of msgid and +msgidPlural, choosing the right plural form +depending on the number n. +
+ +

Parameters

+ +
+
+
msgid
+
the key string to be translated, an ASCII + string
+
msgidPlural
+
the English plural of msgid, + an ASCII string
+
n
+
the number, should be >= 0
+
+
+ +

Return Value

+ +
+the translation, or null if none is found +
+ +

See Also

+ +
+GNU.Gettext.GettextResourceSet Class, GNU.Gettext Namespace +
+ +
+ +

GettextResourceSet.GetString(System.String) Method

+ +
+ + +
public override System.String GetString(System.String msgid);
+
+ +

Summary

+ +
+ +Returns the translation of msgid. +
+ +

Parameters

+ +
+
+
msgid
+
the key string to be translated, an ASCII + string
+
+
+ +

Return Value

+ +
+the translation of msgid, or null if + none is found +
+ +

See Also

+ +
+GNU.Gettext.GettextResourceSet Class, GNU.Gettext Namespace +
+ +
+ +

GettextResourceSet.GetString(System.String, bool) Method

+ +
+ + +
public override System.String GetString(System.String msgid, bool ignoreCase);
+
+ +

Summary

+ +
+ +Returns the translation of msgid, with possibly +case-insensitive lookup. +
+ +

Parameters

+ +
+
+
msgid
+
the key string to be translated, an ASCII + string
+
+
+ +

Return Value

+ +
+the translation of msgid, or null if + none is found +
+ +

See Also

+ +
+GNU.Gettext.GettextResourceSet Class, GNU.Gettext Namespace +
+ +
+ +

GettextResourceSet.PluralEval Method

+ +
+ + +
protected virtual long PluralEval(long n);
+
+ +

Summary

+ +
+ +Returns the index of the plural form to be chosen for a given number. +The default implementation is the Germanic plural formula: +zero for n == 1, one for n != 1. +
+ +

See Also

+ +
+GNU.Gettext.GettextResourceSet Class, GNU.Gettext Namespace +
+ +
+ +

GettextResourceSet.Keys Property

+ +
+ + +
public virtual System.Collections.ICollection Keys { get; }
+
+ +

Summary

+ +
+ +Returns the keys of this resource set, i.e. the strings for which +GetObject() can return a non-null value. +
+ +

See Also

+ +
+GNU.Gettext.GettextResourceSet Class, GNU.Gettext Namespace +
+ + + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/csharpdoc/begin.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/csharpdoc/begin.html new file mode 100644 index 0000000000000000000000000000000000000000..a0917d6140a0de01dfea78f6adbef096d77ccb9b --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/csharpdoc/begin.html @@ -0,0 +1,11 @@ + +- + +

-

+ +
+GNU.Gettext Namespace
+
+ + + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/csharpdoc/index.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/csharpdoc/index.html new file mode 100644 index 0000000000000000000000000000000000000000..96aa05a15a2cf365f7d5f52257c7cbcb61a7ea78 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/csharpdoc/index.html @@ -0,0 +1,10 @@ + +- + + + + + + + + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/csharpdoc/namespaces.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/csharpdoc/namespaces.html new file mode 100644 index 0000000000000000000000000000000000000000..9ffd95e7a2283323a35bf988a2e93c09f71a64ba --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/csharpdoc/namespaces.html @@ -0,0 +1,6 @@ + + +Namespaces

+GNU.Gettext
+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/envsubst.1.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/envsubst.1.html new file mode 100644 index 0000000000000000000000000000000000000000..70a7628081ca3f8e582cb0ee215322f8654ae7df --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/envsubst.1.html @@ -0,0 +1,142 @@ + + + + + + + + +ENVSUBST + + + + +

ENVSUBST

+ +NAME
+SYNOPSIS
+DESCRIPTION
+AUTHOR
+REPORTING BUGS
+COPYRIGHT
+SEE ALSO
+ +
+ + +

NAME + +

+ + +

envsubst +- substitutes environment variables in shell format +strings

+ +

SYNOPSIS + +

+ + + +

envsubst +[OPTION] [SHELL-FORMAT]

+ +

DESCRIPTION + +

+ + +

Substitutes the +values of environment variables.

+ +

Operation +mode:
+-v, --variables

+ +

output the variables occurring +in SHELL-FORMAT

+ +

Informative +output:
+-h, --help

+ +

display this help and exit

+ +

-V, +--version

+ +

output version information and +exit

+ +

In normal +operation mode, standard input is copied to standard output, +with references to environment variables of the form +$VARIABLE or ${VARIABLE} being replaced with the +corresponding values. If a SHELL-FORMAT is given, only +those environment variables that are referenced in +SHELL-FORMAT are substituted; otherwise all +environment variables references occurring in standard input +are substituted.

+ +

When +--variables is used, standard input is +ignored, and the output consists of the environment +variables that are referenced in SHELL-FORMAT, one per +line.

+ +

AUTHOR + +

+ + +

Written by +Bruno Haible.

+ +

REPORTING BUGS + +

+ + +

Report bugs in +the bug tracker at +<https://savannah.gnu.org/projects/gettext> or by +email to <bug-gettext@gnu.org>.

+ +

COPYRIGHT + +

+ + +

Copyright +© 2003-2025 Free Software Foundation, Inc. +License GPLv3+: GNU GPL version 3 or later +<https://gnu.org/licenses/gpl.html>
+This is free software: you are free to change and +redistribute it. There is NO WARRANTY, to the extent +permitted by law.

+ +

SEE ALSO + +

+ + +

The full +documentation for envsubst is maintained as a Texinfo +manual. If the info and envsubst programs are +properly installed at your site, the command

+ +

info +envsubst

+ +

should give you +access to the complete manual.

+
+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext.1.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext.1.html new file mode 100644 index 0000000000000000000000000000000000000000..cfe520442ca9d05a1906ca36a6f7b8b805ddcfca --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext.1.html @@ -0,0 +1,192 @@ + + + + + + + + +GETTEXT + + + + +

GETTEXT

+ +NAME
+SYNOPSIS
+DESCRIPTION
+AUTHOR
+REPORTING BUGS
+COPYRIGHT
+SEE ALSO
+ +
+ + +

NAME + +

+ + +

gettext - +translate message

+ +

SYNOPSIS + +

+ + +

gettext +[OPTION] [[TEXTDOMAIN] MSGID]
+gettext [OPTION] -s [MSGID]...

+ +

DESCRIPTION + +

+ + +

The +gettext program translates a natural language message +into the user’s language, by looking up the +translation in a message catalog.

+ +

Display native +language translation of a textual message.
+-d, +--domain=TEXTDOMAIN

+ +

retrieve translated messages +from TEXTDOMAIN

+ +

-c, +--context=CONTEXT

+ +

specify context for MSGID

+ + + + + + + + + + + + + + + + + + + + +
+ + +

-e

 + + +

enable expansion of some escape sequences

 +
+ + +

-n

 + + +

suppress trailing newline

 +
+ + +

-E

 + + +

(ignored for compatibility)

 +
+ +

[TEXTDOMAIN] MSGID

+ +

retrieve translated message +corresponding to MSGID from TEXTDOMAIN

+ +

Informative +output:
+-h, --help

+ +

display this help and exit

+ +

-V, +--version

+ +

display version information and +exit

+ +

If the +TEXTDOMAIN parameter is not given, the domain is determined +from the environment variable TEXTDOMAIN. If the message +catalog is not found in the regular directory, another +location can be specified with the environment variable +TEXTDOMAINDIR. When used with the -s option the +program behaves like the ’echo’ command. But it +does not simply copy its arguments to stdout. Instead those +messages found in the selected catalog are translated. +Standard search directory: /home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho/share/locale

+ +

AUTHOR + +

+ + +

Written by +Ulrich Drepper.

+ +

REPORTING BUGS + +

+ + +

Report bugs in +the bug tracker at +<https://savannah.gnu.org/projects/gettext> or by +email to <bug-gettext@gnu.org>.

+ +

COPYRIGHT + +

+ + +

Copyright +© 1995-2025 Free Software Foundation, Inc. +License GPLv3+: GNU GPL version 3 or later +<https://gnu.org/licenses/gpl.html>
+This is free software: you are free to change and +redistribute it. There is NO WARRANTY, to the extent +permitted by law.

+ +

SEE ALSO + +

+ + +

The full +documentation for gettext is maintained as a Texinfo +manual. If the info and gettext programs are +properly installed at your site, the command

+ +

info +gettext

+ +

should give you +access to the complete manual.

+
+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext.3.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext.3.html new file mode 100644 index 0000000000000000000000000000000000000000..6d126e44dc825b64e0804e366537c7638bc8f716 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext.3.html @@ -0,0 +1,182 @@ + + + + + + + + +GETTEXT + + + + +

GETTEXT

+ +NAME
+SYNOPSIS
+DESCRIPTION
+RETURN VALUE
+ERRORS
+BUGS
+SEE ALSO
+ +
+ + +

NAME + +

+ + +

gettext, +dgettext, dcgettext - translate message

+ +

SYNOPSIS + +

+ + +

#include +<libintl.h>

+ +

char * +gettext (const char * msgid);
+char * dgettext (const char * domainname, +const char * msgid);
+char * dcgettext (const char * domainname, +const char * msgid,
+int category);

+ +

DESCRIPTION + +

+ + +

The +gettext, dgettext and dcgettext +functions attempt to translate a text string into the +user’s native language, by looking up the translation +in a message catalog.

+ +

The +msgid argument identifies the message to be +translated. By convention, it is the English version of the +message, with non-ASCII characters replaced by ASCII +approximations. This choice allows the translators to work +with message catalogs, called PO files, that contain both +the English and the translated versions of each message, and +can be installed using the msgfmt utility.

+ +

A message +domain is a set of translatable msgid messages. +Usually, every software package has its own message domain. +The domain name is used to determine the message catalog +where the translation is looked up; it must be a non-empty +string. For the gettext function, it is specified +through a preceding textdomain call. For the +dgettext and dcgettext functions, it is passed +as the domainname argument; if this argument is NULL, +the domain name specified through a preceding +textdomain call is used instead.

+ +

Translation +lookup operates in the context of the current locale. For +the gettext and dgettext functions, the +LC_MESSAGES locale facet is used. It is determined by +a preceding call to the setlocale function. +setlocale (LC_ALL, "") initializes the +LC_MESSAGES locale based on the first nonempty value +of the three environment variables LC_ALL, +LC_MESSAGES, LANG; see setlocale(3). +For the dcgettext function, the locale facet is +determined by the category argument, which should be +one of the LC_xxx constants defined in the +<locale.h> header, excluding LC_ALL. In both +cases, the functions also use the LC_CTYPE locale +facet in order to convert the translated message from the +translator’s codeset to the current locale’s +codeset, unless overridden by a prior call to the +bind_textdomain_codeset function.

+ +

The message +catalog used by the functions is at the pathname +dirname/locale/category/domainname.mo. +Here dirname is the directory specified through +bindtextdomain. Its default is system and +configuration dependent; typically it is +prefix/share/locale, where prefix is the +installation prefix of the package. locale is the +name of the current locale facet; the GNU implementation +also tries generalizations, such as the language name +without the territory name. category is +LC_MESSAGES for the gettext and +dgettext functions, or the argument passed to the +dcgettext function.

+ +

If the +LANGUAGE environment variable is set to a nonempty +value, and the locale is not the "C" locale, the +value of LANGUAGE is assumed to contain a colon +separated list of locale names. The functions will attempt +to look up a translation of msgid in each of the +locales in turn. This is a GNU extension.

+ +

In the +"C" locale, or if none of the used catalogs +contain a translation for msgid, the gettext, +dgettext and dcgettext functions return +msgid.

+ +

RETURN VALUE + +

+ + +

If a +translation was found in one of the specified catalogs, it +is converted to the locale’s codeset and returned. The +resulting string is statically allocated and must not be +modified or freed. Otherwise msgid is returned.

+ +

ERRORS + +

+ + +

errno is +not modified.

+ +

BUGS + +

+ + +

The return type +ought to be const char *, but is char * to +avoid warnings in C code predating ANSI C.

+ +

When an empty +string is used for msgid, the functions may return a +nonempty string.

+ +

SEE ALSO + +

+ + + +

ngettext(3), +dngettext(3), dcngettext(3), +setlocale(3), textdomain(3), +bindtextdomain(3), bind_textdomain_codeset(3), +msgfmt(1)

+
+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_1.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_1.html new file mode 100644 index 0000000000000000000000000000000000000000..df6c3cf810d3c4f20f3cbfbd3508c532bd7afa10 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_1.html @@ -0,0 +1,678 @@ + + + + + +GNU gettext utilities: 1. Introduction + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

1. Introduction

+ +

This chapter explains the goals sought in the creation +of GNU gettext and the free Translation Project. +Then, it explains a few broad concepts around +Native Language Support, and positions message translation with regard +to other aspects of national and cultural variance, as they apply +to programs. It also surveys those files used to convey the +translations. It explains how the various tools interact in the +initial generation of these files, and later, how the maintenance +cycle should usually operate. +

+ + + +

In this manual, we use he when speaking of the programmer or +maintainer, she when speaking of the translator, and they +when speaking of the installers or end users of the translated program. +This is only a convenience for clarifying the documentation. It is +absolutely not meant to imply that some roles are more appropriate +to males or females. Besides, as you might guess, GNU gettext +is meant to be useful for people using computers, whatever their sex, +race, religion or nationality! +

+ +

Please submit suggestions and corrections +

+ +

Please include the manual's edition number and update date in your messages. +

+ + + + +

1.1 The Purpose of GNU gettext

+ +

Usually, programs are written and documented in English, and use +English at execution time to interact with users. This is true +not only of GNU software, but also of a great deal of proprietary +and free software. Using a common language is quite handy for +communication between developers, maintainers and users from all +countries. On the other hand, most people are less comfortable with +English than with their own native language, and would prefer to +use their mother tongue for day to day's work, as far as possible. +Many would simply love to see their computer screen showing +a lot less of English, and far more of their own language. +

+ +

However, to many people, this dream might appear so far fetched that +they may believe it is not even worth spending time thinking about +it. They have no confidence at all that the dream might ever +become true. Yet some have not lost hope, and have organized themselves. +The Translation Project is a formalization of this hope into a +workable structure, which has a good chance to get all of us nearer +the achievement of a truly multi-lingual set of programs. +

+

GNU gettext is an important step for the Translation Project, +as it is an asset on which we may build many other steps. This package +offers to programmers, translators and even users, a well integrated +set of tools and documentation. Specifically, the GNU gettext +utilities are a set of tools that provides a framework within which +other free packages may produce multi-lingual messages. These tools +include +

+
    +
  • +A set of conventions about how programs should be written to support +message catalogs. + +
  • +A directory and file naming organization for the message catalogs +themselves. + +
  • +A runtime library supporting the retrieval of translated messages. + +
  • +A few stand-alone programs to massage in various ways the sets of +translatable strings, or already translated strings. + +
  • +A library supporting the parsing and creation of files containing +translated messages. + +
  • +A special mode for Emacs(1) which helps preparing these sets +and bringing them up to date. +
+ +

GNU gettext is designed to minimize the impact of +internationalization on program sources, keeping this impact as small +and hardly noticeable as possible. Internationalization has better +chances of succeeding if it is very light weighted, or at least, +appear to be so, when looking at program sources. +

+

The Translation Project also uses the GNU gettext distribution +as a vehicle for documenting its structure and methods. This goes +beyond the strict technicalities of documenting the GNU gettext +proper. By so doing, translators will find in a single place, as +far as possible, all they need to know for properly doing their +translating work. Also, this supplemental documentation might also +help programmers, and even curious users, in understanding how GNU +gettext is related to the remainder of the Translation +Project, and consequently, have a glimpse at the big picture. +

+ + + +

1.2 I18n, L10n, and Such

+ +

Two long words appear all the time when we discuss support of native +language in programs, and these words have a precise meaning, worth +being explained here, once and for all in this document. The words are +internationalization and localization. Many people, +tired of writing these long words over and over again, took the +habit of writing i18n and l10n instead, quoting the first +and last letter of each word, and replacing the run of intermediate +letters by a number merely telling how many such letters there are. +But in this manual, in the sake of clarity, we will patiently write +the names in full, each time… +

+ +

By internationalization, one refers to the operation by which a +program, or a set of programs turned into a package, is made aware of and +able to support multiple languages. This is a generalization process, +by which the programs are untied from calling only English strings or +other English specific habits, and connected to generic ways of doing +the same, instead. Program developers may use various techniques to +internationalize their programs. Some of these have been standardized. +GNU gettext offers one of these standards. See section The Programmer's View. +

+ +

By localization, one means the operation by which, in a set +of programs already internationalized, one gives the program all +needed information so that it can adapt itself to handle its input +and output in a fashion which is correct for some native language and +cultural habits. This is a particularisation process, by which generic +methods already implemented in an internationalized program are used +in specific ways. The programming environment puts several functions +to the programmers disposal which allow this runtime configuration. +The formal description of specific set of cultural habits for some +country, together with all associated translations targeted to the +same native language, is called the locale for this language +or country. Users achieve localization of programs by setting proper +values to special environment variables, prior to executing those +programs, identifying which locale should be used. +

+

In fact, locale message support is only one component of the cultural +data that makes up a particular locale. There are a whole host of +routines and functions provided to aid programmers in developing +internationalized software and which allow them to access the data +stored in a particular locale. When someone presently refers to a +particular locale, they are obviously referring to the data stored +within that particular locale. Similarly, if a programmer is referring +to “accessing the locale routines”, they are referring to the +complete suite of routines that access all of the locale's information. +

+ + + +

One uses the expression Native Language Support, or merely NLS, +for speaking of the overall activity or feature encompassing both +internationalization and localization, allowing for multi-lingual +interactions in a program. In a nutshell, one could say that +internationalization is the operation by which further localizations +are made possible. +

+

Also, very roughly said, when it comes to multi-lingual messages, +internationalization is usually taken care of by programmers, and +localization is usually taken care of by translators. +

+ + + +

1.3 Aspects in Native Language Support

+ +

For a totally multi-lingual distribution, there are many things to +translate beyond output messages. +

+
    +
  • +As of today, GNU gettext offers a complete toolset for +translating messages output by C programs. Perl scripts and shell +scripts will also need to be translated. Even if there are today some hooks +by which this can be done, these hooks are not integrated as well as they +should be. + +
  • +Some programs, like autoconf or bison, are able +to produce other programs (or scripts). Even if the generating +programs themselves are internationalized, the generated programs they +produce may need internationalization on their own, and this indirect +internationalization could be automated right from the generating +program. In fact, quite usually, generating and generated programs +could be internationalized independently, as the effort needed is +fairly orthogonal. + +
  • +A few programs include textual tables which might need translation +themselves, independently of the strings contained in the program +itself. For example, RFC 1345 gives an English description for each +character which the recode program is able to reconstruct at execution. +Since these descriptions are extracted from the RFC by mechanical means, +translating them properly would require a prior translation of the RFC +itself. + +
  • +Almost all programs accept options, which are often worded out so to +be descriptive for the English readers; one might want to consider +offering translated versions for program options as well. + +
  • +Many programs read, interpret, compile, or are somewhat driven by +input files which are texts containing keywords, identifiers, or +replies which are inherently translatable. For example, one may want +gcc to allow diacriticized characters in identifiers or use +translated keywords; ‘rm -i’ might accept something else than +‘y’ or ‘n’ for replies, etc. Even if the program will +eventually make most of its output in the foreign languages, one has +to decide whether the input syntax, option values, etc., are to be +localized or not. + +
  • +The manual accompanying a package, as well as all documentation files +in the distribution, could surely be translated, too. Translating a +manual, with the intent of later keeping up with updates, is a major +undertaking in itself, generally. + +
+ +

As we already stressed, translation is only one aspect of locales. +Other internationalization aspects are system services and are handled +in GNU libc. There +are many attributes that are needed to define a country's cultural +conventions. These attributes include beside the country's native +language, the formatting of the date and time, the representation of +numbers, the symbols for currency, etc. These local rules are +termed the country's locale. The locale represents the knowledge +needed to support the country's native attributes. +

+ +

There are a few major areas which may vary between countries and +hence, define what a locale must describe. The following list helps +putting multi-lingual messages into the proper context of other tasks +related to locales. See the GNU libc manual for details. +

+
+
Characters and Codesets
+
+ + + + +

The codeset most commonly used through out the USA and most English +speaking parts of the world is the ASCII codeset. However, there are +many characters needed by various locales that are not found within +this codeset. The 8-bit ISO 8859-1 code set has most of the special +characters needed to handle the major European languages. However, in +many cases, choosing ISO 8859-1 is nevertheless not adequate: it +doesn't even handle the major European currency. Hence each locale +will need to specify which codeset they need to use and will need +to have the appropriate character handling routines to cope with +the codeset. +

+
+
Currency
+
+ + +

The symbols used vary from country to country as does the position +used by the symbol. Software needs to be able to transparently +display currency figures in the native mode for each locale. +

+
+
Dates
+
+ + +

The format of date varies between locales. For example, Christmas day +in 1994 is written as 12/25/94 in the USA and as 25/12/94 in Australia. +Other countries might use ISO 8601 dates, etc. +

+

Time of the day may be noted as hh:mm, hh.mm, +or otherwise. Some locales require time to be specified in 24-hour +mode rather than as AM or PM. Further, the nature and yearly extent +of the Daylight Saving correction vary widely between countries. +

+
+
Numbers
+
+ + +

Numbers can be represented differently in different locales. +For example, the following numbers are all written correctly for +their respective locales: +

+
 
12,345.67       English
+12.345,67       German
+ 12345,67       French
+1,2345.67       Asia
+
+ +

Some programs could go further and use different unit systems, like +English units or Metric units, or even take into account variants +about how numbers are spelled in full. +

+
+
Messages
+
+ + +

The most obvious area is the language support within a locale. This is +where GNU gettext provides the means for developers and users to +easily change the language that the software uses to communicate to +the user. +

+
+
+ + +

These areas of cultural conventions are called locale categories. +It is an unfortunate term; locale aspects or locale feature +categories would be a better term, because each “locale category” +describes an area or task that requires localization. The concrete data +that describes the cultural conventions for such an area and for a particular +culture is also called a locale category. In this sense, a locale +is composed of several locale categories: the locale category describing +the codeset, the locale category describing the formatting of numbers, +the locale category containing the translated messages, and so on. +

+ +

Components of locale outside of message handling are standardized in +the ISO C standard and the POSIX:2001 standard (also known as the SUSV3 +specification). GNU libc +fully implements this, and most other modern systems provide a more +or less reasonable support for at least some of the missing components. +

+ + + +

1.4 Files Conveying Translations

+ +

The letters PO in ‘.po’ files means Portable Object, to +distinguish it from ‘.mo’ files, where MO stands for Machine +Object. This paradigm, as well as the PO file format, is inspired +by the NLS standard developed by Uniforum, and first implemented by +Sun in their Solaris system. +

+

PO files are meant to be read and edited by humans, and associate each +original, translatable string of a given package with its translation +in a particular target language. A single PO file is dedicated to +a single target language. If a package supports many languages, +there is one such PO file per language supported, and each package +has its own set of PO files. These PO files are best created by +the xgettext program, and later updated or refreshed through +the msgmerge program. Program xgettext extracts all +marked messages from a set of C files and initializes a PO file with +empty translations. Program msgmerge takes care of adjusting +PO files between releases of the corresponding sources, commenting +obsolete entries, initializing new ones, and updating all source +line references. Files ending with ‘.pot’ are kind of base +translation files found in distributions, in PO file format. +

+

MO files are meant to be read by programs, and are binary in nature. +A few systems already offer tools for creating and handling MO files +as part of the Native Language Support coming with the system, but the +format of these MO files is often different from system to system, +and non-portable. The tools already provided with these systems don't +support all the features of GNU gettext. Therefore GNU +gettext uses its own format for MO files. Files ending with +‘.gmo’ are really MO files, when it is known that these files use +the GNU format. +

+ + + +

1.5 Overview of GNU gettext

+ +

The following diagram summarizes the relation between the files +handled by GNU gettext and the tools acting on these files. +It is followed by somewhat detailed explanations, which you should +read while keeping an eye on the diagram. Having a clear understanding +of these interrelations will surely help programmers, translators +and maintainers. +

+
 
Original C Sources ───> Preparation ───> Marked C Sources ───╮
+                                                             │
+              ╭─────────<─── GNU gettext Library             │
+╭─── make <───┤                                              │
+│             ╰─────────<────────────────────┬───────────────╯
+│                                            │
+│   ╭─────<─── PACKAGE.pot <─── xgettext <───╯   ╭───<─── PO Compendium
+│   │                                            │              ↑
+│   │                                            ╰───╮          │
+│   ╰───╮                                            ├───> PO editor ───╮
+│       ├────> msgmerge ──────> LANG.po ────>────────╯                  │
+│   ╭───╯                                                               │
+│   │                                                                   │
+│   ╰─────────────<───────────────╮                                     │
+│                                 ├─── New LANG.po <────────────────────╯
+│   ╭─── LANG.gmo <─── msgfmt <───╯
+│   │
+│   ╰───> install ───> /.../LANG/PACKAGE.mo ───╮
+│                                              ├───> "Hello world!"
+╰───────> install ───> /.../bin/PROGRAM ───────╯
+
+ + +

As a programmer, the first step to bringing GNU gettext +into your package is identifying, right in the C sources, those strings +which are meant to be translatable, and those which are untranslatable. +This tedious job can be done a little more comfortably using emacs PO +mode, but you can use any means familiar to you for modifying your +C sources. Beside this some other simple, standard changes are needed to +properly initialize the translation library. See section Preparing Program Sources, for +more information about all this. +

+

For newly written software the strings of course can and should be +marked while writing it. The gettext approach makes this +very easy. Simply put the following lines at the beginning of each file +or in a central header file: +

+
 
#define _(String) (String)
+#define N_(String) String
+#define textdomain(Domain)
+#define bindtextdomain(Package, Directory)
+
+ +

Doing this allows you to prepare the sources for internationalization. +Later when you feel ready for the step to use the gettext library +simply replace these definitions by the following: +

+ +
 
#include <libintl.h>
+#define _(String) gettext (String)
+#define gettext_noop(String) String
+#define N_(String) gettext_noop (String)
+
+ + + +

and link against ‘libintl.a’ or ‘libintl.so’. Note that on +GNU systems, you don't need to link with libintl because the +gettext library functions are already contained in GNU libc. +That is all you have to change. +

+ + +

Once the C sources have been modified, the xgettext program +is used to find and extract all translatable strings, and create a +PO template file out of all these. This ‘package.pot’ file +contains all original program strings. It has sets of pointers to +exactly where in C sources each string is used. All translations +are set to empty. The letter t in ‘.pot’ marks this as +a Template PO file, not yet oriented towards any particular language. +See section Invoking the xgettext Program, for more details about how one calls the +xgettext program. If you are really lazy, you might +be interested at working a lot more right away, and preparing the +whole distribution setup (see section The Maintainer's View). By doing so, you +spare yourself typing the xgettext command, as make +should now generate the proper things automatically for you! +

+

The first time through, there is no ‘lang.po’ yet, so the +msgmerge step may be skipped and replaced by a mere copy of +‘package.pot’ to ‘lang.po’, where lang +represents the target language. See Creating a New PO File for details. +

+

Then comes the initial translation of messages. Translation in +itself is a whole matter, still exclusively meant for humans, +and whose complexity far overwhelms the level of this manual. +Nevertheless, a few hints are given in some other chapter of this +manual (see section The Translator's View). You will also find there indications +about how to contact translating teams, or becoming part of them, +for sharing your translating concerns with others who target the same +native language. +

+

While adding the translated messages into the ‘lang.po’ +PO file, if you are not using one of the dedicated PO file editors +(see section Editing PO Files), you are on your own +for ensuring that your efforts fully respect the PO file format, and quoting +conventions (see section The Format of PO Files). This is surely not an impossible task, +as this is the way many people have handled PO files around 1995. +On the other hand, by using a PO file editor, most details +of PO file format are taken care of for you, but you have to acquire +some familiarity with PO file editor itself. +

+

If some common translations have already been saved into a compendium +PO file, translators may use PO mode for initializing untranslated +entries from the compendium, and also save selected translations into +the compendium, updating it (see section Using Translation Compendia). Compendium files +are meant to be exchanged between members of a given translation team. +

+

Programs, or packages of programs, are dynamic in nature: users write +bug reports and suggestion for improvements, maintainers react by +modifying programs in various ways. The fact that a package has +already been internationalized should not make maintainers shy +of adding new strings, or modifying strings already translated. +They just do their job the best they can. For the Translation +Project to work smoothly, it is important that maintainers do not +carry translation concerns on their already loaded shoulders, and that +translators be kept as free as possible of programming concerns. +

+

The only concern maintainers should have is carefully marking new +strings as translatable, when they should be, and do not otherwise +worry about them being translated, as this will come in proper time. +Consequently, when programs and their strings are adjusted in various +ways by maintainers, and for matters usually unrelated to translation, +xgettext would construct ‘package.pot’ files which are +evolving over time, so the translations carried by ‘lang.po’ +are slowly fading out of date. +

+ +

It is important for translators (and even maintainers) to understand +that package translation is a continuous process in the lifetime of a +package, and not something which is done once and for all at the start. +After an initial burst of translation activity for a given package, +interventions are needed once in a while, because here and there, +translated entries become obsolete, and new untranslated entries +appear, needing translation. +

+

The msgmerge program has the purpose of refreshing an already +existing ‘lang.po’ file, by comparing it with a newer +‘package.pot’ template file, extracted by xgettext +out of recent C sources. The refreshing operation adjusts all +references to C source locations for strings, since these strings +move as programs are modified. Also, msgmerge comments out as +obsolete, in ‘lang.po’, those already translated entries +which are no longer used in the program sources (see section Obsolete Entries). It finally discovers new strings and inserts them in +the resulting PO file as untranslated entries (see section Untranslated Entries). See section Invoking the msgmerge Program, for more information about what +msgmerge really does. +

+

Whatever route or means taken, the goal is to obtain an updated +‘lang.po’ file offering translations for all strings. +

+

The temporal mobility, or fluidity of PO files, is an integral part of +the translation game, and should be well understood, and accepted. +People resisting it will have a hard time participating in the +Translation Project, or will give a hard time to other participants! In +particular, maintainers should relax and include all available official +PO files in their distributions, even if these have not recently been +updated, without exerting pressure on the translator teams to get the +job done. The pressure should rather come +from the community of users speaking a particular language, and +maintainers should consider themselves fairly relieved of any concern +about the adequacy of translation files. On the other hand, translators +should reasonably try updating the PO files they are responsible for, +while the package is undergoing pretest, prior to an official +distribution. +

+

Once the PO file is complete and dependable, the msgfmt program +is used for turning the PO file into a machine-oriented format, which +may yield efficient retrieval of translations by the programs of the +package, whenever needed at runtime (see section The Format of GNU MO Files). See section Invoking the msgfmt Program, for more information about all modes of execution +for the msgfmt program. +

+

Finally, the modified and marked C sources are compiled and linked +with the GNU gettext library, usually through the operation of +make, given a suitable ‘Makefile’ exists for the project, +and the resulting executable is installed somewhere users will find it. +The MO files themselves should also be properly installed. Given the +appropriate environment variables are set (see section Setting the Locale through Environment Variables), +the program should localize itself automatically, whenever it executes. +

+

Shipping the MO files as separate files, +as opposed to embedding them in the executable, +has three advantages: +

    +
  • +For the users: +It allows users to prepare and install new translations, +without needing to rebuild the package (which may require developer skills). +
  • +For the distributors: +It allows distributions to +ship translations that were produced after the release of the package. +
  • +For the vendors of complex packages: +When lengthy quality assurance steps are required before making a release, +this quality assurance can start +before the translators have produced the translations, +shortening the critical path of the release schedule by a week or two. +
+

Embedding the translations in the executable, +whether by the ISO C #embed directive or through other means, +would deprive users without developer skills +of the ability to fix translation mistakes and add new translations. +

+

The remainder of this manual has the purpose of explaining in depth the various +steps outlined above. +

+ + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_10.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_10.html new file mode 100644 index 0000000000000000000000000000000000000000..306b8e9f6dc834dd57d1971d48bf312b2bb06f07 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_10.html @@ -0,0 +1,1047 @@ + + + + + +GNU gettext utilities: 10. Producing Binary MO Files + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

10. Producing Binary MO Files

+ + + + + + +

10.1 Invoking the msgfmt Program

+ + +
 
msgfmt [option] filename.po …
+
+ + +

The msgfmt programs generates a binary message catalog from a textual +translation description. +

+ + +

10.1.1 Input file location

+ +
+
‘filename.po …’
+
‘-D directory’
+
‘--directory=directory’
+
+ +

Add directory to the list of directories. Source files are +searched relative to this list of directories. The resulting binary +file will be written relative to the current directory, though. +

+
+
+ +

If an input file is ‘-’, standard input is read. +

+ + +

10.1.2 Operation mode

+ +
+
‘-j’
+
‘--java’
+
+ + +

Java mode: generate a Java ResourceBundle class. +

+
+
‘--java2’
+
+

Like –java, and assume Java2 (JDK 1.2 or higher). +

+
+
‘--csharp’
+
+ +

C# mode: generate a .NET .dll file containing a subclass of +GettextResourceSet. +

+
+
‘--csharp-resources’
+
+ +

C# resources mode: generate a .NET ‘.resources’ file. +

+
+
‘--tcl’
+
+ +

Tcl mode: generate a tcl/msgcat ‘.msg’ file. +

+
+
‘--qt’
+
+ +

Qt mode: generate a Qt ‘.qm’ file. +

+
+
‘--desktop’
+
+ +

Desktop Entry mode: generate a ‘.desktop’ file. +

+
+
‘--xml’
+
+ +

XML mode: generate an XML file. +

+
+
+ + + +

10.1.3 Output file location

+ +
+
‘-o file’
+
‘--output-file=file’
+
+ +

Write output to specified file. +

+
+
‘--strict’
+
+

Direct the program to work strictly following the Uniforum/Sun +implementation. Currently this only affects the naming of the output +file. If this option is not given the name of the output file is the +same as the domain name. If the strict Uniforum mode is enabled the +suffix ‘.mo’ is added to the file name if it is not already +present. +

+

We find this behaviour of Sun's implementation rather silly and so by +default this mode is not selected. +

+
+
+ +

If the output file is ‘-’, output is written to standard output. +

+ + +

10.1.4 Output file location in Java mode

+ +
+
‘-r resource’
+
‘--resource=resource’
+
+ +

Specify the resource name. +

+
+
‘-l locale’
+
‘--locale=locale’
+
+ +

Specify the locale name, either a language specification of the form ll +or a combined language and country specification of the form ll_CC. +

+
+
‘-d directory’
+
+

Specify the base directory of classes directory hierarchy. +

+
+
‘--source’
+
+

Produce a .java source file, instead of a compiled .class file. +

+
+
+ +

The class name is determined by appending the locale name to the resource name, +separated with an underscore. The ‘-d’ option is mandatory. The class +is written under the specified directory. +

+ + +

10.1.5 Output file location in C# mode

+ +
+
‘-r resource’
+
‘--resource=resource’
+
+ +

Specify the resource name. +

+
+
‘-l locale’
+
‘--locale=locale’
+
+ +

Specify the locale name, either a language specification of the form ll +or a combined language and country specification of the form ll_CC. +

+
+
‘-d directory’
+
+

Specify the base directory for locale dependent ‘.dll’ files. +

+
+
+ +

The ‘-l’ and ‘-d’ options are mandatory. The ‘.dll’ file is +written in a subdirectory of the specified directory whose name depends on the +locale. +

+ + +

10.1.6 Output file location in Tcl mode

+ +
+
‘-l locale’
+
‘--locale=locale’
+
+ +

Specify the locale name, either a language specification of the form ll +or a combined language and country specification of the form ll_CC. +

+
+
‘-d directory’
+
+

Specify the base directory of ‘.msg’ message catalogs. +

+
+
+ +

The ‘-l’ and ‘-d’ options are mandatory. The ‘.msg’ file is +written in the specified directory. +

+ + +

10.1.7 Desktop Entry mode options

+ +
+
‘--template=template’
+
+

Specify a .desktop file used as a template. +

+
+
‘-k[keywordspec]’
+
‘--keyword[=keywordspec]’
+
+ +

Specify keywordspec as an additional keyword to be looked for. +Without a keywordspec, the option means to not use default keywords. +

+
+
‘-l locale’
+
‘--locale=locale’
+
+ +

Specify the locale name, either a language specification of the form ll +or a combined language and country specification of the form ll_CC. +

+
+
‘-d directory’
+
+

Specify the directory where PO files are read. The directory must +contain the ‘LINGUAS’ file. +

+
+
+ +

To generate a ‘.desktop’ file for a single locale, you can use it +as follows. +

+
 
msgfmt --desktop --template=template --locale=locale \
+  -o file filename.po …
+
+ +

msgfmt provides a special "bulk" operation mode to process multiple +‘.po’ files at a time. +

+
 
msgfmt --desktop --template=template -d directory -o file
+
+ +

msgfmt first reads the ‘LINGUAS’ file under directory, and +then processes all ‘.po’ files listed there. You can also limit +the locales to a subset, through the ‘LINGUAS’ environment +variable. +

+

For either operation modes, the ‘-o’ and ‘--template’ +options are mandatory. +

+ + +

10.1.8 XML mode options

+ +
+
‘--template=template’
+
+

Specify an XML file used as a template. +

+
+
‘-L name’
+
‘--language=name’
+
+ + +

Specifies the language of the input files. +

+
+
‘-l locale’
+
‘--locale=locale’
+
+ +

Specify the locale name, either a language specification of the form ll +or a combined language and country specification of the form ll_CC. +

+
+
‘-d directory’
+
+

Specify the base directory of ‘.po’ message catalogs. +

+
+
‘--replace-text’
+
+

Output XML with translated text replacing the original text, +not augmenting the original text. +With this option, msgfmt produces a mono-lingual XML file. +Without this option, it produces a multi-lingual XML file. +

+
+ +

To generate an XML file for a single locale, you can use it as follows. +

+
 
msgfmt --xml --template=template --locale=locale \
+  -o file filename.po …
+
+ +

msgfmt provides a special "bulk" operation mode to process multiple +‘.po’ files at a time. +

+
 
msgfmt --xml --template=template -d directory -o file
+
+ +

msgfmt first reads the ‘LINGUAS’ file under directory, and +then processes all ‘.po’ files listed there. You can also limit +the locales to a subset, through the ‘LINGUAS’ environment +variable. +

+

For either operation modes, the ‘-o’ and ‘--template’ +options are mandatory. +

+

If your XML file is not of one of the types covered by the system-wide +installed *.its files, +you need a particular *.its file and a corresponding *.loc file +(see section Preparing Rules for XML Internationalization). +Furthermore you need to store these files +in a directory ‘parent_dir/its/’ + +and set the environment variable GETTEXTDATADIRS to include +parent_dir. +More generally, the value of GETTEXTDATADIRS should be +a colon-separated list of directory names. +

+ + +

10.1.9 Input file syntax

+ +
+
‘-P’
+
‘--properties-input’
+
+ +

Assume the input files are Java ResourceBundles in Java .properties +syntax, not in PO file syntax. +

+
+
‘--stringtable-input’
+
+

Assume the input files are NeXTstep/GNUstep localized resource files in +.strings syntax, not in PO file syntax. +

+
+
+ + + +

10.1.10 Input file interpretation

+ +
+
‘-c’
+
‘--check’
+
+ +

Perform all the checks implied by --check-format, --check-header, +--check-domain. +

+
+
‘--check-format’
+
+ +

Check language dependent format strings. +

+

If the string represents a format string used in a +printf-like function both strings should have the same number of +‘%’ format specifiers, with matching types. If the flag +c-format or possible-c-format appears in the special +comment <#,> for this entry a check is performed. For example, the +check will diagnose using ‘%.*s’ against ‘%s’, or ‘%d’ +against ‘%s’, or ‘%d’ against ‘%x’. It can even handle +positional parameters. +

+

Normally the xgettext program automatically decides whether a +string is a format string or not. This algorithm is not perfect, +though. It might regard a string as a format string though it is not +used in a printf-like function and so msgfmt might report +errors where there are none. +

+

To solve this problem the programmer can dictate the decision to the +xgettext program (see section C Format Strings). The translator should not +consider removing the flag from the <#,> line. This "fix" would be +reversed again as soon as msgmerge is called the next time. +

+
+
‘--check-header’
+
+

Verify presence and contents of the header entry. See section Filling in the Header Entry, +for a description of the various fields in the header entry. +

+
+
‘--check-domain’
+
+

Check for conflicts between domain directives and the --output-file +option +

+
+
‘-C’
+
‘--check-compatibility’
+
+ + +

Check that GNU msgfmt behaves like X/Open msgfmt. This will give an error +when attempting to use the GNU extensions. +

+
+
‘--check-accelerators[=char]’
+
+ + + +

Check presence of keyboard accelerators for menu items. This is based on +the convention used in some GUIs that a keyboard accelerator in a menu +item string is designated by an immediately preceding ‘&’ character. +Sometimes a keyboard accelerator is also called "keyboard mnemonic". +This check verifies that if the untranslated string has exactly one +‘&’ character, the translated string has exactly one ‘&’ as well. +If this option is given with a char argument, this char should +be a non-alphanumeric character and is used as keyboard accelerator mark +instead of ‘&’. +

+
+
‘-f’
+
‘--use-fuzzy’
+
+ + +

Use fuzzy entries in output. Note that using this option is usually wrong, +because fuzzy messages are exactly those which have not been validated by +a human translator. +

+
+
+ + + +

10.1.11 Output details

+ +
+
‘--no-convert’
+
+

Don't convert the messages to UTF-8 encoding. By default, messages are +converted to UTF-8 encoding before being stored in a MO file; this helps +avoiding conversions at run time, since nowadays most locales use the +UTF-8 encoding. +

+
+
‘--no-redundancy’
+
+

Don't pre-expand ISO C 99 <inttypes.h> format string directive macros. +By default, messages that are marked as c-format and contain +ISO C 99 <inttypes.h> format string directive macros are pre-expanded +for selected platforms, and these redundant expansions are stored in the +MO file. These redundant expansions make the translations of these +messages work with the gettext implementation in the libc +of that platform, without requiring GNU gettext's libintl. +The platforms that benefit from this pre-expansion are those with the +musl libc. +

+
+
‘-a number’
+
‘--alignment=number’
+
+ +

Align strings to number bytes (default: 1). +

+
+
‘--endianness=byteorder’
+
+

Write out 32-bit numbers in the given byte order. The possible values are +big and little. The default is little. +

+

MO files of any endianness can be used on any platform. When a MO file has +an endianness other than the platform's one, the 32-bit numbers from the MO +file are swapped at runtime. The performance impact is negligible. +

+

This option can be useful to produce MO files that are optimized for one +platform. +

+
+
‘--no-hash’
+
+

Don't include a hash table in the binary file. Lookup will be more expensive +at run time (binary search instead of hash table lookup). +

+
+
+ + + +

10.1.12 Informative output

+ +
+
‘-h’
+
‘--help’
+
+ +

Display this help and exit. +

+
+
‘-V’
+
‘--version’
+
+ +

Output version information and exit. +

+
+
‘--statistics’
+
+

Print statistics about translations. When the option --verbose is used +in combination with --statistics, the input file name is printed in +front of the statistics line. +

+
+
‘-v’
+
‘--verbose’
+
+ +

Increase verbosity level. +

+
+
+ + + + +

10.2 Invoking the msgunfmt Program

+ + +
 
msgunfmt [option] [file]...
+
+ + +

The msgunfmt program converts a binary message catalog to a +Uniforum style .po file. +

+ + +

10.2.1 Operation mode

+ +
+
‘-j’
+
‘--java’
+
+ + +

Java mode: input is a Java ResourceBundle class. +

+
+
‘--csharp’
+
+ +

C# mode: input is a .NET .dll file containing a subclass of +GettextResourceSet. +

+
+
‘--csharp-resources’
+
+ +

C# resources mode: input is a .NET ‘.resources’ file. +

+
+
‘--tcl’
+
+ +

Tcl mode: input is a tcl/msgcat ‘.msg’ file. +

+
+
+ + + +

10.2.2 Input file location

+ +
+
‘file …’
+

Input .mo files. +

+
+
+ +

If no input file is given or if it is ‘-’, standard input is read. +

+ + +

10.2.3 Input file location in Java mode

+ +
+
‘-r resource’
+
‘--resource=resource’
+
+ +

Specify the resource name. +

+
+
‘-l locale’
+
‘--locale=locale’
+
+ +

Specify the locale name, either a language specification of the form ll +or a combined language and country specification of the form ll_CC. +

+
+
+ +

The class name is determined by appending the locale name to the resource name, +separated with an underscore. The class is located using the CLASSPATH. +

+ + +

10.2.4 Input file location in C# mode

+ +
+
‘-r resource’
+
‘--resource=resource’
+
+ +

Specify the resource name. +

+
+
‘-l locale’
+
‘--locale=locale’
+
+ +

Specify the locale name, either a language specification of the form ll +or a combined language and country specification of the form ll_CC. +

+
+
‘-d directory’
+
+

Specify the base directory for locale dependent ‘.dll’ files. +

+
+
+ +

The ‘-l’ and ‘-d’ options are mandatory. The ‘.msg’ file is +located in a subdirectory of the specified directory whose name depends on the +locale. +

+ + +

10.2.5 Input file location in Tcl mode

+ +
+
‘-l locale’
+
‘--locale=locale’
+
+ +

Specify the locale name, either a language specification of the form ll +or a combined language and country specification of the form ll_CC. +

+
+
‘-d directory’
+
+

Specify the base directory of ‘.msg’ message catalogs. +

+
+
+ +

The ‘-l’ and ‘-d’ options are mandatory. The ‘.msg’ file is +located in the specified directory. +

+ + +

10.2.6 Output file location

+ +
+
‘-o file’
+
‘--output-file=file’
+
+ +

Write output to specified file. +

+
+
+ +

The results are written to standard output if no output file is specified +or if it is ‘-’. +

+ + +

10.2.7 Output details

+ + +
+
‘--color’
+
‘--color=when’
+
+

Specify whether or when to use colors and other text attributes. +See The --color option for details. +

+
+
‘--style=style_file’
+
+

Specify the CSS style rule file to use for --color. +See The --style option for details. +

+
+
‘--force-po’
+
+

Always write an output file even if it contains no message. +

+
+
‘-i’
+
‘--indent’
+
+ +

Write the .po file using indented style. +

+
+
‘--strict’
+
+

Write out a strict Uniforum conforming PO file. Note that this +Uniforum format should be avoided because it doesn't support the +GNU extensions. +

+
+
‘-p’
+
‘--properties-output’
+
+ +

Write out a Java ResourceBundle in Java .properties syntax. Note +that this file format doesn't support plural forms and silently drops +obsolete messages. +

+
+
‘--stringtable-output’
+
+

Write out a NeXTstep/GNUstep localized resource file in .strings syntax. +Note that this file format doesn't support plural forms. +

+
+
‘-w number’
+
‘--width=number’
+
+ +

Set the output page width. Long strings in the output files will be +split across multiple lines in order to ensure that each line's width +(= number of screen columns) is less or equal to the given number. +

+
+
‘--no-wrap’
+
+

Do not break long message lines. Message lines whose width exceeds the +output page width will not be split into several lines. Only file reference +lines which are wider than the output page width will be split. +

+
+
‘-s’
+
‘--sort-output’
+
+ + +

Generate sorted output. Note that using this option makes it much harder +for the translator to understand each message's context. +

+
+
+ + + +

10.2.8 Informative output

+ +
+
‘-h’
+
‘--help’
+
+ +

Display this help and exit. +

+
+
‘-V’
+
‘--version’
+
+ +

Output version information and exit. +

+
+
‘-v’
+
‘--verbose’
+
+ +

Increase verbosity level. +

+
+
+ + + + +

10.3 The Format of GNU MO Files

+ +

The format of the generated MO files is best described by a picture, +which appears below. +

+ +

The first two words serve the identification of the file. The magic +number will always signal GNU MO files. The number is stored in the +byte order used when the MO file was generated, so the magic number +really is two numbers: 0x950412de and 0xde120495. +

+

The second word describes the current revision of the file format, +composed of a major and a minor revision number. The revision numbers +ensure that the readers of MO files can distinguish new formats from +old ones and handle their contents, as far as possible. For now the +major revision is 0 or 1, and the minor revision is also 0 or 1. More +revisions might be added in the future. A program seeing an unexpected +major revision number should stop reading the MO file entirely; whereas +an unexpected minor revision number means that the file can be read but +will not reveal its full contents, when parsed by a program that +supports only smaller minor revision numbers. +

+

The version is kept +separate from the magic number, instead of using different magic +numbers for different formats, mainly because ‘/etc/magic’ is +not updated often. +

+

Follow a number of pointers to later tables in the file, allowing +for the extension of the prefix part of MO files without having to +recompile programs reading them. This might become useful for later +inserting a few flag bits, indication about the charset used, new +tables, or other things. +

+

Then, at offset O and offset T in the picture, two tables +of string descriptors can be found. In both tables, each string +descriptor uses two 32 bits integers, one for the string length, +another for the offset of the string in the MO file, counting in bytes +from the start of the file. The first table contains descriptors +for the original strings, and is sorted so the original strings +are in increasing lexicographical order. The second table contains +descriptors for the translated strings, and is parallel to the first +table: to find the corresponding translation one has to access the +array slot in the second array with the same index. +

+

Having the original strings sorted enables the use of simple binary +search, for when the MO file does not contain an hashing table, or +for when it is not practical to use the hashing table provided in +the MO file. This also has another advantage, as the empty string +in a PO file GNU gettext is usually translated into +some system information attached to that particular MO file, and the +empty string necessarily becomes the first in both the original and +translated tables, making the system information very easy to find. +

+ +

The size S of the hash table can be zero. In this case, the +hash table itself is not contained in the MO file. Some people might +prefer this because a precomputed hashing table takes disk space, and +does not win that much speed. The hash table contains indices +to the sorted array of strings in the MO file. Conflict resolution is +done by double hashing. The precise hashing algorithm used is fairly +dependent on GNU gettext code, and is not documented here. +

+

As for the strings themselves, they follow the hash file, and each +is terminated with a <NUL>, and this <NUL> is not counted in +the length which appears in the string descriptor. The msgfmt +program has an option selecting the alignment for MO file strings. +With this option, each string is separately aligned so it starts at +an offset which is a multiple of the alignment value. On some RISC +machines, a correct alignment will speed things up. +

+ +

Contexts are stored by storing the concatenation of the context, a +<EOT> byte, and the original string, instead of the original string. +

+ +

Plural forms are stored by letting the plural of the original string +follow the singular of the original string, separated through a +<NUL> byte. The length which appears in the string descriptor +includes both. However, only the singular of the original string +takes part in the hash table lookup. The plural variants of the +translation are all stored consecutively, separated through a +<NUL> byte. Here also, the length in the string descriptor +includes all of them. +

+ +

The character encoding of the strings can be any standard ASCII-compatible +encoding, such as UTF-8, ISO-8859-1, EUC-JP, etc., as long as the +encoding's name is stated in the header entry (see section Filling in the Header Entry). +Starting with GNU gettext version 0.22, the MO files produced by +msgfmt have them in UTF-8 encoding, unless the msgfmt +option ‘--no-convert’ is used. +

+

Nothing prevents a MO file from having embedded <NUL>s in strings. +However, the program interface currently used already presumes +that strings are <NUL> terminated, so embedded <NUL>s are +somewhat useless. But the MO file format is general enough so other +interfaces would be later possible, if for example, we ever want to +implement wide characters right in MO files, where <NUL> bytes may +accidentally appear. (No, we don't want to have wide characters in MO +files. They would make the file unnecessarily large, and the +‘wchar_t’ type being platform dependent, MO files would be +platform dependent as well.) +

+

This particular issue has been strongly debated in the GNU +gettext development forum, and it is expectable that MO file +format will evolve or change over time. It is even possible that many +formats may later be supported concurrently. But surely, we have to +start somewhere, and the MO file format described here is a good start. +Nothing is cast in concrete, and the format may later evolve fairly +easily, so we should feel comfortable with the current approach. +

+
 
        byte
+             +------------------------------------------+
+          0  | magic number = 0x950412de                |
+             |                                          |
+          4  | file format revision = 0                 |
+             |                                          |
+          8  | number of strings                        |  == N
+             |                                          |
+         12  | offset of table with original strings    |  == O
+             |                                          |
+         16  | offset of table with translation strings |  == T
+             |                                          |
+         20  | size of hashing table                    |  == S
+             |                                          |
+         24  | offset of hashing table                  |  == H
+             |                                          |
+             .                                          .
+             .    (possibly more entries later)         .
+             .                                          .
+             |                                          |
+          O  | length & offset 0th string  ----------------.
+      O + 8  | length & offset 1st string  ------------------.
+              ...                                    ...   | |
+O + ((N-1)*8)| length & offset (N-1)th string           |  | |
+             |                                          |  | |
+          T  | length & offset 0th translation  ---------------.
+      T + 8  | length & offset 1st translation  -----------------.
+              ...                                    ...   | | | |
+T + ((N-1)*8)| length & offset (N-1)th translation      |  | | | |
+             |                                          |  | | | |
+          H  | start hash table                         |  | | | |
+              ...                                    ...   | | | |
+  H + S * 4  | end hash table                           |  | | | |
+             |                                          |  | | | |
+             | NUL terminated 0th string  <----------------' | | |
+             |                                          |    | | |
+             | NUL terminated 1st string  <------------------' | |
+             |                                          |      | |
+              ...                                    ...       | |
+             |                                          |      | |
+             | NUL terminated 0th translation  <---------------' |
+             |                                          |        |
+             | NUL terminated 1st translation  <-----------------'
+             |                                          |
+              ...                                    ...
+             |                                          |
+             +------------------------------------------+
+
+ + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_11.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_11.html new file mode 100644 index 0000000000000000000000000000000000000000..c806b022d3288529b6c2b2f9423ae9b7fca12199 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_11.html @@ -0,0 +1,1427 @@ + + + + + +GNU gettext utilities: 11. The Programmer's View + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

11. The Programmer's View

+ + +

One aim of the current message catalog implementation provided by +GNU gettext was to use the system's message catalog handling, if the +installer wishes to do so. So we perhaps should first take a look at +the solutions we know about. The people in the POSIX committee did not +manage to agree on one of the semi-official standards which we'll +describe below. In fact they couldn't agree on anything, so they decided +only to include an example of an interface. The major Unix vendors +are split in the usage of the two most important specifications: X/Open's +catgets vs. Uniforum's gettext interface. We'll describe them both and +later explain our solution of this dilemma. +

+ + + + +

11.1 About catgets

+ +

The catgets implementation is defined in the X/Open Portability +Guide, Volume 3, XSI Supplementary Definitions, Chapter 5. But the +process of creating this standard seemed to be too slow for some of +the Unix vendors so they created their implementations on preliminary +versions of the standard. Of course this leads again to problems while +writing platform independent programs: even the usage of catgets +does not guarantee a unique interface. +

+

Another, personal comment on this that only a bunch of committee members +could have made this interface. They never really tried to program +using this interface. It is a fast, memory-saving implementation, an +user can happily live with it. But programmers hate it (at least I and +some others do…) +

+

But we must not forget one point: after all the trouble with transferring +the rights on Unix they at last came to X/Open, the very same who +published this specification. This leads me to making the prediction +that this interface will be in future Unix standards (e.g. Spec1170) and +therefore part of all Unix implementation (implementations, which are +allowed to wear this name). +

+ + + + +

11.1.1 The Interface

+ +

The interface to the catgets implementation consists of three +functions which correspond to those used in file access: catopen +to open the catalog for using, catgets for accessing the message +tables, and catclose for closing after work is done. Prototypes +for the functions and the needed definitions are in the +<nl_types.h> header file. +

+ +

catopen is used like in this: +

+
 
nl_catd catd = catopen ("catalog_name", 0);
+
+ +

The function takes as the argument the name of the catalog. This usual +refers to the name of the program or the package. The second parameter +is not further specified in the standard. I don't even know whether it +is implemented consistently among various systems. So the common advice +is to use 0 as the value. The return value is a handle to the +message catalog, equivalent to handles to file returned by open. +

+ +

This handle is of course used in the catgets function which can +be used like this: +

+
 
char *translation = catgets (catd, set_no, msg_id, "original string");
+
+ +

The first parameter is this catalog descriptor. The second parameter +specifies the set of messages in this catalog, in which the message +described by msg_id is obtained. catgets therefore uses a +three-stage addressing: +

+
 
catalog name ⇒ set number ⇒ message ID ⇒ translation
+
+ + +

The fourth argument is not used to address the translation. It is given +as a default value in case when one of the addressing stages fail. One +important thing to remember is that although the return type of catgets +is char * the resulting string must not be changed. It +should better be const char *, but the standard is published in +1988, one year before ANSI C. +

+ +

The last of these functions is used and behaves as expected: +

+
 
catclose (catd);
+
+ +

After this no catgets call using the descriptor is legal anymore. +

+ + + +

11.1.2 Problems with the catgets Interface?!

+ +

Now that this description seemed to be really easy — where are the +problems we speak of? In fact the interface could be used in a +reasonable way, but constructing the message catalogs is a pain. The +reason for this lies in the third argument of catgets: the unique +message ID. This has to be a numeric value for all messages in a single +set. Perhaps you could imagine the problems keeping such a list while +changing the source code. Add a new message here, remove one there. Of +course there have been developed a lot of tools helping to organize this +chaos but one as the other fails in one aspect or the other. We don't +want to say that the other approach has no problems but they are far +more easy to manage. +

+ + + +

11.2 About gettext

+ +

The definition of the gettext interface comes from a Uniforum +proposal. It was submitted there by Sun, who had implemented the +gettext function in SunOS 4, around 1990. Nowadays, the +gettext interface is specified by the OpenI18N standard. +

+

The main point about this solution is that it does not follow the +method of normal file handling (open-use-close) and that it does not +burden the programmer with so many tasks, especially the unique key handling. +Of course here also a unique key is needed, but this key is the message +itself (how long or short it is). See Comparing the Two Interfaces for a more +detailed comparison of the two methods. +

+

The following section contains a rather detailed description of the +interface. We make it that detailed because this is the interface +we chose for the GNU gettext Library. Programmers interested +in using this library will be interested in this description. +

+ + + + +

11.2.1 The Interface

+ +

The minimal functionality an interface must have is a) to select a +domain the strings are coming from (a single domain for all programs is +not reasonable because its construction and maintenance is difficult, +perhaps impossible) and b) to access a string in a selected domain. +

+

This is principally the description of the gettext interface. It +has a global domain which unqualified usages reference. Of course this +domain is selectable by the user. +

+
 
char *textdomain (const char *domain_name);
+
+ +

This provides the possibility to change or query the current status of +the current global domain of the LC_MESSAGE category. The +argument is a null-terminated string, whose characters must be legal in +the use in filenames. If the domain_name argument is NULL, +the function returns the current value. If no value has been set +before, the name of the default domain is returned: messages. +Please note that although the return value of textdomain is of +type char * no changing is allowed. It is also important to know +that no checks of the availability are made. If the name is not +available you will see this by the fact that no translations are provided. +

+

To use a domain set by textdomain the function +

+
 
char *gettext (const char *msgid);
+
+ +

is to be used. This is the simplest reasonable form one can imagine. +The translation of the string msgid is returned if it is available +in the current domain. If it is not available, the argument itself is +returned. If the argument is NULL the result is undefined. +

+

One thing which should come into mind is that no explicit dependency to +the used domain is given. The current value of the domain is used. +If this changes between two +executions of the same gettext call in the program, both calls +reference a different message catalog. +

+

For the easiest case, which is normally used in internationalized +packages, once at the beginning of execution a call to textdomain +is issued, setting the domain to a unique name, normally the package +name. In the following code all strings which have to be translated are +filtered through the gettext function. That's all, the package speaks +your language. +

+ + + +

11.2.2 Solving Ambiguities

+ +

While this single name domain works well for most applications there +might be the need to get translations from more than one domain. Of +course one could switch between different domains with calls to +textdomain, but this is really not convenient nor is it fast. A +possible situation could be one case subject to discussion during this +writing: all +error messages of functions in the set of common used functions should +go into a separate domain error. By this mean we would only need +to translate them once. +Another case are messages from a library, as these have to be +independent of the current domain set by the application. +

+

For this reasons there are two more functions to retrieve strings: +

+
 
char *dgettext (const char *domain_name, const char *msgid);
+char *dcgettext (const char *domain_name, const char *msgid,
+                 int category);
+
+ +

Both take an additional argument at the first place, which corresponds +to the argument of textdomain. The third argument of +dcgettext allows to use another locale category but LC_MESSAGES. +But I really don't know where this can be useful. If the +domain_name is NULL or category has an value beside +the known ones, the result is undefined. It should also be noted that +this function is not part of the second known implementation of this +function family, the one found in Solaris. +

+

A second ambiguity can arise by the fact, that perhaps more than one +domain has the same name. This can be solved by specifying where the +needed message catalog files can be found. +

+
 
char *bindtextdomain (const char *domain_name,
+                      const char *dir_name);
+
+ +

Calling this function binds the given domain to a file in the specified +directory (how this file is determined follows below). Especially a +file in the systems default place is not favored against the specified +file anymore (as it would be by solely using textdomain). A +NULL pointer for the dir_name parameter returns the binding +associated with domain_name. If domain_name itself is +NULL nothing happens and a NULL pointer is returned. Here +again as for all the other functions is true that none of the return +value must be changed! +

+

It is important to remember that relative path names for the +dir_name parameter can be trouble. Since the path is always +computed relative to the current directory different results will be +achieved when the program executes a chdir command. Relative +paths should always be avoided to avoid dependencies and +unreliabilities. +

+
 
wchar_t *wbindtextdomain (const char *domain_name,
+                          const wchar_t *dir_name);
+
+ +

This function is provided only on native Windows platforms. It is like +bindtextdomain, except that the dir_name parameter is a +wide string (in UTF-16 encoding, as usual on Windows). +

+ + + +

11.2.3 Locating Message Catalog Files

+ +

Because many different languages for many different packages have to be +stored we need some way to add these information to file message catalog +files. The way usually used in Unix environments is have this encoding +in the file name. This is also done here. The directory name given in +bindtextdomains second argument (or the default directory), +followed by the name of the locale, the locale category, and the domain name +are concatenated: +

+
 
dir_name/locale/LC_category/domain_name.mo
+
+ +

The default value for dir_name is system specific. For the GNU +library, and for packages adhering to its conventions, it's: +

 
/usr/local/share/locale
+
+ +

locale is the name of the locale category which is designated by +LC_category. For gettext and dgettext this +LC_category is always LC_MESSAGES.(3) +The name of the locale category is determined through +setlocale (LC_category, NULL). +(4) +When using the function dcgettext, you can specify the locale category +through the third argument. +

+ + + +

11.2.4 How to specify the output character set gettext uses

+ +

gettext not only looks up a translation in a message catalog. It +also converts the translation on the fly to the desired output character +set. This is useful if the user is working in a different character set +than the translator who created the message catalog, because it avoids +distributing variants of message catalogs which differ only in the +character set. +

+

The output character set is, by default, the value of nl_langinfo +(CODESET), which depends on the LC_CTYPE part of the current +locale. But programs which store strings in a locale independent way +(e.g. UTF-8) can request that gettext and related functions +return the translations in that encoding, by use of the +bind_textdomain_codeset function. +

+

Note that the msgid argument to gettext is not subject to +character set conversion. Also, when gettext does not find a +translation for msgid, it returns msgid unchanged – +independently of the current output character set. It is therefore +recommended that all msgids be US-ASCII strings. +

+
+
Function: char * bind_textdomain_codeset (const char *domainname, const char *codeset) + +
+

The bind_textdomain_codeset function can be used to specify the +output character set for message catalogs for domain domainname. +The codeset argument must be a valid codeset name which can be used +for the iconv_open function, or a null pointer. +

+

If the codeset parameter is the null pointer, +bind_textdomain_codeset returns the currently selected codeset +for the domain with the name domainname. It returns NULL if +no codeset has yet been selected. +

+

The bind_textdomain_codeset function can be used several times. +If used multiple times with the same domainname argument, the +later call overrides the settings made by the earlier one. +

+

The bind_textdomain_codeset function returns a pointer to a +string containing the name of the selected codeset. The string is +allocated internally in the function and must not be changed by the +user. If the system went out of core during the execution of +bind_textdomain_codeset, the return value is NULL and the +global variable errno is set accordingly. +

+ + + + +

11.2.5 Using contexts for solving ambiguities

+ +

One place where the gettext functions, if used normally, have big +problems is within programs with graphical user interfaces (GUIs). The +problem is that many of the strings which have to be translated are very +short. They have to appear in pull-down menus which restricts the +length. But strings which are not containing entire sentences or at +least large fragments of a sentence may appear in more than one +situation in the program but might have different translations. This is +especially true for the one-word strings which are frequently used in +GUI programs. +

+

As a consequence many people say that the gettext approach is +wrong and instead catgets should be used which indeed does not +have this problem. But there is a very simple and powerful method to +handle this kind of problems with the gettext functions. +

+

Contexts can be added to strings to be translated. A context dependent +translation lookup is when a translation for a given string is searched, +that is limited to a given context. The translation for the same string +in a different context can be different. The different translations of +the same string in different contexts can be stored in the in the same +MO file, and can be edited by the translator in the same PO file. +

+

The ‘gettext.h’ include file contains the lookup macros for strings +with contexts. They are implemented as thin macros and inline functions +over the functions from <libintl.h>. +

+ +
 
const char *pgettext (const char *msgctxt, const char *msgid);
+
+ +

In a call of this macro, msgctxt and msgid must be string +literals. The macro returns the translation of msgid, restricted +to the context given by msgctxt. +

+

The msgctxt string is visible in the PO file to the translator. +You should try to make it somehow canonical and never changing. Because +every time you change an msgctxt, the translator will have to review +the translation of msgid. +

+

Finding a canonical msgctxt string that doesn't change over time can +be hard. But you shouldn't use the file name or class name containing the +pgettext call – because it is a common development task to rename +a file or a class, and it shouldn't cause translator work. Also you shouldn't +use a comment in the form of a complete English sentence as msgctxt – +because orthography or grammar changes are often applied to such sentences, +and again, it shouldn't force the translator to do a review. +

+

The ‘p’ in ‘pgettext’ stands for “particular”: pgettext +fetches a particular translation of the msgid. +

+ + +
 
const char *dpgettext (const char *domain_name,
+                       const char *msgctxt, const char *msgid);
+const char *dcpgettext (const char *domain_name,
+                        const char *msgctxt, const char *msgid,
+                        int category);
+
+ +

These are generalizations of pgettext. They behave similarly to +dgettext and dcgettext, respectively. The domain_name +argument defines the translation domain. The category argument +allows to use another locale category than LC_MESSAGES. +

+

As as example consider the following fictional situation. A GUI program +has a menu bar with the following entries: +

+
 
+------------+------------+--------------------------------------+
+| File       | Printer    |                                      |
++------------+------------+--------------------------------------+
+| Open     | | Select   |
+| New      | | Open     |
++----------+ | Connect  |
+             +----------+
+
+ +

To have the strings File, Printer, Open, +New, Select, and Connect translated there has to be +at some point in the code a call to a function of the gettext +family. But in two places the string passed into the function would be +Open. The translations might not be the same and therefore we +are in the dilemma described above. +

+

What distinguishes the two places is the menu path from the menu root to +the particular menu entries: +

+
 
Menu|File
+Menu|Printer
+Menu|File|Open
+Menu|File|New
+Menu|Printer|Select
+Menu|Printer|Open
+Menu|Printer|Connect
+
+ +

The context is thus the menu path without its last part. So, the calls +look like this: +

+
 
pgettext ("Menu|", "File")
+pgettext ("Menu|", "Printer")
+pgettext ("Menu|File|", "Open")
+pgettext ("Menu|File|", "New")
+pgettext ("Menu|Printer|", "Select")
+pgettext ("Menu|Printer|", "Open")
+pgettext ("Menu|Printer|", "Connect")
+
+ +

Whether or not to use the ‘|’ character at the end of the context is a +matter of style. +

+

For more complex cases, where the msgctxt or msgid are not +string literals, more general macros are available: +

+ + + +
 
const char *pgettext_expr (const char *msgctxt, const char *msgid);
+const char *dpgettext_expr (const char *domain_name,
+                            const char *msgctxt, const char *msgid);
+const char *dcpgettext_expr (const char *domain_name,
+                             const char *msgctxt, const char *msgid,
+                             int category);
+
+ +

Here msgctxt and msgid can be arbitrary string-valued expressions. +These macros are more general. But in the case that both argument expressions +are string literals, the macros without the ‘_expr’ suffix are more +efficient. +

+ + + +

11.2.6 Additional functions for plural forms

+ +

The functions of the gettext family described so far (and all the +catgets functions as well) have one problem in the real world +which have been neglected completely in all existing approaches. What +is meant here is the handling of plural forms. +

+

Looking through Unix source code before the time anybody thought about +internationalization (and, sadly, even afterwards) one can often find +code similar to the following: +

+
 
   printf ("%d file%s deleted", n, n == 1 ? "" : "s");
+
+ +

After the first complaints from people internationalizing the code people +either completely avoided formulations like this or used strings like +"file(s)". Both look unnatural and should be avoided. First +tries to solve the problem correctly looked like this: +

+
 
   if (n == 1)
+     printf ("%d file deleted", n);
+   else
+     printf ("%d files deleted", n);
+
+ +

But this does not solve the problem. It helps languages where the +plural form of a noun is not simply constructed by adding an +‘s’ +but that is all. Once again people fell into the trap of believing the +rules their language is using are universal. But the handling of plural +forms differs widely between the language families. For example, +Rafal Maszkowski <rzm@mat.uni.torun.pl> reports: +

+

In Polish we use e.g. plik (file) this way: +

 
1 plik
+2,3,4 pliki
+5-21 pliko'w
+22-24 pliki
+25-31 pliko'w
+
+

and so on (o' means 8859-2 oacute which should be rather okreska, +similar to aogonek). +

+ +

There are two things which can differ between languages (and even inside +language families); +

+
    +
  • +The form how plural forms are built differs. This is a problem with +languages which have many irregularities. German, for instance, is a +drastic case. Though English and German are part of the same language +family (Germanic), the almost regular forming of plural noun forms +(appending an +‘s’) +is hardly found in German. + +
  • +The number of plural forms differ. This is somewhat surprising for +those who only have experiences with Romanic and Germanic languages +since here the number is the same (there are two). + +

    But other language families have only one form or many forms. More +information on this in an extra section. +

+ +

The consequence of this is that application writers should not try to +solve the problem in their code. This would be localization since it is +only usable for certain, hardcoded language environments. Instead the +extended gettext interface should be used. +

+

These extra functions are taking instead of the one key string two +strings and a numerical argument. The idea behind this is that using +the numerical argument and the first string as a key, the implementation +can select using rules specified by the translator the right plural +form. The two string arguments then will be used to provide a return +value in case no message catalog is found (similar to the normal +gettext behavior). In this case the rules for Germanic language +is used and it is assumed that the first string argument is the singular +form, the second the plural form. +

+

This has the consequence that programs without language catalogs can +display the correct strings only if the program itself is written using +a Germanic language. This is a limitation but since the GNU C library +(as well as the GNU gettext package) are written as part of the +GNU package and the coding standards for the GNU project require program +being written in English, this solution nevertheless fulfills its +purpose. +

+
+
Function: char * ngettext (const char *msgid1, const char *msgid2, unsigned long int n) + +
+

The ngettext function is similar to the gettext function +as it finds the message catalogs in the same way. But it takes two +extra arguments. The msgid1 parameter must contain the singular +form of the string to be converted. It is also used as the key for the +search in the catalog. The msgid2 parameter is the plural form. +The parameter n is used to determine the plural form. If no +message catalog is found msgid1 is returned if n == 1, +otherwise msgid2. +

+

An example for the use of this function is: +

+
 
printf (ngettext ("%d file removed", "%d files removed", n), n);
+
+ +

Please note that the numeric value n has to be passed to the +printf function as well. It is not sufficient to pass it only to +ngettext. +

+

In the English singular case, the number – always 1 – can be replaced with +"one": +

+
 
printf (ngettext ("One file removed", "%d files removed", n), n);
+
+ +

This works because the ‘printf’ function discards excess arguments that +are not consumed by the format string. +

+

If this function is meant to yield a format string that takes two or more +arguments, you can not use it like this: +

+
 
printf (ngettext ("%d file removed from directory %s",
+                  "%d files removed from directory %s",
+                  n),
+        n, dir);
+
+ +

because in many languages the translators want to replace the ‘%d’ +with an explicit word in the singular case, just like “one” in English, +and C format strings cannot consume the second argument but skip the first +argument. Instead, you have to reorder the arguments so that ‘n’ +comes last: +

+
 
printf (ngettext ("%2$d file removed from directory %1$s",
+                  "%2$d files removed from directory %1$s",
+                  n),
+        dir, n);
+
+ +

See C Format Strings for details about this argument reordering syntax. +

+

When you know that the value of n is within a given range, you can +specify it as a comment directed to the xgettext tool. This +information may help translators to use more adequate translations. Like +this: +

+
 
if (days > 7 && days < 14)
+  /* xgettext: range: 1..6 */
+  printf (ngettext ("one week and one day", "one week and %d days",
+                    days - 7),
+          days - 7);
+
+ +

There is one case where using ngettext is not appropriate, +however: +namely, when neither of the two strings contains a cardinal number. +Consider the following example: +

+
 
puts (ngettext ("Delete the selected file?",
+                "Delete the selected files?",
+                n));
+
+

The Russian language translator would need to provide separate +translations for the following count forms: +

    +
  • 1, 21, 31, 41, 51, 61, 71, 81, 91… +
  • 2–4, 22–24, 32–34, 42–44… +
  • 5–20, 25–30, 35–40… +
+

As you can see, +the case n == 1 cannot be expressed with the Russian plural forms. +Instead, in this case, you need to use separate calls to gettext: +

 
puts (n == 1 ? gettext ("Delete the selected file?")
+             : gettext ("Delete the selected files?"));
+
+

The translator will then use the right grammar constructs +for singular and plural without a number. +

+ +
+
Function: char * dngettext (const char *domain, const char *msgid1, const char *msgid2, unsigned long int n) + +
+

The dngettext is similar to the dgettext function in the +way the message catalog is selected. The difference is that it takes +two extra parameter to provide the correct plural form. These two +parameters are handled in the same way ngettext handles them. +

+ +
+
Function: char * dcngettext (const char *domain, const char *msgid1, const char *msgid2, unsigned long int n, int category) + +
+

The dcngettext is similar to the dcgettext function in the +way the message catalog is selected. The difference is that it takes +two extra parameter to provide the correct plural form. These two +parameters are handled in the same way ngettext handles them. +

+ +

Now, how do these functions solve the problem of the plural forms? +Without the input of linguists (which was not available) it was not +possible to determine whether there are only a few different forms in +which plural forms are formed or whether the number can increase with +every new supported language. +

+

Therefore the solution implemented is to allow the translator to specify +the rules of how to select the plural form. Since the formula varies +with every language this is the only viable solution except for +hardcoding the information in the code (which still would require the +possibility of extensions to not prevent the use of new languages). +

+ + + +

The information about the plural form selection has to be stored in the +header entry of the PO file (the one with the empty msgid string). +The plural form information looks like this: +

+
 
Plural-Forms: nplurals=2; plural=n == 1 ? 0 : 1;
+
+ +

The nplurals value must be a decimal number which specifies how +many different plural forms exist for this language. The string +following plural is an expression which is using the C language +syntax. Exceptions are that no negative numbers are allowed, numbers +must be decimal, and the only variable allowed is n. Spaces are +allowed in the expression, but backslash-newlines are not; in the +examples below the backslash-newlines are present for formatting purposes +only. This expression will be evaluated whenever one of the functions +ngettext, dngettext, or dcngettext is called. The +numeric value passed to these functions is then substituted for all uses +of the variable n in the expression. The resulting value then +must be greater or equal to zero and smaller than the value given as the +value of nplurals. +

+ +

The following rules are known at this point. The language with families +are listed. But this does not necessarily mean the information can be +generalized for the whole family (as can be easily seen in the table +below).(5) +

+
+
Only one form:
+

Some languages only require one single form. There is no distinction +between the singular and plural form. An appropriate header entry +would look like this: +

+
 
Plural-Forms: nplurals=1; plural=0;
+
+ +

Languages with this property include: +

+
+
Asian family
+

Japanese, Vietnamese, Korean

+
Tai-Kadai family
+

Thai

+
+ +
+
Two forms, singular used for one only
+

This is the form used in most existing programs since it is what English +is using. A header entry would look like this: +

+
 
Plural-Forms: nplurals=2; plural=n != 1;
+
+ +

(Note: this uses the feature of C expressions that boolean expressions +have to value zero or one.) +

+

Languages with this property include: +

+
+
Germanic family
+

English, German, Dutch, Swedish, Danish, Norwegian, Faroese

+
Romanic family
+

Spanish, Portuguese, Italian

+
Latin/Greek family
+

Greek

+
Slavic family
+

Bulgarian

+
Finno-Ugric family
+

Finnish, Estonian

+
Semitic family
+

Hebrew

+
Austronesian family
+

Bahasa Indonesian

+
Artificial
+

Esperanto

+
+ +

Other languages using the same header entry are: +

+
+
Finno-Ugric family
+

Hungarian

+
Turkic/Altaic family
+

Turkish

+
+ +

Hungarian does not appear to have a plural if you look at sentences involving +cardinal numbers. For example, “1 apple” is “1 alma”, and “123 apples” is +“123 alma”. But when the number is not explicit, the distinction between +singular and plural exists: “the apple” is “az alma”, and “the apples” is +“az almák”. Since ngettext has to support both types of sentences, +it is classified here, under “two forms”. +

+

The same holds for Turkish: “1 apple” is “1 elma”, and “123 apples” is +“123 elma”. But when the number is omitted, the distinction between singular +and plural exists: “the apple” is “elma”, and “the apples” is +“elmalar”. +

+
+
Two forms, singular used for zero and one
+

Exceptional case in the language family. The header entry would be: +

+
 
Plural-Forms: nplurals=2; plural=n>1;
+
+ +

Languages with this property include: +

+
+
Romanic family
+

Brazilian Portuguese, French

+
+ +
+
Three forms, special case for zero
+

The header entry would be: +

+
 
Plural-Forms: nplurals=3; plural=n%10==1 && n%100!=11 ? 0 : n != 0 ? 1 : 2;
+
+ +

Languages with this property include: +

+
+
Baltic family
+

Latvian

+
+ +
+
Three forms, special cases for one and two
+

The header entry would be: +

+
 
Plural-Forms: nplurals=3; plural=n==1 ? 0 : n==2 ? 1 : 2;
+
+ +

Languages with this property include: +

+
+
Celtic
+

Gaeilge (Irish)

+
+ +
+
Three forms, special case for numbers ending in 00 or [2-9][0-9]
+

The header entry would be: +

+
 
Plural-Forms: nplurals=3; \
+    plural=n==1 ? 0 : (n==0 || (n%100 > 0 && n%100 < 20)) ? 1 : 2;
+
+ +

Languages with this property include: +

+
+
Romanic family
+

Romanian

+
+ +
+
Three forms, special case for numbers ending in 1[2-9]
+

The header entry would look like this: +

+
 
Plural-Forms: nplurals=3; \
+    plural=n%10==1 && n%100!=11 ? 0 : \
+           n%10>=2 && (n%100<10 || n%100>=20) ? 1 : 2;
+
+ +

Languages with this property include: +

+
+
Baltic family
+

Lithuanian

+
+ +
+
Three forms, special cases for numbers ending in 1 and 2, 3, 4, except those ending in 1[1-4]
+

The header entry would look like this: +

+
 
Plural-Forms: nplurals=3; \
+    plural=n%10==1 && n%100!=11 ? 0 : \
+           n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2;
+
+ +

Languages with this property include: +

+
+
Slavic family
+

Russian, Ukrainian, Belarusian, Serbian, Croatian

+
+ +
+
Three forms, special cases for 1 and 2, 3, 4
+

The header entry would look like this: +

+
 
Plural-Forms: nplurals=3; \
+    plural=(n==1) ? 0 : (n>=2 && n<=4) ? 1 : 2;
+
+ +

Languages with this property include: +

+
+
Slavic family
+

Czech, Slovak

+
+ +
+
Three forms, special case for one and some numbers ending in 2, 3, or 4
+

The header entry would look like this: +

+
 
Plural-Forms: nplurals=3; \
+    plural=n==1 ? 0 : \
+           n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2;
+
+ +

Languages with this property include: +

+
+
Slavic family
+

Polish

+
+ +
+
Four forms, special case for one and all numbers ending in 02, 03, or 04
+

The header entry would look like this: +

+
 
Plural-Forms: nplurals=4; \
+    plural=n%100==1 ? 0 : n%100==2 ? 1 : n%100==3 || n%100==4 ? 2 : 3;
+
+ +

Languages with this property include: +

+
+
Slavic family
+

Slovenian

+
+ +
+
Six forms, special cases for one, two, all numbers ending in 02, 03, … 10, all numbers ending in 11 … 99, and others
+

The header entry would look like this: +

+
 
Plural-Forms: nplurals=6; \
+    plural=n==0 ? 0 : n==1 ? 1 : n==2 ? 2 : n%100>=3 && n%100<=10 ? 3 \
+    : n%100>=11 ? 4 : 5;
+
+ +

Languages with this property include: +

+
+
Afroasiatic family
+

Arabic

+
+
+
+ +

You might now ask, ngettext handles only numbers n of type +‘unsigned long’. What about larger integer types? What about negative +numbers? What about floating-point numbers? +

+

About larger integer types, such as ‘uintmax_t’ or +‘unsigned long long’: they can be handled by reducing the value to a +range that fits in an ‘unsigned long’. Simply casting the value to +‘unsigned long’ would not do the right thing, since it would treat +ULONG_MAX + 1 like zero, ULONG_MAX + 2 like singular, and +the like. Here you can exploit the fact that all mentioned plural form +formulas eventually become periodic, with a period that is a divisor of 100 +(or 1000 or 1000000). So, when you reduce a large value to another one in +the range [1000000, 1999999] that ends in the same 6 decimal digits, you +can assume that it will lead to the same plural form selection. This code +does this: +

+
 
#include <inttypes.h>
+uintmax_t nbytes = ...;
+printf (ngettext ("The file has %"PRIuMAX" byte.",
+                  "The file has %"PRIuMAX" bytes.",
+                  (nbytes > ULONG_MAX
+                   ? (nbytes % 1000000) + 1000000
+                   : nbytes)),
+        nbytes);
+
+ +

Negative and floating-point values usually represent physical entities for +which singular and plural don't clearly apply. In such cases, there is no +need to use ngettext; a simple gettext call with a form suitable +for all values will do. For example: +

+
 
printf (gettext ("Time elapsed: %.3f seconds"),
+        num_milliseconds * 0.001);
+
+ +

Even if num_milliseconds happens to be a multiple of 1000, the output +

 
Time elapsed: 1.000 seconds
+
+

is acceptable in English, and similarly for other languages. +

+

The translators' perspective regarding plural forms is explained in +Translating plural forms. +

+ + + +

11.2.7 Optimization of the *gettext functions

+ +

At this point of the discussion we should talk about an advantage of the +GNU gettext implementation. Some readers might have pointed out +that an internationalized program might have a poor performance if some +string has to be translated in an inner loop. While this is unavoidable +when the string varies from one run of the loop to the other it is +simply a waste of time when the string is always the same. Take the +following example: +

+
 
{
+  while (…)
+    {
+      puts (gettext ("Hello world"));
+    }
+}
+
+ +

When the locale selection does not change between two runs the resulting +string is always the same. One way to use this is: +

+
 
{
+  str = gettext ("Hello world");
+  while (…)
+    {
+      puts (str);
+    }
+}
+
+ +

But this solution is not usable in all situation (e.g. when the locale +selection changes) nor does it lead to legible code. +

+

For this reason, GNU gettext caches previous translation results. +When the same translation is requested twice, with no new message +catalogs being loaded in between, gettext will, the second time, +find the result through a single cache lookup. +

+ + + +

11.3 Comparing the Two Interfaces

+ + +

The following discussion is perhaps a little bit colored. As said +above we implemented GNU gettext following the Uniforum +proposal and this surely has its reasons. But it should show how we +came to this decision. +

+

First we take a look at the developing process. When we write an +application using NLS provided by gettext we proceed as always. +Only when we come to a string which might be seen by the users and thus +has to be translated we use gettext("…") instead of +"…". At the beginning of each source file (or in a central +header file) we define +

+
 
#define gettext(String) (String)
+
+ +

Even this definition can be avoided when the system supports the +gettext function in its C library. When we compile this code the +result is the same as if no NLS code is used. When you take a look at +the GNU gettext code you will see that we use _("…") +instead of gettext("…"). This reduces the number of +additional characters per translatable string to 3 (in words: +three). +

+

When now a production version of the program is needed we simply replace +the definition +

+
 
#define _(String) (String)
+
+ +

by +

+ +
 
#include <libintl.h>
+#define _(String) gettext (String)
+
+ +

Additionally we run the program ‘xgettext’ on all source code file +which contain translatable strings and that's it: we have a running +program which does not depend on translations to be available, but which +can use any that becomes available. +

+ +

The same procedure can be done for the gettext_noop invocations +(see section Special Cases of Translatable Strings). One usually defines gettext_noop as a +no-op macro. So you should consider the following code for your project: +

+
 
#define gettext_noop(String) String
+#define N_(String) gettext_noop (String)
+
+ +

N_ is a short form similar to _. The ‘Makefile’ in +the ‘po/’ directory of GNU gettext knows by default both of the +mentioned short forms so you are invited to follow this proposal for +your own ease. +

+

Now to catgets. The main problem is the work for the +programmer. Every time he comes to a translatable string he has to +define a number (or a symbolic constant) which has also be defined in +the message catalog file. He also has to take care for duplicate +entries, duplicate message IDs etc. If he wants to have the same +quality in the message catalog as the GNU gettext program +provides he also has to put the descriptive comments for the strings and +the location in all source code files in the message catalog. This is +nearly a Mission: Impossible. +

+

But there are also some points people might call advantages speaking for +catgets. If you have a single word in a string and this string +is used in different contexts it is likely that in one or the other +language the word has different translations. Example: +

+
 
printf ("%s: %d", gettext ("number"), number_of_errors)
+
+printf ("you should see %d %s", number_count,
+        number_count == 1 ? gettext ("number") : gettext ("numbers"))
+
+ +

Here we have to translate two times the string "number". Even +if you do not speak a language beside English it might be possible to +recognize that the two words have a different meaning. In German the +first appearance has to be translated to "Anzahl" and the second +to "Zahl". +

+

Now you can say that this example is really esoteric. And you are +right! This is exactly how we felt about this problem and decide that +it does not weight that much. The solution for the above problem could +be very easy: +

+
 
printf ("%s %d", gettext ("number:"), number_of_errors)
+
+printf (number_count == 1 ? gettext ("you should see %d number")
+                          : gettext ("you should see %d numbers"),
+        number_count)
+
+ +

We believe that we can solve all conflicts with this method. If it is +difficult one can also consider changing one of the conflicting string a +little bit. But it is not impossible to overcome. +

+

catgets allows same original entry to have different translations, +but gettext has another, scalable approach for solving ambiguities +of this kind: See section Solving Ambiguities. +

+ + + +

11.4 Using libintl.a in own programs

+ +

Starting with version 0.9.4 the library libintl.h should be +self-contained. I.e., you can use it in your own programs without +providing additional functions. The ‘Makefile’ will put the header +and the library in directories selected using the $(prefix). +

+ + + +

11.5 Being a gettext grok

+ +

NOTE: This documentation section is outdated and needs to be +revised. +

+

To fully exploit the functionality of the GNU gettext library it +is surely helpful to read the source code. But for those who don't want +to spend that much time in reading the (sometimes complicated) code here +is a list comments: +

+
    +
  • Changing the language at runtime + + +

    For interactive programs it might be useful to offer a selection of the +used language at runtime. To understand how to do this one need to know +how the used language is determined while executing the gettext +function. The method which is presented here only works correctly +with the GNU implementation of the gettext functions. +

    +

    In the function dcgettext at every call the current setting of +the highest priority environment variable is determined and used. +Highest priority means here the following list with decreasing +priority: +

    +
      +
    1. +
    2. LANGUAGE + +
    3. LC_ALL + + + + + + +
    4. LC_xxx, according to selected locale category + +
    5. LANG +
    + +

    Afterwards the path is constructed using the found value and the +translation file is loaded if available. +

    +

    What happens now when the value for, say, LANGUAGE changes? According +to the process explained above the new value of this variable is found +as soon as the dcgettext function is called. But this also means +the (perhaps) different message catalog file is loaded. In other +words: the used language is changed. +

    +

    But there is one little hook. The code for gcc-2.7.0 and up provides +some optimization. This optimization normally prevents the calling of +the dcgettext function as long as no new catalog is loaded. But +if dcgettext is not called the program also cannot find the +LANGUAGE variable be changed (see section Optimization of the *gettext functions). A +solution for this is very easy. Include the following code in the +language switching function. +

    +
     
      /* Change language.  */
+  setenv ("LANGUAGE", "fr", 1);
+
+  /* Make change known.  */
+  {
+    extern int  _nl_msg_cat_cntr;
+    ++_nl_msg_cat_cntr;
+  }
+
    + + +

    The variable _nl_msg_cat_cntr is defined in ‘loadmsgcat.c’. +You don't need to know what this is for. But it can be used to detect +whether a gettext implementation is GNU gettext and not non-GNU +system's native gettext implementation. +

    +
+ + + + +

11.6 Temporary Notes for the Programmers Chapter

+ +

NOTE: This documentation section is outdated and needs to be +revised. +

+ + + + +

11.6.1 Temporary - Two Possible Implementations

+ +

There are two competing methods for language independent messages: +the X/Open catgets method, and the Uniforum gettext +method. The catgets method indexes messages by integers; the +gettext method indexes them by their English translations. +The catgets method has been around longer and is supported +by more vendors. The gettext method is supported by Sun, +and it has been heard that the COSE multi-vendor initiative is +supporting it. Neither method is a POSIX standard; the POSIX.1 +committee had a lot of disagreement in this area. +

+

Neither one is in the POSIX standard. There was much disagreement +in the POSIX.1 committee about using the gettext routines +vs. catgets (XPG). In the end the committee couldn't +agree on anything, so no messaging system was included as part +of the standard. I believe the informative annex of the standard +includes the XPG3 messaging interfaces, “…as an example of +a messaging system that has been implemented…” +

+

They were very careful not to say anywhere that you should use one +set of interfaces over the other. For more on this topic please +see the Programming for Internationalization FAQ. +

+ + + +

11.6.2 Temporary - About catgets

+ +

There have been a few discussions of late on the use of +catgets as a base. I think it important to present both +sides of the argument and hence am opting to play devil's advocate +for a little bit. +

+

I'll not deny the fact that catgets could have been designed +a lot better. It currently has quite a number of limitations and +these have already been pointed out. +

+

However there is a great deal to be said for consistency and +standardization. A common recurring problem when writing Unix +software is the myriad portability problems across Unix platforms. +It seems as if every Unix vendor had a look at the operating system +and found parts they could improve upon. Undoubtedly, these +modifications are probably innovative and solve real problems. +However, software developers have a hard time keeping up with all +these changes across so many platforms. +

+

And this has prompted the Unix vendors to begin to standardize their +systems. Hence the impetus for Spec1170. Every major Unix vendor +has committed to supporting this standard and every Unix software +developer waits with glee the day they can write software to this +standard and simply recompile (without having to use autoconf) +across different platforms. +

+

As I understand it, Spec1170 is roughly based upon version 4 of the +X/Open Portability Guidelines (XPG4). Because catgets and +friends are defined in XPG4, I'm led to believe that catgets +is a part of Spec1170 and hence will become a standardized component +of all Unix systems. +

+ + + +

11.6.3 Temporary - Why a single implementation

+ +

Now it seems kind of wasteful to me to have two different systems +installed for accessing message catalogs. If we do want to remedy +catgets deficiencies why don't we try to expand catgets +(in a compatible manner) rather than implement an entirely new system. +Otherwise, we'll end up with two message catalog access systems installed +with an operating system - one set of routines for packages using GNU +gettext for their internationalization, and another set of routines +(catgets) for all other software. Bloated? +

+

Supposing another catalog access system is implemented. Which do +we recommend? At least for Linux, we need to attract as many +software developers as possible. Hence we need to make it as easy +for them to port their software as possible. Which means supporting +catgets. We will be implementing the libintl code +within our libc, but does this mean we also have to incorporate +another message catalog access scheme within our libc as well? +And what about people who are going to be using the libintl ++ non-catgets routines. When they port their software to +other platforms, they're now going to have to include the front-end +(libintl) code plus the back-end code (the non-catgets +access routines) with their software instead of just including the +libintl code with their software. +

+

Message catalog support is however only the tip of the iceberg. +What about the data for the other locale categories? They also have +a number of deficiencies. Are we going to abandon them as well and +develop another duplicate set of routines (should libintl +expand beyond message catalog support)? +

+

Like many parts of Unix that can be improved upon, we're stuck with balancing +compatibility with the past with useful improvements and innovations for +the future. +

+ + + +

11.6.4 Temporary - Notes

+ +

X/Open agreed very late on the standard form so that many +implementations differ from the final form. Both of my system (old +Linux catgets and Ultrix-4) have a strange variation. +

+

OK. After incorporating the last changes I have to spend some time on +making the GNU/Linux libc gettext functions. So in future +Solaris is not the only system having gettext. +

+ + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_12.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_12.html new file mode 100644 index 0000000000000000000000000000000000000000..e69f5fc747494644117c8ba3ada53aa2c783de24 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_12.html @@ -0,0 +1,414 @@ + + + + + +GNU gettext utilities: 12. The Translator's View + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

12. The Translator's View

+ + + + + +

12.1 Organization

+ +

For some software packages, each translator works on her own +and communicates directly with the developers of the package. +For some other software packages, on the other hand, +translators are organized +into translation projects and translation teams. +

+

A translation project applies to a group of software packages +and shares procedures and methodologies regarding the translation. +

+

There are currently three major translation projects: +

+
    +
  • +The “Translation Project”, which is used +by all kinds of Free Software packages, but in particular by GNU packages. +It has its home at https://translationproject.org/. + +
  • +The “KDE Localization Project”, which is used by KDE packages. +It is at https://l10n.kde.org/. + +
  • +The “GNOME Localization Project”, which is used by GNOME packages. +It is at https://l10n.gnome.org/. +
+ +

A translation team is a group of translators for a single language, +in the scope of a translation project. +

+ + + +

12.2 Responsibilities in the Translation Project

+ +

The following rules and habits apply to the Translation Project. +

+

The translator's responsibilities are: +

    +
  • +She submits a translations disclaimer to the Free Software Foundation +(once only, and +only when she wants to translate a package that requires a disclaimer). + +

    A disclaimer is a legal document +that allows the software package to distribute her translation work. +It is not as strong as a copyright assignment. +Merely, it says that the signer +will never make use of the copyright on her translations: +will never forbid copying them, +and will never ask for some kind of compensation. +This guarantees that the FSF (and everyone else) +will always be allowed to freely distribute these translations. +The FSF wishes to have this guarantee in a legally binding manner, +to be on the safe side. +

    +

    There are two ways to submit the disclaimer: +Either online through +this form +on the FSF's web site, +or by printing, signing, and submitting +the file ‘disclaim-translations.txt’ found in the GNU gettext distribution. +

    +
  • +Agree with the other translators of the same team +who is “in charge” for the translations of a particular package. +
+ +

The Translation Project has a coordinator. +He can be reached at ‘coordinator@translationproject.org’. +His responsibilities are: +

    +
  • +He maintains the web site https://translationproject.org/. +
  • +When he receives a release or prerelease announcement +from one of the software package maintainers, +he extracts the POT file(s) +and sends notifications to all translation teams about it. +
+ +

The responsibilities of the package maintainers are: +

    +
  • +To incorporate the translations in the software package before a release. +
  • +To forward bug reports about the translations +to the respective translation team. +A developer or maintainer should never apply a translation fix himself, +because that would cause conflicts with the translation team. +
+ + + + + +

12.3 Language dialects

+ +

For many languages, a translation into the main dialect is intelligible +by all speakers of the language. +Speakers of another dialect can have a separate translation if they wish so. +In fact, since the fallback mechanism implemented in GNU libc and GNU libintl +applies on a per-message basis, +the message catalog for the dialect needs only to contain +the translations that differ from those in the main language. +

+

For example, +French speakers in Canada (that is, users in the locale fr_CA) +can use and do accept translations +produced by French speakers in France (typical file name: fr.po). +Nevertheless, the translation system with PO files +enables them to produce special message catalogs (file name: fr_CA.po) +that will take priority over fr.po for users in that locale. +Similarly for users in Austria, +where message catalogs de_AT.po take priority +over the catalogs named de.po that reflect German as spoken in Germany. +

+

The situation is different for Chinese, though: +Since users in the People's Republic of China and in Singapore +want translations with Simplified Chinese characters, +whereas Chinese users in other territories +(such as Taiwan, Hong Kong, and Macao) +want translations with Traditional Chinese characters, +no translator should ever submit a file named zh.po. +Instead, there will typically be two separate translation teams: +a team that produces translations with Simplified Chinese characters +(file name zh_CN.po) +and a team that produces translations with Traditional Chinese characters +(file name zh_TW.po). +

+ + + +

12.4 Translating plural forms

+ +

Suppose you are translating a PO file, and it contains an entry like this: +

+
 
#, c-format
+msgid "One file removed"
+msgid_plural "%d files removed"
+msgstr[0] ""
+msgstr[1] ""
+
+ +

What does this mean? How do you fill it in? +

+

Such an entry denotes a message with plural forms, that is, a message where +the text depends on a cardinal number. The general form of the message, +in English, is the msgid_plural line. The msgid line is the +English singular form, that is, the form for when the number is equal to 1. +More details about plural forms are explained in Additional functions for plural forms. +

+

The first thing you need to look at is the Plural-Forms line in the +header entry of the PO file. It contains the number of plural forms and a +formula. If the PO file does not yet have such a line, you have to add it. +It only depends on the language into which you are translating. You can +get this info by using the msginit command (see Creating a New PO File) – +it contains a database of known plural formulas – or by asking other +members of your translation team. +

+

Suppose the line looks as follows: +

+
 
"Plural-Forms: nplurals=3; plural=n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2;\n"
+
+ +

It's logically one line; recall that the PO file formatting is allowed to +break long lines so that each physical line fits in 80 monospaced columns. +

+

The value of nplurals here tells you that there are three plural +forms. The first thing you need to do is to ensure that the entry contains +an msgstr line for each of the forms: +

+
 
#, c-format
+msgid "One file removed"
+msgid_plural "%d files removed"
+msgstr[0] ""
+msgstr[1] ""
+msgstr[2] ""
+
+ +

Then translate the msgid_plural line and fill it in into each +msgstr line: +

+
 
#, c-format
+msgid "One file removed"
+msgid_plural "%d files removed"
+msgstr[0] "%d slika uklonjenih"
+msgstr[1] "%d slika uklonjenih"
+msgstr[2] "%d slika uklonjenih"
+
+ +

Now you can refine the translation so that it matches the plural form. +According to the formula above, msgstr[0] is used when the number +ends in 1 but does not end in 11; msgstr[1] is used when the number +ends in 2, 3, 4, but not in 12, 13, 14; and msgstr[2] is used in +all other cases. With this knowledge, you can refine the translations: +

+
 
#, c-format
+msgid "One file removed"
+msgid_plural "%d files removed"
+msgstr[0] "%d slika je uklonjena"
+msgstr[1] "%d datoteke uklonjenih"
+msgstr[2] "%d slika uklonjenih"
+
+ +

You noticed that in the English singular form (msgid) the number +placeholder could be omitted and replaced by the numeral word “one”. +Can you do this in your translation as well? +

+
 
msgstr[0] "jednom datotekom je uklonjen"
+
+ +

Well, it depends on whether msgstr[0] applies only to the number 1, +or to other numbers as well. If, according to the plural formula, +msgstr[0] applies only to n == 1, then you can use the +specialized translation without the number placeholder. In our case, +however, msgstr[0] also applies to the numbers 21, 31, 41, etc., +and therefore you cannot omit the placeholder. +

+ + + +

12.5 Prioritizing messages: How to determine which messages to translate first

+ +

A translator sometimes has only a limited amount of time per week to +spend on a package, and some packages have quite large message catalogs +(over 1000 messages). Therefore she wishes to translate the messages +first that are the most visible to the user, or that occur most frequently. +This section describes how to determine these "most urgent" messages. +It also applies to determine the "next most urgent" messages after the +message catalog has already been partially translated. +

+

In a first step, she uses the programs like a user would do. While she +does this, the GNU gettext library logs into a file the not yet +translated messages for which a translation was requested from the program. +

+

In a second step, she uses the PO mode to translate precisely this set +of messages. +

+ +

Here are more details. The GNU libintl library (but not the +corresponding functions in GNU libc) supports an environment variable +GETTEXT_LOG_UNTRANSLATED. The GNU libintl library will +log into this file the messages for which gettext() and related +functions couldn't find the translation. If the file doesn't exist, it +will be created as needed. On systems with GNU libc a shared library +‘preloadable_libintl.so’ is provided that can be used with the ELF +‘LD_PRELOAD’ mechanism. +

+

So, in the first step, the translator uses these commands on systems with +GNU libc: +

+
 
$ LD_PRELOAD=/usr/local/lib/preloadable_libintl.so
+$ export LD_PRELOAD
+$ GETTEXT_LOG_UNTRANSLATED=$HOME/gettextlogused
+$ export GETTEXT_LOG_UNTRANSLATED
+
+ +

and these commands on other systems: +

+
 
$ GETTEXT_LOG_UNTRANSLATED=$HOME/gettextlogused
+$ export GETTEXT_LOG_UNTRANSLATED
+
+ +

Then she uses and peruses the programs. (It is a good and recommended +practice to use the programs for which you provide translations: it +gives you the needed context.) When done, she removes the environment +variables: +

+
 
$ unset LD_PRELOAD
+$ unset GETTEXT_LOG_UNTRANSLATED
+
+ +

The second step starts with removing duplicates: +

+
 
$ msguniq $HOME/gettextlogused > missing.po
+
+ +

The result is a PO file, but needs some preprocessing before a PO file editor +can be used with it. First, it is a multi-domain PO file, containing +messages from many translation domains. Second, it lacks all translator +comments and source references. Here is how to get a list of the affected +translation domains: +

+
 
$ sed -n -e 's,^domain "\(.*\)"$,\1,p' < missing.po | sort | uniq
+
+ +

Then the translator can handle the domains one by one. For simplicity, +let's use environment variables to denote the language, domain and source +package. +

+
 
$ lang=nl             # your language
+$ domain=coreutils    # the name of the domain to be handled
+$ package=/usr/src/gnu/coreutils-4.5.4   # the package where it comes from
+
+ +

She takes the latest copy of ‘$lang.po’ from the Translation Project, +or from the package (in most cases, ‘$package/po/$lang.po’), or +creates a fresh one if she's the first translator (see Creating a New PO File). +She then uses the following commands to mark the not urgent messages as +"obsolete". (This doesn't mean that these messages - translated and +untranslated ones - will go away. It simply means that the PO file editor +will ignore them in the following editing session.) +

+
 
$ msggrep --domain=$domain missing.po | grep -v '^domain' \
+  > $domain-missing.po
+$ msgattrib --set-obsolete --ignore-file $domain-missing.po $domain.$lang.po \
+  > $domain.$lang-urgent.po
+
+ +

Then she translates ‘$domain.$lang-urgent.po’ by use of a PO file editor +(see section Editing PO Files). +(FIXME: I don't know whether Lokalize and gtranslator also +preserve obsolete messages, as they should.) +Finally she restores the not urgent messages (with their earlier +translations, for those which were already translated) through this command: +

+
 
$ msgmerge --no-fuzzy-matching $domain.$lang-urgent.po $package/po/$domain.pot \
+  > $domain.$lang.po
+
+ +

Then she can submit ‘$domain.$lang.po’ and proceed to the next domain. +

+ + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_13.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_13.html new file mode 100644 index 0000000000000000000000000000000000000000..52985323a418502f48f9399323fc206cc60f4760 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_13.html @@ -0,0 +1,1495 @@ + + + + + +GNU gettext utilities: 13. The Maintainer's View + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

13. The Maintainer's View

+ +

The maintainer of a package has many responsibilities. One of them +is ensuring that the package will install easily on many platforms, +and that the magic we described earlier (see section The User's View) will work +for installers and end users. +

+

Of course, there are many possible ways by which GNU gettext +might be integrated in a distribution, and this chapter does not cover +them in all generality. Instead, it details one possible approach which +is especially adequate for many free software distributions following GNU +standards, or even better, Gnits standards, because GNU gettext +is purposely for helping the internationalization of the whole GNU +project, and as many other good free packages as possible. So, the +maintainer's view presented here presumes that the package already has +a ‘configure.ac’ file and uses GNU Autoconf. +

+

Nevertheless, GNU gettext may surely be useful for free packages +not following GNU standards and conventions, but the maintainers of such +packages might have to show imagination and initiative in organizing +their distributions so gettext work for them in all situations. +There are surely many, out there. +

+

Even if gettext methods are now stabilizing, slight adjustments +might be needed between successive gettext versions, so you +should ideally revise this chapter in subsequent releases, looking +for changes. +

+ + + + +

13.1 Flat or Non-Flat Directory Structures

+ +

Some free software packages are distributed as tar files which unpack +in a single directory, these are said to be flat distributions. +Other free software packages have a one level hierarchy of subdirectories, using +for example a subdirectory named ‘doc/’ for the Texinfo manual and +man pages, another called ‘lib/’ for holding functions meant to +replace or complement C libraries, and a subdirectory ‘src/’ for +holding the proper sources for the package. These other distributions +are said to be non-flat. +

+

We cannot say much about flat distributions. A flat +directory structure has the disadvantage of increasing the difficulty +of updating to a new version of GNU gettext. Also, if you have +many PO files, this could somewhat pollute your single directory. +Also, GNU gettext's libintl sources consist of C sources, shell +scripts, sed scripts and complicated Makefile rules, which don't +fit well into an existing flat structure. For these reasons, we +recommend to use non-flat approach in this case as well. +

+

Maybe because GNU gettext itself has a non-flat structure, +we have more experience with this approach, and this is what will be +described in the remaining of this chapter. Some maintainers might +use this as an opportunity to unflatten their package structure. +

+ + + +

13.2 Prerequisite Works

+ +

There are some works which are required for using GNU gettext +in one of your package. These works have some kind of generality +that escape the point by point descriptions used in the remainder +of this chapter. So, we describe them here. +

+
    +
  • +Before attempting to use gettextize you should install some +other packages first. +Ensure that recent versions of GNU m4, GNU Autoconf and GNU +gettext are already installed at your site, and if not, proceed +to do this first. If you get to install these things, beware that +GNU m4 must be fully installed before GNU Autoconf is even +configured. + +

    To further ease the task of a package maintainer the automake +package was designed and implemented. GNU gettext now uses this +tool and the ‘Makefile’ in the ‘po/’ directory therefore +knows about all the goals necessary for using automake. +

    +

    Those four packages are only needed by you, as a maintainer; the +installers of your own package and end users do not really need any of +GNU m4, GNU Autoconf, GNU gettext, or GNU automake +for successfully installing and running your package, with messages +properly translated. But this is not completely true if you provide +internationalized shell scripts within your own package: GNU +gettext shall then be installed at the user site if the end users +want to see the translation of shell script messages. +

    +
  • +Your package should use Autoconf and have a ‘configure.ac’ or +‘configure.in’ file. +If it does not, you have to learn how. The Autoconf documentation +is quite well written, it is a good idea that you print it and get +familiar with it. + +
  • +Your C sources should have already been modified according to +instructions given earlier in this manual. See section Preparing Program Sources. + +
  • +Your ‘po/’ directory should receive all PO files submitted to you +by the translator teams, each having ‘ll.po’ as a name. +This is not usually easy to get translation +work done before your package gets internationalized and available! +Since the cycle has to start somewhere, the easiest for the maintainer +is to start with absolutely no PO files, and wait until various +translator teams get interested in your package, and submit PO files. + +
+ +

It is worth adding here a few words about how the maintainer should +ideally behave with PO files submissions. As a maintainer, your role is +to authenticate the origin of the submission as being the representative +of the appropriate translating teams of the Translation Project (forward +the submission to ‘coordinator@translationproject.org’ in case of doubt), +to ensure that the PO file format is not severely broken and does not +prevent successful installation, and for the rest, to merely put these +PO files in ‘po/’ for distribution. +

+

As a maintainer, you do not have to take on your shoulders the +responsibility of checking if the translations are adequate or +complete, and should avoid diving into linguistic matters. Translation +teams drive themselves and are fully responsible of their linguistic +choices for the Translation Project. Keep in mind that translator teams are not +driven by maintainers. You can help by carefully redirecting all +communications and reports from users about linguistic matters to the +appropriate translation team, or explain users how to reach or join +their team. +

+

Maintainers should never ever apply PO file bug reports +themselves, short-cutting translation teams. If some translator has +difficulty to get some of her points through her team, it should not be +an option for her to directly negotiate translations with maintainers. +Teams ought to settle their problems themselves, if any. If you, as +a maintainer, ever think there is a real problem with a team, please +never try to solve a team's problem on your own. +

+ + + +

13.3 Invoking the gettextize Program

+ + +

The gettextize program is an interactive tool that helps the +maintainer of a package internationalized through GNU gettext. +It is used for two purposes: +

+
    +
  • +As a wizard, when a package is modified to use GNU gettext for +the first time. + +
  • +As a migration tool, for upgrading the GNU gettext support in +a package from a previous to a newer version of GNU gettext. +
+ +

This program performs the following tasks: +

+
    +
  • +It copies into the package some files that are consistently and +identically needed in every package internationalized through +GNU gettext. + +
  • It performs as many of the tasks mentioned in the next section +Files You Must Create or Alter as can be performed automatically. + +
  • It removes obsolete files and idioms used for previous GNU +gettext versions to the form recommended for the current GNU +gettext version. + +
  • It prints a summary of the tasks that ought to be done manually +and could not be done automatically by gettextize. +
+ +

It can be invoked as follows: +

+ + +
 
gettextize [ option… ] [ directory ]
+
+ +

and accepts the following options: +

+
+
‘-f’
+
‘--force’
+
+ +

Force replacement of files which already exist. +

+
+
‘--po-dir=dir’
+
+

Specify a directory containing PO files. Such a directory contains the +translations into various languages of a particular POT file. This +option can be specified multiple times, once for each translation domain. +If it is not specified, the directory named ‘po/’ is updated. +

+
+
‘--no-changelog’
+
+

Don't update or create ChangeLog files. By default, gettextize +logs all changes (file additions, modifications and removals) in a +file called ‘ChangeLog’ in each affected directory. +

+
+
‘--symlink’
+
+

Make symbolic links instead of copying the needed files. This can be +useful to save a few kilobytes of disk space, but it requires extra +effort to create self-contained tarballs, it may disturb some mechanism +the maintainer applies to the sources, and it is likely to introduce +bugs when a newer version of gettext is installed on the system. +

+
+
‘-n’
+
‘--dry-run’
+
+ +

Print modifications but don't perform them. All actions that +gettextize would normally execute are inhibited and instead only +listed on standard output. +

+
+
‘--help’
+
+

Display this help and exit. +

+
+
‘--version’
+
+

Output version information and exit. +

+
+
+ +

If directory is given, this is the top level directory of a +package to prepare for using GNU gettext. If not given, it +is assumed that the current directory is the top level directory of +such a package. +

+

The program gettextize provides the following files. However, +no existing file will be replaced unless the option --force +(-f) is specified. +

+
    +
  1. +The ‘ABOUT-NLS’ file is copied in the main directory of your package, +the one being at the top level. This file contains a reference to the +GNU gettext documentation. It also avoids an error from Automake in +packages that use the Automake option ‘gnits’: +“error: required file './ABOUT-NLS' not found”. + +
  2. +A ‘po/’ directory is created for eventually holding +all translation files, but initially only containing the file +‘po/Makefile.in.in’ from the GNU gettext distribution +(beware the double ‘.in’ in the file name) and a few auxiliary +files. If the ‘po/’ directory already exists, it will be preserved +along with the files it contains, and only ‘Makefile.in.in’ and +the auxiliary files will be overwritten. + +

    If ‘--po-dir’ has been specified, this holds for every directory +specified through ‘--po-dir’, instead of ‘po/’. +

    +
  3. +The file ‘config.rpath’ is copied into the directory containing +configuration support files. It is needed by the AM_GNU_GETTEXT +autoconf macro. + +
  4. +Only if the project is using GNU automake: +A set of autoconf macro files is copied into the package's +autoconf macro repository, usually in a directory called ‘m4/’. +
+ +

If your site support symbolic links, gettextize will not +actually copy the files into your package, but establish symbolic +links instead. This avoids duplicating the disk space needed in +all packages. Merely using the ‘-h’ option while creating the +tar archive of your distribution will resolve each link by an +actual copy in the distribution archive. So, to insist, you really +should use ‘-h’ option with tar within your dist +goal of your main ‘Makefile.in’. +

+

Furthermore, gettextize will update all ‘Makefile.am’ files +in each affected directory, as well as the top level ‘configure.ac’ +or ‘configure.in’ file. +

+

It is interesting to understand that most new files for supporting +GNU gettext facilities in one package go in ‘po/’ and +‘m4/’ subdirectories. Still, these directories will mostly +contain package dependent files. +

+

The gettextize program makes backup files for all files it +replaces or changes, and also write ChangeLog entries about these +changes. This way, the careful maintainer can check after running +gettextize whether its changes are acceptable to him, and +possibly adjust them. An exception to this rule is the ‘intl/’ +directory, which is removed as a whole if it still existed. +

+

It is important to understand that gettextize can not do the +entire job of adapting a package for using GNU gettext. The +amount of remaining work depends on whether the package uses GNU +automake or not. But in any case, the maintainer should still +read the section Files You Must Create or Alter after invoking gettextize. +

+

In particular, if after using ‘gettexize’, you get an error +‘AC_COMPILE_IFELSE was called before AC_GNU_SOURCE’ or +‘AC_RUN_IFELSE was called before AC_GNU_SOURCE’, you can fix it +by modifying ‘configure.ac’, as described in ‘configure.ac’ at top level. +

+

It is also important to understand that gettextize is not part +of the GNU build system, in the sense that it should not be invoked +automatically, and not be invoked by someone who doesn't assume the +responsibilities of a package maintainer. For the latter purpose, a +separate tool is provided, see Invoking the autopoint Program. +

+ + + +

13.4 Files You Must Create or Alter

+ +

Besides files which are automatically added through gettextize, +there are many files needing revision for properly interacting with +GNU gettext. If you are closely following GNU standards for +Makefile engineering and auto-configuration, the adaptations should +be easier to achieve. Here is a point by point description of the +changes needed in each. +

+

So, here comes a list of files, each one followed by a description of +all alterations it needs. Many examples are taken out from the GNU +gettext 0.25.1 distribution itself, or from the GNU +hello distribution (https://www.gnu.org/software/hello). +You may indeed refer to the source code of the GNU gettext and +GNU hello packages, as they are intended to be good examples for +using GNU gettext functionality. +

+ + + + +

13.4.1 ‘POTFILES.in’ in ‘po/’

+ +

The ‘po/’ directory should receive a file named +‘POTFILES.in’. This file tells which files, among all program +sources, have marked strings needing translation. Here is an example +of such a file: +

+
 
# List of source files containing translatable strings.
+# Copyright (C) 1995 Free Software Foundation, Inc.
+
+# Common library files
+lib/error.c
+lib/getopt.c
+lib/xmalloc.c
+
+# Package source files
+src/gettext.c
+src/msgfmt.c
+src/xgettext.c
+
+ +

Hash-marked comments and white lines are ignored. All other lines +list those source files containing strings marked for translation +(see section How Marks Appear in Sources), in a notation relative to the top level +of your whole distribution, rather than the location of the +‘POTFILES.in’ file itself. +

+

When a C file is automatically generated by a tool, like flex or +bison, that doesn't introduce translatable strings by itself, +it is recommended to list in ‘po/POTFILES.in’ the real source file +(ending in ‘.l’ in the case of flex, or in ‘.y’ in the +case of bison), not the generated C file. +

+ + + +

13.4.2 ‘LINGUAS’ in ‘po/’

+ +

The ‘po/’ directory should also receive a file named +‘LINGUAS’. This file contains the list of available translations. +It is a whitespace separated list. Hash-marked comments and white lines +are ignored. Here is an example file: +

+
 
# Set of available languages.
+de fr
+
+ +

This example means that German and French PO files are available, so +that these languages are currently supported by your package. If you +want to further restrict, at installation time, the set of installed +languages, this should not be done by modifying the ‘LINGUAS’ file, +but rather by using the LINGUAS environment variable +(see section The Installer's and Distributor's View). +

+

It is recommended that you add the "languages" ‘en@quot’ and +‘en@boldquot’ to the LINGUAS file. en@quot is a +variant of English message catalogs (en) which uses real quotation +marks instead of the ugly looking asymmetric ASCII substitutes ‘`’ +and ‘'’. en@boldquot is a variant of en@quot that +additionally outputs quoted pieces of text in a bold font, when used in +a terminal emulator which supports the VT100 escape sequences (such as +xterm or the Linux console, but not Emacs in M-x shell mode). +

+

These extra message catalogs ‘en@quot’ and ‘en@boldquot’ +are constructed automatically, not by translators; to support them, you +need the files ‘Rules-quot’, ‘quot.sed’, ‘boldquot.sed’, +‘en@quot.header’, ‘en@boldquot.header’, ‘insert-header.sed’ +in the ‘po/’ directory. You can copy them from GNU gettext's ‘po/’ +directory; they are also installed by running gettextize. +

+ + + +

13.4.3 ‘Makevars’ in ‘po/’

+ +

The ‘po/’ directory also has a file named ‘Makevars’. It +contains variables that are specific to your project. ‘po/Makevars’ +gets inserted into the ‘po/Makefile’ when the latter is created. +The variables thus take effect when the POT file is created or updated, +and when the message catalogs get installed. +

+

The first three variables can be left unmodified if your package has a +single message domain and, accordingly, a single ‘po/’ directory. +Only packages which have multiple ‘po/’ directories at different +locations need to adjust the three first variables defined in +‘Makevars’. +

+

As an alternative to the XGETTEXT_OPTIONS variable, it is also +possible to specify xgettext options through the +AM_XGETTEXT_OPTION autoconf macro. See AM_XGETTEXT_OPTION in ‘po.m4’. +

+ + + +

13.4.4 Extending ‘Makefile’ in ‘po/’

+ +

All files called ‘Rules-*’ in the ‘po/’ directory get appended to +the ‘po/Makefile’ when it is created. They present an opportunity to +add rules for special PO files to the Makefile, without needing to mess +with ‘po/Makefile.in.in’. +

+ + +

GNU gettext comes with a ‘Rules-quot’ file, containing rules for +building catalogs ‘en@quot.po’ and ‘en@boldquot.po’. The +effect of ‘en@quot.po’ is that people who set their LANGUAGE +environment variable to ‘en@quot’ will get messages with proper +looking symmetric Unicode quotation marks instead of abusing the ASCII +grave accent and the ASCII apostrophe for indicating quotations. To +enable this catalog, simply add en@quot to the ‘po/LINGUAS’ +file. The effect of ‘en@boldquot.po’ is that people who set +LANGUAGE to ‘en@boldquot’ will get not only proper quotation +marks, but also the quoted text will be shown in a bold font on terminals +and consoles. This catalog is useful only for command-line programs, not +GUI programs. To enable it, similarly add en@boldquot to the +‘po/LINGUAS’ file. +

+

Similarly, you can create rules for building message catalogs for the +‘sr@latin’ locale – Serbian written with the Latin alphabet – +from those for the ‘sr’ locale – Serbian written with Cyrillic +letters. See Invoking the msgfilter Program. +

+ + + +

13.4.5 ‘configure.ac’ at top level

+ +

‘configure.ac’ or ‘configure.in’ - this is the source from which +autoconf generates the ‘configure’ script. +

+
    +
  1. Declare the package and version. + + +

    This is done by a set of lines like these: +

    +
     
    PACKAGE=gettext
+VERSION=0.25.1
+AC_DEFINE_UNQUOTED(PACKAGE, "$PACKAGE")
+AC_DEFINE_UNQUOTED(VERSION, "$VERSION")
+AC_SUBST(PACKAGE)
+AC_SUBST(VERSION)
+
    + +

    or, if you are using GNU automake, by a line like this: +

    +
     
    AM_INIT_AUTOMAKE(gettext, 0.25.1)
+
    + +

    Of course, you replace ‘gettext’ with the name of your package, +and ‘0.25.1’ by its version numbers, exactly as they +should appear in the packaged tar file name of your distribution +(‘gettext-0.25.1.tar.gz’, here). +

    +
  2. Check for internationalization support. + +

    Here is the main m4 macro for triggering internationalization +support. Just add this line to ‘configure.ac’: +

    +
     
    AM_GNU_GETTEXT([external])
+
    + +

    This call is purposely simple, even if it generates a lot of configure +time checking and actions. +

    +
  3. Have output files created. + +

    The AC_OUTPUT directive, at the end of your ‘configure.ac’ +file, needs to be modified in two ways: +

    +
     
    AC_OUTPUT([existing configuration files po/Makefile.in],
+[existing additional actions])
+
    + +

    The modification to the first argument to AC_OUTPUT asks +for substitution in the ‘po/’ directory. +Note the ‘.in’ suffix used for ‘po/’ only. This is because +the distributed file is really ‘po/Makefile.in.in’. +

    +
+ + + + +

13.4.6 ‘config.guess’, ‘config.sub’ at top level

+ +

You need to add the GNU ‘config.guess’ and ‘config.sub’ files +to your distribution. They are needed because the AM_ICONV macro +contains knowledge about specific platforms and therefore needs to +identify the platform. +

+

You can obtain the newest version of ‘config.guess’ and +‘config.sub’ from the ‘config’ project at +‘https://savannah.gnu.org/’. The commands to fetch them are +

 
$ wget -O config.guess 'https://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD'
+$ wget -O config.sub 'https://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.sub;hb=HEAD'
+
+

Less recent versions are also contained in the GNU automake and +GNU libtool packages. +

+

Normally, ‘config.guess’ and ‘config.sub’ are put at the +top level of a distribution. But it is also possible to put them in a +subdirectory, altogether with other configuration support files like +‘install-sh’, ‘ltconfig’, ‘ltmain.sh’ or ‘missing’. +All you need to do, other than moving the files, is to add the following line +to your ‘configure.ac’. +

+
 
AC_CONFIG_AUX_DIR([subdir])
+
+ + + + +

13.4.7 ‘mkinstalldirs’ at top level

+ +

With earlier versions of GNU gettext, you needed to add the GNU +‘mkinstalldirs’ script to your distribution. This is not needed any +more. You can remove it. +

+ + + +

13.4.8 ‘aclocal.m4’ at top level

+ +

If you do not have an ‘aclocal.m4’ file in your distribution, +the simplest is to concatenate the files ‘build-to-host.m4’, +‘gettext.m4’, ‘host-cpu-c-abi.m4’, ‘intlmacosx.m4’, +‘iconv.m4’, ‘lib-ld.m4’, ‘lib-link.m4’, ‘lib-prefix.m4’, +‘nls.m4’, ‘po.m4’, ‘progtest.m4’ from GNU gettext's +‘prefix/share/gettext/m4/’ directory into a single file. +

+

If you already have an ‘aclocal.m4’ file, then you will have +to merge the said macro files into your ‘aclocal.m4’. Note that if +you are upgrading from a previous release of GNU gettext, you +should most probably replace the macros (AM_GNU_GETTEXT, +etc.), as they usually +change a little from one release of GNU gettext to the next. +Their contents may vary as we get more experience with strange systems +out there. +

+

You should be using GNU automake 1.9 or newer. With it, you need +to copy the files ‘build-to-host.m4’, ‘gettext.m4’, +‘host-cpu-c-abi.m4’, ‘intlmacosx.m4’, ‘iconv.m4’, +‘lib-ld.m4’, ‘lib-link.m4’, ‘lib-prefix.m4’, ‘nls.m4’, +‘po.m4’, ‘progtest.m4’ from GNU gettext's +‘prefix/share/gettext/m4/’ +directory to a subdirectory named ‘m4/’ and add the line +

+
 
ACLOCAL_AMFLAGS = -I m4
+
+ +

to your top level ‘Makefile.am’. +

+

If you are using GNU automake 1.12 or newer, it is even easier: +Add the line +

+
 
ACLOCAL_AMFLAGS = -I m4
+
+ +

to your top level ‘Makefile.am’, and run +‘aclocal --install --system-acdir=prefix/share/gettext/m4 -I m4’. +This will copy the needed files to the ‘m4/’ subdirectory automatically, +before updating ‘aclocal.m4’. +

+

Note: This --system-acdir option should only be used here, once. +If you were to use it after autopoint has been run, +it would destroy the consistency that autopoint guarantees +and lead to all sorts of malfunction at build time. +

+

These macros check for the internationalization support functions +and related information. +

+ + + +

13.4.9 ‘config.h.in’ at top level

+ +

The include file template that holds the C macros to be defined by +configure is usually called ‘config.h.in’ and may be +maintained either manually or automatically. +

+

If it is maintained automatically, by use of the ‘autoheader’ +program, you need to do nothing about it. This is the case in particular +if you are using GNU automake. +

+

If it is maintained manually, you can get away by adding the +following lines to ‘config.h.in’: +

+
 
/* Define to 1 if translation of program messages to the user's
+   native language is requested. */
+#undef ENABLE_NLS
+
+ + + + +

13.4.10 ‘Makefile.in’ at top level

+ +

Here are a few modifications you need to make to your main, top-level +‘Makefile.in’ file. +

+
    +
  1. +Add the following lines near the beginning of your ‘Makefile.in’, +so the ‘dist:’ goal will work properly (as explained further down): + +
     
    PACKAGE = @PACKAGE@
+VERSION = @VERSION@
+
    + +
  2. +Wherever you process subdirectories in your ‘Makefile.in’, be sure +you also process the subdirectory ‘po’. Special +rules in the ‘Makefiles’ take care for the case where no +internationalization is wanted. + +

    If you are using Makefiles, either generated by automake, or hand-written +so they carefully follow the GNU coding standards, the effected goals for +which the new subdirectories must be handled include ‘installdirs’, +‘install’, ‘uninstall’, ‘clean’, ‘distclean’. +

    +

    Here is an example of a canonical order of processing. In this +example, we also define SUBDIRS in Makefile.in for it +to be further used in the ‘dist:’ goal. +

    +
     
    SUBDIRS = doc lib src po
+
    + +
  3. +A delicate point is the ‘dist:’ goal, as ‘po/Makefile’ will later +assume that the proper directory has been set up from the main ‘Makefile’. +Here is an example at what the ‘dist:’ goal might look like: + +
     
    distdir = $(PACKAGE)-$(VERSION)
+dist: Makefile
+	rm -fr $(distdir)
+	mkdir $(distdir)
+	chmod 777 $(distdir)
+	for file in $(DISTFILES); do \
+	  ln $$file $(distdir) 2>/dev/null || cp -p $$file $(distdir); \
+	done
+	for subdir in $(SUBDIRS); do \
+	  mkdir $(distdir)/$$subdir || exit 1; \
+	  chmod 777 $(distdir)/$$subdir; \
+	  (cd $$subdir && $(MAKE) $@) || exit 1; \
+	done
+	tar chozf $(distdir).tar.gz $(distdir)
+	rm -fr $(distdir)
+
    + +
+ +

Note that if you are using GNU automake, ‘Makefile.in’ is +automatically generated from ‘Makefile.am’, and all needed changes +to ‘Makefile.am’ are already made by running ‘gettextize’. +

+ + + +

13.4.11 ‘Makefile.in’ in ‘src/’

+ +

Some of the modifications made in the main ‘Makefile.in’ will +also be needed in the ‘Makefile.in’ from your package sources, +which we assume here to be in the ‘src/’ subdirectory. Here are +all the modifications needed in ‘src/Makefile.in’: +

+
    +
  1. +In view of the ‘dist:’ goal, you should have these lines near the +beginning of ‘src/Makefile.in’: + +
     
    PACKAGE = @PACKAGE@
+VERSION = @VERSION@
+
    + +
  2. +If not done already, you should guarantee that top_srcdir +gets defined. This will serve for cpp include files. Just add +the line: + +
     
    top_srcdir = @top_srcdir@
+
    + +
  3. +You might also want to define subdir as ‘src’, later +allowing for almost uniform ‘dist:’ goals in all your +‘Makefile.in’. At list, the ‘dist:’ goal below assume that +you used: + +
     
    subdir = src
+
    + +
  4. +The main function of your program will normally call +bindtextdomain (see see section Triggering gettext Operations), like this: + +
     
    bindtextdomain (PACKAGE, LOCALEDIR);
+textdomain (PACKAGE);
+
    + +

    On native Windows platforms, the main function may call +wbindtextdomain instead of bindtextdomain. +

    +

    To make LOCALEDIR known to the program, add the following lines to +‘Makefile.in’: +

    +
     
    datadir = @datadir@
+datarootdir= @datarootdir@
+localedir = @localedir@
+DEFS = -DLOCALEDIR=$(localedir_c_make) @DEFS@
+
    + +

    $(localedir_c_make) expands to the value of localedir, in +C syntax, escaped for use in a Makefile. +Note that @datadir@ defaults to ‘$(prefix)/share’, and +$(localedir) defaults to ‘$(prefix)/share/locale’. +

    +
  5. +You should ensure that the final linking will use @LIBINTL@ or +@LTLIBINTL@ as a library. @LIBINTL@ is for use without +libtool, @LTLIBINTL@ is for use with libtool. An +easy way to achieve this is to manage that it gets into LIBS, like +this: + +
     
    LIBS = @LIBINTL@ @LIBS@
+
    + +

    In most packages internationalized with GNU gettext, one will +find a directory ‘lib/’ in which a library containing some helper +functions will be build. (You need at least the few functions which the +GNU gettext Library itself needs.) However some of the functions +in the ‘lib/’ also give messages to the user which of course should be +translated, too. Taking care of this, the support library (say +‘libsupport.a’) should be placed before @LIBINTL@ and +@LIBS@ in the above example. So one has to write this: +

    +
     
    LIBS = ../lib/libsupport.a @LIBINTL@ @LIBS@
+
    + +
  6. +Your ‘dist:’ goal has to conform with others. Here is a +reasonable definition for it: + +
     
    distdir = ../$(PACKAGE)-$(VERSION)/$(subdir)
+dist: Makefile $(DISTFILES)
+	for file in $(DISTFILES); do \
+	  ln $$file $(distdir) 2>/dev/null || cp -p $$file $(distdir) || exit 1; \
+	done
+
    + +
+ +

Note that if you are using GNU automake, ‘Makefile.in’ is +automatically generated from ‘Makefile.am’, and the first three +changes and the last change are not necessary. The remaining needed +‘Makefile.am’ modifications are the following: +

+
    +
  1. +To make LOCALEDIR known to the program, add the following to +‘Makefile.am’: + +
     
    <module>_CPPFLAGS = -DLOCALEDIR=$(localedir_c_make)
+
    + +

    for each specific module or compilation unit, or +

    +
     
    AM_CPPFLAGS = -DLOCALEDIR=$(localedir_c_make)
+
    + +

    for all modules and compilation units together. +

    +
  2. +To ensure that the final linking will use @LIBINTL@ or +@LTLIBINTL@ as a library, add the following to +‘Makefile.am’: + +
     
    <program>_LDADD = @LIBINTL@
+
    + +

    for each specific program, or +

    +
     
    LDADD = @LIBINTL@
+
    + +

    for all programs together. Remember that when you use libtool +to link a program, you need to use @LTLIBINTL@ instead of @LIBINTL@ +for that program. +

    +
+ + + + +

13.4.12 ‘gettext.h’ in ‘lib/’

+ +

Internationalization of packages, as provided by GNU gettext, is +optional. It can be turned off in two situations: +

+
    +
  • +When the installer has specified ‘./configure --disable-nls’. This +can be useful when small binaries are more important than features, for +example when building utilities for boot diskettes. It can also be useful +in order to get some specific C compiler warnings about code quality with +some older versions of GCC (older than 3.0). + +
  • +When the libintl.h header (with its associated libintl library, if any) is +not already installed on the system, it is preferable that the package builds +without internationalization support, rather than to give a compilation +error. +
+ +

A C preprocessor macro can be used to detect these two cases. Usually, +when libintl.h was found and not explicitly disabled, the +ENABLE_NLS macro will be defined to 1 in the autoconf generated +configuration file (usually called ‘config.h’). In the two negative +situations, however, this macro will not be defined, thus it will evaluate +to 0 in C preprocessor expressions. +

+ +

‘gettext.h’ is a convenience header file for conditional use of +‘<libintl.h>’, depending on the ENABLE_NLS macro. If +ENABLE_NLS is set, it includes ‘<libintl.h>’; otherwise it +defines no-op substitutes for the libintl.h functions. We recommend +the use of "gettext.h" over direct use of ‘<libintl.h>’, +so that portability to older systems is guaranteed and installers can +turn off internationalization if they want to. In the C code, you will +then write +

+
 
#include "gettext.h"
+
+ +

instead of +

+
 
#include <libintl.h>
+
+ +

The location of gettext.h is usually in a directory containing +auxiliary include files. In many GNU packages, there is a directory +‘lib/’ containing helper functions; ‘gettext.h’ fits there. +In other packages, it can go into the ‘src’ directory. +

+

Do not install the gettext.h file in public locations. Every +package that needs it should contain a copy of it on its own. +

+ + + +

13.5 Autoconf macros for use in ‘configure.ac’

+ +

GNU gettext installs macros for use in a package's +‘configure.ac’ or ‘configure.in’. +See (autoconf)Top section `Introduction' in The Autoconf Manual. +

+

In order to copy these macros into your package, +use the gettextize or autopoint programs. +See Invoking the gettextize Program or Invoking the autopoint Program. +Attempts to use the autoreconf program for this purpose are unreliable. +

+

The primary macro is, of course, AM_GNU_GETTEXT. +

+ + + + +

13.5.1 AM_GNU_GETTEXT in ‘gettext.m4’

+ +

The AM_GNU_GETTEXT macro tests for the presence of the GNU gettext +function family in either the C library or a separate libintl +library (shared or static libraries are both supported). It also invokes +AM_PO_SUBDIRS, thus preparing the ‘po/’ directories of the +package for building. +

+

AM_GNU_GETTEXT accepts up to two optional arguments. The general +syntax is +

+
 
AM_GNU_GETTEXT([intlsymbol], [needsymbol])
+
+ +

intlsymbol should always be ‘external’. +

+

If needsymbol is specified and is ‘need-ngettext’, then GNU +gettext implementations (in libc or libintl) without the ngettext() +function will be ignored. If needsymbol is specified and is +‘need-formatstring-macros’, then GNU gettext implementations that don't +support the ISO C 99 ‘<inttypes.h>’ formatstring macros will be ignored. +Only one needsymbol can be specified. These requirements can also be +specified by using the macro AM_GNU_GETTEXT_NEED elsewhere. To specify +more than one requirement, just specify the strongest one among them, or +invoke the AM_GNU_GETTEXT_NEED macro several times. The hierarchy +among the various alternatives is as follows: ‘need-formatstring-macros’ +implies ‘need-ngettext’. +

+

The AM_GNU_GETTEXT macro determines whether GNU gettext is +available and should be used. If so, it sets the USE_NLS variable +to ‘yes’; it defines ENABLE_NLS to 1 in the autoconf +generated configuration file (usually called ‘config.h’); it sets +the variables LIBINTL and LTLIBINTL to the linker options +for use in a Makefile (LIBINTL for use without libtool, +LTLIBINTL for use with libtool); it adds an ‘-I’ option to +CPPFLAGS if necessary. In the negative case, it sets +USE_NLS to ‘no’; it sets LIBINTL and LTLIBINTL +to empty and doesn't change CPPFLAGS. +

+

The complexities that AM_GNU_GETTEXT deals with are the following: +

+
    +
  • + +Some operating systems have gettext in the C library, for example +glibc. Some have it in a separate library libintl. GNU libintl +might have been installed as part of the GNU gettext package. + +
  • +GNU libintl, if installed, is not necessarily already in the search +path (CPPFLAGS for the include file search path, LDFLAGS for +the library search path). + +
  • +Except for glibc and the Solaris 11 libc, the operating system's native +gettext cannot exploit the GNU mo files, doesn't have the +necessary locale dependency features, and cannot convert messages from +the catalog's text encoding to the user's locale encoding. + +
  • +GNU libintl, if installed, is not necessarily already in the +run time library search path. To avoid the need for setting an environment +variable like LD_LIBRARY_PATH, the macro adds the appropriate +run time search path options to the LIBINTL and LTLIBINTL +variables. This works on most systems, but not on some operating systems +with limited shared library support, like SCO. + +
  • +GNU libintl relies on POSIX/XSI iconv. The macro checks for +linker options needed to use iconv and appends them to the LIBINTL +and LTLIBINTL variables. +
+ +

Additionally, the AM_GNU_GETTEXT macro sets two variables, for +convenience. Both are derived from the --localedir configure +option. They are correct even on native Windows, where directories +frequently contain backslashes. +

+
localedir_c
+

This is the value of localedir, in C syntax. This variable is +meant to be substituted into C or C++ code through +AC_CONFIG_FILES. +

+
+
localedir_c_make
+

This is the value of localedir, in C syntax, escaped for use in +a Makefile. This variable is meant to be used in Makefiles, +for example for defining a C macro named LOCALEDIR: +

 
AM_CPPFLAGS = ... -DLOCALEDIR=$(localedir_c_make) ...
+
+
+
+ + + + +

13.5.2 AM_GNU_GETTEXT_VERSION in ‘gettext.m4’

+ +

The AM_GNU_GETTEXT_VERSION macro declares the version number of +the GNU gettext infrastructure that is used by the package. +

+

The use of this macro is optional; only the autopoint program makes +use of it (see section Integrating with Version Control Systems). +

+ + + +

13.5.3 AM_GNU_GETTEXT_NEED in ‘gettext.m4’

+ +

The AM_GNU_GETTEXT_NEED macro declares a constraint regarding the +GNU gettext implementation. The syntax is +

+
 
AM_GNU_GETTEXT_NEED([needsymbol])
+
+ +

If needsymbol is ‘need-ngettext’, then GNU gettext implementations +(in libc or libintl) without the ngettext() function will be ignored. +If needsymbol is ‘need-formatstring-macros’, then GNU gettext +implementations that don't support the ISO C 99 ‘<inttypes.h>’ +formatstring macros will be ignored. +

+

The optional second argument of AM_GNU_GETTEXT is also taken into +account. +

+

The AM_GNU_GETTEXT_NEED invocations can occur before or after +the AM_GNU_GETTEXT invocation; the order doesn't matter. +

+ + + +

13.5.4 AM_PO_SUBDIRS in ‘po.m4’

+ +

The AM_PO_SUBDIRS macro prepares the ‘po/’ directories of the +package for building. This macro should be used in internationalized +programs written in other programming languages than C, C++, Objective C, +for example sh, Python, Lisp. See Other Programming Languages for a list of programming languages that support localization +through PO files. +

+

The AM_PO_SUBDIRS macro determines whether internationalization +should be used. If so, it sets the USE_NLS variable to ‘yes’, +otherwise to ‘no’. It also determines the right values for Makefile +variables in each ‘po/’ directory. +

+ + + +

13.5.5 AM_XGETTEXT_OPTION in ‘po.m4’

+ +

The AM_XGETTEXT_OPTION macro registers a command-line option to be +used in the invocations of xgettext in the ‘po/’ directories +of the package. +

+

For example, if you have a source file that defines a function +‘error_at_line’ whose fifth argument is a format string, you can use +

 
AM_XGETTEXT_OPTION([--flag=error_at_line:5:c-format])
+
+

to instruct xgettext to mark all translatable strings in ‘gettext’ +invocations that occur as fifth argument to this function as ‘c-format’. +

+

See Invoking the xgettext Program for the list of options that xgettext +accepts. +

+

The use of this macro is an alternative to the use of the +‘XGETTEXT_OPTIONS’ variable in ‘po/Makevars’. +

+ + + +

13.5.6 AM_ICONV in ‘iconv.m4’

+ +

The AM_ICONV macro tests for the presence of the POSIX/XSI +iconv function family in either the C library or a separate +libiconv library. If found, it sets the am_cv_func_iconv +variable to ‘yes’; it defines HAVE_ICONV to 1 in the autoconf +generated configuration file (usually called ‘config.h’); it defines +ICONV_CONST to ‘const’ or to empty, depending on whether the +second argument of iconv() is of type ‘const char **’ or +‘char **’; it sets the variables LIBICONV and +LTLIBICONV to the linker options for use in a Makefile +(LIBICONV for use without libtool, LTLIBICONV for use with +libtool); it adds an ‘-I’ option to CPPFLAGS if +necessary. If not found, it sets LIBICONV and LTLIBICONV to +empty and doesn't change CPPFLAGS. +

+

The complexities that AM_ICONV deals with are the following: +

+
    +
  • + +Some operating systems have iconv in the C library, for example +glibc. Some have it in a separate library libiconv, for example +OSF/1 or FreeBSD. Regardless of the operating system, GNU libiconv +might have been installed. In that case, it should be used instead of the +operating system's native iconv. + +
  • +GNU libiconv, if installed, is not necessarily already in the search +path (CPPFLAGS for the include file search path, LDFLAGS for +the library search path). + +
  • +GNU libiconv is binary incompatible with some operating system's +native iconv, for example on FreeBSD. Use of an ‘iconv.h’ +and ‘libiconv.so’ that don't fit together would produce program +crashes. + +
  • +GNU libiconv, if installed, is not necessarily already in the +run time library search path. To avoid the need for setting an environment +variable like LD_LIBRARY_PATH, the macro adds the appropriate +run time search path options to the LIBICONV variable. This works +on most systems, but not on some operating systems with limited shared +library support, like SCO. +
+ +

‘iconv.m4’ is distributed with the GNU gettext package because +‘gettext.m4’ relies on it. +

+ + + +

13.6 Integrating with Version Control Systems

+ +

Many projects use version control systems for distributed development +and source backup. This section gives some advice how to manage the +uses of gettextize, autopoint and autoconf on +version controlled files. +

+ + + + +

13.6.1 Avoiding version mismatch in distributed development

+ +

In a project development with multiple developers, there should be a +single developer who occasionally - when there is desire to upgrade to +a new gettext version - runs gettextize and performs the +changes listed in Files You Must Create or Alter, and then commits his changes +to the repository. +

+

It is highly recommended that all developers on a project use the same +version of GNU gettext in the package. In other words, if a +developer runs gettextize, he should go the whole way, make the +necessary remaining changes and commit his changes to the repository. +Otherwise the following damages will likely occur: +

+
    +
  • +Apparent version mismatch between developers. Since some gettext +specific portions in ‘configure.ac’, ‘configure.in’ and +Makefile.am, Makefile.in files depend on the gettext +version, the use of infrastructure files belonging to different +gettext versions can easily lead to build errors. + +
  • +Hidden version mismatch. Such version mismatch can also lead to +malfunctioning of the package, that may be undiscovered by the developers. +The worst case of hidden version mismatch is that internationalization +of the package doesn't work at all. + +
  • +Release risks. All developers implicitly perform constant testing on +a package. This is important in the days and weeks before a release. +If the guy who makes the release tar files uses a different version +of GNU gettext than the other developers, the distribution will +be less well tested than if all had been using the same gettext +version. For example, it is possible that a platform specific bug goes +undiscovered due to this constellation. +
+ + + + +

13.6.2 Files to put under version control

+ +

There are basically three ways to deal with generated files in the +context of a version controlled repository, such as ‘configure’ +generated from ‘configure.ac’, parser.c generated +from parser.y, or po/Makefile.in.in autoinstalled +by gettextize or autopoint. +

+
    +
  1. +All generated files are always committed into the repository. + +
  2. +All generated files are committed into the repository occasionally, +for example each time a release is made. + +
  3. +Generated files are never committed into the repository. +
+ +

Each of these three approaches has different advantages and drawbacks. +

+
    +
  1. +The advantage is that anyone can check out the source at any moment and +gets a working build. The drawbacks are: 1a. It requires some frequent +"push" actions by the maintainers. 1b. The repository grows in size +quite fast. + +
  2. +The advantage is that anyone can check out the source, and the usual +"./configure; make" will work. The drawbacks are: 2a. The one who +checks out the repository needs tools like GNU automake, GNU +autoconf, GNU m4 installed in his PATH; sometimes he +even needs particular versions of them. 2b. When a release is made +and a commit is made on the generated files, the other developers get +conflicts on the generated files when merging the local work back to +the repository. Although these conflicts are easy to resolve, they +are annoying. + +
  3. +The advantage is less work for the maintainers. The drawback is that +anyone who checks out the source not only needs tools like GNU +automake, GNU autoconf, GNU m4 installed in his +PATH, but also that he needs to perform a package specific pre-build +step before being able to "./configure; make". +
+ +

For the first and second approach, all files modified or brought in +by the occasional gettextize invocation and update should be +committed into the repository. +

+

For the third approach, the maintainer can omit from the repository +all the files that gettextize mentions as "copy". Instead, he +adds to the ‘configure.ac’ or ‘configure.in’ a line of the +form +

+
 
AM_GNU_GETTEXT_VERSION(0.25.1)
+
+ +

and adds to the package's pre-build script an invocation of +‘autopoint’. For everyone who checks out the source, this +autopoint invocation will copy into the right place the +gettext infrastructure files that have been omitted from the repository. +

+

The version number used as argument to AM_GNU_GETTEXT_VERSION is +the version of the gettext infrastructure that the package wants +to use. It is also the minimum version number of the ‘autopoint’ +program. So, if you write AM_GNU_GETTEXT_VERSION(0.11.5) then the +developers can have any version >= 0.11.5 installed; the package will work +with the 0.11.5 infrastructure in all developers' builds. When the +maintainer then runs gettextize from, say, version 0.12.1 on the package, +the occurrence of AM_GNU_GETTEXT_VERSION(0.11.5) will be changed +into AM_GNU_GETTEXT_VERSION(0.12.1), and all other developers that +use the CVS will henceforth need to have GNU gettext 0.12.1 or newer +installed. +

+ + + +

13.6.3 Put PO Files under Version Control

+ +

Since translations are valuable assets as well as the source code, it +would make sense to put them under version control. The GNU gettext +infrastructure supports two ways to deal with translations in the +context of a version controlled repository. +

+
    +
  1. +Both POT file and PO files are committed into the repository. + +
  2. +Only PO files are committed into the repository. + +
+ +

If a POT file is absent when building, it will be generated by +scanning the source files with xgettext, and then the PO files +are regenerated as a dependency. On the other hand, some maintainers +want to keep the POT file unchanged during the development phase. So, +even if a POT file is present and older than the source code, it won't +be updated automatically. You can manually update it with make +$(DOMAIN).pot-update, and commit it at certain point. +

+

Special advices for particular version control systems: +

+
    +
  • +Recent version control systems, Git for instance, ignore file's +timestamp. In that case, PO files can be accidentally updated even if +a POT file is not updated. To prevent this, you can set +‘PO_DEPENDS_ON_POT’ variable to no in the ‘Makevars’ +file and do make update-po manually. + +
  • +Location comments such as #: lib/error.c:116 are sometimes +annoying, since these comments are volatile and may introduce unwanted +change to the working copy when building. To mitigate this, you can +decide to omit those comments from the PO files in the repository. + +

    This is possible with the --no-location option of the +msgmerge command (6). The drawback is +that, if the location information is needed, translators have to +recover the location comments by running msgmerge again. +

    +
+ + + + +

13.6.4 Invoking the autopoint Program

+ + +
 
autopoint [option]...
+
+ +

The autopoint program copies standard gettext infrastructure files +into a source package. It extracts from a macro call of the form +AM_GNU_GETTEXT_VERSION(version), found in the package's +‘configure.in’ or ‘configure.ac’ file, the gettext version +used by the package, and copies the infrastructure files belonging to +this version into the package. +

+

To extract the latest available infrastructure which satisfies a version +requirement, then you can use the form +AM_GNU_GETTEXT_REQUIRE_VERSION(version) instead. For +example, if gettext 0.25.1 is installed on your system +and 0.19.1 is requested, then the infrastructure files of version +0.25.1 will be copied into a source package. +

+ + +

13.6.4.1 Options

+ +
+
‘-f’
+
‘--force’
+
+ +

Force overwriting of files that already exist. +

+
+
‘-n’
+
‘--dry-run’
+
+ +

Print modifications but don't perform them. All file copying actions that +autopoint would normally execute are inhibited and instead only +listed on standard output. +

+
+
+ + + +

13.6.4.2 Informative output

+ +
+
‘--help’
+
+

Display this help and exit. +

+
+
‘--version’
+
+

Output version information and exit. +

+
+
+ +

autopoint supports the GNU gettext versions from 0.10.35 +to the current one, 0.25.1. In order to apply +autopoint to a package using a gettext version newer than +0.25.1, you need to install this same version of GNU +gettext at least. +

+

In packages using GNU automake, an invocation of autopoint +should be followed by invocations of aclocal and then autoconf +and autoheader. The reason is that autopoint installs some +autoconf macro files, which are used by aclocal to create +‘aclocal.m4’, and the latter is used by autoconf to create the +package's ‘configure’ script and by autoheader to create the +package's ‘config.h.in’ include file template. +

+

The name ‘autopoint’ is an abbreviation of ‘auto-po-intl-m4’; +in earlier versions, the tool copied or updated mostly files in the ‘po’, +‘intl’, ‘m4’ directories. +

+ + + +

13.7 Creating a Distribution Tarball

+ +

In projects that use GNU automake, the usual commands for creating +a distribution tarball, ‘make dist’ or ‘make distcheck’, +automatically update the PO files as needed. +

+

If GNU automake is not used, the maintainer needs to perform this +update before making a release: +

+
 
$ ./configure
+$ (cd po; make update-po)
+$ make distclean
+
+ + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_14.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_14.html new file mode 100644 index 0000000000000000000000000000000000000000..1c5d5d762d931f611d9e02b4535304b08ea1b525 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_14.html @@ -0,0 +1,127 @@ + + + + + +GNU gettext utilities: 14. The Installer's and Distributor's View + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

14. The Installer's and Distributor's View

+ +

By default, packages fully using GNU gettext, internally, +are installed in such a way as to allow translation of +messages. At configuration time, those packages should +automatically detect whether the underlying host system already provides +the GNU gettext functions. If not, +the GNU gettext library should be automatically prepared +and used. Installers may use special options at configuration +time for changing this behavior. The command ‘./configure +--with-included-gettext’ bypasses system gettext to +use the included GNU gettext instead, +while ‘./configure --disable-nls’ +produces programs totally unable to translate messages. +

+ +

Internationalized packages have usually many ‘ll.po’ +or ‘ll_CC.po’ files, where +

+
    +
  • +ll gives an ISO 639 two-letter code identifying the language. +For some languages, +a two-letter code does not exist, and a three-letter code is used instead. +
  • +The optional CC is an ISO 3166 two-letter code of a country or +territory. +
+ +

Unless translations are disabled, all those available are installed together +with the package. However, the environment variable LINGUAS +may be set, prior to configuration, to limit the installed set. +LINGUAS should then contain a space separated list of locale names +(of the form ll or ll_CC), +stating which languages or language variants are allowed. +

+

GNU gettext uses *.its and *.loc files (see section Preparing Rules for XML Internationalization) +from other packages, provided they are installed in +‘prefix/share/gettext/its/’, +where prefix is the value of the --prefix option +passed to gettext's configure script. +So, this is the canonical location for installing *.its and *.loc files +from other packages. +

+ + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_15.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_15.html new file mode 100644 index 0000000000000000000000000000000000000000..4b9234993182c7119d8939e02e97c8310d1b44ac --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_15.html @@ -0,0 +1,4710 @@ + + + + + +GNU gettext utilities: 15. Other Programming Languages + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

15. Other Programming Languages

+ +

While the presentation of gettext focuses mostly on C and +implicitly applies to C++ as well, its scope is far broader than that: +Many programming languages, scripting languages and other textual data +like GUI resources or package descriptions can make use of the gettext +approach. +

+ + + + +

15.1 The Language Implementor's View

+ +

All programming and scripting languages that have the notion of strings +are eligible to supporting gettext. Supporting gettext +means the following: +

+
    +
  1. +You should add to the language a syntax for translatable strings. In +principle, a function call of gettext would do, but a shorthand +syntax helps keeping the legibility of internationalized programs. For +example, in C we use the syntax _("string"), and in GNU awk we use +the shorthand _"string". + +
  2. +You should arrange that evaluation of such a translatable string at +runtime calls the gettext function, or performs equivalent +processing. + +
  3. +Similarly, you should make the functions ngettext, +dcgettext, dcngettext available from within the language. +These functions are less often used, but are nevertheless necessary for +particular purposes: ngettext for correct plural handling, and +dcgettext and dcngettext for obeying other locale-related +environment variables than LC_MESSAGES, such as LC_TIME or +LC_MONETARY. For these latter functions, you need to make the +LC_* constants, available in the C header <locale.h>, +referenceable from within the language, usually either as enumeration +values or as strings. + +
  4. +You should allow the programmer to designate a message domain, either by +making the textdomain function available from within the +language, or by introducing a magic variable called TEXTDOMAIN. +Similarly, you should allow the programmer to designate where to search +for message catalogs, by providing access to the bindtextdomain +function or — on native Windows platforms — to the wbindtextdomain +function. + +
  5. +You should either perform a setlocale (LC_ALL, "") call during +the startup of your language runtime, or allow the programmer to do so. +Remember that gettext will act as a no-op if the LC_MESSAGES and +LC_CTYPE locale categories are not both set. + +
  6. +A programmer should have a way to extract translatable strings from a +program into a PO file. The GNU xgettext program is being +extended to support very different programming languages. Please +contact the GNU gettext maintainers to help them doing this. +The GNU gettext maintainers will need from you a formal +description of the lexical structure of source files. It should +answer the questions: +
      +
    • +What does a token look like? +
    • +What does a string literal look like? What escape characters exist +inside a string? +
    • +What escape characters exist outside of strings? If Unicode escapes +are supported, are they applied before or after tokenization? +
    • +What is the syntax for function calls? How are consecutive arguments +in the same function call separated? +
    • +What is the syntax for comments? +
    +

    Based on this description, the GNU gettext maintainers +can add support to xgettext. +

    +

    If the string extractor is best integrated into your language's parser, +GNU xgettext can function as a front end to your string extractor. +

    +
  7. +The language's library should have a string formatting facility. +Additionally: +
      +
    1. +There must be a way, in the format string, to denote the arguments by a +positional number or a name. This is needed because for some languages +and some messages with more than one substitutable argument, the +translation will need to output the substituted arguments in different +order. See section Special Comments preceding Keywords. +
    2. +The syntax of format strings must be documented in a way that translators +can understand. The GNU gettext manual will be extended to +include a pointer to this documentation. +
    +

    Based on this, the GNU gettext maintainers can add a format string +equivalence checker to msgfmt, so that translators get told +immediately when they have made a mistake during the translation of a +format string. +

    +
  8. +If the language has more than one implementation, and not all of the +implementations use gettext, but the programs should be portable +across implementations, you should provide a no-i18n emulation, that +makes the other implementations accept programs written for yours, +without actually translating the strings. + +
  9. +To help the programmer in the task of marking translatable strings, +which is sometimes performed using the Emacs PO mode (see section Marking Translatable Strings), +you are welcome to +contact the GNU gettext maintainers, so they can add support for +your language to ‘po-mode.el’. +
+ +

On the implementation side, two approaches are possible, with +different effects on portability and copyright: +

+
    +
  • +You may link against GNU gettext functions if they are found in +the C library. For example, an autoconf test for gettext() and +ngettext() will detect this situation. For the moment, this test +will succeed on GNU systems and on Solaris 11 platforms. No severe +copyright restrictions apply, except if you want to distribute statically +linked binaries. + +
  • +You may emulate or reimplement the GNU gettext functionality. +This has the advantage of full portability and no copyright +restrictions, but also the drawback that you have to reimplement the GNU +gettext features (such as the LANGUAGE environment +variable, the locale aliases database, the automatic charset conversion, +and plural handling). +
+ + + + +

15.2 The Programmer's View

+ +

For the programmer, the general procedure is the same as for the C +language. The Emacs PO mode marking supports other languages, and the GNU +xgettext string extractor recognizes other languages based on the +file extension or a command-line option. In some languages, +setlocale is not needed because it is already performed by the +underlying language runtime. +

+ + + +

15.3 The Translator's View

+ +

The translator works exactly as in the C language case. The only +difference is that when translating format strings, she has to be aware +of the language's particular syntax for positional arguments in format +strings. +

+ + + + +

15.3.1 C Format Strings

+ +

C format strings are described in POSIX (IEEE P1003.1 2001), section +XSH 3 fprintf(), +https://pubs.opengroup.org/onlinepubs/9799919799/functions/fprintf.html. +See also the fprintf() manual page +man fprintf. +

+

Although format strings with positions that reorder arguments, such as +

+
 
"Only %2$d bytes free on '%1$s'."
+
+ +

which is semantically equivalent to +

+
 
"'%s' has only %d bytes free."
+
+ +

are a POSIX/XSI feature and not specified by ISO C 99, translators can rely +on this reordering ability: On the few platforms where printf(), +fprintf() etc. don't support this feature natively, ‘libintl.a’ +or ‘libintl.so’ provides replacement functions, and GNU <libintl.h> +activates these replacement functions automatically. +

+ +

C format strings can contain placeholders +that reference macros defined in ISO C 99 <inttypes.h>. +For example, <PRId64> references the macro PRId64. +The value of such a macro is system-dependent, +but programmers and translators do not need to know this value. +ISO C 23 specifies system-independent format string elements, +for example, "%w64d" instead of "%" PRId64; +however, as of 2024, these are not implemented across systems +and therefore cannot be used portably. +

+ + +

As a special feature for Farsi (Persian) and maybe Arabic, translators can +insert an ‘I’ flag into numeric format directives. For example, the +translation of "%d" can be "%Id". The effect of this flag, +on systems with GNU libc, is that in the output, the ASCII digits are +replaced with the ‘outdigits’ defined in the LC_CTYPE locale +category. On other systems, the gettext function removes this flag, +so that it has no effect. +

+

Note that the programmer should not put this flag into the +untranslated string. (Putting the ‘I’ format directive flag into an +msgid string would lead to undefined behaviour on platforms without +glibc when NLS is disabled.) +

+ + + +

15.3.2 Objective C Format Strings

+ +

Objective C format strings are like C format strings. They support an +additional format directive: "%@", which when executed consumes an argument +of type Object *. +

+ +

Objective C format strings, like C format strings, can contain placeholders +that reference macros defined in ISO C 99 <inttypes.h>. +

+ + + +

15.3.3 C++ Format Strings

+ +

C++ format strings are described in ISO C++ 20, namely in +https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2020/n4861.pdf, +section 20.20.2 Format string [format.string]. +

+

An easier-to-read description is found at +https://en.cppreference.com/w/cpp/utility/format/format#Parameters and +https://en.cppreference.com/w/cpp/utility/format/formatter#Standard_format_specification. +

+ + + +

15.3.4 Python Format Strings

+ +

There are two kinds of format strings in Python: those acceptable to +the Python built-in format operator %, labelled as +‘python-format’, and those acceptable to the format method +of the ‘str’ object. +

+

Python % format strings are described in +Python Library reference / +5. Built-in Types / +5.6. Sequence Types / +5.6.2. String Formatting Operations. +https://docs.python.org/2/library/stdtypes.html#string-formatting-operations. +

+

Python brace format strings are described in PEP 3101 – Advanced +String Formatting, https://www.python.org/dev/peps/pep-3101/. +

+ + + +

15.3.5 Java Format Strings

+ +

There are two kinds of format strings in Java: those acceptable to the +MessageFormat.format function, labelled as ‘java-format’, +and those acceptable to the String.format and +PrintStream.printf functions, labelled as ‘java-printf-format’. +

+

Java format strings are described in the JDK documentation for class +java.text.MessageFormat, +https://docs.oracle.com/javase/7/docs/api/java/text/MessageFormat.html. +See also the ICU documentation +http://icu-project.org/apiref/icu4j/com/ibm/icu/text/MessageFormat.html. +

+

Java printf format strings are described in the JDK documentation +for class java.util.Formatter, +https://docs.oracle.com/javase/7/docs/api/java/util/Formatter.html. +

+ + + +

15.3.6 C# Format Strings

+ +

C# format strings are described in the .NET documentation for class +System.String and in +http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpConFormattingOverview.asp. +

+ + + +

15.3.7 JavaScript Format Strings

+ +

Although JavaScript specification itself does not define any format +strings, many JavaScript implementations provide printf-like +functions. xgettext understands a set of common format strings +used in popular JavaScript implementations including Gjs, Seed, and +Node.JS. In such a format string, a directive starts with ‘%’ +and is finished by a specifier: ‘%’ denotes a literal percent +sign, ‘c’ denotes a character, ‘s’ denotes a string, +‘b’, ‘d’, ‘o’, ‘x’, ‘X’ denote an integer, +‘f’ denotes floating-point number, ‘j’ denotes a JSON +object. +

+ + + +

15.3.8 Scheme Format Strings

+ +

Scheme format strings are documented in the SLIB manual, section +Format Specification. +

+ + + +

15.3.9 Lisp Format Strings

+ +

Lisp format strings are described in the Common Lisp HyperSpec, +chapter 22.3 Formatted Output, +http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/sec_22-3.html. +

+ + + +

15.3.10 Emacs Lisp Format Strings

+ +

Emacs Lisp format strings are documented in the Emacs Lisp reference, +section Formatting Strings, +https://www.gnu.org/manual/elisp-manual-21-2.8/html_chapter/elisp_4.html#SEC75. +Note that as of version 21, XEmacs supports numbered argument specifications +in format strings while FSF Emacs doesn't. +

+ + + +

15.3.11 librep Format Strings

+ +

librep format strings are documented in the librep manual, section +Formatted Output, +http://librep.sourceforge.net/librep-manual.html#Formatted%20Output, +http://www.gwinnup.org/research/docs/librep.html#SEC122. +

+ + + +

15.3.12 Rust Format Strings

+ +

Rust format strings are those supported by the formatx library +https://crates.io/crates/formatx. +These are those supported by the format! built-in +https://doc.rust-lang.org/std/fmt/ +with the restrictions listed in +https://crates.io/crates/formatx, section "Limitations". +

+

A Rust format string consists of +

    +
  • +an opening brace ‘{’, +
  • +an optional non-empty sequence of digits or an optional identifier, +
  • +optionally, a ‘:’ and a format specifier, +where a format specifier is of the form +[[fill]align][sign][#][0][minimumwidth][.precision][type] +where +
      +
    • - +the fill character is any character, +
    • - +the align flag is one of ‘<’, ‘>’, ‘^’, +
    • - +the sign is one of ‘+’, ‘-’, +
    • - +the # flag is ‘#’, +
    • - +the 0 flag is ‘0’, +
    • - +minimumwidth is a non-empty sequence of digits, +
    • - +precision is a non-empty sequence of digits, +
    • - +type is ‘?’, +
    +
  • +optional white-space, +
  • +a closing brace ‘}’. +
+

Brace characters ‘{’ and ‘}’ can be escaped by doubling them: +‘{{’ and ‘}}’. +

+ + + +

15.3.13 Go Format Strings

+ +

Go format strings are documented +on the Go packages site, for package fmt, +at https://pkg.go.dev/fmt. +

+ + + +

15.3.14 Ruby Format Strings

+ +

Ruby format strings are described in the documentation of the Ruby +functions format and sprintf, in +https://ruby-doc.org/core-2.7.1/Kernel.html#method-i-sprintf. +

+

There are two kinds of format strings in Ruby: +

    +
  • +Those that take a list of arguments without names. They support +argument reordering by use of the %n$ syntax. Note +that if one argument uses this syntax, all must use this syntax. +
  • +Those that take a hash table, containing named arguments. The +syntax is %<name>. Note that %{name} is +equivalent to %<name>s. +
+ + + + +

15.3.15 Shell Format Strings

+ +

Shell format strings, as supported by GNU gettext and the ‘envsubst’ +program, are strings with references to shell variables in the form +$variable or ${variable}. References of the form +${variable-default}, +${variable:-default}, +${variable=default}, +${variable:=default}, +${variable+replacement}, +${variable:+replacement}, +${variable?ignored}, +${variable:?ignored}, +that would be valid inside shell scripts, are not supported. The +variable names must consist solely of alphanumeric or underscore +ASCII characters, not start with a digit and be nonempty; otherwise such +a variable reference is ignored. +

+ + + +

15.3.16 awk Format Strings

+ +

awk format strings are described in the gawk documentation, section +Printf, +https://www.gnu.org/manual/gawk/html_node/Printf.html#Printf. +

+ + + +

15.3.17 Lua Format Strings

+ +

Lua format strings are described in the Lua reference manual, section String Manipulation, +https://www.lua.org/manual/5.1/manual.html#pdf-string.format. +

+ + + +

15.3.18 Object Pascal Format Strings

+ +

Object Pascal format strings are described in the documentation of the +Free Pascal runtime library, section Format, +https://www.freepascal.org/docs-html/rtl/sysutils/format.html. +

+ + + +

15.3.19 Modula-2 Format Strings

+ +

Modula-2 format strings are defined as follows: +

    +
  1. +Escape sequences are processed. +These escape sequences are understood: +‘\a’, ‘\b’, ‘\e’, ‘\f’, ‘\n’, ‘\r’, +‘\xhex-digits’, ‘\octal-digits’. +Other than that, a backslash is ignored. +
  2. +A directive consists of +
      +
    • +a ‘%’ character, +
    • +optionally a flag character ‘-’, +
    • +optionally a flag character ‘0’, +
    • +optionally a width specification (a nonnegative integer), +
    • +and finally a specifier: +‘s’ that formats a string, ‘c’ that formats a character, +‘d’ and ‘u’, that format a (signed/unsigned) integer in decimal, +or ‘x’, that formats an unsigned integer in hexadecimal. +
    +

    There is also the directive ‘%%’, that produces a single percent character. +

+ + + + +

15.3.20 D Format Strings

+ +

D format strings are described +in the documentation of the D module std.format, +at https://dlang.org/library/std/format.html. +

+ + + +

15.3.21 Smalltalk Format Strings

+ +

Smalltalk format strings are described in the GNU Smalltalk documentation, +class CharArray, methods ‘bindWith:’ and +‘bindWithArguments:’. +https://www.gnu.org/software/smalltalk/gst-manual/gst_68.html#SEC238. +In summary, a directive starts with ‘%’ and is followed by ‘%’ +or a nonzero digit (‘1’ to ‘9’). +

+ + + +

15.3.22 Qt Format Strings

+ +

Qt format strings are described in the documentation of the QString class +file:/usr/lib/qt-4.3.0/doc/html/qstring.html. +In summary, a directive consists of a ‘%’ followed by a digit. The same +directive cannot occur more than once in a format string. +

+ + + +

15.3.23 Qt Format Strings

+ +

Qt format strings are described in the documentation of the QObject::tr method +file:/usr/lib/qt-4.3.0/doc/html/qobject.html. +In summary, the only allowed directive is ‘%n’. +

+ + + +

15.3.24 KDE Format Strings

+ +

KDE 4 format strings are defined as follows: +A directive consists of a ‘%’ followed by a non-zero decimal number. +If a ‘%n’ occurs in a format strings, all of ‘%1’, ..., ‘%(n-1)’ +must occur as well, except possibly one of them. +

+ + + +

15.3.25 KUIT Format Strings

+ +

KUIT (KDE User Interface Text) is compatible with KDE 4 format strings, +while it also allows programmers to add semantic information to a format +string, through XML markup tags. For example, if the first format +directive in a string is a filename, programmers could indicate that +with a ‘filename’ tag, like ‘<filename>%1</filename>’. +

+

KUIT format strings are described in +https://api.kde.org/frameworks/ki18n/html/prg_guide.html#kuit_markup. +

+ + + +

15.3.26 Boost Format Strings

+ +

Boost format strings are described in the documentation of the +boost::format class, at +https://www.boost.org/libs/format/doc/format.html. +In summary, a directive has either the same syntax as in a C format string, +such as ‘%1$+5d’, or may be surrounded by vertical bars, such as +‘%|1$+5d|’ or ‘%|1$+5|’, or consists of just an argument number +between percent signs, such as ‘%1%’. +

+ + + +

15.3.27 Tcl Format Strings

+ +

Tcl format strings are described in the ‘format.n’ manual page, +http://www.scriptics.com/man/tcl8.3/TclCmd/format.htm. +

+ + + +

15.3.28 Perl Format Strings

+ +

There are two kinds of format strings in Perl: those acceptable to the +Perl built-in function printf, labelled as ‘perl-format’, +and those acceptable to the libintl-perl function __x, +labelled as ‘perl-brace-format’. +

+

Perl printf format strings are described in the sprintf +section of ‘man perlfunc’. +

+

Perl brace format strings are described in the +‘Locale::TextDomain(3pm)’ manual page of the CPAN package +libintl-perl. In brief, Perl format uses placeholders put between +braces (‘{’ and ‘}’). The placeholder must have the syntax +of simple identifiers. +

+ + + +

15.3.29 PHP Format Strings

+ +

PHP format strings are described in the documentation of the PHP function +sprintf, in ‘phpdoc/manual/function.sprintf.html’ or +http://www.php.net/manual/en/function.sprintf.php. +

+ + + +

15.3.30 GCC internal Format Strings

+ +

These format strings are used inside the GCC sources. In such a format +string, a directive starts with ‘%’, is optionally followed by a +size specifier ‘l’, an optional flag ‘+’, another optional flag +‘#’, and is finished by a specifier: ‘%’ denotes a literal +percent sign, ‘c’ denotes a character, ‘s’ denotes a string, +‘i’ and ‘d’ denote an integer, ‘o’, ‘u’, ‘x’ +denote an unsigned integer, ‘.*s’ denotes a string preceded by a +width specification, ‘H’ denotes a ‘location_t *’ pointer, +‘D’ denotes a general declaration, ‘F’ denotes a function +declaration, ‘T’ denotes a type, ‘A’ denotes a function argument, +‘C’ denotes a tree code, ‘E’ denotes an expression, ‘L’ +denotes a programming language, ‘O’ denotes a binary operator, +‘P’ denotes a function parameter, ‘Q’ denotes an assignment +operator, ‘V’ denotes a const/volatile qualifier. +

+ + + +

15.3.31 GFC internal Format Strings

+ +

These format strings are used inside the GNU Fortran Compiler sources, +that is, the Fortran frontend in the GCC sources. In such a format +string, a directive starts with ‘%’ and is finished by a +specifier: ‘%’ denotes a literal percent sign, ‘C’ denotes the +current source location, ‘L’ denotes a source location, ‘c’ +denotes a character, ‘s’ denotes a string, ‘i’ and ‘d’ +denote an integer, ‘u’ denotes an unsigned integer. ‘i’, +‘d’, and ‘u’ may be preceded by a size specifier ‘l’. +

+ + + +

15.3.32 YCP Format Strings

+ +

YCP sformat strings are described in the libycp documentation +file:/usr/share/doc/packages/libycp/YCP-builtins.html. +In summary, a directive starts with ‘%’ and is followed by ‘%’ +or a nonzero digit (‘1’ to ‘9’). +

+ + + + +

15.4 The Maintainer's View

+ +

For the maintainer, the general procedure differs from the C language +case: +

+
    +
  • +If only a single programming language is used, the XGETTEXT_OPTIONS +variable in ‘po/Makevars’ (see section ‘Makevars’ in ‘po/’) should be adjusted to +match the xgettext options for that particular programming language. +If the package uses more than one programming language with gettext +support, it becomes necessary to change the POT file construction rule +in ‘po/Makefile.in.in’. It is recommended to make one xgettext +invocation per programming language, each with the options appropriate for +that language, and to combine the resulting files using msgcat. +
+ + + + +

15.5 Individual Programming Languages

+ + + + + + + +

15.5.1 C, C++, Objective C

+ +
+
RPMs
+

gcc, gpp, gobjc, glibc, gettext +

+
+
Ubuntu packages
+

gcc, g++, gobjc, libc6-dev, libasprintf-dev +

+
+
File extension
+

For C: c, h. +
For C++: C, c++, cc, cxx, cpp, hpp. +
For Objective C: m. +

+
+
String syntax
+

"abc" +

+
+
gettext shorthand
+

_("abc") +

+
+
gettext/ngettext functions
+

gettext, dgettext, dcgettext, ngettext, +dngettext, dcngettext +

+
+
textdomain
+

textdomain function +

+
+
bindtextdomain
+

bindtextdomain and wbindtextdomain functions +

+
+
setlocale
+

Programmer must call setlocale (LC_ALL, "") +

+
+
Prerequisite
+

#include <libintl.h> +
#include <locale.h> +
#define _(string) gettext (string) +

+
+
Use or emulate GNU gettext
+

Use +

+
+
Extractor
+

xgettext -k_ +

+
+
Formatting with positions
+

fprintf "%2$d %1$d" +
In C++: autosprintf "%2$d %1$d" +(see (autosprintf)Top section `Introduction' in GNU autosprintf) +
In C++ 20 or newer: std::vformat "{1} {0}" +

+
+
Portability
+

autoconf (gettext.m4) and #if ENABLE_NLS +

+
+
po-mode marking
+

yes +

+
+ +

The following examples are available in the ‘examples’ directory: +hello-c, hello-c-gnome2, hello-c-gnome3, hello-c-http, +hello-c++, hello-c++20, +hello-c++-qt, hello-c++-kde, +hello-c++-gnome2, hello-c++-gnome3, hello-c++-wxwidgets, +hello-objc, hello-objc-gnustep, hello-objc-gnome2. +

+ + + +

15.5.2 Python

+ +
+
RPMs
+

python +

+
+
Ubuntu packages
+

python +

+
+
File extension
+

py +

+
+
String syntax
+

'abc', u'abc', r'abc', ur'abc', +
"abc", u"abc", r"abc", ur"abc", +
'''abc''', u'''abc''', r'''abc''', ur'''abc''', +
"""abc""", u"""abc""", r"""abc""", ur"""abc""" +

+
+
gettext shorthand
+

_('abc') etc. +

+
+
gettext/ngettext functions
+

gettext.gettext, gettext.dgettext, +gettext.ngettext, gettext.dngettext, +also ugettext, ungettext +

+
+
textdomain
+

gettext.textdomain function, or +gettext.install(domain) function +

+
+
bindtextdomain
+

gettext.bindtextdomain function, or +gettext.install(domain,localedir) function +

+
+
setlocale
+

not used by the gettext emulation +

+
+
Prerequisite
+

import gettext +

+
+
Use or emulate GNU gettext
+

emulate +

+
+
Extractor
+

xgettext +

+
+
Formatting with positions
+

'...%(ident)d...' % { 'ident': value } +
'...{ident}...'.format(ident=value) (see PEP 3101) +

+
+
Portability
+

fully portable +

+
+
po-mode marking
+

— +

+
+ +

An example is available in the ‘examples’ directory: hello-python. +

+

A note about format strings: Python supports format strings with unnamed +arguments, such as '...%d...', and format strings with named arguments, +such as '...%(ident)d...'. The latter are preferable for +internationalized programs, for two reasons: +

+
    +
  • +When a format string takes more than one argument, the translator can provide +a translation that uses the arguments in a different order, if the format +string uses named arguments. For example, the translator can reformulate +
     
    "'%(volume)s' has only %(freespace)d bytes free."
+
    +

    to +

     
    "Only %(freespace)d bytes free on '%(volume)s'."
+
    +

    Additionally, the identifiers also provide some context to the translator. +

    +
  • +In the context of plural forms, the format string used for the singular form +does not use the numeric argument in many languages. Even in English, one +prefers to write "one hour" instead of "1 hour". Omitting +individual arguments from format strings like this is only possible with +the named argument syntax. (With unnamed arguments, Python – unlike C – +verifies that the format string uses all supplied arguments.) +
+ +

A note about f-strings (PEP 498): xgettext +

    +
  • +syntactically recognizes f-strings, +
  • +is able to extract f-strings that contain no sub-expressions. +
+

However, xgettext does not extract f-strings marked for translation +that contain sub-expressions. This will not work as expected: +

 
_(f"The file {file[i]} does not exist.")
+
+

because the translator is generally not a programmer and should thus not be +confronted with expressions from the programming language. +

+ +

Related software

+ +

An internationalization system based on GNU gettext and PO files is +Babel. +

+ + + +

15.5.3 Java

+ + +
+
RPMs
+

java, java2 +

+
+
Ubuntu packages
+

default-jdk +

+
+
File extension
+

java +

+
+
String syntax
+

"abc", """text block""" +

+
+
gettext shorthand
+

i18n("abc") +

+
+
gettext/ngettext functions
+

GettextResource.gettext, GettextResource.ngettext, +GettextResource.pgettext, GettextResource.npgettext +

+
+
textdomain
+

—, use ResourceBundle.getResource instead +

+
+
bindtextdomain
+

—, use CLASSPATH instead +

+
+
setlocale
+

automatic +

+
+
Prerequisite
+

— +

+
+
Use or emulate GNU gettext
+

—, uses a Java specific message catalog format +

+
+
Extractor
+

xgettext -ki18n +

+
+
Formatting with positions
+

MessageFormat.format "{1,number} {0,number}" +or String.format "%2$d %1$d" +

+
+
Portability
+

fully portable +

+
+
po-mode marking
+

— +

+
+ +

Before marking strings as internationalizable, uses of the string +concatenation operator need to be converted to MessageFormat +applications. For example, "file "+filename+" not found" becomes +MessageFormat.format("file {0} not found", new Object[] { filename }). +Only after this is done, can the strings be marked and extracted. +

+

GNU gettext uses the native Java internationalization mechanism, namely +ResourceBundles. There are two formats of ResourceBundles: +.properties files and .class files. The .properties +format is a text file which the translators can directly edit, like PO +files, but which doesn't support plural forms. Whereas the .class +format is compiled from .java source code and can support plural +forms (provided it is accessed through an appropriate API, see below). +

+

To convert a PO file to a .properties file, the msgcat +program can be used with the option --properties-output. To convert +a .properties file back to a PO file, the msgcat program +can be used with the option --properties-input. All the tools +that manipulate PO files can work with .properties files as well, +if given the --properties-input and/or --properties-output +option. +

+

To convert a PO file to a ResourceBundle class, the msgfmt program +can be used with the option --java or --java2. To convert a +ResourceBundle back to a PO file, the msgunfmt program can be used +with the option --java. +

+

Two different programmatic APIs can be used to access ResourceBundles. +Note that both APIs work with all kinds of ResourceBundles, whether +GNU gettext generated classes, or other .class or .properties +files. +

+
    +
  1. +The java.util.ResourceBundle API. + +

    In particular, its getString function returns a string translation. +Note that a missing translation yields a MissingResourceException. +

    +

    This has the advantage of being the standard API. And it does not require +any additional libraries, only the msgcat generated .properties +files or the msgfmt generated .class files. But it cannot do +plural handling, even if the resource was generated by msgfmt from +a PO file with plural handling. +

    +
  2. +The gnu.gettext.GettextResource API. + +

    Reference documentation in Javadoc 1.1 style format is in the +javadoc2 directory. +

    +

    Its gettext function returns a string translation. Note that when +a translation is missing, the msgid argument is returned unchanged. +

    +

    This has the advantage of having the ngettext function for plural +handling and the pgettext and npgettext for strings constraint +to a particular context. +

    + +

    To use this API, one needs the libintl.jar file which is part of +the GNU gettext package and distributed under the LGPL. +

+ +

Four examples, using the second API, are available in the ‘examples’ +directory: hello-java, hello-java-awt, hello-java-swing, +hello-java-qtjambi. +

+

Now, to make use of the API and define a shorthand for ‘getString’, +there are three idioms that you can choose from: +

+
    +
  • +(This one assumes Java 1.5 or newer.) +In a unique class of your project, say ‘Util’, define a static variable +holding the ResourceBundle instance and the shorthand: + +
     
    private static ResourceBundle myResources =
+  ResourceBundle.getBundle("domain-name");
+public static String i18n(String s) {
+  return myResources.getString(s);
+}
+
    + +

    All classes containing internationalized strings then contain +

    +
     
    import static Util.i18n;
+
    + +

    and the shorthand is used like this: +

    +
     
    System.out.println(i18n("Operation completed."));
+
    + +
  • +In a unique class of your project, say ‘Util’, define a static variable +holding the ResourceBundle instance: + +
     
    public static ResourceBundle myResources =
+  ResourceBundle.getBundle("domain-name");
+
    + +

    All classes containing internationalized strings then contain +

    +
     
    private static ResourceBundle res = Util.myResources;
+private static String i18n(String s) { return res.getString(s); }
+
    + +

    and the shorthand is used like this: +

    +
     
    System.out.println(i18n("Operation completed."));
+
    + +
  • +You add a class with a very short name, say ‘S’, containing just the +definition of the resource bundle and of the shorthand: + +
     
    public class S {
+  public static ResourceBundle myResources =
+    ResourceBundle.getBundle("domain-name");
+  public static String i18n(String s) {
+    return myResources.getString(s);
+  }
+}
+
    + +

    and the shorthand is used like this: +

    +
     
    System.out.println(S.i18n("Operation completed."));
+
    +
+ +

Which of the three idioms you choose, will depend on whether your project +requires portability to Java versions prior to Java 1.5 and, if so, whether +copying two lines of codes into every class is more acceptable in your project +than a class with a single-letter name. +

+ + + +

15.5.4 C#

+ +
+
RPMs
+

mono or dotnet8.0 +

+
+
Ubuntu packages
+

mono-mcs or dotnet8 +

+
+
File extension
+

cs +

+
+
String syntax
+

"abc", @"abc" +

+
+
gettext shorthand
+

_("abc") +

+
+
gettext/ngettext functions
+

GettextResourceManager.GetString, +GettextResourceManager.GetPluralString +GettextResourceManager.GetParticularString +GettextResourceManager.GetParticularPluralString +

+
+
textdomain
+

new GettextResourceManager(domain) +

+
+
bindtextdomain
+

—, compiled message catalogs are located in subdirectories of the directory +containing the executable +

+
+
setlocale
+

automatic +

+
+
Prerequisite
+

— +

+
+
Use or emulate GNU gettext
+

—, uses a C# specific message catalog format +

+
+
Extractor
+

xgettext -k_ +

+
+
Formatting with positions
+

String.Format "{1} {0}" +

+
+
Portability
+

fully portable +

+
+
po-mode marking
+

— +

+
+ +

Before marking strings as internationalizable, uses of the string +concatenation operator need to be converted to String.Format +invocations. For example, "file "+filename+" not found" becomes +String.Format("file {0} not found", filename). +Only after this is done, can the strings be marked and extracted. +

+

GNU gettext uses the native C#/.NET internationalization mechanism, namely +the classes ResourceManager and ResourceSet. Applications +use the ResourceManager methods to retrieve the native language +translation of strings. An instance of ResourceSet is the in-memory +representation of a message catalog file. The ResourceManager loads +and accesses ResourceSet instances as needed to look up the +translations. +

+

There are two formats of ResourceSets that can be directly loaded by +the C# runtime: .resources files and .dll files. +

+
    +
  • +The .resources format is a binary file usually generated through the +resgen or monoresgen utility, but which doesn't support plural +forms. .resources files can also be embedded in .NET .exe files. +This only affects whether a file system access is performed to load the message +catalog; it doesn't affect the contents of the message catalog. + +
  • +On the other hand, the .dll format is a binary file that is compiled +from .cs source code and can support plural forms (provided it is +accessed through the GNU gettext API, see below). +
+ +

Note that these .NET .dll and .exe files are not tied to a +particular platform; their file format and GNU gettext for C# can be used +on any platform. +

+

To convert a PO file to a .resources file, the msgfmt program +can be used with the option ‘--csharp-resources’. To convert a +.resources file back to a PO file, the msgunfmt program can be +used with the option ‘--csharp-resources’. You can also, in some cases, +use the monoresgen program (from the mono/mcs package). +This program can also convert a .resources file back to a PO file. But +beware: as of this writing (January 2004), the monoresgen converter is +quite buggy. +

+

To convert a PO file to a .dll file, the msgfmt program can be +used with the option --csharp. The result will be a .dll file +containing a subclass of GettextResourceSet, which itself is a subclass +of ResourceSet. To convert a .dll file containing a +GettextResourceSet subclass back to a PO file, the msgunfmt +program can be used with the option --csharp. +

+

The advantages of the .dll format over the .resources format +are: +

+
    +
  1. +Freedom to localize: Users can add their own translations to an application +after it has been built and distributed. Whereas when the programmer uses +a ResourceManager constructor provided by the system, the set of +.resources files for an application must be specified when the +application is built and cannot be extended afterwards. + +
  2. +Plural handling: A message catalog in .dll format supports the plural +handling function GetPluralString. Whereas .resources files can +only contain data and only support lookups that depend on a single string. + +
  3. +Context handling: A message catalog in .dll format supports the +query-with-context functions GetParticularString and +GetParticularPluralString. Whereas .resources files can +only contain data and only support lookups that depend on a single string. + +
  4. +The GettextResourceManager that loads the message catalogs in +.dll format also provides for inheritance on a per-message basis. +For example, in Austrian (de_AT) locale, translations from the German +(de) message catalog will be used for messages not found in the +Austrian message catalog. This has the consequence that the Austrian +translators need only translate those few messages for which the translation +into Austrian differs from the German one. Whereas when working with +.resources files, each message catalog must provide the translations +of all messages by itself. + +
  5. +The GettextResourceManager that loads the message catalogs in +.dll format also provides for a fallback: The English msgid is +returned when no translation can be found. Whereas when working with +.resources files, a language-neutral .resources file must +explicitly be provided as a fallback. +
+ +

On the side of the programmatic APIs, the programmer can use either the +standard ResourceManager API and the GNU GettextResourceManager +API. The latter is an extension of the former, because +GettextResourceManager is a subclass of ResourceManager. +

+
    +
  1. +The System.Resources.ResourceManager API. + +

    This API works with resources in .resources format. +

    +

    The creation of the ResourceManager is done through +

     
      new ResourceManager(domainname, Assembly.GetExecutingAssembly())
+
    + +

    The GetString function returns a string's translation. Note that this +function returns null when a translation is missing (i.e. not even found in +the fallback resource file). +

    +
  2. +The GNU.Gettext.GettextResourceManager API. + +

    This API works with resources in .dll format. +

    +

    Reference documentation is in the +csharpdoc directory. +

    +

    The creation of the ResourceManager is done through +

     
      new GettextResourceManager(domainname)
+
    + +

    The GetString function returns a string's translation. Note that when +a translation is missing, the msgid argument is returned unchanged. +

    +

    The GetPluralString function returns a string translation with plural +handling, like the ngettext function in C. +

    +

    The GetParticularString function returns a string's translation, +specific to a particular context, like the pgettext function in C. +Note that when a translation is missing, the msgid argument is returned +unchanged. +

    +

    The GetParticularPluralString function returns a string translation, +specific to a particular context, with plural handling, like the +npgettext function in C. +

    + +

    To use this API, one needs the GNU.Gettext.dll file which is part of +the GNU gettext package and distributed under the LGPL. +

+ +

You can also mix both approaches: use the +GNU.Gettext.GettextResourceManager constructor, but otherwise use +only the ResourceManager type and only the GetString method. +This is appropriate when you want to profit from the tools for PO files, +but don't want to change an existing source code that uses +ResourceManager and don't (yet) need the GetPluralString method. +

+

Two examples, using the second API, are available in the ‘examples’ +directory: hello-csharp, hello-csharp-forms. +

+

Now, to make use of the API and define a shorthand for ‘GetString’, +there are two idioms that you can choose from: +

+
    +
  • +In a unique class of your project, say ‘Util’, define a static variable +holding the ResourceManager instance: + +
     
    public static GettextResourceManager MyResourceManager =
+  new GettextResourceManager("domain-name");
+
    + +

    All classes containing internationalized strings then contain +

    +
     
    private static GettextResourceManager Res = Util.MyResourceManager;
+private static String _(String s) { return Res.GetString(s); }
+
    + +

    and the shorthand is used like this: +

    +
     
    Console.WriteLine(_("Operation completed."));
+
    + +
  • +You add a class with a very short name, say ‘S’, containing just the +definition of the resource manager and of the shorthand: + +
     
    public class S {
+  public static GettextResourceManager MyResourceManager =
+    new GettextResourceManager("domain-name");
+  public static String _(String s) {
+     return MyResourceManager.GetString(s);
+  }
+}
+
    + +

    and the shorthand is used like this: +

    +
     
    Console.WriteLine(S._("Operation completed."));
+
    +
+ +

Which of the two idioms you choose, will depend on whether copying two lines +of codes into every class is more acceptable in your project than a class +with a single-letter name. +

+ + + +

15.5.5 JavaScript

+ +
+
RPMs
+

js +

+
+
Ubuntu packages
+

gjs +

+
+
File extension
+

js +

+
+
String syntax
+
    +
  • "abc" + +
  • 'abc' + +
  • `abc` + +
  • tag`abc${expression}def{expression}...`, +see the description of ‘--tag’ in Invoking the xgettext Program. + +
+ +
+
gettext shorthand
+

_("abc") +

+
+
gettext/ngettext functions
+

gettext, dgettext, dcgettext, ngettext, +dngettext +

+
+
textdomain
+

textdomain function +

+
+
bindtextdomain
+

bindtextdomain function +

+
+
setlocale
+

automatic +

+
+
Prerequisite
+

— +

+
+
Use or emulate GNU gettext
+

use, or emulate +

+
+
Extractor
+

xgettext +

+
+
Formatting with positions
+

A format method on strings can be used. +But since it is not standard in JavaScript, +you have to enable it yourself, through +

+
 
const Format = imports.format;
+String.prototype.format = Format.format;
+
+ +
+
Portability
+

On platforms without gettext, the functions are not available. +

+
+
po-mode marking
+

— +

+
+ + + + +

15.5.6 TypeScript and TSX

+ +
+
RPMs
+

js +

+
+
Ubuntu packages
+

gjs +

+
+
File extension
+

ts for TypeScript, tsx for TSX (TypeScript with JSX) +

+
+
String syntax
+
    +
  • "abc" + +
  • 'abc' + +
  • `abc` + +
+ +
+
gettext shorthand
+

_("abc") +

+
+
gettext/ngettext functions
+

gettext, dgettext, dcgettext, ngettext, +dngettext +

+
+
textdomain
+

textdomain function +

+
+
bindtextdomain
+

bindtextdomain function +

+
+
setlocale
+

automatic +

+
+
Prerequisite
+

unknown +

+
+
Use or emulate GNU gettext
+

use, or emulate +

+
+
Extractor
+

xgettext +

+
+
Formatting with positions
+

A format method on strings can be used. +But since it is not standard in TypeScript, +you have to enable it yourself.

+
+
Portability
+

On platforms without gettext, the functions are not available. +

+
+
po-mode marking
+

— +

+
+ + + + +

15.5.7 GNU guile - Scheme

+ +
+
RPMs
+

guile +

+
+
Ubuntu packages
+

guile-2.0 +

+
+
File extension
+

scm +

+
+
String syntax
+

"abc" +

+
+
gettext shorthand
+

(_ "abc"), _"abc" (GIMP script-fu extension) +

+
+
gettext/ngettext functions
+

gettext, ngettext +

+
+
textdomain
+

textdomain +

+
+
bindtextdomain
+

bindtextdomain +

+
+
setlocale
+

(catch #t (lambda () (setlocale LC_ALL "")) (lambda args #f)) +

+
+
Prerequisite
+

(use-modules (ice-9 format)) +

+
+
Use or emulate GNU gettext
+

use +

+
+
Extractor
+

xgettext -L Guile -k_ +

+ + +

‘xgettext -L Scheme’ and ‘xgettext -L Guile’ are nearly equivalent. +They differ in the interpretation of escape sequences in string literals: +While ‘xgettext -L Scheme’ assumes the +R6RS and +R7RS +syntax of string literals, +‘xgettext -L Guile’ assumes the syntax of string literals +understood by Guile 2.x and 3.0 +(without command-line option --r6rs or --r7rs, +and before a #!r6rs directive is seen). +After a #!r6rs directive, +there is no difference any more +between ‘xgettext -L Scheme’ and ‘xgettext -L Guile’ +for the rest of the file. +

+
+
Formatting with positions
+

— +

+
+
Portability
+

On platforms without gettext, no translation. +

+
+
po-mode marking
+

— +

+
+ +

An example is available in the ‘examples’ directory: hello-guile. +

+ + + +

15.5.8 GNU clisp - Common Lisp

+ +
+
RPMs
+

clisp 2.28 or newer +

+
+
Ubuntu packages
+

clisp +

+
+
File extension
+

lisp +

+
+
String syntax
+

"abc" +

+
+
gettext shorthand
+

(_ "abc"), (ENGLISH "abc") +

+
+
gettext/ngettext functions
+

i18n:gettext, i18n:ngettext +

+
+
textdomain
+

i18n:textdomain +

+
+
bindtextdomain
+

i18n:textdomaindir +

+
+
setlocale
+

automatic +

+
+
Prerequisite
+

— +

+
+
Use or emulate GNU gettext
+

use +

+
+
Extractor
+

xgettext -k_ -kENGLISH +

+
+
Formatting with positions
+

format "~1@*~D ~0@*~D" +

+
+
Portability
+

On platforms without gettext, no translation. +

+
+
po-mode marking
+

— +

+
+ +

An example is available in the ‘examples’ directory: hello-clisp. +

+ + + +

15.5.9 GNU clisp C sources

+ +
+
RPMs
+

clisp +

+
+
Ubuntu packages
+

clisp +

+
+
File extension
+

d +

+
+
String syntax
+

"abc" +

+
+
gettext shorthand
+

ENGLISH ? "abc" : "" +
GETTEXT("abc") +
GETTEXTL("abc") +

+
+
gettext/ngettext functions
+

clgettext, clgettextl +

+
+
textdomain
+

— +

+
+
bindtextdomain
+

— +

+
+
setlocale
+

automatic +

+
+
Prerequisite
+

#include "lispbibl.c" +

+
+
Use or emulate GNU gettext
+

use +

+
+
Extractor
+

clisp-xgettext +

+
+
Formatting with positions
+

fprintf "%2$d %1$d" +

+
+
Portability
+

On platforms without gettext, no translation. +

+
+
po-mode marking
+

— +

+
+ + + + +

15.5.10 Emacs Lisp

+ +
+
RPMs
+

emacs, xemacs +

+
+
Ubuntu packages
+

emacs, xemacs21 +

+
+
File extension
+

el +

+
+
String syntax
+

"abc" +

+
+
gettext shorthand
+

(_"abc") +

+
+
gettext/ngettext functions
+

gettext, dgettext (xemacs only) +

+
+
textdomain
+

domain special form (xemacs only) +

+
+
bindtextdomain
+

bind-text-domain function (xemacs only) +

+
+
setlocale
+

automatic +

+
+
Prerequisite
+

— +

+
+
Use or emulate GNU gettext
+

use +

+
+
Extractor
+

xgettext +

+
+
Formatting with positions
+

format "%2$d %1$d" +

+
+
Portability
+

Only XEmacs. Without I18N3 defined at build time, no translation. +

+
+
po-mode marking
+

— +

+
+ + + + +

15.5.11 librep

+ +
+
RPMs
+

librep 0.15.3 or newer +

+
+
Ubuntu packages
+

librep16 +

+
+
File extension
+

jl +

+
+
String syntax
+

"abc" +

+
+
gettext shorthand
+

(_"abc") +

+
+
gettext/ngettext functions
+

gettext +

+
+
textdomain
+

textdomain function +

+
+
bindtextdomain
+

bindtextdomain function +

+
+
setlocale
+

— +

+
+
Prerequisite
+

(require 'rep.i18n.gettext) +

+
+
Use or emulate GNU gettext
+

use +

+
+
Extractor
+

xgettext +

+
+
Formatting with positions
+

format "%2$d %1$d" +

+
+
Portability
+

On platforms without gettext, no translation. +

+
+
po-mode marking
+

— +

+
+ +

An example is available in the ‘examples’ directory: hello-librep. +

+ + + +

15.5.12 Rust

+ + +
+
RPMs
+

rust, rust-cargo +

+
+
Ubuntu packages
+

rustc, cargo +

+
+
File extension
+

rs +

+
+
String syntax
+

"abc", r"abc", r#"abc"# etc. +

+
+
gettext shorthand
+

— +

+
+
gettext/ngettext functions
+

gettext, ngettext +

+
+
textdomain
+

textdomain function +

+
+
bindtextdomain
+

bindtextdomain function +

+
+
setlocale
+

setlocale function +

+
+
Prerequisite
+

$ cargo add gettext-rs +

+

use gettextrs::*; +

+

Note: We recommend the ‘gettext-rs’ crate. +We do not recommend the ‘gettext’ crate, because +(as of 2025) it does not handle +catalog fallback (e.g. from de_AT to de) +nor the LANGUAGE environment variable. +

+
+
Use or emulate GNU gettext
+

use +

+
+
Extractor
+

xgettext +

+
+
Formatting with positions
+

There are three common ways of doing string formatting in Rust: +

    +
  • +Using the built-ins format!, println!, etc. +This facility supports only constant strings, known at compile-time. +Thus it cannot be used with translated format strings. +You would get an error such as +“error: format argument must be a string literal”. +
  • +Using the strfmt library. +The facility cannot be recommended, +because it does not support the case where +some of the values are strings and some of the values are numbers +(without an excessive amount of contortions). +
  • +Using the formatx library. +This is the one we recommend. +
+ +

So, you have to convert the format!, println!, etc. +invocations to use formatx. +For example, +

 
println!("Hello {}, you got {} coins.", name, left);
+
+

becomes +

 
println!("{}", formatx!(gettext("Hello {}, you got {} coins."),
+                        name, left)
+               .unwrap());
+
+ +

For swapped positions, a translator may translate +"Hello {}, you got {} coins." +with +"Hello, {1} coins are left for you, {0}." +

+
+
Portability
+

fully portable +

+
+
po-mode marking
+

— +

+
+ +

An example is available in the ‘examples’ directory: hello-rust. +

+ + + + +

15.5.13 Go

+ + + +

Three packages are available, +that can be used for message localization with PO files: +

+ +

Go programs can be classified as one of: +

    +
  • +Single-locale programs, +that use the same locale across all threads of the program. +Example: Most command-line programs. +
  • +Multi-locale programs, +that use one locale per thread. +Example: Web servers. +
+ +

The three different packages support these two classes of programs differently: +

    +
  • +github.com/leonelquinteros/gotext package: +It has two different APIs, +one for the single-locale case and one for the multi-locale case. +
  • +github.com/gosexy/gettext package: +Its API supports only the single-locale case. +
  • +github.com/snapcore/go-gettext package: +Its API supports the single-locale case and the multi-locale case in the same way. +
+ + +

Gettext support characteristics:

+ +
+
RPMs
+

golang +

+
+
Ubuntu packages
+

golang-go (which provides the go program), +or gccgo (which provides a go-version command).
+gccgo has better portability; for example it works on SPARC CPUs. +

+
+
File extension
+

go +

+
+
String syntax
+

"abc", `abc` +

+
+
gettext shorthand
+

— +

+
+
gettext/ngettext functions
+

This depends on the API: +

    +
  • +github.com/leonelquinteros/gotext API: +Get, GetD, GetN, GetND +
  • +github.com/gosexy/gettext API: +Gettext, DGettext, DCGettext, NGettext, +DNGettext, DCNGettext +
  • +github.com/snapcore/go-gettext API: +Gettext, NGettext +
+ +

Note that the ngettext-like functions need to take +two argument strings that consume the same number of arguments. +For example, you cannot write +fmt.Sprintf(gotext.GetN("a piece", "%d pieces", n), n) +because in the singular case, +fmt.Sprintf would treat the unused argument as an error and +produce "a piece%!(EXTRA int=1)" instead of the desired "a piece". +As a workaround, you need to convert n to a string and +format that string with precision zero: +fmt.Sprintf(gotext.GetN("%.0sa piece", "%s pieces", n), strconv.Itoa(n)) +

+
+
textdomain
+

This depends on the API: +

    +
  • +github.com/leonelquinteros/gotext API: +Locale.AddDomain method or gotext.Configure function +
  • +github.com/gosexy/gettext API: +Textdomain function +
  • +github.com/snapcore/go-gettext API: +TextDomain constructor +
+ +
+
bindtextdomain
+

This depends on the API: +

    +
  • +github.com/leonelquinteros/gotext API: +gotext.NewLocale function or gotext.Configure function +
  • +github.com/gosexy/gettext API: +BindTextdomain function +
  • +github.com/snapcore/go-gettext API: +TextDomain constructor +
+ +
+
setlocale
+

This depends on the API: +

    +
  • +github.com/leonelquinteros/gotext API: +Programmer must determine the appropriate locale and pass it to the +gotext.NewLocale function or gotext.Configure function. +
  • +github.com/gosexy/gettext API: +Programmer must call gettext.SetLocale(gettext.LcAll, ""). +
  • +github.com/snapcore/go-gettext API: +Programmer must determine the appropriate locale and pass it to the +TextDomain.Locale method. +
+ +
+
Prerequisite
+

This depends on the API: +

    +
  • +github.com/leonelquinteros/gotext API: +import ("github.com/leonelquinteros/gotext") +
  • +github.com/gosexy/gettext API: +import ("github.com/gosexy/gettext") +
  • +github.com/snapcore/go-gettext API: +import ("github.com/snapcore/go-gettext") +
+ +
+
Use or emulate GNU gettext
+

This depends on the API: +

    +
  • +github.com/leonelquinteros/gotext API: +Emulate +
  • +github.com/gosexy/gettext API: +Use +
  • +github.com/snapcore/go-gettext API: +Emulate +
+ +
+
Extractor
+

xgettext +

+
+
Formatting with positions
+

fmt.Sprintf("%[2]d %[1]d", ...) +

+
+
Portability
+

fully portable +

+
+
po-mode marking
+

— +

+
+ +

Two examples are available in the ‘examples’ directory: +hello-go and hello-go-http. +

+ + + +

15.5.14 Ruby

+ +
+
RPMs
+

ruby, ruby-gettext +

+
+
Ubuntu packages
+

ruby, ruby-gettext +

+
+
File extension
+

rb +

+
+
String syntax
+

"abc", 'abc', %q/abc/ etc., +%q(abc), %q[abc], %q{abc} +

+
+
gettext shorthand
+

_("abc") +

+
+
gettext/ngettext functions
+

gettext, ngettext +

+
+
textdomain
+

— +

+
+
bindtextdomain
+

bindtextdomain function +

+
+
setlocale
+

— +

+
+
Prerequisite
+

require 'gettext' +include GetText +

+
+
Use or emulate GNU gettext
+

emulate +

+
+
Extractor
+

xgettext +

+
+
Formatting with positions
+

sprintf("%2$d %1$d", x, y) +
"%{new} replaces %{old}" % {:old => oldvalue, :new => newvalue} +

+
+
Portability
+

fully portable +

+
+
po-mode marking
+

— +

+
+ +

An example is available in the ‘examples’ directory: hello-ruby. +

+ + + +

15.5.15 sh - Shell Script

+ +
+
RPMs
+

bash, gettext +

+
+
Ubuntu packages
+

bash, gettext-base +

+
+
File extension
+

sh +

+
+
String syntax
+

"abc", 'abc', abc +

+
+
gettext shorthand
+

"`gettext \"abc\"`" +

+
+
gettext/ngettext functions
+
+ +

gettext, ngettext programs +
eval_gettext, eval_ngettext, eval_pgettext, +eval_npgettext shell functions +

+
+
textdomain
+
+

environment variable TEXTDOMAIN +

+
+
bindtextdomain
+
+

environment variable TEXTDOMAINDIR +

+
+
setlocale
+

automatic +

+
+
Prerequisite
+

. gettext.sh +

+
+
Use or emulate GNU gettext
+

use +

+
+
Extractor
+

xgettext +

+
+
Formatting with positions
+

— +

+
+
Portability
+

fully portable +

+
+
po-mode marking
+

— +

+
+ +

An example is available in the ‘examples’ directory: hello-sh. +

+ + + + +

15.5.15.1 Preparing Shell Scripts for Internationalization

+ +

Preparing a shell script for internationalization is conceptually similar +to the steps described in Preparing Program Sources. The concrete steps for shell +scripts are as follows. +

+
    +
  1. +Insert the line + +
     
    . gettext.sh
+
    + +

    near the top of the script. gettext.sh is a shell function library +that provides the functions +eval_gettext (see Invoking the eval_gettext function), +eval_ngettext (see Invoking the eval_ngettext function), +eval_pgettext (see Invoking the eval_pgettext function), and +eval_npgettext (see Invoking the eval_npgettext function). +You have to ensure that gettext.sh can be found in the PATH. +

    +
  2. +Set and export the TEXTDOMAIN and TEXTDOMAINDIR environment +variables. Usually TEXTDOMAIN is the package or program name, and +TEXTDOMAINDIR is the absolute pathname corresponding to +$prefix/share/locale, where $prefix is the installation location. + +
     
    TEXTDOMAIN=@PACKAGE@
+export TEXTDOMAIN
+TEXTDOMAINDIR=@LOCALEDIR@
+export TEXTDOMAINDIR
+
    + +
  3. +Prepare the strings for translation, as described in Preparing Translatable Strings. + +
  4. +Simplify translatable strings so that they don't contain command substitution +("`...`" or "$(...)"), variable access with defaulting (like +${variable-default}), access to positional arguments +(like $0, $1, ...) or highly volatile shell variables (like +$?). This can always be done through simple local code restructuring. +For example, + +
     
    echo "Usage: $0 [OPTION] FILE..."
+
    + +

    becomes +

    +
     
    program_name=$0
+echo "Usage: $program_name [OPTION] FILE..."
+
    + +

    Similarly, +

    +
     
    echo "Remaining files: `ls | wc -l`"
+
    + +

    becomes +

    +
     
    filecount="`ls | wc -l`"
+echo "Remaining files: $filecount"
+
    + +
  5. +For each translatable string, change the output command ‘echo’ or +‘$echo’ to ‘gettext’ (if the string contains no references to +shell variables) or to ‘eval_gettext’ (if it refers to shell variables), +followed by a no-argument ‘echo’ command (to account for the terminating +newline). Similarly, for cases with plural handling, replace a conditional +‘echo’ command with an invocation of ‘ngettext’ or +‘eval_ngettext’, followed by a no-argument ‘echo’ command. + +

    When doing this, you also need to add an extra backslash before the dollar +sign in references to shell variables, so that the ‘eval_gettext’ +function receives the translatable string before the variable values are +substituted into it. For example, +

    +
     
    echo "Remaining files: $filecount"
+
    + +

    becomes +

    +
     
    eval_gettext "Remaining files: \$filecount"; echo
+
    + +

    If the output command is not ‘echo’, you can make it use ‘echo’ +nevertheless, through the use of backquotes. However, note that inside +backquotes, backslashes must be doubled to be effective (because the +backquoting eats one level of backslashes). For example, assuming that +‘error’ is a shell function that signals an error, +

    +
     
    error "file not found: $filename"
+
    + +

    is first transformed into +

    +
     
    error "`echo \"file not found: \$filename\"`"
+
    + +

    which then becomes +

    +
     
    error "`eval_gettext \"file not found: \\\$filename\"`"
+
    +
+ + + + +

15.5.15.2 Contents of gettext.sh

+ +

gettext.sh, contained in the run-time package of GNU gettext, provides +the following: +

+ + + + + +

15.5.15.3 Invoking the gettext program

+ + +
 
gettext [option] [[textdomain] msgid]
+gettext [option] -s [msgid]...
+
+ + +

The gettext program displays the native language translation of a +textual message. +

+

Arguments +

+
+
‘-c context’
+
‘--context=context’
+
+ +

Specify the context for the messages to be translated. +See Using contexts for solving ambiguities for details. +

+
+
‘-d textdomain’
+
‘--domain=textdomain’
+
+ +

Retrieve translated messages from textdomain. Usually a textdomain +corresponds to a package, a program, or a module of a program. +

+
+
‘-e’
+
+

Enable expansion of some escape sequences. This option is for compatibility +with the ‘echo’ program or shell built-in. The escape sequences +‘\a’, ‘\b’, ‘\c’, ‘\f’, ‘\n’, ‘\r’, ‘\t’, +‘\v’, ‘\\’, and ‘\’ followed by one to three octal digits, are +interpreted like the System V ‘echo’ program did. +

+
+
‘-E’
+
+

This option is only for compatibility with the ‘echo’ program or shell +built-in. It has no effect. +

+
+
‘-h’
+
‘--help’
+
+ +

Display this help and exit. +

+
+
‘-n’
+
+

This option has only an effect if the -s option is given. It +suppresses the additional newline at the end. +

+
+
‘-V’
+
‘--version’
+
+ +

Output version information and exit. +

+
+
‘[textdomain] msgid’
+

Retrieve translated message corresponding to msgid from textdomain. +

+
+
+ +

If the textdomain parameter is not given, the domain is determined from +the environment variable TEXTDOMAIN. If the message catalog is not +found in the regular directory, another location can be specified with the +environment variable TEXTDOMAINDIR. +

+

When used with the -s option the program behaves like the ‘echo’ +command. But it does not simply copy its arguments to stdout. Instead those +messages found in the selected catalog are translated. Also, a newline is +added at the end, unless either the option -n is specified or the +option -e is specified and some of the argument strings contains a +‘\c’ escape sequence. +

+

Note: xgettext supports only the one-argument form of the +gettext invocation, where no options are present and the +textdomain is implicit, from the environment. +

+ + + +

15.5.15.4 Invoking the ngettext program

+ + +
 
ngettext [option] [textdomain] msgid msgid-plural count
+
+ + +

The ngettext program displays the native language translation of a +textual message whose grammatical form depends on a number. +

+

Arguments +

+
+
‘-c context’
+
‘--context=context’
+
+ +

Specify the context for the messages to be translated. +See Using contexts for solving ambiguities for details. +

+
+
‘-d textdomain’
+
‘--domain=textdomain’
+
+ +

Retrieve translated messages from textdomain. Usually a textdomain +corresponds to a package, a program, or a module of a program. +

+
+
‘-e’
+
+

Enable expansion of some escape sequences. This option is for compatibility +with the ‘gettext’ program. The escape sequences +‘\a’, ‘\b’, ‘\f’, ‘\n’, ‘\r’, ‘\t’, +‘\v’, ‘\\’, and ‘\’ followed by one to three octal digits, are +interpreted like the System V ‘echo’ program did. +

+
+
‘-E’
+
+

This option is only for compatibility with the ‘gettext’ program. It has +no effect. +

+
+
‘-h’
+
‘--help’
+
+ +

Display this help and exit. +

+
+
‘-V’
+
‘--version’
+
+ +

Output version information and exit. +

+
+
‘textdomain’
+

Retrieve translated message from textdomain. +

+
+
‘msgid msgid-plural’
+

Translate msgid (English singular) / msgid-plural (English plural). +

+
+
‘count’
+

Choose singular/plural form based on this value. +

+
+
+ +

If the textdomain parameter is not given, the domain is determined from +the environment variable TEXTDOMAIN. If the message catalog is not +found in the regular directory, another location can be specified with the +environment variable TEXTDOMAINDIR. +

+

Note: xgettext supports only the three-arguments form of the +ngettext invocation, where no options are present and the +textdomain is implicit, from the environment. +

+ + + +

15.5.15.5 Invoking the envsubst program

+ + +
 
envsubst [option] [shell-format]
+
+ + + + +

The envsubst program substitutes the values of environment variables. +

+

Operation mode +

+
+
‘-v’
+
‘--variables’
+
+ +

Output the variables occurring in shell-format. +

+
+
+ +

Informative output +

+
+
‘-h’
+
‘--help’
+
+ +

Display this help and exit. +

+
+
‘-V’
+
‘--version’
+
+ +

Output version information and exit. +

+
+
+ +

In normal operation mode, standard input is copied to standard output, +with references to environment variables of the form $VARIABLE or +${VARIABLE} being replaced with the corresponding values. If a +shell-format is given, only those environment variables that are +referenced in shell-format are substituted; otherwise all environment +variables references occurring in standard input are substituted. +

+

These substitutions are a subset of the substitutions that a shell performs +on unquoted and double-quoted strings. Other kinds of substitutions done +by a shell, such as ${variable-default} or +$(command-list) or `command-list`, are not performed +by the envsubst program, due to security reasons. +

+

When --variables is used, standard input is ignored, and the output +consists of the environment variables that are referenced in +shell-format, one per line. +

+ + + +

15.5.15.6 Invoking the eval_gettext function

+ +
 
eval_gettext msgid
+
+ + +

This function outputs the native language translation of a textual message, +performing dollar-substitution on the result. Note that only shell variables +mentioned in msgid will be dollar-substituted in the result. +

+ + + +

15.5.15.7 Invoking the eval_ngettext function

+ +
 
eval_ngettext msgid msgid-plural count
+
+ + +

This function outputs the native language translation of a textual message +whose grammatical form depends on a number, performing dollar-substitution +on the result. Note that only shell variables mentioned in msgid or +msgid-plural will be dollar-substituted in the result. +

+ + + +

15.5.15.8 Invoking the eval_pgettext function

+ +
 
eval_pgettext msgctxt msgid
+
+ + +

This function outputs the native language translation of a textual message +in the given context msgctxt (see Using contexts for solving ambiguities), performing +dollar-substitution on the result. Note that only shell variables mentioned +in msgid will be dollar-substituted in the result. +

+ + + +

15.5.15.9 Invoking the eval_npgettext function

+ +
 
eval_npgettext msgctxt msgid msgid-plural count
+
+ + +

This function outputs the native language translation of a textual message +whose grammatical form depends on a number in the given context msgctxt +(see Using contexts for solving ambiguities), performing dollar-substitution on the result. Note +that only shell variables mentioned in msgid or msgid-plural +will be dollar-substituted in the result. +

+ + + +

15.5.16 bash - Bourne-Again Shell Script

+ +

GNU bash 2.0 or newer has a special shorthand for translating a +string and substituting variable values in it: $"msgid". But +the use of this construct is discouraged, due to the security +holes it opens and due to its portability problems. +

+

The security holes of $"..." come from the fact that after looking up +the translation of the string, bash processes it like it processes +any double-quoted string: dollar and backquote processing, like ‘eval’ +does. +

+
    +
  1. +In a locale whose encoding is one of BIG5, BIG5-HKSCS, GBK, GB18030, SHIFT_JIS, +JOHAB, some double-byte characters have a second byte whose value is +0x60. For example, the byte sequence \xe0\x60 is a single +character in these locales. Many versions of bash (all versions +up to bash-2.05, and newer versions on platforms without mbsrtowcs() +function) don't know about character boundaries and see a backquote character +where there is only a particular Chinese character. Thus it can start +executing part of the translation as a command list. This situation can occur +even without the translator being aware of it: if the translator provides +translations in the UTF-8 encoding, it is the gettext() function which +will, during its conversion from the translator's encoding to the user's +locale's encoding, produce the dangerous \x60 bytes. + +
  2. +A translator could - voluntarily or inadvertently - use backquotes +"`...`" or dollar-parentheses "$(...)" in her translations. +The enclosed strings would be executed as command lists by the shell. +
+ +

The portability problem is that bash must be built with +internationalization support; this is normally not the case on systems +that don't have the gettext() function in libc. +

+ + + +

15.5.17 GNU awk

+ +
+
RPMs
+

gawk 3.1 or newer +

+
+
Ubuntu packages
+

gawk +

+
+
File extension
+

awk, gawk, twjr. +The file extension twjr is used by TexiWeb Jr +(https://github.com/arnoldrobbins/texiwebjr). +

+
+
String syntax
+

"abc" +

+
+
gettext shorthand
+

_"abc" +

+
+
gettext/ngettext functions
+

dcgettext, missing dcngettext in gawk-3.1.0 +

+
+
textdomain
+

TEXTDOMAIN variable +

+
+
bindtextdomain
+

bindtextdomain function +

+
+
setlocale
+

automatic, but missing setlocale (LC_MESSAGES, "") in gawk-3.1.0 +

+
+
Prerequisite
+

— +

+
+
Use or emulate GNU gettext
+

use +

+
+
Extractor
+

xgettext +

+
+
Formatting with positions
+

printf "%2$d %1$d" (GNU awk only) +

+
+
Portability
+

On platforms without gettext, no translation. On non-GNU awks, you must +define dcgettext, dcngettext and bindtextdomain +yourself. +

+
+
po-mode marking
+

— +

+
+ +

An example is available in the ‘examples’ directory: hello-gawk. +

+ + + +

15.5.18 Lua

+ +
+
RPMs
+

lua +

+
+
Ubuntu packages
+

lua, lua-gettext +
+You need to install the lua-gettext package from +https://gitlab.com/sukhichev/lua-gettext/blob/master/README.us.md. +Debian and Ubuntu packages of it are available. Download the +appropriate one, and install it through +‘sudo dpkg -i lua-gettext_0.0+nmu1_amd64.deb’. +

+
+
File extension
+

lua +

+
+
String syntax
+
    +
  • "abc" + +
  • 'abc' + +
  • [[abc]] + +
  • [=[abc]=] + +
  • [==[abc]==] + +
  • ... + +
+ +
+
gettext shorthand
+

_("abc") +

+
+
gettext/ngettext functions
+

gettext.gettext, gettext.dgettext, gettext.dcgettext, +gettext.ngettext, gettext.dngettext, gettext.dcngettext +

+
+
textdomain
+

textdomain function +

+
+
bindtextdomain
+

bindtextdomain function +

+
+
setlocale
+

automatic +

+
+
Prerequisite
+

require 'gettext' or running lua interpreter with -l gettext option +

+
+
Use or emulate GNU gettext
+

use +

+
+
Extractor
+

xgettext +

+
+
Formatting with positions
+

— +

+
+
Portability
+

On platforms without gettext, the functions are not available. +

+
+
po-mode marking
+

— +

+
+ + + + +

15.5.19 Pascal - Free Pascal Compiler

+ +
+
RPMs
+

fpc +

+
+
Ubuntu packages
+

fp-compiler, fp-units-fcl +

+
+
File extension
+

pp, pas +

+
+
String syntax
+

'abc' +

+
+
gettext shorthand
+

automatic +

+
+
gettext/ngettext functions
+

—, use ResourceString data type instead +

+
+
textdomain
+

—, use TranslateResourceStrings function instead +

+
+
bindtextdomain
+

—, use TranslateResourceStrings function instead +

+
+
setlocale
+

automatic, but uses only LANG, not LC_MESSAGES or LC_ALL +

+
+
Prerequisite
+

{$mode delphi} or {$mode objfpc}
uses gettext; +

+
+
Use or emulate GNU gettext
+

emulate partially +

+
+
Extractor
+

ppc386 followed by xgettext or rstconv +

+
+
Formatting with positions
+

uses sysutils;
format "%1:d %0:d" +

+
+
Portability
+

? +

+
+
po-mode marking
+

— +

+
+ +

The Pascal compiler has special support for the ResourceString data +type. It generates a .rst file. This is then converted to a +.pot file by use of xgettext or rstconv. At runtime, +a .mo file corresponding to translations of this .pot file +can be loaded using the TranslateResourceStrings function in the +gettext unit. +

+

An example is available in the ‘examples’ directory: hello-pascal. +

+ + + +

15.5.20 Modula-2

+ +
+
RPMs
+

gcc-gm2, libgm2 +

+
+
Ubuntu packages
+

gm2 +

+
+
File extension
+

mod, def +

+
+
String syntax
+

'abc', "abc" +

+
+
gettext shorthand
+

— +

+
+
gettext/ngettext functions
+

Gettext, DGettext, DCGettext, +NGettext, DNGettext, DCNGettext +

+
+
textdomain
+

TextDomain function +

+
+
bindtextdomain
+

BindTextDomain function +

+
+
setlocale
+

Programmer must call SetLocale (LC_ALL, "") +

+
+
Prerequisite
+

FROM Libintl IMPORT Gettext ...; +

+
+
Use or emulate GNU gettext
+

Use +

+
+
Extractor
+

xgettext +

+
+
Formatting with positions
+

— +

+
+
Portability
+

fully portable to all platforms supported by GNU Modula-2 +

+
+
po-mode marking
+

— +

+
+ +

An example is available in the ‘examples’ directory: hello-modula2. +

+ + + +

15.5.21 D

+ +
+
RPMs
+

gcc-gdc or ldc +

+
+
Ubuntu packages
+

gdc or ldc +

+
+
File extension
+

d +

+
+
String syntax
+

r"abc", `abc`, "abc", +q"[abc]", q"(abc)", q"<abc>", q"{abc}", +q{abc}, x"6A 6B 6C" +

+
+
gettext shorthand
+

_("abc") +

+
+
gettext/ngettext functions
+

gettext, dgettext, dcgettext, +ngettext, dngettext, dcngettext +

+

Note that the ngettext-like functions need to take +two argument strings that consume the same number of arguments. +For example, you cannot write +format(ngettext("a piece", "%d pieces", n), n) +because in the singular case, +format would treat the unused argument as an error and +throw an exception. +As a workaround, you need to convert n to a string and +format that string with precision zero: +format(ngettext("%.0sa piece", "%s pieces", n), to!string(n)) +or +format(ngettext("%.0sa piece", "%s pieces", n), text(n)) +

+
+
textdomain
+

textdomain function +

+
+
bindtextdomain
+

bindtextdomain function +

+
+
setlocale
+

Programmer must call setlocale (LC_ALL, "") +

+
+
Prerequisite
+

import gnu.libintl; +
alias _ = gettext; +

+
+
Use or emulate GNU gettext
+

Use +

+
+
Extractor
+

xgettext -k_ --flag=_:1:pass-c-format --flag=_:1:pass-d-format +

+
+
Formatting with positions
+

fprintf "%2$d %1$d", format "%2$d %1$d" +

+
+
Portability
+

fully portable +

+
+
po-mode marking
+

— +

+
+ +

An example is available in the ‘examples’ directory: hello-d. +

+ + + +

15.5.22 GNU Smalltalk

+ +
+
RPMs
+

smalltalk +

+
+
Ubuntu packages
+

gnu-smalltalk +

+
+
File extension
+

st +

+
+
String syntax
+

'abc' +

+
+
gettext shorthand
+

NLS ? 'abc' +

+
+
gettext/ngettext functions
+

LcMessagesDomain>>#at:, LcMessagesDomain>>#at:plural:with: +

+
+
textdomain
+

LcMessages>>#domain:localeDirectory: (returns a LcMessagesDomain +object).
+Example: I18N Locale default messages domain: 'gettext' localeDirectory: /usr/local/share/locale' +

+
+
bindtextdomain
+

LcMessages>>#domain:localeDirectory:, see above. +

+
+
setlocale
+

Automatic if you use I18N Locale default. +

+
+
Prerequisite
+

PackageLoader fileInPackage: 'I18N'! +

+
+
Use or emulate GNU gettext
+

emulate +

+
+
Extractor
+

xgettext +

+
+
Formatting with positions
+

'%1 %2' bindWith: 'Hello' with: 'world' +

+
+
Portability
+

fully portable +

+
+
po-mode marking
+

— +

+
+ +

An example is available in the ‘examples’ directory: +hello-smalltalk. +

+ + + +

15.5.23 Vala

+ +
+
RPMs
+

vala +

+
+
Ubuntu packages
+

valac +

+
+
File extension
+

vala +

+
+
String syntax
+
    +
  • "abc" + +
  • """abc""" + +
+ +
+
gettext shorthand
+

_("abc") +

+
+
gettext/ngettext functions
+

gettext, dgettext, dcgettext, ngettext, +dngettext, dpgettext, dpgettext2 +

+
+
textdomain
+

textdomain function, defined under the Intl namespace +

+
+
bindtextdomain
+

bindtextdomain function, defined under the Intl namespace +

+
+
setlocale
+

Programmer must call Intl.setlocale (LocaleCategory.ALL, "") +

+
+
Prerequisite
+

— +

+
+
Use or emulate GNU gettext
+

Use +

+
+
Extractor
+

xgettext +

+
+
Formatting with positions
+

Same as for the C language. +

+
+
Portability
+

autoconf (gettext.m4) and #if ENABLE_NLS +

+
+
po-mode marking
+

yes +

+
+ + + + +

15.5.24 wxWidgets library

+ +
+
RPMs
+

wxGTK, gettext +

+
+
Ubuntu packages
+

libwxgtk3.0-dev or libwxgtk3.2-dev +

+
+
File extension
+

cpp +

+
+
String syntax
+

"abc" +

+
+
gettext shorthand
+

_("abc") +

+
+
gettext/ngettext functions
+

wxLocale::GetString, wxGetTranslation +

+
+
textdomain
+

wxLocale::AddCatalog +

+
+
bindtextdomain
+

wxLocale::AddCatalogLookupPathPrefix +

+
+
setlocale
+

wxLocale::Init, wxSetLocale +

+
+
Prerequisite
+

#include <wx/intl.h> +

+
+
Use or emulate GNU gettext
+

emulate, see include/wx/intl.h and src/common/intl.cpp +

+
+
Extractor
+

xgettext +

+
+
Formatting with positions
+

wxString::Format supports positions if and only if the system has +wprintf(), vswprintf() functions and they support positions +according to POSIX. +

+
+
Portability
+

fully portable +

+
+
po-mode marking
+

yes +

+
+ + + + +

15.5.25 Tcl - Tk's scripting language

+ +
+
RPMs
+

tcl +

+
+
Ubuntu packages
+

tcl +

+
+
File extension
+

tcl +

+
+
String syntax
+

"abc" +

+
+
gettext shorthand
+

[_ "abc"] +

+
+
gettext/ngettext functions
+

::msgcat::mc +

+
+
textdomain
+

— +

+
+
bindtextdomain
+

—, use ::msgcat::mcload instead +

+
+
setlocale
+

automatic, uses LANG, but ignores LC_MESSAGES and LC_ALL +

+
+
Prerequisite
+

package require msgcat +
proc _ {s} {return [::msgcat::mc $s]} +

+
+
Use or emulate GNU gettext
+

—, uses a Tcl specific message catalog format +

+
+
Extractor
+

xgettext -k_ +

+
+
Formatting with positions
+

format "%2\$d %1\$d" +

+
+
Portability
+

fully portable +

+
+
po-mode marking
+

— +

+
+ +

Two examples are available in the ‘examples’ directory: +hello-tcl, hello-tcl-tk. +

+

Before marking strings as internationalizable, substitutions of variables +into the string need to be converted to format applications. For +example, "file $filename not found" becomes +[format "file %s not found" $filename]. +Only after this is done, can the strings be marked and extracted. +After marking, this example becomes +[format [_ "file %s not found"] $filename] or +[msgcat::mc "file %s not found" $filename]. Note that the +msgcat::mc function implicitly calls format when more than one +argument is given. +

+ + + +

15.5.26 Perl

+ +
+
RPMs
+

perl +

+
+
Ubuntu packages
+

perl, libintl-perl +

+
+
File extension
+

pl, PL, pm, perl, cgi +

+
+
String syntax
+
    +
  • "abc" + +
  • 'abc' + +
  • qq (abc) + +
  • q (abc) + +
  • qr /abc/ + +
  • qx (/bin/date) + +
  • /pattern match/ + +
  • ?pattern match? + +
  • s/substitution/operators/ + +
  • $tied_hash{"message"} + +
  • $tied_hash_reference->{"message"} + +
  • etc., issue the command ‘man perlsyn’ for details + +
+ +
+
gettext shorthand
+

__ (double underscore) +

+
+
gettext/ngettext functions
+

gettext, dgettext, dcgettext, ngettext, +dngettext, dcngettext, pgettext, dpgettext, +dcpgettext, npgettext, dnpgettext, +dcnpgettext +

+
+
textdomain
+

textdomain function +

+
+
bindtextdomain
+

bindtextdomain function +

+
+
bind_textdomain_codeset
+

bind_textdomain_codeset function +

+
+
setlocale
+

Use setlocale (LC_ALL, ""); +

+
+
Prerequisite
+

use POSIX; +
use Locale::TextDomain; (included in the package libintl-perl +which is available on the Comprehensive Perl Archive Network CPAN, +https://www.cpan.org/). +

+
+
Use or emulate GNU gettext
+

platform dependent: gettext_pp emulates, gettext_xs uses GNU gettext +

+
+
Extractor
+

xgettext -k__ -k\$__ -k%__ -k__x -k__n:1,2 -k__nx:1,2 -k__xn:1,2 +-kN__ -kN__n:1,2 -k__p:1c,2 -k__np:1c,2,3 -kN__p:1c,2 -kN__np:1c,2,3 +

+
+
Formatting with positions
+

Both kinds of format strings support formatting with positions. +
printf "%2\$d %1\$d", ... (requires Perl 5.8.0 or newer) +
__expand("[new] replaces [old]", old => $oldvalue, new => $newvalue) +

+
+
Portability
+

The libintl-perl package is platform independent but is not +part of the Perl core. The programmer is responsible for +providing a dummy implementation of the required functions if the +package is not installed on the target system. +

+
+
po-mode marking
+

— +

+
+
Documentation
+

Included in libintl-perl, available on CPAN +(https://www.cpan.org/). +

+
+
+ +

An example is available in the ‘examples’ directory: hello-perl. +

+ + +

The xgettext parser backend for Perl differs significantly from +the parser backends for other programming languages, just as Perl +itself differs significantly from other programming languages. The +Perl parser backend offers many more string marking facilities than +the other backends but it also has some Perl specific limitations, the +worst probably being its imperfectness. +

+ + + + +

15.5.26.1 General Problems Parsing Perl Code

+ +

It is often heard that only Perl can parse Perl. This is not true. +Perl cannot be parsed at all, it can only be executed. +Perl has various built-in ambiguities that can only be resolved at runtime. +

+

The following example may illustrate one common problem: +

+
 
print gettext "Hello World!";
+
+ +

Although this example looks like a bullet-proof case of a function +invocation, it is not: +

+
 
open gettext, ">testfile" or die;
+print gettext "Hello world!"
+
+ +

In this context, the string gettext looks more like a +file handle. But not necessarily: +

+
 
use Locale::Messages qw (:libintl_h);
+open gettext ">testfile" or die;
+print gettext "Hello world!";
+
+ +

Now, the file is probably syntactically incorrect, provided that the module +Locale::Messages found first in the Perl include path exports a +function gettext. But what if the module +Locale::Messages really looks like this? +

+
 
use vars qw (*gettext);
+
+1;
+
+ +

In this case, the string gettext will be interpreted as a file +handle again, and the above example will create a file ‘testfile’ +and write the string “Hello world!” into it. Even advanced +control flow analysis will not really help: +

+
 
if (0.5 < rand) {
+   eval "use Sane";
+} else {
+   eval "use InSane";
+}
+print gettext "Hello world!";
+
+ +

If the module Sane exports a function gettext that does +what we expect, and the module InSane opens a file for writing +and associates the handle gettext with this output +stream, we are clueless again about what will happen at runtime. It is +completely unpredictable. The truth is that Perl has so many ways to +fill its symbol table at runtime that it is impossible to interpret a +particular piece of code without executing it. +

+

Of course, xgettext will not execute your Perl sources while +scanning for translatable strings, but rather use heuristics in order +to guess what you meant. +

+

Another problem is the ambiguity of the slash and the question mark. +Their interpretation depends on the context: +

+
 
# A pattern match.
+print "OK\n" if /foobar/;
+
+# A division.
+print 1 / 2;
+
+# Another pattern match.
+print "OK\n" if ?foobar?;
+
+# Conditional.
+print $x ? "foo" : "bar";
+
+ +

The slash may either act as the division operator or introduce a +pattern match, whereas the question mark may act as the ternary +conditional operator or as a pattern match, too. Other programming +languages like awk present similar problems, but the consequences of a +misinterpretation are particularly nasty with Perl sources. In awk +for instance, a statement can never exceed one line and the parser +can recover from a parsing error at the next newline and interpret +the rest of the input stream correctly. Perl is different, as a +pattern match is terminated by the next appearance of the delimiter +(the slash or the question mark) in the input stream, regardless of +the semantic context. If a slash is really a division sign but +mis-interpreted as a pattern match, the rest of the input file is most +probably parsed incorrectly. +

+

There are certain cases, where the ambiguity cannot be resolved at all: +

+
 
$x = wantarray ? 1 : 0;
+
+ +

The Perl built-in function wantarray does not accept any arguments. +The Perl parser therefore knows that the question mark does not start +a regular expression but is the ternary conditional operator. +

+
 
sub wantarrays {}
+$x = wantarrays ? 1 : 0;
+
+ +

Now the situation is different. The function wantarrays takes +a variable number of arguments (like any non-prototyped Perl function). +The question mark is now the delimiter of a pattern match, and hence +the piece of code does not compile. +

+
 
sub wantarrays() {}
+$x = wantarrays ? 1 : 0;
+
+ +

Now the function is prototyped, Perl knows that it does not accept any +arguments, and the question mark is therefore interpreted as the +ternaray operator again. But that unfortunately outsmarts xgettext. +

+

The Perl parser in xgettext cannot know whether a function has +a prototype and what that prototype would look like. It therefore makes +an educated guess. If a function is known to be a Perl built-in and +this function does not accept any arguments, a following question mark +or slash is treated as an operator, otherwise as the delimiter of a +following regular expression. The Perl built-ins that do not accept +arguments are wantarray, fork, time, times, +getlogin, getppid, getpwent, getgrent, +gethostent, getnetent, getprotoent, getservent, +setpwent, setgrent, endpwent, endgrent, +endhostent, endnetent, endprotoent, and +endservent. +

+

If you find that xgettext fails to extract strings from +portions of your sources, you should therefore look out for slashes +and/or question marks preceding these sections. You may have come +across a bug in xgettext's Perl parser (and of course you +should report that bug). In the meantime you should consider to +reformulate your code in a manner less challenging to xgettext. +

+

In particular, if the parser is too dumb to see that a function +does not accept arguments, use parentheses: +

+
 
$x = somefunc() ? 1 : 0;
+$y = (somefunc) ? 1 : 0;
+
+ +

In fact the Perl parser itself has similar problems and warns you +about such constructs. +

+ + + +

15.5.26.2 Which keywords will xgettext look for?

+ +

Unless you instruct xgettext otherwise by invoking it with one +of the options --keyword or -k, it will recognize the +following keywords in your Perl sources: +

+
    +
  • gettext + +
  • dgettext:2 + +

    The second argument will be extracted. +

    +
  • dcgettext:2 + +

    The second argument will be extracted. +

    +
  • ngettext:1,2 + +

    The first (singular) and the second (plural) argument will be +extracted. +

    +
  • dngettext:2,3 + +

    The second (singular) and the third (plural) argument will be +extracted. +

    +
  • dcngettext:2,3 + +

    The second (singular) and the third (plural) argument will be +extracted. +

    +
  • pgettext:1c,2 + +

    The first (message context) and the second argument will be extracted. +

    +
  • dpgettext:2c,3 + +

    The second (message context) and the third argument will be extracted. +

    +
  • dcpgettext:2c,3 + +

    The second (message context) and the third argument will be extracted. +

    +
  • npgettext:1c,2,3 + +

    The first (message context), second (singular), and third (plural) +argument will be extracted. +

    +
  • dnpgettext:2c,3,4 + +

    The second (message context), third (singular), and fourth (plural) +argument will be extracted. +

    +
  • dcnpgettext:2c,3,4 + +

    The second (message context), third (singular), and fourth (plural) +argument will be extracted. +

    +
  • gettext_noop + +
  • %gettext + +

    The keys of lookups into the hash %gettext will be extracted. +

    +
  • $gettext + +

    The keys of lookups into the hash reference $gettext will be extracted. +

    +
+ + + + +

15.5.26.3 How to Extract Hash Keys

+ +

Translating messages at runtime is normally performed by looking up the +original string in the translation database and returning the +translated version. The “natural” Perl implementation is a hash +lookup, and, of course, xgettext supports such practice. +

+
 
print __"Hello world!";
+print $__{"Hello world!"};
+print $__->{"Hello world!"};
+print $$__{"Hello world!"};
+
+ + +

The above four lines all do the same thing. The Perl module +Locale::TextDomain exports by default a hash %__ that +is tied to the function __(). It also exports a reference +$__ to %__. +

+

If an argument to the xgettext option --keyword, +resp. -k starts with a percent sign, the rest of the keyword is +interpreted as the name of a hash. If it starts with a dollar +sign, the rest of the keyword is interpreted as a reference to a +hash. +

+

Note that you can omit the quotation marks (single or double) around +the hash key (almost) whenever Perl itself allows it: +

+
 
print $gettext{Error};
+
+ +

The exact rule is: You can omit the surrounding quotes, when the hash +key is a valid C (!) identifier, i.e. when it starts with an +underscore or an ASCII letter and is followed by an arbitrary number +of underscores, ASCII letters or digits. Other Unicode characters +are not allowed, regardless of the use utf8 pragma. +

+ + + +

15.5.26.4 What are Strings And Quote-like Expressions?

+ +

Perl offers a plethora of different string constructs. Those that can +be used either as arguments to functions or inside braces for hash +lookups are generally supported by xgettext. +

+
    +
  • double-quoted strings +
    +
     
    print gettext "Hello World!";
+
    + +
  • single-quoted strings +
    +
     
    print gettext 'Hello World!';
+
    + +
  • the operator qq +
    +
     
    print gettext qq |Hello World!|;
+print gettext qq <E-mail: <guido\@imperia.net>>;
+
    + +

    The operator qq is fully supported. You can use arbitrary +delimiters, including the four bracketing delimiters (round, angle, +square, curly) that nest. +

    +
  • the operator q +
    +
     
    print gettext q |Hello World!|;
+print gettext q <E-mail: <guido@imperia.net>>;
+
    + +

    The operator q is fully supported. You can use arbitrary +delimiters, including the four bracketing delimiters (round, angle, +square, curly) that nest. +

    +
  • the operator qx +
    +
     
    print gettext qx ;LANGUAGE=C /bin/date;
+print gettext qx [/usr/bin/ls | grep '^[A-Z]*'];
+
    + +

    The operator qx is fully supported. You can use arbitrary +delimiters, including the four bracketing delimiters (round, angle, +square, curly) that nest. +

    +

    The example is actually a useless use of gettext. It will +invoke the gettext function on the output of the command +specified with the qx operator. The feature was included +in order to make the interface consistent (the parser will extract +all strings and quote-like expressions). +

    +
  • here documents +
    +
     
    print gettext <<'EOF';
+program not found in $PATH
+EOF
+
+print ngettext <<EOF, <<"EOF";
+one file deleted
+EOF
+several files deleted
+EOF
+
    + +

    Here-documents are recognized. If the delimiter is enclosed in single +quotes, the string is not interpolated. If it is enclosed in double +quotes or has no quotes at all, the string is interpolated. +

    +

    Delimiters that start with a digit are not supported! +

    +
+ + + + +

15.5.26.5 Unsupported Uses Of String Interpolation

+ +

Perl is capable of interpolating variables into strings. This offers +some nice features in localized programs but can also lead to +problems. +

+

A common error is a construct like the following: +

+
 
print gettext "This is the program $0!\n";
+
+ +

Perl will interpolate at runtime the value of the variable $0 +into the argument of the gettext() function. Hence, this +argument is not a string constant but a variable argument ($0 +is a global variable that holds the name of the Perl script being +executed). The interpolation is performed by Perl before the string +argument is passed to gettext() and will therefore depend on +the name of the script which can only be determined at runtime. +Consequently, it is almost impossible that a translation can be looked +up at runtime (except if, by accident, the interpolated string is found +in the message catalog). +

+

The xgettext program will therefore produce a warning +if it encounters a variable inside of a string to be extracted, +and not extract that string. +In general, this will happen for all kinds of string interpolations that +cannot be safely performed at compile time. If you absolutely know +what you are doing, you can always circumvent this behavior: +

+
 
my $know_what_i_am_doing = "This is program $0!\n";
+print gettext $know_what_i_am_doing;
+
+ +

Since the parser only recognizes strings and quote-like expressions, +but not variables or other terms, the above construct will be +accepted. You will have to find another way, however, to let your +original string make it into your message catalog. +

+

If invoked with the option --extract-all, resp. -a, +variable interpolation will be accepted. Rationale: You will +generally use this option in order to prepare your sources for +internationalization. +

+

Please see the manual page ‘man perlop’ for details of strings and +quote-like expressions that are subject to interpolation and those +that are not. Safe interpolations (that will not lead to a warning) +are: +

+
    +
  • the escape sequences \t (tab, HT, TAB), \n +(newline, NL), \r (return, CR), \f (form feed, FF), +\b (backspace, BS), \a (alarm, bell, BEL), and \e +(escape, ESC). + +
  • octal chars, like \033 +
    +Note that octal escapes in the range of 400-777 are translated into a +UTF-8 representation, regardless of the presence of the use utf8 pragma. + +
  • hex chars, like \x1b + +
  • wide hex chars, like \x{263a} +
    +Note that this escape is translated into a UTF-8 representation, +regardless of the presence of the use utf8 pragma. + +
  • control chars, like \c[ (CTRL-[) + +
  • named Unicode chars, like \N{LATIN CAPITAL LETTER C WITH CEDILLA} +
    +Note that this escape is translated into a UTF-8 representation, +regardless of the presence of the use utf8 pragma. +
+ +

The following escapes are considered partially safe: +

+
    +
  • \l lowercase next char + +
  • \u uppercase next char + +
  • \L lowercase till \E + +
  • \U uppercase till \E + +
  • \E end case modification + +
  • \Q quote non-word characters till \E + +
+ +

These escapes are only considered safe if the string consists of +ASCII characters only. Translation of characters outside the range +defined by ASCII is locale-dependent and can actually only be performed +at runtime; xgettext doesn't do these locale-dependent translations +at extraction time. +

+

Except for the modifier \Q, these translations, albeit valid, +are generally useless and only obfuscate your sources. If a +translation can be safely performed at compile time you can just as +well write what you mean. +

+ + + +

15.5.26.6 Valid Uses Of String Interpolation

+ +

Perl is often used to generate sources for other programming languages +or arbitrary file formats. Web applications that output HTML code +make a prominent example for such usage. +

+

You will often come across situations where you want to intersperse +code written in the target (programming) language with translatable +messages, like in the following HTML example: +

+
 
print gettext <<EOF;
+<h1>My Homepage</h1>
+<script language="JavaScript"><!--
+for (i = 0; i < 100; ++i) {
+    alert ("Thank you so much for visiting my homepage!");
+}
+//--></script>
+EOF
+
+ +

The parser will extract the entire here document, and it will appear +entirely in the resulting PO file, including the JavaScript snippet +embedded in the HTML code. If you exaggerate with constructs like +the above, you will run the risk that the translators of your package +will look out for a less challenging project. You should consider an +alternative expression here: +

+
 
print <<EOF;
+<h1>$gettext{"My Homepage"}</h1>
+<script language="JavaScript"><!--
+for (i = 0; i < 100; ++i) {
+    alert ("$gettext{'Thank you so much for visiting my homepage!'}");
+}
+//--></script>
+EOF
+
+ +

Only the translatable portions of the code will be extracted here, and +the resulting PO file will begrudgingly improve in terms of readability. +

+

You can interpolate hash lookups in all strings or quote-like +expressions that are subject to interpolation (see the manual page +‘man perlop’ for details). Double interpolation is unsupported, however: +

+
 
# TRANSLATORS: Replace "the earth" with the name of your planet.
+print gettext qq{Welcome to $gettext->{"the earth"}};
+
+ +

The qq-quoted string is recognized as an argument to xgettext in +the first place, and checked for unsupported variable interpolation. The +dollar sign of hash-dereferencing will therefore terminate the parser +with an “unsupported interpolation” warning. +

+

It is valid to interpolate hash lookups in regular expressions: +

+
 
if ($var =~ /$gettext{"the earth"}/) {
+   print gettext "Match!\n";
+}
+s/$gettext{"U. S. A."}/$gettext{"U. S. A."} $gettext{"(dial +0)"}/g;
+
+ + + + +

15.5.26.7 When To Use Parentheses

+ +

In Perl, parentheses around function arguments are mostly optional. +xgettext will always assume that all +recognized keywords (except for hashes and hash references) are names +of properly prototyped functions, and will (hopefully) only require +parentheses where Perl itself requires them. All constructs in the +following example are therefore ok to use: +

+
 
print gettext ("Hello World!\n");
+print gettext "Hello World!\n";
+print dgettext ($package => "Hello World!\n");
+print dgettext $package, "Hello World!\n";
+
+# The "fat comma" => turns the left-hand side argument into a
+# single-quoted string!
+print dgettext smellovision => "Hello World!\n";
+
+# The following assignment only works with prototyped functions.
+# Otherwise, the functions will act as "greedy" list operators and
+# eat up all following arguments.
+my $anonymous_hash = {
+   planet => gettext "earth",
+   cakes => ngettext "one cake", "several cakes", $n,
+   still => $works,
+};
+# The same without fat comma:
+my $other_hash = {
+   'planet', gettext "earth",
+   'cakes', ngettext "one cake", "several cakes", $n,
+   'still', $works,
+};
+
+# Parentheses are only significant for the first argument.
+print dngettext 'package', ("one cake", "several cakes", $n), $discarded;
+
+ + + + +

15.5.26.8 How To Grok with Long Lines

+ +

The necessity of long messages can often lead to a cumbersome or +unreadable coding style. Perl has several options that may prevent +you from writing unreadable code, and +xgettext does its best to do likewise. This is where the dot +operator (the string concatenation operator) may come in handy: +

+
 
print gettext ("This is a very long"
+               . " message that is still"
+               . " readable, because"
+               . " it is split into"
+               . " multiple lines.\n");
+
+ +

Perl is smart enough to concatenate these constant string fragments +into one long string at compile time, and so is +xgettext. You will only find one long message in the resulting +POT file. +

+

Note that the future Perl 6 will probably use the underscore +(‘_’) as the string concatenation operator, and the dot +(‘.’) for dereferencing. This new syntax is not yet supported by +xgettext. +

+

If embedded newline characters are not an issue, or even desired, you +may also insert newline characters inside quoted strings wherever you +feel like it: +

+
 
print gettext ("<em>In HTML output
+embedded newlines are generally no
+problem, since adjacent whitespace
+is always rendered into a single
+space character.</em>");
+
+ +

You may also consider to use here documents: +

+
 
print gettext <<EOF;
+<em>In HTML output
+embedded newlines are generally no
+problem, since adjacent whitespace
+is always rendered into a single
+space character.</em>
+EOF
+
+ +

Please do not forget that the line breaks are real, i.e. they +translate into newline characters that will consequently show up in +the resulting POT file. +

+ + + +

15.5.26.9 Bugs, Pitfalls, And Things That Do Not Work

+ +

The foregoing sections should have proven that +xgettext is quite smart in extracting translatable strings from +Perl sources. Yet, some more or less exotic constructs that could be +expected to work, actually do not work. +

+

One of the more relevant limitations can be found in the +implementation of variable interpolation inside quoted strings. Only +simple hash lookups can be used there: +

+
 
print <<EOF;
+$gettext{"The dot operator"
+          . " does not work"
+          . "here!"}
+Likewise, you cannot @{[ gettext ("interpolate function calls") ]}
+inside quoted strings or quote-like expressions.
+EOF
+
+ +

This is valid Perl code and will actually trigger invocations of the +gettext function at runtime. Yet, the Perl parser in +xgettext will fail to recognize the strings. A less obvious +example can be found in the interpolation of regular expressions: +

+
 
s/<!--START_OF_WEEK-->/gettext ("Sunday")/e;
+
+ +

The modifier e will cause the substitution to be interpreted as +an evaluable statement. Consequently, at runtime the function +gettext() is called, but again, the parser fails to extract the +string “Sunday”. Use a temporary variable as a simple workaround if +you really happen to need this feature: +

+
 
my $sunday = gettext "Sunday";
+s/<!--START_OF_WEEK-->/$sunday/;
+
+ +

Hash slices would also be handy but are not recognized: +

+
 
my @weekdays = @gettext{'Sunday', 'Monday', 'Tuesday', 'Wednesday',
+                        'Thursday', 'Friday', 'Saturday'};
+# Or even:
+@weekdays = @gettext{qw (Sunday Monday Tuesday Wednesday Thursday
+                         Friday Saturday) };
+
+ +

This is perfectly valid usage of the tied hash %gettext but the +strings are not recognized and therefore will not be extracted. +

+

Another caveat of the current version is its rudimentary support for +non-ASCII characters in identifiers. You may encounter serious +problems if you use identifiers with characters outside the range of +'A'-'Z', 'a'-'z', '0'-'9' and the underscore '_'. +

+

Maybe some of these missing features will be implemented in future +versions, but since you can always make do without them at minimal effort, +these todos have very low priority. +

+

A nasty problem are brace format strings that already contain braces +as part of the normal text, for example the usage strings typically +encountered in programs: +

+
 
die "usage: $0 {OPTIONS} FILENAME...\n";
+
+ +

If you want to internationalize this code with Perl brace format strings, +you will run into a problem: +

+
 
die __x ("usage: {program} {OPTIONS} FILENAME...\n", program => $0);
+
+ +

Whereas ‘{program}’ is a placeholder, ‘{OPTIONS}’ +is not and should probably be translated. Yet, there is no way to teach +the Perl parser in xgettext to recognize the first one, and leave +the other one alone. +

+

There are two possible work-arounds for this problem. If you are +sure that your program will run under Perl 5.8.0 or newer (these +Perl versions handle positional parameters in printf()) or +if you are sure that the translator will not have to reorder the arguments +in her translation – for example if you have only one brace placeholder +in your string, or if it describes a syntax, like in this one –, you can +mark the string as no-perl-brace-format and use printf(): +

+
 
# xgettext: no-perl-brace-format
+die sprintf ("usage: %s {OPTIONS} FILENAME...\n", $0);
+
+ +

If you want to use the more portable Perl brace format, you will have to do +put placeholders in place of the literal braces: +

+
 
die __x ("usage: {program} {[}OPTIONS{]} FILENAME...\n",
+         program => $0, '[' => '{', ']' => '}');
+
+ +

Perl brace format strings know no escaping mechanism. No matter how this +escaping mechanism looked like, it would either give the programmer a +hard time, make translating Perl brace format strings heavy-going, or +result in a performance penalty at runtime, when the format directives +get executed. Most of the time you will happily get along with +printf() for this special case. +

+ + + +

15.5.27 PHP Hypertext Preprocessor

+ +
+
RPMs
+

php +

+
+
Ubuntu packages
+

php +

+
+
File extension
+

php, php3, php4 +

+
+
String syntax
+

"abc", 'abc', +<<<EOT, <<<"EOT", <<<'EOT' +

+
+
gettext shorthand
+

_("abc") +

+
+
gettext/ngettext functions
+

gettext, dgettext, dcgettext, +ngettext, dngettext, dcngettext +

+
+
textdomain
+

textdomain function +

+
+
bindtextdomain
+

bindtextdomain function +

+
+
setlocale
+

Programmer must call setlocale (LC_ALL, "") +

+
+
Prerequisite
+

— +

+
+
Use or emulate GNU gettext
+

use +

+
+
Extractor
+

xgettext +

+
+
Formatting with positions
+

printf "%2\$d %1\$d" +

+
+
Portability
+

On platforms without gettext, the functions are not available. +

+
+
po-mode marking
+

— +

+
+ +

An example is available in the ‘examples’ directory: hello-php. +

+ + + +

15.5.28 Pike

+ +
+
RPMs
+

roxen +

+
+
Ubuntu packages
+

pike8.0 or pike7.8 +

+
+
File extension
+

pike +

+
+
String syntax
+

"abc" +

+
+
gettext shorthand
+

— +

+
+
gettext/ngettext functions
+

gettext, dgettext, dcgettext +

+
+
textdomain
+

textdomain function +

+
+
bindtextdomain
+

bindtextdomain function +

+
+
setlocale
+

setlocale function +

+
+
Prerequisite
+

import Locale.Gettext; +

+
+
Use or emulate GNU gettext
+

use +

+
+
Extractor
+

— +

+
+
Formatting with positions
+

— +

+
+
Portability
+

On platforms without gettext, the functions are not available. +

+
+
po-mode marking
+

— +

+
+ + + + +

15.5.29 GNU Compiler Collection sources

+ +
+
RPMs
+

gcc +

+
+
Ubuntu packages
+

gcc +

+
+
File extension
+

c, h. +

+
+
String syntax
+

"abc" +

+
+
gettext shorthand
+

_("abc") +

+
+
gettext/ngettext functions
+

gettext, dgettext, dcgettext, ngettext, +dngettext, dcngettext +

+
+
textdomain
+

textdomain function +

+
+
bindtextdomain
+

bindtextdomain function +

+
+
setlocale
+

Programmer must call setlocale (LC_ALL, "") +

+
+
Prerequisite
+

#include "intl.h" +

+
+
Use or emulate GNU gettext
+

Use +

+
+
Extractor
+

xgettext -k_ +

+
+
Formatting with positions
+

— +

+
+
Portability
+

Uses autoconf macros +

+
+
po-mode marking
+

yes +

+
+ + + + +

15.5.30 YCP - YaST2 scripting language

+ +
+
RPMs
+

libycp, libycp-devel, yast2-core, yast2-core-devel +

+
+
Ubuntu packages
+

— +

+
+
File extension
+

ycp +

+
+
String syntax
+

"abc" +

+
+
gettext shorthand
+

_("abc") +

+
+
gettext/ngettext functions
+

_() with 1 or 3 arguments +

+
+
textdomain
+

textdomain statement +

+
+
bindtextdomain
+

— +

+
+
setlocale
+

— +

+
+
Prerequisite
+

— +

+
+
Use or emulate GNU gettext
+

use +

+
+
Extractor
+

xgettext +

+
+
Formatting with positions
+

sformat "%2 %1" +

+
+
Portability
+

fully portable +

+
+
po-mode marking
+

— +

+
+ +

An example is available in the ‘examples’ directory: hello-ycp. +

+ + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_16.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_16.html new file mode 100644 index 0000000000000000000000000000000000000000..01b3d3bbaa9526db68bf4fd4fea5a3c3f14d1050 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_16.html @@ -0,0 +1,656 @@ + + + + + +GNU gettext utilities: 16. Other Data Formats + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

16. Other Data Formats

+ +

While the GNU gettext tools deal mainly with POT and PO files, they can +also manipulate a couple of other data formats. +

+ + + + +

16.1 Internationalizable Data Formats

+ +

Here is a list of other data formats which can be internationalized +using GNU gettext. +

+ + + + +

16.1.1 POT - Portable Object Template

+ +
+
RPMs
+

gettext +

+
+
Ubuntu packages
+

gettext +

+
+
File extension
+

pot, po +

+
+
Extractor
+

xgettext +

+
+ + + + +

16.1.2 Resource String Table

+ +

RST is the format of resource string table files of the Free Pascal compiler +versions older than 3.0.0. RSJ is the new format of resource string table +files, created by the Free Pascal compiler version 3.0.0 or newer. +

+
+
RPMs
+

fpk +

+
+
Ubuntu packages
+

fp-compiler +

+
+
File extension
+

rst, rsj +

+
+
Extractor
+

xgettext, rstconv +

+
+ + + + +

16.1.3 Glade - GNOME user interface description

+ +
+
RPMs
+

glade, libglade, glade2, libglade2, intltool +

+
+
Ubuntu packages
+

glade, libglade2-dev, intltool +

+
+
File extension
+

glade, glade2, ui +

+
+
Extractor
+

xgettext, libglade-xgettext, xml-i18n-extract, intltool-extract +

+
+ + + + +

16.1.4 GSettings - GNOME user configuration schema

+ +
+
RPMs
+

glib2 +

+
+
Ubuntu packages
+

libglib2.0-dev +

+
+
File extension
+

gschema.xml +

+
+
Extractor
+

xgettext, intltool-extract +

+
+ + + + +

16.1.5 AppData - freedesktop.org application description

+ +

This file format is specified in +https://www.freedesktop.org/software/appstream/docs/. +

+
+
RPMs
+

appdata-tools, appstream, libappstream-glib, libappstream-glib-builder +

+
+
Ubuntu packages
+

appdata-tools, appstream, libappstream-glib-dev +

+
+
File extension
+

appdata.xml, metainfo.xml +

+
+
Extractor
+

xgettext, intltool-extract, itstool +

+
+ + + + +

16.1.6 Preparing Rules for XML Internationalization

+ + + + + + +

16.1.6.1 Specifying ITS Rules

+ +

Marking translatable strings in an XML file is done through a separate +"rule" file, making use of the Internationalization Tag Set standard +(ITS, https://www.w3.org/TR/its20/). The currently supported ITS +data categories are: ‘Translate’, ‘Localization Note’, +‘Elements Within Text’, and ‘Preserve Space’. In addition to +them, xgettext also recognizes the following extended data +categories: +

+
+
‘Context’
+
+

This data category associates msgctxt to the extracted text. In +the global rule, the contextRule element contains the following: +

+
    +
  • +A required selector attribute. It contains an absolute selector +that selects the nodes to which this rule applies. + +
  • +A required contextPointer attribute that contains a relative +selector pointing to a node that holds the msgctxt value. + +
  • +An optional textPointer attribute that contains a relative +selector pointing to a node that holds the msgid value. +
+ +
+
‘Extended Preserve Space’
+
+

This data category extends the standard ‘Preserve Space’ data +category with the additional values ‘trim’ and ‘paragraph’. +‘trim’ means to remove the leading and trailing whitespaces of the +content, but not to normalize whitespaces in the middle. +‘paragraph’ means to normalize the content but keep the paragraph +boundaries. In the global +rule, the preserveSpaceRule element contains the following: +

+
    +
  • +A required selector attribute. It contains an absolute selector +that selects the nodes to which this rule applies. + +
  • +A required space attribute with the value default, +preserve, trim, or paragraph. +
+ +
+
‘Escape Special Characters’
+
+

This data category indicates whether the special XML characters +(<, >, &, ") are escaped with entity +references. In the global rule, the escapeRule element contains +the following: +

+
    +
  • +A required selector attribute. It contains an absolute selector +that selects the nodes to which this rule applies. + +
  • +A required escape attribute with the value yes or no. + +
  • +An optional unescape-if attribute with the value +xml, xhtml, html, or no. +
+ +

The default values, escape="no" and unescape-if="no", +should be good for most XML file types. +A rule with escape="no", +that was necessary with GNU gettext versions before 0.23, +is now redundant. +

+

The unescape-if attribute is useful for XML file types +which present messages with embedded XML elements to the translator. +Such file types are for example DocBook or XHTML. +If unescape-if="xml" is specified and the translation +of a message looks like valid XML, the usual escaping of <, +>, and character references is omitted. +The resulting XML document then is likely what the translator intended. +However, if the translator did not merely copy the XML markup from the +message to the translation, but added or removed markup, +the resulting XML document may be invalid. +It is therefore useful if, after invoking msgfmt, you check +the resulting XML document against the appropriate XML schema or DTD. +

+

Similarly, if unescape-if="xhtml" is specified and the translation +looks like valid XHTML, the usual escaping is omitted. +And likewise for unescape-if="html". +

+
+
+ +

All those extended data categories can only be expressed with global +rules, and the rule elements have to have the +https://www.gnu.org/s/gettext/ns/its/extensions/1.0 namespace. +

+

Given the following XML document in a file ‘messages.xml’: +

+
 
<?xml version="1.0"?>
+<messages>
+  <message>
+    <p>A translatable string</p>
+  </message>
+  <message>
+    <p translatable="no">A non-translatable string</p>
+  </message>
+</messages>
+
+ +

To extract the first text content ("A translatable string"), but not the +second ("A non-translatable string"), the following ITS rules can be used: +

+
 
<?xml version="1.0"?>
+<its:rules xmlns:its="http://www.w3.org/2005/11/its" version="1.0">
+  <its:translateRule selector="/messages" translate="no"/>
+  <its:translateRule selector="//message/p" translate="yes"/>
+
+  <!-- If 'p' has an attribute 'translatable' with the value 'no', then
+       the content is not translatable.  -->
+  <its:translateRule selector="//message/p[@translatable = 'no']"
+    translate="no"/>
+</its:rules>
+
+ +

ITS rules files must have the ‘.its’ file extension and obey +the XML schema version 1.0 encoded by its.xsd10 or +the XML schema version 1.1 encoded by its.xsd11 +and its auxiliary schema its-extensions.xsd. +

+ + + +

16.1.6.2 Specifying where to find the ITS Rules

+ +

‘xgettext’ needs another file called "locating rules" to associate +an ITS rule with an XML file. If the above ITS file is saved as +‘messages.its’, the locating rules file would look like: +

+
 
<?xml version="1.0"?>
+<locatingRules>
+  <locatingRule name="Messages" pattern="*.xml">
+    <documentRule localName="messages" target="messages.its"/>
+  </locatingRule>
+  <locatingRule name="Messages" pattern="*.msg" target="messages.its"/>
+</locatingRules>
+
+ +

The locatingRule element must have a pattern attribute, +which denotes either a literal file name or a wildcard pattern of the +XML file(7). The locatingRule element can have child +documentRule element, which adds checks on the content of the XML +file. +

+

The first rule matches any file with the ‘.xml’ file extension, but +it only applies to XML files whose root element is ‘<messages>’. +

+

The second rule indicates that the same ITS rules file are also +applicable to any file with the ‘.msg’ file extension. The +optional name attribute of locatingRule allows to choose +rules by name, typically with xgettext's -L option. +

+

The associated ITS rules file is indicated by the target attribute +of locatingRule or documentRule. If it is specified in a +documentRule element, the parent locatingRule shouldn't +have the target attribute. +

+

Locating rules files must have the ‘.loc’ file extension and obey +the XML schema version 1.0 encoded by locating-rules.xsd10 or +the XML schema version 1.1 encoded by locating-rules.xsd11. +Both ITS rules files and locating rules files must be installed in the +‘$prefix/share/gettext/its’ directory. Once those files are +properly installed, xgettext can extract translatable strings +from the matching XML files. +

+ + +

16.1.6.3 Two Use-cases of Translated Strings in XML

+ +

After strings have been extracted from an XML file to a POT file +through xgettext +and the translator has produced a PO file with translations, +it can be used in two ways: +

+
    +
  • +The PO file (or the MO file generated from it) can be directly consumed +by a program. + +
  • +Or the translated strings can be merged back to the original XML document. +To do this use the msgfmt program with the option --xml. +See section Invoking the msgfmt Program, for more details about how one calls +the ‘msgfmt’ program. + +

    During this merge from a PO file into an XML file, it may happen that +more escaping of special characters for XML is needed +than what msgfmt does by default. +In this case, you can enforce more escaping +either throuch an <escapeRule> ITS rule, +or through an attribute gt:escape="yes" on the particular XML element. +

    +
+ + + + + +

16.2 Localized Data Formats

+ +

Here is a list of file formats that contain localized data and that the +GNU gettext tools can manipulate. +

+ + + + +

16.2.1 Editable Message Catalogs

+ +

These file formats can be used with all of the msg* tools and with +the xgettext program. +

+

If you just want to convert among these formats, you can use the +msgcat program (with the appropriate option) or the xgettext +program. +

+ + + + +

16.2.1.1 PO - Portable Object

+ +
+
File extension
+

po +

+
+ + + + +

16.2.1.2 Java .properties

+ +
+
File extension
+

properties +

+
+ + + + +

16.2.1.3 NeXTstep/GNUstep .strings

+ +
+
File extension
+

strings +

+
+ + + + +

16.2.2 Compiled Message Catalogs

+ +

These file formats can be created through msgfmt and converted back +to PO format through msgunfmt. +

+ + + + +

16.2.2.1 MO - Machine Object

+ +
+
File extension
+

mo +

+
+ +

See section The Format of GNU MO Files for details. +

+ + + +

16.2.2.2 Java ResourceBundle

+ +
+
File extension
+

class +

+
+ +

For more information, see the section Java and the examples +hello-java, hello-java-awt, hello-java-swing. +

+ + + +

16.2.2.3 C# Satellite Assembly

+ +
+
File extension
+

dll +

+
+ +

For more information, see the section C#. +

+ + + +

16.2.2.4 C# Resource

+ +
+
File extension
+

resources +

+
+ +

For more information, see the section C#. +

+ + + +

16.2.2.5 Tcl message catalog

+ +
+
File extension
+

msg +

+
+ +

For more information, see the section Tcl - Tk's scripting language and the examples +hello-tcl, hello-tcl-tk. +

+ + + +

16.2.2.6 Qt message catalog

+ +
+
File extension
+

qm +

+
+ +

For more information, see the examples hello-c++-qt and +hello-c++-kde. +

+ + + +

16.2.3 Desktop Entry files

+ +

The programmer produces a desktop entry file template with only the +English strings. These strings get included in the POT file, by way of +xgettext (usually by listing the template in po/POTFILES.in). +The translators produce PO files, one for each language. Finally, an +msgfmt --desktop invocation collects all the translations in the +desktop entry file. +

+

For more information, see the example hello-c-gnome3. +

+ + + + +

16.2.3.1 How to handle icons in Desktop Entry files

+ +

Icons are generally locale dependent, for the following reasons: +

+
    +
  • +Icons may contain signs that are considered rude in some cultures. For +example, the high-five sign, in some cultures, is perceived as an +unfriendly “stop” sign. +
  • +Icons may contain metaphors that are culture specific. For example, a +mailbox in the U.S. looks different than mailboxes all around the world. +
  • +Icons may need to be mirrored for right-to-left locales. +
  • +Icons may contain text strings (a bad practice, but anyway). +
+ +

However, icons are not covered by GNU gettext localization, because +

    +
  • +Icons cannot be easily embedded in PO files, +
  • +The need to localize an icon is rare, and the ability to do so in a PO +file would introduce translator mistakes. +
+ +

Desktop Entry files may contain an ‘Icon’ property, and this +property is localizable. If a translator wishes to localize an icon, +she should do so by bypassing the normal workflow with PO files: +

    +
  1. +The translator contacts the package developers directly, sending them +the icon appropriate for her locale, with a request to change the +template file. +
  2. +The package developers add the icon file to their repository, and a +line +
     
    Icon[locale]=icon_file_name
+
    +

    to the template file. +

+

This line remains in place when this template file is merged with the +translators' PO files, through msgfmt. +

+ + + +

16.2.4 XML files

+ +

See the section Preparing Rules for XML Internationalization and +Invoking the msgfmt Program, subsection “XML mode operations”. +

+ + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_17.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_17.html new file mode 100644 index 0000000000000000000000000000000000000000..c434f4f2f2840635e890eb6a1d76ff1f78dcafb0 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_17.html @@ -0,0 +1,1386 @@ + + + + + +GNU gettext utilities: 17. Concluding Remarks + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

17. Concluding Remarks

+ +

We would like to conclude this GNU gettext manual by presenting +an history of the Translation Project so far. We finally give +a few pointers for those who want to do further research or readings +about Native Language Support matters. +

+ + + + +

17.1 History of GNU gettext

+ +

Internationalization concerns and algorithms have been informally +and casually discussed for years in GNU, sometimes around GNU +libc, maybe around the incoming Hurd, or otherwise +(nobody clearly remembers). And even then, when the work started for +real, this was somewhat independently of these previous discussions. +

+

This all began in July 1994, when Patrick D'Cruze had the idea and +initiative of internationalizing version 3.9.2 of GNU fileutils. +He then asked Jim Meyering, the maintainer, how to get those changes +folded into an official release. That first draft was full of +#ifdefs and somewhat disconcerting, and Jim wanted to find +nicer ways. Patrick and Jim shared some tries and experimentations +in this area. Then, feeling that this might eventually have a deeper +impact on GNU, Jim wanted to know what standards were, and contacted +Richard Stallman, who very quickly and verbally described an overall +design for what was meant to become glocale, at that time. +

+

Jim implemented glocale and got a lot of exhausting feedback +from Patrick and Richard, of course, but also from Mitchum DSouza +(who wrote a catgets-like package), Roland McGrath, maybe David +MacKenzie, François Pinard, and Paul Eggert, all pushing and +pulling in various directions, not always compatible, to the extent +that after a couple of test releases, glocale was torn apart. +In particular, Paul Eggert – always keeping an eye on developments +in Solaris – advocated the use of the gettext API over +glocale's catgets-based API. +

+

While Jim took some distance and time and became dad for a second +time, Roland wanted to get GNU libc internationalized, and +got Ulrich Drepper involved in that project. Instead of starting +from glocale, Ulrich rewrote something from scratch, but +more conforming to the set of guidelines who emerged out of the +glocale effort. Then, Ulrich got people from the previous +forum to involve themselves into this new project, and the switch +from glocale to what was first named msgutils, renamed +nlsutils, and later gettext, became officially accepted +by Richard in May 1995 or so. +

+

Let's summarize by saying that Ulrich Drepper wrote GNU gettext +in April 1995. The first official release of the package, including +PO mode, occurred in July 1995, and was numbered 0.7. Other people +contributed to the effort by providing a discussion forum around +Ulrich, writing little pieces of code, or testing. These are quoted +in the THANKS file which comes with the GNU gettext +distribution. +

+

While this was being done, François adapted half a dozen of +GNU packages to glocale first, then later to gettext, +putting them in pretest, so providing along the way an effective +user environment for fine tuning the evolving tools. He also took +the responsibility of organizing and coordinating the Translation +Project. After nearly a year of informal exchanges between people from +many countries, translator teams started to exist in May 1995, through +the creation and support by Patrick D'Cruze of twenty unmoderated +mailing lists for that many native languages, and two moderated +lists: one for reaching all teams at once, the other for reaching +all willing maintainers of internationalized free software packages. +

+

François also wrote PO mode in June 1995 with the collaboration +of Greg McGary, as a kind of contribution to Ulrich's package. +He also gave a hand with the GNU gettext Texinfo manual. +

+

In 1997, Ulrich Drepper released the GNU libc 2.0, which included the +gettext, textdomain and bindtextdomain functions. +

+

In 2000, Ulrich Drepper added plural form handling (the ngettext +function) to GNU libc. Later, in 2001, he released GNU libc 2.2.x, +which is the first free C library with full internationalization support. +

+

Ulrich being quite busy in his role of General Maintainer of GNU libc, +he handed over the GNU gettext maintenance to Bruno Haible in +2000. Bruno added the plural form handling to the tools as well, added +support for UTF-8 and CJK locales, and wrote a few new tools for +manipulating PO files. +

+ + + + +

17.2 Notes on the Free Translation Project

+ +

This section contains the text that was, for a long time, distributed +as a file named ABOUT-NLS. +

+

NOTE: This documentation section is outdated. It it included +here for historical purposes only. +

+ +

Free software is going international! The Free Translation Project is +a way to get maintainers of free software, translators, and users all +together, so that free software will gradually become able to speak many +languages. A few packages already provide translations for their messages. +

+

If you found this ‘ABOUT-NLS’ file inside a distribution, you +may assume that the distributed package does use GNU gettext +internally, itself available at your nearest GNU archive site. But you +do not need to install GNU gettext prior to configuring, +installing or using this package with messages translated. +

+

Installers will find here some useful hints. These notes also explain +how users should proceed for getting the programs to use the available +translations. They tell how people wanting to contribute and work +on translations can contact the appropriate team. +

+ + + + + +

17.2.1 INSTALL Matters

+ +

Some packages are localizable when properly installed; the +programs they contain can be made to speak your own native language. +Most such packages use GNU gettext. Other packages have their +own ways to internationalization, predating GNU gettext. +

+

By default, this package will be installed to allow translation of +messages. It will automatically detect whether the system already +provides the GNU gettext functions. Installers may use special +options at configuration time for changing the default behaviour. The +command: +

+
 
./configure --disable-nls
+
+ +

will totally disable translation of messages. +

+

When you already have GNU gettext installed on your system and +run configure without an option for your new package, configure +will probably detect the previously built and installed ‘libintl’ +library and will decide to use it. If not, you may have to to use the +‘--with-libintl-prefix’ option to tell configure where to +look for it. +

+

Internationalized packages usually have many ‘po/ll.po’ +or ‘po/ll_CC.po’ +files, where +

+
    +
  • +ll gives an ISO 639 two-letter code identifying the language. +For some languages, +a two-letter code does not exist, and a three-letter code is used instead. +
  • +The optional CC is an ISO 3166 two-letter code of a country or +territory. +
+ +

Unless translations have been forbidden +at configure time by using the ‘--disable-nls’ switch, +all available translations are installed together with the package. +However, the environment variable LINGUAS may be set, prior +to configuration, to limit the installed set. +LINGUAS should then contain a space separated list of locale names +(of the form ll or ll_CC, +stating which languages or language variants are allowed. +

+ + + +

17.2.2 Using This Package

+ +

As a user, if your language has been installed for this package, you +only have to set the LANG environment variable to the appropriate +‘ll_CC’ combination. If you happen to have the LC_ALL +or some other LC_xxx environment variables set, you should unset them +before setting LANG, otherwise the setting of LANG will not +have the desired effect. Here +

+
    +
  • +‘ll’ is an ISO 639 two-letter language code. +For some languages, +a two-letter code does not exist, and a three-letter code is used instead. +
  • +‘CC’ is an ISO 3166 two-letter code of a country or territory. +
+ +

For example, let's suppose that you +speak German and live in Germany. At the shell prompt, merely execute +‘setenv LANG de_DE’ (in csh), +‘export LANG; LANG=de_DE’ (in sh) or +‘export LANG=de_DE’ (in bash). This can be done from your +‘.login’ or ‘.profile’ file, once and for all. +

+

You might think that the country code specification is redundant. But in +fact, some languages have dialects in different countries. For example, +‘de_AT’ is used for Austria, and ‘pt_BR’ for Brazil. The country +code serves to distinguish the dialects. +

+

The locale naming convention of ‘ll_CC’, with +‘ll’ denoting the language and ‘CC’ denoting the +country, is the one use on systems based on GNU libc. On other systems, +some variations of this scheme are used, such as ‘ll’ or +‘ll_CC.encoding’. You can get the list of +locales supported by your system for your language by running the command +‘locale -a | grep '^ll'’. +

+

Not all programs have translations for all languages. By default, an +English message is shown in place of a nonexistent translation. If you +understand other languages, you can set up a priority list of languages. +This is done through a different environment variable, called +LANGUAGE. GNU gettext gives preference to LANGUAGE +over LANG for the purpose of message handling, but you still +need to have LANG set to the primary language; this is required +by other parts of the system libraries. +For example, some Swedish users who would rather read translations in +German than English for when Swedish is not available, set LANGUAGE +to ‘sv:de’ while leaving LANG to ‘sv_SE’. +

+

Special advice for Norwegian users: The language code for Norwegian +bokmål changed from ‘no’ to ‘nb’ recently (in 2003). +During the transition period, while some message catalogs for this language +are installed under ‘nb’ and some older ones under ‘no’, it's +recommended for Norwegian users to set LANGUAGE to ‘nb:no’ so that +both newer and older translations are used. +

+

In the LANGUAGE environment variable, but not in the LANG +environment variable, ‘ll_CC’ combinations can be +abbreviated as ‘ll’ to denote the language's main dialect. +For example, ‘de’ is equivalent to ‘de_DE’ (German as spoken in +Germany), and ‘pt’ to ‘pt_PT’ (Portuguese as spoken in Portugal) +in this context. +

+ + + + +

17.2.3 Translating Teams

+ +

For the Free Translation Project to be a success, we need interested +people who like their own language and write it well, and who are also +able to synergize with other translators speaking the same language. +Each translation team has its own mailing list. The up-to-date list +of teams can be found at the Free Translation Project's homepage, +‘https://translationproject.org/’, in the "Teams" area. +

+

If you'd like to volunteer to work at translating messages, you +should become a member of the translating team for your own language. +The subscribing address is not the same as the list itself, it +has ‘-request’ appended. For example, speakers of Swedish can send +a message to ‘sv-request@li.org’, having this message body: +

+
 
subscribe
+
+ +

Keep in mind that team members are expected to participate +actively in translations, or at solving translational +difficulties, rather than merely lurking around. If your team does not +exist yet and you want to start one, or if you are unsure about what to +do or how to get started, please write to +‘coordinator@translationproject.org’ to reach the +coordinator for all translator teams. +

+

The English team is special. It works at improving and uniformizing +the terminology in use. Proven linguistic skills are praised +more than programming skills, here. +

+ + + +

17.2.4 Available Packages

+ +

Languages are not equally supported in all packages. The following +matrix shows the current state of internationalization, as of +May 2025. The matrix shows, in regard of each package, for which +languages PO files have been submitted to translation coordination, +with a translation percentage of at least 50%. +

+
 
Ready PO files       ab af an ar ast be bg bn bn_IN ca ckb crh cs da
+                   +-------------------------------------------------+
+a2ps               |                                           []    |
+anubis             |                                              [] |
+aspell             |             []  []             []         [] [] |
+bash               |                    []          []         []    |
+beebase            |                                                 |
+bfd                |                                                 |
+binutils           |                                []               |
+bison              |                    []          []               |
+bison-runtime      |             []     []          []            [] |
+buzztrax           |                                           [] [] |
+ccd2cue            |                                              [] |
+ccide              |                                              [] |
+cflow              |                                                 |
+chambercourt       |                                                 |
+clisp              |                                              [] |
+coreutils          |                    []          []         [] [] |
+cpio               |                    []                        [] |
+cppi               |                                              [] |
+cpplib             |                                                 |
+cryptsetup         |                                           [] [] |
+datamash           |                                              [] |
+denemo             |                                []         [] [] |
+dfarc              |                                []            [] |
+dialog             |       []    []                 []         [] [] |
+dico               |                                              [] |
+diffutils          |                    []                     [] [] |
+dink               |                                []            [] |
+direvent           |                                              [] |
+doodle             |                                           [] [] |
+dos2unix           |                                []            [] |
+dos2unix-man       |                                                 |
+e2fsprogs          |                                []         [] [] |
+enscript           |                                []            [] |
+exif               |             []                            [] [] |
+fetchmail          |                                []         [] [] |
+findutils          |                 [] []                     [] [] |
+flex               |                    []          []            [] |
+freedink           |                                []         [] [] |
+fusionforge        |                                                 |
+gas                |                                                 |
+gawk               |                    []          []               |
+gcal               |                                []            [] |
+gcc                |                                                 |
+gdbm               |                                                 |
+gettext-examples   |    []       []     []          []         [] [] |
+gettext-runtime    |             []     []          []         [] [] |
+gettext-tools      |                    []          []            [] |
+gnubik             |          []                                  [] |
+gnuchess           |                                              [] |
+gnucobol           |                                                 |
+gnulib             |                    []                           |
+gnunet             |                                                 |
+gnunet-gtk         |                                                 |
+gnutls             |                                           []    |
+gold               |                                                 |
+gphoto2            |                                           [] [] |
+gprof              |                    []                        [] |
+grep               |                 [] []          []         [] [] |
+grip               |                 [] []          []            [] |
+grub               |             []                 []            [] |
+gsasl              |                                              [] |
+gss                |                                              [] |
+gst-plugins-bad    |             []     []                     [] [] |
+gst-plugins-base   |                    []          []         [] [] |
+gst-plugins-good   |                    []          []         [] [] |
+gst-plugins-ugly   |             []     []          []         [] [] |
+gstreamer          |             []     []          []         [] [] |
+gtick              |                                           [] [] |
+gtkam              |                 []                        [] [] |
+gtkspell           |    []       []  []             []         [] [] |
+gutenprint         |                                []            [] |
+hello              |                                           []    |
+help2man           |                                              [] |
+help2man-texi      |                                                 |
+i18nparse          |                                                 |
+idutils            |                                              [] |
+kbd                |                                           []    |
+klavaro            |          []        [] []       []         [] [] |
+ld                 |                                                 |
+libc               |                 [] []          []         [] [] |
+libexif            |                                              [] |
+libextractor       |                                              [] |
+libgphoto2         |                                           [] [] |
+libgphoto2_port    |                                           [] [] |
+libiconv           |                 [] []                     [] [] |
+libidn             |                                           [] [] |
+libidn2            |                                           [] [] |
+lilypond           |                                []         [] [] |
+lordsawar          |                                []            [] |
+lynx               |                                []         [] [] |
+m4                 |                    []                           |
+mailfromd          |                                              [] |
+mailutils          |                                                 |
+make               |                    []                     [] [] |
+man-db             |             []                 []         [] [] |
+man-db-manpages    |                                                 |
+meritous           |                                              [] |
+midi-instruments   |          []                    []         [] [] |
+minicom            |                                           [] [] |
+mpop               |                                                 |
+msmtp              |                                                 |
+nano               |                                []         [] [] |
+opcodes            |                                                 |
+parted             |                                           [] [] |
+pies               |                                                 |
+procps-ng          |                                                 |
+procps-ng-man      |                                                 |
+psmisc             |                 []                        [] [] |
+psmisc-man         |                                                 |
+pspp               |          []                    []               |
+pyspread           |                                              [] |
+radius             |                                []               |
+recode             |                 []             []         [] [] |
+recutils           |                                                 |
+rush               |                                              [] |
+sarg               |                                              [] |
+savane             |                                                 |
+sed                |             []  [] []          []         [] [] |
+sharutils          |                                           []    |
+shepherd           |                                                 |
+shishi             |                                                 |
+skribilo           |                                              [] |
+solfege            |                                []         [] [] |
+solfege-manual     |                                []               |
+sudo               |             []                 []         [] [] |
+sudoers            |                                []         []    |
+sysstat            |                 []                              |
+tar                |                    []          []         [] [] |
+texinfo            |                                []         [] [] |
+texinfo_document   |                                           []    |
+tigervnc           |                    []                     []    |
+tin                |                                              [] |
+tin-man            |                                                 |
+trader             |                                              [] |
+util-linux         |                                           [] [] |
+util-linux-man     |                                                 |
+vmm                |                                                 |
+vorbis-tools       |                                           [] [] |
+wastesedge         |                                              [] |
+wcd                |                                              [] |
+wcd-man            |                                                 |
+wdiff              |                                []         [] [] |
+wget               |                 []                        [] [] |
+wget2              |                                                 |
+wincoll            |                                                 |
+wyslij-po          |                                              [] |
+xboard             |                                              [] |
+xdg-user-dirs      | [] [] [] [] []  [] []     []   [] []  []  [] [] |
+xkeyboard-config   |          []        []          []         [] [] |
+xz                 |                                []               |
+xz-man             |                                                 |
+                   +-------------------------------------------------+
+                     ab af an ar ast be bg bn bn_IN ca ckb crh cs da
+                      1  3  2  6 15  14 31  1   1   52  1   1  62 95
+
+                     de  el en en_GB eo es  et eu fa fi fr  fur ga gd
+                   +--------------------------------------------------+
+a2ps               | []  []             []  []          []            |
+anubis             | []                 []           [] []            |
+aspell             | []         []   [] []           [] []  []  []    |
+bash               | []              [] []              []      []    |
+beebase            | []                 []              []            |
+bfd                |                    []              []            |
+binutils           |                                    []            |
+bison              | []  []          [] []  []       [] []            |
+bison-runtime      | []  []          [] []  []       [] []      []    |
+buzztrax           | []                 []           [] []            |
+ccd2cue            | []              [] []              []            |
+ccide              | []              [] []           [] []  []        |
+cflow              | []              []                 []            |
+chambercourt       |     []                             []            |
+clisp              | []     []          []              []            |
+coreutils          | []                 []  []          []            |
+cpio               | []                 []           [] []      []    |
+cppi               | []              [] []           [] []            |
+cpplib             | []                                 []            |
+cryptsetup         | []                 []              []            |
+datamash           | []              [] []              []            |
+denemo             |                                                  |
+dfarc              | []              [] []           [] []  []        |
+dialog             | []  []          [] []     [] [] [] []  []  [] [] |
+dico               | []                 []           [] []            |
+diffutils          | []  []          [] []           [] []            |
+dink               | []              [] []           [] []            |
+direvent           | []              [] []              []            |
+doodle             | []              [] []           [] []      []    |
+dos2unix           | []              [] []              []  []        |
+dos2unix-man       | []                 []              []            |
+e2fsprogs          | []                 []              []            |
+enscript           | []         []   [] []           [] []      []    |
+exif               | []              [] []           [] []  []        |
+fetchmail          | ()         []   [] []              []            |
+findutils          | []  []          [] []  []       [] []            |
+flex               | []              [] []           [] []      []    |
+freedink           | []  []          [] []     []    [] []  []        |
+fusionforge        | []                 []              []            |
+gas                |                    []           [] []            |
+gawk               | []                 []           [] []            |
+gcal               | []                 []              []            |
+gcc                | []                                 []            |
+gdbm               | []              [] []              []            |
+gettext-examples   | []  []          [] []           [] []      []    |
+gettext-runtime    | []              [] []           [] []      []    |
+gettext-tools      | []                 []           [] []            |
+gnubik             | []              [] []           [] []  []        |
+gnuchess           | []              [] []              []            |
+gnucobol           | []                                 []            |
+gnulib             | []              [] []           [] []            |
+gnunet             |                    []                            |
+gnunet-gtk         | []                 []                            |
+gnutls             | []              [] []           [] []            |
+gold               |                    []           [] []            |
+gphoto2            | ()              []                 []            |
+gprof              | []              [] []           [] []      []    |
+grep               | []              [] []  []       [] []      []    |
+grip               | []                 []           [] []  []        |
+grub               | []              [] []           [] []            |
+gsasl              | []              [] []           [] []      []    |
+gss                | []              [] []           [] []      []    |
+gst-plugins-bad    | []              [] []              []  []        |
+gst-plugins-base   | []  []          [] []           [] []  []        |
+gst-plugins-good   | []  []          [] []           [] []  []        |
+gst-plugins-ugly   | []  []          [] []     []    [] []  []        |
+gstreamer          | []  []          [] []     []    [] []  []        |
+gtick              | ()              [] []           [] []      []    |
+gtkam              | ()              [] []           [] []            |
+gtkspell           | []  []          [] []     []    [] []  []  []    |
+gutenprint         | []                 []              []            |
+hello              | []                     []    [] [] []            |
+help2man           | []  []          [] []           [] []            |
+help2man-texi      | []                 []              []            |
+i18nparse          | []              [] []              ()            |
+idutils            | []              [] []           [] []      []    |
+kbd                | []  []          [] []              []            |
+klavaro            | []  []          [] []     []       []            |
+ld                 |                    []              []            |
+libc               | []                 []           [] []            |
+libexif            | []                 []              []            |
+libextractor       | []                 []              []            |
+libgphoto2         | ()                 []              []            |
+libgphoto2_port    | ()                 []     []    [] []  []        |
+libiconv           | []              [] []  []       [] []      []    |
+libidn             | []              [] []           [] []            |
+libidn2            | []              [] []              []  []        |
+lilypond           | []              [] []              []            |
+lordsawar          | []                                 []            |
+lynx               | []              []     []       [] []            |
+m4                 | []              [] []              []            |
+mailfromd          | []                                 []            |
+mailutils          | []                 []           [] []            |
+make               | []                 []           [] []      []    |
+man-db             | []              [] []              []            |
+man-db-manpages    | []                 []              []            |
+meritous           |                 []                               |
+midi-instruments   | []  []          [] []  []    [] [] []            |
+minicom            | []                 []           [] []            |
+mpop               | []              [] []              []            |
+msmtp              | []              [] []              []            |
+nano               | []              [] []           [] []      []    |
+opcodes            | []                                 []            |
+parted             | []                 []              []  []        |
+pies               | []                 []              []            |
+procps-ng          | []                 []              []            |
+procps-ng-man      |                                                  |
+psmisc             | []  []          [] []           [] []            |
+psmisc-man         | []                                 []            |
+pspp               | []  []             []              []            |
+pyspread           | []                                 []            |
+radius             |                    []              []            |
+recode             | []              [] []           [] []      []    |
+recutils           | []                              [] []            |
+rush               | []                 []           [] []            |
+sarg               | []                 []              []            |
+savane             | []                 []              []            |
+sed                | []  []          [] []  []       [] []      []    |
+sharutils          | []              []     []          []            |
+shepherd           | []                                               |
+shishi             | []                              [] []            |
+skribilo           |                 [] []              []  []        |
+solfege            | []              [] []  []    [] [] []            |
+solfege-manual     | []              [] []  []          []            |
+sudo               | []              [] []           [] []  []        |
+sudoers            | []              []              [] []            |
+sysstat            | []              []              [] []  []        |
+tar                | []              [] []  []       [] []      []    |
+texinfo            | []              [] []              []            |
+texinfo_document   |                    []              []            |
+tigervnc           | []                 []           [] []  []        |
+tin                | []                     []          []            |
+tin-man            | []         []                                    |
+trader             | []         []   []              [] []            |
+util-linux         | []                 []              []            |
+util-linux-man     | []                                 []            |
+vmm                |                                                  |
+vorbis-tools       | []              [] []              []            |
+wastesedge         |                                    []            |
+wcd                | []              [] []           [] []  []        |
+wcd-man            | []                                 []            |
+wdiff              | []              [] []  []       [] []      []    |
+wget               | []              [] []  []       [] []      []    |
+wget2              | []                 []              []            |
+wincoll            | []  []             []              []            |
+wyslij-po          | []              [] []           [] []            |
+xboard             | []                 []              []            |
+xdg-user-dirs      | []  []          [] []  [] [] [] [] []  []  [] [] |
+xkeyboard-config   | []              [] []           [] []  []        |
+xz                 | []              [] []           []               |
+xz-man             | []                                 []            |
+                   +--------------------------------------------------+
+                     de  el en en_GB eo es  et eu fa fi fr  fur ga gd
+                     131 23  1   5   81 121 19  8  5 74 142 25  26  2
+
+                     gl gu he hi hr hu hy id is it ja ka kk kn ko ku
+                   +-------------------------------------------------+
+a2ps               |             [] []             []          []    |
+anubis             |             [] []    []    []                   |
+aspell             |             [] []    []    [] []                |
+bash               |             [] []                         []    |
+beebase            |                            ()                   |
+bfd                |                                                 |
+binutils           |                                                 |
+bison              |                               []                |
+bison-runtime      | []          [] []    []    [] [] []             |
+buzztrax           |                                                 |
+ccd2cue            |                []                               |
+ccide              |             [] []                []             |
+cflow              |                                                 |
+chambercourt       |                                                 |
+clisp              |                                                 |
+coreutils          |             [] []             []          []    |
+cpio               |             [] []    []    [] []          []    |
+cppi               | []          [] []          [] [] []             |
+cpplib             |                                                 |
+cryptsetup         |                               []                |
+datamash           |                                                 |
+denemo             |                                                 |
+dfarc              |             [] []          []                   |
+dialog             | []          [] []    [] [] [] [] []          [] |
+dico               |                                                 |
+diffutils          |             [] []    []    [] [] []       []    |
+dink               |                []                               |
+direvent           |                []                               |
+doodle             |                            []                   |
+dos2unix           |                []             [] []       []    |
+dos2unix-man       |                                           []    |
+e2fsprogs          |                []                               |
+enscript           |             []       []                         |
+exif               | []          [] []    [] [] [] [] []       []    |
+fetchmail          |                      []    [] []                |
+findutils          |             [] []    []    []    []       []    |
+flex               |                                                 |
+freedink           |             [] []    []    []                   |
+fusionforge        |                                                 |
+gas                |                      []                         |
+gawk               |                      []    ()             []    |
+gcal               |                                                 |
+gcc                |                                                 |
+gdbm               |                                  []             |
+gettext-examples   | []          [] []    []    [] [] []             |
+gettext-runtime    | []          [] []          [] []          []    |
+gettext-tools      |             []       []    [] []          []    |
+gnubik             | []    []    []             []                   |
+gnuchess           | []                                              |
+gnucobol           |                                                 |
+gnulib             |                            []    []             |
+gnunet             |                                                 |
+gnunet-gtk         |                                                 |
+gnutls             |                            []    []             |
+gold               |                                                 |
+gphoto2            |                []    []    [] [] []       []    |
+gprof              |                []    []    []    []             |
+grep               | []          [] []    []    [] [] []       []    |
+grip               |                []          [] []          []    |
+grub               | []    []    [] []    []    []    []       []    |
+gsasl              |                []    []    []    []             |
+gss                |             [] []    []    []    []             |
+gst-plugins-bad    |             [] []    []    []    []             |
+gst-plugins-base   | []          [] []    []    []    []             |
+gst-plugins-good   | []          [] []    []    [] [] []             |
+gst-plugins-ugly   | []          [] []    []    [] [] []             |
+gstreamer          | []          [] []    []    []                   |
+gtick              | []             []    []    []                   |
+gtkam              |       []       []    [] [] [] []                |
+gtkspell           | []    []    [] [] [] [] [] [] [] []             |
+gutenprint         | []          [] []          []    []             |
+hello              |             []                   []             |
+help2man           |             []             [] []          []    |
+help2man-texi      |                                                 |
+i18nparse          |                                  []             |
+idutils            |                []    []          []             |
+kbd                |                      []                         |
+klavaro            | []          [] []    []    []       []          |
+ld                 |                                                 |
+libc               | []          []       []    [] []          []    |
+libexif            |                            []                   |
+libextractor       |                                                 |
+libgphoto2         |                                                 |
+libgphoto2_port    |                            [] [] []             |
+libiconv           | []          [] []    []    [] [] []       []    |
+libidn             |             [] []    []    []             []    |
+libidn2            |                []    []          []       []    |
+lilypond           |                            [] []                |
+lordsawar          |                               []                |
+lynx               |                []    []    [] []                |
+m4                 |                                           []    |
+mailfromd          |                                                 |
+mailutils          |                                                 |
+make               |             []       []    [] []          []    |
+man-db             |                      []    [] []          []    |
+man-db-manpages    |                      []                   []    |
+meritous           |                                                 |
+midi-instruments   | []    []    [] [] [] [] [] [] [] []       [] [] |
+minicom            |                []    []       [] []       []    |
+mpop               |                                                 |
+msmtp              |                                                 |
+nano               | []          [] []    [] [] [] []          []    |
+opcodes            |                                                 |
+parted             |                []    []    [] [] []       []    |
+pies               |                                                 |
+procps-ng          |                                           []    |
+procps-ng-man      |                                                 |
+psmisc             |             [] []    []    []    []       []    |
+psmisc-man         |             []                            []    |
+pspp               |                []             []                |
+pyspread           |                                                 |
+radius             |                      []                         |
+recode             | []    []    [] []    []    []                   |
+recutils           |                                                 |
+rush               |                                                 |
+sarg               |                                  []             |
+savane             |       []                                        |
+sed                | []          [] []    []    [] [] []       []    |
+sharutils          |                                                 |
+shepherd           |                                                 |
+shishi             |                                                 |
+skribilo           |                []                               |
+solfege            | []                         []                   |
+solfege-manual     |                                                 |
+sudo               | []          [] []    []    [] [] []       []    |
+sudoers            |             []       []    [] []          []    |
+sysstat            |             []       []    []    []       []    |
+tar                |             [] []    []    [] []          []    |
+texinfo            |             []             []                   |
+texinfo_document   |             []                   []             |
+tigervnc           |       []             []          []       []    |
+tin                |                                                 |
+tin-man            |                                                 |
+trader             |             [] []                               |
+util-linux         |             []                []          []    |
+util-linux-man     |                                                 |
+vmm                |                                                 |
+vorbis-tools       |             []       []          []             |
+wastesedge         |                            []                   |
+wcd                |                                                 |
+wcd-man            |                                                 |
+wdiff              | []             []          []                   |
+wget               |             [] []    []    [] []          []    |
+wget2              |             []       []       []          []    |
+wincoll            |                                                 |
+wyslij-po          | []          [] []    []                         |
+xboard             |                                                 |
+xdg-user-dirs      | [] [] [] [] [] []    [] [] [] [] [] [] [] [] [] |
+xkeyboard-config   | []    []    [] []    []    []    []       []    |
+xz                 |             [] []          []    []       []    |
+xz-man             |                            []             []    |
+                   +-------------------------------------------------+
+                     gl gu he hi hr hu hy id is it ja ka kk kn ko ku
+                     30  1 10  1 58 62  2 59  7 65 45 44  2  1 45  3
+
+                     ky lg lt lv mk ml mn mr ms mt nb ne nl nn or pa
+                   +-------------------------------------------------+
+a2ps               |                         []    []    []          |
+anubis             |                         []    []    []          |
+aspell             |                   []                []          |
+bash               |                               []    []          |
+beebase            |                                     []          |
+bfd                |                                                 |
+binutils           |                                                 |
+bison              |                         []                      |
+bison-runtime      | []    [] []             []    []    []          |
+buzztrax           |                                                 |
+ccd2cue            |                                                 |
+ccide              |          []                         []          |
+cflow              |                                                 |
+chambercourt       |                                                 |
+clisp              |                                     []          |
+coreutils          |                               []    []          |
+cpio               |                                     []          |
+cppi               |                                                 |
+cpplib             |                                                 |
+cryptsetup         |                                                 |
+datamash           |                               []    []          |
+denemo             |                                     []          |
+dfarc              |             []                      []          |
+dialog             |       [] []             []    []    []          |
+dico               |                                                 |
+diffutils          |          []             []    []    []          |
+dink               |                                     []          |
+direvent           |                                     []          |
+doodle             |                                     []          |
+dos2unix           |                               []    []          |
+dos2unix-man       |                                     []          |
+e2fsprogs          |                                     []          |
+enscript           |                                     []          |
+exif               |          []             []          []          |
+fetchmail          |                                     []          |
+findutils          |                               []    []          |
+flex               |                                     []          |
+freedink           |          []                   []    []          |
+fusionforge        |                                                 |
+gas                |                                                 |
+gawk               |                                     []          |
+gcal               |                                                 |
+gcc                |                                                 |
+gdbm               |                                                 |
+gettext-examples   | []       []             [] [] []    [] []       |
+gettext-runtime    |                               []    [] []       |
+gettext-tools      |                                                 |
+gnubik             |                               []    []          |
+gnuchess           |                               []    []          |
+gnucobol           |                                                 |
+gnulib             |                                     []          |
+gnunet             |                                                 |
+gnunet-gtk         |                                                 |
+gnutls             |                         []          []          |
+gold               |                                                 |
+gphoto2            |                                     []          |
+gprof              |                         []          []          |
+grep               |                               []    []          |
+grip               |                               []    []          |
+grub               |       []                      []    []          |
+gsasl              |                                     []          |
+gss                |                                                 |
+gst-plugins-bad    |          []                   []    []          |
+gst-plugins-base   |          []                   []    []          |
+gst-plugins-good   |          []                   []    []          |
+gst-plugins-ugly   |          []             [] [] []    []          |
+gstreamer          |       [] []                   []    []          |
+gtick              |                               []    []          |
+gtkam              |                               []    []       [] |
+gtkspell           | []    [] []       []    []    []    []          |
+gutenprint         |                                     []          |
+hello              |          []                   []    []          |
+help2man           |                               []                |
+help2man-texi      |                                                 |
+i18nparse          |                                     []          |
+idutils            |                               []    []          |
+kbd                |                                                 |
+klavaro            |                               []    []       [] |
+ld                 |                                                 |
+libc               |                                     []          |
+libexif            |                                     []          |
+libextractor       |                                     []          |
+libgphoto2         |                                     []          |
+libgphoto2_port    |                                     []          |
+libiconv           |       []                            []          |
+libidn             |                                     []          |
+libidn2            |          []                         []          |
+lilypond           |                                     []          |
+lordsawar          |                                                 |
+lynx               |                                     []          |
+m4                 |                                     []          |
+mailfromd          |                                                 |
+mailutils          |                                                 |
+make               |                                     []          |
+man-db             |                                     []          |
+man-db-manpages    |                                                 |
+meritous           |                                                 |
+midi-instruments   |       []          []    []       [] []          |
+minicom            |                               []                |
+mpop               |                                                 |
+msmtp              |                                                 |
+nano               |                         []    []    []          |
+opcodes            |                                                 |
+parted             |                                     []          |
+pies               |                                                 |
+procps-ng          |                                                 |
+procps-ng-man      |                                                 |
+psmisc             |                                     []          |
+psmisc-man         |                                                 |
+pspp               |       []                            []          |
+pyspread           |                                        []       |
+radius             |                                     []          |
+recode             |                               []    []          |
+recutils           |                                     []          |
+rush               |                                     []          |
+sarg               |                                                 |
+savane             |                                                 |
+sed                |                               []    []          |
+sharutils          |                                     []          |
+shepherd           |                                                 |
+shishi             |                                                 |
+skribilo           |                                                 |
+solfege            |                               []    []          |
+solfege-manual     |                                     []          |
+sudo               |                               []    []          |
+sudoers            |                               []                |
+sysstat            |          []                   []    []          |
+tar                | []                            []    []          |
+texinfo            |                               []    []          |
+texinfo_document   |                                                 |
+tigervnc           |                                                 |
+tin                |                                                 |
+tin-man            |                                                 |
+trader             |                               []                |
+util-linux         |                                     []          |
+util-linux-man     |                                                 |
+vmm                |                                                 |
+vorbis-tools       |                                     []          |
+wastesedge         |                                     []          |
+wcd                |                                     []          |
+wcd-man            |                                     []          |
+wdiff              |                         []    []    []          |
+wget               |                               []    []          |
+wget2              |                                                 |
+wincoll            |                                                 |
+wyslij-po          |                                     [] []       |
+xboard             |                                     []          |
+xdg-user-dirs      | [] [] [] [] [] []    []       []    [] [] [] [] |
+xkeyboard-config   |       []                            []          |
+xz                 |                                     []          |
+xz-man             |                                                 |
+                   +-------------------------------------------------+
+                     ky lg lt lv mk ml mn mr ms mt nb ne nl nn or pa
+                      5  1 10 17  2  1  3  1 15  2 44  1 95  5  1  3
+
+                     pl pt pt_BR ro  ru rw sk sl sq sr  sv  sw ta te
+                   +-------------------------------------------------+
+a2ps               | []          []  []             []  []           |
+anubis             | [] []       []  []             []  []           |
+aspell             | [] []  []   []  []    [] [] [] []  []           |
+bash               | [] []  []   []                 []  []           |
+beebase            |             []                 []  []           |
+bfd                |    []       []  []             []  []           |
+binutils           |    []       []  []             []  []           |
+bison              | [] []  []                      []  []           |
+bison-runtime      | [] []  []   []  []       [] [] []  []     []    |
+buzztrax           |        []   []                 []  []           |
+ccd2cue            |        []   []                 []  []           |
+ccide              | []          []  []             []  []           |
+cflow              | []     []   []                 []  []           |
+chambercourt       |        []   []                 []  []           |
+clisp              |                 []             []  []           |
+coreutils          | [] []  []   []  []       []    []  []           |
+cpio               | [] []  []   []  []             []  []           |
+cppi               | []     []   []                 []  []           |
+cpplib             |             []                     []           |
+cryptsetup         | []          []  []             []  []           |
+datamash           |        []   []                 []  []           |
+denemo             |                                                 |
+dfarc              | []     []   []                 []  []           |
+dialog             | [] []  []   []  []    [] [] [] []  []  []       |
+dico               | []     []   []                 []  []           |
+diffutils          | [] []  []   []  []             []  []           |
+dink               |                                    []           |
+direvent           | []     []   []                 []  []           |
+doodle             |        []   []              [] []  []           |
+dos2unix           | []     []   []  []             []  []           |
+dos2unix-man       | []     []   []                 []  []           |
+e2fsprogs          | [] []       []                 []  []           |
+enscript           | []     []   []  []       []    []  []           |
+exif               | [] []  []   []  []    []       []  []           |
+fetchmail          | []          []  []          [] []  []           |
+findutils          | [] []  []   []  []       []    []  []           |
+flex               | [] []  []   []  []             []  []           |
+freedink           | []     []   []  []       []    []  []           |
+fusionforge        |                                                 |
+gas                |             []  []                 []           |
+gawk               | [] []  []   []                 []  []           |
+gcal               |             []                 []  []           |
+gcc                |                 []                 []           |
+gdbm               | []     []   []  []             []  []           |
+gettext-examples   | [] []  []   []  []    [] [] [] []  []     []    |
+gettext-runtime    | [] []  []   []  []    [] []    []  []           |
+gettext-tools      | [] []  []   []  []    [] []    []  []           |
+gnubik             | [] []  []   []           []    []  []           |
+gnuchess           |        []   []                 []  []           |
+gnucobol           |                                []               |
+gnulib             | [] []  []   []  []             []  []           |
+gnunet             |                                []               |
+gnunet-gtk         |                                []               |
+gnutls             | []     []   []                 []  []           |
+gold               |             []                 []               |
+gphoto2            | []     []   []  []             []  []           |
+gprof              |        []   []  []             []  []           |
+grep               | [] []  []   []  []    [] []    []  []     []    |
+grip               | []     []   []  []             []               |
+grub               | [] []  []   []  []       []    []  []           |
+gsasl              | []     []   []        []       []  []           |
+gss                | []     []   []        []       []  []           |
+gst-plugins-bad    | []     []   []  []    [] []    []  []           |
+gst-plugins-base   | []     []   []  []    [] []    []  []           |
+gst-plugins-good   | []     []   []  []    [] []    []  []           |
+gst-plugins-ugly   | []     []   []  []    [] [] [] []  []     []    |
+gstreamer          | []     []   []  []    [] []    []  []           |
+gtick              | []     []   []  []    []       []  []           |
+gtkam              | [] []  []   []  []    []       []  []           |
+gtkspell           | [] []  []   []  []    [] [] [] []  []     []    |
+gutenprint         |             []  []    [] []        []           |
+hello              | [] []  []   []  []    []       []  []     []    |
+help2man           | []     []   []  []             []  []           |
+help2man-texi      | []     []   []                 []  []           |
+i18nparse          |        []   []           []        []           |
+idutils            | []     []   []  []             []  []           |
+kbd                | [] []  []   []  []             []  []           |
+klavaro            | [] []  []   []  []    [] []    []  []           |
+ld                 |        []   []  []             []               |
+libc               | [] []  []   []  []    []       []  []           |
+libexif            | []          []        []       []  []           |
+libextractor       | []     []   []                 []               |
+libgphoto2         | []          []                     []           |
+libgphoto2_port    | []     []   []  []    []       []  []           |
+libiconv           | []     []   []  []    [] []    []  []           |
+libidn             | []     []   []                 []  []           |
+libidn2            | []     []   []  []             []  []           |
+lilypond           |             []                     []           |
+lordsawar          |                 []                 []           |
+lynx               |        []   []  []                 []           |
+m4                 | []     []   []                 []  []           |
+mailfromd          | []     []   []                 []               |
+mailutils          | []     []   []                 []               |
+make               | [] []  []   []  []             []  []           |
+man-db             | [] []  []   []  []             []  []           |
+man-db-manpages    | [] []  []   []  []             []  []           |
+meritous           |        []   []                 []  []           |
+midi-instruments   | [] []  []   []  []    [] []    []  []           |
+minicom            | []     []   []  []             []  []           |
+mpop               |        []   []  []             []  []           |
+msmtp              |        []   []  []             []  []           |
+nano               | [] []  []   []  []    []    [] []  []           |
+opcodes            |        []   []                 []  []           |
+parted             | [] []  []   []  []    [] []    []  []           |
+pies               | []     []   []                 []               |
+procps-ng          | []     []   []                     []           |
+procps-ng-man      |             []                     []           |
+psmisc             | [] []  []   []  []             []  []           |
+psmisc-man         |        []   []  []             []  []           |
+pspp               |                 []                 []     []    |
+pyspread           |        []                      []  []           |
+radius             | []              []             []               |
+recode             | [] []  []   []  []    [] []    []  []           |
+recutils           |        []   []                 []  []           |
+rush               | []     []   []                 []  []           |
+sarg               |        []   []  []             []               |
+savane             |        []   []  ()                              |
+sed                | [] []  []   []  []    [] []    []  []           |
+sharutils          | []     []   []                 []  []           |
+shepherd           |             []        []       []  []           |
+shishi             | []          []                 []  []           |
+skribilo           |        []   []                 []  []           |
+solfege            | []     []   []  []    []           []           |
+solfege-manual     | []     []   []                     []           |
+sudo               | [] []  []   []  []             []  []           |
+sudoers            | [] []  []   []  []             []  []           |
+sysstat            |    []  []   []  []             []  []           |
+tar                | [] []  []   []  []       []    []  []           |
+texinfo            | [] []  []   []  []    []       []  []           |
+texinfo_document   | [] []  []   []        []       []  []           |
+tigervnc           |             []  []    []       []  []           |
+tin                |                 []                              |
+tin-man            |                                                 |
+trader             |        []   []  []             []  []           |
+util-linux         | [] []  []   []                 []  []           |
+util-linux-man     | []          []                 []               |
+vmm                |             []                 []               |
+vorbis-tools       | []     []   []           []    []  []           |
+wastesedge         |        []                          []           |
+wcd                |        []   []                 []  []           |
+wcd-man            |        []   []                 []  []           |
+wdiff              | []     []   []  []       []    []  []           |
+wget               | [] []  []   []  []    []       []  []           |
+wget2              | []          []  []             []  []           |
+wincoll            |        []   []        []       []  []           |
+wyslij-po          | []     []   []                 []  []           |
+xboard             | []          []  []             []  []           |
+xdg-user-dirs      | [] []  []   []  []    [] [] [] []  []     [] [] |
+xkeyboard-config   | [] []  []   []  []       [] [] []  []           |
+xz                 | [] []  []   []                 []  []           |
+xz-man             |        []   []                 []               |
+                   +-------------------------------------------------+
+                     pl pt pt_BR ro  ru rw sk sl sq sr  sv  sw ta te
+                     99 49  113  135 85  0 37 32 11 130 131  1  8  1
+
+                     tg th tr uk  ur vi wa wo zh_CN zh_HK zh_TW
+                   +--------------------------------------------+
+a2ps               |    []    []                                | 20
+anubis             |       [] []     []                         | 21
+aspell             |          []     [] []     []               | 34
+bash               |          []     []        []          []   | 23
+beebase            |          []                                |  8
+bfd                |          []                                |  8
+binutils           |          []                                |  8
+bison              |          []                           []   | 18
+bison-runtime      |    [] [] []     []        []          []   | 41
+buzztrax           |                 []        []               | 12
+ccd2cue            |    []    []     []        []               | 14
+ccide              |          []     []        []               | 20
+cflow              |          []               []               | 10
+chambercourt       |          []                                |  7
+clisp              |                                            | 13
+coreutils          |       [] []     []        []          []   | 27
+cpio               |       [] []     []        []               | 25
+cppi               |          []     []        []               | 20
+cpplib             |          []               []               |  6
+cryptsetup         |          []               []               | 13
+datamash           |          []                                | 12
+denemo             |                           []    []    []   |  7
+dfarc              |                 []                         | 19
+dialog             |    [] [] []     [] []     []          []   | 48
+dico               |          []                                | 11
+diffutils          |       [] []     []        []          []   | 32
+dink               |       []                                   | 11
+direvent           |          []     []                         | 14
+doodle             |          []     []        []               | 18
+dos2unix           |          []     []        []          []   | 23
+dos2unix-man       |          []               []               | 12
+e2fsprogs          |          []     []        []               | 16
+enscript           |       [] []     []                         | 22
+exif               |       [] []     []        []               | 33
+fetchmail          |                 []        []               | 19
+findutils          |       [] []     []        []          []   | 32
+flex               |       [] []     []        []          []   | 22
+freedink           |    []           []                         | 27
+fusionforge        |                                            |  3
+gas                |          []                                |  8
+gawk               |       [] []     []        []               | 19
+gcal               |       []                  []               | 10
+gcc                |          []                                |  5
+gdbm               |          []     []                         | 13
+gettext-examples   |       [] []     []        []    []    []   | 44
+gettext-runtime    |       [] []     []        []          []   | 34
+gettext-tools      |       [] []     []        []          []   | 26
+gnubik             |          []     []        []               | 24
+gnuchess           |          []     []        []               | 15
+gnucobol           |                                            |  3
+gnulib             |          []               []          []   | 19
+gnunet             |                                            |  2
+gnunet-gtk         |                                            |  3
+gnutls             |          []     []        []               | 18
+gold               |          []                                |  6
+gphoto2            |          []     []        []          []   | 21
+gprof              |       [] []     []                         | 22
+grep               |    [] [] []     []        []          []   | 38
+grip               |          []     []        []    []    []   | 25
+grub               |       [] []     []        []               | 31
+gsasl              |          []     []        []               | 21
+gss                |                 []        []               | 20
+gst-plugins-bad    |       [] []     []        []          []   | 30
+gst-plugins-base   |       [] []     []        []               | 32
+gst-plugins-good   |       [] []     []        []          []   | 34
+gst-plugins-ugly   |       [] []     []        []          []   | 40
+gstreamer          |       [] []     []        []          []   | 35
+gtick              |          []     []        []               | 23
+gtkam              |          []     []        []               | 27
+gtkspell           |    [] [] []     [] []     []    []    []   | 51
+gutenprint         |       [] []               []               | 19
+hello              |    []    []               []               | 23
+help2man           |          []     []        []               | 21
+help2man-texi      |          []                                |  9
+i18nparse          |          []                                | 10
+idutils            |          []     []        []               | 21
+kbd                |          []                                | 15
+klavaro            |       [] []  [] []    []  []               | 36
+ld                 |          []                                |  7
+libc               |       [] []     []        []          []   | 29
+libexif            |          []     []                         | 13
+libextractor       |          []     []                         | 11
+libgphoto2         |          []     []                         | 10
+libgphoto2_port    |          []     []        []          []   | 22
+libiconv           |          []     [] []     []          []   | 34
+libidn             |          []     []        []               | 21
+libidn2            |          []               []               | 21
+lilypond           |                           []               | 13
+lordsawar          |       []                                   |  8
+lynx               |       [] []     []                         | 20
+m4                 |          []               []               | 14
+mailfromd          |          []     []                         |  9
+mailutils          |          []     []                         | 10
+make               |          []     []        []          []   | 25
+man-db             |       [] []     []        []          []   | 25
+man-db-manpages    |       [] []               []               | 15
+meritous           |                                            |  6
+midi-instruments   |    [] [] []     []        []          []   | 44
+minicom            |                 []                    []   | 20
+mpop               |          []                                | 10
+msmtp              |          []                                | 10
+nano               |       [] []     []        []          []   | 34
+opcodes            |          []                                |  7
+parted             |       [] []     []        []          []   | 27
+pies               |          []     []                         |  9
+procps-ng          |          []     []        []               | 11
+procps-ng-man      |          []               []               |  4
+psmisc             |          []     []        []          []   | 27
+psmisc-man         |          []                                | 10
+pspp               |    []    []               []               | 16
+pyspread           |          []                                |  8
+radius             |          []     []                         | 10
+recode             |       [] []     []        []               | 31
+recutils           |          []     []                         | 10
+rush               |          []     []        []               | 14
+sarg               |                                            |  9
+savane             |          []                                |  7
+sed                |       [] []     []        []          []   | 38
+sharutils          |          []     []        []               | 14
+shepherd           |          []                                |  6
+shishi             |                 []        []               |  9
+skribilo           |          []                                | 11
+solfege            |       []        []        []               | 23
+solfege-manual     |       []                                   | 12
+sudo               |       [] []     []        []          []   | 32
+sudoers            |          []               []          []   | 22
+sysstat            |       [] []     []        []               | 24
+tar                |       [] []     []        []          []   | 33
+texinfo            |       [] []     []                         | 22
+texinfo_document   |          []                                | 13
+tigervnc           |       [] []               []          []   | 20
+tin                |       []                  []          []   |  8
+tin-man            |                                            |  2
+trader             |                                            | 14
+util-linux         |       [] []               []               | 18
+util-linux-man     |          []                                |  6
+vmm                |          []                                |  3
+vorbis-tools       |                 []                         | 17
+wastesedge         |       []                                   |  7
+wcd                |          []     []        []               | 15
+wcd-man            |          []                                |  8
+wdiff              |          []     []        []          []   | 27
+wget               |       [] []     []        []          []   | 31
+wget2              |          []               []               | 14
+wincoll            |          []                                | 10
+wyslij-po          |          []     []        []               | 20
+xboard             |       [] []               []               | 13
+xdg-user-dirs      |    [] [] []     [] []     []    []    []   | 72
+xkeyboard-config   |       [] []               []               | 33
+xz                 |       [] []     []        []          []   | 22
+xz-man             |          []                                |  8
+                   +--------------------------------------------+
+  85 teams           tg th tr uk  ur vi wa wo zh_CN zh_HK zh_TW
+ 151 domains          0 11 52 125  1 87  5  1  90     5    42    2840
+
+ +

Some counters in the preceding matrix are higher than the number of visible +blocks let us expect. This is because a few extra PO files are used for +implementing regional variants of languages, or language dialects. +

+

For a PO file in the matrix above to be effective, the package to which +it applies should also have been internationalized and distributed as +such by its maintainer. There might be an observable lag between the +mere existence a PO file and its wide availability in a distribution. +

+

If May 2025 seems to be old, you may fetch a more recent copy +of this ‘ABOUT-NLS’ file on most GNU archive sites. The most +up-to-date matrix with full percentage details can be found at +‘https://translationproject.org/extra/matrix.html’. +

+ + + + +

17.2.5 Using gettext in new packages

+ +

If you are writing a freely available program and want to internationalize +it you are welcome to use GNU ‘gettext’ in your package. Of course +you have to respect the GNU Lesser General Public License which covers +the use of the GNU ‘gettext’ library. This means in particular that +even non-free programs can use libintl as a shared library, whereas +only free software can use libintl as a static library or use +modified versions of libintl. +

+

Once the sources are changed appropriately and the setup can handle the +use of gettext the only thing missing are the translations. The +Free Translation Project is also available for packages which are not +developed inside the GNU project. Therefore the information given above +applies also for every other Free Software Project. Contact +‘coordinator@translationproject.org’ to make the ‘.pot’ files +available to the translation teams. +

+ + + +

17.3 Related Readings

+ +

NOTE: This documentation section is outdated and needs to be +revised. +

+

Eugene H. Dorr (‘dorre@well.com’) maintains an interesting +bibliography on internationalization matters, called +Internationalization Reference List, which is available as: +

 
ftp://ftp.ora.com/pub/examples/nutshell/ujip/doc/i18n-books.txt
+
+ +

Michael Gschwind (‘mike@vlsivie.tuwien.ac.at’) maintains a +Frequently Asked Questions (FAQ) list, entitled Programming for +Internationalisation. This FAQ discusses writing programs which +can handle different language conventions, character sets, etc.; +and is applicable to all character set encodings, with particular +emphasis on ISO 8859-1. It is regularly published in Usenet +groups ‘comp.unix.questions’, ‘comp.std.internat’, +‘comp.software.international’, ‘comp.lang.c’, +‘comp.windows.x’, ‘comp.std.c’, ‘comp.answers’ +and ‘news.answers’. The home location of this document is: +

 
ftp://ftp.vlsivie.tuwien.ac.at/pub/8bit/ISO-programming
+
+ +

Patrick D'Cruze (‘pdcruze@li.org’) wrote a tutorial about NLS +matters, and Jochen Hein (‘Hein@student.tu-clausthal.de’) took +over the responsibility of maintaining it. It may be found as: +

 
ftp://sunsite.unc.edu/pub/Linux/utils/nls/catalogs/Incoming/...
+     ...locale-tutorial-0.8.txt.gz
+
+

This site is mirrored in: +

 
ftp://ftp.ibp.fr/pub/linux/sunsite/
+
+ +

A French version of the same tutorial should be findable at: +

 
ftp://ftp.ibp.fr/pub/linux/french/docs/
+
+

together with French translations of many Linux-related documents. +

+ + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_18.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_18.html new file mode 100644 index 0000000000000000000000000000000000000000..b0ed2c1d821da34fa2a06dea035e1d1d6ba1d930 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_18.html @@ -0,0 +1,846 @@ + + + + + +GNU gettext utilities: A. Language Codes + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

A. Language Codes

+ +

The ISO 639 standard defines two-letter codes for many languages, and +three-letter codes for more rarely used languages. +All abbreviations for languages used in the Translation Project should +come from this standard. +

+ + + + +

A.1 Usual Language Codes

+ +

For the commonly used languages, the ISO 639-1 standard defines two-letter +codes. +

+
+
‘aa’
+

Afar. +

+
‘ab’
+

Abkhazian. +

+
‘ae’
+

Avestan. +

+
‘af’
+

Afrikaans. +

+
‘ak’
+

Akan. +

+
‘am’
+

Amharic. +

+
‘an’
+

Aragonese. +

+
‘ar’
+

Arabic. +

+
‘as’
+

Assamese. +

+
‘av’
+

Avaric. +

+
‘ay’
+

Aymara. +

+
‘az’
+

Azerbaijani. +

+
‘ba’
+

Bashkir. +

+
‘be’
+

Belarusian. +

+
‘bg’
+

Bulgarian. +

+
‘bh’
+

Bihari languages. +

+
‘bi’
+

Bislama. +

+
‘bm’
+

Bambara. +

+
‘bn’
+

Bengali. +

+
‘bo’
+

Tibetan. +

+
‘br’
+

Breton. +

+
‘bs’
+

Bosnian. +

+
‘ca’
+

Catalan; Valencian. +

+
‘ce’
+

Chechen. +

+
‘ch’
+

Chamorro. +

+
‘co’
+

Corsican. +

+
‘cr’
+

Cree. +

+
‘cs’
+

Czech. +

+
‘cu’
+

Church Slavic; Old Slavonic; Church Slavonic; Old Bulgarian; Old Church Slavonic. +

+
‘cv’
+

Chuvash. +

+
‘cy’
+

Welsh. +

+
‘da’
+

Danish. +

+
‘de’
+

German. +

+
‘dv’
+

Divehi; Dhivehi; Maldivian. +

+
‘dz’
+

Dzongkha. +

+
‘ee’
+

Ewe. +

+
‘el’
+

Greek, Modern (1453-). +

+
‘en’
+

English. +

+
‘eo’
+

Esperanto. +

+
‘es’
+

Spanish; Castilian. +

+
‘et’
+

Estonian. +

+
‘eu’
+

Basque. +

+
‘fa’
+

Persian. +

+
‘ff’
+

Fulah. +

+
‘fi’
+

Finnish. +

+
‘fj’
+

Fijian. +

+
‘fo’
+

Faroese. +

+
‘fr’
+

French. +

+
‘fy’
+

Western Frisian. +

+
‘ga’
+

Irish. +

+
‘gd’
+

Gaelic; Scottish Gaelic. +

+
‘gl’
+

Galician. +

+
‘gn’
+

Guarani. +

+
‘gu’
+

Gujarati. +

+
‘gv’
+

Manx. +

+
‘ha’
+

Hausa. +

+
‘he’
+

Hebrew. +

+
‘hi’
+

Hindi. +

+
‘ho’
+

Hiri Motu. +

+
‘hr’
+

Croatian. +

+
‘ht’
+

Haitian; Haitian Creole. +

+
‘hu’
+

Hungarian. +

+
‘hy’
+

Armenian. +

+
‘hz’
+

Herero. +

+
‘ia’
+

Interlingua (International Auxiliary Language Association). +

+
‘id’
+

Indonesian. +

+
‘ie’
+

Interlingue; Occidental. +

+
‘ig’
+

Igbo. +

+
‘ii’
+

Sichuan Yi; Nuosu. +

+
‘ik’
+

Inupiak. +

+
‘io’
+

Ido. +

+
‘is’
+

Icelandic. +

+
‘it’
+

Italian. +

+
‘iu’
+

Inuktitut. +

+
‘ja’
+

Japanese. +

+
‘jv’
+

Javanese. +

+
‘ka’
+

Georgian. +

+
‘kg’
+

Kongo. +

+
‘ki’
+

Kikuyu; Gikuyu. +

+
‘kj’
+

Kuanyama; Kwanyama. +

+
‘kk’
+

Kazakh. +

+
‘kl’
+

Kalaallisut; Greenlandic. +

+
‘km’
+

Central Khmer. +

+
‘kn’
+

Kannada. +

+
‘ko’
+

Korean. +

+
‘kr’
+

Kanuri. +

+
‘ks’
+

Kashmiri. +

+
‘ku’
+

Kurdish. +

+
‘kv’
+

Komi. +

+
‘kw’
+

Cornish. +

+
‘ky’
+

Kirghiz; Kyrgyz. +

+
‘la’
+

Latin. +

+
‘lb’
+

Luxembourgish; Letzeburgesch. +

+
‘lg’
+

Ganda. +

+
‘li’
+

Limburgan; Limburger; Limburgish. +

+
‘ln’
+

Lingala. +

+
‘lo’
+

Lao. +

+
‘lt’
+

Lithuanian. +

+
‘lu’
+

Luba-Katanga. +

+
‘lv’
+

Latvian. +

+
‘mg’
+

Malagasy. +

+
‘mh’
+

Marshallese. +

+
‘mi’
+

Maori. +

+
‘mk’
+

Macedonian. +

+
‘ml’
+

Malayalam. +

+
‘mn’
+

Mongolian. +

+
‘mr’
+

Marathi. +

+
‘ms’
+

Malay. +

+
‘mt’
+

Maltese. +

+
‘my’
+

Burmese. +

+
‘na’
+

Nauru. +

+
‘nb’
+

Bokmål, Norwegian; Norwegian Bokmål. +

+
‘nd’
+

Ndebele, North; North Ndebele. +

+
‘ne’
+

Nepali. +

+
‘ng’
+

Ndonga. +

+
‘nl’
+

Dutch; Flemish. +

+
‘nn’
+

Norwegian Nynorsk; Nynorsk, Norwegian. +

+
‘no’
+

Norwegian. +

+
‘nr’
+

Ndebele, South; South Ndebele. +

+
‘nv’
+

Navajo; Navaho. +

+
‘ny’
+

Chichewa; Nyanja. +

+
‘oc’
+

Occitan (post 1500); Provençal. +

+
‘oj’
+

Ojibwa. +

+
‘om’
+

Oromo. +

+
‘or’
+

Oriya. +

+
‘os’
+

Ossetian; Ossetic. +

+
‘pa’
+

Panjabi; Punjabi. +

+
‘pi’
+

Pali. +

+
‘pl’
+

Polish. +

+
‘ps’
+

Pushto; Pashto. +

+
‘pt’
+

Portuguese. +

+
‘qu’
+

Quechua. +

+
‘rm’
+

Romansh. +

+
‘rn’
+

Rundi. +

+
‘ro’
+

Romanian; Moldavian; Moldovan. +

+
‘ru’
+

Russian. +

+
‘rw’
+

Kinyarwanda. +

+
‘sa’
+

Sanskrit. +

+
‘sc’
+

Sardinian. +

+
‘sd’
+

Sindhi. +

+
‘se’
+

Northern Sami. +

+
‘sg’
+

Sango. +

+
‘si’
+

Sinhala; Sinhalese. +

+
‘sk’
+

Slovak. +

+
‘sl’
+

Slovenian. +

+
‘sm’
+

Samoan. +

+
‘sn’
+

Shona. +

+
‘so’
+

Somali. +

+
‘sq’
+

Albanian. +

+
‘sr’
+

Serbian. +

+
‘ss’
+

Swati. +

+
‘st’
+

Sotho, Southern. +

+
‘su’
+

Sundanese. +

+
‘sv’
+

Swedish. +

+
‘sw’
+

Swahili. +

+
‘ta’
+

Tamil. +

+
‘te’
+

Telugu. +

+
‘tg’
+

Tajik. +

+
‘th’
+

Thai. +

+
‘ti’
+

Tigrinya. +

+
‘tk’
+

Turkmen. +

+
‘tl’
+

Tagalog. +

+
‘tn’
+

Tswana. +

+
‘to’
+

Tonga (Tonga Islands). +

+
‘tr’
+

Turkish. +

+
‘ts’
+

Tsonga. +

+
‘tt’
+

Tatar. +

+
‘tw’
+

Twi. +

+
‘ty’
+

Tahitian. +

+
‘ug’
+

Uighur; Uyghur. +

+
‘uk’
+

Ukrainian. +

+
‘ur’
+

Urdu. +

+
‘uz’
+

Uzbek. +

+
‘ve’
+

Venda. +

+
‘vi’
+

Vietnamese. +

+
‘vo’
+

Volapük. +

+
‘wa’
+

Walloon. +

+
‘wo’
+

Wolof. +

+
‘xh’
+

Xhosa. +

+
‘yi’
+

Yiddish. +

+
‘yo’
+

Yoruba. +

+
‘za’
+

Zhuang; Chuang. +

+
‘zh’
+

Chinese. +

+
‘zu’
+

Zulu. +

+
+ + + + +

A.2 Rare Language Codes

+ +

For rarely used languages, the ISO 639-2 standard defines three-letter +codes. Here is the current list, reduced to only living languages with at least +one million of speakers. +

+
+
‘ace’
+

Achinese. +

+
‘awa’
+

Awadhi. +

+
‘bal’
+

Baluchi. +

+
‘ban’
+

Balinese. +

+
‘bej’
+

Beja; Bedawiyet. +

+
‘bem’
+

Bemba. +

+
‘bho’
+

Bhojpuri. +

+
‘bik’
+

Bikol. +

+
‘bin’
+

Bini; Edo. +

+
‘bug’
+

Buginese. +

+
‘ceb’
+

Cebuano. +

+
‘din’
+

Dinka. +

+
‘doi’
+

Dogri. +

+
‘fil’
+

Filipino; Pilipino. +

+
‘fon’
+

Fon. +

+
‘gon’
+

Gondi. +

+
‘gsw’
+

Swiss German; Alemannic; Alsatian. +

+
‘hil’
+

Hiligaynon. +

+
‘hmn’
+

Hmong. +

+
‘ilo’
+

Iloko. +

+
‘kab’
+

Kabyle. +

+
‘kam’
+

Kamba. +

+
‘kbd’
+

Kabardian. +

+
‘kmb’
+

Kimbundu. +

+
‘kok’
+

Konkani. +

+
‘kru’
+

Kurukh. +

+
‘lua’
+

Luba-Lulua. +

+
‘luo’
+

Luo (Kenya and Tanzania). +

+
‘mad’
+

Madurese. +

+
‘mag’
+

Magahi. +

+
‘mai’
+

Maithili. +

+
‘mak’
+

Makasar. +

+
‘man’
+

Mandingo. +

+
‘men’
+

Mende. +

+
‘min’
+

Minangkabau. +

+
‘mni’
+

Manipuri. +

+
‘mos’
+

Mossi. +

+
‘mwr’
+

Marwari. +

+
‘nap’
+

Neapolitan. +

+
‘nso’
+

Pedi; Sepedi; Northern Sotho. +

+
‘nym’
+

Nyamwezi. +

+
‘nyn’
+

Nyankole. +

+
‘pag’
+

Pangasinan. +

+
‘pam’
+

Pampanga; Kapampangan. +

+
‘raj’
+

Rajasthani. +

+
‘sas’
+

Sasak. +

+
‘sat’
+

Santali. +

+
‘scn’
+

Sicilian. +

+
‘shn’
+

Shan. +

+
‘sid’
+

Sidamo. +

+
‘srr’
+

Serer. +

+
‘suk’
+

Sukuma. +

+
‘sus’
+

Susu. +

+
‘tem’
+

Timne. +

+
‘tiv’
+

Tiv. +

+
‘tum’
+

Tumbuka. +

+
‘umb’
+

Umbundu. +

+
‘wal’
+

Walamo. +

+
‘war’
+

Waray. +

+
‘yao’
+

Yao. +

+
+ + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_19.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_19.html new file mode 100644 index 0000000000000000000000000000000000000000..9ac0634e543c3b20a2cc4b2064954ea846cceb3b --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_19.html @@ -0,0 +1,839 @@ + + + + + +GNU gettext utilities: B. Country Codes + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

B. Country Codes

+ +

The ISO 3166 standard defines two character codes for many countries +and territories. All abbreviations for countries used in the Translation +Project should come from this standard. +

+
+
‘AD’
+

Andorra. +

+
‘AE’
+

United Arab Emirates. +

+
‘AF’
+

Afghanistan. +

+
‘AG’
+

Antigua and Barbuda. +

+
‘AI’
+

Anguilla. +

+
‘AL’
+

Albania. +

+
‘AM’
+

Armenia. +

+
‘AO’
+

Angola. +

+
‘AQ’
+

Antarctica. +

+
‘AR’
+

Argentina. +

+
‘AS’
+

American Samoa. +

+
‘AT’
+

Austria. +

+
‘AU’
+

Australia. +

+
‘AW’
+

Aruba. +

+
‘AX’
+

Aaland Islands. +

+
‘AZ’
+

Azerbaijan. +

+
‘BA’
+

Bosnia and Herzegovina. +

+
‘BB’
+

Barbados. +

+
‘BD’
+

Bangladesh. +

+
‘BE’
+

Belgium. +

+
‘BF’
+

Burkina Faso. +

+
‘BG’
+

Bulgaria. +

+
‘BH’
+

Bahrain. +

+
‘BI’
+

Burundi. +

+
‘BJ’
+

Benin. +

+
‘BL’
+

Saint Barthelemy. +

+
‘BM’
+

Bermuda. +

+
‘BN’
+

Brunei Darussalam. +

+
‘BO’
+

Bolivia, Plurinational State of. +

+
‘BQ’
+

Bonaire, Sint Eustatius and Saba. +

+
‘BR’
+

Brazil. +

+
‘BS’
+

Bahamas. +

+
‘BT’
+

Bhutan. +

+
‘BV’
+

Bouvet Island. +

+
‘BW’
+

Botswana. +

+
‘BY’
+

Belarus. +

+
‘BZ’
+

Belize. +

+
‘CA’
+

Canada. +

+
‘CC’
+

Cocos (Keeling) Islands. +

+
‘CD’
+

Congo, The Democratic Republic of the. +

+
‘CF’
+

Central African Republic. +

+
‘CG’
+

Congo. +

+
‘CH’
+

Switzerland. +

+
‘CI’
+

Côte d'Ivoire. +

+
‘CK’
+

Cook Islands. +

+
‘CL’
+

Chile. +

+
‘CM’
+

Cameroon. +

+
‘CN’
+

China. +

+
‘CO’
+

Colombia. +

+
‘CR’
+

Costa Rica. +

+
‘CU’
+

Cuba. +

+
‘CV’
+

Cape Verde. +

+
‘CW’
+

Curaçao. +

+
‘CX’
+

Christmas Island. +

+
‘CY’
+

Cyprus. +

+
‘CZ’
+

Czech Republic. +

+
‘DE’
+

Germany. +

+
‘DJ’
+

Djibouti. +

+
‘DK’
+

Denmark. +

+
‘DM’
+

Dominica. +

+
‘DO’
+

Dominican Republic. +

+
‘DZ’
+

Algeria. +

+
‘EC’
+

Ecuador. +

+
‘EE’
+

Estonia. +

+
‘EG’
+

Egypt. +

+
‘EH’
+

Western Sahara. +

+
‘ER’
+

Eritrea. +

+
‘ES’
+

Spain. +

+
‘ET’
+

Ethiopia. +

+
‘FI’
+

Finland. +

+
‘FJ’
+

Fiji. +

+
‘FK’
+

Falkland Islands (Malvinas). +

+
‘FM’
+

Micronesia, Federated States of. +

+
‘FO’
+

Faroe Islands. +

+
‘FR’
+

France. +

+
‘GA’
+

Gabon. +

+
‘GB’
+

United Kingdom. +

+
‘GD’
+

Grenada. +

+
‘GE’
+

Georgia. +

+
‘GF’
+

French Guiana. +

+
‘GG’
+

Guernsey. +

+
‘GH’
+

Ghana. +

+
‘GI’
+

Gibraltar. +

+
‘GL’
+

Greenland. +

+
‘GM’
+

Gambia. +

+
‘GN’
+

Guinea. +

+
‘GP’
+

Guadeloupe. +

+
‘GQ’
+

Equatorial Guinea. +

+
‘GR’
+

Greece. +

+
‘GS’
+

South Georgia and the South Sandwich Islands. +

+
‘GT’
+

Guatemala. +

+
‘GU’
+

Guam. +

+
‘GW’
+

Guinea-Bissau. +

+
‘GY’
+

Guyana. +

+
‘HK’
+

Hong Kong. +

+
‘HM’
+

Heard Island and McDonald Islands. +

+
‘HN’
+

Honduras. +

+
‘HR’
+

Croatia. +

+
‘HT’
+

Haiti. +

+
‘HU’
+

Hungary. +

+
‘ID’
+

Indonesia. +

+
‘IE’
+

Ireland. +

+
‘IL’
+

Israel. +

+
‘IM’
+

Isle of Man. +

+
‘IN’
+

India. +

+
‘IO’
+

British Indian Ocean Territory. +

+
‘IQ’
+

Iraq. +

+
‘IR’
+

Iran, Islamic Republic of. +

+
‘IS’
+

Iceland. +

+
‘IT’
+

Italy. +

+
‘JE’
+

Jersey. +

+
‘JM’
+

Jamaica. +

+
‘JO’
+

Jordan. +

+
‘JP’
+

Japan. +

+
‘KE’
+

Kenya. +

+
‘KG’
+

Kyrgyzstan. +

+
‘KH’
+

Cambodia. +

+
‘KI’
+

Kiribati. +

+
‘KM’
+

Comoros. +

+
‘KN’
+

Saint Kitts and Nevis. +

+
‘KP’
+

Korea, Democratic People's Republic of. +

+
‘KR’
+

Korea, Republic of. +

+
‘KW’
+

Kuwait. +

+
‘KY’
+

Cayman Islands. +

+
‘KZ’
+

Kazakhstan. +

+
‘LA’
+

Lao People's Democratic Republic. +

+
‘LB’
+

Lebanon. +

+
‘LC’
+

Saint Lucia. +

+
‘LI’
+

Liechtenstein. +

+
‘LK’
+

Sri Lanka. +

+
‘LR’
+

Liberia. +

+
‘LS’
+

Lesotho. +

+
‘LT’
+

Lithuania. +

+
‘LU’
+

Luxembourg. +

+
‘LV’
+

Latvia. +

+
‘LY’
+

Libya. +

+
‘MA’
+

Morocco. +

+
‘MC’
+

Monaco. +

+
‘MD’
+

Moldova, Republic of. +

+
‘ME’
+

Montenegro. +

+
‘MF’
+

Saint Martin (French part). +

+
‘MG’
+

Madagascar. +

+
‘MH’
+

Marshall Islands. +

+
‘MK’
+

North Macedonia. +

+
‘ML’
+

Mali. +

+
‘MM’
+

Myanmar. +

+
‘MN’
+

Mongolia. +

+
‘MO’
+

Macao. +

+
‘MP’
+

Northern Mariana Islands. +

+
‘MQ’
+

Martinique. +

+
‘MR’
+

Mauritania. +

+
‘MS’
+

Montserrat. +

+
‘MT’
+

Malta. +

+
‘MU’
+

Mauritius. +

+
‘MV’
+

Maldives. +

+
‘MW’
+

Malawi. +

+
‘MX’
+

Mexico. +

+
‘MY’
+

Malaysia. +

+
‘MZ’
+

Mozambique. +

+
‘NA’
+

Namibia. +

+
‘NC’
+

New Caledonia. +

+
‘NE’
+

Niger. +

+
‘NF’
+

Norfolk Island. +

+
‘NG’
+

Nigeria. +

+
‘NI’
+

Nicaragua. +

+
‘NL’
+

Netherlands. +

+
‘NO’
+

Norway. +

+
‘NP’
+

Nepal. +

+
‘NR’
+

Nauru. +

+
‘NU’
+

Niue. +

+
‘NZ’
+

New Zealand. +

+
‘OM’
+

Oman. +

+
‘PA’
+

Panama. +

+
‘PE’
+

Peru. +

+
‘PF’
+

French Polynesia. +

+
‘PG’
+

Papua New Guinea. +

+
‘PH’
+

Philippines. +

+
‘PK’
+

Pakistan. +

+
‘PL’
+

Poland. +

+
‘PM’
+

Saint Pierre and Miquelon. +

+
‘PN’
+

Pitcairn. +

+
‘PR’
+

Puerto Rico. +

+
‘PS’
+

Palestine, State of. +

+
‘PT’
+

Portugal. +

+
‘PW’
+

Palau. +

+
‘PY’
+

Paraguay. +

+
‘QA’
+

Qatar. +

+
‘RE’
+

Reunion. +

+
‘RO’
+

Romania. +

+
‘RS’
+

Serbia. +

+
‘RU’
+

Russian Federation. +

+
‘RW’
+

Rwanda. +

+
‘SA’
+

Saudi Arabia. +

+
‘SB’
+

Solomon Islands. +

+
‘SC’
+

Seychelles. +

+
‘SD’
+

Sudan. +

+
‘SE’
+

Sweden. +

+
‘SG’
+

Singapore. +

+
‘SH’
+

Saint Helena, Ascension and Tristan da Cunha. +

+
‘SI’
+

Slovenia. +

+
‘SJ’
+

Svalbard and Jan Mayen. +

+
‘SK’
+

Slovakia. +

+
‘SL’
+

Sierra Leone. +

+
‘SM’
+

San Marino. +

+
‘SN’
+

Senegal. +

+
‘SO’
+

Somalia. +

+
‘SR’
+

Suriname. +

+
‘SS’
+

South Sudan. +

+
‘ST’
+

Sao Tome and Principe. +

+
‘SV’
+

El Salvador. +

+
‘SX’
+

Sint Maarten (Dutch part). +

+
‘SY’
+

Syrian Arab Republic. +

+
‘SZ’
+

Swaziland. +

+
‘TC’
+

Turks and Caicos Islands. +

+
‘TD’
+

Chad. +

+
‘TF’
+

French Southern Territories. +

+
‘TG’
+

Togo. +

+
‘TH’
+

Thailand. +

+
‘TJ’
+

Tajikistan. +

+
‘TK’
+

Tokelau. +

+
‘TL’
+

Timor-Leste. +

+
‘TM’
+

Turkmenistan. +

+
‘TN’
+

Tunisia. +

+
‘TO’
+

Tonga. +

+
‘TR’
+

Türkiye. +

+
‘TT’
+

Trinidad and Tobago. +

+
‘TV’
+

Tuvalu. +

+
‘TW’
+

Taiwan, Province of China. +

+
‘TZ’
+

Tanzania, United Republic of. +

+
‘UA’
+

Ukraine. +

+
‘UG’
+

Uganda. +

+
‘UM’
+

United States Minor Outlying Islands. +

+
‘US’
+

United States. +

+
‘UY’
+

Uruguay. +

+
‘UZ’
+

Uzbekistan. +

+
‘VA’
+

Holy See (Vatican City State). +

+
‘VC’
+

Saint Vincent and the Grenadines. +

+
‘VE’
+

Venezuela, Bolivarian Republic of. +

+
‘VG’
+

Virgin Islands, British. +

+
‘VI’
+

Virgin Islands, U.S.. +

+
‘VN’
+

Viet Nam. +

+
‘VU’
+

Vanuatu. +

+
‘WF’
+

Wallis and Futuna. +

+
‘WS’
+

Samoa. +

+
‘YE’
+

Yemen. +

+
‘YT’
+

Mayotte. +

+
‘ZA’
+

South Africa. +

+
‘ZM’
+

Zambia. +

+
‘ZW’
+

Zimbabwe. +

+
+ + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_2.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_2.html new file mode 100644 index 0000000000000000000000000000000000000000..1368700d1ebcba7625a468fe68881e0a9a567aaa --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_2.html @@ -0,0 +1,403 @@ + + + + + +GNU gettext utilities: 2. The User's View + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

2. The User's View

+ +

Nowadays, when users log into a computer, they usually find that all +their programs show messages in their native language – at least for +users of languages with an active free software community, like French or +German; to a lesser extent for languages with a smaller participation in +free software and the GNU project, like Hindi and Filipino. +

+

How does this work? How can the user influence the language that is used +by the programs? This chapter will answer it. +

+ + + + +

2.1 Operating System Installation

+ +

The default language is often already specified during operating system +installation. When the operating system is installed, the installer +typically asks for the language used for the installation process and, +separately, for the language to use in the installed system. Some OS +installers only ask for the language once. +

+

This determines the system-wide default language for all users. But the +installers often give the possibility to install extra localizations for +additional languages. For example, the localizations of KDE (the K +Desktop Environment) and LibreOffice are often bundled separately, as one +installable package per language. +

+

At this point it is good to consider the intended use of the machine: If +it is a machine designated for personal use, additional localizations are +probably not necessary. If, however, the machine is in use in an +organization or company that has international relationships, one can +consider the needs of guest users. If you have a guest from abroad, for +a week, what could be his preferred locales? It may be worth installing +these additional localizations ahead of time, since they cost only a bit +of disk space at this point. +

+

The system-wide default language is the locale configuration that is used +when a new user account is created. But the user can have his own locale +configuration that is different from the one of the other users of the +same machine. He can specify it, typically after the first login, as +described in the next section. +

+ + + +

2.2 Setting the Locale Used by GUI Programs

+ +

The immediately available programs in a user's desktop come from a group +of programs called a “desktop environment”; it usually includes the window +manager, a web browser, a text editor, and more. The most common free +desktop environments are KDE, GNOME, and Xfce. +

+

The locale used by GUI programs of the desktop environment can be specified +in a configuration screen called “control center”, “language settings” +or “country settings”. +

+

Individual GUI programs that are not part of the desktop environment can +have their locale specified either in a settings panel, or through environment +variables. +

+

For some programs, it is possible to specify the locale through environment +variables, possibly even to a different locale than the desktop's locale. +This means, instead of starting a program through a menu or from the file +system, you can start it from the command-line, after having set some +environment variables. The environment variables can be those specified +in the next section (Setting the Locale through Environment Variables); for some versions of +KDE, however, the locale is specified through a variable KDE_LANG, +rather than LANG or LC_ALL. +

+ + + +

2.3 Setting the Locale through Environment Variables

+ +

As a user, if your language has been installed for this package, in the +simplest case, you only have to set the LANG environment variable +to the appropriate ‘ll_CC’ combination. For example, +let's suppose that you speak German and live in Germany. At the shell +prompt, merely execute +‘setenv LANG de_DE’ (in csh), +‘export LANG; LANG=de_DE’ (in sh) or +‘export LANG=de_DE’ (in bash). This can be done from your +‘.login’ or ‘.profile’ file, once and for all. +

+ + + + +

2.3.1 Locale Names

+ +

A locale name usually has the form ‘ll_CC’. Here +

+
    +
  • +‘ll’ is an ISO 639 two-letter language code. +For some languages, +a two-letter code does not exist, and a three-letter code is used instead. +
  • +‘CC’ is an ISO 3166 two-letter code of a country or territory. +
+ +

For example, +for German in Germany, ll is de, and CC is DE. +You find a list of the language codes in appendix Language Codes and +a list of the country codes in appendix Country Codes. +

+

You might think that the country code specification is redundant. But in +fact, some languages have dialects in different countries. For example, +‘de_AT’ is used for Austria, and ‘pt_BR’ for Brazil. The country +code serves to distinguish the dialects. +

+

Many locale names have an extended syntax +‘ll_CC.encoding’ that also specifies the character +encoding. These are in use because between 2000 and 2005, most users have +switched to locales in UTF-8 encoding. For example, the German locale on +glibc systems is nowadays ‘de_DE.UTF-8’. The older name ‘de_DE’ +still refers to the German locale as of 2000 that stores characters in +ISO-8859-1 encoding – a text encoding that cannot even accommodate the Euro +currency sign. +

+

Some locale names use ‘ll_CC@variant’ instead of +‘ll_CC’. The ‘@variant’ can denote any kind of +characteristics that is not already implied by the language ll and +the country CC. It can denote a particular monetary unit. For example, +on glibc systems, ‘de_DE@euro’ denotes the locale that uses the Euro +currency, in contrast to the older locale ‘de_DE’ which implies the use +of the currency before 2002. It can also denote a dialect of the language, +or the script used to write text (for example, ‘sr_RS@latin’ uses the +Latin script, whereas ‘sr_RS’ uses the Cyrillic script to write Serbian), +or the orthography rules, or similar. +

+

On other systems, some variations of this scheme are used, such as +‘ll’. You can get the list of locales supported by your system +for your language by running the command ‘locale -a | grep '^ll'’. +

+

There are also two special locales: +

    +
  • The locale called ‘C’.
    +When it is used, it disables all localization: in this locale, all programs +standardized by POSIX use English messages and an unspecified character +encoding (often US-ASCII, but sometimes also ISO-8859-1 or UTF-8, depending on +the operating system). +
  • The locale called ‘C.UTF-8’.
    +This locale exists on all modern GNU and Unix systems, +but not on all operating systems. +When it is used, it disables all localization as well. +It uses UTF-8 as character encoding. +
+ + + + +

2.3.2 Locale Environment Variables

+ +

A locale is composed of several locale categories, see Aspects in Native Language Support. +When a program looks up locale dependent values, it does this according to +the following environment variables, in priority order: +

+
    +
  1. +
  2. LANGUAGE + +
  3. LC_ALL + + + + + + +
  4. LC_xxx, according to selected locale category: +LC_CTYPE, LC_NUMERIC, LC_TIME, LC_COLLATE, +LC_MONETARY, LC_MESSAGES, ... + +
  5. LANG +
+ +

Variables whose value is set but is empty are ignored in this lookup. +

+

LANG is the normal environment variable for specifying a locale. +As a user, you normally set this variable (unless some of the other variables +have already been set by the system, in ‘/etc/profile’ or similar +initialization files). +

+

LC_CTYPE, LC_NUMERIC, LC_TIME, LC_COLLATE, +LC_MONETARY, LC_MESSAGES, and so on, are the environment +variables meant to override LANG and affecting a single locale +category only. For example, assume you are a Swedish user in Spain, and you +want your programs to handle numbers and dates according to Spanish +conventions, and only the messages should be in Swedish. Then you could +create a locale named ‘sv_ES’ or ‘sv_ES.UTF-8’ by use of the +localedef program. But it is simpler, and achieves the same effect, +to set the LANG variable to es_ES.UTF-8 and the +LC_MESSAGES variable to sv_SE.UTF-8; these two locales come +already preinstalled with the operating system. +

+

LC_ALL is an environment variable that overrides all of these. +It is typically used in scripts that run particular programs. For example, +configure scripts generated by GNU autoconf use LC_ALL to make +sure that the configuration tests don't operate in locale dependent ways. +

+

Some systems, unfortunately, set LC_ALL in ‘/etc/profile’ or in +similar initialization files. As a user, you therefore have to unset this +variable if you want to set LANG and optionally some of the other +LC_xxx variables. +

+

The LANGUAGE variable is described in the next subsection. +

+ + + +

2.3.3 Specifying a Priority List of Languages

+ +

Not all programs have translations for all languages. By default, an +English message is shown in place of a nonexistent translation. If you +understand other languages, you can set up a priority list of languages. +This is done through a different environment variable, called +LANGUAGE. GNU gettext gives preference to LANGUAGE +over LC_ALL and LANG for the purpose of message handling, +but you still need to have LANG (or LC_ALL) set to the primary +language; this is required by other parts of the system libraries. +For example, some Swedish users who would rather read translations in +German than English for when Swedish is not available, set LANGUAGE +to ‘sv:de’ while leaving LANG to ‘sv_SE’. +

+

Special advice for Norwegian users: The language code for Norwegian +bokmål changed from ‘no’ to ‘nb’ back in 2003. +Most of the message catalogs for this language are installed under ‘nb’. +But in order to also use the older ones installed under ‘no’, it is +recommended for Norwegian users to set LANGUAGE to ‘nb:no’. +

+

In the LANGUAGE environment variable, but not in the other +environment variables, ‘ll_CC’ combinations can be +abbreviated as ‘ll’ to denote the language's main dialect. +For example, ‘de’ is equivalent to ‘de_DE’ (German as spoken in +Germany), and ‘pt’ to ‘pt_PT’ (Portuguese as spoken in Portugal) +in this context. +

+

Special advice for Chinese users: +Users who want to see translations with Simplified Chinese characters +should set LANGUAGE to zh_CN, +whereas users who want to see translations with Traditional Chinese characters +should set LANGUAGE to zh_TW. +Chinese users in Singapore will want to set it to zh_SG:zh_CN, +Chinese users in Hong Kong will want to set it to zh_HK:zh_TW, +and Chinese users in Macao will want to set it to zh_MO:zh_TW. +Here zh_CN or zh_TW, respectively, acts as fallback, +since only few packages have translations +for zh_SG, zh_HK, or zh_MO. +

+

Note: The variable LANGUAGE is ignored if the locale is set to +‘C’. In other words, you have to first enable localization, by setting +LANG (or LC_ALL) to a value other than ‘C’, before you can +use a language priority list through the LANGUAGE variable. +

+ + + +

2.4 Obtaining good output in a Windows console

+ +

On Windows, consoles such as the one started by the cmd.exe +program do input and output in an encoding, called “OEM code page”, +that is different from the encoding that text-mode programs usually use, +called “ANSI code page”. (Note: This problem does not exist for +Cygwin consoles; these consoles do input and output in the UTF-8 +encoding.) As a workaround, you may request that the programs produce +output in this “OEM” encoding. To do so, set the environment variable +OUTPUT_CHARSET to the “OEM” encoding, through a command such as +

 
set OUTPUT_CHARSET=CP850
+
+

Note: This has an effect only on strings looked up in message catalogs; +other categories of text are usually not affected by this setting. +Note also that this environment variable also affects output sent to a +file or to a pipe; output to a file is most often expected to be in the +“ANSI” or in the UTF-8 encoding. +

+

Here are examples of the “ANSI” and “OEM” code pages: +

+ + + + + + +

Territories  

  ANSI encoding  

  OEM encoding +

Western Europe  

  CP1252  

  CP850 +

Slavic countries (Latin 2)  

  CP1250  

  CP852 +

Baltic countries  

  CP1257  

  CP775 +

Russia  

  CP1251  

  CP866 +

+ + + + +

2.5 Installing Translations for Particular Programs

+ +

Languages are not equally well supported in all packages using GNU +gettext, and more translations are added over time. Usually, you +use the translations that are shipped with the operating system +or with particular packages that you install afterwards. But you can also +install newer localizations directly. For doing this, you will need an +understanding where each localization file is stored on the file system. +

+ +

For programs that participate in the Translation Project, you can start +looking for translations here: +https://translationproject.org/team/index.html. +

+

For programs that are part of the KDE project, the starting point is: +https://l10n.kde.org/. +

+

For programs that are part of the GNOME project, the starting point is: +https://wiki.gnome.org/TranslationProject. +

+

For other programs, you may check whether the program's source code package +contains some ‘ll.po’ files; often they are kept together in a +directory called ‘po/’. Each ‘ll.po’ file contains the +message translations for the language whose abbreviation of ll. +

+ + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_20.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_20.html new file mode 100644 index 0000000000000000000000000000000000000000..1be4264f866c3d79fe975d0deadeffc875bc9b2e --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_20.html @@ -0,0 +1,1544 @@ + + + + + +GNU gettext utilities: C. Licenses + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

C. Licenses

+ +

The files of this package are covered by the licenses indicated in each +particular file or directory. Here is a summary: +

+
    +
  • +The libintl and libasprintf libraries are covered by the +GNU Lesser General Public License (LGPL). +A copy of the license is included in GNU LESSER GENERAL PUBLIC LICENSE. + +
  • +The executable programs of this package and the libgettextpo library +are covered by the GNU General Public License (GPL). +A copy of the license is included in GNU GENERAL PUBLIC LICENSE. + +
  • +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 included in GNU Free Documentation License. +
    +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 included in GNU GENERAL PUBLIC LICENSE. +
+ + + + + + +

C.1 GNU GENERAL PUBLIC LICENSE

+

Version 2, June 1991 +

+ +
 
Copyright © 1989, 1991 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 licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +License is intended to guarantee your freedom to share and change free +software—to make sure the software is free for all its users. This +General Public License applies to most of the Free Software +Foundation's software and to any other program whose authors commit to +using it. (Some other Free Software Foundation software is covered by +the GNU Lesser General Public License instead.) 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 +this service 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 make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the rights. +These restrictions translate to certain responsibilities for you if you +distribute copies of the software, or if you modify it. +

+

For example, if you distribute copies of such a program, whether +gratis or for a fee, you must give the recipients all the rights that +you have. 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. +

+

We protect your rights with two steps: (1) copyright the software, and +(2) offer you this license which gives you legal permission to copy, +distribute and/or modify the software. +

+

Also, for each author's protection and ours, we want to make certain +that everyone understands that there is no warranty for this free +software. If the software is modified by someone else and passed on, we +want its recipients to know that what they have is not the original, so +that any problems introduced by others will not reflect on the original +authors' reputations. +

+

Finally, any free program is threatened constantly by software +patents. We wish to avoid the danger that redistributors of a free +program will individually obtain patent licenses, in effect making the +program proprietary. To prevent this, we have made it clear that any +patent must be licensed for everyone's free use or not licensed at all. +

+

The precise terms and conditions for copying, distribution and +modification follow. +

+ +

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

+ +
    +
  1. +This License applies to any program or other work which contains +a notice placed by the copyright holder saying it may be distributed +under the terms of this General Public License. The “Program”, below, +refers to any such program or work, and a “work based on the Program” +means either the Program or any derivative work under copyright law: +that is to say, a work containing the Program or a portion of it, +either verbatim or with modifications and/or translated into another +language. (Hereinafter, translation is included without limitation in +the term “modification”.) Each licensee is addressed as “you”. + +

    Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running the Program is not restricted, and the output from the Program +is covered only if its contents constitute a work based on the +Program (independent of having been made by running the Program). +Whether that is true depends on what the Program does. +

    +
  2. +You may copy and distribute 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 and disclaimer of warranty; keep intact all the +notices that refer to this License and to the absence of any warranty; +and give any other recipients of the Program a copy of this License +along with the Program. + +

    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. +

    +
  3. +You may modify your copy or copies of the Program or any portion +of it, thus forming a work based on the Program, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + +
      +
    1. +You must cause the modified files to carry prominent notices +stating that you changed the files and the date of any change. + +
    2. +You must cause any work that you distribute or publish, that in +whole or in part contains or is derived from the Program or any +part thereof, to be licensed as a whole at no charge to all third +parties under the terms of this License. + +
    3. +If the modified program normally reads commands interactively +when run, you must cause it, when started running for such +interactive use in the most ordinary way, to print or display an +announcement including an appropriate copyright notice and a +notice that there is no warranty (or else, saying that you provide +a warranty) and that users may redistribute the program under +these conditions, and telling the user how to view a copy of this +License. (Exception: if the Program itself is interactive but +does not normally print such an announcement, your work based on +the Program is not required to print an announcement.) +
    + +

    These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Program, +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 Program, 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 Program. +

    +

    In addition, mere aggregation of another work not based on the Program +with the Program (or with a work based on the Program) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. +

    +
  4. +You may copy and distribute the Program (or a work based on it, +under Section 2) in object code or executable form under the terms of +Sections 1 and 2 above provided that you also do one of the following: + +
      +
    1. +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; or, + +
    2. +Accompany it with a written offer, valid for at least three +years, to give any third party, for a charge no more than your +cost of physically performing source distribution, a complete +machine-readable copy of the corresponding source code, to be +distributed under the terms of Sections 1 and 2 above on a medium +customarily used for software interchange; or, + +
    3. +Accompany it with the information you received as to the offer +to distribute corresponding source code. (This alternative is +allowed only for noncommercial distribution and only if you +received the program in object code or executable form with such +an offer, in accord with Subsection b above.) +
    + +

    The source code for a work means the preferred form of the work for +making modifications to it. For an executable work, 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 executable. However, as a +special exception, the source code 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. +

    +

    If distribution of executable or 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 counts as +distribution of the source code, even though third parties are not +compelled to copy the source along with the object code. +

    +
  5. +You may not copy, modify, sublicense, or distribute the Program +except as expressly provided under this License. Any attempt +otherwise to copy, modify, sublicense or distribute the Program 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. + +
  6. +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 Program or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Program (or any work based on the +Program), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Program or works based on it. + +
  7. +Each time you redistribute the Program (or any work based on the +Program), the recipient automatically receives a license from the +original licensor to copy, distribute or modify the Program 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 to +this License. + +
  8. +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 Program at all. For example, if a patent +license would not permit royalty-free redistribution of the Program 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 Program. + +

    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. +

    +
  9. +If the distribution and/or use of the Program is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Program 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. + +
  10. +The Free Software Foundation may publish revised and/or new versions +of the 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 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 Program does not specify a version number of +this License, you may choose any version ever published by the Free Software +Foundation. +

    +
  11. +If you wish to incorporate parts of the Program into other free +programs whose distribution conditions are different, 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. + + +
  12. +BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, 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. + +
  13. +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 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. +
+ + + + +

Appendix: 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 +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 program's name and a brief idea of what it does.
+Copyright (C) yyyy  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 2 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 is interactive, make it output a short notice like this +when it starts in an interactive mode: +

+
 
Gnomovision version 69, Copyright (C) year name of author
+Gnomovision 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, the +commands you use may be called something other than ‘show w’ and +‘show c’; they could even be mouse-clicks or menu items—whatever +suits your program. +

+

You should also get your employer (if you work as a programmer) or your +school, if any, to sign a “copyright disclaimer” for the program, if +necessary. Here is a sample; alter the names: +

+
 
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+`Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+signature of Moe Ghoul, 1 April 1989
+Moe Ghoul, President of Vice
+
+ +

This 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. + +

+ + +

C.2 GNU LESSER GENERAL PUBLIC LICENSE

+

Version 2.1, February 1999 +

+ +
 
Copyright © 1991, 1999 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.
+
+[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—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. +

+

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. +

+ +

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

+ +
    +
  1. +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. +

    +
  2. +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. +

    +
  3. +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: + +
      +
    1. +The modified work must itself be a software library. + +
    2. +You must cause the files modified to carry prominent notices +stating that you changed the files and the date of any change. + +
    3. +You must cause the whole of the work to be licensed at no +charge to all third parties under the terms of this License. + +
    4. +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. +

    +
  4. +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. + +

    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. +

    +
  5. +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. +

    +
  6. +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. +

    +
  7. +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: +

    +
      +
    1. +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.) + +
    2. +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. + +
    3. +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. + +
    4. +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. + +
    5. +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. +

    +
  8. +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: + +
      +
    1. +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. + +
    2. +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. +
    + +
  9. +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. + +
  10. +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. + +
  11. +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. + +
  12. +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. +

    +
  13. +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. + +
  14. +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. +

    +
  15. +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 +

    +
  16. +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. + +
  17. +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

+ + + +

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 an 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.1 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, see <https://www.gnu.org/licenses/>.
+
+ +

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 Moe Ghoul, 1 April 1990
+Moe Ghoul, President of Vice
+
+ +

That's all there is to it! + +

+ + +

C.3 GNU Free Documentation License

+

Version 1.3, 3 November 2008 +

+ +
 
Copyright © 2000, 2001, 2002, 2007, 2008 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.
+
+ +
    +
  1. +PREAMBLE + +

    The purpose of this License is to make a manual, textbook, or other +functional and useful document 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. +

    +
  2. +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 +ASCII without markup, Texinfo input format, LaTeX input +format, SGML or XML using a publicly available +DTD, and standard-conforming simple HTML, +PostScript or PDF designed for human modification. Examples +of transparent image formats include PNG, XCF and +JPG. Opaque formats include proprietary formats that can be +read and edited only by proprietary word processors, SGML or +XML for which the DTD and/or processing tools are +not generally available, and the machine-generated HTML, +PostScript or 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. +

    +

    The “publisher” means any person or entity that distributes copies +of the Document to the public. +

    +

    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. +

    +
  3. +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. +

    +
  4. +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. +

    +
  5. +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: +

    +
      +
    1. +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. + +
    2. +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. + +
    3. +State on the Title page the name of the publisher of the +Modified Version, as the publisher. + +
    4. +Preserve all the copyright notices of the Document. + +
    5. +Add an appropriate copyright notice for your modifications +adjacent to the other copyright notices. + +
    6. +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. + +
    7. +Preserve in that license notice the full lists of Invariant Sections +and required Cover Texts given in the Document's license notice. + +
    8. +Include an unaltered copy of this License. + +
    9. +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. + +
    10. +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. + +
    11. +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. + +
    12. +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. + +
    13. +Delete any section Entitled “Endorsements”. Such a section +may not be included in the Modified Version. + +
    14. +Do not retitle any existing section to be Entitled “Endorsements” or +to conflict in title with any Invariant Section. + +
    15. +Preserve any Warranty Disclaimers. +
    + +

    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. +

    +
  6. +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.” +

    +
  7. +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. +

    +
  8. +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. +

    +
  9. +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. +

    +
  10. +TERMINATION + +

    You may not copy, modify, sublicense, or distribute the Document +except as expressly provided under this License. Any attempt +otherwise to copy, modify, sublicense, or distribute it is void, and +will automatically terminate your rights under this License. +

    +

    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, receipt of a copy of some or all of the same material does +not give you any rights to use it. +

    +
  11. +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 +https://www.gnu.org/licenses/. +

    +

    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. If the Document +specifies that a proxy can decide which future versions of this +License can be used, that proxy's public statement of acceptance of a +version permanently authorizes you to choose that version for the +Document. +

    +
  12. +RELICENSING + +

    “Massive Multiauthor Collaboration Site” (or “MMC Site”) means any +World Wide Web server that publishes copyrightable works and also +provides prominent facilities for anybody to edit those works. A +public wiki that anybody can edit is an example of such a server. A +“Massive Multiauthor Collaboration” (or “MMC”) contained in the +site means any set of copyrightable works thus published on the MMC +site. +

    +

    “CC-BY-SA” means the Creative Commons Attribution-Share Alike 3.0 +license published by Creative Commons Corporation, a not-for-profit +corporation with a principal place of business in San Francisco, +California, as well as future copyleft versions of that license +published by that same organization. +

    +

    “Incorporate” means to publish or republish a Document, in whole or +in part, as part of another Document. +

    +

    An MMC is “eligible for relicensing” if it is licensed under this +License, and if all works that were first published under this License +somewhere other than this MMC, and subsequently incorporated in whole +or in part into the MMC, (1) had no cover texts or invariant sections, +and (2) were thus incorporated prior to November 1, 2008. +

    +

    The operator of an MMC Site may republish an MMC contained in the site +under CC-BY-SA on the same site at any time before August 1, 2009, +provided the MMC is eligible for relicensing. +

    +
+ + + +

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: +

+
 
  Copyright (C)  year  your name.
+  Permission is granted to copy, distribute and/or modify this document
+  under the terms of the GNU Free Documentation License, Version 1.3
+  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''.
+
+ +

If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, +replace the “with…Texts.” line with this: +

+
 
    with the Invariant Sections being list their titles, with
+    the Front-Cover Texts being list, and with the Back-Cover Texts
+    being list.
+
+ +

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. +

+ + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_21.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_21.html new file mode 100644 index 0000000000000000000000000000000000000000..e8794dd73cb16bceaa3190ef31fa953ecd913429 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_21.html @@ -0,0 +1,171 @@ + + + + + +GNU gettext utilities: Program Index + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

Program Index

+ +
Jump to:   A +   +B +   +E +   +G +   +M +   +N +   +Q +   +R +   +X +   +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Index Entry Section
A
autopoint13.6.4 Invoking the autopoint Program
B
boldquot9.4.5 Built-in filters
E
envsubst15.5.15.5 Invoking the envsubst program
G
gettext15.5.15 sh - Shell Script
gettext15.5.15.3 Invoking the gettext program
gettextize13.3 Invoking the gettextize Program
M
msgattrib9.8 Invoking the msgattrib Program
msgcat9.1 Invoking the msgcat Program
msgcmp9.7 Invoking the msgcmp Program
msgcomm9.6 Invoking the msgcomm Program
msgconv9.2 Invoking the msgconv Program
msgen9.9 Invoking the msgen Program
msgexec9.10 Invoking the msgexec Program
msgfilter9.4 Invoking the msgfilter Program
msgfmt10.1 Invoking the msgfmt Program
msggrep9.3 Invoking the msggrep Program
msginit6.1 Invoking the msginit Program
msgmerge7.1 Invoking the msgmerge Program
msgunfmt10.2 Invoking the msgunfmt Program
msguniq9.5 Invoking the msguniq Program
N
ngettext15.5.15 sh - Shell Script
ngettext15.5.15.4 Invoking the ngettext program
Q
quot9.4.5 Built-in filters
R
recode-sr-latin9.4.5 Built-in filters
X
xgettext5.1 Invoking the xgettext Program
+
Jump to:   A +   +B +   +E +   +G +   +M +   +N +   +Q +   +R +   +X +   +
+ + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_22.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_22.html new file mode 100644 index 0000000000000000000000000000000000000000..3ae23a100fab99d6324a178c8fafde71b1b57af6 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_22.html @@ -0,0 +1,733 @@ + + + + + +GNU gettext utilities: Option Index + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

Option Index

+ +
Jump to:   - +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Index Entry Section
-
-<, msgcat option9.1.3 Message selection
-<, msgcomm option9.6.3 Message selection
->, msgcat option9.1.3 Message selection
->, msgcomm option9.6.3 Message selection
-a, msgfmt option10.1.11 Output details
-a, xgettext option5.1.6 Language specific options
--add-comments, xgettext option5.1.5 Operation mode
--add-location, msgattrib option9.8.6 Output details
--add-location, msgcat option9.1.5 Output details
--add-location, msgcomm option9.6.5 Output details
--add-location, msgconv option9.2.5 Output details
--add-location, msgen option9.9.4 Output details
--add-location, msgfilter option9.4.7 Output details
--add-location, msggrep option9.3.5 Output details
--add-location, msgmerge option7.1.7 Output details
--add-location, msguniq option9.5.5 Output details
--add-location, xgettext option5.1.8 Output details
--alignment, msgfmt option10.1.11 Output details
--backup, msgmerge option7.1.4 Output file location in update mode
--boost, xgettext option5.1.6 Language specific options
--c++, xgettext option5.1.3 Choice of input file language
-c, gettext option15.5.15.3 Invoking the gettext program
-c, msgfmt option10.1.10 Input file interpretation
-C, msgfmt option10.1.10 Input file interpretation
-C, msggrep option9.3.3 Message selection
-C, msgmerge option7.1.1 Input file location
-c, ngettext option15.5.15.4 Invoking the ngettext program
-c, xgettext option5.1.5 Operation mode
-C, xgettext option5.1.3 Choice of input file language
--check, msgfmt option10.1.10 Input file interpretation
--check, xgettext option5.1.5 Operation mode
--check-accelerators, msgfmt option10.1.10 Input file interpretation
--check-compatibility, msgfmt option10.1.10 Input file interpretation
--check-domain, msgfmt option10.1.10 Input file interpretation
--check-format, msgfmt option10.1.10 Input file interpretation
--check-header, msgfmt option10.1.10 Input file interpretation
--clear-fuzzy, msgattrib option9.8.4 Attribute manipulation
--clear-obsolete, msgattrib option9.8.4 Attribute manipulation
--clear-previous, msgattrib option9.8.4 Attribute manipulation
--color, msgattrib option9.8.6 Output details
--color, msgcat option9.1.5 Output details
--color, msgcat option9.11.1 The --color option
--color, msgcomm option9.6.5 Output details
--color, msgconv option9.2.5 Output details
--color, msgen option9.9.4 Output details
--color, msgfilter option9.4.7 Output details
--color, msggrep option9.3.5 Output details
--color, msginit option6.1.4 Output details
--color, msgmerge option7.1.7 Output details
--color, msgunfmt option10.2.7 Output details
--color, msguniq option9.5.5 Output details
--color, xgettext option5.1.8 Output details
--comment, msggrep option9.3.3 Message selection
--compendium, msgmerge option7.1.1 Input file location
--context, gettext option15.5.15.3 Invoking the gettext program
--context, ngettext option15.5.15.4 Invoking the ngettext program
--copyright-holder, xgettext option5.1.8 Output details
--csharp, msgfmt option10.1.2 Operation mode
--csharp, msgunfmt option10.2.1 Operation mode
--csharp-resources, msgfmt option10.1.2 Operation mode
--csharp-resources, msgunfmt option10.2.1 Operation mode
-d, autopoint option13.6.4.1 Options
-d, gettext option15.5.15.3 Invoking the gettext program
-d, gettextize option13.3 Invoking the gettextize Program
-D, msgattrib option9.8.1 Input file location
-D, msgcat option9.1.1 Input file location
-D, msgcmp option9.7.1 Input file location
-D, msgcomm option9.6.1 Input file location
-D, msgconv option9.2.1 Input file location
-D, msgen option9.9.1 Input file location
-D, msgexec option9.10.1 Input file location
-D, msgfilter option9.4.1 Input file location
-D, msgfmt option10.1.1 Input file location
-d, msgfmt option10.1.4 Output file location in Java mode
-d, msgfmt option10.1.5 Output file location in C# mode
-d, msgfmt option10.1.6 Output file location in Tcl mode
-d, msgfmt option10.1.7 Desktop Entry mode options
-d, msgfmt option10.1.8 XML mode options
-D, msggrep option9.3.1 Input file location
-D, msgmerge option7.1.1 Input file location
-d, msgunfmt option10.2.4 Input file location in C# mode
-d, msgunfmt option10.2.5 Input file location in Tcl mode
-d, msguniq option9.5.3 Message selection
-D, msguniq option9.5.1 Input file location
-d, ngettext option15.5.15.4 Invoking the ngettext program
-D, xgettext option5.1.1 Input file location
-d, xgettext option5.1.2 Output file location
--debug, xgettext option5.1.6 Language specific options
--default-domain, xgettext option5.1.2 Output file location
--desktop, msgfmt option10.1.2 Operation mode
--directory, msgattrib option9.8.1 Input file location
--directory, msgcat option9.1.1 Input file location
--directory, msgcmp option9.7.1 Input file location
--directory, msgcomm option9.6.1 Input file location
--directory, msgconv option9.2.1 Input file location
--directory, msgen option9.9.1 Input file location
--directory, msgexec option9.10.1 Input file location
--directory, msgfilter option9.4.1 Input file location
--directory, msgfmt option10.1.1 Input file location
--directory, msggrep option9.3.1 Input file location
--directory, msgmerge option7.1.1 Input file location
--directory, msguniq option9.5.1 Input file location
--directory, xgettext option5.1.1 Input file location
--domain, gettext option15.5.15.3 Invoking the gettext program
--domain, msggrep option9.3.3 Message selection
--domain, ngettext option15.5.15.4 Invoking the ngettext program
--dry-run, autopoint option13.6.4.1 Options
--dry-run, gettextize option13.3 Invoking the gettextize Program
-E, gettext option15.5.15.3 Invoking the gettext program
-e, gettext option15.5.15.3 Invoking the gettext program
-e, msgfilter option9.4.4 Useful filter-options when the filter is ‘sed’
-e, msggrep option9.3.3 Message selection
-E, msggrep option9.3.3 Message selection
-E, ngettext option15.5.15.4 Invoking the ngettext program
-e, ngettext option15.5.15.4 Invoking the ngettext program
--empty, msgattrib option9.8.4 Attribute manipulation
--endianness, msgfmt option10.1.11 Output details
--exclude-file, xgettext option5.1.5 Operation mode
--expression, msgfilter option9.4.4 Useful filter-options when the filter is ‘sed’
--extended-regexp, msggrep option9.3.3 Message selection
--extract-all, xgettext option5.1.6 Language specific options
--extracted-comment, msggrep option9.3.3 Message selection
-f, autopoint option13.6.4.1 Options
-f, gettextize option13.3 Invoking the gettextize Program
-F, msgattrib option9.8.6 Output details
-F, msgcat option9.1.5 Output details
-f, msgcat option9.1.1 Input file location
-F, msgcomm option9.6.5 Output details
-f, msgcomm option9.6.1 Input file location
-F, msgconv option9.2.5 Output details
-F, msgen option9.9.4 Output details
-F, msgfilter option9.4.7 Output details
-f, msgfilter option9.4.4 Useful filter-options when the filter is ‘sed’
-f, msgfmt option10.1.10 Input file interpretation
-f, msggrep option9.3.3 Message selection
-F, msggrep option9.3.3 Message selection
-F, msgmerge option7.1.7 Output details
-F, msguniq option9.5.5 Output details
-F, xgettext option5.1.8 Output details
-f, xgettext option5.1.1 Input file location
--file, msgfilter option9.4.4 Useful filter-options when the filter is ‘sed’
--file, msggrep option9.3.3 Message selection
--files-from, msgcat option9.1.1 Input file location
--files-from, msgcomm option9.6.1 Input file location
--files-from, xgettext option5.1.1 Input file location
--fixed-strings, msggrep option9.3.3 Message selection
--flag, xgettext option5.1.6 Language specific options
--for-msgfmt, msgmerge option7.1.5 Operation modifiers
--force, autopoint option13.6.4.1 Options
--force, gettextize option13.3 Invoking the gettextize Program
--force-po, msgattrib option9.8.6 Output details
--force-po, msgcat option9.1.5 Output details
--force-po, msgcomm option9.6.5 Output details
--force-po, msgconv option9.2.5 Output details
--force-po, msgen option9.9.4 Output details
--force-po, msgfilter option9.4.7 Output details
--force-po, msggrep option9.3.5 Output details
--force-po, msgmerge option7.1.7 Output details
--force-po, msgunfmt option10.2.7 Output details
--force-po, msguniq option9.5.5 Output details
--force-po, xgettext option5.1.8 Output details
--foreign-user, xgettext option5.1.8 Output details
--from-code, xgettext option5.1.4 Input file interpretation
--fuzzy, msgattrib option9.8.4 Attribute manipulation
--generated, xgettext option5.1.8 Output details
-h, envsubst option15.5.15.5 Invoking the envsubst program
-h, gettext option15.5.15.3 Invoking the gettext program
-h, msgattrib option9.8.7 Informative output
-h, msgcat option9.1.6 Informative output
-h, msgcmp option9.7.4 Informative output
-h, msgcomm option9.6.6 Informative output
-h, msgconv option9.2.6 Informative output
-h, msgen option9.9.5 Informative output
-h, msgexec option9.10.3 Informative output
-h, msgfilter option9.4.8 Informative output
-h, msgfmt option10.1.12 Informative output
-h, msggrep option9.3.6 Informative output
-h, msginit option6.1.5 Informative output
-h, msgmerge option7.1.8 Informative output
-h, msgunfmt option10.2.8 Informative output
-h, msguniq option9.5.6 Informative output
-h, ngettext option15.5.15.4 Invoking the ngettext program
-h, xgettext option5.1.9 Informative output
--help, autopoint option13.6.4.2 Informative output
--help, envsubst option15.5.15.5 Invoking the envsubst program
--help, gettext option15.5.15.3 Invoking the gettext program
--help, gettextize option13.3 Invoking the gettextize Program
--help, msgattrib option9.8.7 Informative output
--help, msgcat option9.1.6 Informative output
--help, msgcmp option9.7.4 Informative output
--help, msgcomm option9.6.6 Informative output
--help, msgconv option9.2.6 Informative output
--help, msgen option9.9.5 Informative output
--help, msgexec option9.10.3 Informative output
--help, msgfilter option9.4.8 Informative output
--help, msgfmt option10.1.12 Informative output
--help, msggrep option9.3.6 Informative output
--help, msginit option6.1.5 Informative output
--help, msgmerge option7.1.8 Informative output
--help, msgunfmt option10.2.8 Informative output
--help, msguniq option9.5.6 Informative output
--help, ngettext option15.5.15.4 Invoking the ngettext program
--help, xgettext option5.1.9 Informative output
-i, msgattrib option9.8.6 Output details
-i, msgcat option9.1.5 Output details
-i, msgcomm option9.6.5 Output details
-i, msgconv option9.2.5 Output details
-i, msgen option9.9.4 Output details
-i, msgexec option9.10.1 Input file location
-i, msgfilter option9.4.1 Input file location
-i, msggrep option9.3.3 Message selection
-i, msginit option6.1.1 Input file location
-i, msgmerge option7.1.7 Output details
-i, msgunfmt option10.2.7 Output details
-i, msguniq option9.5.5 Output details
-i, xgettext option5.1.8 Output details
--ignore-case, msggrep option9.3.3 Message selection
--ignore-file, msgattrib option9.8.4 Attribute manipulation
--indent, msgattrib option9.8.6 Output details
--indent, msgcat option9.1.5 Output details
--indent, msgcomm option9.6.5 Output details
--indent, msgconv option9.2.5 Output details
--indent, msgen option9.9.4 Output details
--indent, msgfilter option9.4.7 Output details
--indent, msggrep option9.3.5 Output details
--indent, msgmerge option7.1.7 Output details
--indent, msgunfmt option10.2.7 Output details
--indent, msguniq option9.5.5 Output details
--indent, xgettext option5.1.8 Output details
--input, msgexec option9.10.1 Input file location
--input, msgfilter option9.4.1 Input file location
--input, msginit option6.1.1 Input file location
--invert-match, msggrep option9.3.3 Message selection
--its, xgettext option5.1.7 Options for XML input files
--itstool, xgettext option5.1.8 Output details
-j, msgfmt option10.1.2 Operation mode
-J, msggrep option9.3.3 Message selection
-j, msgunfmt option10.2.1 Operation mode
-j, xgettext option5.1.5 Operation mode
--java, msgfmt option10.1.2 Operation mode
--java, msgunfmt option10.2.1 Operation mode
--java2, msgfmt option10.1.2 Operation mode
--join-existing, xgettext option5.1.5 Operation mode
-k, msgfmt option10.1.7 Desktop Entry mode options
-K, msggrep option9.3.3 Message selection
-k, xgettext option5.1.6 Language specific options
--kde, xgettext option5.1.6 Language specific options
--keep-header, msgfilter option9.4.7 Output details
--keyword, msgfmt option10.1.7 Desktop Entry mode options
--keyword, xgettext option5.1.6 Language specific options
-l, msgfmt option10.1.4 Output file location in Java mode
-L, msgfmt option10.1.8 XML mode options
-l, msgfmt option10.1.5 Output file location in C# mode
-l, msgfmt option10.1.6 Output file location in Tcl mode
-l, msgfmt option10.1.7 Desktop Entry mode options
-l, msgfmt option10.1.8 XML mode options
-l, msginit option6.1.4 Output details
-l, msgunfmt option10.2.3 Input file location in Java mode
-l, msgunfmt option10.2.4 Input file location in C# mode
-l, msgunfmt option10.2.5 Input file location in Tcl mode
-L, xgettext option5.1.3 Choice of input file language
--lang, msgcat option9.1.5 Output details
--lang, msgen option9.9.4 Output details
--lang, msgmerge option7.1.7 Output details
--language, msgfmt option10.1.8 XML mode options
--language, xgettext option5.1.3 Choice of input file language
--less-than, msgcat option9.1.3 Message selection
--less-than, msgcomm option9.6.3 Message selection
--locale, msgfmt option10.1.4 Output file location in Java mode
--locale, msgfmt option10.1.5 Output file location in C# mode
--locale, msgfmt option10.1.6 Output file location in Tcl mode
--locale, msgfmt option10.1.7 Desktop Entry mode options
--locale, msgfmt option10.1.8 XML mode options
--locale, msginit option6.1.4 Output details
--locale, msgunfmt option10.2.3 Input file location in Java mode
--locale, msgunfmt option10.2.4 Input file location in C# mode
--locale, msgunfmt option10.2.5 Input file location in Tcl mode
--location, msggrep option9.3.3 Message selection
-m, msgcmp option9.7.2 Operation modifiers
-M, msggrep option9.3.3 Message selection
-m, msgmerge option7.1.5 Operation modifiers
-m, xgettext option5.1.8 Output details
-M, xgettext option5.1.8 Output details
--more-than, msgcat option9.1.3 Message selection
--more-than, msgcomm option9.6.3 Message selection
--msgctxt, msggrep option9.3.3 Message selection
--msgid, msggrep option9.3.3 Message selection
--msgid-bugs-address, xgettext option5.1.8 Output details
--msgstr, msggrep option9.3.3 Message selection
--msgstr-prefix, xgettext option5.1.8 Output details
--msgstr-suffix, xgettext option5.1.8 Output details
--multi-domain, msgcmp option9.7.2 Operation modifiers
--multi-domain, msgmerge option7.1.5 Operation modifiers
-n, gettext option15.5.15.3 Invoking the gettext program
-n, msgattrib option9.8.6 Output details
-n, msgcat option9.1.5 Output details
-N, msgcmp option9.7.2 Operation modifiers
-n, msgcomm option9.6.5 Output details
-n, msgfilter option9.4.4 Useful filter-options when the filter is ‘sed’
-N, msggrep option9.3.3 Message selection
-N, msgmerge option7.1.5 Operation modifiers
-n, msguniq option9.5.5 Output details
-n, xgettext option5.1.8 Output details
--newline, msgfilter option9.4.3 The filter
--newline, msgfilter option9.10 Invoking the msgexec Program
--no-changelog, gettextize option13.3 Invoking the gettextize Program
--no-convert, msgfmt option10.1.11 Output details
--no-fuzzy, msgattrib option9.8.3 Message selection
--no-fuzzy-matching, msgcmp option9.7.2 Operation modifiers
--no-fuzzy-matching, msgmerge option7.1.5 Operation modifiers
--no-git, xgettext option5.1.8 Output details
--no-hash, msgfmt option10.1.11 Output details
--no-location, msgattrib option9.8.6 Output details
--no-location, msgcat option9.1.5 Output details
--no-location, msgcomm option9.6.5 Output details
--no-location, msgconv option9.2.5 Output details
--no-location, msgen option9.9.4 Output details
--no-location, msgfilter option9.4.7 Output details
--no-location, msggrep option9.3.5 Output details
--no-location, msgmerge option7.1.7 Output details
--no-location, msguniq option9.5.5 Output details
--no-location, xgettext option5.1.8 Output details
--no-obsolete, msgattrib option9.8.3 Message selection
--no-redundancy, msgfmt option10.1.11 Output details
--no-translator, msginit option6.1.4 Output details
--no-wrap, msgattrib option9.8.6 Output details
--no-wrap, msgcat option9.1.5 Output details
--no-wrap, msgcomm option9.6.5 Output details
--no-wrap, msgconv option9.2.5 Output details
--no-wrap, msgen option9.9.4 Output details
--no-wrap, msgfilter option9.4.7 Output details
--no-wrap, msggrep option9.3.5 Output details
--no-wrap, msginit option6.1.4 Output details
--no-wrap, msgmerge option7.1.7 Output details
--no-wrap, msgunfmt option10.2.7 Output details
--no-wrap, msguniq option9.5.5 Output details
--no-wrap, xgettext option5.1.8 Output details
-o, msgattrib option9.8.2 Output file location
-o, msgcat option9.1.2 Output file location
-o, msgcomm option9.6.2 Output file location
-o, msgconv option9.2.2 Output file location
-o, msgen option9.9.2 Output file location
-o, msgfilter option9.4.2 Output file location
-o, msgfmt option10.1.3 Output file location
-o, msggrep option9.3.2 Output file location
-o, msginit option6.1.2 Output file location
-o, msgmerge option7.1.3 Output file location
-o, msgunfmt option10.2.6 Output file location
-o, msguniq option9.5.2 Output file location
-o, xgettext option5.1.2 Output file location
--obsolete, msgattrib option9.8.4 Attribute manipulation
--omit-header, msgcomm option9.6.5 Output details
--omit-header, xgettext option5.1.8 Output details
--only-file, msgattrib option9.8.4 Attribute manipulation
--only-fuzzy, msgattrib option9.8.3 Message selection
--only-obsolete, msgattrib option9.8.3 Message selection
--output, xgettext option5.1.2 Output file location
--output-dir, xgettext option5.1.2 Output file location
--output-file, msgattrib option9.8.2 Output file location
--output-file, msgcat option9.1.2 Output file location
--output-file, msgcomm option9.6.2 Output file location
--output-file, msgconv option9.2.2 Output file location
--output-file, msgen option9.9.2 Output file location
--output-file, msgfilter option9.4.2 Output file location
--output-file, msgfmt option10.1.3 Output file location
--output-file, msggrep option9.3.2 Output file location
--output-file, msginit option6.1.2 Output file location
--output-file, msgmerge option7.1.3 Output file location
--output-file, msgunfmt option10.2.6 Output file location
--output-file, msguniq option9.5.2 Output file location
-P, msgattrib option9.8.5 Input file syntax
-p, msgattrib option9.8.6 Output details
-p, msgcat option9.1.5 Output details
-P, msgcat option9.1.4 Input file syntax
-P, msgcmp option9.7.3 Input file syntax
-p, msgcomm option9.6.5 Output details
-P, msgcomm option9.6.4 Input file syntax
-p, msgconv option9.2.5 Output details
-P, msgconv option9.2.4 Input file syntax
-P, msgen option9.9.3 Input file syntax
-p, msgen option9.9.4 Output details
-P, msgexec option9.10.2 Input file syntax
-p, msgfilter option9.4.7 Output details
-P, msgfilter option9.4.6 Input file syntax
-P, msgfmt option10.1.9 Input file syntax
-P, msggrep option9.3.4 Input file syntax
-p, msggrep option9.3.5 Output details
-p, msginit option6.1.4 Output details
-P, msginit option6.1.3 Input file syntax
-P, msgmerge option7.1.6 Input file syntax
-p, msgmerge option7.1.7 Output details
-p, msgunfmt option10.2.7 Output details
-P, msguniq option9.5.4 Input file syntax
-p, msguniq option9.5.5 Output details
-p, xgettext option5.1.2 Output file location
--package-name, xgettext option5.1.8 Output details
--package-version, xgettext option5.1.8 Output details
--po-dir, gettextize option13.3 Invoking the gettextize Program
--previous, msgattrib option9.8.4 Attribute manipulation
--previous, msgmerge option7.1.5 Operation modifiers
--properties-input, msgattrib option9.8.5 Input file syntax
--properties-input, msgcat option9.1.4 Input file syntax
--properties-input, msgcmp option9.7.3 Input file syntax
--properties-input, msgcomm option9.6.4 Input file syntax
--properties-input, msgconv option9.2.4 Input file syntax
--properties-input, msgen option9.9.3 Input file syntax
--properties-input, msgexec option9.10.2 Input file syntax
--properties-input, msgfilter option9.4.6 Input file syntax
--properties-input, msgfmt option10.1.9 Input file syntax
--properties-input, msggrep option9.3.4 Input file syntax
--properties-input, msginit option6.1.3 Input file syntax
--properties-input, msgmerge option7.1.6 Input file syntax
--properties-input, msguniq option9.5.4 Input file syntax
--properties-output, msgattrib option9.8.6 Output details
--properties-output, msgcat option9.1.5 Output details
--properties-output, msgcomm option9.6.5 Output details
--properties-output, msgconv option9.2.5 Output details
--properties-output, msgen option9.9.4 Output details
--properties-output, msgfilter option9.4.7 Output details
--properties-output, msggrep option9.3.5 Output details
--properties-output, msginit option6.1.4 Output details
--properties-output, msgmerge option7.1.7 Output details
--properties-output, msgunfmt option10.2.7 Output details
--properties-output, msguniq option9.5.5 Output details
--properties-output, xgettext option5.1.8 Output details
-q, msgmerge option7.1.8 Informative output
--qt, msgfmt option10.1.2 Operation mode
--qt, xgettext option5.1.6 Language specific options
--quiet, msgfilter option9.4.4 Useful filter-options when the filter is ‘sed’
--quiet, msgmerge option7.1.8 Informative output
-r, msgfmt option10.1.4 Output file location in Java mode
-r, msgfmt option10.1.5 Output file location in C# mode
-r, msgunfmt option10.2.3 Input file location in Java mode
-r, msgunfmt option10.2.4 Input file location in C# mode
--reference, xgettext option5.1.8 Output details
--regexp=, msggrep option9.3.3 Message selection
--repeated, msguniq option9.5.3 Message selection
--replace-text, msgfmt option10.1.8 XML mode options
--resource, msgfmt option10.1.4 Output file location in Java mode
--resource, msgfmt option10.1.5 Output file location in C# mode
--resource, msgunfmt option10.2.3 Input file location in Java mode
--resource, msgunfmt option10.2.4 Input file location in C# mode
-s, msgattrib option9.8.6 Output details
-s, msgcat option9.1.5 Output details
-s, msgcomm option9.6.5 Output details
-s, msgconv option9.2.5 Output details
-s, msgen option9.9.4 Output details
-s, msgfilter option9.4.7 Output details
-s, msgmerge option7.1.7 Output details
-s, msgunfmt option10.2.7 Output details
-s, msguniq option9.5.5 Output details
-s, xgettext option5.1.8 Output details
--sentence-end, xgettext option5.1.5 Operation mode
--set-fuzzy, msgattrib option9.8.4 Attribute manipulation
--set-obsolete, msgattrib option9.8.4 Attribute manipulation
--silent, msgfilter option9.4.4 Useful filter-options when the filter is ‘sed’
--silent, msgmerge option7.1.8 Informative output
--sort-by-file, msgattrib option9.8.6 Output details
--sort-by-file, msgcat option9.1.5 Output details
--sort-by-file, msgcomm option9.6.5 Output details
--sort-by-file, msgconv option9.2.5 Output details
--sort-by-file, msgen option9.9.4 Output details
--sort-by-file, msgfilter option9.4.7 Output details
--sort-by-file, msggrep option9.3.5 Output details
--sort-by-file, msgmerge option7.1.7 Output details
--sort-by-file, msguniq option9.5.5 Output details
--sort-by-file, xgettext option5.1.8 Output details
--sort-output, msgattrib option9.8.6 Output details
--sort-output, msgcat option9.1.5 Output details
--sort-output, msgcomm option9.6.5 Output details
--sort-output, msgconv option9.2.5 Output details
--sort-output, msgen option9.9.4 Output details
--sort-output, msgfilter option9.4.7 Output details
--sort-output, msggrep option9.3.5 Output details
--sort-output, msgmerge option7.1.7 Output details
--sort-output, msgunfmt option10.2.7 Output details
--sort-output, msguniq option9.5.5 Output details
--sort-output, xgettext option5.1.8 Output details
--source, msgfmt option10.1.4 Output file location in Java mode
--statistics, msgfmt option10.1.12 Informative output
--strict, msgattrib option9.8.6 Output details
--strict, msgcat option9.1.5 Output details
--strict, msgcomm option9.6.5 Output details
--strict, msgconv option9.2.5 Output details
--strict, msgen option9.9.4 Output details
--strict, msgfilter option9.4.7 Output details
--strict, msgfmt option10.1.3 Output file location
--strict, msggrep option9.3.5 Output details
--strict, msgmerge option7.1.7 Output details
--strict, msgunfmt option10.2.7 Output details
--strict, msguniq option9.5.5 Output details
--strict, xgettext option5.1.8 Output details
--stringtable-input, msgattrib option9.8.5 Input file syntax
--stringtable-input, msgcat option9.1.4 Input file syntax
--stringtable-input, msgcmp option9.7.3 Input file syntax
--stringtable-input, msgcomm option9.6.4 Input file syntax
--stringtable-input, msgen option9.9.3 Input file syntax
--stringtable-input, msgexec option9.10.2 Input file syntax
--stringtable-input, msgfilter option9.4.6 Input file syntax
--stringtable-input, msgfmt option10.1.9 Input file syntax
--stringtable-input, msggrep option9.3.4 Input file syntax
--stringtable-input, msginit option6.1.3 Input file syntax
--stringtable-input, msgmerge option7.1.6 Input file syntax
--stringtable-input, msgonv option9.2.4 Input file syntax
--stringtable-input, msguniq option9.5.4 Input file syntax
--stringtable-output, msgattrib option9.8.6 Output details
--stringtable-output, msgcat option9.1.5 Output details
--stringtable-output, msgcomm option9.6.5 Output details
--stringtable-output, msgconv option9.2.5 Output details
--stringtable-output, msgen option9.9.4 Output details
--stringtable-output, msgfilter option9.4.7 Output details
--stringtable-output, msggrep option9.3.5 Output details
--stringtable-output, msginit option6.1.4 Output details
--stringtable-output, msgmerge option7.1.7 Output details
--stringtable-output, msgunfmt option10.2.7 Output details
--stringtable-output, msguniq option9.5.5 Output details
--stringtable-output, xgettext option5.1.8 Output details
--style, msgattrib option9.8.6 Output details
--style, msgcat option9.1.5 Output details
--style, msgcat option9.11.3 The --style option
--style, msgcomm option9.6.5 Output details
--style, msgconv option9.2.5 Output details
--style, msgen option9.9.4 Output details
--style, msgfilter option9.4.7 Output details
--style, msggrep option9.3.5 Output details
--style, msginit option6.1.4 Output details
--style, msgmerge option7.1.7 Output details
--style, msgunfmt option10.2.7 Output details
--style, msguniq option9.5.5 Output details
--style, xgettext option5.1.8 Output details
--suffix, msgmerge option7.1.4 Output file location in update mode
--symlink, gettextize option13.3 Invoking the gettextize Program
-t, msgcat option9.1.5 Output details
-t, msgconv option9.2.3 Conversion target
-T, msggrep option9.3.3 Message selection
-t, msguniq option9.5.5 Output details
-T, xgettext option5.1.6 Language specific options
--tag, xgettext option5.1.6 Language specific options
--tcl, msgfmt option10.1.2 Operation mode
--tcl, msgunfmt option10.2.1 Operation mode
--template, msgfmt option10.1.7 Desktop Entry mode options
--template, msgfmt option10.1.8 XML mode options
--to-code, msgcat option9.1.5 Output details
--to-code, msgconv option9.2.3 Conversion target
--to-code, msguniq option9.5.5 Output details
--translated, msgattrib option9.8.3 Message selection
--trigraphs, xgettext option5.1.6 Language specific options
-u, msgcat option9.1.3 Message selection
-u, msgcomm option9.6.3 Message selection
-U, msgmerge option7.1.2 Operation mode
-u, msguniq option9.5.3 Message selection
--unique, msgcat option9.1.3 Message selection
--unique, msgcomm option9.6.3 Message selection
--unique, msguniq option9.5.3 Message selection
--untranslated, msgattrib option9.8.3 Message selection
--update, msgmerge option7.1.2 Operation mode
--use-first, msgcat option9.1.5 Output details
--use-first, msguniq option9.5.5 Output details
--use-fuzzy, msgcmp option9.7.2 Operation modifiers
--use-fuzzy, msgfmt option10.1.10 Input file interpretation
--use-untranslated, msgcmp option9.7.2 Operation modifiers
-v, envsubst option15.5.15.5 Invoking the envsubst program
-V, envsubst option15.5.15.5 Invoking the envsubst program
-V, gettext option15.5.15.3 Invoking the gettext program
-V, msgattrib option9.8.7 Informative output
-V, msgcat option9.1.6 Informative output
-V, msgcmp option9.7.4 Informative output
-V, msgcomm option9.6.6 Informative output
-V, msgconv option9.2.6 Informative output
-V, msgen option9.9.5 Informative output
-V, msgexec option9.10.3 Informative output
-V, msgfilter option9.4.8 Informative output
-V, msgfmt option10.1.12 Informative output
-v, msgfmt option10.1.12 Informative output
-v, msggrep option9.3.3 Message selection
-V, msggrep option9.3.6 Informative output
-V, msginit option6.1.5 Informative output
-v, msgmerge option7.1.8 Informative output
-V, msgmerge option7.1.8 Informative output
-v, msgunfmt option10.2.8 Informative output
-V, msgunfmt option10.2.8 Informative output
-V, msguniq option9.5.6 Informative output
-V, ngettext option15.5.15.4 Invoking the ngettext program
-V, xgettext option5.1.9 Informative output
-v, xgettext option5.1.9 Informative output
--variables, envsubst option15.5.15.5 Invoking the envsubst program
--verbose, msgfmt option10.1.12 Informative output
--verbose, msgmerge option7.1.8 Informative output
--verbose, msgunfmt option10.2.8 Informative output
--verbose, xgettext option5.1.9 Informative output
--version, autopoint option13.6.4.2 Informative output
--version, envsubst option15.5.15.5 Invoking the envsubst program
--version, gettext option15.5.15.3 Invoking the gettext program
--version, gettextize option13.3 Invoking the gettextize Program
--version, msgattrib option9.8.7 Informative output
--version, msgcat option9.1.6 Informative output
--version, msgcmp option9.7.4 Informative output
--version, msgcomm option9.6.6 Informative output
--version, msgconv option9.2.6 Informative output
--version, msgen option9.9.5 Informative output
--version, msgexec option9.10.3 Informative output
--version, msgfilter option9.4.8 Informative output
--version, msgfmt option10.1.12 Informative output
--version, msggrep option9.3.6 Informative output
--version, msginit option6.1.5 Informative output
--version, msgmerge option7.1.8 Informative output
--version, msgunfmt option10.2.8 Informative output
--version, msguniq option9.5.6 Informative output
--version, ngettext option15.5.15.4 Invoking the ngettext program
--version, xgettext option5.1.9 Informative output
-w, msgattrib option9.8.6 Output details
-w, msgcat option9.1.5 Output details
-w, msgcomm option9.6.5 Output details
-w, msgconv option9.2.5 Output details
-w, msgen option9.9.4 Output details
-w, msgfilter option9.4.7 Output details
-w, msggrep option9.3.5 Output details
-w, msginit option6.1.4 Output details
-w, msgmerge option7.1.7 Output details
-w, msgunfmt option10.2.7 Output details
-w, msguniq option9.5.5 Output details
-w, xgettext option5.1.8 Output details
--width, msgattrib option9.8.6 Output details
--width, msgcat option9.1.5 Output details
--width, msgcomm option9.6.5 Output details
--width, msgconv option9.2.5 Output details
--width, msgen option9.9.4 Output details
--width, msgfilter option9.4.7 Output details
--width, msggrep option9.3.5 Output details
--width, msginit option6.1.4 Output details
--width, msgmerge option7.1.7 Output details
--width, msgunfmt option10.2.7 Output details
--width, msguniq option9.5.5 Output details
--width, xgettext option5.1.8 Output details
-X, msggrep option9.3.3 Message selection
-x, xgettext option5.1.5 Operation mode
--xml, msgfmt option10.1.2 Operation mode
+
Jump to:   - +
+ + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_23.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_23.html new file mode 100644 index 0000000000000000000000000000000000000000..63c37952c07b0b66b1f46a6a184c16fefc8c10f2 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_23.html @@ -0,0 +1,172 @@ + + + + + +GNU gettext utilities: Variable Index + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

Variable Index

+ +
Jump to:   G +   +L +   +M +   +O +   +P +   +T +   +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Index Entry Section
G
GETTEXT_LOG_UNTRANSLATED, environment variable12.5 Prioritizing messages: How to determine which messages to translate first
GETTEXTDATADIRS, environment variable5.1.7 Options for XML input files
GETTEXTDATADIRS, environment variable10.1.8 XML mode options
L
LANG, environment variable2.3.2 Locale Environment Variables
LANG, environment variable11.5 Being a gettext grok
LANGUAGE, environment variable2.3.2 Locale Environment Variables
LANGUAGE, environment variable11.5 Being a gettext grok
LANGUAGE, environment variable13.4.4 Extending ‘Makefile’ in ‘po/’
LC_ALL, environment variable2.3.2 Locale Environment Variables
LC_ALL, environment variable11.5 Being a gettext grok
LC_COLLATE, environment variable2.3.2 Locale Environment Variables
LC_COLLATE, environment variable11.5 Being a gettext grok
LC_CTYPE, environment variable2.3.2 Locale Environment Variables
LC_CTYPE, environment variable11.5 Being a gettext grok
LC_MESSAGES, environment variable2.3.2 Locale Environment Variables
LC_MESSAGES, environment variable11.5 Being a gettext grok
LC_MONETARY, environment variable2.3.2 Locale Environment Variables
LC_MONETARY, environment variable11.5 Being a gettext grok
LC_NUMERIC, environment variable2.3.2 Locale Environment Variables
LC_NUMERIC, environment variable11.5 Being a gettext grok
LC_TIME, environment variable2.3.2 Locale Environment Variables
LC_TIME, environment variable11.5 Being a gettext grok
LINGUAS, environment variable14. The Installer's and Distributor's View
M
MSGEXEC_LOCATION, environment variable9.10 Invoking the msgexec Program
MSGEXEC_MSGCTXT, environment variable9.10 Invoking the msgexec Program
MSGEXEC_MSGID, environment variable9.10 Invoking the msgexec Program
MSGEXEC_MSGID_PLURAL, environment variable9.10 Invoking the msgexec Program
MSGEXEC_PLURAL_FORM, environment variable9.10 Invoking the msgexec Program
MSGEXEC_PREV_MSGCTXT, environment variable9.10 Invoking the msgexec Program
MSGEXEC_PREV_MSGID, environment variable9.10 Invoking the msgexec Program
MSGEXEC_PREV_MSGID_PLURAL, environment variable9.10 Invoking the msgexec Program
MSGFILTER_LOCATION, environment variable9.4 Invoking the msgfilter Program
MSGFILTER_MSGCTXT, environment variable9.4 Invoking the msgfilter Program
MSGFILTER_MSGID, environment variable9.4 Invoking the msgfilter Program
MSGFILTER_MSGID_PLURAL, environment variable9.4 Invoking the msgfilter Program
MSGFILTER_PLURAL_FORM, environment variable9.4 Invoking the msgfilter Program
MSGFILTER_PREV_MSGCTXT, environment variable9.4 Invoking the msgfilter Program
MSGFILTER_PREV_MSGID, environment variable9.4 Invoking the msgfilter Program
MSGFILTER_PREV_MSGID_PLURAL, environment variable9.4 Invoking the msgfilter Program
O
OUTPUT_CHARSET, environment variable2.4 Obtaining good output in a Windows console
P
PO_STYLE, environment variable9.11.3 The --style option
T
TERM, environment variable9.11.2 The environment variable TERM
TEXTDOMAIN, environment variable15.5.15 sh - Shell Script
TEXTDOMAINDIR, environment variable15.5.15 sh - Shell Script
+
Jump to:   G +   +L +   +M +   +O +   +P +   +T +   +
+ + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_24.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_24.html new file mode 100644 index 0000000000000000000000000000000000000000..cfd81ab411cbfa2dc8b580d002af60dcda9a04e8 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_24.html @@ -0,0 +1,408 @@ + + + + + +GNU gettext utilities: PO Mode Index + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

PO Mode Index

+ +
Jump to:   # +   +, +   +. +   +0 +   +< +   += +   +> +   +? +   +_ +   +
+A +   +C +   +D +   +E +   +F +   +H +   +I +   +K +   +L +   +M +   +N +   +O +   +P +   +Q +   +R +   +S +   +T +   +U +   +V +   +W +   +X +   +Y +   +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Index Entry Section
#
#, PO Mode command8.7.10 Modifying Comments
#, PO Mode command8.7.10 Modifying Comments
,
,, PO Mode command4.5 Marking Translatable Strings
.
., PO Mode command8.7.3 Entry Positioning
., PO Mode command8.7.3 Entry Positioning
‘.emacs’ customizations8.7.1 Completing GNU gettext Installation
0
0, PO Mode command8.7.2 Main PO mode Commands
0, PO Mode command8.7.2 Main PO mode Commands
<
<, PO Mode command8.7.3 Entry Positioning
<, PO Mode command8.7.3 Entry Positioning
=
=, PO Mode command8.7.2 Main PO mode Commands
=, PO Mode command8.7.2 Main PO mode Commands
>
>, PO Mode command8.7.3 Entry Positioning
>, PO Mode command8.7.3 Entry Positioning
?
?, PO Mode command8.7.2 Main PO mode Commands
?, PO Mode command8.7.2 Main PO mode Commands
_
_, PO Mode command8.7.2 Main PO mode Commands
_, PO Mode command8.7.2 Main PO mode Commands
A
A, PO Mode command8.7.13 Consulting Auxiliary PO Files
a, PO Mode command8.7.13 Consulting Auxiliary PO Files
a, PO Mode command8.7.13 Consulting Auxiliary PO Files
A, PO Mode command8.7.13 Consulting Auxiliary PO Files
auxiliary PO file8.7.13 Consulting Auxiliary PO Files
C
C-c C-a, PO Mode command8.7.11 Details of Sub Edition
C-c C-a, PO Mode command8.7.11 Details of Sub Edition
C-c C-a, PO Mode command8.7.13 Consulting Auxiliary PO Files
C-c C-a, PO Mode command8.7.13 Consulting Auxiliary PO Files
C-c C-c, PO Mode command8.7.11 Details of Sub Edition
C-c C-c, PO Mode command8.7.11 Details of Sub Edition
C-c C-k, PO Mode command8.7.11 Details of Sub Edition
C-c C-k, PO Mode command8.7.11 Details of Sub Edition
C-j, PO Mode command8.7.9 Modifying Translations
C-j, PO Mode command8.7.9 Modifying Translations
commands8.7.2 Main PO mode Commands
comment out PO file entry8.7.8 Obsolete Entries
consulting program sources8.7.12 C Sources Context
consulting translations to other languages8.7.13 Consulting Auxiliary PO Files
current entry of a PO file8.7.3 Entry Positioning
cut and paste for translated strings8.7.9 Modifying Translations
D
DEL, PO Mode command8.7.6 Fuzzy Entries
DEL, PO Mode command8.7.8 Obsolete Entries
DEL, PO Mode command8.7.8 Obsolete Entries
E
editing comments8.7.10 Modifying Comments
editing multiple entries8.7.11 Details of Sub Edition
editing translations8.7.9 Modifying Translations
etags, using for marking strings4.5 Marking Translatable Strings
exiting PO subedit8.7.11 Details of Sub Edition
F
f, PO Mode command8.7.6 Fuzzy Entries
F, PO Mode command8.7.6 Fuzzy Entries
F, PO Mode command8.7.6 Fuzzy Entries
f, PO Mode command8.7.6 Fuzzy Entries
find source fragment for a PO file entry8.7.12 C Sources Context
H
h, PO Mode command8.7.2 Main PO mode Commands
h, PO Mode command8.7.2 Main PO mode Commands
I
installing PO mode8.7.1 Completing GNU gettext Installation
K
K, PO Mode command8.7.10 Modifying Comments
k, PO Mode command8.7.7 Untranslated Entries
K, PO Mode command8.7.10 Modifying Comments
k, PO Mode command8.7.7 Untranslated Entries
k, PO Mode command8.7.9 Modifying Translations
k, PO Mode command8.7.9 Modifying Translations
L
LFD, PO Mode command8.7.9 Modifying Translations
LFD, PO Mode command8.7.9 Modifying Translations
looking at the source to aid translation8.7.12 C Sources Context
M
m, PO Mode command8.7.3 Entry Positioning
m, PO Mode command8.7.3 Entry Positioning
M-,, PO Mode command4.5 Marking Translatable Strings
M-., PO Mode command4.5 Marking Translatable Strings
M-A, PO Mode command8.7.13 Consulting Auxiliary PO Files
M-A, PO Mode command8.7.13 Consulting Auxiliary PO Files
M-s, PO Mode command8.7.12 C Sources Context
M-S, PO Mode command8.7.12 C Sources Context
M-S, PO Mode command8.7.12 C Sources Context
M-s, PO Mode command8.7.12 C Sources Context
marking strings for translation4.5 Marking Translatable Strings
moving by fuzzy entries8.7.6 Fuzzy Entries
moving by obsolete entries8.7.8 Obsolete Entries
moving by translated entries8.7.5 Translated Entries
moving by untranslated entries8.7.7 Untranslated Entries
moving through a PO file8.7.3 Entry Positioning
N
n, PO Mode command8.7.3 Entry Positioning
n, PO Mode command8.7.3 Entry Positioning
next-error, stepping through PO file validation results8.7.2 Main PO mode Commands
normalize, PO Mode command8.7.13 Consulting Auxiliary PO Files
O
O, PO Mode command8.7.8 Obsolete Entries
o, PO Mode command8.7.8 Obsolete Entries
o, PO Mode command8.7.8 Obsolete Entries
O, PO Mode command8.7.8 Obsolete Entries
obsolete active entry8.7.8 Obsolete Entries
P
p, PO Mode command8.7.3 Entry Positioning
p, PO Mode command8.7.3 Entry Positioning
pending subedits8.7.11 Details of Sub Edition
po-auto-edit-with-msgid, PO Mode variable8.7.9 Modifying Translations
po-auto-fuzzy-on-edit, PO Mode variable8.7.5 Translated Entries
po-auto-select-on-unfuzzy, PO Mode variable8.7.6 Fuzzy Entries
po-confirm-and-quit, PO Mode command8.7.2 Main PO mode Commands
po-consider-as-auxiliary, PO Mode command8.7.13 Consulting Auxiliary PO Files
po-consider-source-path, PO Mode command8.7.12 C Sources Context
po-current-entry, PO Mode command8.7.3 Entry Positioning
po-cycle-auxiliary, PO Mode command8.7.13 Consulting Auxiliary PO Files
po-cycle-source-reference, PO Mode command8.7.12 C Sources Context
po-edit-comment, PO Mode command8.7.10 Modifying Comments
po-edit-msgstr, PO Mode command8.7.9 Modifying Translations
po-exchange-location, PO Mode command8.7.3 Entry Positioning
po-fade-out-entry, PO Mode command8.7.6 Fuzzy Entries
po-fade-out-entry, PO Mode command8.7.8 Obsolete Entries
po-first-entry, PO Mode command8.7.3 Entry Positioning
po-help, PO Mode command8.7.2 Main PO mode Commands
po-ignore-as-auxiliary, PO Mode command8.7.13 Consulting Auxiliary PO Files
po-ignore-source-path, PO Mode command8.7.12 C Sources Context
po-kill-comment, PO Mode command8.7.10 Modifying Comments
po-kill-msgstr, PO Mode command8.7.7 Untranslated Entries
po-kill-msgstr, PO Mode command8.7.9 Modifying Translations
po-kill-ring-save-comment, PO Mode command8.7.10 Modifying Comments
po-kill-ring-save-msgstr, PO Mode command8.7.9 Modifying Translations
po-last-entry, PO Mode command8.7.3 Entry Positioning
po-mark-translatable, PO Mode command4.5 Marking Translatable Strings
po-msgid-to-msgstr, PO Mode command8.7.9 Modifying Translations
po-next-entry, PO Mode command8.7.3 Entry Positioning
po-next-fuzzy-entry, PO Mode command8.7.6 Fuzzy Entries
po-next-obsolete-entry, PO Mode command8.7.8 Obsolete Entries
po-next-translated-entry, PO Mode command8.7.5 Translated Entries
po-next-untranslated-entry, PO Mode command8.7.7 Untranslated Entries
po-normalize, PO Mode command8.7.4 Normalizing Strings in Entries
po-other-window, PO Mode command8.7.2 Main PO mode Commands
po-pop-location, PO Mode command8.7.3 Entry Positioning
po-previous-entry, PO Mode command8.7.3 Entry Positioning
po-previous-fuzzy-entry, PO Mode command8.7.6 Fuzzy Entries
po-previous-obsolete-entry, PO Mode command8.7.8 Obsolete Entries
po-previous-translated-entry, PO Mode command8.7.5 Translated Entries
po-previous-untransted-entry, PO Mode command8.7.7 Untranslated Entries
po-push-location, PO Mode command8.7.3 Entry Positioning
po-quit, PO Mode command8.7.2 Main PO mode Commands
po-select-auxiliary, PO Mode command8.7.13 Consulting Auxiliary PO Files
po-select-mark-and-mark, PO Mode command4.5 Marking Translatable Strings
po-select-source-reference, PO Mode command8.7.12 C Sources Context
po-statistics, PO Mode command8.7.2 Main PO mode Commands
po-subedit-abort, PO Mode command8.7.11 Details of Sub Edition
po-subedit-cycle-auxiliary, PO Mode command8.7.11 Details of Sub Edition
po-subedit-exit, PO Mode command8.7.11 Details of Sub Edition
po-subedit-mode-hook, PO Mode variable8.7.10 Modifying Comments
po-tags-search, PO Mode command4.5 Marking Translatable Strings
po-undo, PO Mode command8.7.2 Main PO mode Commands
po-unfuzzy, PO Mode command8.7.6 Fuzzy Entries
po-validate, PO Mode command8.7.2 Main PO mode Commands
po-yank-comment, PO Mode command8.7.10 Modifying Comments
po-yank-msgstr, PO Mode command8.7.9 Modifying Translations
+
Jump to:   # +   +, +   +. +   +0 +   +< +   += +   +> +   +? +   +_ +   +
+A +   +C +   +D +   +E +   +F +   +H +   +I +   +K +   +L +   +M +   +N +   +O +   +P +   +Q +   +R +   +S +   +T +   +U +   +V +   +W +   +X +   +Y +   +
+ + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_25.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_25.html new file mode 100644 index 0000000000000000000000000000000000000000..3c3f544bddd3c3570d71724c02dabbc1f3641031 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_25.html @@ -0,0 +1,275 @@ + + + + + +GNU gettext utilities: PO Mode Index: Q – Y + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ +

PO Mode Index: Q – Y

+
Jump to:   # +   +, +   +. +   +0 +   +< +   += +   +> +   +? +   +_ +   +
+A +   +C +   +D +   +E +   +F +   +H +   +I +   +K +   +L +   +M +   +N +   +O +   +P +   +Q +   +R +   +S +   +T +   +U +   +V +   +W +   +X +   +Y +   +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Index Entry Section
Q
q, PO Mode command8.7.2 Main PO mode Commands
Q, PO Mode command8.7.2 Main PO mode Commands
Q, PO Mode command8.7.2 Main PO mode Commands
q, PO Mode command8.7.2 Main PO mode Commands
R
r, PO Mode command8.7.3 Entry Positioning
r, PO Mode command8.7.3 Entry Positioning
RET, PO Mode command8.7.9 Modifying Translations
RET, PO Mode command8.7.9 Modifying Translations
S
S, PO Mode command8.7.12 C Sources Context
s, PO Mode command8.7.12 C Sources Context
s, PO Mode command8.7.12 C Sources Context
S, PO Mode command8.7.12 C Sources Context
starting a string translation8.7.9 Modifying Translations
string normalization in entries8.7.4 Normalizing Strings in Entries
subedit minor mode8.7.11 Details of Sub Edition
T
T, PO Mode command8.7.5 Translated Entries
t, PO Mode command8.7.5 Translated Entries
t, PO Mode command8.7.5 Translated Entries
T, PO Mode command8.7.5 Translated Entries
TAB, PO Mode command8.7.6 Fuzzy Entries
TAB, PO Mode command8.7.6 Fuzzy Entries
‘TAGS’, and marking translatable strings4.5 Marking Translatable Strings
U
u, PO Mode command8.7.7 Untranslated Entries
U, PO Mode command8.7.7 Untranslated Entries
U, PO Mode command8.7.7 Untranslated Entries
u, PO Mode command8.7.7 Untranslated Entries
use the source, Luke8.7.12 C Sources Context
using obsolete translations to make new entries8.7.9 Modifying Translations
using translation compendia8.9 Using Translation Compendia
V
V, PO Mode command8.7.2 Main PO mode Commands
V, PO Mode command8.7.2 Main PO mode Commands
W
W, PO Mode command8.7.10 Modifying Comments
w, PO Mode command8.7.9 Modifying Translations
W, PO Mode command8.7.10 Modifying Comments
w, PO Mode command8.7.9 Modifying Translations
X
x, PO Mode command8.7.3 Entry Positioning
x, PO Mode command8.7.3 Entry Positioning
Y
y, PO Mode command8.7.9 Modifying Translations
Y, PO Mode command8.7.10 Modifying Comments
Y, PO Mode command8.7.10 Modifying Comments
y, PO Mode command8.7.9 Modifying Translations
+
Jump to:   # +   +, +   +. +   +0 +   +< +   += +   +> +   +? +   +_ +   +
+A +   +C +   +D +   +E +   +F +   +H +   +I +   +K +   +L +   +M +   +N +   +O +   +P +   +Q +   +R +   +S +   +T +   +U +   +V +   +W +   +X +   +Y +   +
+ + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_26.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_26.html new file mode 100644 index 0000000000000000000000000000000000000000..c03e0419a431cc485492920435d34858ce663794 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_26.html @@ -0,0 +1,104 @@ + + + + + +GNU gettext utilities: Autoconf Macro Index + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

Autoconf Macro Index

+ +
Jump to:   A +   +
+ + + + + + + + + + + +
Index Entry Section
A
AM_GNU_GETTEXT13.5.1 AM_GNU_GETTEXT in ‘gettext.m4’
AM_GNU_GETTEXT_NEED13.5.3 AM_GNU_GETTEXT_NEED in ‘gettext.m4’
AM_GNU_GETTEXT_VERSION13.5.2 AM_GNU_GETTEXT_VERSION in ‘gettext.m4’
AM_ICONV13.5.6 AM_ICONV in ‘iconv.m4’
AM_PO_SUBDIRS13.5.4 AM_PO_SUBDIRS in ‘po.m4’
AM_XGETTEXT_OPTION13.5.5 AM_XGETTEXT_OPTION in ‘po.m4’
+
Jump to:   A +   +
+ + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_27.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_27.html new file mode 100644 index 0000000000000000000000000000000000000000..6b60aeba5e07faf6bf118740c84a16c85d05c3cf --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_27.html @@ -0,0 +1,313 @@ + + + + + +GNU gettext utilities: General Index + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

General Index

+ +
Jump to:   _ +   +
+A +   +B +   +C +   +D +   +E +   +F +   +G +   +H +   +I +   +J +   +K +   +L +   +M +   +N +   +O +   +P +   +Q +   +R +   +S +   +T +   +U +   +V +   +W +   +X +   +Y +   +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Index Entry Section
_
_, a macro to mark strings for translation4.4 How Marks Appear in Sources
_nl_msg_cat_cntr11.5 Being a gettext grok
A
‘ABOUT-NLS’ file2.5 Installing Translations for Particular Programs
‘ABOUT-NLS’ file17.2 Notes on the Free Translation Project
accumulating translations8.9.1.1 Concatenate PO Files
‘aclocal.m4’ file13.4.8 ‘aclocal.m4’ at top level
adding keywords, xgettext5.1.6 Language specific options
ambiguities4.3.1 Decent English style
ANSI encoding2.4 Obtaining good output in a Windows console
apply a filter to translations9.4 Invoking the msgfilter Program
apply command to all translations in a catalog9.10 Invoking the msgexec Program
Arabic digits15.3.1 C Format Strings
attribute manipulation9.8 Invoking the msgattrib Program
attribute, fuzzy8.7.6 Fuzzy Entries
attributes of a PO file entry8.7.6 Fuzzy Entries
attributes, manipulating9. Manipulating PO Files
autoconf macros for gettext13.5 Autoconf macros for use in ‘configure.ac’
autopoint program, usage13.6.4 Invoking the autopoint Program
auxiliary PO file8.7.13 Consulting Auxiliary PO Files
available translations2.5 Installing Translations for Particular Programs
awk15.5.17 GNU awk
awk, string concatenationString concatenation operator
awk-format flag3. The Format of PO Files
B
backup old file, and msgmerge program7.1.4 Output file location in update mode
bash15.5.16 bash - Bourne-Again Shell Script
bibliography17.3 Related Readings
big picture1.5 Overview of GNU gettext
bind_textdomain_codeset11.2.4 How to specify the output character set gettext uses
Boost format strings5.1.6 Language specific options
boost-format flag3. The Format of PO Files
bug report address1. Introduction
C
C and C-like languages15.5.1 C, C++, Objective C
C trigraphs5.1.6 Language specific options
C#15.5.4 C#
C# mode, and msgfmt program10.1.2 Operation mode
C# mode, and msgunfmt program10.2.1 Operation mode
C# resources mode, and msgfmt program10.1.2 Operation mode
C# resources mode, and msgunfmt program10.2.1 Operation mode
C#, string concatenationString concatenation operator
C#, strings with embedded expressionsStrings with embedded expressions
c++-format flag3. The Format of PO Files
c-format flag3. The Format of PO Files
c-format, and xgettext4.7 Special Comments preceding Keywords
catalog encoding and msgexec output9.10 Invoking the msgexec Program
catclose, a catgets function11.1.1 The Interface
catgets, a catgets function11.1.1 The Interface
catgets, X/Open specification11.1 About catgets
catopen, a catgets function11.1.1 The Interface
character encoding1.3 Aspects in Native Language Support
charset conversion at runtime11.2.4 How to specify the output character set gettext uses
charset of PO files6.2 Filling in the Header Entry
check format strings10.1.10 Input file interpretation
checking of translations9. Manipulating PO Files
clisp15.5.8 GNU clisp - Common Lisp
clisp C sources15.5.9 GNU clisp C sources
codeset1.3 Aspects in Native Language Support
combining two PO files9. Manipulating PO Files
combining two POT files5.2 Combining PO Template Files
comments in PO files3. The Format of PO Files
comments, automatic3. The Format of PO Files
comments, extracted3. The Format of PO Files
comments, translator3. The Format of PO Files
Common Lisp15.5.8 GNU clisp - Common Lisp
compare PO files9.7 Invoking the msgcmp Program
comparison of interfaces11.3 Comparing the Two Interfaces
compatibility with X/Open msgfmt10.1.10 Input file interpretation
compendium8.9 Using Translation Compendia
compendium, creating8.9.1 Creating Compendia
concatenate PO files9.1 Invoking the msgcat Program
concatenating PO files into a compendium8.9.1.1 Concatenate PO Files
concatenation of strings4.3.4 No string concatenation
‘config.h.in’ file13.4.9 ‘config.h.in’ at top level
context11.2.5 Using contexts for solving ambiguities
context, argument specification in xgettext5.1.6 Language specific options
context, in MO files10.3 The Format of GNU MO Files
context, in PO files3. The Format of PO Files
control characters4.3.7 No unusual markup
convert binary message catalog into PO file10.2 Invoking the msgunfmt Program
convert translations to a different encoding9.2 Invoking the msgconv Program
converting a package to use gettext13.2 Prerequisite Works
country codesB. Country Codes
create new PO file6.1 Invoking the msginit Program
creating a new PO file6. Creating a New PO File
creating compendia8.9.1 Creating Compendia
csharp-format flag3. The Format of PO Files
currency symbols1.3 Aspects in Native Language Support
D
D15.5.21 D
D, string concatenationString concatenation operator
D, strings with embedded expressionsStrings with embedded expressions
d-format flag3. The Format of PO Files
date format1.3 Aspects in Native Language Support
dcngettext11.2.6 Additional functions for plural forms
dcpgettext11.2.5 Using contexts for solving ambiguities
dcpgettext_expr11.2.5 Using contexts for solving ambiguities
debugging messages marked as format strings5.1.6 Language specific options
Desktop Entry mode, and msgfmt program10.1.2 Operation mode
dialect9. Manipulating PO Files
disabling NLS13.4.12 ‘gettext.h’ in ‘lib/’
distribution tarball13.7 Creating a Distribution Tarball
dngettext11.2.6 Additional functions for plural forms
dollar substitution15.5.15.5 Invoking the envsubst program
domain ambiguities11.2.2 Solving Ambiguities
dpgettext11.2.5 Using contexts for solving ambiguities
dpgettext_expr11.2.5 Using contexts for solving ambiguities
duplicate elimination9. Manipulating PO Files
duplicate removal9.5 Invoking the msguniq Program
+
Jump to:   _ +   +
+A +   +B +   +C +   +D +   +E +   +F +   +G +   +H +   +I +   +J +   +K +   +L +   +M +   +N +   +O +   +P +   +Q +   +R +   +S +   +T +   +U +   +V +   +W +   +X +   +Y +   +
+ + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_28.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_28.html new file mode 100644 index 0000000000000000000000000000000000000000..705fc6cad6f0ccabcae77b5c1a68e2eef95f0190 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_28.html @@ -0,0 +1,354 @@ + + + + + +GNU gettext utilities: General Index: E – L + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ +

General Index: E – L

+
Jump to:   _ +   +
+A +   +B +   +C +   +D +   +E +   +F +   +G +   +H +   +I +   +J +   +K +   +L +   +M +   +N +   +O +   +P +   +Q +   +R +   +S +   +T +   +U +   +V +   +W +   +X +   +Y +   +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Index Entry Section
E
editing comments in PO files8.7.10 Modifying Comments
Editing PO Files8. Editing PO Files
editing translations8.7.9 Modifying Translations
elisp-format flag3. The Format of PO Files
Emacs Lisp15.5.10 Emacs Lisp
Emacs PO Mode8.7 Emacs's PO File Editor
encoding1.3 Aspects in Native Language Support
encoding conversion9. Manipulating PO Files
encoding conversion at runtime11.2.4 How to specify the output character set gettext uses
encoding for your language6.2 Filling in the Header Entry
encoding in MO files10.3 The Format of GNU MO Files
encoding list6.2 Filling in the Header Entry
encoding of PO files6.2 Filling in the Header Entry
environment variables15.5.15.5 Invoking the envsubst program
envsubst program, usage15.5.15.5 Invoking the envsubst program
eval_gettext function, usage15.5.15.6 Invoking the eval_gettext function
eval_ngettext function, usage15.5.15.7 Invoking the eval_ngettext function
eval_npgettext function, usage15.5.15.9 Invoking the eval_npgettext function
eval_pgettext function, usage15.5.15.8 Invoking the eval_pgettext function
evolution of packages1.5 Overview of GNU gettext
extracting parts of a PO file into a compendium8.9.1.2 Extract a Message Subset from a PO File
F
FDL, GNU Free Documentation LicenseC.3 GNU Free Documentation License
file format, ‘.mo’10.3 The Format of GNU MO Files
file format, ‘.po’3. The Format of PO Files
files, ‘.po’ and ‘.mo’1.4 Files Conveying Translations
files, ‘.pot’1.5 Overview of GNU gettext
filter messages according to attributes9.8 Invoking the msgattrib Program
find common messages9.6 Invoking the msgcomm Program
force use of fuzzy entries10.1.10 Input file interpretation
format strings4.7 Special Comments preceding Keywords
Free Pascal15.5.19 Pascal - Free Pascal Compiler
function attribute, __format__5.1.6 Language specific options
function attribute, __format_arg__5.1.6 Language specific options
fuzzy entries8.7.6 Fuzzy Entries
fuzzy flag3. The Format of PO Files
G
gawk15.5.17 GNU awk
gcc-internal-format flag3. The Format of PO Files
GCC-source15.5.29 GNU Compiler Collection sources
generate binary message catalog from PO file10.1 Invoking the msgfmt Program
generate translation catalog in English9.9 Invoking the msgen Program
gettext files13.4 Files You Must Create or Alter
gettext installation8.7.1 Completing GNU gettext Installation
gettext interface11.2.1 The Interface
gettext program, usage15.5.15.3 Invoking the gettext program
gettext vs catgets11.3 Comparing the Two Interfaces
gettext, a programmer's view11.2 About gettext
‘gettext.h’ file13.4.12 ‘gettext.h’ in ‘lib/’
gettextize program, usage13.3 Invoking the gettextize Program
gfc-internal-format flag3. The Format of PO Files
GNOME PO file editor8.3 GNOME's PO File Editor
Go15.5.13 Go
Go, string concatenationString concatenation operator
go-format flag3. The Format of PO Files
GPL, GNU General Public LicenseC.1 GNU GENERAL PUBLIC LICENSE
GUI programs11.2.5 Using contexts for solving ambiguities
guile15.5.7 GNU guile - Scheme
Guile15.5.7 GNU guile - Scheme
Guile15.5.7 GNU guile - Scheme
H
hash table, inside MO files10.3 The Format of GNU MO Files
he, she, and they1. Introduction
header entry of a PO file6.2 Filling in the Header Entry
help option4.3.3 Split at paragraphs
history of GNU gettext17.1 History of GNU gettext
I
i18n1.2 I18n, L10n, and Such
importing PO files8.7.4 Normalizing Strings in Entries
include file ‘libintl.h’1.5 Overview of GNU gettext
include file ‘libintl.h’4.1 Importing the gettext declaration
include file ‘libintl.h’11.3 Comparing the Two Interfaces
include file ‘libintl.h’13.4.12 ‘gettext.h’ in ‘lib/’
initialization4.2 Triggering gettext Operations
initialize new PO file6.1 Invoking the msginit Program
initialize translations from a compendium8.9.2.1 Initialize a New Translation File
installing gettext8.7.1 Completing GNU gettext Installation
interface to catgets11.1.1 The Interface
internationalization1.2 I18n, L10n, and Such
inttypes.hThe <inttypes.h> macros
inttypes.h15.3.1 C Format Strings
inttypes.h15.3.2 Objective C Format Strings
ISO 3166B. Country Codes
ISO 639A. Language Codes
J
Java15.5.3 Java
Java mode, and msgfmt program10.1.2 Operation mode
Java mode, and msgunfmt program10.2.1 Operation mode
Java, string concatenationString concatenation operator
java-format flag3. The Format of PO Files
java-printf-format flag3. The Format of PO Files
JavaScript, string concatenationString concatenation operator
JavaScript, strings with embedded expressionsStrings with embedded expressions
javascript-format flag3. The Format of PO Files
K
KDE format strings5.1.6 Language specific options
KDE PO file editor8.2 KDE's PO File Editor
kde-format flag3. The Format of PO Files
keyboard accelerator checking10.1.10 Input file interpretation
L
l10n1.2 I18n, L10n, and Such
language codesA. Language Codes
language selection2.3.2 Locale Environment Variables
language selection at runtime11.5 Being a gettext grok
large package11.2.2 Solving Ambiguities
LGPL, GNU Lesser General Public LicenseC.2 GNU LESSER GENERAL PUBLIC LICENSE
libiconv library13.5.6 AM_ICONV in ‘iconv.m4’
libintl for C#15.5.4 C#
libintl for Java15.5.3 Java
libintl library13.5.1 AM_GNU_GETTEXT in ‘gettext.m4’
librep Lisp15.5.11 librep
librep-format flag3. The Format of PO Files
License, GNU FDLC.3 GNU Free Documentation License
License, GNU GPLC.1 GNU GENERAL PUBLIC LICENSE
License, GNU LGPLC.2 GNU LESSER GENERAL PUBLIC LICENSE
LicensesC. Licenses
‘LINGUAS’ file13.4.2 ‘LINGUAS’ in ‘po/’
link with ‘libintl’1.5 Overview of GNU gettext
Linux1.3 Aspects in Native Language Support
Linux1.5 Overview of GNU gettext
Linux6.2 Filling in the Header Entry
Lisp15.5.8 GNU clisp - Common Lisp
lisp-format flag3. The Format of PO Files
list of translation teams, where to find6.2 Filling in the Header Entry
locale categories1.3 Aspects in Native Language Support
locale categories1.3 Aspects in Native Language Support
locale category, LC_ALL4.2 Triggering gettext Operations
locale category, LC_COLLATE4.2 Triggering gettext Operations
locale category, LC_CTYPE1.3 Aspects in Native Language Support
locale category, LC_CTYPE4.2 Triggering gettext Operations
locale category, LC_CTYPE4.2 Triggering gettext Operations
locale category, LC_MESSAGES1.3 Aspects in Native Language Support
locale category, LC_MESSAGES4.2 Triggering gettext Operations
locale category, LC_MONETARY1.3 Aspects in Native Language Support
locale category, LC_MONETARY4.2 Triggering gettext Operations
locale category, LC_NUMERIC1.3 Aspects in Native Language Support
locale category, LC_NUMERIC4.2 Triggering gettext Operations
locale category, LC_RESPONSES4.2 Triggering gettext Operations
locale category, LC_TIME1.3 Aspects in Native Language Support
locale category, LC_TIME4.2 Triggering gettext Operations
locale program6.2 Filling in the Header Entry
localization1.2 I18n, L10n, and Such
lookup message translation15.5.15.3 Invoking the gettext program
lookup message translation15.5.15.6 Invoking the eval_gettext function
lookup message translation with context15.5.15.8 Invoking the eval_pgettext function
lookup plural message translation15.5.15.4 Invoking the ngettext program
lookup plural message translation15.5.15.7 Invoking the eval_ngettext function
lookup plural message translation with context15.5.15.9 Invoking the eval_npgettext function
Lua, string concatenationString concatenation operator
lua-format flag3. The Format of PO Files
+
Jump to:   _ +   +
+A +   +B +   +C +   +D +   +E +   +F +   +G +   +H +   +I +   +J +   +K +   +L +   +M +   +N +   +O +   +P +   +Q +   +R +   +S +   +T +   +U +   +V +   +W +   +X +   +Y +   +
+ + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_29.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_29.html new file mode 100644 index 0000000000000000000000000000000000000000..c5b1169d6d7aa88003b7b72ab3dfc6d7de4b1880 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_29.html @@ -0,0 +1,399 @@ + + + + + +GNU gettext utilities: General Index: M – P + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ +

General Index: M – P

+
Jump to:   _ +   +
+A +   +B +   +C +   +D +   +E +   +F +   +G +   +H +   +I +   +J +   +K +   +L +   +M +   +N +   +O +   +P +   +Q +   +R +   +S +   +T +   +U +   +V +   +W +   +X +   +Y +   +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Index Entry Section
M
magic signature of MO files10.3 The Format of GNU MO Files
‘Makefile.in.in’ extensions13.4.4 Extending ‘Makefile’ in ‘po/’
‘Makevars’ file13.4.3 ‘Makevars’ in ‘po/’
manipulating PO files9. Manipulating PO Files
marking Perl sources15.5.26 Perl
marking string initializers4.8 Special Cases of Translatable Strings
marking strings that require translation4.4 How Marks Appear in Sources
marking strings, preparations4.3 Preparing Translatable Strings
marking translatable strings1.5 Overview of GNU gettext
markup4.3.7 No unusual markup
menu entries11.2.5 Using contexts for solving ambiguities
menu, keyboard accelerator support10.1.10 Input file interpretation
merge PO files9.1 Invoking the msgcat Program
merging two PO files9. Manipulating PO Files
merging two POT files5.2 Combining PO Template Files
message catalog files location11.2.3 Locating Message Catalog Files
messages1.3 Aspects in Native Language Support
migration from earlier versions of gettext13.2 Prerequisite Works
‘mkinstalldirs’ file13.4.7 ‘mkinstalldirs’ at top level
mnemonics of menu entries10.1.10 Input file interpretation
MO file's format10.3 The Format of GNU MO Files
modify message attributes9.8.4 Attribute manipulation
Modula-215.5.20 Modula-2
Modula-2, string concatenationString concatenation operator
modula2-format flag3. The Format of PO Files
msgattrib program, usage9.8 Invoking the msgattrib Program
msgcat program, usage9.1 Invoking the msgcat Program
msgcmp program, usage9.7 Invoking the msgcmp Program
msgcomm program, usage9.6 Invoking the msgcomm Program
msgconv program, usage9.2 Invoking the msgconv Program
msgctxt3. The Format of PO Files
msgen program, usage9.9 Invoking the msgen Program
msgexec program, usage9.10 Invoking the msgexec Program
msgfilter filter and catalog encoding9.4.3 The filter
msgfilter program, usage9.4 Invoking the msgfilter Program
msgfmt program, usage10.1 Invoking the msgfmt Program
msggrep program, usage9.3 Invoking the msggrep Program
msgid3. The Format of PO Files
msgid_plural3. The Format of PO Files
msginit program, usage6.1 Invoking the msginit Program
msgmerge program, usage7.1 Invoking the msgmerge Program
msgstr3. The Format of PO Files
msgunfmt program, usage10.2 Invoking the msgunfmt Program
msguniq program, usage9.5 Invoking the msguniq Program
multi-line strings8.7.4 Normalizing Strings in Entries
N
N_, a convenience macro11.3 Comparing the Two Interfaces
Native Language Support1.2 I18n, L10n, and Such
Natural Language Support1.2 I18n, L10n, and Such
newlines in PO files3. The Format of PO Files
ngettext11.2.6 Additional functions for plural forms
ngettext program, usage15.5.15.4 Invoking the ngettext program
NLS1.2 I18n, L10n, and Such
no-awk-format flag3. The Format of PO Files
no-boost-format flag3. The Format of PO Files
no-c++-format flag3. The Format of PO Files
no-c-format flag3. The Format of PO Files
no-c-format, and xgettext4.7 Special Comments preceding Keywords
no-csharp-format flag3. The Format of PO Files
no-d-format flag3. The Format of PO Files
no-elisp-format flag3. The Format of PO Files
no-gcc-internal-format flag3. The Format of PO Files
no-gfc-internal-format flag3. The Format of PO Files
no-go-format flag3. The Format of PO Files
no-java-format flag3. The Format of PO Files
no-java-printf-format flag3. The Format of PO Files
no-javascript-format flag3. The Format of PO Files
no-kde-format flag3. The Format of PO Files
no-librep-format flag3. The Format of PO Files
no-lisp-format flag3. The Format of PO Files
no-lua-format flag3. The Format of PO Files
no-modula2-format flag3. The Format of PO Files
no-objc-format flag3. The Format of PO Files
no-object-pascal-format flag3. The Format of PO Files
no-perl-brace-format flag3. The Format of PO Files
no-perl-format flag3. The Format of PO Files
no-php-format flag3. The Format of PO Files
no-python-brace-format flag3. The Format of PO Files
no-python-format flag3. The Format of PO Files
no-qt-format flag3. The Format of PO Files
no-qt-plural-format flag3. The Format of PO Files
no-ruby-format flag3. The Format of PO Files
no-rust-format flag3. The Format of PO Files
no-scheme-format flag3. The Format of PO Files
no-sh-format flag3. The Format of PO Files
no-smalltalk-format flag3. The Format of PO Files
no-tcl-format flag3. The Format of PO Files
no-ycp-format flag3. The Format of PO Files
nplurals, in a PO file header11.2.6 Additional functions for plural forms
number format1.3 Aspects in Native Language Support
O
objc-format flag3. The Format of PO Files
Object Pascal15.5.19 Pascal - Free Pascal Compiler
object-pascal-format flag3. The Format of PO Files
obsolete entries8.7.8 Obsolete Entries
OEM encoding2.4 Obtaining good output in a Windows console
optimization of gettext functions11.2.7 Optimization of the *gettext functions
orthography9. Manipulating PO Files
outdigits15.3.1 C Format Strings
output to stdout, xgettext5.1.2 Output file location
overview of gettext1.5 Overview of GNU gettext
P
package and version declaration in ‘configure.ac’13.4.5 ‘configure.ac’ at top level
package build and installation options14. The Installer's and Distributor's View
package distributor's view of gettext14. The Installer's and Distributor's View
package installer's view of gettext14. The Installer's and Distributor's View
package maintainer's view of gettext13. The Maintainer's View
paragraphs4.3.3 Split at paragraphs
Pascal15.5.19 Pascal - Free Pascal Compiler
Perl15.5.26 Perl
Perl default keywords15.5.26.2 Which keywords will xgettext look for?
Perl long lines15.5.26.8 How To Grok with Long Lines
Perl parentheses15.5.26.7 When To Use Parentheses
Perl pitfalls15.5.26.9 Bugs, Pitfalls, And Things That Do Not Work
Perl quote-like expressions15.5.26.4 What are Strings And Quote-like Expressions?
Perl special keywords for hash-lookups15.5.26.3 How to Extract Hash Keys
Perl unsupported string interpolation15.5.26.5 Unsupported Uses Of String Interpolation
Perl valid string interpolation15.5.26.6 Valid Uses Of String Interpolation
Perl, string concatenationString concatenation operator
Perl, strings with embedded expressionsStrings with embedded expressions
perl-brace-format flag3. The Format of PO Files
perl-format flag3. The Format of PO Files
pgettext11.2.5 Using contexts for solving ambiguities
pgettext_expr11.2.5 Using contexts for solving ambiguities
PHP15.5.27 PHP Hypertext Preprocessor
PHP, string concatenationString concatenation operator
PHP, strings with embedded expressionsStrings with embedded expressions
php-format flag3. The Format of PO Files
Pike15.5.28 Pike
plural form formulas11.2.6 Additional functions for plural forms
plural forms11.2.6 Additional functions for plural forms
plural forms, in MO files10.3 The Format of GNU MO Files
plural forms, in PO files3. The Format of PO Files
plural forms, translating12.4 Translating plural forms
plural, in a PO file header11.2.6 Additional functions for plural forms
PO files' format3. The Format of PO Files
PO mode (Emacs) commands8.7.2 Main PO mode Commands
PO template file5. Making the PO Template File
po_file_check_all9.13.8 Checking API
po_file_create9.13.2 po_file_t API
po_file_domain_header9.13.5 PO Header Entry API
po_file_domains9.13.2 po_file_t API
po_file_free9.13.2 po_file_t API
po_file_read9.13.2 po_file_t API
po_file_write9.13.2 po_file_t API
po_format_list9.13.7 Format Type API
po_format_pretty_name9.13.7 Format Type API
po_header_field9.13.5 PO Header Entry API
po_header_set_field9.13.5 PO Header Entry API
po_message_add_filepos9.13.6 po_filepos_t API
po_message_check_all9.13.8 Checking API
po_message_check_format9.13.8 Checking API
po_message_comments9.13.4 po_message_t API
po_message_create9.13.4 po_message_t API
po_message_extracted_comments9.13.4 po_message_t API
po_message_filepos9.13.6 po_filepos_t API
po_message_is_format9.13.4 po_message_t API
po_message_is_fuzzy9.13.4 po_message_t API
po_message_is_obsolete9.13.4 po_message_t API
po_message_is_range9.13.4 po_message_t API
po_message_iterator9.13.3 po_message_iterator_t API
po_message_iterator_free9.13.3 po_message_iterator_t API
po_message_msgctxt9.13.4 po_message_t API
po_message_msgid9.13.4 po_message_t API
po_message_msgid_plural9.13.4 po_message_t API
po_message_msgstr9.13.4 po_message_t API
po_message_msgstr_plural9.13.4 po_message_t API
po_message_prev_msgctxt9.13.4 po_message_t API
po_message_prev_msgid9.13.4 po_message_t API
po_message_prev_msgid_plural9.13.4 po_message_t API
po_message_remove_filepos9.13.6 po_filepos_t API
po_message_set_comments9.13.4 po_message_t API
po_message_set_extracted_comments9.13.4 po_message_t API
po_message_set_format9.13.4 po_message_t API
po_message_set_fuzzy9.13.4 po_message_t API
po_message_set_msgctxt9.13.4 po_message_t API
po_message_set_msgid9.13.4 po_message_t API
po_message_set_msgid_plural9.13.4 po_message_t API
po_message_set_msgstr9.13.4 po_message_t API
po_message_set_msgstr_plural9.13.4 po_message_t API
po_message_set_obsolete9.13.4 po_message_t API
po_message_set_prev_msgctxt9.13.4 po_message_t API
po_message_set_prev_msgid9.13.4 po_message_t API
po_message_set_prev_msgid_plural9.13.4 po_message_t API
po_message_set_range9.13.4 po_message_t API
po_next_message9.13.3 po_message_iterator_t API
PologyPology
portability problems with sed9.4.3 The filter
‘POTFILES.in’ file13.4.1 ‘POTFILES.in’ in ‘po/’
preparing programs for translation4. Preparing Program Sources
preparing rules for XML translation16.1.6 Preparing Rules for XML Internationalization
preparing shell scripts for translation15.5.15.1 Preparing Shell Scripts for Internationalization
problems with catgets interface11.1.2 Problems with the catgets Interface?!
programming languages15.1 The Language Implementor's View
Python15.5.2 Python
Python, string concatenationString concatenation operator
Python, strings with embedded expressionsStrings with embedded expressions
python-brace-format flag3. The Format of PO Files
python-format flag3. The Format of PO Files
+
Jump to:   _ +   +
+A +   +B +   +C +   +D +   +E +   +F +   +G +   +H +   +I +   +J +   +K +   +L +   +M +   +N +   +O +   +P +   +Q +   +R +   +S +   +T +   +U +   +V +   +W +   +X +   +Y +   +
+ + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_3.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_3.html new file mode 100644 index 0000000000000000000000000000000000000000..05d2b3782f5f3c8671300e10320bb4d72da25b19 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_3.html @@ -0,0 +1,610 @@ + + + + + +GNU gettext utilities: 3. The Format of PO Files + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

3. The Format of PO Files

+ +

The GNU gettext toolset helps programmers and translators +at producing, updating and using translation files, mainly those +PO files which are textual, editable files. This chapter explains +the format of PO files. +

+

A PO file is made up of many entries, each entry holding the relation +between an original untranslated string and its corresponding +translation. All entries in a given PO file usually pertain +to a single project, and all translations are expressed in a single +target language. One PO file entry has the following schematic +structure: +

+
 
white-space
+#  translator-comments
+#. extracted-comments
+#: reference…
+#, flag…
+#| msgid previous-untranslated-string
+msgid untranslated-string
+msgstr translated-string
+
+ +

The general structure of a PO file should be well understood by +the translator. When using PO mode, very little has to be known +about the format details, as PO mode takes care of them for her. +

+

A simple entry can look like this: +

+
 
#: lib/error.c:116
+msgid "Unknown system error"
+msgstr "Error desconegut del sistema"
+
+ + + + +

Entries begin with some optional white space. Usually, when generated +through GNU gettext tools, there is exactly one blank line +between entries. Then comments follow, on lines all starting with the +character #. There are two kinds of comments: those which have +some white space immediately following the # - the translator +comments -, which comments are created and maintained exclusively by the +translator, and those which have some non-white character just after the +# - the automatic comments -, which comments are created and +maintained automatically by GNU gettext tools. Comment lines +starting with #. contain comments given by the programmer, directed +at the translator; these comments are called extracted comments +because the xgettext program extracts them from the program's +source code. Comment lines starting with #: contain references to +the program's source code. Comment lines starting with #, contain +flags; more about these below. Comment lines starting with #| +contain the previous untranslated string for which the translator gave +a translation. +

+

All comments, of either kind, are optional. +

+

References to the program's source code, in lines that start with #:, +are of the form file_name:line_number or just +file_name. If the file_name contains spaces. it is enclosed +within Unicode characters U+2068 and U+2069. +

+ + +

After white space and comments, entries show two strings, namely +first the untranslated string as it appears in the original program +sources, and then, the translation of this string. The original +string is introduced by the keyword msgid, and the translation, +by msgstr. The two strings, untranslated and translated, +are quoted in various ways in the PO file, using " +delimiters and \ escapes, but the translator does not really +have to pay attention to the precise quoting format, as PO mode fully +takes care of quoting for her. +

+

The msgid strings, as well as automatic comments, are produced +and managed by other GNU gettext tools, and PO mode does not +provide means for the translator to alter these. The most she can +do is merely deleting them, and only by deleting the whole entry. +On the other hand, the msgstr string, as well as translator +comments, are really meant for the translator, and PO mode gives her +the full control she needs. +

+

The comment lines beginning with #, are special because they are +not completely ignored by the programs as comments generally are. The +comma separated list of flags is used by the msgfmt +program to give the user some better diagnostic messages. Currently +there are two forms of flags defined: +

+
+
fuzzy
+
+

This flag can be generated by the msgmerge program or it can be +inserted by the translator herself. It shows that the msgstr +string might not be a correct translation (anymore). Only the translator +can judge if the translation requires further modification, or is +acceptable as is. Once satisfied with the translation, she then removes +this fuzzy attribute. The msgmerge program inserts this +when it combined the msgid and msgstr entries after fuzzy +search only. See section Fuzzy Entries. +

+
+
c-format
+
+
+
no-c-format
+
+

These flags should not be added by a human. Instead only the +xgettext program adds them. In an automated PO file processing +system as proposed here, the user's changes would be thrown away again as +soon as the xgettext program generates a new template file. +

+

The c-format flag indicates that the untranslated string and the +translation are supposed to be C format strings. The no-c-format +flag indicates that they are not C format strings, even though the untranslated +string happens to look like a C format string (with ‘%’ directives). +

+

When the c-format flag is given for a string the msgfmt +program does some more tests to check the validity of the translation. +See section Invoking the msgfmt Program, Special Comments preceding Keywords and C Format Strings. +

+
+
objc-format
+
+
+
no-objc-format
+
+

Likewise for Objective C, see Objective C Format Strings. +

+
+
c++-format
+
+
+
no-c++-format
+
+

Likewise for C++, see C++ Format Strings. +

+
+
python-format
+
+
+
no-python-format
+
+

Likewise for Python, see Python Format Strings. +

+
+
python-brace-format
+
+
+
no-python-brace-format
+
+

Likewise for Python brace, see Python Format Strings. +

+
+
java-format
+
+
+
no-java-format
+
+

Likewise for Java MessageFormat format strings, see Java Format Strings. +

+
+
java-printf-format
+
+
+
no-java-printf-format
+
+

Likewise for Java printf format strings, see Java Format Strings. +

+
+
csharp-format
+
+
+
no-csharp-format
+
+

Likewise for C#, see C# Format Strings. +

+
+
javascript-format
+
+
+
no-javascript-format
+
+

Likewise for JavaScript, see JavaScript Format Strings. +

+
+
scheme-format
+
+
+
no-scheme-format
+
+

Likewise for Scheme, see Scheme Format Strings. +

+
+
lisp-format
+
+
+
no-lisp-format
+
+

Likewise for Lisp, see Lisp Format Strings. +

+
+
elisp-format
+
+
+
no-elisp-format
+
+

Likewise for Emacs Lisp, see Emacs Lisp Format Strings. +

+
+
librep-format
+
+
+
no-librep-format
+
+

Likewise for librep, see librep Format Strings. +

+
+
rust-format
+
+
+
no-rust-format
+
+

Likewise for Rust, see Rust Format Strings. +

+
+
go-format
+
+
+
no-go-format
+
+

Likewise for Go, see Go Format Strings. +

+
+
ruby-format
+
+
+
no-ruby-format
+
+

Likewise for Ruby, see Ruby Format Strings. +

+
+
sh-format
+
+
+
no-sh-format
+
+

Likewise for Shell, see Shell Format Strings. +

+
+
awk-format
+
+
+
no-awk-format
+
+

Likewise for awk, see awk Format Strings. +

+
+
lua-format
+
+
+
no-lua-format
+
+

Likewise for Lua, see Lua Format Strings. +

+
+
object-pascal-format
+
+
+
no-object-pascal-format
+
+

Likewise for Object Pascal, see Object Pascal Format Strings. +

+
+
modula2-format
+
+
+
no-modula2-format
+
+

Likewise for Modula-2, see Modula-2 Format Strings. +

+
+
d-format
+
+
+
no-d-format
+
+

Likewise for D, see D Format Strings. +

+
+
smalltalk-format
+
+
+
no-smalltalk-format
+
+

Likewise for Smalltalk, see Smalltalk Format Strings. +

+
+
qt-format
+
+
+
no-qt-format
+
+

Likewise for Qt, see Qt Format Strings. +

+
+
qt-plural-format
+
+
+
no-qt-plural-format
+
+

Likewise for Qt plural forms, see Qt Format Strings. +

+
+
kde-format
+
+
+
no-kde-format
+
+

Likewise for KDE, see KDE Format Strings. +

+
+
boost-format
+
+
+
no-boost-format
+
+

Likewise for Boost, see Boost Format Strings. +

+
+
tcl-format
+
+
+
no-tcl-format
+
+

Likewise for Tcl, see Tcl Format Strings. +

+
+
perl-format
+
+
+
no-perl-format
+
+

Likewise for Perl, see Perl Format Strings. +

+
+
perl-brace-format
+
+
+
no-perl-brace-format
+
+

Likewise for Perl brace, see Perl Format Strings. +

+
+
php-format
+
+
+
no-php-format
+
+

Likewise for PHP, see PHP Format Strings. +

+
+
gcc-internal-format
+
+
+
no-gcc-internal-format
+
+

Likewise for the GCC sources, see GCC internal Format Strings. +

+
+
gfc-internal-format
+
+
+
no-gfc-internal-format
+
+

Likewise for the GNU Fortran Compiler sources, see GFC internal Format Strings. +

+
+
ycp-format
+
+
+
no-ycp-format
+
+

Likewise for YCP, see YCP Format Strings. +

+
+
+ + + +

It is also possible to have entries with a context specifier. They look like +this: +

+
 
white-space
+#  translator-comments
+#. extracted-comments
+#: reference…
+#, flag…
+#| msgctxt previous-context
+#| msgid previous-untranslated-string
+msgctxt context
+msgid untranslated-string
+msgstr translated-string
+
+ +

The context serves to disambiguate messages with the same +untranslated-string. It is possible to have several entries with +the same untranslated-string in a PO file, provided that they each +have a different context. Note that an empty context string +and an absent msgctxt line do not mean the same thing. +

+ + +

A different kind of entries is used for translations which involve +plural forms. +

+
 
white-space
+#  translator-comments
+#. extracted-comments
+#: reference…
+#, flag…
+#| msgid previous-untranslated-string-singular
+#| msgid_plural previous-untranslated-string-plural
+msgid untranslated-string-singular
+msgid_plural untranslated-string-plural
+msgstr[0] translated-string-case-0
+...
+msgstr[N] translated-string-case-n
+
+ +

Such an entry can look like this: +

+
 
#: src/msgcmp.c:338 src/po-lex.c:699
+#, c-format
+msgid "found %d fatal error"
+msgid_plural "found %d fatal errors"
+msgstr[0] "s'ha trobat %d error fatal"
+msgstr[1] "s'han trobat %d errors fatals"
+
+ +

Here also, a msgctxt context can be specified before msgid, +like above. +

+

Here, additional kinds of flags can be used: +

+
+
range:
+
+

This flag is followed by a range of non-negative numbers, using the syntax +range: minimum-value..maximum-value. It designates the +possible values that the numeric parameter of the message can take. In some +languages, translators may produce slightly better translations if they know +that the value can only take on values between 0 and 10, for example. +

+
+ +

The previous-untranslated-string is optionally inserted by the +msgmerge program, at the same time when it marks a message fuzzy. +It helps the translator to see which changes were done by the developers +on the untranslated-string. +

+

It happens that some lines, usually whitespace or comments, follow the +very last entry of a PO file. Such lines are not part of any entry, +and will be dropped when the PO file is processed by the tools, or may +disturb some PO file editors. +

+

The remainder of this section may be safely skipped by those using +a PO file editor, yet it may be interesting for everybody to have a better +idea of the precise format of a PO file. On the other hand, those +wishing to modify PO files by hand should carefully continue reading on. +

+

An empty untranslated-string is reserved to contain the header +entry with the meta information (see section Filling in the Header Entry). This header +entry should be the first entry of the file. The empty +untranslated-string is reserved for this purpose and must +not be used anywhere else. +

+

Each of untranslated-string and translated-string respects +the C syntax for a character string, including the surrounding quotes +and embedded backslashed escape sequences, except that universal character +escape sequences (\u and \U) are not allowed. When the time +comes to write multi-line strings, one should not use escaped newlines. +Instead, a closing quote should follow the last character on the +line to be continued, and an opening quote should resume the string +at the beginning of the following PO file line. For example: +

+
 
msgid ""
+"Here is an example of how one might continue a very long string\n"
+"for the common case the string represents multi-line output.\n"
+
+ +

In this example, the empty string is used on the first line, to +allow better alignment of the H from the word ‘Here’ +over the f from the word ‘for’. In this example, the +msgid keyword is followed by three strings, which are meant +to be concatenated. Concatenating the empty string does not change +the resulting overall string, but it is a way for us to comply with +the necessity of msgid to be followed by a string on the same +line, while keeping the multi-line presentation left-justified, as +we find this to be a cleaner disposition. The empty string could have +been omitted, but only if the string starting with ‘Here’ was +promoted on the first line, right after msgid.(2) It was not really necessary +either to switch between the two last quoted strings immediately after +the newline ‘\n’, the switch could have occurred after any +other character, we just did it this way because it is neater. +

+ +

One should carefully distinguish between end of lines marked as +‘\n’ inside quotes, which are part of the represented +string, and end of lines in the PO file itself, outside string quotes, +which have no incidence on the represented string. +

+ +

Outside strings, white lines and comments may be used freely. +Comments start at the beginning of a line with ‘#’ and extend +until the end of the PO file line. Comments written by translators +should have the initial ‘#’ immediately followed by some white +space. If the ‘#’ is not immediately followed by white space, +this comment is most likely generated and managed by specialized GNU +tools, and might disappear or be replaced unexpectedly when the PO +file is given to msgmerge. +

+

For a PO file to be valid, no two entries without msgctxt may have +the same untranslated-string or untranslated-string-singular. +Similarly, no two entries may have the same msgctxt and the same +untranslated-string or untranslated-string-singular. +

+ + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_30.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_30.html new file mode 100644 index 0000000000000000000000000000000000000000..e39f27b5e3fbdd2f07ba68e957b94fda4f6a3b94 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_30.html @@ -0,0 +1,303 @@ + + + + + +GNU gettext utilities: General Index: Q – Y + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ +

General Index: Q – Y

+
Jump to:   _ +   +
+A +   +B +   +C +   +D +   +E +   +F +   +G +   +H +   +I +   +J +   +K +   +L +   +M +   +N +   +O +   +P +   +Q +   +R +   +S +   +T +   +U +   +V +   +W +   +X +   +Y +   +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Index Entry Section
Q
Qt format strings5.1.6 Language specific options
Qt mode, and msgfmt program10.1.2 Operation mode
qt-format flag3. The Format of PO Files
qt-plural-format flag3. The Format of PO Files
quotation marks6.2 Filling in the Header Entry
quotation marks13.4.4 Extending ‘Makefile’ in ‘po/’
quote characters, use in PO files6.2 Filling in the Header Entry
R
range: flag3. The Format of PO Files
recode-sr-latin program9.4.5 Built-in filters
related reading17.3 Related Readings
release13.7 Creating a Distribution Tarball
RSJ16.1.2 Resource String Table
RST16.1.2 Resource String Table
Ruby15.5.14 Ruby
Ruby, string concatenationString concatenation operator
Ruby, strings with embedded expressionsStrings with embedded expressions
ruby-format flag3. The Format of PO Files
Rust15.5.12 Rust
rust-format flag3. The Format of PO Files
S
Scheme15.5.7 GNU guile - Scheme
Scheme15.5.7 GNU guile - Scheme
scheme-format flag3. The Format of PO Files
scripting languages15.1 The Language Implementor's View
search messages in a catalog9.3 Invoking the msggrep Program
selecting message language2.3.2 Locale Environment Variables
sentence end markers, xgettext5.1.5 Operation mode
sentences4.3.2 Entire sentences
setting up gettext at build time14. The Installer's and Distributor's View
setting up gettext at run time2.3.2 Locale Environment Variables
several domains11.2.2 Solving Ambiguities
sex1. Introduction
sh-format flag3. The Format of PO Files
she, he, and they1. Introduction
shell format string15.5.15.5 Invoking the envsubst program
shell scripts15.5.15 sh - Shell Script
Shell, string concatenationString concatenation operator
Shell, strings with embedded expressionsStrings with embedded expressions
Smalltalk15.5.22 GNU Smalltalk
Smalltalk, string concatenationString concatenation operator
smalltalk-format flag3. The Format of PO Files
sorting msgcat output9.1.5 Output details
sorting msgmerge output7.1.7 Output details
sorting msgunfmt output10.2.7 Output details
sorting output of xgettext5.1.8 Output details
specifying plural form in a PO file11.2.6 Additional functions for plural forms
standard output, and msgcat9.1.2 Output file location
standard output, and msgmerge program7.1.3 Output file location
string concatenation4.3.4 No string concatenation
string normalization in entries8.7.4 Normalizing Strings in Entries
style4.3.1 Decent English style
supported languages, msgfmt10.1.8 XML mode options
supported languages, xgettext5.1.3 Choice of input file language
supported syntax checks, xgettext5.1.5 Operation mode
T
Tcl15.5.25 Tcl - Tk's scripting language
Tcl mode, and msgfmt program10.1.2 Operation mode
Tcl mode, and msgunfmt program10.2.1 Operation mode
Tcl, strings with embedded expressionsStrings with embedded expressions
tcl-format flag3. The Format of PO Files
template PO file1.5 Overview of GNU gettext
testing ‘.po’ files for equivalence5.1.8 Output details
Tk's scripting language15.5.25 Tcl - Tk's scripting language
Translate ToolkitTranslate Toolkit
translated entries8.7.5 Translated Entries
translating menu entries11.2.5 Using contexts for solving ambiguities
translation aspects1.3 Aspects in Native Language Support
Translation Matrix2.5 Installing Translations for Particular Programs
Translation Project1.1 The Purpose of GNU gettext
turning off NLS support13.4.12 ‘gettext.h’ in ‘lib/’
tutorial of gettext usage1.5 Overview of GNU gettext
TypeScript, string concatenationString concatenation operator
TypeScript, strings with embedded expressionsStrings with embedded expressions
U
unify duplicate translations9.5 Invoking the msguniq Program
untranslated entries8.7.7 Untranslated Entries
update translations from a compendium8.9.2.2 Update an Existing Translation File
upgrading to new versions of gettext13.2 Prerequisite Works
V
Vala, string concatenationString concatenation operator
version control for backup files, msgmerge7.1.4 Output file location in update mode
W
weblate8.1 Web-based PO editing
Windows2.4 Obtaining good output in a Windows console
wxWidgets library15.5.24 wxWidgets library
X
xargs, and output from msgexec9.10 Invoking the msgexec Program
xerror9.13.1 Error Handling
xerror29.13.1 Error Handling
xgettext program, usage5.1 Invoking the xgettext Program
XML mode, and msgfmt program10.1.2 Operation mode
xmodmap program, and typing quotation marks6.2 Filling in the Header Entry
Y
YaST2 scripting language15.5.30 YCP - YaST2 scripting language
YCP15.5.30 YCP - YaST2 scripting language
ycp-format flag3. The Format of PO Files
+
Jump to:   _ +   +
+A +   +B +   +C +   +D +   +E +   +F +   +G +   +H +   +I +   +J +   +K +   +L +   +M +   +N +   +O +   +P +   +Q +   +R +   +S +   +T +   +U +   +V +   +W +   +X +   +Y +   +
+ + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_4.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_4.html new file mode 100644 index 0000000000000000000000000000000000000000..faee4c283411dd90b84c0096bfd5b05879d65f0c --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_4.html @@ -0,0 +1,1428 @@ + + + + + +GNU gettext utilities: 4. Preparing Program Sources + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

4. Preparing Program Sources

+ + +

For the programmer, changes to the C source code fall into three +categories. First, you have to make the localization functions +known to all modules needing message translation. Second, you should +properly trigger the operation of GNU gettext when the program +initializes, usually from the main function. Last, you should +identify, adjust and mark all constant strings in your program +needing translation. +

+ + + + +

4.1 Importing the gettext declaration

+ +

Presuming that your set of programs, or package, has been adjusted +so all needed GNU gettext files are available, and your +‘Makefile’ files are adjusted (see section The Maintainer's View), each C module +having translated C strings should contain the line: +

+ +
 
#include <libintl.h>
+
+ +

Similarly, each C module containing printf()/fprintf()/... +calls with a format string that could be a translated C string (even if +the C string comes from a different C module) should contain the line: +

+
 
#include <libintl.h>
+
+ + + + +

4.2 Triggering gettext Operations

+ +

The initialization of locale data should be done with more or less +the same code in every program, as demonstrated below: +

+
 
int
+main (int argc, char *argv[])
+{
+  …
+  setlocale (LC_ALL, "");
+  bindtextdomain (PACKAGE, LOCALEDIR);
+  textdomain (PACKAGE);
+  …
+}
+
+ +

PACKAGE and LOCALEDIR should be provided either by +‘config.h’ or by the Makefile. For now consult the gettext +or hello sources for more information. +

+ + +

The use of LC_ALL might not be appropriate for you. +LC_ALL includes all locale categories and especially +LC_CTYPE. This latter category is responsible for determining +character classes with the isalnum etc. functions from +‘ctype.h’ which could especially for programs, which process some +kind of input language, be wrong. For example this would mean that a +source code using the ç (c-cedilla character) is runnable in +France but not in the U.S. +

+

Some systems also have problems with parsing numbers using the +scanf functions if an other but the LC_ALL locale category is +used. The standards say that additional formats but the one known in the +"C" locale might be recognized. But some systems seem to reject +numbers in the "C" locale format. In some situation, it might +also be a problem with the notation itself which makes it impossible to +recognize whether the number is in the "C" locale or the local +format. This can happen if thousands separator characters are used. +Some locales define this character according to the national +conventions to '.' which is the same character used in the +"C" locale to denote the decimal point. +

+

So it is sometimes necessary to replace the LC_ALL line in the +code above by a sequence of setlocale lines +

+
 
{
+  …
+  setlocale (LC_CTYPE, "");
+  setlocale (LC_MESSAGES, "");
+  …
+}
+
+ + + + + + + + +

On all POSIX conformant systems the locale categories LC_CTYPE, +LC_MESSAGES, LC_COLLATE, LC_MONETARY, +LC_NUMERIC, and LC_TIME are available. On some systems +which are only ISO C compliant, LC_MESSAGES is missing, but +a substitute for it is defined in GNU gettext's <libintl.h> and +in GNU gnulib's <locale.h>. +

+

Note that changing the LC_CTYPE also affects the functions +declared in the <ctype.h> standard header and some functions +declared in the <string.h> and <stdlib.h> standard headers. +If this is not +desirable in your application (for example in a compiler's parser), +you can use a set of substitute functions which hardwire the C locale, +such as found in the modules +‘c-ctype’, +‘c-strcase’, +‘c-strcasestr’, +‘c-snprintf’, +‘c-strtod’, ‘c-strtold’, +‘c-dtoastr’, ‘c-ldtoastr’ +in the GNU gnulib source distribution. +

+

It is also possible to switch the locale forth and back between the +environment dependent locale and the C locale, but this approach is +normally avoided because a setlocale call is expensive, +because it is tedious to determine the places where a locale switch +is needed in a large program's source, and because switching a locale +is not multithread-safe. +

+ + + +

4.3 Preparing Translatable Strings

+ +

Before strings can be marked for translations, they sometimes need to +be adjusted. Usually preparing a string for translation is done right +before marking it, during the marking phase which is described in the +next sections. What you have to keep in mind while doing that is the +following. +

+
    +
  • +Decent English style. + +
  • +Entire sentences. + +
  • +Split at paragraphs. + +
  • +Use format strings instead of string concatenation. + +
  • +Use placeholders in format strings instead of embedded URLs. + +
  • +Use placeholders in format strings instead of programmer-defined format +string directives. + +
  • +Avoid unusual markup and unusual control characters. +
+ +

Let's look at some examples of these guidelines. +

+ + + + +

4.3.1 Decent English style

+ +

Translatable strings should be in good English style. If slang language +with abbreviations and shortcuts is used, often translators will not +understand the message and will produce very inappropriate translations. +

+
 
"%s: is parameter\n"
+
+ +

This is nearly untranslatable: Is the displayed item a parameter or +the parameter? +

+
 
"No match"
+
+ +

The ambiguity in this message makes it unintelligible: Is the program +attempting to set something on fire? Does it mean "The given object does +not match the template"? Does it mean "The template does not fit for any +of the objects"? +

+ +

In both cases, adding more words to the message will help both the +translator and the English speaking user. +

+ + + +

4.3.2 Entire sentences

+ +

Translatable strings should be entire sentences. It is often not possible +to translate single verbs or adjectives in a substitutable way. +

+
 
printf ("File %s is %s protected", filename, rw ? "write" : "read");
+
+ +

Most translators will not look at the source and will thus only see the +string "File %s is %s protected", which is unintelligible. Change +this to +

+
 
printf (rw ? "File %s is write protected" : "File %s is read protected",
+        filename);
+
+ +

This way the translator will not only understand the message, she will +also be able to find the appropriate grammatical construction. A French +translator for example translates "write protected" like "protected +against writing". +

+

Entire sentences are also important because in many languages, the +declination of some word in a sentence depends on the gender or the +number (singular/plural) of another part of the sentence. There are +usually more interdependencies between words than in English. The +consequence is that asking a translator to translate two half-sentences +and then combining these two half-sentences through dumb string concatenation +will not work, for many languages, even though it would work for English. +That's why translators need to handle entire sentences. +

+

Often sentences don't fit into a single line. If a sentence is output +using two subsequent printf statements, like this +

+
 
printf ("Locale charset \"%s\" is different from\n", lcharset);
+printf ("input file charset \"%s\".\n", fcharset);
+
+ +

the translator would have to translate two half sentences, but nothing +in the POT file would tell her that the two half sentences belong together. +It is necessary to merge the two printf statements so that the +translator can handle the entire sentence at once and decide at which +place to insert a line break in the translation (if at all): +

+
 
printf ("Locale charset \"%s\" is different from\n\
+input file charset \"%s\".\n", lcharset, fcharset);
+
+ +

You may now ask: how about two or more adjacent sentences? Like in this case: +

+
 
puts ("Apollo 13 scenario: Stack overflow handling failed.");
+puts ("On the next stack overflow we will crash!!!");
+
+ +

Should these two statements merged into a single one? I would recommend to +merge them if the two sentences are related to each other, because then it +makes it easier for the translator to understand and translate both. On +the other hand, if one of the two messages is a stereotypic one, occurring +in other places as well, you will do a favour to the translator by not +merging the two. (Identical messages occurring in several places are +combined by xgettext, so the translator has to handle them once only.) +

+ + + +

4.3.3 Split at paragraphs

+ +

Translatable strings should be limited to one paragraph; don't let a +single message be longer than ten lines. The reason is that when the +translatable string changes, the translator is faced with the task of +updating the entire translated string. Maybe only a single word will +have changed in the English string, but the translator doesn't see that +(with the current translation tools), therefore she has to proofread +the entire message. +

+ +

Many GNU programs have a ‘--help’ output that extends over several +screen pages. It is a courtesy towards the translators to split such a +message into several ones of five to ten lines each. While doing that, +you can also attempt to split the documented options into groups, +such as the input options, the output options, and the informative +output options. This will help every user to find the option he is +looking for. +

+ + + +

4.3.4 No string concatenation

+ +

Hardcoded string concatenation is sometimes used to construct English +strings: +

+
 
strcpy (s, "Replace ");
+strcat (s, object1);
+strcat (s, " with ");
+strcat (s, object2);
+strcat (s, "?");
+
+ +

In order to present to the translator only entire sentences, and also +because in some languages the translator might want to swap the order +of object1 and object2, it is necessary to change this +to use a format string: +

+
 
sprintf (s, "Replace %s with %s?", object1, object2);
+
+ + +

String concatenation operator

+ +

In many programming languages, +a particular operator denotes string concatenation +at runtime (or possibly at compile time, if the compiler supports that). +

+ + + + + + + + + + + + + + + + +
    +
  • +In C++, string concatenation of std::string objects +is denoted by the ‘+’ operator. +
  • +In Python, string concatenation is denoted by the ‘+’ operator. +
  • +In Java, string concatenation is denoted by the ‘+’ operator. +
  • +In C#, string concatenation is denoted by the ‘+’ operator. +
  • +In JavaScript and TypeScript, +string concatenation is denoted by the ‘+’ operator. +
  • +In Go, string concatenation is denoted by the ‘+’ operator. +
  • +In Ruby, string concatenation is denoted by the ‘+’ operator. +
  • +In Shell, string concatenation is denoted by mere juxtaposition of strings. +
  • +In awk, string concatenation is denoted by mere juxtaposition of strings. +
  • +In Lua, string concatenation is denoted by the ‘..’ operator. +
  • +In Modula-2, string concatenation is denoted by the ‘+’ operator. +
  • +In D, string concatenation is denoted by the ‘~’ operator. +
  • +In Smalltalk, string concatenation is denoted by the ‘,’ operator. +
  • +In Vala, string concatenation is denoted by the ‘+’ operator. +
  • +In Perl, string concatenation is denoted by the ‘.’ operator. +
  • +In PHP, string concatenation is denoted by the ‘.’ operator. +
+ +

So, for example, in Java, you would change +

+
 
System.out.println("Replace "+object1+" with "+object2+"?");
+
+ +

into a statement involving a format string: +

+
 
System.out.println(
+    MessageFormat.format("Replace {0} with {1}?",
+                         new Object[] { object1, object2 }));
+
+ +

Similarly, in C#, you would change +

+
 
Console.WriteLine("Replace "+object1+" with "+object2+"?");
+
+ +

into a statement involving a format string: +

+
 
Console.WriteLine(
+    String.Format("Replace {0} with {1}?", object1, object2));
+
+ + +

Strings with embedded expressions

+ +

In some programming languages, +it is possible to have strings with embedded expressions. +The expressions can refer to variables of the program. +The value of such an expression is converted to a string +and inserted in place of the expression; +but no formatting function is called. +

+ + + + + + + + + + +
    +
  • +In Python, f-strings can contain expressions. +Such as f"Hello, {name}!". +
  • +In C#, since C# 6.0, interpolated strings can contain expressions. +Such as $"Hello, {name}!". +
  • +In JavaScript, since ES6, and in TypeScript, +template literals can contain expressions. +Such as `Hello, ${name}!`. +
  • +In Ruby, interpolated strings can contain expressions. +Such as "Hello, #{name}!". +
  • +In Shell language, double-quoted strings can contain +references to variables, along with default values and string operations. +Such as "Hello, $name!" or "Hello, ${name}!". +
  • +In D, interpolation expression sequences can contain expressions. +Such as i"Hello, $(name)!". +
  • +In Tcl, strings are subject to variable substitution. +Such as "Hello, $name!". +
  • +In Perl, interpolated strings can contain expressions. +Such as "Hello, $name!". +
  • +In PHP, string literals are subject to variable parsing. +Such as "Hello, $name!". +
+ +

These cases are effectively string concatenation as well, +just with a different syntax. +

+

So, for example, in Python, you would change +

+
 
print (f'Replace {object1.name} with {object2.name}?')
+
+ +

into a statement involving a format string: +

+
 
print ('Replace %(name1)s with %(name2)s?'
+       % { 'name1': object1.name, 'name2': object2.name })
+
+ +

or equivalently +

 
print ('Replace {name1} with {name2}?'
+       .format(name1 = object1.name, name2 = object2.name))
+
+ +

And in JavaScript, you would change +

+
 
print (`Replace ${object1.name} with ${object2.name}?`)
+
+ +

into a statement involving a format string: +

+
 
print ('Replace %s with %s?'.format(object1.name, object2.name))
+
+ +

Specifically in JavaScript, +an alternative is to use a tagged template literal: +

+
 
print (tag`Replace ${object1.name} with ${object2.name}?`)
+
+ +

and pass an option ‘--tag=tag:format’ to xgettext. +

+ +

Format strings with embedded named references

+ +

Format strings with embedded named references are different: +They are suitable for internationalization, because it is possible +to insert a call to the gettext function (that will return a +translated format string) before the argument values are +inserted in place of the placeholders. +

+

The format string types that allow embedded named references are: +

+ + + +

The <inttypes.h> macros

+ +

A similar case is compile time concatenation of strings. The ISO C 99 +include file <inttypes.h> contains a macro PRId64 that +can be used as a formatting directive for outputting an ‘int64_t’ +integer through printf. It expands to a constant string, usually +"d" or "ld" or "lld" or something like this, depending on the platform. +Assume you have code like +

+
 
printf ("The amount is %0" PRId64 "\n", number);
+
+ +

The gettext tools and library have special support for these +<inttypes.h> macros. You can therefore simply write +

+
 
printf (gettext ("The amount is %0" PRId64 "\n"), number);
+
+ +

The PO file will contain the string "The amount is %0<PRId64>\n". +The translators will provide a translation containing "%0<PRId64>" +as well, and at runtime the gettext function's result will +contain the appropriate constant string, "d" or "ld" or "lld". +

+

This works only for the predefined <inttypes.h> macros. If +you have defined your own similar macros, let's say ‘MYPRId64’, +that are not known to xgettext, the solution for this problem +is to change the code like this: +

+
 
char buf1[100];
+sprintf (buf1, "%0" MYPRId64, number);
+printf (gettext ("The amount is %s\n"), buf1);
+
+ +

This means, you put the platform dependent code in one statement, and the +internationalization code in a different statement. Note that a buffer length +of 100 is safe, because all available hardware integer types are limited to +128 bits, and to print a 128 bit integer one needs at most 54 characters, +regardless whether in decimal, octal or hexadecimal. +

+ + + +

4.3.5 No embedded URLs

+ +

It is good to not embed URLs in translatable strings, for several reasons: +

    +
  • +It avoids possible mistakes during copy and paste. +
  • +Translators cannot translate the URLs or, by mistake, use the URLs from +other packages that are present in their compendium. +
  • +When the URLs change, translators don't need to revisit the translation +of the string. +
+ +

The same holds for email addresses. +

+

So, you would change +

+
 
fputs (_("GNU GPL version 3 <https://gnu.org/licenses/gpl.html>\n"),
+       stream);
+
+ +

to +

+
 
fprintf (stream, _("GNU GPL version 3 <%s>\n"),
+         "https://gnu.org/licenses/gpl.html");
+
+ + + + +

4.3.6 No programmer-defined format string directives

+ +

The GNU C Library's <printf.h> facility and the C++ standard library's <format> header file make it possible for the programmer to define their own format string directives. However, such format directives cannot be used in translatable strings, for two reasons: +

    +
  • +There is no reference documentation for format strings with such directives, that the translators could consult. They would therefore have to guess where the directive starts and where it ends. +
  • +An ‘msgfmt -c’ invocation cannot check whether the translator has produced a compatible translation of the format string. As a consequence, when a format string contains a programmer-defined directive, the program may crash at runtime when it uses the translated format string. +
+ +

To avoid this situation, you need to move the formatting with the custom directive into a format string that does not get translated. +

+

For example, assuming code that makes use of a %r directive: +

+
 
fprintf (stream, _("The contents is: %r"), data);
+
+ +

you would rewrite it to: +

+
 
char *tmp;
+if (asprintf (&tmp, "%r", data) < 0)
+  error (...);
+fprintf (stream, _("The contents is: %s"), tmp);
+free (tmp);
+
+ +

Similarly, in C++, assuming you have defined a custom formatter for the type of data, the code +

+
 
cout << format (_("The contents is: {:#$#}"), data);
+
+ +

should be rewritten to: +

+
 
string tmp = format ("{:#$#}", data);
+cout << format (_("The contents is: {}"), tmp);
+
+ + + + +

4.3.7 No unusual markup

+ +

Unusual markup or control characters should not be used in translatable +strings. Translators will likely not understand the particular meaning +of the markup or control characters. +

+

For example, if you have a convention that ‘|’ delimits the +left-hand and right-hand part of some GUI elements, translators will +often not understand it without specific comments. It might be +better to have the translator translate the left-hand and right-hand +part separately. +

+

Another example is the ‘argp’ convention to use a single ‘\v’ +(vertical tab) control character to delimit two sections inside a +string. This is flawed. Some translators may convert it to a simple +newline, some to blank lines. With some PO file editors it may not be +easy to even enter a vertical tab control character. So, you cannot +be sure that the translation will contain a ‘\v’ character, at the +corresponding position. The solution is, again, to let the translator +translate two separate strings and combine at run-time the two translated +strings with the ‘\v’ required by the convention. +

+

HTML markup, however, is common enough that it's probably ok to use in +translatable strings. But please bear in mind that the GNU gettext tools +don't verify that the translations are well-formed HTML. +

+ + + +

4.4 How Marks Appear in Sources

+ +

All strings requiring translation should be marked in the C sources. Marking +is done in such a way that each translatable string appears to be +the sole argument of some function or preprocessor macro. There are +only a few such possible functions or macros meant for translation, +and their names are said to be marking keywords. The marking is +attached to strings themselves, rather than to what we do with them. +This approach has more uses. A blatant example is an error message +produced by formatting. The format string needs translation, as +well as some strings inserted through some ‘%s’ specification +in the format, while the result from sprintf may have so many +different instances that it is impractical to list them all in some +‘error_string_out()’ routine, say. +

+

This marking operation has two goals. The first goal of marking +is for triggering the retrieval of the translation, at run time. +The keyword is possibly resolved into a routine able to dynamically +return the proper translation, as far as possible or wanted, for the +argument string. Most localizable strings are found in executable +positions, that is, attached to variables or given as parameters to +functions. But this is not universal usage, and some translatable +strings appear in structured initializations. See section Special Cases of Translatable Strings. +

+

The second goal of the marking operation is to help xgettext +at properly extracting all translatable strings when it scans a set +of program sources and produces PO file templates. +

+

The canonical keyword for marking translatable strings is +‘gettext’, it gave its name to the whole GNU gettext +package. For packages making only light use of the ‘gettext’ +keyword, macro or function, it is easily used as is. However, +for packages using the gettext interface more heavily, it +is usually more convenient to give the main keyword a shorter, less +obtrusive name. Indeed, the keyword might appear on a lot of strings +all over the package, and programmers usually do not want nor need +their program sources to remind them forcefully, all the time, that they +are internationalized. Further, a long keyword has the disadvantage +of using more horizontal space, forcing more indentation work on +sources for those trying to keep them within 79 or 80 columns. +

+ +

Many packages use ‘_’ (a simple underline) as a keyword, +and write ‘_("Translatable string")’ instead of ‘gettext +("Translatable string")’. Further, the coding rule, from GNU standards, +wanting that there is a space between the keyword and the opening +parenthesis is relaxed, in practice, for this particular usage. +So, the textual overhead per translatable string is reduced to +only three characters: the underline and the two parentheses. +However, even if GNU gettext uses this convention internally, +it does not offer it officially. The real, genuine keyword is truly +‘gettext’ indeed. It is fairly easy for those wanting to use +‘_’ instead of ‘gettext’ to declare: +

+
 
#include <libintl.h>
+#define _(String) gettext (String)
+
+ +

instead of merely using ‘#include <libintl.h>’. +

+

The marking keywords ‘gettext’ and ‘_’ take the translatable +string as sole argument. It is also possible to define marking functions +that take it at another argument position. It is even possible to make +the marked argument position depend on the total number of arguments of +the function call; this is useful in C++. All this is achieved using +xgettext's ‘--keyword’ option. How to pass such an option +to xgettext, assuming that gettextize is used, is described +in ‘Makevars’ in ‘po/’ and AM_XGETTEXT_OPTION in ‘po.m4’. +

+

Note also that long strings can be split across lines, into multiple +adjacent string tokens. Automatic string concatenation is performed +at compile time according to ISO C and ISO C++; xgettext also +supports this syntax. +

+

In C++, marking a C++ format string requires a small code change, +because the first argument to std::format must be a constant +expression. +For example, +

 
std::format ("{} {}!", "Hello", "world")
+
+

needs to be changed to +

 
std::vformat (gettext ("{} {}!"), std::make_format_args("Hello", "world"))
+
+ +

Later on, the maintenance is relatively easy. If, as a programmer, +you add or modify a string, you will have to ask yourself if the +new or altered string requires translation, and include it within +‘_()’ if you think it should be translated. For example, ‘"%s"’ +is an example of string not requiring translation. But +‘"%s: %d"’ does require translation, because in French, unlike +in English, it's customary to put a space before a colon. +

+ + + +

4.5 Marking Translatable Strings

+ +

In PO mode, one set of features is meant more for the programmer than +for the translator, and allows him to interactively mark which strings, +in a set of program sources, are translatable, and which are not. +Even if it is a fairly easy job for a programmer to find and mark +such strings by other means, using any editor of his choice, PO mode +makes this work more comfortable. Further, this gives translators +who feel a little like programmers, or programmers who feel a little +like translators, a tool letting them work at marking translatable +strings in the program sources, while simultaneously producing a set of +translation in some language, for the package being internationalized. +

+ +

The set of program sources, targeted by the PO mode commands describe +here, should have an Emacs tags table constructed for your project, +prior to using these PO file commands. This is easy to do. In any +shell window, change the directory to the root of your project, then +execute a command resembling: +

+
 
etags src/*.[hc] lib/*.[hc]
+
+ +

presuming here you want to process all ‘.h’ and ‘.c’ files +from the ‘src/’ and ‘lib/’ directories. This command will +explore all said files and create a ‘TAGS’ file in your root +directory, somewhat summarizing the contents using a special file +format Emacs can understand. +

+ +

For packages following the GNU coding standards, there is +a make goal tags or TAGS which constructs the tag files in +all directories and for all files containing source code. +

+

Once your ‘TAGS’ file is ready, the following commands assist +the programmer at marking translatable strings in his set of sources. +But these commands are necessarily driven from within a PO file +window, and it is likely that you do not even have such a PO file yet. +This is not a problem at all, as you may safely open a new, empty PO +file, mainly for using these commands. This empty PO file will slowly +fill in while you mark strings as translatable in your program sources. +

+
+
,
+
+

Search through program sources for a string which looks like a +candidate for translation (po-tags-search). +

+
+
M-,
+
+

Mark the last string found with ‘_()’ (po-mark-translatable). +

+
+
M-.
+
+

Mark the last string found with a keyword taken from a set of possible +keywords. This command with a prefix allows some management of these +keywords (po-select-mark-and-mark). +

+
+
+ + +

The , (po-tags-search) command searches for the next +occurrence of a string which looks like a possible candidate for +translation, and displays the program source in another Emacs window, +positioned in such a way that the string is near the top of this other +window. If the string is too big to fit whole in this window, it is +positioned so only its end is shown. In any case, the cursor +is left in the PO file window. If the shown string would be better +presented differently in different native languages, you may mark it +using M-, or M-.. Otherwise, you might rather ignore it +and skip to the next string by merely repeating the , command. +

+

A string is a good candidate for translation if it contains a sequence +of three or more letters. A string containing at most two letters in +a row will be considered as a candidate if it has more letters than +non-letters. The command disregards strings containing no letters, +or isolated letters only. It also disregards strings within comments, +or strings already marked with some keyword PO mode knows (see below). +

+

If you have never told Emacs about some ‘TAGS’ file to use, the +command will request that you specify one from the minibuffer, the +first time you use the command. You may later change your ‘TAGS’ +file by using the regular Emacs command M-x visit-tags-table, +which will ask you to name the precise ‘TAGS’ file you want +to use. See (emacs)Tags section `Tag Tables' in The Emacs Editor. +

+

Each time you use the , command, the search resumes from where it was +left by the previous search, and goes through all program sources, +obeying the ‘TAGS’ file, until all sources have been processed. +However, by giving a prefix argument to the command (C-u +,), you may request that the search be restarted all over again +from the first program source; but in this case, strings that you +recently marked as translatable will be automatically skipped. +

+

Using this , command does not prevent using of other regular +Emacs tags commands. For example, regular tags-search or +tags-query-replace commands may be used without disrupting the +independent , search sequence. However, as implemented, the +initial , command (or the , command is used with a +prefix) might also reinitialize the regular Emacs tags searching to the +first tags file, this reinitialization might be considered spurious. +

+ + +

The M-, (po-mark-translatable) command will mark the +recently found string with the ‘_’ keyword. The M-. +(po-select-mark-and-mark) command will request that you type +one keyword from the minibuffer and use that keyword for marking +the string. Both commands will automatically create a new PO file +untranslated entry for the string being marked, and make it the +current entry (making it easy for you to immediately proceed to its +translation, if you feel like doing it right away). It is possible +that the modifications made to the program source by M-, or +M-. render some source line longer than 80 columns, forcing you +to break and re-indent this line differently. You may use the O +command from PO mode, or any other window changing command from +Emacs, to break out into the program source window, and do any +needed adjustments. You will have to use some regular Emacs command +to return the cursor to the PO file window, if you want command +, for the next string, say. +

+

The M-. command has a few built-in speedups, so you do not +have to explicitly type all keywords all the time. The first such +speedup is that you are presented with a preferred keyword, +which you may accept by merely typing <RET> at the prompt. +The second speedup is that you may type any non-ambiguous prefix of the +keyword you really mean, and the command will complete it automatically +for you. This also means that PO mode has to know all +your possible keywords, and that it will not accept mistyped keywords. +

+

If you reply ? to the keyword request, the command gives a +list of all known keywords, from which you may choose. When the +command is prefixed by an argument (C-u M-.), it inhibits +updating any program source or PO file buffer, and does some simple +keyword management instead. In this case, the command asks for a +keyword, written in full, which becomes a new allowed keyword for +later M-. commands. Moreover, this new keyword automatically +becomes the preferred keyword for later commands. By typing +an already known keyword in response to C-u M-., one merely +changes the preferred keyword and does nothing more. +

+

All keywords known for M-. are recognized by the , command +when scanning for strings, and strings already marked by any of those +known keywords are automatically skipped. If many PO files are opened +simultaneously, each one has its own independent set of known keywords. +There is no provision in PO mode, currently, for deleting a known +keyword, you have to quit the file (maybe using q) and reopen +it afresh. When a PO file is newly brought up in an Emacs window, only +‘gettext’ and ‘_’ are known as keywords, and ‘gettext’ +is preferred for the M-. command. In fact, this is not useful to +prefer ‘_’, as this one is already built in the M-, command. +

+ + + +

4.6 Adding advice for translators

+ +

Sometimes you might want to add advice for the translators to a +particular message. +For example: +

    +
  • +The translatable string might be decent English but nevertheless ambiguous. +
  • +The translatable string refers to something in English culture (such as +a film's name) that is different in other cultures. +
  • +The translator should make an adjustment that is specific to her locale. +
+ +

The way to do this is to add comments, +before the gettext invocation or inside the gettext invocation +but before the string, that start with the substring ‘TRANSLATORS:’. +These comments will be extracted into the POT file, so that translators +can see them. +For example, when you write +

+
 
/* TRANSLATORS: This is an English idiom,
+   meaning not to reveal a secret. */
+puts (gettext ("Don't spill the beans!"));
+
+ +

the POT file will contain: +

+
 
#. TRANSLATORS: This is an English idiom,
+#. meaning not to reveal a secret.
+#: source.c:213
+msgid "Don't spill the beans!"
+msgstr ""
+
+ +

and the translators will be shown the advice +in a particular place in their translation tool. +

+

Only comments that immediately precede the gettext invocation or +the translatable string are considered. +Intervening blank lines are OK, +but if there is other code between the comment and the translatable string, +the comment no longer applies. +

+

Note: The string TRANSLATORS: is a convention, enabled by the +Makefile.in.in file that is part of a package's build system. +It is not enabled by default in xgettext. +If you are using xgettext +without the Makefile.in.in infrastructure, +you will need to pass the option --add-comments=TRANSLATORS: yourself. +

+ + + +

4.7 Special Comments preceding Keywords

+ + +

In C programs strings are often used within calls of functions from the +printf family. The special thing about these format strings is +that they can contain format specifiers introduced with %. Assume +we have the code +

+
 
printf (gettext ("String `%s' has %d characters\n"), s, strlen (s));
+
+ +

A possible German translation for the above string might be: +

+
 
"%d Zeichen lang ist die Zeichenkette `%s'"
+
+ +

A C programmer, even if he cannot speak German, will recognize that +there is something wrong here. The order of the two format specifiers +is changed but of course the arguments in the printf don't have. +This will most probably lead to problems because now the length of the +string is regarded as the address. +

+

To prevent errors at runtime caused by translations, the msgfmt +tool can check statically whether the arguments in the original and the +translation string match in type and number. If this is not the case +and the ‘-c’ option has been passed to msgfmt, msgfmt +will give an error and refuse to produce a MO file. Thus consistent +use of ‘msgfmt -c’ will catch the error, so that it cannot cause +problems at runtime. +

+

If the word order in the above German translation would be correct one +would have to write +

+
 
"%2$d Zeichen lang ist die Zeichenkette `%1$s'"
+
+ +

The routines in msgfmt know about this special notation. +

+

Because not all strings in a program will be format strings, it is not +useful for msgfmt to test all the strings in the ‘.po’ file. +This might cause problems because the string might contain what looks +like a format specifier, but the string is not used in printf. +

+

Therefore xgettext adds a special tag to those messages it +thinks might be a format string. There is no absolute rule for this, +only a heuristic. In the ‘.po’ file the entry is marked using the +c-format flag in the #, comment line (see section The Format of PO Files). +

+ + +

The careful reader now might say that this again can cause problems. +The heuristic might guess it wrong. This is true and therefore +xgettext knows about a special kind of comment which lets +the programmer take over the decision. If in the same line as or +the immediately preceding line to the gettext keyword +the xgettext program finds a comment containing the words +xgettext:c-format, it will mark the string in any case with +the c-format flag. This kind of comment should be used when +xgettext does not recognize the string as a format string but +it really is one and it should be tested. Please note that when the +comment is in the same line as the gettext keyword, it must be +before the string to be translated. Also note that a comment such as +xgettext:c-format applies only to the first string in the same +or the next line, not to multiple strings. +

+

This situation happens quite often. The printf function is often +called with strings which do not contain a format specifier. Of course +one would normally use fputs but it does happen. In this case +xgettext does not recognize this as a format string but what +happens if the translation introduces a valid format specifier? The +printf function will try to access one of the parameters but none +exists because the original code does not pass any parameters. +

+

xgettext of course could make a wrong decision the other way +round, i.e. a string marked as a format string actually is not a format +string. In this case the msgfmt might give too many warnings and +would prevent translating the ‘.po’ file. The method to prevent +this wrong decision is similar to the one used above, only the comment +to use must contain the string xgettext:no-c-format. +

+

If a string is marked with c-format and this is not correct the +user can find out who is responsible for the decision. See +Invoking the xgettext Program to see how the --debug option can be +used for solving this problem. +

+ + + +

4.8 Special Cases of Translatable Strings

+ +

The attentive reader might now point out that it is not always possible +to mark translatable string with gettext or something like this. +Consider the following case: +

+
 
{
+  static const char *messages[] = {
+    "some very meaningful message",
+    "and another one"
+  };
+  const char *string;
+  …
+  string
+    = index > 1 ? "a default message" : messages[index];
+
+  fputs (string);
+  …
+}
+
+ +

While it is no problem to mark the string "a default message" it +is not possible to mark the string initializers for messages. +What is to be done? We have to fulfill two tasks. First we have to mark the +strings so that the xgettext program (see section Invoking the xgettext Program) +can find them, and second we have to translate the string at runtime +before printing them. +

+

The first task can be fulfilled by creating a new keyword, which names a +no-op. For the second we have to mark all access points to a string +from the array. So one solution can look like this: +

+
 
#define gettext_noop(String) String
+
+{
+  static const char *messages[] = {
+    gettext_noop ("some very meaningful message"),
+    gettext_noop ("and another one")
+  };
+  const char *string;
+  …
+  string
+    = index > 1 ? gettext ("a default message") : gettext (messages[index]);
+
+  fputs (string);
+  …
+}
+
+ +

Please convince yourself that the string which is written by +fputs is translated in any case. How to get xgettext know +the additional keyword gettext_noop is explained in Invoking the xgettext Program. +

+

The above is of course not the only solution. You could also come along +with the following one: +

+
 
#define gettext_noop(String) String
+
+{
+  static const char *messages[] = {
+    gettext_noop ("some very meaningful message"),
+    gettext_noop ("and another one")
+  };
+  const char *string;
+  …
+  string
+    = index > 1 ? gettext_noop ("a default message") : messages[index];
+
+  fputs (gettext (string));
+  …
+}
+
+ +

But this has a drawback. The programmer has to take care that +he uses gettext_noop for the string "a default message". +A use of gettext could have in rare cases unpredictable results. +

+

One advantage is that you need not make control flow analysis to make +sure the output is really translated in any case. But this analysis is +generally not very difficult. If it should be in any situation you can +use this second method in this situation. +

+ + + +

4.9 Letting Users Report Translation Bugs

+ +

Code sometimes has bugs, but translations sometimes have bugs too. The +users need to be able to report them. Reporting translation bugs to the +programmer or maintainer of a package is not very useful, since the +maintainer must never change a translation, except on behalf of the +translator. Hence the translation bugs must be reported to the +translators. +

+

Here is a way to organize this so that the maintainer does not need to +forward translation bug reports, nor even keep a list of the addresses of +the translators or their translation teams. +

+

Every program has a place where is shows the bug report address. For +GNU programs, it is the code which handles the “–help” option, +typically in a function called “usage”. In this place, instruct the +translator to add her own bug reporting address. For example, if that +code has a statement +

+
 
printf (_("Report bugs to <%s>.\n"), PACKAGE_BUGREPORT);
+
+ +

you can add some translator instructions like this: +

+
 
/* TRANSLATORS: The placeholder indicates the bug-reporting address
+   for this package.  Please add _another line_ saying
+   "Report translation bugs to <...>\n" with the address for translation
+   bugs (typically your translation team's web or email address).  */
+printf (_("Report bugs to <%s>.\n"), PACKAGE_BUGREPORT);
+
+ +

These will be extracted by ‘xgettext’, leading to a .pot file that +contains this: +

+
 
#. TRANSLATORS: The placeholder indicates the bug-reporting address
+#. for this package.  Please add _another line_ saying
+#. "Report translation bugs to <...>\n" with the address for translation
+#. bugs (typically your translation team's web or email address).
+#: src/hello.c:178
+#, c-format
+msgid "Report bugs to <%s>.\n"
+msgstr ""
+
+ + + + +

4.10 Marking Proper Names for Translation

+ +

Should names of persons, cities, locations etc. be marked for translation +or not? People who only know languages that can be written with Latin +letters (English, Spanish, French, German, etc.) are tempted to say “no”, +because names usually do not change when transported between these languages. +However, in general when translating from one script to another, names +are translated too, usually phonetically or by transliteration. For +example, Russian or Greek names are converted to the Latin alphabet when +being translated to English, and English or French names are converted +to the Katakana script when being translated to Japanese. This is +necessary because the speakers of the target language in general cannot +read the script the name is originally written in. +

+

As a programmer, you should therefore make sure that names are marked +for translation, with a special comment telling the translators that it +is a proper name and how to pronounce it. In its simple form, it looks +like this: +

+
 
printf (_("Written by %s.\n"),
+        /* TRANSLATORS: This is a proper name.  See the gettext
+           manual, section Names.  Note this is actually a non-ASCII
+           name: The first name is (with Unicode escapes)
+           "Fran\u00e7ois" or (with HTML entities) "Fran&ccedil;ois".
+           Pronunciation is like "fraa-swa pee-nar".  */
+        _("Francois Pinard"));
+
+ +

The GNU gnulib library offers a module ‘propername’ +(https://www.gnu.org/software/gnulib/MODULES.html#module=propername) +which takes care to automatically append the original name, in parentheses, +to the translated name. For names that cannot be written in ASCII, it +also frees the translator from the task of entering the appropriate non-ASCII +characters if no script change is needed. In this more comfortable form, +it looks like this: +

+
 
printf (_("Written by %s and %s.\n"),
+        proper_name ("Ulrich Drepper"),
+        /* TRANSLATORS: This is a proper name.  See the gettext
+           manual, section Names.  Note this is actually a non-ASCII
+           name: The first name is (with Unicode escapes)
+           "Fran\u00e7ois" or (with HTML entities) "Fran&ccedil;ois".
+           Pronunciation is like "fraa-swa pee-nar".  */
+        proper_name_utf8 ("Francois Pinard", "Fran\303\247ois Pinard"));
+
+ +

You can also write the original name directly in Unicode (rather than with +Unicode escapes or HTML entities) and denote the pronunciation using the +International Phonetic Alphabet (see +https://en.wikipedia.org/wiki/International_Phonetic_Alphabet). +

+

As a translator, you should use some care when translating names, because +it is frustrating if people see their names mutilated or distorted. +

+

If your language uses the Latin script, all you need to do is to reproduce +the name as perfectly as you can within the usual character set of your +language. In this particular case, this means to provide a translation +containing the c-cedilla character. If your language uses a different +script and the people speaking it don't usually read Latin words, it means +transliteration. If the programmer used the simple case, you should still +give, in parentheses, the original writing of the name – for the sake of +the people that do read the Latin script. If the programmer used the +‘propername’ module mentioned above, you don't need to give the original +writing of the name in parentheses, because the program will already do so. +Here is an example, using Greek as the target script: +

+
 
#. This is a proper name.  See the gettext
+#. manual, section Names.  Note this is actually a non-ASCII
+#. name: The first name is (with Unicode escapes)
+#. "Fran\u00e7ois" or (with HTML entities) "Fran&ccedil;ois".
+#. Pronunciation is like "fraa-swa pee-nar".
+msgid "Francois Pinard"
+msgstr "\phi\rho\alpha\sigma\omicron\alpha \pi\iota\nu\alpha\rho"
+       " (Francois Pinard)"
+
+ +

Because translation of names is such a sensitive domain, it is a good +idea to test your translation before submitting it. +

+ + + +

4.11 Preparing Library Sources

+ +

When you are preparing a library, not a program, for the use of +gettext, only a few details are different. Here we assume that +the library has a translation domain and a POT file of its own. (If +it uses the translation domain and POT file of the main program, then +the previous sections apply without changes.) +

+
    +
  1. +The library code doesn't call setlocale (LC_ALL, ""). It's the +responsibility of the main program to set the locale. The library's +documentation should mention this fact, so that developers of programs +using the library are aware of it. + +
  2. +The library code doesn't call textdomain (PACKAGE), because it +would interfere with the text domain set by the main program. + +
  3. +The initialization code for a program was + +
     
      setlocale (LC_ALL, "");
+  bindtextdomain (PACKAGE, LOCALEDIR);
+  textdomain (PACKAGE);
+
    + +

    For a library it is reduced to +

    +
     
      bindtextdomain (PACKAGE, LOCALEDIR);
+
    + +

    If your library's API doesn't already have an initialization function, +you need to create one, containing at least the bindtextdomain +invocation. However, you usually don't need to export and document this +initialization function: It is sufficient that all entry points of the +library call the initialization function if it hasn't been called before. +The typical idiom used to achieve this is a static boolean variable that +indicates whether the initialization function has been called. If the +library is meant to be used in multithreaded applications, this variable +needs to be marked volatile, so that its value get propagated +between threads. Like this: +

    +
     
    static volatile bool libfoo_initialized;
+
+static void
+libfoo_initialize (void)
+{
+  bindtextdomain (PACKAGE, LOCALEDIR);
+  libfoo_initialized = true;
+}
+
+/* This function is part of the exported API.  */
+struct foo *
+create_foo (...)
+{
+  /* Must ensure the initialization is performed.  */
+  if (!libfoo_initialized)
+    libfoo_initialize ();
+  ...
+}
+
+/* This function is part of the exported API.  The argument must be
+   non-NULL and have been created through create_foo().  */
+int
+foo_refcount (struct foo *argument)
+{
+  /* No need to invoke the initialization function here, because
+     create_foo() must already have been called before.  */
+  ...
+}
+
    + +

    The more general solution for initialization functions, POSIX +pthread_once, is not needed in this case. +

    +
  4. +The usual declaration of the ‘_’ macro in each source file was + +
     
    #include <libintl.h>
+#define _(String) gettext (String)
+
    + +

    for a program. For a library, which has its own translation domain, +it reads like this: +

    +
     
    #include <libintl.h>
+#define _(String) dgettext (PACKAGE, String)
+
    + +

    In other words, dgettext is used instead of gettext. +Similarly, the dngettext function should be used in place of the +ngettext function. +

+ + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_5.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_5.html new file mode 100644 index 0000000000000000000000000000000000000000..771e9b3f687e37cbda25a17e48c35f69e6e42920 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_5.html @@ -0,0 +1,1090 @@ + + + + + +GNU gettext utilities: 5. Making the PO Template File + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

5. Making the PO Template File

+ +

After preparing the sources, the programmer creates a PO template file. +This section explains how to use xgettext for this purpose. +

+

xgettext creates a file named ‘domainname.po’. You +should then rename it to ‘domainname.pot’. (Why doesn't +xgettext create it under the name ‘domainname.pot’ +right away? The answer is: for historical reasons. When xgettext +was specified, the distinction between a PO file and PO file template +was fuzzy, and the suffix ‘.pot’ wasn't in use at that time.) +

+ + + + + +

5.1 Invoking the xgettext Program

+ + +
 
xgettext [option] [inputfile] …
+
+ +

The xgettext program extracts translatable strings from given +input files. +

+ + +

5.1.1 Input file location

+ +
+
‘inputfile …’
+

Input files. +

+
+
‘-f file’
+
‘--files-from=file’
+
+ +

Read the names of the input files from file instead of getting +them from the command line. +

+

Often file is a temporary file, generated during the build process. +In this case, you should also pass the --generated=file option. +

+
+
‘-D directory’
+
‘--directory=directory’
+
+ +

Add directory to the list of directories. Source files are +searched relative to this list of directories. The resulting ‘.po’ +file will be written relative to the current directory, though. +

+
+
+ +

If inputfile is ‘-’, standard input is read. +

+ + +

5.1.2 Output file location

+ +
+
‘-d name’
+
‘--default-domain=name’
+
+ +

Use ‘name.po’ for output (instead of ‘messages.po’). +

+
+
‘-o file’
+
‘--output=file’
+
+ +

Write output to specified file (instead of ‘name.po’ or +‘messages.po’). +

+
+
‘-p dir’
+
‘--output-dir=dir’
+
+ +

Output files will be placed in directory dir. +

+
+
+ + +

If the output file is ‘-’ or ‘/dev/stdout’, the output +is written to standard output. +

+ + +

5.1.3 Choice of input file language

+ +
+
‘-L name’
+
‘--language=name’
+
+ + +

Specifies the language of the input files. The supported languages are +C, C++, ObjectiveC, +PO, +Python, +Java, JavaProperties, +C#, +JavaScript, +TypeScript, TSX, +Scheme, Guile, +Lisp, +EmacsLisp, +librep, +Rust, +Go, +Ruby, +Shell, +awk, +Lua, +Modula-2, +D, +Smalltalk, +Vala, +Tcl, +Perl, +PHP, +GCC-source, +YCP, +NXStringTable, +RST, RSJ, +Glade, +GSettings, +Desktop. +

+
+
‘-C’
+
‘--c++’
+
+ +

This is a shorthand for --language=C++. +

+
+
+ +

By default the language is guessed depending on the input file name +extension. +

+ + +

5.1.4 Input file interpretation

+ +
+
‘--from-code=name’
+
+

Specifies the encoding of the input files. This option is needed only +if some untranslated message strings or their corresponding comments +contain non-ASCII characters. Note that Tcl and Glade input files are +always assumed to be in UTF-8, regardless of this option. +

+
+
+ +

By default the input files are assumed to be in ASCII. +

+ + +

5.1.5 Operation mode

+ +
+
‘-j’
+
‘--join-existing’
+
+ +

Join messages with existing file. +

+
+
‘-x file’
+
‘--exclude-file=file’
+
+ +

Entries from file are not extracted. file should be a PO or +POT file. +

+
+
‘-c[tag]’
+
‘--add-comments[=tag]’
+
+ +

Place comment blocks starting with tag and preceding keyword lines +in the output file. Without a tag, the option means to put all +comment blocks preceding keyword lines in the output file. +

+

Note that comment blocks are only extracted if there is no program code +between the comment and the string that gets extracted. +For example, in the following C source code: +

+
 
/* This is the first comment.  */
+gettext ("foo");
+
+/* This is the second comment: not extracted  */
+gettext (
+  "bar");
+
+gettext (
+  /* This is the third comment.  */
+  "baz");
+
+/* This is the fourth comment.  */
+
+gettext ("I love blank lines in my programs");
+
+ +

the second comment line will not be extracted, because there is a line +with some tokens between the comment line and the line that contains +the string. But the fourth comment is extracted, because between it and +the line with the string there is merely a blank line. +

+
+
‘--check[=CHECK]’
+
+ +

Perform a syntax check on msgid and msgid_plural. The supported checks +are: +

+
+
‘ellipsis-unicode’
+

Prefer Unicode ellipsis character over ASCII ... +

+
+
‘space-ellipsis’
+

Prohibit whitespace before an ellipsis character +

+
+
‘quote-unicode’
+

Prefer Unicode quotation marks over ASCII "'` +

+
+
‘bullet-unicode’
+

Prefer Unicode bullet character over ASCII * or - +

+
+
+ +

The option has an effect on all input files. To enable or disable +checks for a certain string, you can mark it with an xgettext: +special comment in the source file. For example, if you specify the +--check=space-ellipsis option, but want to suppress the check on +a particular string, add the following comment: +

+
 
/* xgettext: no-space-ellipsis-check */
+gettext ("We really want a space before ellipsis here ...");
+
+ +

The xgettext: comment can be followed by flags separated with a +comma. The possible flags are of the form ‘[no-]name-check’, +where name is the name of a valid syntax check. If a flag is +prefixed by no-, the meaning is negated. +

+

Some tests apply the checks to each sentence within the msgid, rather +than the whole string. xgettext detects the end of sentence by +performing a pattern match, which usually looks for a period followed by +a certain number of spaces. The number is specified with the +--sentence-end option. +

+
+
‘--sentence-end[=TYPE]’
+
+ +

The supported values are: +

+
+
‘single-space’
+

Expect at least one whitespace after a period +

+
+
‘double-space’
+

Expect at least two whitespaces after a period +

+
+
+ +
+
+ + + +

5.1.6 Language specific options

+ +
+
‘-a’
+
‘--extract-all’
+
+ +

Extract all strings. +

+

This option has an effect with most languages, namely +C, C++, ObjectiveC, +Python, +Java, +C#, +JavaScript, +Scheme, Guile, +Lisp, +EmacsLisp, +librep, +Rust, +Go, +Shell, +awk, +Lua, +Modula-2, +D, +Vala, +Tcl, +Perl, +PHP, +GCC-source, +Glade, +GSettings. +

+
+
‘-k[keywordspec]’
+
‘--keyword[=keywordspec]’
+
+ +

Specify keywordspec as an additional keyword to be looked for. +Without a keywordspec, the option means to not use default keywords. +

+ + +

If keywordspec is a C identifier id, xgettext looks +for strings in the first argument of each call to the function or macro +id. If keywordspec is of the form +‘id:argnum’, xgettext looks for strings in the +argnumth argument of the call. If keywordspec is of the form +‘id:argnum1,argnum2’, xgettext looks for +strings in the argnum1st argument and in the argnum2nd argument +of the call, and treats them as singular/plural variants for a message +with plural handling. Also, if keywordspec is of the form +‘id:contextargnumc,argnum’ or +‘id:argnum,contextargnumc’, xgettext treats +strings in the contextargnumth argument as a context specifier. +And, as a special-purpose support for GNOME, if keywordspec is of the +form ‘id:argnumg’, xgettext recognizes the +argnumth argument as a string with context, using the GNOME glib +syntax ‘"msgctxt|msgid"’. +
+Furthermore, if keywordspec is of the form +‘id:…,totalnumargst’, xgettext recognizes this +argument specification only if the number of actual arguments is equal to +totalnumargs. This is useful for disambiguating overloaded function +calls in C++. +
+Finally, if keywordspec is of the form +‘id:argnum...,"xcomment"’, xgettext, when +extracting a message from the specified argument strings, adds an extracted +comment xcomment to the message. Note that when used through a normal +shell command line, the double-quotes around the xcomment need to be +escaped. +

+

This option has an effect with most languages, namely +C, C++, ObjectiveC, +Python, +Java, +C#, +JavaScript, +TypeScript, TSX, +Scheme, Guile, +Lisp, +EmacsLisp, +librep, +Rust, +Go, +Shell, +awk, +Lua, +Modula-2, +D, +Vala, +Tcl, +Perl, +PHP, +GCC-source, +Glade, +GSettings, +Desktop. +

+

The default keyword specifications, which are always looked for if not +explicitly disabled, are language dependent. They are: +

+
    +
  • +For C, C++, and GCC-source: gettext, dgettext:2, +dcgettext:2, ngettext:1,2, dngettext:2,3, +dcngettext:2,3, gettext_noop, and pgettext:1c,2, +dpgettext:2c,3, dcpgettext:2c,3, npgettext:1c,2,3, +dnpgettext:2c,3,4, dcnpgettext:2c,3,4. + +
  • +For Objective C: Like for C, and also NSLocalizedString, _, +NSLocalizedStaticString, __. + +
  • +For Shell scripts: gettext, ngettext:1,2, eval_gettext, +eval_ngettext:1,2, eval_pgettext:1c,2, +eval_npgettext:1c,2,3. + +
  • +For Python: gettext, ugettext, dgettext:2, +ngettext:1,2, ungettext:1,2, dngettext:2,3, _. + +
  • +For Lisp: gettext, ngettext:1,2, gettext-noop. + +
  • +For EmacsLisp: _. + +
  • +For librep: _. + +
  • +For Scheme and Guile: gettext, ngettext:1,2, gettext-noop. + +
  • +For Java: GettextResource.gettext:2, +GettextResource.ngettext:2,3, GettextResource.pgettext:2c,3, +GettextResource.npgettext:2c,3,4, gettext, ngettext:1,2, +pgettext:1c,2, npgettext:1c,2,3, getString. + +
  • +For C#: GetString, GetPluralString:1,2, +GetParticularString:1c,2, GetParticularPluralString:1c,2,3. + +
  • +For awk: dcgettext, dcngettext:1,2. + +
  • +For Tcl: ::msgcat::mc. + +
  • +For Perl: gettext, %gettext, $gettext, dgettext:2, +dcgettext:2, ngettext:1,2, dngettext:2,3, +dcngettext:2,3, gettext_noop. + +
  • +For PHP: _, gettext, dgettext:2, dcgettext:2, +ngettext:1,2, dngettext:2,3, dcngettext:2,3. + +
  • +For Glade 1: label, title, text, format, +copyright, comments, preview_text, tooltip. + +
  • +For Lua: _, gettext.gettext, gettext.dgettext:2, +gettext.dcgettext:2, gettext.ngettext:1,2, +gettext.dngettext:2,3, gettext.dcngettext:2,3. + +
  • +For D: gettext, dgettext:2, dcgettext:2, +ngettext:1,2, dngettext:2,3, dcngettext:2,3. + +
  • +For JavaScript, TypeScript, TSX: +_, gettext, dgettext:2, +dcgettext:2, ngettext:1,2, dngettext:2,3, +pgettext:1c,2, dpgettext:2c,3. + +
  • +For Vala: _, Q_, N_, NC_, dgettext:2, +dcgettext:2, ngettext:1,2, dngettext:2,3, +dpgettext:2c,3, dpgettext2:2c,3. + +
  • +For Desktop: Name, GenericName, Comment, +Keywords. +
+ +

To disable the default keyword specifications, the option ‘-k’ or +‘--keyword’ or ‘--keyword=’, without a keywordspec, can be +used. +

+
+
‘--flag=word:arg:flag’
+
+

Specifies additional flags for strings occurring as part of the argth +argument of the function word. The possible flags are the possible +format string indicators, such as ‘c-format’, and their negations, +such as ‘no-c-format’, possibly prefixed with ‘pass-’. +
+ +The meaning of --flag=function:arg:lang-format +is that in language lang, the specified function expects as +argth argument a format string. (For those of you familiar with +GCC function attributes, --flag=function:arg:c-format is +roughly equivalent to the declaration +‘__attribute__ ((__format__ (__printf__, arg, ...)))’ attached +to function in a C source file.) +For example, if you use the ‘error’ function from GNU libc, you can +specify its behaviour through --flag=error:3:c-format. The effect of +this specification is that xgettext will mark as format strings all +gettext invocations that occur as argth argument of +function. +This is useful when such strings contain no format string directives: +together with the checks done by ‘msgfmt -c’ it will ensure that +translators cannot accidentally use format string directives that would +lead to a crash at runtime. +
+ +The meaning of --flag=function:arg:pass-lang-format +is that in language lang, if the function call occurs in a +position that must yield a format string, then its argth argument +must yield a format string of the same type as well. (If you know GCC +function attributes, the --flag=function:arg:pass-c-format +option is roughly equivalent to the declaration +‘__attribute__ ((__format_arg__ (arg)))’ attached to function +in a C source file.) +For example, if you use the ‘_’ shortcut for the gettext function, +you should use --flag=_:1:pass-c-format. The effect of this +specification is that xgettext will propagate a format string +requirement for a _("string") call to its first argument, the literal +"string", and thus mark it as a format string. +This is useful when such strings contain no format string directives: +together with the checks done by ‘msgfmt -c’ it will ensure that +translators cannot accidentally use format string directives that would +lead to a crash at runtime. +
+This option has an effect with most languages, namely +C, C++, ObjectiveC, +Python, +Java, +C#, +JavaScript, +TypeScript, TSX, +Scheme, Guile, +Lisp, +EmacsLisp, +librep, +Rust, +Go, +Shell, +awk, +Lua, +Modula-2, +D, +Vala, +Tcl, +Perl, +PHP, +GCC-source, +YCP. +

+
+
‘--tag=word:format’
+
+

Defines the behaviour of tagged template literals with tag word. +This option has an effect only with language JavaScript. +
+format is a symbolic description +of the first step of the JavaScript function named word, +namely how this function constructs a format string +based on the parts of the template literal. +Currently only one value is supported: javascript-gnome-format, +which describes the construction of a format string with numbered placeholders +{0}, {1}, {2}, etc. +For example, javascript-gnome-format transforms the template literal +word`My name is ${id.name} and I am ${id.age} years old.` +into the format string "My name is {0} and I am {1} years old.". +

+
+
‘-T’
+
‘--trigraphs’
+
+ + +

Understand ANSI C trigraphs for input +(deprecated, since trigraphs have been removed from ISO C 23). +
+This option has an effect only with the languages C, C++, ObjectiveC. +

+
+
‘--qt’
+
+ +

Recognize Qt format strings. +
+This option has an effect only with the language C++. +

+
+
‘--kde’
+
+ +

Recognize KDE 4 format strings. +
+This option has an effect only with the language C++. +

+
+
‘--boost’
+
+ +

Recognize Boost format strings. +
+This option has an effect only with the language C++. +

+
+
‘--debug’
+
+ +

Use the flags c-format and possible-c-format to show who was +responsible for marking a message as a format string. The latter form is +used if the xgettext program decided, the former form is used if +the programmer prescribed it. +

+

By default only the c-format form is used. The translator should +not have to care about these details. +

+
+
+ +

This implementation of xgettext is able to process a few awkward +cases, like strings in preprocessor macros, ANSI concatenation of +adjacent strings, and escaped end of lines for continued strings. +

+ + +

5.1.7 Options for XML input files

+ +

When some of the input files are XML files +and they are not of one of the types covered +by the system-wide installed *.its files, +a *.its file is needed for each such file type, +so that xgettext can handle them. +There are two ways to specify such a file: +

+
    +
  • +
    +
    ‘--its=file’
    +
    +

    Use the ITS rules defined in file. +

    +
    + +
  • +The environment variable GETTEXTDATADIRS. +Together with the *.its file, you need a corresponding *.loc file +(see section Preparing Rules for XML Internationalization). +Furthermore you need to store these files +in a directory ‘parent_dir/its/’ + +and set the environment variable GETTEXTDATADIRS to include +parent_dir. +More generally, the value of GETTEXTDATADIRS should be +a colon-separated list of directory names. +
+ +

Note that when the option --its is specified, +the system-wide installed *.its files are ignored +and the environment variable GETTEXTDATADIRS has no effect either. +

+ + +

5.1.8 Output details

+ + +
+
‘--color’
+
‘--color=when’
+
+

Specify whether or when to use colors and other text attributes. +See The --color option for details. +

+
+
‘--style=style_file’
+
+

Specify the CSS style rule file to use for --color. +See The --style option for details. +

+
+
‘--force-po’
+
+

Always write an output file even if no message is defined. +

+
+
‘-i’
+
‘--indent’
+
+ +

Write the .po file using indented style. +

+
+
‘--no-location’
+
+

Do not write ‘#: filename:line’ lines. Note that using +this option makes it harder for technically skilled translators to understand +each message's context. +

+
+
‘-n’
+
‘--add-location=type’
+
+ +

Generate ‘#: filename:line’ lines (default). +

+

The optional type can be either ‘full’, ‘file’, or +‘never’. If it is not given or ‘full’, it generates the +lines with both file name and line number. If it is ‘file’, the +line number part is omitted. If it is ‘never’, it completely +suppresses the lines (same as --no-location). +

+
+
‘--strict’
+
+

Write out a strict Uniforum conforming PO file. Note that this +Uniforum format should be avoided because it doesn't support the +GNU extensions. +

+
+
‘--properties-output’
+
+

Write out a Java ResourceBundle in Java .properties syntax. Note +that this file format doesn't support plural forms and silently drops +obsolete messages. +

+
+
‘--stringtable-output’
+
+

Write out a NeXTstep/GNUstep localized resource file in .strings syntax. +Note that this file format doesn't support plural forms. +

+
+
‘--itstool’
+
+

Write out comments recognized by itstool (http://itstool.org). +Note that this is only effective with XML files. +

+
+
‘-w number’
+
‘--width=number’
+
+ +

Set the output page width. Long strings in the output files will be +split across multiple lines in order to ensure that each line's width +(= number of screen columns) is less or equal to the given number. +

+
+
‘--no-wrap’
+
+

Do not break long message lines. Message lines whose width exceeds the +output page width will not be split into several lines. Only file reference +lines which are wider than the output page width will be split. +

+
+
‘-s’
+
‘--sort-output’
+
+ + +

Generate sorted output (deprecated). Note that using this option makes it +much harder for the translator to understand each message's context. +

+
+
‘-F’
+
‘--sort-by-file’
+
+ +

Sort output by file location. +

+
+
‘--omit-header’
+
+

Don't write header with ‘msgid ""’ entry. +Note: Using this option may lead to an error in subsequent operations +if the output contains non-ASCII characters. +

+ +

This is useful for testing purposes because it eliminates a source +of variance for generated .gmo files. With --omit-header, +two invocations of xgettext on the same files with the same +options at different times are guaranteed to produce the same results. +

+

Note that using this option will lead to an error if the resulting file +would not entirely be in ASCII. +

+
+
‘--no-git’
+
+

Don't use the git program +to produce a reproducible ‘POT-Creation-Date’ field in the output. +

+

Use this option, for speed, if +your project has a very long Git history +(hundreds of thousands of commits) +or you are specifying thousands of input files. +

+

By default, xgettext determines the ‘POT-Creation-Date’ as +the maximum version-controlled modification time +among all the given input files. +With this option, you can specify that it should instead use +the maximum modification time (time stamp on disk) +among all the given input files. +

+

By “version control”, here we mean the Git version control system. +

+
+
‘--copyright-holder=string’
+
+

Set the copyright holder in the output. string should be the +copyright holder of the surrounding package. (Note that the msgid +strings, extracted from the package's sources, belong to the copyright +holder of the package.) Translators are expected to transfer or disclaim +the copyright for their translations, so that package maintainers can +distribute them without legal risk. If string is empty, the output +files are marked as being in the public domain; in this case, the translators +are expected to disclaim their copyright, again so that package maintainers +can distribute them without legal risk. +

+

The default value for string is the Free Software Foundation, Inc., +simply because xgettext was first used in the GNU project. +

+
+
‘--foreign-user’
+
+

Omit FSF copyright in output. This option is equivalent to +‘--copyright-holder=''’. It can be useful for packages outside the GNU +project that want their translations to be in the public domain. +

+
+
‘--package-name=package’
+
+

Set the package name in the header of the output. +

+
+
‘--package-version=version’
+
+

Set the package version in the header of the output. This option has an +effect only if the ‘--package-name’ option is also used. +

+
+
‘--msgid-bugs-address=email@address’
+
+

Set the reporting address for msgid bugs. This is the email address or URL +to which the translators shall report bugs in the untranslated strings: +

+
    +
  • - Strings which are not entire sentences; see the maintainer guidelines +in Preparing Translatable Strings. +
  • - Strings which use unclear terms or require additional context to be +understood. +
  • - Strings which make invalid assumptions about notation of date, time or +money. +
  • - Pluralisation problems. +
  • - Incorrect English spelling. +
  • - Incorrect formatting. +
+ +

It can be your email address, or a mailing list address where translators +can write to without being subscribed, or the URL of a web page through +which the translators can contact you. +

+

The default value is empty, which means that translators will be clueless! +Don't forget to specify this option. +

+
+
‘--generated=file’
+
+ +

Declares that the given file is generated +and therefore should not have +an influence on the ‘POT-Creation-Date’ field in the output. +

+

When you specify this option, +you should also specify one or more --reference options, +to indicate the files from which the given file was generated. +

+
+
‘--reference=file’
+
+ +

Declares that the output depends on the contents of the given file. +This has an influence on the ‘POT-Creation-Date’ field in the output. +

+

By default, xgettext determines the ‘POT-Creation-Date’ as +the maximum version-controlled modification time +among all the given input files. +With this option, you can specify that +the output depends also on some other files. +For example, use this option when +some of the input files is not under version control +but instead is generated from one or more files that are under version control. +

+

By “version control”, here we mean the Git version control system. +

+
+
‘-m[string]’
+
‘--msgstr-prefix[=string]’
+
+ +

Use string (or "" if not specified) as prefix for msgstr values. +

+
+
‘-M[string]’
+
‘--msgstr-suffix[=string]’
+
+ +

Use string (or "" if not specified) as suffix for msgstr values. +

+
+
+ + + +

5.1.9 Informative output

+ +
+
‘-h’
+
‘--help’
+
+ +

Display this help and exit. +

+
+
‘-V’
+
‘--version’
+
+ +

Output version information and exit. +

+
+
‘-v’
+
‘--verbose’
+
+ +

Increase verbosity level. +

+
+
+ + + +

5.1.10 Example

+ +

A sample invocation of xgettext, in a project +that has a single source file ‘src/hello.c’ +that uses ‘_’ as shorthand for the gettext function, +could be: +

+
 
xgettext -o hello.pot \
+         --add-comments=TRANSLATORS: \
+         --keyword=_ --flag=_:1:pass-c-format \
+         --directory=.. \
+         src/hello.c
+
+ + + + +

5.2 Combining PO Template Files

+ +

When a package contains sources in different programming languages and +different, incompatible xgettext command line options are required +for these different parts of the package, the solution is to create +intermediate PO template files for each of the parts and then combine (merge) +them together. +

+ + +

For example, assume you have two source files ‘a.c’ and ‘b.py’, +and want to extract their translatable strings in separate steps. +

+

Each of the following command sequences does this. The output is the same. +

+
    +
  • +This command sequence creates intermediate POT files and then combines them. +
     
    xgettext -o part-c.pot a.c
+xgettext -o part-py.pot b.py
+xgettext -o all.pot part-c.pot part-py.pot
+
    +
  • +This command sequence does several xgettext invocations, with a +single POT file that accumulates the translatable strings. +
     
    xgettext -o all.pot a.c
+xgettext -o all.pot --join-existing b.py
+
    +
  • +Likewise here, but a ‘--default-domain’ option is used to denote +the output file rather than a ‘-o’ option. +
     
    xgettext --default-domain=all a.c
+xgettext --default-domain=all --join-existing b.py
+mv all.po all.pot
+
    +
+ +

One might be tempted to think that ‘msgcat’ can do the same thing, +through a command sequence such as: +

 
xgettext -o part-c.pot a.c
+xgettext -o part-py.pot b.py
+msgcat -o all.pot part-c.pot part-py.pot
+
+

But no, this does not work reliably, because sometimes part-c.pot +and part-py.pot will contain different POT-Creation-Date +values, and msgcat then produces an all.pot file that has +conflict markers in the header entry. +This is because msgcat generally is meant to produce PO files that +are to be reviewed and edited by a translator; this is not desired here. +

+ + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_6.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_6.html new file mode 100644 index 0000000000000000000000000000000000000000..d94e11bba54ef466e81d0c1772153ee04c2e3207 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_6.html @@ -0,0 +1,537 @@ + + + + + +GNU gettext utilities: 6. Creating a New PO File + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

6. Creating a New PO File

+ +

When starting a new translation, the translator creates a file called +‘LANG.po’, as a copy of the ‘package.pot’ template +file with modifications in the initial comments (at the beginning of the file) +and in the header entry (the first entry, near the beginning of the file). +

+

The easiest way to do so is by use of the ‘msginit’ program. +For example: +

+
 
$ cd PACKAGE-VERSION
+$ cd po
+$ msginit
+
+ +

The alternative way is to do the copy and modifications by hand. +To do so, the translator copies ‘package.pot’ to +‘LANG.po’. Then she modifies the initial comments and +the header entry of this file. +

+ + + + +

6.1 Invoking the msginit Program

+ + +
 
msginit [option]
+
+ + + +

The msginit program creates a new PO file, initializing the meta +information with values from the user's environment. +

+

Here are more details. The following header fields of a PO file are +automatically filled, when possible. +

+
+
‘Project-Id-Version’
+

The value is guessed from the configure script or any other files +in the current directory. +

+
+
‘PO-Revision-Date’
+

The value is taken from the PO-Creation-Data in the input POT +file, or the current date is used. +

+
+
‘Last-Translator’
+

The value is taken from user's password file entry and the mailer +configuration files. +

+
+
‘Language-Team, Language’
+

These values are set according to the current locale and the predefined +list of translation teams. +

+
+
‘MIME-Version, Content-Type, Content-Transfer-Encoding’
+

These values are set according to the content of the POT file and the +current locale. If the POT file contains charset=UTF-8, it means that +the POT file contains non-ASCII characters, and we keep the UTF-8 +encoding. Otherwise, when the POT file is plain ASCII, we use the +locale's encoding. +

+
+
‘Plural-Forms’
+

The value is first looked up from the embedded table. +

+

As an experimental feature, you can instruct msginit to use the +information from Unicode CLDR, by setting the GETTEXTCLDRDIR +environment variable. The program will look for a file named +common/supplemental/plurals.xml under that directory. You can +get the CLDR data from http://cldr.unicode.org/. +

+
+
+ + + +

6.1.1 Input file location

+ +
+
‘-i inputfile’
+
‘--input=inputfile’
+
+ +

Input POT file. +

+
+
+ +

If no inputfile is given, the current directory is searched for the +POT file. If it is ‘-’, standard input is read. +

+ + +

6.1.2 Output file location

+ +
+
‘-o file’
+
‘--output-file=file’
+
+ +

Write output to specified PO file. +

+
+
+ +

If no output file is given, it depends on the ‘--locale’ option or the +user's locale setting. If it is ‘-’, the results are written to +standard output. +

+ + +

6.1.3 Input file syntax

+ +
+
‘-P’
+
‘--properties-input’
+
+ +

Assume the input file is a Java ResourceBundle in Java .properties +syntax, not in PO file syntax. +

+
+
‘--stringtable-input’
+
+

Assume the input file is a NeXTstep/GNUstep localized resource file in +.strings syntax, not in PO file syntax. +

+
+
+ + + +

6.1.4 Output details

+ +
+
‘-l ll_CC[.encoding]’
+
‘--locale=ll_CC[.encoding]’
+
+ +

Set target locale. ll should be a language code, and CC should +be a country code. The optional part .encoding specifies the encoding +of the locale; most often this part is .UTF-8. +The command ‘locale -a’ can be used to output a list +of all installed locales. The default is the user's locale setting. +

+
+
‘--no-translator’
+
+

Declares that the PO file will not have a human translator and is instead +automatically generated. +

+
+
‘--color’
+
‘--color=when’
+
+

Specify whether or when to use colors and other text attributes. +See The --color option for details. +

+
+
‘--style=style_file’
+
+

Specify the CSS style rule file to use for --color. +See The --style option for details. +

+
+
‘-p’
+
‘--properties-output’
+
+ +

Write out a Java ResourceBundle in Java .properties syntax. Note +that this file format doesn't support plural forms and silently drops +obsolete messages. +

+
+
‘--stringtable-output’
+
+

Write out a NeXTstep/GNUstep localized resource file in .strings syntax. +Note that this file format doesn't support plural forms. +

+
+
‘-w number’
+
‘--width=number’
+
+ +

Set the output page width. Long strings in the output files will be +split across multiple lines in order to ensure that each line's width +(= number of screen columns) is less or equal to the given number. +

+
+
‘--no-wrap’
+
+

Do not break long message lines. Message lines whose width exceeds the +output page width will not be split into several lines. Only file reference +lines which are wider than the output page width will be split. +

+
+
+ + + +

6.1.5 Informative output

+ +
+
‘-h’
+
‘--help’
+
+ +

Display this help and exit. +

+
+
‘-V’
+
‘--version’
+
+ +

Output version information and exit. +

+
+
+ + + + +

6.2 Filling in the Header Entry

+ +

The initial comments "SOME DESCRIPTIVE TITLE", "YEAR" and +"FIRST AUTHOR <EMAIL@ADDRESS>, YEAR" ought to be replaced by sensible +information. This can be done in any text editor; if Emacs is used +and it switched to PO mode automatically (because it has recognized +the file's suffix), you can disable it by typing M-x fundamental-mode. +

+

Modifying the header entry can already be done using PO mode: in Emacs, +type M-x po-mode RET and then RET again to start editing the +entry. You should fill in the following fields. +

+
+
Project-Id-Version
+

This is the name and version of the package. Fill it in if it has not +already been filled in by xgettext. +

+
+
Report-Msgid-Bugs-To
+

This has already been filled in by xgettext. It contains an email +address or URL where you can report bugs in the untranslated strings: +

+
    +
  • - Strings which are not entire sentences, see the maintainer guidelines +in Preparing Translatable Strings. +
  • - Strings which use unclear terms or require additional context to be +understood. +
  • - Strings which make invalid assumptions about notation of date, time or +money. +
  • - Pluralisation problems. +
  • - Incorrect English spelling. +
  • - Incorrect formatting. +
+ +
+
POT-Creation-Date
+

This has already been filled in by xgettext. +

+
+
PO-Revision-Date
+

You don't need to fill this in. It will be filled by the PO file editor +when you save the file. +

+
+
Last-Translator
+

Fill in your name and email address (without double quotes). +

+
+
Language-Team
+

Fill in the English name of the language, and the email address or +homepage URL of the language team you are part of. +

+

Before starting a translation, it is a good idea to get in touch with +your translation team, not only to make sure you don't do duplicated work, +but also to coordinate difficult linguistic issues. +

+ +

In the Free Translation Project, each translation team has its own mailing +list. The up-to-date list of teams can be found at the Free Translation +Project's homepage, https://translationproject.org/, in the "Teams" +area. +

+
+
Language
+

Fill in the language code of the language. This can be in one of three +forms: +

+
    +
  • - +‘ll’, an ISO 639 two-letter language code (lowercase). +For some languages, +a two-letter code does not exist, and a three-letter code is used instead. +See Language Codes for the list of codes. + +
  • - +‘ll_CC’, where ‘ll’ is an ISO 639 two-letter +or three-letter +language code (lowercase) and ‘CC’ is an ISO 3166 two-letter +country code (uppercase). The country code specification is not redundant: +Some languages have dialects in different countries. For example, +‘de_AT’ is used for Austria, and ‘pt_BR’ for Brazil. The country +code serves to distinguish the dialects. See Language Codes and +Country Codes for the lists of codes. + +
  • - +‘ll_CC@variant’, where ‘ll’ is an +ISO 639 two-letter +or three-letter +language code (lowercase), ‘CC’ is an +ISO 3166 two-letter country code (uppercase), and ‘variant’ is +a variant designator. The variant designator (lowercase) can be a script +designator, such as ‘latin’ or ‘cyrillic’. +
+ +

The naming convention ‘ll_CC’ is also the way locales are +named on systems based on GNU libc. But there are three important differences: +

+
    +
  • +In this PO file field, but not in locale names, ‘ll_CC’ +combinations denoting a language's main dialect are abbreviated as +‘ll’. For example, ‘de’ is equivalent to ‘de_DE’ +(German as spoken in Germany), and ‘pt’ to ‘pt_PT’ (Portuguese as +spoken in Portugal) in this context. + +
  • +In this PO file field, suffixes like ‘.encoding’ are not used. + +
  • +In this PO file field, variant designators that are not relevant to message +translation, such as ‘@euro’, are not used. +
+ +

So, if your locale name is ‘de_DE.UTF-8’, the language specification in +PO files is just ‘de’. +

+
+
Content-Type
+
+ +

Replace ‘CHARSET’ with the character encoding used for your language, +in your locale, or UTF-8. This field is needed for correct operation of the +msgmerge and msgfmt programs, as well as for users whose +locale's character encoding differs from yours (see How to specify the output character set gettext uses). +

+ +

You get the character encoding of your locale by running the shell command +‘locale charmap’. If the result is ‘C’ or ‘ANSI_X3.4-1968’, +which is equivalent to ‘ASCII’ (= ‘US-ASCII’), it means that your +locale is not correctly configured. In this case, ask your translation +team which charset to use. ‘ASCII’ is not usable for any language +except Latin. +

+ +

Because the PO files must be portable to operating systems with less advanced +internationalization facilities, the character encodings that can be used +are limited to those supported by both GNU libc and GNU +libiconv. These are: +ASCII, ISO-8859-1, ISO-8859-2, ISO-8859-3, +ISO-8859-4, ISO-8859-5, ISO-8859-6, ISO-8859-7, +ISO-8859-8, ISO-8859-9, ISO-8859-13, ISO-8859-14, +ISO-8859-15, +KOI8-R, KOI8-U, KOI8-T, +CP850, CP866, CP874, +CP932, CP949, CP950, CP1250, CP1251, +CP1252, CP1253, CP1254, CP1255, CP1256, +CP1257, GB2312, EUC-JP, EUC-KR, EUC-TW, +BIG5, BIG5-HKSCS, GBK, GB18030, SHIFT_JIS, +JOHAB, TIS-620, VISCII, GEORGIAN-PS, UTF-8. +

+ +

In the GNU system, the following encodings are frequently used for the +corresponding languages. +

+ +
    +
  • ISO-8859-1 for +Afrikaans, Albanian, Basque, Breton, Catalan, Cornish, Danish, Dutch, +English, Estonian, Faroese, Finnish, French, Galician, German, +Greenlandic, Icelandic, Indonesian, Irish, Italian, Malay, Manx, +Norwegian, Occitan, Portuguese, Spanish, Swedish, Tagalog, Uzbek, +Walloon, +
  • ISO-8859-2 for +Bosnian, Croatian, Czech, Hungarian, Polish, Romanian, Serbian, Slovak, +Slovenian, +
  • ISO-8859-3 for Maltese, +
  • ISO-8859-5 for Macedonian, Serbian, +
  • ISO-8859-6 for Arabic, +
  • ISO-8859-7 for Greek, +
  • ISO-8859-8 for Hebrew, +
  • ISO-8859-9 for Turkish, +
  • ISO-8859-13 for Latvian, Lithuanian, Maori, +
  • ISO-8859-14 for Welsh, +
  • ISO-8859-15 for +Basque, Catalan, Dutch, English, Finnish, French, Galician, German, Irish, +Italian, Portuguese, Spanish, Swedish, Walloon, +
  • KOI8-R for Russian, +
  • KOI8-U for Ukrainian, +
  • KOI8-T for Tajik, +
  • CP1251 for Bulgarian, Belarusian, +
  • GB2312, GBK, GB18030 +for simplified writing of Chinese, +
  • BIG5, BIG5-HKSCS +for traditional writing of Chinese, +
  • EUC-JP for Japanese, +
  • EUC-KR for Korean, +
  • TIS-620 for Thai, +
  • GEORGIAN-PS for Georgian, +
  • UTF-8 for any language, including those listed above. +
+ + + +

When single quote characters or double quote characters are used in +translations for your language, and your locale's encoding is one of the +ISO-8859-* charsets, it is best if you create your PO files in UTF-8 +encoding, instead of your locale's encoding. This is because in UTF-8 +the real quote characters can be represented (single quote characters: +U+2018, U+2019, double quote characters: U+201C, U+201D), whereas none of +ISO-8859-* charsets has them all. Users in UTF-8 locales will see the +real quote characters, whereas users in ISO-8859-* locales will see the +vertical apostrophe and the vertical double quote instead (because that's +what the character set conversion will transliterate them to). +

+ +

To enter such quote characters under X11, you can change your keyboard +mapping using the xmodmap program. The X11 names of the quote +characters are "leftsinglequotemark", "rightsinglequotemark", +"leftdoublequotemark", "rightdoublequotemark", "singlelowquotemark", +"doublelowquotemark". +

+

The character encoding name can be written in either upper or lower case. +Usually upper case is preferred. +

+
+
Content-Transfer-Encoding
+

Set this to 8bit. +

+
+
Plural-Forms
+

This field is optional. It is only needed if the PO file has plural forms. +You can find them by searching for the ‘msgid_plural’ keyword. The +format of the plural forms field is described in Additional functions for plural forms and +Translating plural forms. +

+
+ + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_7.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_7.html new file mode 100644 index 0000000000000000000000000000000000000000..8fd242cb58cd712e6bee9b4751555342360e92ad --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_7.html @@ -0,0 +1,429 @@ + + + + + +GNU gettext utilities: 7. Updating Existing PO Files + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

7. Updating Existing PO Files

+ + + + + +

7.1 Invoking the msgmerge Program

+ + +
 
msgmerge [option] def.po ref.pot
+
+ +

The msgmerge program merges two Uniforum style .po files together. +The def.po file is an existing PO file with translations which will +be taken over to the newly created file as long as they still match; +comments will be preserved, but extracted comments and file positions will +be discarded. The ref.pot file is the last created PO file with +up-to-date source references but old translations, or a PO Template file +(generally created by xgettext); any translations or comments +in the file will be discarded, however dot comments and file positions +will be preserved. Where an exact match cannot be found, fuzzy matching +is used to produce better results. +

+ + +

7.1.1 Input file location

+ +
+
‘def.po’
+

Translations referring to old sources. +

+
+
‘ref.pot’
+

References to the new sources. +

+
+
‘-D directory’
+
‘--directory=directory’
+
+ +

Add directory to the list of directories. Source files are +searched relative to this list of directories. The resulting ‘.po’ +file will be written relative to the current directory, though. +

+
+
‘-C file’
+
‘--compendium=file’
+
+ +

Specify an additional library of message translations. See section Using Translation Compendia. +This option may be specified more than once. +

+
+
+ + + +

7.1.2 Operation mode

+ +
+
‘-U’
+
‘--update’
+
+ +

Update def.po. Do nothing if def.po is already up to date. +

+
+
+ + + +

7.1.3 Output file location

+ +
+
‘-o file’
+
‘--output-file=file’
+
+ +

Write output to specified file. +

+
+
+ + +

The results are written to standard output if no output file is specified +or if it is ‘-’. +

+ + +

7.1.4 Output file location in update mode

+ +

The result is written back to def.po. +

+
+
‘--backup=control’
+
+ +

Make a backup of def.po +

+
+
‘--suffix=suffix’
+
+

Override the usual backup suffix. +

+
+
+ + +

The version control method may be selected via the --backup option +or through the VERSION_CONTROL environment variable. Here are the +values: +

+
+
‘none’
+
‘off’
+

Never make backups (even if --backup is given). +

+
+
‘numbered’
+
‘t’
+

Make numbered backups. +

+
+
‘existing’
+
‘nil’
+

Make numbered backups if numbered backups for this file already exist, +otherwise make simple backups. +

+
+
‘simple’
+
‘never’
+

Always make simple backups. +

+
+
+ +

The backup suffix is ‘~’, unless set with --suffix or the +SIMPLE_BACKUP_SUFFIX environment variable. +

+ + +

7.1.5 Operation modifiers

+ +
+
‘-m’
+
‘--multi-domain’
+
+ +

Apply ref.pot to each of the domains in def.po. +

+
+
‘--for-msgfmt’
+
+

Produce a PO file meant for msgfmt only, not for a translator. +This option omits untranslated messages, fuzzy messages (except the header +entry), and obsolete messages from the output. Also, it omits translator +comments and ‘#: filename:line’ lines from the output. +In particular, this option implies ‘--no-fuzzy-matching’. +

+
+
‘-N’
+
‘--no-fuzzy-matching’
+
+ +

Do not use fuzzy matching when an exact match is not found. This may speed +up the operation considerably. +

+
+
‘--previous’
+
+

Keep the previous msgids of translated messages, marked with ‘#|’, when +adding the fuzzy marker to such messages. +

+
+ + + +

7.1.6 Input file syntax

+ +
+
‘-P’
+
‘--properties-input’
+
+ +

Assume the input files are Java ResourceBundles in Java .properties +syntax, not in PO file syntax. +

+
+
‘--stringtable-input’
+
+

Assume the input files are NeXTstep/GNUstep localized resource files in +.strings syntax, not in PO file syntax. +

+
+
+ + + +

7.1.7 Output details

+ + +
+
‘--lang=catalogname’
+
+

Specify the ‘Language’ field to be used in the header entry. See +Filling in the Header Entry for the meaning of this field. Note: The +‘Language-Team’ and ‘Plural-Forms’ fields are left unchanged. +If this option is not specified, the ‘Language’ field is inferred, as +best as possible, from the ‘Language-Team’ field. +

+
+
‘--color’
+
‘--color=when’
+
+

Specify whether or when to use colors and other text attributes. +See The --color option for details. +

+
+
‘--style=style_file’
+
+

Specify the CSS style rule file to use for --color. +See The --style option for details. +

+
+
‘--force-po’
+
+

Always write an output file even if it contains no message. +

+
+
‘-i’
+
‘--indent’
+
+ +

Write the .po file using indented style. +

+
+
‘--no-location’
+
+

Do not write ‘#: filename:line’ lines. +

+
+
‘-n’
+
‘--add-location=type’
+
+

Generate ‘#: filename:line’ lines (default). +

+

The optional type can be either ‘full’, ‘file’, or +‘never’. If it is not given or ‘full’, it generates the +lines with both file name and line number. If it is ‘file’, the +line number part is omitted. If it is ‘never’, it completely +suppresses the lines (same as --no-location). +

+
+
‘--strict’
+
+

Write out a strict Uniforum conforming PO file. Note that this +Uniforum format should be avoided because it doesn't support the +GNU extensions. +

+
+
‘-p’
+
‘--properties-output’
+
+ +

Write out a Java ResourceBundle in Java .properties syntax. Note +that this file format doesn't support plural forms and silently drops +obsolete messages. +

+
+
‘--stringtable-output’
+
+

Write out a NeXTstep/GNUstep localized resource file in .strings syntax. +Note that this file format doesn't support plural forms. +

+
+
‘-w number’
+
‘--width=number’
+
+ +

Set the output page width. Long strings in the output files will be +split across multiple lines in order to ensure that each line's width +(= number of screen columns) is less or equal to the given number. +

+
+
‘--no-wrap’
+
+

Do not break long message lines. Message lines whose width exceeds the +output page width will not be split into several lines. Only file reference +lines which are wider than the output page width will be split. +

+
+
‘-s’
+
‘--sort-output’
+
+ + +

Generate sorted output (deprecated). Note that using this option makes it +much harder for the translator to understand each message's context. +

+
+
‘-F’
+
‘--sort-by-file’
+
+ +

Sort output by file location. +

+
+
+ + + +

7.1.8 Informative output

+ +
+
‘-h’
+
‘--help’
+
+ +

Display this help and exit. +

+
+
‘-V’
+
‘--version’
+
+ +

Output version information and exit. +

+
+
‘-v’
+
‘--verbose’
+
+ +

Increase verbosity level. +

+
+
‘-q’
+
‘--quiet’
+
‘--silent’
+
+ + +

Suppress progress indicators. +

+
+
+ + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_8.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_8.html new file mode 100644 index 0000000000000000000000000000000000000000..628391eac0483feedb4fa878c6dfc43f02416a5b --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_8.html @@ -0,0 +1,1682 @@ + + + + + +GNU gettext utilities: 8. Editing PO Files + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

8. Editing PO Files

+ +

As a translator, you will typically edit a PO file +in an editor that has built-in knowledge about the PO file format. +You most probably won't want to edit a PO file +in a text editor for plain-text files, +because that would be cumbersome regarding cursor navigation +and would also easily lead to syntax mistakes. +

+ + + + +

8.1 Web-based PO editing

+ +

There are two ways to edit a PO file: +either through a web-based PO editor, in a browser, +or through a PO editor that you can install on your computer. +Which one you choose, depends on your habits. +

+

Typically, the software project for which you want to provide translations +has set up a workflow that you, as a translator, have to follow. +

+
    +
  • +There are projects which use the Weblate +localization suite. +In this case, you have the choice between a +web-based PO editor +and a workflow +where you download the previous translation, +update it with your preferred PO editor, +and then upload it back. + +
  • +There are projects which offer you only a web-based PO editor, as only choice. +Since web-based tools restrict your freedom as a user – you cannot make +modifications on your own to that tool –, +you should complain to that project and claim the choice of using a locally +installed PO editor, because that is the only way that can guarantee +your freedom of choice and freedom to modify the software. + +
  • +There are projects which do not support web-based localizations. +In this case, pick a PO file editor as listed in the next few sections. +Examples for such projects are +the Free Translation Project, +as well as projects where you directly interact with the version control +system of the project. +
+ + + + +

8.2 KDE's PO File Editor

+ +

Lokalize (https://apps.kde.org/lokalize/) +is the PO file editor made by the KDE project. +It is present in many +GNU/Linux distributions. +

+ + + +

8.3 GNOME's PO File Editor

+ +

Gtranslator (https://wiki.gnome.org/Apps/Gtranslator) +is the PO file editor made by the GNOME project. +It is present in many +GNU/Linux distributions. +

+ + + +

8.4 Poedit

+ +

Poedit (https://github.com/vslavik/poedit) +is another decent PO file editor. +It works on all major desktop OSes and +is present in many +GNU/Linux distributions. +

+ + + +

8.5 OmegaT

+ +

OmegaT +(Wikipedia: https://en.wikipedia.org/wiki/OmegaT, +home page: https://omegat.org/, +code: https://github.com/omegat-org/omegat) +is a translation editor +that focuses on speeding up the translator's work through advanced features +like translation memory, spell-checking, glossaries, dictionaries. +It supports not only PO files, but also +direct translation of various file formats +(such as plain text, web pages, OpenDocument files, DocBook XML, etc.) +without using intermediate files. +It is present in many +GNU/Linux distributions. +

+ + + +

8.6 The Virtaal Translation Editor

+ +

Virtaal +(Wikipedia: https://en.wikipedia.org/wiki/Virtaal, +home page: https://virtaal.translatehouse.org/, +code: https://github.com/translate/virtaal) +is a translation editor +that supports not only PO files but also XLIFF files. +It is present in some +GNU/Linux distributions, +such as Debian up to Debian 11. +

+ + + +

8.7 Emacs's PO File Editor

+ + +

For those of you being +the lucky users of Emacs, PO mode has been specifically created +for providing a cozy environment for editing or modifying PO files. +While editing a PO file, PO mode allows for the easy browsing of +auxiliary and compendium PO files, as well as for following references into +the set of C program sources from which PO files have been derived. +It has a few special features, among which are the interactive marking +of program strings as translatable, and the validation of PO files +with easy repositioning to PO file lines showing errors. +

+

For the beginning, besides main PO mode commands +(see section Main PO mode Commands), you should know how to move between entries +(see section Entry Positioning), and how to handle untranslated entries +(see section Untranslated Entries). +

+ + + + +

8.7.1 Completing GNU gettext Installation

+ +

Once you have received, unpacked, configured and compiled the GNU +gettext distribution, the ‘make install’ command puts in +place the programs xgettext, msgfmt, gettext, and +msgmerge, as well as their available message catalogs. To +top off a comfortable installation, you might also want to make the +PO mode available to your Emacs users. +

+ + +

During the installation of the PO mode, you might want to modify your +file ‘.emacs’, once and for all, so it contains a few lines looking +like: +

+
 
(setq auto-mode-alist
+      (cons '("\\.po\\'\\|\\.po\\." . po-mode) auto-mode-alist))
+(autoload 'po-mode "po-mode" "Major mode for translators to edit PO files" t)
+
+ +

Later, whenever you edit some ‘.po’ +file, or any file having the string ‘.po.’ within its name, +Emacs loads ‘po-mode.elc’ (or ‘po-mode.el’) as needed, and +automatically activates PO mode commands for the associated buffer. +The string PO appears in the mode line for any buffer for +which PO mode is active. Many PO files may be active at once in a +single Emacs session. +

+

If you are using Emacs version 20 or newer, and have already installed +the appropriate international fonts on your system, you may also tell +Emacs how to determine automatically the coding system of every PO file. +This will often (but not always) cause the necessary fonts to be loaded +and used for displaying the translations on your Emacs screen. For this +to happen, add the lines: +

+
 
(modify-coding-system-alist 'file "\\.po\\'\\|\\.po\\."
+                            'po-find-file-coding-system)
+(autoload 'po-find-file-coding-system "po-mode")
+
+ +

to your ‘.emacs’ file. If, with this, you still see boxes instead +of international characters, try a different font set (via Shift Mouse +button 1). +

+ + + +

8.7.2 Main PO mode Commands

+ +

After setting up Emacs with something similar to the lines in +Completing GNU gettext Installation, PO mode is activated for a window when Emacs finds a +PO file in that window. This puts the window read-only and establishes a +po-mode-map, which is a genuine Emacs mode, in a way that is not derived +from text mode in any way. Functions found on po-mode-hook, +if any, will be executed. +

+

When PO mode is active in a window, the letters ‘PO’ appear +in the mode line for that window. The mode line also displays how +many entries of each kind are held in the PO file. For example, +the string ‘132t+3f+10u+2o’ would tell the translator that the +PO mode contains 132 translated entries (see section Translated Entries, +3 fuzzy entries (see section Fuzzy Entries), 10 untranslated entries +(see section Untranslated Entries) and 2 obsolete entries (see section Obsolete Entries). Zero-coefficients items are not shown. So, in this example, if +the fuzzy entries were unfuzzied, the untranslated entries were translated +and the obsolete entries were deleted, the mode line would merely display +‘145t’ for the counters. +

+

The main PO commands are those which do not fit into the other categories of +subsequent sections. These allow for quitting PO mode or for managing windows +in special ways. +

+
+
_
+
+

Undo last modification to the PO file (po-undo). +

+
+
Q
+
+

Quit processing and save the PO file (po-quit). +

+
+
q
+
+

Quit processing, possibly after confirmation (po-confirm-and-quit). +

+
+
0
+
+

Temporary leave the PO file window (po-other-window). +

+
+
?
+
h
+
+ +

Show help about PO mode (po-help). +

+
+
=
+
+

Give some PO file statistics (po-statistics). +

+
+
V
+
+

Batch validate the format of the whole PO file (po-validate). +

+
+
+ + + +

The command _ (po-undo) interfaces to the Emacs +undo facility. See (emacs)Undo section `Undoing Changes' in The Emacs Editor. Each time _ is typed, modifications which the translator +did to the PO file are undone a little more. For the purpose of +undoing, each PO mode command is atomic. This is especially true for +the <RET> command: the whole edition made by using a single +use of this command is undone at once, even if the edition itself +implied several actions. However, while in the editing window, one +can undo the edition work quite parsimoniously. +

+ + + + +

The commands Q (po-quit) and q +(po-confirm-and-quit) are used when the translator is done with the +PO file. The former is a bit less verbose than the latter. If the file +has been modified, it is saved to disk first. In both cases, and prior to +all this, the commands check if any untranslated messages remain in the +PO file and, if so, the translator is asked if she really wants to leave +off working with this PO file. This is the preferred way of getting rid +of an Emacs PO file buffer. Merely killing it through the usual command +C-x k (kill-buffer) is not the tidiest way to proceed. +

+ + +

The command 0 (po-other-window) is another, softer way, +to leave PO mode, temporarily. It just moves the cursor to some other +Emacs window, and pops one if necessary. For example, if the translator +just got PO mode to show some source context in some other, she might +discover some apparent bug in the program source that needs correction. +This command allows the translator to change sex, become a programmer, +and have the cursor right into the window containing the program she +(or rather he) wants to modify. By later getting the cursor back +in the PO file window, or by asking Emacs to edit this file once again, +PO mode is then recovered. +

+ + + +

The command h (po-help) displays a summary of all available PO +mode commands. The translator should then type any character to resume +normal PO mode operations. The command ? has the same effect +as h. +

+ + +

The command = (po-statistics) computes the total number of +entries in the PO file, the ordinal of the current entry (counted from +1), the number of untranslated entries, the number of obsolete entries, +and displays all these numbers. +

+ + +

The command V (po-validate) launches msgfmt in +checking and verbose +mode over the current PO file. This command first offers to save the +current PO file on disk. The msgfmt tool, from GNU gettext, +has the purpose of creating a MO file out of a PO file, and PO mode uses +the features of this program for checking the overall format of a PO file, +as well as all individual entries. +

+ +

The program msgfmt runs asynchronously with Emacs, so the +translator regains control immediately while her PO file is being studied. +Error output is collected in the Emacs ‘*compilation*’ buffer, +displayed in another window. The regular Emacs command C-x` +(next-error), as well as other usual compile commands, allow the +translator to reposition quickly to the offending parts of the PO file. +Once the cursor is on the line in error, the translator may decide on +any PO mode action which would help correcting the error. +

+ + + +

8.7.3 Entry Positioning

+ +

The cursor in a PO file window is almost always part of +an entry. The only exceptions are the special case when the cursor +is after the last entry in the file, or when the PO file is +empty. The entry where the cursor is found to be is said to be the +current entry. Many PO mode commands operate on the current entry, +so moving the cursor does more than allowing the translator to browse +the PO file, this also selects on which entry commands operate. +

+ +

Some PO mode commands alter the position of the cursor in a specialized +way. A few of those special purpose positioning are described here, +the others are described in following sections (for a complete list try +C-h m): +

+
+
.
+
+

Redisplay the current entry (po-current-entry). +

+
+
n
+
+

Select the entry after the current one (po-next-entry). +

+
+
p
+
+

Select the entry before the current one (po-previous-entry). +

+
+
<
+
+

Select the first entry in the PO file (po-first-entry). +

+
+
>
+
+

Select the last entry in the PO file (po-last-entry). +

+
+
m
+
+

Record the location of the current entry for later use +(po-push-location). +

+
+
r
+
+

Return to a previously saved entry location (po-pop-location). +

+
+
x
+
+

Exchange the current entry location with the previously saved one +(po-exchange-location). +

+
+
+ + + +

Any Emacs command able to reposition the cursor may be used +to select the current entry in PO mode, including commands which +move by characters, lines, paragraphs, screens or pages, and search +commands. However, there is a kind of standard way to display the +current entry in PO mode, which usual Emacs commands moving +the cursor do not especially try to enforce. The command . +(po-current-entry) has the sole purpose of redisplaying the +current entry properly, after the current entry has been changed by +means external to PO mode, or the Emacs screen otherwise altered. +

+

It is yet to be decided if PO mode helps the translator, or otherwise +irritates her, by forcing a rigid window disposition while she +is doing her work. We originally had quite precise ideas about +how windows should behave, but on the other hand, anyone used to +Emacs is often happy to keep full control. Maybe a fixed window +disposition might be offered as a PO mode option that the translator +might activate or deactivate at will, so it could be offered on an +experimental basis. If nobody feels a real need for using it, or +a compulsion for writing it, we should drop this whole idea. +The incentive for doing it should come from translators rather than +programmers, as opinions from an experienced translator are surely +more worth to me than opinions from programmers thinking about +how others should do translation. +

+ + + + +

The commands n (po-next-entry) and p +(po-previous-entry) move the cursor the entry following, +or preceding, the current one. If n is given while the +cursor is on the last entry of the PO file, or if p +is given while the cursor is on the first entry, no move is done. +

+ + + + +

The commands < (po-first-entry) and > +(po-last-entry) move the cursor to the first entry, or last +entry, of the PO file. When the cursor is located past the last +entry in a PO file, most PO mode commands will return an error saying +‘After last entry’. Moreover, the commands < and > +have the special property of being able to work even when the cursor +is not into some PO file entry, and one may use them for nicely +correcting this situation. But even these commands will fail on a +truly empty PO file. There are development plans for the PO mode for it +to interactively fill an empty PO file from sources. See section Marking Translatable Strings. +

+

The translator may decide, before working at the translation of +a particular entry, that she needs to browse the remainder of the +PO file, maybe for finding the terminology or phraseology used +in related entries. She can of course use the standard Emacs idioms +for saving the current cursor location in some register, and use that +register for getting back, or else, use the location ring. +

+ + + + +

PO mode offers another approach, by which cursor locations may be saved +onto a special stack. The command m (po-push-location) +merely adds the location of current entry to the stack, pushing +the already saved locations under the new one. The command +r (po-pop-location) consumes the top stack element and +repositions the cursor to the entry associated with that top element. +This position is then lost, for the next r will move the cursor +to the previously saved location, and so on until no locations remain +on the stack. +

+

If the translator wants the position to be kept on the location stack, +maybe for taking a look at the entry associated with the top +element, then go elsewhere with the intent of getting back later, she +ought to use m immediately after r. +

+ + +

The command x (po-exchange-location) simultaneously +repositions the cursor to the entry associated with the top element of +the stack of saved locations, and replaces that top element with the +location of the current entry before the move. Consequently, repeating +the x command toggles alternatively between two entries. +For achieving this, the translator will position the cursor on the +first entry, use m, then position to the second entry, and +merely use x for making the switch. +

+ + + +

8.7.4 Normalizing Strings in Entries

+ +

There are many different ways for encoding a particular string into a +PO file entry, because there are so many different ways to split and +quote multi-line strings, and even, to represent special characters +by backslashed escaped sequences. Some features of PO mode rely on +the ability for PO mode to scan an already existing PO file for a +particular string encoded into the msgid field of some entry. +Even if PO mode has internally all the built-in machinery for +implementing this recognition easily, doing it fast is technically +difficult. To facilitate a solution to this efficiency problem, +we decided on a canonical representation for strings. +

+

A conventional representation of strings in a PO file is currently +under discussion, and PO mode experiments with a canonical representation. +Having both xgettext and PO mode converging towards a uniform +way of representing equivalent strings would be useful, as the internal +normalization needed by PO mode could be automatically satisfied +when using xgettext from GNU gettext. An explicit +PO mode normalization should then be only necessary for PO files +imported from elsewhere, or for when the convention itself evolves. +

+

So, for achieving normalization of at least the strings of a given +PO file needing a canonical representation, the following PO mode +command is available: +

+ +
+
M-x po-normalize
+
+

Tidy the whole PO file by making entries more uniform. +

+
+
+ +

The special command M-x po-normalize, which has no associated +keys, revises all entries, ensuring that strings of both original +and translated entries use uniform internal quoting in the PO file. +It also removes any crumb after the last entry. This command may be +useful for PO files freshly imported from elsewhere, or if we ever +improve on the canonical quoting format we use. This canonical format +is not only meant for getting cleaner PO files, but also for greatly +speeding up msgid string lookup for some other PO mode commands. +

+

M-x po-normalize presently makes three passes over the entries. +The first implements heuristics for converting PO files for GNU +gettext 0.6 and earlier, in which msgid and msgstr +fields were using K&R style C string syntax for multi-line strings. +These heuristics may fail for comments not related to obsolete +entries and ending with a backslash; they also depend on subsequent +passes for finalizing the proper commenting of continued lines for +obsolete entries. This first pass might disappear once all oldish PO +files would have been adjusted. The second and third pass normalize +all msgid and msgstr strings respectively. They also +clean out those trailing backslashes used by XView's msgfmt +for continued lines. +

+ +

Having such an explicit normalizing command allows for importing PO +files from other sources, but also eases the evolution of the current +convention, evolution driven mostly by aesthetic concerns, as of now. +It is easy to make suggested adjustments at a later time, as the +normalizing command and eventually, other GNU gettext tools +should greatly automate conformance. A description of the canonical +string format is given below, for the particular benefit of those not +having Emacs handy, and who would nevertheless want to handcraft +their PO files in nice ways. +

+ +

Right now, in PO mode, strings are single line or multi-line. A string +goes multi-line if and only if it has embedded newlines, that +is, if it matches ‘[^\n]\n+[^\n]’. So, we would have: +

+
 
msgstr "\n\nHello, world!\n\n\n"
+
+ +

but, replacing the space by a newline, this becomes: +

+
 
msgstr ""
+"\n"
+"\n"
+"Hello,\n"
+"world!\n"
+"\n"
+"\n"
+
+ +

We are deliberately using a caricatural example, here, to make the +point clearer. Usually, multi-lines are not that bad looking. +It is probable that we will implement the following suggestion. +We might lump together all initial newlines into the empty string, +and also all newlines introducing empty lines (that is, for n +> 1, the n-1'th last newlines would go together on a separate +string), so making the previous example appear: +

+
 
msgstr "\n\n"
+"Hello,\n"
+"world!\n"
+"\n\n"
+
+ +

There are a few yet undecided little points about string normalization, +to be documented in this manual, once these questions settle. +

+ + + +

8.7.5 Translated Entries

+ +

Each PO file entry for which the msgstr field has been filled with +a translation, and which is not marked as fuzzy (see section Fuzzy Entries), +is said to be a translated entry. Only translated entries will +later be compiled by GNU msgfmt and become usable in programs. +Other entry types will be excluded; translation will not occur for them. +

+ +

Some commands are more specifically related to translated entry processing. +

+
+
t
+
+

Find the next translated entry (po-next-translated-entry). +

+
+
T
+
+

Find the previous translated entry (po-previous-translated-entry). +

+
+
+ + + + + +

The commands t (po-next-translated-entry) and T +(po-previous-translated-entry) move forwards or backwards, chasing +for an translated entry. If none is found, the search is extended and +wraps around in the PO file buffer. +

+ +

Translated entries usually result from the translator having edited in +a translation for them, Modifying Translations. However, if the +variable po-auto-fuzzy-on-edit is not nil, the entry having +received a new translation first becomes a fuzzy entry, which ought to +be later unfuzzied before becoming an official, genuine translated entry. +See section Fuzzy Entries. +

+ + + +

8.7.6 Fuzzy Entries

+ +

Each PO file entry may have a set of attributes, which are +qualities given a name and explicitly associated with the translation, +using a special system comment. One of these attributes +has the name fuzzy, and entries having this attribute are said +to have a fuzzy translation. They are called fuzzy entries, for short. +

+

Fuzzy entries, even if they account for translated entries for +most other purposes, usually call for revision by the translator. +Those may be produced by applying the program msgmerge to +update an older translated PO files according to a new PO template +file, when this tool hypothesises that some new msgid has +been modified only slightly out of an older one, and chooses to pair +what it thinks to be the old translation for the new modified entry. +The slight alteration in the original string (the msgid string) +should often be reflected in the translated string, and this requires +the intervention of the translator. For this reason, msgmerge +might mark some entries as being fuzzy. +

+ +

Also, the translator may decide herself to mark an entry as fuzzy +for her own convenience, when she wants to remember that the entry +has to be later revisited. So, some commands are more specifically +related to fuzzy entry processing. +

+
+
f
+
+

Find the next fuzzy entry (po-next-fuzzy-entry). +

+
+
F
+
+

Find the previous fuzzy entry (po-previous-fuzzy-entry). +

+
+
<TAB>
+
+

Remove the fuzzy attribute of the current entry (po-unfuzzy). +

+
+
+ + + + + +

The commands f (po-next-fuzzy-entry) and F +(po-previous-fuzzy-entry) move forwards or backwards, chasing for +a fuzzy entry. If none is found, the search is extended and wraps +around in the PO file buffer. +

+ + + +

The command <TAB> (po-unfuzzy) removes the fuzzy +attribute associated with an entry, usually leaving it translated. +Further, if the variable po-auto-select-on-unfuzzy has not +the nil value, the <TAB> command will automatically chase +for another interesting entry to work on. The initial value of +po-auto-select-on-unfuzzy is nil. +

+

The initial value of po-auto-fuzzy-on-edit is nil. However, +if the variable po-auto-fuzzy-on-edit is set to t, any entry +edited through the <RET> command is marked fuzzy, as a way to +ensure some kind of double check, later. In this case, the usual paradigm +is that an entry becomes fuzzy (if not already) whenever the translator +modifies it. If she is satisfied with the translation, she then uses +<TAB> to pick another entry to work on, clearing the fuzzy attribute +on the same blow. If she is not satisfied yet, she merely uses <SPC> +to chase another entry, leaving the entry fuzzy. +

+ + +

The translator may also use the <DEL> command +(po-fade-out-entry) over any translated entry to mark it as being +fuzzy, when she wants to easily leave a trace she wants to later return +working at this entry. +

+

Also, when time comes to quit working on a PO file buffer with the q +command, the translator is asked for confirmation, if fuzzy string +still exists. +

+ + + +

8.7.7 Untranslated Entries

+ +

When xgettext originally creates a PO file, unless told +otherwise, it initializes the msgid field with the untranslated +string, and leaves the msgstr string to be empty. Such entries, +having an empty translation, are said to be untranslated entries. +Later, when the programmer slightly modifies some string right in +the program, this change is later reflected in the PO file +by the appearance of a new untranslated entry for the modified string. +

+

The usual commands moving from entry to entry consider untranslated +entries on the same level as active entries. Untranslated entries +are easily recognizable by the fact they end with ‘msgstr ""’. +

+ +

The work of the translator might be (quite naively) seen as the process +of seeking for an untranslated entry, editing a translation for +it, and repeating these actions until no untranslated entries remain. +Some commands are more specifically related to untranslated entry +processing. +

+
+
u
+
+

Find the next untranslated entry (po-next-untranslated-entry). +

+
+
U
+
+

Find the previous untranslated entry (po-previous-untransted-entry). +

+
+
k
+
+

Turn the current entry into an untranslated one (po-kill-msgstr). +

+
+
+ + + + + +

The commands u (po-next-untranslated-entry) and U +(po-previous-untransted-entry) move forwards or backwards, +chasing for an untranslated entry. If none is found, the search is +extended and wraps around in the PO file buffer. +

+ + +

An entry can be turned back into an untranslated entry by +merely emptying its translation, using the command k +(po-kill-msgstr). See section Modifying Translations. +

+

Also, when time comes to quit working on a PO file buffer +with the q command, the translator is asked for confirmation, +if some untranslated string still exists. +

+ + + +

8.7.8 Obsolete Entries

+ +

By obsolete PO file entries, we mean those entries which are +commented out, usually by msgmerge when it found that the +translation is not needed anymore by the package being localized. +

+

The usual commands moving from entry to entry consider obsolete +entries on the same level as active entries. Obsolete entries are +easily recognizable by the fact that all their lines start with +#, even those lines containing msgid or msgstr. +

+

Commands exist for emptying the translation or reinitializing it +to the original untranslated string. Commands interfacing with the +kill ring may force some previously saved text into the translation. +The user may interactively edit the translation. All these commands +may apply to obsolete entries, carefully leaving the entry obsolete +after the fact. +

+ +

Moreover, some commands are more specifically related to obsolete +entry processing. +

+
+
o
+
+

Find the next obsolete entry (po-next-obsolete-entry). +

+
+
O
+
+

Find the previous obsolete entry (po-previous-obsolete-entry). +

+
+
<DEL>
+
+

Make an active entry obsolete, or zap out an obsolete entry +(po-fade-out-entry). +

+
+
+ + + + + +

The commands o (po-next-obsolete-entry) and O +(po-previous-obsolete-entry) move forwards or backwards, +chasing for an obsolete entry. If none is found, the search is +extended and wraps around in the PO file buffer. +

+

PO mode does not provide ways for un-commenting an obsolete entry +and making it active, because this would reintroduce an original +untranslated string which does not correspond to any marked string +in the program sources. This goes with the philosophy of never +introducing useless msgid values. +

+ + + + +

However, it is possible to comment out an active entry, so making +it obsolete. GNU gettext utilities will later react to the +disappearance of a translation by using the untranslated string. +The command <DEL> (po-fade-out-entry) pushes the current entry +a little further towards annihilation. If the entry is active (it is a +translated entry), then it is first made fuzzy. If it is already fuzzy, +then the entry is merely commented out, with confirmation. If the entry +is already obsolete, then it is completely deleted from the PO file. +It is easy to recycle the translation so deleted into some other PO file +entry, usually one which is untranslated. See section Modifying Translations. +

+

Here is a quite interesting problem to solve for later development of +PO mode, for those nights you are not sleepy. The idea would be that +PO mode might become bright enough, one of these days, to make good +guesses at retrieving the most probable candidate, among all obsolete +entries, for initializing the translation of a newly appeared string. +I think it might be a quite hard problem to do this algorithmically, as +we have to develop good and efficient measures of string similarity. +Right now, PO mode completely lets the decision to the translator, +when the time comes to find the adequate obsolete translation, it +merely tries to provide handy tools for helping her to do so. +

+ + + +

8.7.9 Modifying Translations

+ +

PO mode prevents direct modification of the PO file, by the usual +means Emacs gives for altering a buffer's contents. By doing so, +it pretends helping the translator to avoid little clerical errors +about the overall file format, or the proper quoting of strings, +as those errors would be easily made. Other kinds of errors are +still possible, but some may be caught and diagnosed by the batch +validation process, which the translator may always trigger by the +V command. For all other errors, the translator has to rely on +her own judgment, and also on the linguistic reports submitted to her +by the users of the translated package, having the same mother tongue. +

+

When the time comes to create a translation, correct an error diagnosed +mechanically or reported by a user, the translators have to resort to +using the following commands for modifying the translations. +

+
+
<RET>
+
+

Interactively edit the translation (po-edit-msgstr). +

+
+
<LFD>
+
C-j
+
+ +

Reinitialize the translation with the original, untranslated string +(po-msgid-to-msgstr). +

+
+
k
+
+

Save the translation on the kill ring, and delete it (po-kill-msgstr). +

+
+
w
+
+

Save the translation on the kill ring, without deleting it +(po-kill-ring-save-msgstr). +

+
+
y
+
+

Replace the translation, taking the new from the kill ring +(po-yank-msgstr). +

+
+
+ + + +

The command <RET> (po-edit-msgstr) opens a new Emacs +window meant to edit in a new translation, or to modify an already existing +translation. The new window contains a copy of the translation taken from +the current PO file entry, all ready for edition, expunged of all quoting +marks, fully modifiable and with the complete extent of Emacs modifying +commands. When the translator is done with her modifications, she may use +C-c C-c to close the subedit window with the automatically requoted +results, or C-c C-k to abort her modifications. See section Details of Sub Edition, +for more information. +

+ + + +

The command <LFD> (po-msgid-to-msgstr) initializes, or +reinitializes the translation with the original string. This command is +normally used when the translator wants to redo a fresh translation of +the original string, disregarding any previous work. +

+ +

It is possible to arrange so, whenever editing an untranslated +entry, the <LFD> command be automatically executed. If you set +po-auto-edit-with-msgid to t, the translation gets +initialised with the original string, in case none exists already. +The default value for po-auto-edit-with-msgid is nil. +

+ +

In fact, whether it is best to start a translation with an empty +string, or rather with a copy of the original string, is a matter of +taste or habit. Sometimes, the source language and the +target language are so different that is simply best to start writing +on an empty page. At other times, the source and target languages +are so close that it would be a waste to retype a number of words +already being written in the original string. A translator may also +like having the original string right under her eyes, as she will +progressively overwrite the original text with the translation, even +if this requires some extra editing work to get rid of the original. +

+ + + + + +

The command k (po-kill-msgstr) merely empties the +translation string, so turning the entry into an untranslated +one. But while doing so, its previous contents is put apart in +a special place, known as the kill ring. The command w +(po-kill-ring-save-msgstr) has also the effect of taking a +copy of the translation onto the kill ring, but it otherwise leaves +the entry alone, and does not remove the translation from the +entry. Both commands use exactly the Emacs kill ring, which is shared +between buffers, and which is well known already to Emacs lovers. +

+

The translator may use k or w many times in the course +of her work, as the kill ring may hold several saved translations. +From the kill ring, strings may later be reinserted in various +Emacs buffers. In particular, the kill ring may be used for moving +translation strings between different entries of a single PO file +buffer, or if the translator is handling many such buffers at once, +even between PO files. +

+

To facilitate exchanges with buffers which are not in PO mode, the +translation string put on the kill ring by the k command is fully +unquoted before being saved: external quotes are removed, multi-line +strings are concatenated, and backslash escaped sequences are turned +into their corresponding characters. In the special case of obsolete +entries, the translation is also uncommented prior to saving. +

+ + +

The command y (po-yank-msgstr) completely replaces the +translation of the current entry by a string taken from the kill ring. +Following Emacs terminology, we then say that the replacement +string is yanked into the PO file buffer. +See (emacs)Yanking section `Yanking' in The Emacs Editor. +The first time y is used, the translation receives the value of +the most recent addition to the kill ring. If y is typed once +again, immediately, without intervening keystrokes, the translation +just inserted is taken away and replaced by the second most recent +addition to the kill ring. By repeating y many times in a row, +the translator may travel along the kill ring for saved strings, +until she finds the string she really wanted. +

+

When a string is yanked into a PO file entry, it is fully and +automatically requoted for complying with the format PO files should +have. Further, if the entry is obsolete, PO mode then appropriately +push the inserted string inside comments. Once again, translators +should not burden themselves with quoting considerations besides, of +course, the necessity of the translated string itself respective to +the program using it. +

+

Note that k or w are not the only commands pushing strings +on the kill ring, as almost any PO mode command replacing translation +strings (or the translator comments) automatically saves the old string +on the kill ring. The main exceptions to this general rule are the +yanking commands themselves. +

+ +

To better illustrate the operation of killing and yanking, let's +use an actual example, taken from a common situation. When the +programmer slightly modifies some string right in the program, his +change is later reflected in the PO file by the appearance +of a new untranslated entry for the modified string, and the fact +that the entry translating the original or unmodified string becomes +obsolete. In many cases, the translator might spare herself some work +by retrieving the unmodified translation from the obsolete entry, +then initializing the untranslated entry msgstr field with +this retrieved translation. Once this done, the obsolete entry is +not wanted anymore, and may be safely deleted. +

+

When the translator finds an untranslated entry and suspects that a +slight variant of the translation exists, she immediately uses m +to mark the current entry location, then starts chasing obsolete +entries with o, hoping to find some translation corresponding +to the unmodified string. Once found, she uses the <DEL> command +for deleting the obsolete entry, knowing that <DEL> also kills +the translation, that is, pushes the translation on the kill ring. +Then, r returns to the initial untranslated entry, and y +then yanks the saved translation right into the msgstr +field. The translator is then free to use <RET> for fine +tuning the translation contents, and maybe to later use u, +then m again, for going on with the next untranslated string. +

+

When some sequence of keys has to be typed over and over again, the +translator may find it useful to become better acquainted with the Emacs +capability of learning these sequences and playing them back under request. +See (emacs)Keyboard Macros section `Keyboard Macros' in The Emacs Editor. +

+ + + +

8.7.10 Modifying Comments

+ +

Any translation work done seriously will raise many linguistic +difficulties, for which decisions have to be made, and the choices +further documented. These documents may be saved within the +PO file in form of translator comments, which the translator +is free to create, delete, or modify at will. These comments may +be useful to herself when she returns to this PO file after a while. +

+

Comments not having whitespace after the initial ‘#’, for example, +those beginning with ‘#.’ or ‘#:’, are not translator +comments, they are exclusively created by other gettext tools. +So, the commands below will never alter such system added comments, +they are not meant for the translator to modify. See section The Format of PO Files. +

+

The following commands are somewhat similar to those modifying translations, +so the general indications given for those apply here. See section Modifying Translations. +

+
+
#
+
+

Interactively edit the translator comments (po-edit-comment). +

+
+
K
+
+

Save the translator comments on the kill ring, and delete it +(po-kill-comment). +

+
+
W
+
+

Save the translator comments on the kill ring, without deleting it +(po-kill-ring-save-comment). +

+
+
Y
+
+

Replace the translator comments, taking the new from the kill ring +(po-yank-comment). +

+
+
+ +

These commands parallel PO mode commands for modifying the translation +strings, and behave much the same way as they do, except that they handle +this part of PO file comments meant for translator usage, rather +than the translation strings. So, if the descriptions given below are +slightly succinct, it is because the full details have already been given. +See section Modifying Translations. +

+ + +

The command # (po-edit-comment) opens a new Emacs window +containing a copy of the translator comments on the current PO file entry. +If there are no such comments, PO mode understands that the translator wants +to add a comment to the entry, and she is presented with an empty screen. +Comment marks (#) and the space following them are automatically +removed before edition, and reinstated after. For translator comments +pertaining to obsolete entries, the uncommenting and recommenting operations +are done twice. Once in the editing window, the keys C-c C-c +allow the translator to tell she is finished with editing the comment. +See section Details of Sub Edition, for further details. +

+ +

Functions found on po-subedit-mode-hook, if any, are executed after +the string has been inserted in the edit buffer. +

+ + + + + + +

The command K (po-kill-comment) gets rid of all +translator comments, while saving those comments on the kill ring. +The command W (po-kill-ring-save-comment) takes +a copy of the translator comments on the kill ring, but leaves +them undisturbed in the current entry. The command Y +(po-yank-comment) completely replaces the translator comments +by a string taken at the front of the kill ring. When this command +is immediately repeated, the comments just inserted are withdrawn, +and replaced by other strings taken along the kill ring. +

+

On the kill ring, all strings have the same nature. There is no +distinction between translation strings and translator +comments strings. So, for example, let's presume the translator +has just finished editing a translation, and wants to create a new +translator comment to document why the previous translation was +not good, just to remember what was the problem. Foreseeing that she +will do that in her documentation, the translator may want to quote +the previous translation in her translator comments. To do so, she +may initialize the translator comments with the previous translation, +still at the head of the kill ring. Because editing already pushed the +previous translation on the kill ring, she merely has to type M-w +prior to #, and the previous translation will be right there, +all ready for being introduced by some explanatory text. +

+

On the other hand, presume there are some translator comments already +and that the translator wants to add to those comments, instead +of wholly replacing them. Then, she should edit the comment right +away with #. Once inside the editing window, she can use the +regular Emacs commands C-y (yank) and M-y +(yank-pop) to get the previous translation where she likes. +

+ + + +

8.7.11 Details of Sub Edition

+ +

The PO subedit minor mode has a few peculiarities worth being described +in fuller detail. It installs a few commands over the usual editing set +of Emacs, which are described below. +

+
+
C-c C-c
+
+

Complete edition (po-subedit-exit). +

+
+
C-c C-k
+
+

Abort edition (po-subedit-abort). +

+
+
C-c C-a
+
+

Consult auxiliary PO files (po-subedit-cycle-auxiliary). +

+
+
+ + + + +

The window's contents represents a translation for a given message, +or a translator comment. The translator may modify this window to +her heart's content. Once this is done, the command C-c C-c +(po-subedit-exit) may be used to return the edited translation into +the PO file, replacing the original translation, even if it moved out of +sight or if buffers were switched. +

+ + +

If the translator becomes unsatisfied with her translation or comment, +to the extent she prefers keeping what was existent prior to the +<RET> or # command, she may use the command C-c C-k +(po-subedit-abort) to merely get rid of edition, while preserving +the original translation or comment. Another way would be for her to exit +normally with C-c C-c, then type U once for undoing the +whole effect of last edition. +

+ + +

The command C-c C-a (po-subedit-cycle-auxiliary) +allows for glancing through translations +already achieved in other languages, directly while editing the current +translation. This may be quite convenient when the translator is fluent +at many languages, but of course, only makes sense when such completed +auxiliary PO files are already available to her (see section Consulting Auxiliary PO Files). +

+

Functions found on po-subedit-mode-hook, if any, are executed after +the string has been inserted in the edit buffer. +

+

While editing her translation, the translator should pay attention to not +inserting unwanted <RET> (newline) characters at the end of +the translated string if those are not meant to be there, or to removing +such characters when they are required. Since these characters are not +visible in the editing buffer, they are easily introduced by mistake. +To help her, <RET> automatically puts the character < +at the end of the string being edited, but this < is not really +part of the string. On exiting the editing window with C-c C-c, +PO mode automatically removes such < and all whitespace added after +it. If the translator adds characters after the terminating <, it +looses its delimiting property and integrally becomes part of the string. +If she removes the delimiting <, then the edited string is taken +as is, with all trailing newlines, even if invisible. Also, if +the translated string ought to end itself with a genuine <, then +the delimiting < may not be removed; so the string should appear, +in the editing window, as ending with two < in a row. +

+ +

When a translation (or a comment) is being edited, the translator may move +the cursor back into the PO file buffer and freely move to other entries, +browsing at will. If, with an edition pending, the translator wanders in the +PO file buffer, she may decide to start modifying another entry. Each entry +being edited has its own subedit buffer. It is possible to simultaneously +edit the translation and the comment of a single entry, or to +edit entries in different PO files, all at once. Typing <RET> +on a field already being edited merely resumes that particular edit. Yet, +the translator should better be comfortable at handling many Emacs windows! +

+ +

Pending subedits may be completed or aborted in any order, regardless +of how or when they were started. When many subedits are pending and the +translator asks for quitting the PO file (with the q command), subedits +are automatically resumed one at a time, so she may decide for each of them. +

+ + + +

8.7.12 C Sources Context

+ +

PO mode is particularly powerful when used with PO files +created through GNU gettext utilities, as those utilities +insert special comments in the PO files they generate. +Some of these special comments relate the PO file entry to +exactly where the untranslated string appears in the program sources. +

+

When the translator gets to an untranslated entry, she is fairly +often faced with an original string which is not as informative as +it normally should be, being succinct, cryptic, or otherwise ambiguous. +Before choosing how to translate the string, she needs to understand +better what the string really means and how tight the translation has +to be. Most of the time, when problems arise, the only way left to make +her judgment is looking at the true program sources from where this +string originated, searching for surrounding comments the programmer +might have put in there, and looking around for helping clues of +any kind. +

+

Surely, when looking at program sources, the translator will receive +more help if she is a fluent programmer. However, even if she is +not versed in programming and feels a little lost in C code, the +translator should not be shy at taking a look, once in a while. +It is most probable that she will still be able to find some of the +hints she needs. She will learn quickly to not feel uncomfortable +in program code, paying more attention to programmer's comments, +variable and function names (if he dared choosing them well), and +overall organization, than to the program code itself. +

+ +

The following commands are meant to help the translator at getting +program source context for a PO file entry. +

+
+
s
+
+

Resume the display of a program source context, or cycle through them +(po-cycle-source-reference). +

+
+
M-s
+
+

Display of a program source context selected by menu +(po-select-source-reference). +

+
+
S
+
+

Add a directory to the search path for source files +(po-consider-source-path). +

+
+
M-S
+
+

Delete a directory from the search path for source files +(po-ignore-source-path). +

+
+
+ + + + + +

The commands s (po-cycle-source-reference) and M-s +(po-select-source-reference) both open another window displaying +some source program file, and already positioned in such a way that +it shows an actual use of the string to be translated. By doing +so, the command gives source program context for the string. But if +the entry has no source context references, or if all references +are unresolved along the search path for program sources, then the +command diagnoses this as an error. +

+

Even if s (or M-s) opens a new window, the cursor stays +in the PO file window. If the translator really wants to +get into the program source window, she ought to do it explicitly, +maybe by using command O. +

+

When s is typed for the first time, or for a PO file entry which +is different of the last one used for getting source context, then the +command reacts by giving the first context available for this entry, +if any. If some context has already been recently displayed for the +current PO file entry, and the translator wandered off to do other +things, typing s again will merely resume, in another window, +the context last displayed. In particular, if the translator moved +the cursor away from the context in the source file, the command will +bring the cursor back to the context. By using s many times +in a row, with no other commands intervening, PO mode will cycle to +the next available contexts for this particular entry, getting back +to the first context once the last has been shown. +

+

The command M-s behaves differently. Instead of cycling through +references, it lets the translator choose a particular reference among +many, and displays that reference. It is best used with completion, +if the translator types <TAB> immediately after M-s, in +response to the question, she will be offered a menu of all possible +references, as a reminder of which are the acceptable answers. +This command is useful only where there are really many contexts +available for a single string to translate. +

+ + + + +

Program source files are usually found relative to where the PO +file stands. As a special provision, when this fails, the file is +also looked for, but relative to the directory immediately above it. +Those two cases take proper care of most PO files. However, it might +happen that a PO file has been moved, or is edited in a different +place than its normal location. When this happens, the translator +should tell PO mode in which directory normally sits the genuine PO +file. Many such directories may be specified, and all together, they +constitute what is called the search path for program sources. +The command S (po-consider-source-path) is used to interactively +enter a new directory at the front of the search path, and the command +M-S (po-ignore-source-path) is used to select, with completion, +one of the directories she does not want anymore on the search path. +

+ + + +

8.7.13 Consulting Auxiliary PO Files

+ +

PO mode is able to help the knowledgeable translator, being fluent in +many languages, at taking advantage of translations already achieved +in other languages she just happens to know. It provides these other +language translations as additional context for her own work. Moreover, +it has features to ease the production of translations for many languages +at once, for translators preferring to work in this way. +

+ + +

An auxiliary PO file is an existing PO file meant for the same +package the translator is working on, but targeted to a different mother +tongue language. Commands exist for declaring and handling auxiliary +PO files, and also for showing contexts for the entry under work. +

+

Here are the auxiliary file commands available in PO mode. +

+
+
a
+
+

Seek auxiliary files for another translation for the same entry +(po-cycle-auxiliary). +

+
+
C-c C-a
+
+

Switch to a particular auxiliary file (po-select-auxiliary). +

+
+
A
+
+

Declare this PO file as an auxiliary file (po-consider-as-auxiliary). +

+
+
M-A
+
+

Remove this PO file from the list of auxiliary files +(po-ignore-as-auxiliary). +

+
+
+ + + + + +

Command A (po-consider-as-auxiliary) adds the current +PO file to the list of auxiliary files, while command M-A +(po-ignore-as-auxiliary just removes it. +

+ + +

The command a (po-cycle-auxiliary) seeks all auxiliary PO +files, round-robin, searching for a translated entry in some other language +having an msgid field identical as the one for the current entry. +The found PO file, if any, takes the place of the current PO file in +the display (its window gets on top). Before doing so, the current PO +file is also made into an auxiliary file, if not already. So, a +in this newly displayed PO file will seek another PO file, and so on, +so repeating a will eventually yield back the original PO file. +

+ + +

The command C-c C-a (po-select-auxiliary) asks the translator +for her choice of a particular auxiliary file, with completion, and +then switches to that selected PO file. The command also checks if +the selected file has an msgid field identical as the one for +the current entry, and if yes, this entry becomes current. Otherwise, +the cursor of the selected file is left undisturbed. +

+

For all this to work fully, auxiliary PO files will have to be normalized, +in that way that msgid fields should be written exactly +the same way. It is possible to write msgid fields in various +ways for representing the same string, different writing would break the +proper behaviour of the auxiliary file commands of PO mode. This is not +expected to be much a problem in practice, as most existing PO files have +their msgid entries written by the same GNU gettext tools. +

+ +

However, PO files initially created by PO mode itself, while marking +strings in source files, are normalised differently. So are PO +files resulting of the ‘M-x normalize’ command. Until these +discrepancies between PO mode and other GNU gettext tools get +fully resolved, the translator should stay aware of normalisation issues. +

+ + + +

8.8 Editing PO Files in vim

+ +

FIXME: Try these scripts. Do they work well? How do they compare? +

+

There are two vim plugins for editing PO files in vim: +

+ + +

Additionally, if you only need syntax highlighting, not editing, of PO files, +there is a vim script for that at +https://www.vim.org/scripts/script.php?script_id=913. +

+ + + +

8.9 Using Translation Compendia

+ +

A compendium is a special PO file containing a set of +translations recurring in many different packages. The translator can +use gettext tools to build a new compendium, to add entries to her +compendium, and to initialize untranslated entries, or to update +already translated entries, from translations kept in the compendium. +

+ + + + +

8.9.1 Creating Compendia

+ +

Basically every PO file consisting of translated entries only can be +declared as a valid compendium. Often the translator wants to have +special compendia; let's consider two cases: concatenating PO +files and extracting a message subset from a PO file. +

+ + +

8.9.1.1 Concatenate PO Files

+ +

To concatenate several valid PO files into one compendium file you can +use ‘msgcomm’ or ‘msgcat’ (the latter preferred): +

+
 
msgcat -o compendium.po file1.po file2.po
+
+ +

By default, msgcat will accumulate divergent translations +for the same string. Those occurrences will be marked as fuzzy +and highly visible decorated; calling msgcat on +‘file1.po’: +

+
 
#: src/hello.c:200
+#, c-format
+msgid "Report bugs to <%s>.\n"
+msgstr "Comunicar `bugs' a <%s>.\n"
+
+ +

and ‘file2.po’: +

+
 
#: src/bye.c:100
+#, c-format
+msgid "Report bugs to <%s>.\n"
+msgstr "Comunicar \"bugs\" a <%s>.\n"
+
+ +

will result in: +

+
 
#: src/hello.c:200 src/bye.c:100
+#, fuzzy, c-format
+msgid "Report bugs to <%s>.\n"
+msgstr ""
+"#-#-#-#-#  file1.po  #-#-#-#-#\n"
+"Comunicar `bugs' a <%s>.\n"
+"#-#-#-#-#  file2.po  #-#-#-#-#\n"
+"Comunicar \"bugs\" a <%s>.\n"
+
+ +

The translator will have to resolve this “conflict” manually; she +has to decide whether the first or the second version is appropriate +(or provide a new translation), to delete the “marker lines”, and +finally to remove the fuzzy mark. +

+

If the translator knows in advance the first found translation of a +message is always the best translation she can make use to the +‘--use-first’ switch: +

+
 
msgcat --use-first -o compendium.po file1.po file2.po
+
+ +

A good compendium file must not contain fuzzy or untranslated +entries. If input files are “dirty” you must preprocess the input +files or postprocess the result using ‘msgattrib --translated --no-fuzzy’. +

+ + +

8.9.1.2 Extract a Message Subset from a PO File

+ +

Nobody wants to translate the same messages again and again; thus you +may wish to have a compendium file containing ‘getopt.c’ messages. +

+

To extract a message subset (e.g., all ‘getopt.c’ messages) from an +existing PO file into one compendium file you can use ‘msggrep’: +

+
 
msggrep --location src/getopt.c -o compendium.po file.po
+
+ + + + +

8.9.2 Using Compendia

+ +

You can use a compendium file to initialize a translation from scratch +or to update an already existing translation. +

+ + +

8.9.2.1 Initialize a New Translation File

+ +

Since a PO file with translations does not exist the translator can +merely use ‘/dev/null’ to fake the “old” translation file. +

+
 
msgmerge --compendium compendium.po -o file.po /dev/null file.pot
+
+ + + +

8.9.2.2 Update an Existing Translation File

+ +

Concatenate the compendium file(s) and the existing PO, merge the +result with the POT file and remove the obsolete entries (optional, +here done using ‘msgattrib’): +

+
 
msgcat --use-first -o update.po compendium1.po compendium2.po file.po
+msgmerge update.po file.pot | msgattrib --no-obsolete > file.po
+
+ + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_9.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_9.html new file mode 100644 index 0000000000000000000000000000000000000000..61254a277e5d35b099d9fc0cf5ded0a94b02bbc5 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_9.html @@ -0,0 +1,3735 @@ + + + + + +GNU gettext utilities: 9. Manipulating PO Files + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+ +
+ + +

9. Manipulating PO Files

+ +

Sometimes it is necessary to manipulate PO files in a way that is better +performed automatically than by hand. GNU gettext includes a +complete set of tools for this purpose. +

+ + +

When merging two packages into a single package, the resulting POT file +will be the concatenation of the two packages' POT files. Thus the +maintainer must concatenate the two existing package translations into +a single translation catalog, for each language. This is best performed +using ‘msgcat’. It is then the translators' duty to deal with any +possible conflicts that arose during the merge. +

+ +

When a translator takes over the translation job from another translator, +but she uses a different character encoding in her locale, she will +convert the catalog to her character encoding. This is best done through +the ‘msgconv’ program. +

+

When a maintainer takes a source file with tagged messages from another +package, he should also take the existing translations for this source +file (and not let the translators do the same job twice). One way to do +this is through ‘msggrep’, another is to create a POT file for +that source file and use ‘msgmerge’. +

+ + +

When a translator wants to adjust some translation catalog for a special +dialect or orthography — for example, German as written in Switzerland +versus German as written in Germany — she needs to apply some text +processing to every message in the catalog. The tool for doing this is +‘msgfilter’. +

+

Another use of msgfilter is to produce approximately the POT file for +which a given PO file was made. This can be done through a filter command +like ‘msgfilter sed -e d | sed -e '/^# /d'’. Note that the original +POT file may have had different comments and different plural message counts, +that's why it's better to use the original POT file if available. +

+ +

When a translator wants to check her translations, for example according +to orthography rules or using a non-interactive spell checker, she can do +so using the ‘msgexec’ program. +

+ +

When third party tools create PO or POT files, sometimes duplicates cannot +be avoided. But the GNU gettext tools give an error when they +encounter duplicate msgids in the same file and in the same domain. +To merge duplicates, the ‘msguniq’ program can be used. +

+

‘msgcomm’ is a more general tool for keeping or throwing away +duplicates, occurring in different files. +

+

‘msgcmp’ can be used to check whether a translation catalog is +completely translated. +

+ +

‘msgattrib’ can be used to select and extract only the fuzzy +or untranslated messages of a translation catalog. +

+

‘msgen’ is useful as a first step for preparing English translation +catalogs. It copies each message's msgid to its msgstr. +

+

Finally, for those applications where all these various programs are not +sufficient, a library ‘libgettextpo’ is provided that can be used to +write other specialized programs that process PO files. +

+ + + + +

9.1 Invoking the msgcat Program

+ + +
 
msgcat [option] [inputfile]...
+
+ + + +

The msgcat program concatenates and merges the specified PO files. +It finds messages which are common to two or more of the specified PO files. +By using the --more-than option, greater commonality may be requested +before messages are printed. Conversely, the --less-than option may be +used to specify less commonality before messages are printed (i.e. +‘--less-than=2’ will only print the unique messages). Translations, +comments, extracted comments, and file positions will be cumulated, except that +if --use-first is specified, they will be taken from the first PO file +to define them. +

+

To concatenate POT files, better use xgettext, not msgcat, +because msgcat would choke on the undefined charsets in the specified +POT files. +

+ + +

9.1.1 Input file location

+ +
+
‘inputfile …’
+

Input files. +

+
+
‘-f file’
+
‘--files-from=file’
+
+ +

Read the names of the input files from file instead of getting +them from the command line. +

+
+
‘-D directory’
+
‘--directory=directory’
+
+ +

Add directory to the list of directories. Source files are +searched relative to this list of directories. The resulting ‘.po’ +file will be written relative to the current directory, though. +

+
+
+ +

If inputfile is ‘-’, standard input is read. +

+ + +

9.1.2 Output file location

+ +
+
‘-o file’
+
‘--output-file=file’
+
+ +

Write output to specified file. +

+
+
+ + +

The results are written to standard output if no output file is specified +or if it is ‘-’. +

+ + +

9.1.3 Message selection

+ +
+
‘-< number’
+
‘--less-than=number’
+
+ +

Print messages with less than number definitions, defaults to infinite +if not set. +

+
+
‘-> number’
+
‘--more-than=number’
+
+ +

Print messages with more than number definitions, defaults to 0 if not +set. +

+
+
‘-u’
+
‘--unique’
+
+ +

Shorthand for ‘--less-than=2’. Requests that only unique messages be +printed. +

+
+
+ + + +

9.1.4 Input file syntax

+ +
+
‘-P’
+
‘--properties-input’
+
+ +

Assume the input files are Java ResourceBundles in Java .properties +syntax, not in PO file syntax. +

+
+
‘--stringtable-input’
+
+

Assume the input files are NeXTstep/GNUstep localized resource files in +.strings syntax, not in PO file syntax. +

+
+
+ + + +

9.1.5 Output details

+ + +
+
‘-t’
+
‘--to-code=name’
+
+ +

Specify encoding for output. +

+
+
‘--use-first’
+
+

Use first available translation for each message. Don't merge several +translations into one. +

+
+
‘--lang=catalogname’
+
+

Specify the ‘Language’ field to be used in the header entry. See +Filling in the Header Entry for the meaning of this field. Note: The +‘Language-Team’ and ‘Plural-Forms’ fields are left unchanged. +

+
+
‘--color’
+
‘--color=when’
+
+

Specify whether or when to use colors and other text attributes. +See The --color option for details. +

+
+
‘--style=style_file’
+
+

Specify the CSS style rule file to use for --color. +See The --style option for details. +

+
+
‘--force-po’
+
+

Always write an output file even if it contains no message. +

+
+
‘-i’
+
‘--indent’
+
+ +

Write the .po file using indented style. +

+
+
‘--no-location’
+
+

Do not write ‘#: filename:line’ lines. +

+
+
‘-n’
+
‘--add-location=type’
+
+ +

Generate ‘#: filename:line’ lines (default). +

+

The optional type can be either ‘full’, ‘file’, or +‘never’. If it is not given or ‘full’, it generates the +lines with both file name and line number. If it is ‘file’, the +line number part is omitted. If it is ‘never’, it completely +suppresses the lines (same as --no-location). +

+
+
‘--strict’
+
+

Write out a strict Uniforum conforming PO file. Note that this +Uniforum format should be avoided because it doesn't support the +GNU extensions. +

+
+
‘-p’
+
‘--properties-output’
+
+ +

Write out a Java ResourceBundle in Java .properties syntax. Note +that this file format doesn't support plural forms and silently drops +obsolete messages. +

+
+
‘--stringtable-output’
+
+

Write out a NeXTstep/GNUstep localized resource file in .strings syntax. +Note that this file format doesn't support plural forms. +

+
+
‘-w number’
+
‘--width=number’
+
+ +

Set the output page width. Long strings in the output files will be +split across multiple lines in order to ensure that each line's width +(= number of screen columns) is less or equal to the given number. +

+
+
‘--no-wrap’
+
+

Do not break long message lines. Message lines whose width exceeds the +output page width will not be split into several lines. Only file reference +lines which are wider than the output page width will be split. +

+
+
‘-s’
+
‘--sort-output’
+
+ + +

Generate sorted output. Note that using this option makes it much harder +for the translator to understand each message's context. +

+
+
‘-F’
+
‘--sort-by-file’
+
+ +

Sort output by file location. +

+
+
+ + + +

9.1.6 Informative output

+ +
+
‘-h’
+
‘--help’
+
+ +

Display this help and exit. +

+
+
‘-V’
+
‘--version’
+
+ +

Output version information and exit. +

+
+
+ + + + +

9.2 Invoking the msgconv Program

+ + +
 
msgconv [option] [inputfile]
+
+ + +

The msgconv program converts a translation catalog to a different +character encoding. +

+ + +

9.2.1 Input file location

+ +
+
‘inputfile’
+

Input PO file. +

+
+
‘-D directory’
+
‘--directory=directory’
+
+ +

Add directory to the list of directories. Source files are +searched relative to this list of directories. The resulting ‘.po’ +file will be written relative to the current directory, though. +

+
+
+ +

If no inputfile is given or if it is ‘-’, standard input is read. +

+ + +

9.2.2 Output file location

+ +
+
‘-o file’
+
‘--output-file=file’
+
+ +

Write output to specified file. +

+
+
+ +

The results are written to standard output if no output file is specified +or if it is ‘-’. +

+ + +

9.2.3 Conversion target

+ +
+
‘-t’
+
‘--to-code=name’
+
+ +

Specify encoding for output. +

+
+
+ +

The default encoding is the current locale's encoding. +

+ + +

9.2.4 Input file syntax

+ +
+
‘-P’
+
‘--properties-input’
+
+ +

Assume the input file is a Java ResourceBundle in Java .properties +syntax, not in PO file syntax. +

+
+
‘--stringtable-input’
+
+

Assume the input file is a NeXTstep/GNUstep localized resource file in +.strings syntax, not in PO file syntax. +

+
+
+ + + +

9.2.5 Output details

+ + +
+
‘--color’
+
‘--color=when’
+
+

Specify whether or when to use colors and other text attributes. +See The --color option for details. +

+
+
‘--style=style_file’
+
+

Specify the CSS style rule file to use for --color. +See The --style option for details. +

+
+
‘--force-po’
+
+

Always write an output file even if it contains no message. +

+
+
‘-i’
+
‘--indent’
+
+ +

Write the .po file using indented style. +

+
+
‘--no-location’
+
+

Do not write ‘#: filename:line’ lines. +

+
+
‘-n’
+
‘--add-location=type’
+
+

Generate ‘#: filename:line’ lines (default). +

+

The optional type can be either ‘full’, ‘file’, or +‘never’. If it is not given or ‘full’, it generates the +lines with both file name and line number. If it is ‘file’, the +line number part is omitted. If it is ‘never’, it completely +suppresses the lines (same as --no-location). +

+
+
‘--strict’
+
+

Write out a strict Uniforum conforming PO file. Note that this +Uniforum format should be avoided because it doesn't support the +GNU extensions. +

+
+
‘-p’
+
‘--properties-output’
+
+ +

Write out a Java ResourceBundle in Java .properties syntax. Note +that this file format doesn't support plural forms and silently drops +obsolete messages. +

+
+
‘--stringtable-output’
+
+

Write out a NeXTstep/GNUstep localized resource file in .strings syntax. +Note that this file format doesn't support plural forms. +

+
+
‘-w number’
+
‘--width=number’
+
+ +

Set the output page width. Long strings in the output files will be +split across multiple lines in order to ensure that each line's width +(= number of screen columns) is less or equal to the given number. +

+
+
‘--no-wrap’
+
+

Do not break long message lines. Message lines whose width exceeds the +output page width will not be split into several lines. Only file reference +lines which are wider than the output page width will be split. +

+
+
‘-s’
+
‘--sort-output’
+
+ +

Generate sorted output. Note that using this option makes it much harder +for the translator to understand each message's context. +

+
+
‘-F’
+
‘--sort-by-file’
+
+ +

Sort output by file location. +

+
+
+ + + +

9.2.6 Informative output

+ +
+
‘-h’
+
‘--help’
+
+ +

Display this help and exit. +

+
+
‘-V’
+
‘--version’
+
+ +

Output version information and exit. +

+
+
+ + + + +

9.3 Invoking the msggrep Program

+ + +
 
msggrep [option] [inputfile]
+
+ + +

The msggrep program extracts all messages of a translation catalog +that match a given pattern or belong to some given source files. +

+ + +

9.3.1 Input file location

+ +
+
‘inputfile’
+

Input PO file. +

+
+
‘-D directory’
+
‘--directory=directory’
+
+ +

Add directory to the list of directories. Source files are +searched relative to this list of directories. The resulting ‘.po’ +file will be written relative to the current directory, though. +

+
+
+ +

If no inputfile is given or if it is ‘-’, standard input is read. +

+ + +

9.3.2 Output file location

+ +
+
‘-o file’
+
‘--output-file=file’
+
+ +

Write output to specified file. +

+
+
+ +

The results are written to standard output if no output file is specified +or if it is ‘-’. +

+ + +

9.3.3 Message selection

+ +
 
  [-N sourcefile]... [-M domainname]...
+  [-J msgctxt-pattern] [-K msgid-pattern] [-T msgstr-pattern]
+  [-C comment-pattern]
+
+ +

A message is selected if +

    +
  • it comes from one of the specified source files, +
  • or if it comes from one of the specified domains, +
  • or if ‘-J’ is given and its context (msgctxt) matches +msgctxt-pattern, +
  • or if ‘-K’ is given and its key (msgid or msgid_plural) matches +msgid-pattern, +
  • or if ‘-T’ is given and its translation (msgstr) matches +msgstr-pattern, +
  • or if ‘-C’ is given and the translator's comment matches +comment-pattern. +
+ +

When more than one selection criterion is specified, the set of selected +messages is the union of the selected messages of each criterion. +

+

msgctxt-pattern or msgid-pattern or msgstr-pattern syntax: +

 
  [-E | -F] [-e pattern | -f file]...
+
+

patterns are basic regular expressions by default, or extended regular +expressions if -E is given, or fixed strings if -F is given. +

+
+
‘-N sourcefile’
+
‘--location=sourcefile’
+
+ +

Select messages extracted from sourcefile. sourcefile can be +either a literal file name or a wildcard pattern. +

+
+
‘-M domainname’
+
‘--domain=domainname’
+
+ +

Select messages belonging to domain domainname. +

+
+
‘-J’
+
‘--msgctxt’
+
+ +

Start of patterns for the msgctxt. +

+
+
‘-K’
+
‘--msgid’
+
+ +

Start of patterns for the msgid. +

+
+
‘-T’
+
‘--msgstr’
+
+ +

Start of patterns for the msgstr. +

+
+
‘-C’
+
‘--comment’
+
+ +

Start of patterns for the translator's comment. +

+
+
‘-X’
+
‘--extracted-comment’
+
+ +

Start of patterns for the extracted comments. +

+
+
‘-E’
+
‘--extended-regexp’
+
+ +

Specify that pattern is an extended regular expression. +

+
+
‘-F’
+
‘--fixed-strings’
+
+ +

Specify that pattern is a set of newline-separated strings. +

+
+
‘-e pattern’
+
‘--regexp=pattern’
+
+ +

Use pattern as a regular expression. +

+
+
‘-f file’
+
‘--file=file’
+
+ +

Obtain pattern from file. +

+
+
‘-i’
+
‘--ignore-case’
+
+ +

Ignore case distinctions. +

+
+
‘-v’
+
‘--invert-match’
+
+ +

Output only the messages that do not match any selection criterion, instead +of the messages that match a selection criterion. +

+
+
+ + + +

9.3.4 Input file syntax

+ +
+
‘-P’
+
‘--properties-input’
+
+ +

Assume the input file is a Java ResourceBundle in Java .properties +syntax, not in PO file syntax. +

+
+
‘--stringtable-input’
+
+

Assume the input file is a NeXTstep/GNUstep localized resource file in +.strings syntax, not in PO file syntax. +

+
+
+ + + +

9.3.5 Output details

+ + +
+
‘--color’
+
‘--color=when’
+
+

Specify whether or when to use colors and other text attributes. +See The --color option for details. +

+
+
‘--style=style_file’
+
+

Specify the CSS style rule file to use for --color. +See The --style option for details. +

+
+
‘--force-po’
+
+

Always write an output file even if it contains no message. +

+
+
‘--indent’
+
+

Write the .po file using indented style. +

+
+
‘--no-location’
+
+

Do not write ‘#: filename:line’ lines. +

+
+
‘-n’
+
‘--add-location=type’
+
+

Generate ‘#: filename:line’ lines (default). +

+

The optional type can be either ‘full’, ‘file’, or +‘never’. If it is not given or ‘full’, it generates the +lines with both file name and line number. If it is ‘file’, the +line number part is omitted. If it is ‘never’, it completely +suppresses the lines (same as --no-location). +

+
+
‘--strict’
+
+

Write out a strict Uniforum conforming PO file. Note that this +Uniforum format should be avoided because it doesn't support the +GNU extensions. +

+
+
‘-p’
+
‘--properties-output’
+
+ +

Write out a Java ResourceBundle in Java .properties syntax. Note +that this file format doesn't support plural forms and silently drops +obsolete messages. +

+
+
‘--stringtable-output’
+
+

Write out a NeXTstep/GNUstep localized resource file in .strings syntax. +Note that this file format doesn't support plural forms. +

+
+
‘-w number’
+
‘--width=number’
+
+ +

Set the output page width. Long strings in the output files will be +split across multiple lines in order to ensure that each line's width +(= number of screen columns) is less or equal to the given number. +

+
+
‘--no-wrap’
+
+

Do not break long message lines. Message lines whose width exceeds the +output page width will not be split into several lines. Only file reference +lines which are wider than the output page width will be split. +

+
+
‘--sort-output’
+
+

Generate sorted output. Note that using this option makes it much harder +for the translator to understand each message's context. +

+
+
‘--sort-by-file’
+
+

Sort output by file location. +

+
+
+ + + +

9.3.6 Informative output

+ +
+
‘-h’
+
‘--help’
+
+ +

Display this help and exit. +

+
+
‘-V’
+
‘--version’
+
+ +

Output version information and exit. +

+
+
+ + + +

9.3.7 Examples

+ +

To extract the messages that come from the source files +gnulib-lib/error.c and gnulib-lib/getopt.c: +

+
 
msggrep -N gnulib-lib/error.c -N gnulib-lib/getopt.c input.po
+
+ +

To extract the messages that contain the string “Please specify” in the +original string: +

+
 
msggrep --msgid -F -e 'Please specify' input.po
+
+ +

To extract the messages that have a context specifier of either “Menu>File” +or “Menu>Edit” or a submenu of them: +

+
 
msggrep --msgctxt -E -e '^Menu>(File|Edit)' input.po
+
+ +

To extract the messages whose translation contains one of the strings in the +file wordlist.txt: +

+
 
msggrep --msgstr -F -f wordlist.txt input.po
+
+ + + + +

9.4 Invoking the msgfilter Program

+ + +
 
msgfilter [option] filter [filter-option]
+
+ + +

The msgfilter program applies a filter to all translations of a +translation catalog. +

+ + + + + + + + +

During each filter invocation, the environment variable +MSGFILTER_MSGID is bound to the message's msgid, and the environment +variable MSGFILTER_LOCATION is bound to the location in the PO file +of the message. If the message has a context, the environment variable +MSGFILTER_MSGCTXT is bound to the message's msgctxt, otherwise it is +unbound. If the message has a plural form, environment variable +MSGFILTER_MSGID_PLURAL is bound to the message's msgid_plural and +MSGFILTER_PLURAL_FORM is bound to the order number of the plural +actually processed (starting with 0), otherwise both are unbound. +If the message has a previous msgid (added by msgmerge), +environment variable MSGFILTER_PREV_MSGCTXT is bound to the +message's previous msgctxt, MSGFILTER_PREV_MSGID is bound to +the previous msgid, and MSGFILTER_PREV_MSGID_PLURAL is bound to +the previous msgid_plural. +

+ + +

9.4.1 Input file location

+ +
+
‘-i inputfile’
+
‘--input=inputfile’
+
+ +

Input PO file. +

+
+
‘-D directory’
+
‘--directory=directory’
+
+ +

Add directory to the list of directories. Source files are +searched relative to this list of directories. The resulting ‘.po’ +file will be written relative to the current directory, though. +

+
+
+ +

If no inputfile is given or if it is ‘-’, standard input is read. +

+ + +

9.4.2 Output file location

+ +
+
‘-o file’
+
‘--output-file=file’
+
+ +

Write output to specified file. +

+
+
+ +

The results are written to standard output if no output file is specified +or if it is ‘-’. +

+ + +

9.4.3 The filter

+ +

The filter can be any program that reads a translation from standard +input and writes a modified translation to standard output. A frequently +used filter is ‘sed’. A few particular built-in filters are also +recognized. +

+
+
‘--newline’
+
+

Add newline at the end of each input line and also strip the ending +newline from the output line. +

+
+
+ + +

Note: If the filter is not a built-in filter, you have to care about encodings: +It is your responsibility to ensure that the filter can cope +with input encoded in the translation catalog's encoding. If the +filter wants input in a particular encoding, you can in a first step +convert the translation catalog to that encoding using the ‘msgconv’ +program, before invoking ‘msgfilter’. If the filter wants input +in the locale's encoding, but you want to avoid the locale's encoding, then +you can first convert the translation catalog to UTF-8 using the +‘msgconv’ program and then make ‘msgfilter’ work in an UTF-8 +locale, by using the LC_ALL environment variable. +

+ +

Note: Most translations in a translation catalog don't end with a +newline character. For this reason, unless the --newline +option is used, it is important that the filter recognizes its +last input line even if it ends without a newline, and that it doesn't +add an undesired trailing newline at the end. The ‘sed’ program on +some platforms is known to ignore the last line of input if it is not +terminated with a newline. You can use GNU sed instead; it does +not have this limitation. +

+ + +

9.4.4 Useful filter-options when the filter is ‘sed’

+ +
+
‘-e script’
+
‘--expression=script’
+
+ +

Add script to the commands to be executed. +

+
+
‘-f scriptfile’
+
‘--file=scriptfile’
+
+ +

Add the contents of scriptfile to the commands to be executed. +

+
+
‘-n’
+
‘--quiet’
+
‘--silent’
+
+ + +

Suppress automatic printing of pattern space. +

+
+
+ + + +

9.4.5 Built-in filters

+ +

The filter ‘recode-sr-latin’ is recognized as a built-in filter. +The command ‘recode-sr-latin’ converts Serbian text, written in the +Cyrillic script, to the Latin script. +The command ‘msgfilter recode-sr-latin’ applies this conversion to the +translations of a PO file. Thus, it can be used to convert an ‘sr.po’ +file to an ‘sr@latin.po’ file. +

+ +

The filter ‘quot’ is recognized as a built-in filter. +The command ‘msgfilter quot’ converts any quotations surrounded +by a pair of ‘"’, ‘'’, and ‘`’. +

+ +

The filter ‘boldquot’ is recognized as a built-in filter. +The command ‘msgfilter boldquot’ converts any quotations +surrounded by a pair of ‘"’, ‘'’, and ‘`’, also adding the +VT100 escape sequences to the text to decorate it as bold. +

+

The use of built-in filters is not sensitive to the current locale's encoding. +Moreover, when used with a built-in filter, ‘msgfilter’ can automatically +convert the message catalog to the UTF-8 encoding when needed. +

+ + +

9.4.6 Input file syntax

+ +
+
‘-P’
+
‘--properties-input’
+
+ +

Assume the input file is a Java ResourceBundle in Java .properties +syntax, not in PO file syntax. +

+
+
‘--stringtable-input’
+
+

Assume the input file is a NeXTstep/GNUstep localized resource file in +.strings syntax, not in PO file syntax. +

+
+
+ + + +

9.4.7 Output details

+ + +
+
‘--color’
+
‘--color=when’
+
+

Specify whether or when to use colors and other text attributes. +See The --color option for details. +

+
+
‘--style=style_file’
+
+

Specify the CSS style rule file to use for --color. +See The --style option for details. +

+
+
‘--force-po’
+
+

Always write an output file even if it contains no message. +

+
+
‘--indent’
+
+

Write the .po file using indented style. +

+
+
‘--keep-header’
+
+

Keep the header entry, i.e. the message with ‘msgid ""’, unmodified, +instead of filtering it. By default, the header entry is subject to +filtering like any other message. +

+
+
‘--no-location’
+
+

Do not write ‘#: filename:line’ lines. +

+
+
‘-n’
+
‘--add-location=type’
+
+

Generate ‘#: filename:line’ lines (default). +

+

The optional type can be either ‘full’, ‘file’, or +‘never’. If it is not given or ‘full’, it generates the +lines with both file name and line number. If it is ‘file’, the +line number part is omitted. If it is ‘never’, it completely +suppresses the lines (same as --no-location). +

+
+
‘--strict’
+
+

Write out a strict Uniforum conforming PO file. Note that this +Uniforum format should be avoided because it doesn't support the +GNU extensions. +

+
+
‘-p’
+
‘--properties-output’
+
+ +

Write out a Java ResourceBundle in Java .properties syntax. Note +that this file format doesn't support plural forms and silently drops +obsolete messages. +

+
+
‘--stringtable-output’
+
+

Write out a NeXTstep/GNUstep localized resource file in .strings syntax. +Note that this file format doesn't support plural forms. +

+
+
‘-w number’
+
‘--width=number’
+
+ +

Set the output page width. Long strings in the output files will be +split across multiple lines in order to ensure that each line's width +(= number of screen columns) is less or equal to the given number. +

+
+
‘--no-wrap’
+
+

Do not break long message lines. Message lines whose width exceeds the +output page width will not be split into several lines. Only file reference +lines which are wider than the output page width will be split. +

+
+
‘-s’
+
‘--sort-output’
+
+ +

Generate sorted output. Note that using this option makes it much harder +for the translator to understand each message's context. +

+
+
‘-F’
+
‘--sort-by-file’
+
+ +

Sort output by file location. +

+
+
+ + + +

9.4.8 Informative output

+ +
+
‘-h’
+
‘--help’
+
+ +

Display this help and exit. +

+
+
‘-V’
+
‘--version’
+
+ +

Output version information and exit. +

+
+
+ + + +

9.4.9 Examples

+ +

To convert German translations to Swiss orthography (in an UTF-8 locale): +

+
 
msgconv -t UTF-8 de.po | msgfilter sed -e 's/ß/ss/g'
+
+ +

To convert Serbian translations in Cyrillic script to Latin script: +

+
 
msgfilter recode-sr-latin < sr.po
+
+ + + + +

9.5 Invoking the msguniq Program

+ + +
 
msguniq [option] [inputfile]
+
+ + + +

The msguniq program unifies duplicate translations in a translation +catalog. It finds duplicate translations of the same message ID. Such +duplicates are invalid input for other programs like msgfmt, +msgmerge or msgcat. By default, duplicates are merged +together. When using the ‘--repeated’ option, only duplicates are +output, and all other messages are discarded. Comments and extracted +comments will be cumulated, except that if ‘--use-first’ is +specified, they will be taken from the first translation. File positions +will be cumulated. When using the ‘--unique’ option, duplicates are +discarded. +

+ + +

9.5.1 Input file location

+ +
+
‘inputfile’
+

Input PO file. +

+
+
‘-D directory’
+
‘--directory=directory’
+
+ +

Add directory to the list of directories. Source files are +searched relative to this list of directories. The resulting ‘.po’ +file will be written relative to the current directory, though. +

+
+
+ +

If no inputfile is given or if it is ‘-’, standard input is read. +

+ + +

9.5.2 Output file location

+ +
+
‘-o file’
+
‘--output-file=file’
+
+ +

Write output to specified file. +

+
+
+ +

The results are written to standard output if no output file is specified +or if it is ‘-’. +

+ + +

9.5.3 Message selection

+ +
+
‘-d’
+
‘--repeated’
+
+ +

Print only duplicates. +

+
+
‘-u’
+
‘--unique’
+
+ +

Print only unique messages, discard duplicates. +

+
+
+ + + +

9.5.4 Input file syntax

+ +
+
‘-P’
+
‘--properties-input’
+
+ +

Assume the input file is a Java ResourceBundle in Java .properties +syntax, not in PO file syntax. +

+
+
‘--stringtable-input’
+
+

Assume the input file is a NeXTstep/GNUstep localized resource file in +.strings syntax, not in PO file syntax. +

+
+
+ + + +

9.5.5 Output details

+ + +
+
‘-t’
+
‘--to-code=name’
+
+ +

Specify encoding for output. +

+
+
‘--use-first’
+
+

Use first available translation for each message. Don't merge several +translations into one. +

+
+
‘--color’
+
‘--color=when’
+
+

Specify whether or when to use colors and other text attributes. +See The --color option for details. +

+
+
‘--style=style_file’
+
+

Specify the CSS style rule file to use for --color. +See The --style option for details. +

+
+
‘--force-po’
+
+

Always write an output file even if it contains no message. +

+
+
‘-i’
+
‘--indent’
+
+ +

Write the .po file using indented style. +

+
+
‘--no-location’
+
+

Do not write ‘#: filename:line’ lines. +

+
+
‘-n’
+
‘--add-location=type’
+
+ +

Generate ‘#: filename:line’ lines (default). +

+

The optional type can be either ‘full’, ‘file’, or +‘never’. If it is not given or ‘full’, it generates the +lines with both file name and line number. If it is ‘file’, the +line number part is omitted. If it is ‘never’, it completely +suppresses the lines (same as --no-location). +

+
+
‘--strict’
+
+

Write out a strict Uniforum conforming PO file. Note that this +Uniforum format should be avoided because it doesn't support the +GNU extensions. +

+
+
‘-p’
+
‘--properties-output’
+
+ +

Write out a Java ResourceBundle in Java .properties syntax. Note +that this file format doesn't support plural forms and silently drops +obsolete messages. +

+
+
‘--stringtable-output’
+
+

Write out a NeXTstep/GNUstep localized resource file in .strings syntax. +Note that this file format doesn't support plural forms. +

+
+
‘-w number’
+
‘--width=number’
+
+ +

Set the output page width. Long strings in the output files will be +split across multiple lines in order to ensure that each line's width +(= number of screen columns) is less or equal to the given number. +

+
+
‘--no-wrap’
+
+

Do not break long message lines. Message lines whose width exceeds the +output page width will not be split into several lines. Only file reference +lines which are wider than the output page width will be split. +

+
+
‘-s’
+
‘--sort-output’
+
+ +

Generate sorted output. Note that using this option makes it much harder +for the translator to understand each message's context. +

+
+
‘-F’
+
‘--sort-by-file’
+
+ +

Sort output by file location. +

+
+
+ + + +

9.5.6 Informative output

+ +
+
‘-h’
+
‘--help’
+
+ +

Display this help and exit. +

+
+
‘-V’
+
‘--version’
+
+ +

Output version information and exit. +

+
+
+ + + + +

9.6 Invoking the msgcomm Program

+ + +
 
msgcomm [option] [inputfile]...
+
+ + +

The msgcomm program finds messages which are common to two or more +of the specified PO files. +By using the --more-than option, greater commonality may be requested +before messages are printed. Conversely, the --less-than option may be +used to specify less commonality before messages are printed (i.e. +‘--less-than=2’ will only print the unique messages). Translations, +comments and extracted comments will be preserved, but only from the first +PO file to define them. File positions from all PO files will be +cumulated. +

+ + +

9.6.1 Input file location

+ +
+
‘inputfile …’
+

Input files. +

+
+
‘-f file’
+
‘--files-from=file’
+
+ +

Read the names of the input files from file instead of getting +them from the command line. +

+
+
‘-D directory’
+
‘--directory=directory’
+
+ +

Add directory to the list of directories. Source files are +searched relative to this list of directories. The resulting ‘.po’ +file will be written relative to the current directory, though. +

+
+
+ +

If inputfile is ‘-’, standard input is read. +

+ + +

9.6.2 Output file location

+ +
+
‘-o file’
+
‘--output-file=file’
+
+ +

Write output to specified file. +

+
+
+ +

The results are written to standard output if no output file is specified +or if it is ‘-’. +

+ + +

9.6.3 Message selection

+ +
+
‘-< number’
+
‘--less-than=number’
+
+ +

Print messages with less than number definitions, defaults to infinite +if not set. +

+
+
‘-> number’
+
‘--more-than=number’
+
+ +

Print messages with more than number definitions, defaults to 1 if not +set. +

+
+
‘-u’
+
‘--unique’
+
+ +

Shorthand for ‘--less-than=2’. Requests that only unique messages be +printed. +

+
+
+ + + +

9.6.4 Input file syntax

+ +
+
‘-P’
+
‘--properties-input’
+
+ +

Assume the input files are Java ResourceBundles in Java .properties +syntax, not in PO file syntax. +

+
+
‘--stringtable-input’
+
+

Assume the input files are NeXTstep/GNUstep localized resource files in +.strings syntax, not in PO file syntax. +

+
+
+ + + +

9.6.5 Output details

+ + +
+
‘--color’
+
‘--color=when’
+
+

Specify whether or when to use colors and other text attributes. +See The --color option for details. +

+
+
‘--style=style_file’
+
+

Specify the CSS style rule file to use for --color. +See The --style option for details. +

+
+
‘--force-po’
+
+

Always write an output file even if it contains no message. +

+
+
‘-i’
+
‘--indent’
+
+ +

Write the .po file using indented style. +

+
+
‘--no-location’
+
+

Do not write ‘#: filename:line’ lines. +

+
+
‘-n’
+
‘--add-location=type’
+
+ +

Generate ‘#: filename:line’ lines (default). +

+

The optional type can be either ‘full’, ‘file’, or +‘never’. If it is not given or ‘full’, it generates the +lines with both file name and line number. If it is ‘file’, the +line number part is omitted. If it is ‘never’, it completely +suppresses the lines (same as --no-location). +

+
+
‘--strict’
+
+

Write out a strict Uniforum conforming PO file. Note that this +Uniforum format should be avoided because it doesn't support the +GNU extensions. +

+
+
‘-p’
+
‘--properties-output’
+
+ +

Write out a Java ResourceBundle in Java .properties syntax. Note +that this file format doesn't support plural forms and silently drops +obsolete messages. +

+
+
‘--stringtable-output’
+
+

Write out a NeXTstep/GNUstep localized resource file in .strings syntax. +Note that this file format doesn't support plural forms. +

+
+
‘-w number’
+
‘--width=number’
+
+ +

Set the output page width. Long strings in the output files will be +split across multiple lines in order to ensure that each line's width +(= number of screen columns) is less or equal to the given number. +

+
+
‘--no-wrap’
+
+

Do not break long message lines. Message lines whose width exceeds the +output page width will not be split into several lines. Only file reference +lines which are wider than the output page width will be split. +

+
+
‘-s’
+
‘--sort-output’
+
+ +

Generate sorted output. Note that using this option makes it much harder +for the translator to understand each message's context. +

+
+
‘-F’
+
‘--sort-by-file’
+
+ +

Sort output by file location. +

+
+
‘--omit-header’
+
+

Don't write header with ‘msgid ""’ entry. +Note: Using this option may lead to an error in subsequent operations +if the output contains non-ASCII characters. +

+
+
+ + + +

9.6.6 Informative output

+ +
+
‘-h’
+
‘--help’
+
+ +

Display this help and exit. +

+
+
‘-V’
+
‘--version’
+
+ +

Output version information and exit. +

+
+
+ + + + +

9.7 Invoking the msgcmp Program

+ + +
 
msgcmp [option] def.po ref.pot
+
+ + +

The msgcmp program compares two Uniforum style .po files to check that +both contain the same set of msgid strings. The def.po file is an +existing PO file with the translations. The ref.pot file is the last +created PO file, or a PO Template file (generally created by xgettext). +This is useful for checking that you have translated each and every message +in your program. Where an exact match cannot be found, fuzzy matching is +used to produce better diagnostics. +

+ + +

9.7.1 Input file location

+ +
+
‘def.po’
+

Translations. +

+
+
‘ref.pot’
+

References to the sources. +

+
+
‘-D directory’
+
‘--directory=directory’
+
+ +

Add directory to the list of directories. Source files are +searched relative to this list of directories. +

+
+
+ + + +

9.7.2 Operation modifiers

+ +
+
‘-m’
+
‘--multi-domain’
+
+ +

Apply ref.pot to each of the domains in def.po. +

+
+
‘-N’
+
‘--no-fuzzy-matching’
+
+ +

Do not use fuzzy matching when an exact match is not found. This may speed +up the operation considerably. +

+
+
‘--use-fuzzy’
+
+

Consider fuzzy messages in the def.po file like translated messages. +Note that using this option is usually wrong, because fuzzy messages are +exactly those which have not been validated by a human translator. +

+
+
‘--use-untranslated’
+
+

Consider untranslated messages in the def.po file like translated +messages. Note that using this option is usually wrong. +

+
+
+ + + +

9.7.3 Input file syntax

+ +
+
‘-P’
+
‘--properties-input’
+
+ +

Assume the input files are Java ResourceBundles in Java .properties +syntax, not in PO file syntax. +

+
+
‘--stringtable-input’
+
+

Assume the input files are NeXTstep/GNUstep localized resource files in +.strings syntax, not in PO file syntax. +

+
+
+ + + +

9.7.4 Informative output

+ +
+
‘-h’
+
‘--help’
+
+ +

Display this help and exit. +

+
+
‘-V’
+
‘--version’
+
+ +

Output version information and exit. +

+
+
+ + + + +

9.8 Invoking the msgattrib Program

+ + +
 
msgattrib [option] [inputfile]
+
+ + + +

The msgattrib program filters the messages of a translation catalog +according to their attributes, and manipulates the attributes. +

+ + +

9.8.1 Input file location

+ +
+
‘inputfile’
+

Input PO file. +

+
+
‘-D directory’
+
‘--directory=directory’
+
+ +

Add directory to the list of directories. Source files are +searched relative to this list of directories. The resulting ‘.po’ +file will be written relative to the current directory, though. +

+
+
+ +

If no inputfile is given or if it is ‘-’, standard input is read. +

+ + +

9.8.2 Output file location

+ +
+
‘-o file’
+
‘--output-file=file’
+
+ +

Write output to specified file. +

+
+
+ +

The results are written to standard output if no output file is specified +or if it is ‘-’. +

+ + +

9.8.3 Message selection

+ +
+
‘--translated’
+
+

Keep translated messages, remove untranslated messages. +

+
+
‘--untranslated’
+
+

Keep untranslated messages, remove translated messages. +

+
+
‘--no-fuzzy’
+
+

Remove +‘fuzzy’ +marked messages. +

+
+
‘--only-fuzzy’
+
+

Keep +‘fuzzy’ +marked messages, remove all other messages. +

+
+
‘--no-obsolete’
+
+

Remove obsolete #~ messages. +

+
+
‘--only-obsolete’
+
+

Keep obsolete #~ messages, remove all other messages. +

+
+
+ + + +

9.8.4 Attribute manipulation

+ +

Attributes are modified after the message selection/removal has been +performed. If the ‘--only-file’ or ‘--ignore-file’ option is +specified, the attribute modification is applied only to those messages +that are listed in the only-file and not listed in the +ignore-file. +

+
+
‘--set-fuzzy’
+
+

Set all messages +‘fuzzy’. +

+
+
‘--clear-fuzzy’
+
+

Set all messages +non-‘fuzzy’. +

+
+
‘--set-obsolete’
+
+

Set all messages obsolete. +

+
+
‘--clear-obsolete’
+
+

Set all messages non-obsolete. +

+
+
‘--previous’
+
+

When setting +‘fuzzy’ +mark, keep “previous msgid” of translated messages. +

+
+
‘--clear-previous’
+
+

Remove the “previous msgid” (‘#|’) comments from all messages. +

+
+
‘--empty’
+
+

When removing +‘fuzzy’ +mark, also set msgstr empty. +

+
+
‘--only-file=file’
+
+

Limit the attribute changes to entries that are listed in file. +file should be a PO or POT file. +

+
+
‘--ignore-file=file’
+
+

Limit the attribute changes to entries that are not listed in file. +file should be a PO or POT file. +

+
+
‘--fuzzy’
+
+

Synonym for ‘--only-fuzzy --clear-fuzzy’: It keeps only the fuzzy +messages and removes their +‘fuzzy’ +mark. +

+
+
‘--obsolete’
+
+

Synonym for ‘--only-obsolete --clear-obsolete’: It keeps only the +obsolete messages and makes them non-obsolete. +

+
+
+ + + +

9.8.5 Input file syntax

+ +
+
‘-P’
+
‘--properties-input’
+
+ +

Assume the input file is a Java ResourceBundle in Java .properties +syntax, not in PO file syntax. +

+
+
‘--stringtable-input’
+
+

Assume the input file is a NeXTstep/GNUstep localized resource file in +.strings syntax, not in PO file syntax. +

+
+
+ + + +

9.8.6 Output details

+ + +
+
‘--color’
+
‘--color=when’
+
+

Specify whether or when to use colors and other text attributes. +See The --color option for details. +

+
+
‘--style=style_file’
+
+

Specify the CSS style rule file to use for --color. +See The --style option for details. +

+
+
‘--force-po’
+
+

Always write an output file even if it contains no message. +

+
+
‘-i’
+
‘--indent’
+
+ +

Write the .po file using indented style. +

+
+
‘--no-location’
+
+

Do not write ‘#: filename:line’ lines. +

+
+
‘-n’
+
‘--add-location=type’
+
+ +

Generate ‘#: filename:line’ lines (default). +

+

The optional type can be either ‘full’, ‘file’, or +‘never’. If it is not given or ‘full’, it generates the +lines with both file name and line number. If it is ‘file’, the +line number part is omitted. If it is ‘never’, it completely +suppresses the lines (same as --no-location). +

+
+
‘--strict’
+
+

Write out a strict Uniforum conforming PO file. Note that this +Uniforum format should be avoided because it doesn't support the +GNU extensions. +

+
+
‘-p’
+
‘--properties-output’
+
+ +

Write out a Java ResourceBundle in Java .properties syntax. Note +that this file format doesn't support plural forms and silently drops +obsolete messages. +

+
+
‘--stringtable-output’
+
+

Write out a NeXTstep/GNUstep localized resource file in .strings syntax. +Note that this file format doesn't support plural forms. +

+
+
‘-w number’
+
‘--width=number’
+
+ +

Set the output page width. Long strings in the output files will be +split across multiple lines in order to ensure that each line's width +(= number of screen columns) is less or equal to the given number. +

+
+
‘--no-wrap’
+
+

Do not break long message lines. Message lines whose width exceeds the +output page width will not be split into several lines. Only file reference +lines which are wider than the output page width will be split. +

+
+
‘-s’
+
‘--sort-output’
+
+ +

Generate sorted output. Note that using this option makes it much harder +for the translator to understand each message's context. +

+
+
‘-F’
+
‘--sort-by-file’
+
+ +

Sort output by file location. +

+
+
+ + + +

9.8.7 Informative output

+ +
+
‘-h’
+
‘--help’
+
+ +

Display this help and exit. +

+
+
‘-V’
+
‘--version’
+
+ +

Output version information and exit. +

+
+
+ + + + +

9.9 Invoking the msgen Program

+ + +
 
msgen [option] inputfile
+
+ + +

The msgen program creates an English translation catalog. The +input file is the last created English PO file, or a PO Template file +(generally created by xgettext). Untranslated entries are assigned a +translation that is identical to the msgid. +

+

Note: ‘msginit --no-translator --locale=en’ performs a very similar +task. The main difference is that msginit cares specially about +the header entry, whereas msgen doesn't. +

+ + +

9.9.1 Input file location

+ +
+
‘inputfile’
+

Input PO or POT file. +

+
+
‘-D directory’
+
‘--directory=directory’
+
+ +

Add directory to the list of directories. Source files are +searched relative to this list of directories. The resulting ‘.po’ +file will be written relative to the current directory, though. +

+
+
+ +

If inputfile is ‘-’, standard input is read. +

+ + +

9.9.2 Output file location

+ +
+
‘-o file’
+
‘--output-file=file’
+
+ +

Write output to specified file. +

+
+
+ +

The results are written to standard output if no output file is specified +or if it is ‘-’. +

+ + +

9.9.3 Input file syntax

+ +
+
‘-P’
+
‘--properties-input’
+
+ +

Assume the input file is a Java ResourceBundle in Java .properties +syntax, not in PO file syntax. +

+
+
‘--stringtable-input’
+
+

Assume the input file is a NeXTstep/GNUstep localized resource file in +.strings syntax, not in PO file syntax. +

+
+
+ + + +

9.9.4 Output details

+ + +
+
‘--lang=catalogname’
+
+

Specify the ‘Language’ field to be used in the header entry. See +Filling in the Header Entry for the meaning of this field. Note: The +‘Language-Team’ and ‘Plural-Forms’ fields are not set by this +option. +

+
+
‘--color’
+
‘--color=when’
+
+

Specify whether or when to use colors and other text attributes. +See The --color option for details. +

+
+
‘--style=style_file’
+
+

Specify the CSS style rule file to use for --color. +See The --style option for details. +

+
+
‘--force-po’
+
+

Always write an output file even if it contains no message. +

+
+
‘-i’
+
‘--indent’
+
+ +

Write the .po file using indented style. +

+
+
‘--no-location’
+
+

Do not write ‘#: filename:line’ lines. +

+
+
‘-n’
+
‘--add-location=type’
+
+

Generate ‘#: filename:line’ lines (default). +

+

The optional type can be either ‘full’, ‘file’, or +‘never’. If it is not given or ‘full’, it generates the +lines with both file name and line number. If it is ‘file’, the +line number part is omitted. If it is ‘never’, it completely +suppresses the lines (same as --no-location). +

+
+
‘--strict’
+
+

Write out a strict Uniforum conforming PO file. Note that this +Uniforum format should be avoided because it doesn't support the +GNU extensions. +

+
+
‘-p’
+
‘--properties-output’
+
+ +

Write out a Java ResourceBundle in Java .properties syntax. Note +that this file format doesn't support plural forms and silently drops +obsolete messages. +

+
+
‘--stringtable-output’
+
+

Write out a NeXTstep/GNUstep localized resource file in .strings syntax. +Note that this file format doesn't support plural forms. +

+
+
‘-w number’
+
‘--width=number’
+
+ +

Set the output page width. Long strings in the output files will be +split across multiple lines in order to ensure that each line's width +(= number of screen columns) is less or equal to the given number. +

+
+
‘--no-wrap’
+
+

Do not break long message lines. Message lines whose width exceeds the +output page width will not be split into several lines. Only file reference +lines which are wider than the output page width will be split. +

+
+
‘-s’
+
‘--sort-output’
+
+ +

Generate sorted output. Note that using this option makes it much harder +for the translator to understand each message's context. +

+
+
‘-F’
+
‘--sort-by-file’
+
+ +

Sort output by file location. +

+
+
+ + + +

9.9.5 Informative output

+ +
+
‘-h’
+
‘--help’
+
+ +

Display this help and exit. +

+
+
‘-V’
+
‘--version’
+
+ +

Output version information and exit. +

+
+
+ + + + +

9.10 Invoking the msgexec Program

+ + +
 
msgexec [option] command [command-option]
+
+ + +

The msgexec program applies a command to all translations of a +translation catalog. +The command can be any program that reads a translation from standard +input. It is invoked once for each translation. Its output becomes +msgexec's output. msgexec's return code is the maximum return code +across all invocations. +

+ +

A special builtin command called ‘0’ outputs the translation, followed +by a null byte. The output of ‘msgexec 0’ is suitable as input for +‘xargs -0’. +

+
+
‘--newline’
+
+

Add newline at the end of each input line. +

+
+
+ + + + + + + + + +

During each command invocation, the environment variable +MSGEXEC_MSGID is bound to the message's msgid, and the environment +variable MSGEXEC_LOCATION is bound to the location in the PO file +of the message. If the message has a context, the environment variable +MSGEXEC_MSGCTXT is bound to the message's msgctxt, otherwise it is +unbound. If the message has a plural form, environment variable +MSGEXEC_MSGID_PLURAL is bound to the message's msgid_plural and +MSGEXEC_PLURAL_FORM is bound to the order number of the plural +actually processed (starting with 0), otherwise both are unbound. +If the message has a previous msgid (added by msgmerge), +environment variable MSGEXEC_PREV_MSGCTXT is bound to the +message's previous msgctxt, MSGEXEC_PREV_MSGID is bound to +the previous msgid, and MSGEXEC_PREV_MSGID_PLURAL is bound to +the previous msgid_plural. +

+ +

Note: It is your responsibility to ensure that the command can cope +with input encoded in the translation catalog's encoding. If the +command wants input in a particular encoding, you can in a first step +convert the translation catalog to that encoding using the ‘msgconv’ +program, before invoking ‘msgexec’. If the command wants input +in the locale's encoding, but you want to avoid the locale's encoding, then +you can first convert the translation catalog to UTF-8 using the +‘msgconv’ program and then make ‘msgexec’ work in an UTF-8 +locale, by using the LC_ALL environment variable. +

+ + +

9.10.1 Input file location

+ +
+
‘-i inputfile’
+
‘--input=inputfile’
+
+ +

Input PO file. +

+
+
‘-D directory’
+
‘--directory=directory’
+
+ +

Add directory to the list of directories. Source files are +searched relative to this list of directories. The resulting ‘.po’ +file will be written relative to the current directory, though. +

+
+
+ +

If no inputfile is given or if it is ‘-’, standard input is read. +

+ + +

9.10.2 Input file syntax

+ +
+
‘-P’
+
‘--properties-input’
+
+ +

Assume the input file is a Java ResourceBundle in Java .properties +syntax, not in PO file syntax. +

+
+
‘--stringtable-input’
+
+

Assume the input file is a NeXTstep/GNUstep localized resource file in +.strings syntax, not in PO file syntax. +

+
+
+ + + +

9.10.3 Informative output

+ +
+
‘-h’
+
‘--help’
+
+ +

Display this help and exit. +

+
+
‘-V’
+
‘--version’
+
+ +

Output version information and exit. +

+
+
+ + + + +

9.11 Highlighting parts of PO files

+ +

Translators are usually only interested in seeing the untranslated and +fuzzy messages of a PO file. Also, when a message is set fuzzy because +the msgid changed, they want to see the differences between the previous +msgid and the current one (especially if the msgid is long and only few +words in it have changed). Finally, it's always welcome to highlight the +different sections of a message in a PO file (comments, msgid, msgstr, etc.). +

+

Such highlighting is possible through the options ‘--color’ and +‘--style’. They are supported by all the programs that produce +a PO file on standard output, such as msgcat, msgmerge, +and msgunfmt. +

+ + + + +

9.11.1 The --color option

+ +

The ‘--color=when’ option specifies under which conditions +colorized output should be generated. The when part can be one of +the following: +

+
+
always
+
yes
+

The output will be colorized. +

+
+
never
+
no
+

The output will not be colorized. +

+
+
auto
+
tty
+

The output will be colorized if the output device is a tty, i.e. when the +output goes directly to a text screen or terminal emulator window. +

+
+
html
+

The output will be colorized and be in HTML format. +

+
+
test
+

This is a special value, understood only by the msgcat program. It +is explained in the next section (The environment variable TERM). +

+
+ +

‘--color’ is equivalent to ‘--color=yes’. The default is +‘--color=auto’. +

+

Thus, a command like ‘msgcat vi.po’ will produce colorized output +when called by itself in a command window. Whereas in a pipe, such as +‘msgcat vi.po | less -R’, it will not produce colorized output. To +get colorized output in this situation nevertheless, use the command +‘msgcat --color vi.po | less -R’. +

+

The ‘--color=html’ option will produce output that can be viewed in +a browser. This can be useful, for example, for Indic languages, +because the renderic of Indic scripts in browsers is usually better than +in terminal emulators. +

+

Note that the output produced with the --color option is not +a valid PO file in itself. It contains additional terminal-specific escape +sequences or HTML tags. A PO file reader will give a syntax error when +confronted with such content. Except for the ‘--color=html’ case, +you therefore normally don't need to save output produced with the +--color option in a file. +

+ + + +

9.11.2 The environment variable TERM

+ +

The environment variable TERM contains a identifier for the text +window's capabilities. You can get a detailed list of these cababilities +by using the ‘infocmp’ command, using ‘man 5 terminfo’ as a +reference. +

+

When producing text with embedded color directives, msgcat looks +at the TERM variable. Text windows today typically support at least +8 colors. Often, however, the text window supports 16 or more colors, +even though the TERM variable is set to a identifier denoting only +8 supported colors. It can be worth setting the TERM variable to +a different value in these cases: +

+
+
xterm
+

xterm is in most cases built with support for 16 colors. It can also +be built with support for 88 or 256 colors (but not both). You can try to +set TERM to either xterm-16color, xterm-88color, or +xterm-256color. +

+
+
rxvt
+

rxvt is often built with support for 16 colors. You can try to set +TERM to rxvt-16color. +

+
+
konsole
+

konsole too is often built with support for 16 colors. You can try to +set TERM to konsole-16color or xterm-16color. +

+
+ +

After setting TERM, you can verify it by invoking +‘msgcat --color=test’ and seeing whether the output looks like a +reasonable color map. +

+ + + +

9.11.3 The --style option

+ +

The ‘--style=style_file’ option specifies the style file to use +when colorizing. It has an effect only when the --color option is +effective. +

+ +

If the --style option is not specified, the environment variable +PO_STYLE is considered. It is meant to point to the user's +preferred style for PO files. +

+

The default style file is ‘$prefix/share/gettext/styles/po-default.css’, +where $prefix is the installation location. +

+

A few style files are predefined: +

+
‘po-vim.css’
+

This style imitates the look used by vim 7. +

+
+
‘po-emacs-x.css’
+

This style imitates the look used by GNU Emacs 21 and 22 in an X11 window. +

+
+
‘po-emacs-xterm.css’
+
‘po-emacs-xterm16.css’
+
‘po-emacs-xterm256.css’
+

This style imitates the look used by GNU Emacs 22 in a terminal of type +‘xterm’ (8 colors) or ‘xterm-16color’ (16 colors) or +‘xterm-256color’ (256 colors), respectively. +

+
+ +

You can use these styles without specifying a directory. They are actually +located in ‘$prefix/share/gettext/styles/’, where $prefix is the +installation location. +

+

You can also design your own styles. This is described in the next section. +

+ + + + +

9.11.4 Style rules for PO files

+ +

The same style file can be used for styling of a PO file, for terminal +output and for HTML output. It is written in CSS (Cascading Style Sheet) +syntax. See https://www.w3.org/TR/css2/cover.html for a formal +definition of CSS. Many HTML authoring tutorials also contain explanations +of CSS. +

+

In the case of HTML output, the style file is embedded in the HTML output. +In the case of text output, the style file is interpreted by the +msgcat program. This means, in particular, that when +@import is used with relative file names, the file names are +

+
    +
  • - +relative to the resulting HTML file, in the case of HTML output, + +
  • - +relative to the style sheet containing the @import, in the case of +text output. (Actually, @imports are not yet supported in this case, +due to a limitation in libcroco.) +
+ +

CSS rules are built up from selectors and declarations. The declarations +specify graphical properties; the selectors specify when they apply. +

+

In PO files, the following simple selectors (based on "CSS classes", see +the CSS2 spec, section 5.8.3) are supported. +

+
    +
  • +Selectors that apply to entire messages: + +
    +
    .header
    +

    This matches the header entry of a PO file. +

    +
    +
    .translated
    +

    This matches a translated message. +

    +
    +
    .untranslated
    +

    This matches an untranslated message (i.e. a message with empty translation). +

    +
    +
    .fuzzy
    +

    This matches a fuzzy message (i.e. a message which has a translation that +needs review by the translator). +

    +
    +
    .obsolete
    +

    This matches an obsolete message (i.e. a message that was translated but is +not needed by the current POT file any more). +

    +
    + +
  • +Selectors that apply to parts of a message in PO syntax. Recall the general +structure of a message in PO syntax: + +
     
    white-space
+#  translator-comments
+#. extracted-comments
+#: reference…
+#, flag…
+#| msgid previous-untranslated-string
+msgid untranslated-string
+msgstr translated-string
+
    + +
    +
    .comment
    +

    This matches all comments (translator comments, extracted comments, +source file reference comments, flag comments, previous message comments, +as well as the entire obsolete messages). +

    +
    +
    .translator-comment
    +

    This matches the translator comments. +

    +
    +
    .extracted-comment
    +

    This matches the extracted comments, i.e. the comments placed by the +programmer at the attention of the translator. +

    +
    +
    .reference-comment
    +

    This matches the source file reference comments (entire lines). +

    +
    +
    .reference
    +

    This matches the individual source file references inside the source file +reference comment lines. +

    +
    +
    .flag-comment
    +

    This matches the flag comment lines (entire lines). +

    +
    +
    .flag
    +

    This matches the individual flags inside flag comment lines. +

    +
    +
    .fuzzy-flag
    +

    This matches the `fuzzy' flag inside flag comment lines. +

    +
    +
    .previous-comment
    +

    This matches the comments containing the previous untranslated string (entire +lines). +

    +
    +
    .previous
    +

    This matches the previous untranslated string including the string delimiters, +the associated keywords (msgid etc.) and the spaces between them. +

    +
    +
    .msgid
    +

    This matches the untranslated string including the string delimiters, +the associated keywords (msgid etc.) and the spaces between them. +

    +
    +
    .msgstr
    +

    This matches the translated string including the string delimiters, +the associated keywords (msgstr etc.) and the spaces between them. +

    +
    +
    .keyword
    +

    This matches the keywords (msgid, msgstr, etc.). +

    +
    +
    .string
    +

    This matches strings, including the string delimiters (double quotes). +

    +
    + +
  • +Selectors that apply to parts of strings: + +
    +
    .text
    +

    This matches the entire contents of a string (excluding the string delimiters, +i.e. the double quotes). +

    +
    +
    .escape-sequence
    +

    This matches an escape sequence (starting with a backslash). +

    +
    +
    .format-directive
    +

    This matches a format string directive (starting with a ‘%’ sign in the +case of most programming languages, with a ‘{’ in the case of +java-format and csharp-format, with a ‘~’ in the case of +lisp-format and scheme-format, or with ‘$’ in the case of +sh-format). +

    +
    +
    .invalid-format-directive
    +

    This matches an invalid format string directive. +

    +
    +
    .added
    +

    In an untranslated string, this matches a part of the string that was not +present in the previous untranslated string. (Not yet implemented in this +release.) +

    +
    +
    .changed
    +

    In an untranslated string or in a previous untranslated string, this matches +a part of the string that is changed or replaced. (Not yet implemented in +this release.) +

    +
    +
    .removed
    +

    In a previous untranslated string, this matches a part of the string that +is not present in the current untranslated string. (Not yet implemented in +this release.) +

    +
    +
+ +

These selectors can be combined to hierarchical selectors. For example, +

+
 
.msgstr .invalid-format-directive { color: red; }
+
+ +

will highlight the invalid format directives in the translated strings. +

+

In text mode, pseudo-classes (CSS2 spec, section 5.11) and pseudo-elements +(CSS2 spec, section 5.12) are not supported. +

+

The declarations in HTML mode are not limited; any graphical attribute +supported by the browsers can be used. +

+

The declarations in text mode are limited to the following properties. Other +properties will be silently ignored. +

+
+
color (CSS2 spec, section 14.1)
+
background-color (CSS2 spec, section 14.2.1)
+

These properties is supported. Colors will be adjusted to match the terminal's +capabilities. Note that many terminals support only 8 colors. +

+
+
font-weight (CSS2 spec, section 15.2.3)
+

This property is supported, but most terminals can only render two different +weights: normal and bold. Values >= 600 are rendered as +bold. +

+
+
font-style (CSS2 spec, section 15.2.3)
+

This property is supported. The values italic and oblique are +rendered the same way. +

+
+
text-decoration (CSS2 spec, section 16.3.1)
+

This property is supported, limited to the values none and +underline. +

+
+ + + + +

9.11.5 Customizing less for viewing PO files

+ +

The ‘less’ program is a popular text file browser for use in a text +screen or terminal emulator. It also supports text with embedded escape +sequences for colors and text decorations. +

+

You can use less to view a PO file like this (assuming an UTF-8 +environment): +

+
 
msgcat --to-code=UTF-8 --color xyz.po | less -R
+
+ +

You can simplify this to this simple command: +

+
 
less xyz.po
+
+ +

after these three preparations: +

+
    +
  1. +Add the options ‘-R’ and ‘-f’ to the LESS environment +variable. In sh shells: +
     
    $ LESS="$LESS -R -f"
+$ export LESS
+
    + +
  2. +If your system does not already have the ‘lessopen.sh’ and +‘lessclose.sh’ scripts, create them and set the LESSOPEN and +LESSCLOSE environment variables, as indicated in the manual page +(‘man less’). + +
  3. +Add to ‘lessopen.sh’ a piece of script that recognizes PO files +through their file extension and invokes msgcat on them, producing +a temporary file. Like this: + +
     
    case "$1" in
+  *.po)
+    tmpfile=`mktemp "${TMPDIR-/tmp}/less.XXXXXX"`
+    msgcat --to-code=UTF-8 --color "$1" > "$tmpfile"
+    echo "$tmpfile"
+    exit 0
+    ;;
+esac
+
    +
+ + + + +

9.12 Other tools for manipulating PO files

+ + +

Pology

+ +

The “Pology” package is a Free Software package for manipulating PO files. +It features, in particular: +

+
    +
  • +Examination and in-place modification of collections of PO files. +
  • +Format-aware diffing and patching of PO files. +
  • +Handling of version-control branches. +
  • +Fine-grained asynchronous review workflow. +
  • +Custom translation validation. +
  • +Language and project specific support. +
+ +

Its home page is at http://pology.nedohodnik.net/. +

+ +

Translate Toolkit

+ +

The “Translate Toolkit” is a Free Software package. +It contains a set of programs to +convert between PO files and other file formats, +merge translations, +and perform various checks. +

+

Its home page is at https://toolkit.translatehouse.org/. +The code is at https://github.com/translate/translate. +

+ + + +

9.13 Writing your own programs that process PO files

+ +

For the tasks for which a combination of ‘msgattrib’, ‘msgcat’ etc. +is not sufficient, a set of C functions is provided in a library, to make it +possible to process PO files in your own programs. When you use this library, +you don't need to write routines to parse the PO file; instead, you retrieve +a pointer in memory to each of messages contained in the PO file. Functions +for writing those memory structures to a file after working with them are +provided too. +

+

The functions are declared in the header file ‘<gettext-po.h>’, and are +defined in a library called ‘libgettextpo’. +

+

The library is multithread-safe in the following sense: +Different threads can safely use the various functions simultaneously on +unrelated data objects. +For example, if several threads have created separate po_file_t objects, +each of them can safely work on its respective po_file_t object, +without caring about the other threads. +

+ +

The following example shows code how these functions can be used. Error +handling code is omitted, as its implementation is delegated to the user +provided functions. +

+
 
struct po_xerror_handler handler =
+  {
+    .xerror = …,
+    .xerror2 = …
+  };
+const char *filename = …;
+/* Read the file into memory.  */
+po_file_t file = po_file_read (filename, &handler);
+
+{
+  const char * const *domains = po_file_domains (file);
+  const char * const *domainp;
+
+  /* Iterate the domains contained in the file.  */
+  for (domainp = domains; *domainp; domainp++)
+    {
+      po_message_t *message;
+      const char *domain = *domainp;
+      po_message_iterator_t iterator = po_message_iterator (file, domain);
+
+      /* Iterate each message inside the domain.  */
+      while ((message = po_next_message (iterator)) != NULL)
+        {
+          /* Read data from the message …  */
+          const char *msgid = po_message_msgid (message);
+          const char *msgstr = po_message_msgstr (message);
+
+          …
+
+          /* Modify its contents …  */
+          if (perform_some_tests (msgid, msgstr))
+            po_message_set_fuzzy (message, 1);
+
+          …
+        }
+      /* Always release returned po_message_iterator_t.  */
+      po_message_iterator_free (iterator);
+    }
+
+  /* Write back the result.  */
+  po_file_t result = po_file_write (file, filename, &handler);
+}
+
+/* Always release the returned po_file_t.  */
+po_file_free (file);
+
+ + + + +

9.13.1 Error Handling

+ +

Error management is performed through callbacks provided by the user of +the library. They are provided through a parameter with the following +type: +

+
+
Data Type: struct po_xerror_handler + +
+

Its pointer is defined as po_xerror_handler_t. Contains +two fields, xerror and xerror2, with the following function +signatures. +

+ +
+
Function: void xerror (int severity, po_message_t message, const char *filename, size_t lineno, size_t column, int multiline_p, const char *message_text) + +
+

This function is called to signal a problem of the given severity. +It must not return if severity is +PO_SEVERITY_FATAL_ERROR. +

+

message_text is the problem description. When multiline_p +is true, it can contain multiple lines of text, each terminated with a +newline, otherwise a single line. +

+

message and/or filename and lineno indicate where the +problem occurred: +

+
    +
  • +If filename is NULL, filename and lineno and +column should be ignored. + +
  • +If lineno is (size_t)(-1), lineno and column +should be ignored. + +
  • +If column is (size_t)(-1), it should be ignored. +
+
+ +
+
Function: void xerror2 (int severity, po_message_t message1, const char *filename1, size_t lineno1, size_t column1, int multiline_p1, const char *message_text1, po_message_t message2, const char *filename2, size_t lineno2, size_t column2, int multiline_p2, const char *message_text2) + +
+

This function is called to signal a problem of the given severity +that refers to two messages. It must not return if +severity is PO_SEVERITY_FATAL_ERROR. +

+

It is similar to two calls to xerror. If possible, an ellipsis can be +appended to message_text1 and prepended to message_text2. +

+ + + + +

9.13.2 po_file_t API

+ +
+
Data Type: po_file_t + +
+

This is a pointer type that refers to the contents of a PO file, after it has +been read into memory. +

+ +
+
Function: po_file_t po_file_create () + +
+

The po_file_create function creates an empty PO file representation in +memory. +

+ +
+
Function: po_file_t po_file_read (const char *filename, struct po_xerror_handler *handler) + +
+

The po_file_read function reads a PO file into memory. The file name +is given as argument. The return value is a handle to the PO file's contents, +valid until po_file_free is called on it. In case of error, the +functions from handler are called to signal it. +

+

This function is exported as ‘po_file_read_v3’ at ABI level, but is +defined as po_file_read in C code after the inclusion of +‘<gettext-po.h>’. +

+ +
+
Function: po_file_t po_file_write (po_file_t file, const char *filename, struct po_xerror_handler *handler) + +
+

The po_file_write function writes the contents of the memory +structure file the filename given. The return value is +file after a successful operation. In case of error, the +functions from handler are called to signal it. +

+

This function is exported as ‘po_file_write_v2’ at ABI level, but +is defined as po_file_write in C code after the inclusion of +‘<gettext-po.h>’. +

+ +
+
Function: void po_file_free (po_file_t file) + +
+

The po_file_free function frees a PO file's contents from memory, +including all messages that are only implicitly accessible through iterators. +

+ +
+
Function: const char * const * po_file_domains (po_file_t file) + +
+

The po_file_domains function returns the domains for which the given +PO file has messages. The return value is a NULL terminated array +which is valid as long as the file handle is valid. For PO files which +contain no ‘domain’ directive, the return value contains only one domain, +namely the default domain "messages". +

+ + + + +

9.13.3 po_message_iterator_t API

+ +
+
Data Type: po_message_iterator_t + +
+

This is a pointer type that refers to an iterator that produces a sequence of +messages. +

+ +
+
Function: po_message_iterator_t po_message_iterator (po_file_t file, const char *domain) + +
+

The po_message_iterator returns an iterator that will produce the +messages of file that belong to the given domain. If domain +is NULL, the default domain is used instead. To list the messages, +use the function po_next_message repeatedly. +

+ +
+
Function: void po_message_iterator_free (po_message_iterator_t iterator) + +
+

The po_message_iterator_free function frees an iterator previously +allocated through the po_message_iterator function. +

+ +
+
Function: po_message_t po_next_message (po_message_iterator_t iterator) + +
+

The po_next_message function returns the next message from +iterator and advances the iterator. It returns NULL when the +iterator has reached the end of its message list. +

+ + + + +

9.13.4 po_message_t API

+ +
+
Data Type: po_message_t + +
+

This is a pointer type that refers to a message of a PO file, including its +translation. +

+ +
+
Function: po_message_t po_message_create (void) + +
+

Returns a freshly constructed message. To finish initializing the +message, you must set the msgid and msgstr. It must be +inserted into a file to manage its memory, as there is no +po_message_free available to the user of the library. +

+ +

The following functions access details of a po_message_t. Recall +that the results are valid as long as the file handle is valid. +

+
+
Function: const char * po_message_msgctxt (po_message_t message) + +
+

The po_message_msgctxt function returns the msgctxt, the +context of message. Returns NULL for a message not restricted +to a context. +

+ +
+
Function: void po_message_set_msgctxt (po_message_t message, const char *msgctxt) + +
+

The po_message_set_msgctxt function changes the msgctxt, +the context of the message, to the value provided through +msgctxt. The value NULL removes the restriction. +

+ +
+
Function: const char * po_message_msgid (po_message_t message) + +
+

The po_message_msgid function returns the msgid (untranslated +English string) of message. This is guaranteed to be non-NULL. +

+ +
+
Function: void po_message_set_msgid (po_message_t message, const char *msgid) + +
+

The po_message_set_msgid function changes the msgid +(untranslated English string) of message to the value provided through +msgid, a non-NULL string. +

+ +
+
Function: const char * po_message_msgid_plural (po_message_t message) + +
+

The po_message_msgid_plural function returns the msgid_plural +(untranslated English plural string) of message, a message with plurals, +or NULL for a message without plural. +

+ +
+
Function: void po_message_set_msgid_plural (po_message_t message, const char *msgid_plural) + +
+

The po_message_set_msgid_plural function changes the +msgid_plural (untranslated English plural string) of a message to +the value provided through msgid_plural, or removes the plurals if +NULL is provided as msgid_plural. +

+ +
+
Function: const char * po_message_msgstr (po_message_t message) + +
+

The po_message_msgstr function returns the msgstr (translation) +of message. For an untranslated message, the return value is an empty +string. +

+ +
+
Function: void po_message_set_msgstr (po_message_t message, const char *msgstr) + +
+

The po_message_set_msgstr function changes the msgstr +(translation) of message to the value provided through msgstr, a +non-NULL string. +

+ +
+
Function: const char * po_message_msgstr_plural (po_message_t message, int index) + +
+

The po_message_msgstr_plural function returns the +msgstr[index] of message, a message with plurals, or +NULL when the index is out of range or for a message without +plural. +

+ +
+
Function: void po_message_set_msgstr_plural (po_message_t message, int index, const char *msgstr_plural) + +
+

The po_message_set_msgstr_plural function changes the +msgstr[index] of message, a message with plurals, to +the value provided through msgstr_plural. message must be a +message with plurals. +Use NULL as the value of msgstr_plural with +index pointing to the last element to reduce the number of plural +forms. +

+ +
+
Function: const char * po_message_comments (po_message_t message) + +
+

The po_message_comments function returns the comments of message, +a multiline string, ending in a newline, or a non-NULL empty string. +

+ +
+
Function: void po_message_set_comments (po_message_t message, const char *comments) + +
+

The po_message_set_comments function changes the comments of +message to the value comments, a multiline string, ending in a +newline, or a non-NULL empty string. +

+ +
+
Function: const char * po_message_extracted_comments (po_message_t message) + +
+

The po_message_extracted_comments function returns the extracted +comments of message, a multiline string, ending in a newline, or a +non-NULL empty string. +

+ +
+
Function: void po_message_set_extracted_comments (po_message_t message, const char *extracted_comments) + +
+

The po_message_set_extracted_comments function changes the +comments of message to the value extracted_comments, a multiline +string, ending in a newline, or a non-NULL empty string. +

+ +
+
Function: const char * po_message_prev_msgctxt (po_message_t message) + +
+

The po_message_prev_msgctxt function returns the previous +msgctxt, the previous context of message. Return +NULL for a message that does not have a previous context. +

+ +
+
Function: void po_message_set_prev_msgctxt (po_message_t message, const char *prev_msgctxt) + +
+

The po_message_set_prev_msgctxt function changes the previous +msgctxt, the context of the message, to the value provided +through prev_msgctxt. The value NULL removes the stored +previous msgctxt. +

+ +
+
Function: const char * po_message_prev_msgid (po_message_t message) + +
+

The po_message_prev_msgid function returns the previous +msgid (untranslated English string) of message, or +NULL if there is no previous msgid stored. +

+ +
+
Function: void po_message_set_prev_msgid (po_message_t message, const char *prev_msgid) + +
+

The po_message_set_prev_msgid function changes the previous +msgid (untranslated English string) of message to the value +provided through prev_msgid, or removes the message when it is +NULL. +

+ +
+
Function: const char * po_message_prev_msgid_plural (po_message_t message) + +
+

The po_message_prev_msgid_plural function returns the previous +msgid_plural (untranslated English plural string) of +message, a message with plurals, or NULL for a message +without plural without any stored previous msgid_plural. +

+ +
+
Function: void po_message_set_prev_msgid_plural (po_message_t message, const char *prev_msgid_plural) + +
+

The po_message_set_prev_msgid_plural function changes the +previous msgid_plural (untranslated English plural string) of a +message to the value provided through prev_msgid_plural, or +removes the stored previous msgid_plural if NULL is +provided as prev_msgid_plural. +

+ +
+
Function: int po_message_is_obsolete (po_message_t message) + +
+

The po_message_is_obsolete function returns true when message +is marked as obsolete. +

+ +
+
Function: void po_message_set_obsolete (po_message_t message, int obsolete) + +
+

The po_message_set_obsolete function changes the obsolete mark of +message. +

+ +
+
Function: int po_message_is_fuzzy (po_message_t message) + +
+

The po_message_is_fuzzy function returns true when message +is marked as fuzzy. +

+ +
+
Function: void po_message_set_fuzzy (po_message_t message, int fuzzy) + +
+

The po_message_set_fuzzy function changes the fuzzy mark of +message. +

+ +
+
Function: int po_message_is_format (po_message_t message, const char *format_type) + +
+

The po_message_is_format function returns true when the message +is marked as being a format string of format_type. +

+ +
+
Function: void po_message_set_format (po_message_t message, const char *format_type, int value) + +
+

The po_message_set_format function changes +the format string mark of the message for the format_type provided. +Pass value = 1 +to assert the format string mark (leading to e.g. ‘c-format’), +value = 0 +to assert the opposite (leading to e.g. ‘no-c-format’), +or value = -1 +to remove the format string mark and its opposite. +

+ +
+
Function: int po_message_is_range (po_message_t message, int *minp, int *maxp) + +
+

The po_message_is_range function returns true when the message +has a numeric range set, and stores the minimum and maximum value in the +locations pointed by minp and maxp respectively. +

+ +
+
Function: void po_message_set_range (po_message_t message, int min, int max) + +
+

The po_message_set_range function changes the numeric range of +the message. min and max must be non-negative, with +min < max. Use min and max with value -1 +to remove the numeric range of message. +

+ + + + +

9.13.5 PO Header Entry API

+ +

The following functions provide an interface to extract and manipulate +the header entry (see section Filling in the Header Entry) from a file loaded in memory. +The meta information must be written back into the domain message with +the empty string as msgid. +

+
+
Function: const char * po_file_domain_header (po_file_t file, const char *domain) + +
+

Returns the header entry of a domain from file, a PO file loaded in +memory. The value NULL provided as domain denotes the +default domain. Returns NULL if there is no header entry. +

+ +
+
Function: char * po_header_field (const char *header, const char *field) + +
+

Returns the value of field in the header entry. The return +value is either a freshly allocated string, to be freed by the caller, +or NULL. +

+ +
+
Function: char * po_header_set_field (const char *header, const char *field, const char *value) + +
+

Returns a freshly allocated string which contains the entry from +header with field set to value. The field is added if +necessary. +

+ + + + +

9.13.6 po_filepos_t API

+ +
+
Data Type: po_filepos_t + +
+

This is a pointer type that refers to a string's position within a +source file. +

+ +

The following functions provide an interface to extract and manipulate +these references. +

+
+
Function: po_filepos_t po_message_filepos (po_message_t message, int index) + +
+

Returns the file reference in position index from the message. If +index is out of range, returns NULL. +

+ +
+
Function: void po_message_remove_filepos (po_message_t message, int index) + +
+

Removes the file reference in position index from the message. It +moves all references following index one position backwards. +

+ +
+
Function: void po_message_add_filepos (po_message_t message, const char *file, size_t start_line) + +
+

Adds a reference to the string from file starting at +start_line, if it is not already present for the message. The +value (size_t)(-1) for start_line denotes that the line +number is not available. +

+ + + + +

9.13.7 Format Type API

+ +
+
Function: const char * const * po_format_list (void) + +
+

Returns a NULL terminated array of the supported format types. +

+ +
+
Function: const char * po_format_pretty_name (const char *format_type) + +
+

Returns the pretty name associated with format_type. For example, +it returns “C#” when format_type is “csharp_format”. +Return NULL if format_type is not a supported format type. +

+ + + + +

9.13.8 Checking API

+ +
+
Function: void po_file_check_all (po_file_t file, po_xerror_handler_t handler) + +
+

Tests whether the entire file is valid, like msgfmt does it. If it +is invalid, passes the reasons to handler. +

+ +
+
Function: void po_message_check_all (po_message_t message, po_message_iterator_t iterator, po_xerror_handler_t handler) + +
+

Tests message, to be inserted at iterator in a PO file in memory, +like msgfmt does it. If it is invalid, passes the reasons to +handler. iterator is not modified by this call; it only +specifies the file and the domain. +

+ +
+
Function: void po_message_check_format (po_message_t message, po_xerror_handler_t handler) + +
+

Tests whether the message translation from message is a valid +format string if the message is marked as being a format string. If it +is invalid, passes the reasons to handler. +

+

This function is exported as ‘po_message_check_format_v2’ at ABI +level, but is defined as po_message_check_format in C code after +the inclusion of ‘<gettext-po.h>’. +

+ + + + + + + + + + + + + + +
[ << ][ >> ]           [Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_abt.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_abt.html new file mode 100644 index 0000000000000000000000000000000000000000..3ffc8ac94c4ce4acfeb0883c5cfbca0762cf7c97 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_abt.html @@ -0,0 +1,167 @@ + + + + + +GNU gettext utilities: About This Document + + + + + + + + + + + + + + + + + + + + +
[Top][Contents][Index][ ? ]
+

About This Document

+

+ This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. +

+

+ The buttons in the navigation panels have the following meaning: +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Button Name Go to From 1.2.3 go to
[ < ] BackPrevious section in reading order1.2.2
[ > ] ForwardNext section in reading order1.2.4
[ << ] FastBackBeginning of this chapter or previous chapter1
[ Up ] UpUp section1.2
[ >> ] FastForwardNext chapter2
[Top] TopCover (top) of document  
[Contents] ContentsTable of contents  
[Index] IndexIndex  
[ ? ] AboutAbout (help)  
+ +

+ where the Example assumes that the current position is at Subsubsection One-Two-Three of a document of the following structure: +

+ +
    +
  • 1. Section One +
      +
    • 1.1 Subsection One-One +
        +
      • ...
        • +
      +
      • +
    • 1.2 Subsection One-Two +
        +
      • 1.2.1 Subsubsection One-Two-One
        • +
      • 1.2.2 Subsubsection One-Two-Two
        • +
      • 1.2.3 Subsubsection One-Two-Three     + <== Current Position
        • +
      • 1.2.4 Subsubsection One-Two-Four
        • +
      +
      • +
    • 1.3 Subsection One-Three +
        +
      • ...
        • +
      +
      • +
    • 1.4 Subsection One-Four
      • +
    +
    • +
+ +
+ + + + + +
[Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_fot.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_fot.html new file mode 100644 index 0000000000000000000000000000000000000000..fc7126e6afc79b5a9fd1d62b166b59ce67cc24c1 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_fot.html @@ -0,0 +1,101 @@ + + + + + +GNU gettext utilities: Footnotes + + + + + + + + + + + + + + + + + + + + +
[Top][Contents][Index][ ? ]
+

Footnotes

+

(1)

+

In this manual, all mentions of Emacs +refers to either GNU Emacs or to XEmacs, which people sometimes call FSF +Emacs and Lucid Emacs, respectively. +

(2)

+

This +limitation is not imposed by GNU gettext, but is for compatibility +with the msgfmt implementation on Solaris. +

(3)

+

Some +system, e.g. mingw, don't have LC_MESSAGES. Here we use a more or +less arbitrary value for it, namely 1729, the smallest positive integer +which can be represented in two different ways as the sum of two cubes. +

(4)

+

When the system does not support setlocale its behavior +in setting the locale values is simulated by looking at the environment +variables. +

(5)

+

Additions are welcome. Send appropriate information to +bug-gettext@gnu.org and bug-glibc-manual@gnu.org. +The Unicode CLDR Project (http://cldr.unicode.org) provides a +comprehensive set of plural forms in a different format. The +msginit program has preliminary support for the format so you can +use it as a baseline (see section Invoking the msginit Program). +

(6)

+

you can also use it through the +‘MSGMERGE_OPTIONS’ option from ‘Makevars’ +

(7)

+

Note that the file name matching is done after +removing any .in suffix from the input file name. Thus the +pattern attribute must not include a pattern matching .in. +For example, if the input file name is ‘foo.msg.in’, the pattern +should be either *.msg or just *, rather than +*.in. +

+ + + + + +
[Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_toc.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_toc.html new file mode 100644 index 0000000000000000000000000000000000000000..5cd9faab3980741351575ce4a0380dcdb6c5f960 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettext_toc.html @@ -0,0 +1,606 @@ + + + + + +GNU gettext utilities: GNU gettext utilities + + + + + + + + + + + + + + + + + + + +
[Top][Contents][Index][ ? ]
+

GNU gettext utilities

+ +

Table of Contents

+
+ + +
+ + + + +

This manual documents the GNU gettext tools and the GNU libintl library, +version 0.25.1. +

+ + +
+ + + + + +
[Top][Contents][Index][ ? ]
+

+ + This document was generated by Bruno Haible on July, 2 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettextize.1.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettextize.1.html new file mode 100644 index 0000000000000000000000000000000000000000..7a9bb2219ea3832efd28aa53ad70f64564411aeb --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/gettextize.1.html @@ -0,0 +1,166 @@ + + + + + + + + +GETTEXTIZE + + + + +

GETTEXTIZE

+ +NAME
+SYNOPSIS
+DESCRIPTION
+OPTIONS
+AUTHOR
+REPORTING BUGS
+COPYRIGHT
+SEE ALSO
+ +
+ + +

NAME + +

+ + +

gettextize +- install or upgrade gettext infrastructure

+ +

SYNOPSIS + +

+ + + +

gettextize +[OPTION]... [package-dir]

+ +

DESCRIPTION + +

+ + +

Prepares a +source package to use gettext.

+ +

OPTIONS + +

+ + + + + + + + + +
+ + +

--help

 + + +

print this help and exit

 +
+ + +

--version

+ +

print version information and +exit

+ +

-f, +--force

+ +

force writing of new files even +if old exist

+ + +

--po-dir=DIR

+ +

specify directory with PO +files

+ + +

--no-changelog

+ +

don’t update or create +ChangeLog files

+ + +

--symlink

+ +

make symbolic links instead of +copying files

+ +

-n, +--dry-run

+ +

print modifications but +don’t perform them

+ +

AUTHOR + +

+ + +

Written by +Ulrich Drepper

+ +

REPORTING BUGS + +

+ + +

Report bugs in +the bug tracker at +<https://savannah.gnu.org/projects/gettext> or by +email to <bug-gettext@gnu.org>.

+ +

COPYRIGHT + +

+ + +

Copyright +© 1995-2025 Free Software Foundation, Inc. +License GPLv3+: GNU GPL version 3 or later +<https://gnu.org/licenses/gpl.html>
+This is free software: you are free to change and +redistribute it. There is NO WARRANTY, to the extent +permitted by law.

+ +

SEE ALSO + +

+ + +

The full +documentation for gettextize is maintained as a +Texinfo manual. If the info and gettextize +programs are properly installed at your site, the +command

+ +

info +gettextize

+ +

should give you +access to the complete manual.

+
+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgattrib.1.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgattrib.1.html new file mode 100644 index 0000000000000000000000000000000000000000..81de5bd059d3adfb7841bd0cc1d0df380f39f159 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgattrib.1.html @@ -0,0 +1,366 @@ + + + + + + + + +MSGATTRIB + + + + +

MSGATTRIB

+ +NAME
+SYNOPSIS
+DESCRIPTION
+AUTHOR
+REPORTING BUGS
+COPYRIGHT
+SEE ALSO
+ +
+ + +

NAME + +

+ + +

msgattrib +- attribute matching and manipulation on message +catalog

+ +

SYNOPSIS + +

+ + + +

msgattrib +[OPTION] [INPUTFILE]

+ +

DESCRIPTION + +

+ + +

Filters the +messages of a translation catalog according to their +attributes, and manipulates the attributes.

+ +

Mandatory +arguments to long options are mandatory for short options +too.

+ +

Input file +location:
+INPUTFILE

+ +

input PO file

+ +

-D, +--directory=DIRECTORY

+ +

add DIRECTORY to list for input +files search

+ +

If no input +file is given or if it is -, standard input is +read.

+ +

Output file +location:
+-o, +--output-file=FILE

+ +

write output to specified +file

+ +

The results are +written to standard output if no output file is specified or +if it is -.

+ +

Message +selection:
+--translated

+ +

keep translated, remove +untranslated messages

+ + +

--untranslated

+ +

keep untranslated, remove +translated messages

+ + +

--no-fuzzy

+ +

remove ’fuzzy’ +marked messages

+ + +

--only-fuzzy

+ +

keep ’fuzzy’ marked +messages

+ + +

--no-obsolete

+ +

remove obsolete #~ messages

+ + +

--only-obsolete

+ +

keep obsolete #~ messages

+ +

Attribute +manipulation:
+--set-fuzzy

+ +

set all messages +’fuzzy’

+ + +

--clear-fuzzy

+ +

set all messages +non-’fuzzy’

+ + +

--set-obsolete

+ +

set all messages obsolete

+ + +

--clear-obsolete

+ +

set all messages +non-obsolete

+ + +

--previous

+ +

when setting +’fuzzy’, keep previous msgids of translated +messages.

+ + +

--clear-previous

+ +

remove the "previous +msgid" from all messages

+ +

--empty

+ +

when removing +’fuzzy’, also set msgstr empty

+ + +

--only-file=FILE.po

+ +

manipulate only entries listed +in FILE.po

+ + +

--ignore-file=FILE.po

+ +

manipulate only entries not +listed in FILE.po

+ +

--fuzzy

+ +

synonym for +--only-fuzzy +--clear-fuzzy

+ + +

--obsolete

+ +

synonym for +--only-obsolete +--clear-obsolete

+ +

Input file +syntax:
+-P, +--properties-input

+ +

input file is in Java +.properties syntax

+ + +

--stringtable-input

+ +

input file is in +NeXTstep/GNUstep .strings syntax

+ +

Output +details:
+--color

+ +

use colors and other text +attributes always

+ + +

--color=WHEN

+ +

use colors and other text +attributes if WHEN. WHEN may be ’always’, +’never’, ’auto’, or +’html’.

+ + +

--style=STYLEFILE

+ +

specify CSS style rule file for +--color

+ +

-e, +--no-escape

+ +

do not use C escapes in output +(default)

+ +

-E, +--escape

+ +

use C escapes in output, no +extended chars

+ + +

--force-po

+ +

write PO file even if empty

+ +

-i, +--indent

+ +

write the .po file using +indented style

+ + +

--no-location

+ +

do not write ’#: +filename:line’ lines

+ +

-n, +--add-location

+ +

generate ’#: +filename:line’ lines (default)

+ + +

--strict

+ +

write out strict Uniforum +conforming .po file

+ +

-p, +--properties-output

+ +

write out a Java .properties +file

+ + +

--stringtable-output

+ +

write out a NeXTstep/GNUstep +.strings file

+ +

-w, +--width=NUMBER

+ +

set output page width

+ + +

--no-wrap

+ +

do not break long message +lines, longer than the output page width, into several +lines

+ +

-s, +--sort-output

+ +

generate sorted output

+ +

-F, +--sort-by-file

+ +

sort output by file +location

+ +

Informative +output:
+-h, --help

+ +

display this help and exit

+ +

-V, +--version

+ +

output version information and +exit

+ +

AUTHOR + +

+ + +

Written by +Bruno Haible.

+ +

REPORTING BUGS + +

+ + +

Report bugs in +the bug tracker at +<https://savannah.gnu.org/projects/gettext> or by +email to <bug-gettext@gnu.org>.

+ +

COPYRIGHT + +

+ + +

Copyright +© 2001-2025 Free Software Foundation, Inc. +License GPLv3+: GNU GPL version 3 or later +<https://gnu.org/licenses/gpl.html>
+This is free software: you are free to change and +redistribute it. There is NO WARRANTY, to the extent +permitted by law.

+ +

SEE ALSO + +

+ + +

The full +documentation for msgattrib is maintained as a +Texinfo manual. If the info and msgattrib +programs are properly installed at your site, the +command

+ +

info +msgattrib

+ +

should give you +access to the complete manual.

+
+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgcat.1.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgcat.1.html new file mode 100644 index 0000000000000000000000000000000000000000..311b9b4092bce2854b49a0fd7e2b90d12895ebcb --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgcat.1.html @@ -0,0 +1,314 @@ + + + + + + + + +MSGCAT + + + + +

MSGCAT

+ +NAME
+SYNOPSIS
+DESCRIPTION
+AUTHOR
+REPORTING BUGS
+COPYRIGHT
+SEE ALSO
+ +
+ + +

NAME + +

+ + +

msgcat - +combines several message catalogs

+ +

SYNOPSIS + +

+ + +

msgcat +[OPTION] [INPUTFILE]...

+ +

DESCRIPTION + +

+ + +

Concatenates +and merges the specified PO files. Find messages which are +common to two or more of the specified PO files. By using +the --more-than option, greater +commonality may be requested before messages are printed. +Conversely, the --less-than option +may be used to specify less commonality before messages are +printed (i.e. --less-than=2 +will only print the unique messages). Translations, +comments, extracted comments, and file positions will be +cumulated, except that if +--use-first is specified, they will +be taken from the first PO file to define them.

+ +

Mandatory +arguments to long options are mandatory for short options +too.

+ +

Input file +location:
+INPUTFILE ...

+ +

input files

+ +

-f, +--files-from=FILE

+ +

get list of input files from +FILE

+ +

-D, +--directory=DIRECTORY

+ +

add DIRECTORY to list for input +files search

+ +

If input file +is -, standard input is read.

+ +

Output file +location:
+-o, +--output-file=FILE

+ +

write output to specified +file

+ +

The results are +written to standard output if no output file is specified or +if it is -.

+ +

Message +selection:
+-<, +--less-than=NUMBER

+ +

print messages with less than +this many definitions, defaults to infinite if not set

+ +

->, +--more-than=NUMBER

+ +

print messages with more than +this many definitions, defaults to 0 if not set

+ +

-u, +--unique

+ +

shorthand for +--less-than=2, requests that +only unique messages be printed

+ +

Input file +syntax:
+-P, +--properties-input

+ +

input files are in Java +.properties syntax

+ + +

--stringtable-input

+ +

input files are in +NeXTstep/GNUstep .strings syntax

+ +

Output +details:
+-t, +--to-code=NAME

+ +

encoding for output

+ + +

--use-first

+ +

use first available translation +for each message, don’t merge several translations

+ + +

--lang=CATALOGNAME

+ +

set ’Language’ +field in the header entry

+ +

--color

+ +

use colors and other text +attributes always

+ + +

--color=WHEN

+ +

use colors and other text +attributes if WHEN. WHEN may be ’always’, +’never’, ’auto’, or +’html’.

+ + +

--style=STYLEFILE

+ +

specify CSS style rule file for +--color

+ +

-e, +--no-escape

+ +

do not use C escapes in output +(default)

+ +

-E, +--escape

+ +

use C escapes in output, no +extended chars

+ + +

--force-po

+ +

write PO file even if empty

+ +

-i, +--indent

+ +

write the .po file using +indented style

+ + +

--no-location

+ +

do not write ’#: +filename:line’ lines

+ +

-n, +--add-location

+ +

generate ’#: +filename:line’ lines (default)

+ + +

--strict

+ +

write out strict Uniforum +conforming .po file

+ +

-p, +--properties-output

+ +

write out a Java .properties +file

+ + +

--stringtable-output

+ +

write out a NeXTstep/GNUstep +.strings file

+ +

-w, +--width=NUMBER

+ +

set output page width

+ + +

--no-wrap

+ +

do not break long message +lines, longer than the output page width, into several +lines

+ +

-s, +--sort-output

+ +

generate sorted output

+ +

-F, +--sort-by-file

+ +

sort output by file +location

+ +

Informative +output:
+-h, --help

+ +

display this help and exit

+ +

-V, +--version

+ +

output version information and +exit

+ +

AUTHOR + +

+ + +

Written by +Bruno Haible.

+ +

REPORTING BUGS + +

+ + +

Report bugs in +the bug tracker at +<https://savannah.gnu.org/projects/gettext> or by +email to <bug-gettext@gnu.org>.

+ +

COPYRIGHT + +

+ + +

Copyright +© 2001-2025 Free Software Foundation, Inc. +License GPLv3+: GNU GPL version 3 or later +<https://gnu.org/licenses/gpl.html>
+This is free software: you are free to change and +redistribute it. There is NO WARRANTY, to the extent +permitted by law.

+ +

SEE ALSO + +

+ + +

The full +documentation for msgcat is maintained as a Texinfo +manual. If the info and msgcat programs are +properly installed at your site, the command

+ +

info +msgcat

+ +

should give you +access to the complete manual.

+
+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgcmp.1.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgcmp.1.html new file mode 100644 index 0000000000000000000000000000000000000000..85242674b3c671e35ac6609a9a7ef0828509411c --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgcmp.1.html @@ -0,0 +1,195 @@ + + + + + + + + +MSGCMP + + + + +

MSGCMP

+ +NAME
+SYNOPSIS
+DESCRIPTION
+AUTHOR
+REPORTING BUGS
+COPYRIGHT
+SEE ALSO
+ +
+ + +

NAME + +

+ + +

msgcmp - +compare message catalog and template

+ +

SYNOPSIS + +

+ + +

msgcmp +[OPTION] def.po ref.pot

+ +

DESCRIPTION + +

+ + +

Compare two +Uniforum style .po files to check that both contain the same +set of msgid strings. The def.po file is an existing PO file +with the translations. The ref.pot file is the last created +PO file, or a PO Template file (generally created by +xgettext). This is useful for checking that you have +translated each and every message in your program. Where an +exact match cannot be found, fuzzy matching is used to +produce better diagnostics.

+ +

Mandatory +arguments to long options are mandatory for short options +too.

+ +

Input file +location:

+ + + + + + + + +
+ + +

def.po

 + + +

translations

 +
+ +

ref.pot

+ +

references to the sources

+ +

-D, +--directory=DIRECTORY

+ +

add DIRECTORY to list for input +files search

+ +

Operation +modifiers:
+-m, --multi-domain

+ +

apply ref.pot to each of the +domains in def.po

+ +

-N, +--no-fuzzy-matching

+ +

do not use fuzzy matching

+ + +

--use-fuzzy

+ +

consider fuzzy entries

+ + +

--use-untranslated

+ +

consider untranslated +entries

+ +

Input file +syntax:
+-P, +--properties-input

+ +

input files are in Java +.properties syntax

+ + +

--stringtable-input

+ +

input files are in +NeXTstep/GNUstep .strings syntax

+ +

Informative +output:
+-h, --help

+ +

display this help and exit

+ +

-V, +--version

+ +

output version information and +exit

+ +

AUTHOR + +

+ + +

Written by +Peter Miller.

+ +

REPORTING BUGS + +

+ + +

Report bugs in +the bug tracker at +<https://savannah.gnu.org/projects/gettext> or by +email to <bug-gettext@gnu.org>.

+ +

COPYRIGHT + +

+ + +

Copyright +© 1995-2025 Free Software Foundation, Inc. +License GPLv3+: GNU GPL version 3 or later +<https://gnu.org/licenses/gpl.html>
+This is free software: you are free to change and +redistribute it. There is NO WARRANTY, to the extent +permitted by law.

+ +

SEE ALSO + +

+ + +

The full +documentation for msgcmp is maintained as a Texinfo +manual. If the info and msgcmp programs are +properly installed at your site, the command

+ +

info +msgcmp

+ +

should give you +access to the complete manual.

+
+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgcomm.1.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgcomm.1.html new file mode 100644 index 0000000000000000000000000000000000000000..71e3d7966569b39df744b9efe4309af0c59d05f8 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgcomm.1.html @@ -0,0 +1,302 @@ + + + + + + + + +MSGCOMM + + + + +

MSGCOMM

+ +NAME
+SYNOPSIS
+DESCRIPTION
+AUTHOR
+REPORTING BUGS
+COPYRIGHT
+SEE ALSO
+ +
+ + +

NAME + +

+ + +

msgcomm - +match two message catalogs

+ +

SYNOPSIS + +

+ + +

msgcomm +[OPTION] [INPUTFILE]...

+ +

DESCRIPTION + +

+ + +

Find messages +which are common to two or more of the specified PO files. +By using the --more-than option, +greater commonality may be requested before messages are +printed. Conversely, the +--less-than option may be used to +specify less commonality before messages are printed (i.e. +--less-than=2 will only +print the unique messages). Translations, comments and +extracted comments will be preserved, but only from the +first PO file to define them. File positions from all PO +files will be cumulated.

+ +

Mandatory +arguments to long options are mandatory for short options +too.

+ +

Input file +location:
+INPUTFILE ...

+ +

input files

+ +

-f, +--files-from=FILE

+ +

get list of input files from +FILE

+ +

-D, +--directory=DIRECTORY

+ +

add DIRECTORY to list for input +files search

+ +

If input file +is -, standard input is read.

+ +

Output file +location:
+-o, +--output-file=FILE

+ +

write output to specified +file

+ +

The results are +written to standard output if no output file is specified or +if it is -.

+ +

Message +selection:
+-<, +--less-than=NUMBER

+ +

print messages with less than +this many definitions, defaults to infinite if not set

+ +

->, +--more-than=NUMBER

+ +

print messages with more than +this many definitions, defaults to 1 if not set

+ +

-u, +--unique

+ +

shorthand for +--less-than=2, requests that +only unique messages be printed

+ +

Input file +syntax:
+-P, +--properties-input

+ +

input files are in Java +.properties syntax

+ + +

--stringtable-input

+ +

input files are in +NeXTstep/GNUstep .strings syntax

+ +

Output +details:
+--color

+ +

use colors and other text +attributes always

+ + +

--color=WHEN

+ +

use colors and other text +attributes if WHEN. WHEN may be ’always’, +’never’, ’auto’, or +’html’.

+ + +

--style=STYLEFILE

+ +

specify CSS style rule file for +--color

+ +

-e, +--no-escape

+ +

do not use C escapes in output +(default)

+ +

-E, +--escape

+ +

use C escapes in output, no +extended chars

+ + +

--force-po

+ +

write PO file even if empty

+ +

-i, +--indent

+ +

write the .po file using +indented style

+ + +

--no-location

+ +

do not write ’#: +filename:line’ lines

+ +

-n, +--add-location

+ +

generate ’#: +filename:line’ lines (default)

+ + +

--strict

+ +

write out strict Uniforum +conforming .po file

+ +

-p, +--properties-output

+ +

write out a Java .properties +file

+ + +

--stringtable-output

+ +

write out a NeXTstep/GNUstep +.strings file

+ +

-w, +--width=NUMBER

+ +

set output page width

+ + +

--no-wrap

+ +

do not break long message +lines, longer than the output page width, into several +lines

+ +

-s, +--sort-output

+ +

generate sorted output

+ +

-F, +--sort-by-file

+ +

sort output by file +location

+ + +

--omit-header

+ +

don’t write header with +’msgid ""’ entry

+ +

Informative +output:
+-h, --help

+ +

display this help and exit

+ +

-V, +--version

+ +

output version information and +exit

+ +

AUTHOR + +

+ + +

Written by +Peter Miller.

+ +

REPORTING BUGS + +

+ + +

Report bugs in +the bug tracker at +<https://savannah.gnu.org/projects/gettext> or by +email to <bug-gettext@gnu.org>.

+ +

COPYRIGHT + +

+ + +

Copyright +© 1995-2025 Free Software Foundation, Inc. +License GPLv3+: GNU GPL version 3 or later +<https://gnu.org/licenses/gpl.html>
+This is free software: you are free to change and +redistribute it. There is NO WARRANTY, to the extent +permitted by law.

+ +

SEE ALSO + +

+ + +

The full +documentation for msgcomm is maintained as a Texinfo +manual. If the info and msgcomm programs are +properly installed at your site, the command

+ +

info +msgcomm

+ +

should give you +access to the complete manual.

+
+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgconv.1.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgconv.1.html new file mode 100644 index 0000000000000000000000000000000000000000..f371523509b463aa9283433d303048ba51526f31 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgconv.1.html @@ -0,0 +1,269 @@ + + + + + + + + +MSGCONV + + + + +

MSGCONV

+ +NAME
+SYNOPSIS
+DESCRIPTION
+AUTHOR
+REPORTING BUGS
+COPYRIGHT
+SEE ALSO
+ +
+ + +

NAME + +

+ + +

msgconv - +character set conversion for message catalog

+ +

SYNOPSIS + +

+ + +

msgconv +[OPTION] [INPUTFILE]

+ +

DESCRIPTION + +

+ + +

Converts a +translation catalog to a different character encoding.

+ +

Mandatory +arguments to long options are mandatory for short options +too.

+ +

Input file +location:
+INPUTFILE

+ +

input PO file

+ +

-D, +--directory=DIRECTORY

+ +

add DIRECTORY to list for input +files search

+ +

If no input +file is given or if it is -, standard input is +read.

+ +

Output file +location:
+-o, +--output-file=FILE

+ +

write output to specified +file

+ +

The results are +written to standard output if no output file is specified or +if it is -.

+ +

Conversion +target:
+-t, +--to-code=NAME

+ +

encoding for output

+ +

The default +encoding is the current locale’s encoding.

+ +

Input file +syntax:
+-P, +--properties-input

+ +

input file is in Java +.properties syntax

+ + +

--stringtable-input

+ +

input file is in +NeXTstep/GNUstep .strings syntax

+ +

Output +details:
+--color

+ +

use colors and other text +attributes always

+ + +

--color=WHEN

+ +

use colors and other text +attributes if WHEN. WHEN may be ’always’, +’never’, ’auto’, or +’html’.

+ + +

--style=STYLEFILE

+ +

specify CSS style rule file for +--color

+ +

-e, +--no-escape

+ +

do not use C escapes in output +(default)

+ +

-E, +--escape

+ +

use C escapes in output, no +extended chars

+ + +

--force-po

+ +

write PO file even if empty

+ +

-i, +--indent

+ +

indented output style

+ + +

--no-location

+ +

suppress ’#: +filename:line’ lines

+ +

-n, +--add-location

+ +

preserve ’#: +filename:line’ lines (default)

+ + +

--strict

+ +

strict Uniforum output +style

+ +

-p, +--properties-output

+ +

write out a Java .properties +file

+ + +

--stringtable-output

+ +

write out a NeXTstep/GNUstep +.strings file

+ +

-w, +--width=NUMBER

+ +

set output page width

+ + +

--no-wrap

+ +

do not break long message +lines, longer than the output page width, into several +lines

+ +

-s, +--sort-output

+ +

generate sorted output

+ +

-F, +--sort-by-file

+ +

sort output by file +location

+ +

Informative +output:
+-h, --help

+ +

display this help and exit

+ +

-V, +--version

+ +

output version information and +exit

+ +

AUTHOR + +

+ + +

Written by +Bruno Haible.

+ +

REPORTING BUGS + +

+ + +

Report bugs in +the bug tracker at +<https://savannah.gnu.org/projects/gettext> or by +email to <bug-gettext@gnu.org>.

+ +

COPYRIGHT + +

+ + +

Copyright +© 2001-2025 Free Software Foundation, Inc. +License GPLv3+: GNU GPL version 3 or later +<https://gnu.org/licenses/gpl.html>
+This is free software: you are free to change and +redistribute it. There is NO WARRANTY, to the extent +permitted by law.

+ +

SEE ALSO + +

+ + +

The full +documentation for msgconv is maintained as a Texinfo +manual. If the info and msgconv programs are +properly installed at your site, the command

+ +

info +msgconv

+ +

should give you +access to the complete manual.

+
+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgen.1.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgen.1.html new file mode 100644 index 0000000000000000000000000000000000000000..1e1638e4876aac902b78b6ae045098bacaad7d84 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgen.1.html @@ -0,0 +1,266 @@ + + + + + + + + +MSGEN + + + + +

MSGEN

+ +NAME
+SYNOPSIS
+DESCRIPTION
+AUTHOR
+REPORTING BUGS
+COPYRIGHT
+SEE ALSO
+ +
+ + +

NAME + +

+ + +

msgen - +create English message catalog

+ +

SYNOPSIS + +

+ + +

msgen +[OPTION] INPUTFILE

+ +

DESCRIPTION + +

+ + +

Creates an +English translation catalog. The input file is the last +created English PO file, or a PO Template file (generally +created by xgettext). Untranslated entries are assigned a +translation that is identical to the msgid.

+ +

Mandatory +arguments to long options are mandatory for short options +too.

+ +

Input file +location:
+INPUTFILE

+ +

input PO or POT file

+ +

-D, +--directory=DIRECTORY

+ +

add DIRECTORY to list for input +files search

+ +

If input file +is -, standard input is read.

+ +

Output file +location:
+-o, +--output-file=FILE

+ +

write output to specified +file

+ +

The results are +written to standard output if no output file is specified or +if it is -.

+ +

Input file +syntax:
+-P, +--properties-input

+ +

input file is in Java +.properties syntax

+ + +

--stringtable-input

+ +

input file is in +NeXTstep/GNUstep .strings syntax

+ +

Output +details:
+--lang=CATALOGNAME

+ +

set ’Language’ +field in the header entry

+ +

--color

+ +

use colors and other text +attributes always

+ + +

--color=WHEN

+ +

use colors and other text +attributes if WHEN. WHEN may be ’always’, +’never’, ’auto’, or +’html’.

+ + +

--style=STYLEFILE

+ +

specify CSS style rule file for +--color

+ +

-e, +--no-escape

+ +

do not use C escapes in output +(default)

+ +

-E, +--escape

+ +

use C escapes in output, no +extended chars

+ + +

--force-po

+ +

write PO file even if empty

+ +

-i, +--indent

+ +

indented output style

+ + +

--no-location

+ +

suppress ’#: +filename:line’ lines

+ +

-n, +--add-location

+ +

preserve ’#: +filename:line’ lines (default)

+ + +

--strict

+ +

strict Uniforum output +style

+ +

-p, +--properties-output

+ +

write out a Java .properties +file

+ + +

--stringtable-output

+ +

write out a NeXTstep/GNUstep +.strings file

+ +

-w, +--width=NUMBER

+ +

set output page width

+ + +

--no-wrap

+ +

do not break long message +lines, longer than the output page width, into several +lines

+ +

-s, +--sort-output

+ +

generate sorted output

+ +

-F, +--sort-by-file

+ +

sort output by file +location

+ +

Informative +output:
+-h, --help

+ +

display this help and exit

+ +

-V, +--version

+ +

output version information and +exit

+ +

AUTHOR + +

+ + +

Written by +Bruno Haible.

+ +

REPORTING BUGS + +

+ + +

Report bugs in +the bug tracker at +<https://savannah.gnu.org/projects/gettext> or by +email to <bug-gettext@gnu.org>.

+ +

COPYRIGHT + +

+ + +

Copyright +© 2001-2025 Free Software Foundation, Inc. +License GPLv3+: GNU GPL version 3 or later +<https://gnu.org/licenses/gpl.html>
+This is free software: you are free to change and +redistribute it. There is NO WARRANTY, to the extent +permitted by law.

+ +

SEE ALSO + +

+ + +

The full +documentation for msgen is maintained as a Texinfo +manual. If the info and msgen programs are +properly installed at your site, the command

+ +

info +msgen

+ +

should give you +access to the complete manual.

+
+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgexec.1.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgexec.1.html new file mode 100644 index 0000000000000000000000000000000000000000..adb3c829012ae179514f9db8a2f3880d47b0770b --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgexec.1.html @@ -0,0 +1,170 @@ + + + + + + + + +MSGEXEC + + + + +

MSGEXEC

+ +NAME
+SYNOPSIS
+DESCRIPTION
+AUTHOR
+REPORTING BUGS
+COPYRIGHT
+SEE ALSO
+ +
+ + +

NAME + +

+ + +

msgexec - +process translations of message catalog

+ +

SYNOPSIS + +

+ + +

msgexec +[OPTION] COMMAND [COMMAND-OPTION]

+ +

DESCRIPTION + +

+ + +

Applies a +command to all translations of a translation catalog. The +COMMAND can be any program that reads a translation from +standard input. It is invoked once for each translation. Its +output becomes msgexec’s output. msgexec’s +return code is the maximum return code across all +invocations.

+ +

A special +builtin command called ’0’ outputs the +translation, followed by a null byte. The output of +"msgexec 0" is suitable as input for "xargs +-0".

+ +

Command +input:
+--newline

+ +

add newline at the end of +input

+ +

Mandatory +arguments to long options are mandatory for short options +too.

+ +

Input file +location:
+-i, +--input=INPUTFILE

+ +

input PO file

+ +

-D, +--directory=DIRECTORY

+ +

add DIRECTORY to list for input +files search

+ +

If no input +file is given or if it is -, standard input is +read.

+ +

Input file +syntax:
+-P, +--properties-input

+ +

input file is in Java +.properties syntax

+ + +

--stringtable-input

+ +

input file is in +NeXTstep/GNUstep .strings syntax

+ +

Informative +output:
+-h, --help

+ +

display this help and exit

+ +

-V, +--version

+ +

output version information and +exit

+ +

AUTHOR + +

+ + +

Written by +Bruno Haible.

+ +

REPORTING BUGS + +

+ + +

Report bugs in +the bug tracker at +<https://savannah.gnu.org/projects/gettext> or by +email to <bug-gettext@gnu.org>.

+ +

COPYRIGHT + +

+ + +

Copyright +© 2001-2025 Free Software Foundation, Inc. +License GPLv3+: GNU GPL version 3 or later +<https://gnu.org/licenses/gpl.html>
+This is free software: you are free to change and +redistribute it. There is NO WARRANTY, to the extent +permitted by law.

+ +

SEE ALSO + +

+ + +

The full +documentation for msgexec is maintained as a Texinfo +manual. If the info and msgexec programs are +properly installed at your site, the command

+ +

info +msgexec

+ +

should give you +access to the complete manual.

+
+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgfilter.1.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgfilter.1.html new file mode 100644 index 0000000000000000000000000000000000000000..695b9b2b6abeb344ff54dfaf34631de57839a0d7 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgfilter.1.html @@ -0,0 +1,299 @@ + + + + + + + + +MSGFILTER + + + + +

MSGFILTER

+ +NAME
+SYNOPSIS
+DESCRIPTION
+AUTHOR
+REPORTING BUGS
+COPYRIGHT
+SEE ALSO
+ +
+ + +

NAME + +

+ + +

msgfilter +- edit translations of message catalog

+ +

SYNOPSIS + +

+ + + +

msgfilter +[OPTION] FILTER [FILTER-OPTION]

+ +

DESCRIPTION + +

+ + +

Applies a +filter to all translations of a translation catalog.

+ +

Mandatory +arguments to long options are mandatory for short options +too.

+ +

Input file +location:
+-i, +--input=INPUTFILE

+ +

input PO file

+ +

-D, +--directory=DIRECTORY

+ +

add DIRECTORY to list for input +files search

+ +

If no input +file is given or if it is -, standard input is +read.

+ +

Output file +location:
+-o, +--output-file=FILE

+ +

write output to specified +file

+ +

The results are +written to standard output if no output file is specified or +if it is -.

+ +

The FILTER can +be any program that reads a translation from standard input +and writes a modified translation to standard output.

+ +

Filter input +and output:
+--newline

+ +

add a newline at the end of +input and remove a newline from the end of output

+ +

Useful +FILTER-OPTIONs when the FILTER is ’sed’:
+-e, +--expression=SCRIPT

+ +

add SCRIPT to the commands to +be executed

+ +

-f, +--file=SCRIPTFILE

+ +

add the contents of SCRIPTFILE +to the commands to be executed

+ +

-n, +--quiet, --silent

+ +

suppress automatic printing of +pattern space

+ +

Input file +syntax:
+-P, +--properties-input

+ +

input file is in Java +.properties syntax

+ + +

--stringtable-input

+ +

input file is in +NeXTstep/GNUstep .strings syntax

+ +

Output +details:
+--color

+ +

use colors and other text +attributes always

+ + +

--color=WHEN

+ +

use colors and other text +attributes if WHEN. WHEN may be ’always’, +’never’, ’auto’, or +’html’.

+ + +

--style=STYLEFILE

+ +

specify CSS style rule file for +--color

+ + +

--no-escape

+ +

do not use C escapes in output +(default)

+ +

-E, +--escape

+ +

use C escapes in output, no +extended chars

+ + +

--force-po

+ +

write PO file even if empty

+ + +

--indent

+ +

indented output style

+ + +

--keep-header

+ +

keep header entry unmodified, +don’t filter it

+ + +

--no-location

+ +

suppress ’#: +filename:line’ lines

+ +

-n, +--add-location

+ +

preserve ’#: +filename:line’ lines (default)

+ + +

--strict

+ +

strict Uniforum output +style

+ +

-p, +--properties-output

+ +

write out a Java .properties +file

+ + +

--stringtable-output

+ +

write out a NeXTstep/GNUstep +.strings file

+ +

-w, +--width=NUMBER

+ +

set output page width

+ + +

--no-wrap

+ +

do not break long message +lines, longer than the output page width, into several +lines

+ +

-s, +--sort-output

+ +

generate sorted output

+ +

-F, +--sort-by-file

+ +

sort output by file +location

+ +

Informative +output:
+-h, --help

+ +

display this help and exit

+ +

-V, +--version

+ +

output version information and +exit

+ +

AUTHOR + +

+ + +

Written by +Bruno Haible.

+ +

REPORTING BUGS + +

+ + +

Report bugs in +the bug tracker at +<https://savannah.gnu.org/projects/gettext> or by +email to <bug-gettext@gnu.org>.

+ +

COPYRIGHT + +

+ + +

Copyright +© 2001-2025 Free Software Foundation, Inc. +License GPLv3+: GNU GPL version 3 or later +<https://gnu.org/licenses/gpl.html>
+This is free software: you are free to change and +redistribute it. There is NO WARRANTY, to the extent +permitted by law.

+ +

SEE ALSO + +

+ + +

The full +documentation for msgfilter is maintained as a +Texinfo manual. If the info and msgfilter +programs are properly installed at your site, the +command

+ +

info +msgfilter

+ +

should give you +access to the complete manual.

+
+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgfmt.1.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgfmt.1.html new file mode 100644 index 0000000000000000000000000000000000000000..cf949d605c15cbfc87b41a1b2a3f74cf7205251a --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgfmt.1.html @@ -0,0 +1,484 @@ + + + + + + + + +MSGFMT + + + + +

MSGFMT

+ +NAME
+SYNOPSIS
+DESCRIPTION
+AUTHOR
+REPORTING BUGS
+COPYRIGHT
+SEE ALSO
+ +
+ + +

NAME + +

+ + +

msgfmt - +compile message catalog to binary format

+ +

SYNOPSIS + +

+ + +

msgfmt +[OPTION] filename.po ...

+ +

DESCRIPTION + +

+ + +

Generate binary +message catalog from textual translation description.

+ +

Mandatory +arguments to long options are mandatory for short options +too. Similarly for optional arguments.

+ +

Input file +location:
+filename.po ...

+ +

input files

+ +

-D, +--directory=DIRECTORY

+ +

add DIRECTORY to list for input +files search

+ +

If input file +is -, standard input is read.

+ +

Operation +mode:
+-j, --java

+ +

Java mode: generate a Java +ResourceBundle class

+ +

--java2

+ +

like --java, +and assume Java2 (JDK 1.2 or higher)

+ + +

--csharp

+ +

C# mode: generate a .NET .dll +file

+ + +

--csharp-resources

+ +

C# resources mode: generate a +.NET .resources file

+ + + + + + + + + + + + + + +
+ + +

--tcl

 + + +

Tcl mode: generate a tcl/msgcat .msg file

 +
+ + +

--qt

 + + +

Qt mode: generate a Qt .qm file

 +
+ + +

--desktop

+ +

Desktop Entry mode: generate a +.desktop file

+ + + + + + + + +
+ + +

--xml

 + + +

XML mode: generate XML file

 +
+ +

Output file +location:
+-o, +--output-file=FILE

+ +

write output to specified +file

+ + +

--strict

+ +

enable strict Uniforum mode

+ +

If output file +is -, output is written to standard output.

+ +

Output file +location in Java mode:
+-r, +--resource=RESOURCE

+ +

resource name

+ +

-l, +--locale=LOCALE

+ +

locale name, either language or +language_COUNTRY

+ + +

--source

+ +

produce a .java file, instead +of a .class file

+ +

-d DIRECTORY

+ +

base directory of classes +directory hierarchy

+ +

The class name +is determined by appending the locale name to the resource +name, separated with an underscore. The -d +option is mandatory. The class is written under the +specified directory.

+ +

Output file +location in C# mode:
+-r, +--resource=RESOURCE

+ +

resource name

+ +

-l, +--locale=LOCALE

+ +

locale name, either language or +language_COUNTRY

+ +

-d DIRECTORY

+ +

base directory for locale +dependent .dll files

+ +

The +-l and -d options are mandatory. +The .dll file is written in a subdirectory of the specified +directory whose name depends on the locale.

+ +

Output file +location in Tcl mode:
+-l, --locale=LOCALE

+ +

locale name, either language or +language_COUNTRY

+ +

-d DIRECTORY

+ +

base directory of .msg message +catalogs

+ +

The +-l and -d options are mandatory. +The .msg file is written in the specified directory.

+ +

Desktop +Entry mode options:
+-l, --locale=LOCALE

+ +

locale name, either language or +language_COUNTRY

+ +

-o, +--output-file=FILE

+ +

write output to specified +file

+ + +

--template=TEMPLATE

+ +

a .desktop file used as a +template

+ +

-d DIRECTORY

+ +

base directory of .po files

+ +

-kWORD, +--keyword=WORD

+ +

look for WORD as an additional +keyword

+ +

-k, +--keyword

+ +

do not to use default +keywords

+ +

The +-l, -o, and +--template options are mandatory. If +-D is specified, input files are read from the +directory instead of the command line arguments.

+ +

XML mode +options:
+-l, --locale=LOCALE

+ +

locale name, either language or +language_COUNTRY

+ +

-L, +--language=NAME

+ +

recognise the specified XML +language

+ +

-o, +--output-file=FILE

+ +

write output to specified +file

+ + +

--template=TEMPLATE

+ +

an XML file used as a +template

+ +

-d DIRECTORY

+ +

base directory of .po files

+ + +

--replace-text

+ +

output XML with translated text +replacing the original text, not augmenting the original +text

+ +

The +-l, -o, and +--template options are mandatory. If +-D is specified, input files are read from the +directory instead of the command line arguments.

+ +

Input file +syntax:
+-P, +--properties-input

+ +

input files are in Java +.properties syntax

+ + +

--stringtable-input

+ +

input files are in +NeXTstep/GNUstep .strings syntax

+ +

Input file +interpretation:
+-c, --check

+ +

perform all the checks implied +by --check-format, +--check-header, +--check-domain

+ + +

--check-format

+ +

check language dependent format +strings

+ + +

--check-header

+ +

verify presence and contents of +the header entry

+ + +

--check-domain

+ +

check for conflicts between +domain directives and the +--output-file option

+ +

-C, +--check-compatibility

+ +

check that GNU msgfmt behaves +like X/Open msgfmt

+ + +

--check-accelerators[=CHAR]

+ +

check presence of keyboard +accelerators for menu items

+ +

-f, +--use-fuzzy

+ +

use fuzzy entries in output

+ +

Output +details:
+--no-convert

+ +

don’t convert the +messages to UTF-8 encoding

+ + +

--no-redundancy

+ +

don’t pre-expand +ISO C 99 <inttypes.h> format string directive +macros

+ +

-a, +--alignment=NUMBER

+ +

align strings to NUMBER bytes +(default: 1)

+ + +

--endianness=BYTEORDER

+ +

write out 32-bit numbers +in the given byte order (big or little, default depends on +platform)

+ + +

--no-hash

+ +

binary file will not include +the hash table

+ +

Informative +output:
+-h, --help

+ +

display this help and exit

+ +

-V, +--version

+ +

output version information and +exit

+ + +

--statistics

+ +

print statistics about +translations

+ +

-v, +--verbose

+ +

increase verbosity level

+ +

AUTHOR + +

+ + +

Written by +Ulrich Drepper.

+ +

REPORTING BUGS + +

+ + +

Report bugs in +the bug tracker at +<https://savannah.gnu.org/projects/gettext> or by +email to <bug-gettext@gnu.org>.

+ +

COPYRIGHT + +

+ + +

Copyright +© 1995-2025 Free Software Foundation, Inc. +License GPLv3+: GNU GPL version 3 or later +<https://gnu.org/licenses/gpl.html>
+This is free software: you are free to change and +redistribute it. There is NO WARRANTY, to the extent +permitted by law.

+ +

SEE ALSO + +

+ + +

The full +documentation for msgfmt is maintained as a Texinfo +manual. If the info and msgfmt programs are +properly installed at your site, the command

+ +

info +msgfmt

+ +

should give you +access to the complete manual.

+
+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msggrep.1.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msggrep.1.html new file mode 100644 index 0000000000000000000000000000000000000000..906110ebedf1ac19d6455f7cc7503a9dd109f53d --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msggrep.1.html @@ -0,0 +1,377 @@ + + + + + + + + +MSGGREP + + + + +

MSGGREP

+ +NAME
+SYNOPSIS
+DESCRIPTION
+AUTHOR
+REPORTING BUGS
+COPYRIGHT
+SEE ALSO
+ +
+ + +

NAME + +

+ + +

msggrep - +pattern matching on message catalog

+ +

SYNOPSIS + +

+ + +

msggrep +[OPTION] [INPUTFILE]

+ +

DESCRIPTION + +

+ + +

Extracts all +messages of a translation catalog that match a given pattern +or belong to some given source files.

+ +

Mandatory +arguments to long options are mandatory for short options +too.

+ +

Input file +location:
+INPUTFILE

+ +

input PO file

+ +

-D, +--directory=DIRECTORY

+ +

add DIRECTORY to list for input +files search

+ +

If no input +file is given or if it is -, standard input is +read.

+ +

Output file +location:
+-o, +--output-file=FILE

+ +

write output to specified +file

+ +

The results are +written to standard output if no output file is specified or +if it is -.

+ +

Message +selection:

+ +

[-N SOURCEFILE]... +[-M DOMAINNAME]... [-J MSGCTXT-PATTERN] +[-K MSGID-PATTERN] [-T +MSGSTR-PATTERN] [-C COMMENT-PATTERN] +[-X EXTRACTED-COMMENT-PATTERN]

+ +

A message is +selected if it comes from one of the specified source files, +or if it comes from one of the specified domains, or if +-J is given and its context (msgctxt) matches +MSGCTXT-PATTERN, or if -K is given and +its key (msgid or msgid_plural) matches MSGID-PATTERN, +or if -T is given and its translation (msgstr) +matches MSGSTR-PATTERN, or if -C is given +and the translator’s comment matches +COMMENT-PATTERN, or if -X is given and +the extracted comment matches +EXTRACTED-COMMENT-PATTERN.

+ +

When more than +one selection criterion is specified, the set of selected +messages is the union of the selected messages of each +criterion.

+ + +

MSGCTXT-PATTERN +or MSGID-PATTERN or MSGSTR-PATTERN or +COMMENT-PATTERN or +EXTRACTED-COMMENT-PATTERN syntax:

+ +

[-E | +-F] [-e PATTERN | -f +FILE]...

+ +

PATTERNs are +basic regular expressions by default, or extended regular +expressions if -E is given, or fixed strings if +-F is given.
+-N, +--location=SOURCEFILE

+ +

select messages extracted from +SOURCEFILE

+ +

-M, +--domain=DOMAINNAME

+ +

select messages belonging to +domain DOMAINNAME

+ +

-J, +--msgctxt

+ +

start of patterns for the +msgctxt

+ +

-K, +--msgid

+ +

start of patterns for the +msgid

+ +

-T, +--msgstr

+ +

start of patterns for the +msgstr

+ +

-C, +--comment

+ +

start of patterns for the +translator’s comment

+ +

-X, +--extracted-comment

+ +

start of patterns for the +extracted comment

+ +

-E, +--extended-regexp

+ +

PATTERN is an extended regular +expression

+ +

-F, +--fixed-strings

+ +

PATTERN is a set of +newline-separated strings

+ +

-e, +--regexp=PATTERN

+ +

use PATTERN as a regular +expression

+ +

-f, +--file=FILE

+ +

obtain PATTERN from FILE

+ +

-i, +--ignore-case

+ +

ignore case distinctions

+ +

-v, +--invert-match

+ +

output only the messages that +do not match any selection criterion

+ +

Input file +syntax:
+-P, +--properties-input

+ +

input file is in Java +.properties syntax

+ + +

--stringtable-input

+ +

input file is in +NeXTstep/GNUstep .strings syntax

+ +

Output +details:
+--color

+ +

use colors and other text +attributes always

+ + +

--color=WHEN

+ +

use colors and other text +attributes if WHEN. WHEN may be ’always’, +’never’, ’auto’, or +’html’.

+ + +

--style=STYLEFILE

+ +

specify CSS style rule file for +--color

+ + +

--no-escape

+ +

do not use C escapes in output +(default)

+ + +

--escape

+ +

use C escapes in output, no +extended chars

+ + +

--force-po

+ +

write PO file even if empty

+ + +

--indent

+ +

indented output style

+ + +

--no-location

+ +

suppress ’#: +filename:line’ lines

+ +

-n, +--add-location

+ +

preserve ’#: +filename:line’ lines (default)

+ + +

--strict

+ +

strict Uniforum output +style

+ +

-p, +--properties-output

+ +

write out a Java .properties +file

+ + +

--stringtable-output

+ +

write out a NeXTstep/GNUstep +.strings file

+ +

-w, +--width=NUMBER

+ +

set output page width

+ + +

--no-wrap

+ +

do not break long message +lines, longer than the output page width, into several +lines

+ + +

--sort-output

+ +

generate sorted output

+ + +

--sort-by-file

+ +

sort output by file +location

+ +

Informative +output:
+-h, --help

+ +

display this help and exit

+ +

-V, +--version

+ +

output version information and +exit

+ +

AUTHOR + +

+ + +

Written by +Bruno Haible.

+ +

REPORTING BUGS + +

+ + +

Report bugs in +the bug tracker at +<https://savannah.gnu.org/projects/gettext> or by +email to <bug-gettext@gnu.org>.

+ +

COPYRIGHT + +

+ + +

Copyright +© 2001-2025 Free Software Foundation, Inc. +License GPLv3+: GNU GPL version 3 or later +<https://gnu.org/licenses/gpl.html>
+This is free software: you are free to change and +redistribute it. There is NO WARRANTY, to the extent +permitted by law.

+ +

SEE ALSO + +

+ + +

The full +documentation for msggrep is maintained as a Texinfo +manual. If the info and msggrep programs are +properly installed at your site, the command

+ +

info +msggrep

+ +

should give you +access to the complete manual.

+
+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msginit.1.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msginit.1.html new file mode 100644 index 0000000000000000000000000000000000000000..b7406f960772f9d29f6f639de1662a40587fa80b --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msginit.1.html @@ -0,0 +1,216 @@ + + + + + + + + +MSGINIT + + + + +

MSGINIT

+ +NAME
+SYNOPSIS
+DESCRIPTION
+AUTHOR
+REPORTING BUGS
+COPYRIGHT
+SEE ALSO
+ +
+ + +

NAME + +

+ + +

msginit - +initialize a message catalog

+ +

SYNOPSIS + +

+ + +

msginit +[OPTION]

+ +

DESCRIPTION + +

+ + +

Creates a new +PO file, initializing the meta information with values from +the user’s environment.

+ +

Mandatory +arguments to long options are mandatory for short options +too.

+ +

Input file +location:
+-i, +--input=INPUTFILE

+ +

input POT file

+ +

If no input +file is given, the current directory is searched for the POT +file. If it is -, standard input is read.

+ +

Output file +location:
+-o, +--output-file=FILE

+ +

write output to specified PO +file

+ +

If no output +file is given, it depends on the --locale +option or the user’s locale setting. If it is -, +the results are written to standard output.

+ +

Input file +syntax:
+-P, +--properties-input

+ +

input file is in Java +.properties syntax

+ + +

--stringtable-input

+ +

input file is in +NeXTstep/GNUstep .strings syntax

+ +

Output +details:
+-l, +--locale=LL_CC[.ENCODING]

+ +

set target locale

+ + +

--no-translator

+ +

assume the PO file is +automatically generated

+ +

--color

+ +

use colors and other text +attributes always

+ + +

--color=WHEN

+ +

use colors and other text +attributes if WHEN. WHEN may be ’always’, +’never’, ’auto’, or +’html’.

+ + +

--style=STYLEFILE

+ +

specify CSS style rule file for +--color

+ +

-p, +--properties-output

+ +

write out a Java .properties +file

+ + +

--stringtable-output

+ +

write out a NeXTstep/GNUstep +.strings file

+ +

-w, +--width=NUMBER

+ +

set output page width

+ + +

--no-wrap

+ +

do not break long message +lines, longer than the output page width, into several +lines

+ +

Informative +output:
+-h, --help

+ +

display this help and exit

+ +

-V, +--version

+ +

output version information and +exit

+ +

AUTHOR + +

+ + +

Written by +Bruno Haible.

+ +

REPORTING BUGS + +

+ + +

Report bugs in +the bug tracker at +<https://savannah.gnu.org/projects/gettext> or by +email to <bug-gettext@gnu.org>.

+ +

COPYRIGHT + +

+ + +

Copyright +© 2001-2025 Free Software Foundation, Inc. +License GPLv3+: GNU GPL version 3 or later +<https://gnu.org/licenses/gpl.html>
+This is free software: you are free to change and +redistribute it. There is NO WARRANTY, to the extent +permitted by law.

+ +

SEE ALSO + +

+ + +

The full +documentation for msginit is maintained as a Texinfo +manual. If the info and msginit programs are +properly installed at your site, the command

+ +

info +msginit

+ +

should give you +access to the complete manual.

+
+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgmerge.1.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgmerge.1.html new file mode 100644 index 0000000000000000000000000000000000000000..739b4c08cedc987c8d20b577d5852648a7726803 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgmerge.1.html @@ -0,0 +1,380 @@ + + + + + + + + +MSGMERGE + + + + +

MSGMERGE

+ +NAME
+SYNOPSIS
+DESCRIPTION
+AUTHOR
+REPORTING BUGS
+COPYRIGHT
+SEE ALSO
+ +
+ + +

NAME + +

+ + +

msgmerge +- merge message catalog and template

+ +

SYNOPSIS + +

+ + + +

msgmerge +[OPTION] def.po ref.pot

+ +

DESCRIPTION + +

+ + +

Merges two +Uniforum style .po files together. The def.po file is an +existing PO file with translations which will be taken over +to the newly created file as long as they still match; +comments will be preserved, but extracted comments and file +positions will be discarded. The ref.pot file is the last +created PO file with up-to-date source +references but old translations, or a PO Template file +(generally created by xgettext); any translations or +comments in the file will be discarded, however dot comments +and file positions will be preserved. Where an exact match +cannot be found, fuzzy matching is used to produce better +results.

+ +

Mandatory +arguments to long options are mandatory for short options +too.

+ +

Input file +location:

+ + + + + + + + +
+ + +

def.po

 + + +

translations referring to old sources

 +
+ +

ref.pot

+ +

references to new sources

+ +

-D, +--directory=DIRECTORY

+ +

add DIRECTORY to list for input +files search

+ +

-C, +--compendium=FILE

+ +

additional library of message +translations, may be specified more than once

+ +

Operation +mode:
+-U, --update

+ +

update def.po, do nothing if +def.po already up to date

+ +

Output file +location:
+-o, +--output-file=FILE

+ +

write output to specified +file

+ +

The results are +written to standard output if no output file is specified or +if it is -.

+ +

Output file +location in update mode: The result is written back to +def.po.
+--backup=CONTROL

+ +

make a backup of def.po

+ + +

--suffix=SUFFIX

+ +

override the usual backup +suffix

+ +

The version +control method may be selected via the +--backup option or through the +VERSION_CONTROL environment variable. Here are the values: +
+none, off

+ +

never make backups (even if +--backup is given)

+ +

numbered, t

+ +

make numbered backups

+ +

existing, nil

+ +

numbered if numbered backups +exist, simple otherwise

+ +

simple, never

+ +

always make simple backups

+ +

The backup +suffix is ’~’, unless set with +--suffix or the SIMPLE_BACKUP_SUFFIX +environment variable.

+ +

Operation +modifiers:
+-m, --multi-domain

+ +

apply ref.pot to each of the +domains in def.po

+ + +

--for-msgfmt

+ +

produce output for +’msgfmt’, not for a translator

+ +

-N, +--no-fuzzy-matching

+ +

do not use fuzzy matching

+ + +

--previous

+ +

keep previous msgids of +translated messages

+ +

Input file +syntax:
+-P, +--properties-input

+ +

input files are in Java +.properties syntax

+ + +

--stringtable-input

+ +

input files are in +NeXTstep/GNUstep .strings syntax

+ +

Output +details:
+--lang=CATALOGNAME

+ +

set ’Language’ +field in the header entry

+ +

--color

+ +

use colors and other text +attributes always

+ + +

--color=WHEN

+ +

use colors and other text +attributes if WHEN. WHEN may be ’always’, +’never’, ’auto’, or +’html’.

+ + +

--style=STYLEFILE

+ +

specify CSS style rule file for +--color

+ +

-e, +--no-escape

+ +

do not use C escapes in output +(default)

+ +

-E, +--escape

+ +

use C escapes in output, no +extended chars

+ + +

--force-po

+ +

write PO file even if empty

+ +

-i, +--indent

+ +

indented output style

+ + +

--no-location

+ +

suppress ’#: +filename:line’ lines

+ +

-n, +--add-location

+ +

preserve ’#: +filename:line’ lines (default)

+ + +

--strict

+ +

strict Uniforum output +style

+ +

-p, +--properties-output

+ +

write out a Java .properties +file

+ + +

--stringtable-output

+ +

write out a NeXTstep/GNUstep +.strings file

+ +

-w, +--width=NUMBER

+ +

set output page width

+ + +

--no-wrap

+ +

do not break long message +lines, longer than the output page width, into several +lines

+ +

-s, +--sort-output

+ +

generate sorted output +(deprecated)

+ +

-F, +--sort-by-file

+ +

sort output by file +location

+ +

Informative +output:
+-h, --help

+ +

display this help and exit

+ +

-V, +--version

+ +

output version information and +exit

+ +

-v, +--verbose

+ +

increase verbosity level

+ +

-q, +--quiet, --silent

+ +

suppress progress +indicators

+ +

AUTHOR + +

+ + +

Written by +Peter Miller.

+ +

REPORTING BUGS + +

+ + +

Report bugs in +the bug tracker at +<https://savannah.gnu.org/projects/gettext> or by +email to <bug-gettext@gnu.org>.

+ +

COPYRIGHT + +

+ + +

Copyright +© 1995-2025 Free Software Foundation, Inc. +License GPLv3+: GNU GPL version 3 or later +<https://gnu.org/licenses/gpl.html>
+This is free software: you are free to change and +redistribute it. There is NO WARRANTY, to the extent +permitted by law.

+ +

SEE ALSO + +

+ + +

The full +documentation for msgmerge is maintained as a Texinfo +manual. If the info and msgmerge programs are +properly installed at your site, the command

+ +

info +msgmerge

+ +

should give you +access to the complete manual.

+
+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgunfmt.1.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgunfmt.1.html new file mode 100644 index 0000000000000000000000000000000000000000..1595be6d7e3f1f4f436e687d5fcedb92efbaf678 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msgunfmt.1.html @@ -0,0 +1,319 @@ + + + + + + + + +MSGUNFMT + + + + +

MSGUNFMT

+ +NAME
+SYNOPSIS
+DESCRIPTION
+AUTHOR
+REPORTING BUGS
+COPYRIGHT
+SEE ALSO
+ +
+ + +

NAME + +

+ + +

msgunfmt +- uncompile message catalog from binary format

+ +

SYNOPSIS + +

+ + + +

msgunfmt +[OPTION] [FILE]...

+ +

DESCRIPTION + +

+ + +

Convert binary +message catalog to Uniforum style .po file.

+ +

Mandatory +arguments to long options are mandatory for short options +too.

+ +

Operation +mode:
+-j, --java

+ +

Java mode: input is a Java +ResourceBundle class

+ + +

--csharp

+ +

C# mode: input is a .NET .dll +file

+ + +

--csharp-resources

+ +

C# resources mode: input is a +.NET .resources file

+ + + + + + + + +
+ + +

--tcl

 + + +

Tcl mode: input is a tcl/msgcat .msg file

 +
+ +

Input file +location:
+FILE ...

+ +

input .mo files

+ +

If no input +file is given or if it is -, standard input is +read.

+ +

Input file +location in Java mode:
+-r, +--resource=RESOURCE

+ +

resource name

+ +

-l, +--locale=LOCALE

+ +

locale name, either language or +language_COUNTRY

+ +

The class name +is determined by appending the locale name to the resource +name, separated with an underscore. The class is located +using the CLASSPATH.

+ +

Input file +location in C# mode:
+-r, +--resource=RESOURCE

+ +

resource name

+ +

-l, +--locale=LOCALE

+ +

locale name, either language or +language_COUNTRY

+ +

-d DIRECTORY

+ +

base directory for locale +dependent .dll files

+ +

The +-l and -d options are mandatory. +The .dll file is located in a subdirectory of the specified +directory whose name depends on the locale.

+ +

Input file +location in Tcl mode:
+-l, --locale=LOCALE

+ +

locale name, either language or +language_COUNTRY

+ +

-d DIRECTORY

+ +

base directory of .msg message +catalogs

+ +

The +-l and -d options are mandatory. +The .msg file is located in the specified directory.

+ +

Output file +location:
+-o, +--output-file=FILE

+ +

write output to specified +file

+ +

The results are +written to standard output if no output file is specified or +if it is -.

+ +

Output +details:
+--color

+ +

use colors and other text +attributes always

+ + +

--color=WHEN

+ +

use colors and other text +attributes if WHEN. WHEN may be ’always’, +’never’, ’auto’, or +’html’.

+ + +

--style=STYLEFILE

+ +

specify CSS style rule file for +--color

+ +

-e, +--no-escape

+ +

do not use C escapes in output +(default)

+ +

-E, +--escape

+ +

use C escapes in output, no +extended chars

+ + +

--force-po

+ +

write PO file even if empty

+ +

-i, +--indent

+ +

write indented output style

+ + +

--strict

+ +

write strict uniforum style

+ +

-p, +--properties-output

+ +

write out a Java .properties +file

+ + +

--stringtable-output

+ +

write out a NeXTstep/GNUstep +.strings file

+ +

-w, +--width=NUMBER

+ +

set output page width

+ + +

--no-wrap

+ +

do not break long message +lines, longer than the output page width, into several +lines

+ +

-s, +--sort-output

+ +

generate sorted output

+ +

Informative +output:
+-h, --help

+ +

display this help and exit

+ +

-V, +--version

+ +

output version information and +exit

+ +

-v, +--verbose

+ +

increase verbosity level

+ +

AUTHOR + +

+ + +

Written by +Ulrich Drepper.

+ +

REPORTING BUGS + +

+ + +

Report bugs in +the bug tracker at +<https://savannah.gnu.org/projects/gettext> or by +email to <bug-gettext@gnu.org>.

+ +

COPYRIGHT + +

+ + +

Copyright +© 1995-2025 Free Software Foundation, Inc. +License GPLv3+: GNU GPL version 3 or later +<https://gnu.org/licenses/gpl.html>
+This is free software: you are free to change and +redistribute it. There is NO WARRANTY, to the extent +permitted by law.

+ +

SEE ALSO + +

+ + +

The full +documentation for msgunfmt is maintained as a Texinfo +manual. If the info and msgunfmt programs are +properly installed at your site, the command

+ +

info +msgunfmt

+ +

should give you +access to the complete manual.

+
+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msguniq.1.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msguniq.1.html new file mode 100644 index 0000000000000000000000000000000000000000..492a0d84856c8ff454404db9021bd588caf913f6 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/msguniq.1.html @@ -0,0 +1,294 @@ + + + + + + + + +MSGUNIQ + + + + +

MSGUNIQ

+ +NAME
+SYNOPSIS
+DESCRIPTION
+AUTHOR
+REPORTING BUGS
+COPYRIGHT
+SEE ALSO
+ +
+ + +

NAME + +

+ + +

msguniq - +unify duplicate translations in message catalog

+ +

SYNOPSIS + +

+ + +

msguniq +[OPTION] [INPUTFILE]

+ +

DESCRIPTION + +

+ + +

Unifies +duplicate translations in a translation catalog. Finds +duplicate translations of the same message ID. Such +duplicates are invalid input for other programs like msgfmt, +msgmerge or msgcat. By default, duplicates are merged +together. When using the --repeated +option, only duplicates are output, and all other messages +are discarded. Comments and extracted comments will be +cumulated, except that if +--use-first is specified, they will +be taken from the first translation. File positions will be +cumulated. When using the --unique +option, duplicates are discarded.

+ +

Mandatory +arguments to long options are mandatory for short options +too.

+ +

Input file +location:
+INPUTFILE

+ +

input PO file

+ +

-D, +--directory=DIRECTORY

+ +

add DIRECTORY to list for input +files search

+ +

If no input +file is given or if it is -, standard input is +read.

+ +

Output file +location:
+-o, +--output-file=FILE

+ +

write output to specified +file

+ +

The results are +written to standard output if no output file is specified or +if it is -.

+ +

Message +selection:
+-d, --repeated

+ +

print only duplicates

+ +

-u, +--unique

+ +

print only unique messages, +discard duplicates

+ +

Input file +syntax:
+-P, +--properties-input

+ +

input file is in Java +.properties syntax

+ + +

--stringtable-input

+ +

input file is in +NeXTstep/GNUstep .strings syntax

+ +

Output +details:
+-t, +--to-code=NAME

+ +

encoding for output

+ + +

--use-first

+ +

use first available translation +for each message, don’t merge several translations

+ +

--color

+ +

use colors and other text +attributes always

+ + +

--color=WHEN

+ +

use colors and other text +attributes if WHEN. WHEN may be ’always’, +’never’, ’auto’, or +’html’.

+ + +

--style=STYLEFILE

+ +

specify CSS style rule file for +--color

+ +

-e, +--no-escape

+ +

do not use C escapes in output +(default)

+ +

-E, +--escape

+ +

use C escapes in output, no +extended chars

+ + +

--force-po

+ +

write PO file even if empty

+ +

-i, +--indent

+ +

write the .po file using +indented style

+ + +

--no-location

+ +

do not write ’#: +filename:line’ lines

+ +

-n, +--add-location

+ +

generate ’#: +filename:line’ lines (default)

+ + +

--strict

+ +

write out strict Uniforum +conforming .po file

+ +

-p, +--properties-output

+ +

write out a Java .properties +file

+ + +

--stringtable-output

+ +

write out a NeXTstep/GNUstep +.strings file

+ +

-w, +--width=NUMBER

+ +

set output page width

+ + +

--no-wrap

+ +

do not break long message +lines, longer than the output page width, into several +lines

+ +

-s, +--sort-output

+ +

generate sorted output

+ +

-F, +--sort-by-file

+ +

sort output by file +location

+ +

Informative +output:
+-h, --help

+ +

display this help and exit

+ +

-V, +--version

+ +

output version information and +exit

+ +

AUTHOR + +

+ + +

Written by +Bruno Haible.

+ +

REPORTING BUGS + +

+ + +

Report bugs in +the bug tracker at +<https://savannah.gnu.org/projects/gettext> or by +email to <bug-gettext@gnu.org>.

+ +

COPYRIGHT + +

+ + +

Copyright +© 2001-2025 Free Software Foundation, Inc. +License GPLv3+: GNU GPL version 3 or later +<https://gnu.org/licenses/gpl.html>
+This is free software: you are free to change and +redistribute it. There is NO WARRANTY, to the extent +permitted by law.

+ +

SEE ALSO + +

+ + +

The full +documentation for msguniq is maintained as a Texinfo +manual. If the info and msguniq programs are +properly installed at your site, the command

+ +

info +msguniq

+ +

should give you +access to the complete manual.

+
+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/ngettext.1.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/ngettext.1.html new file mode 100644 index 0000000000000000000000000000000000000000..6606dee4c644334466e9e47c65576cc76248ec6e --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/ngettext.1.html @@ -0,0 +1,202 @@ + + + + + + + + +NGETTEXT + + + + +

NGETTEXT

+ +NAME
+SYNOPSIS
+DESCRIPTION
+AUTHOR
+REPORTING BUGS
+COPYRIGHT
+SEE ALSO
+ +
+ + +

NAME + +

+ + +

ngettext +- translate message and choose plural form

+ +

SYNOPSIS + +

+ + + +

ngettext +[OPTION] [TEXTDOMAIN] MSGID MSGID-PLURAL +COUNT

+ +

DESCRIPTION + +

+ + +

The +ngettext program translates a natural language +message into the user’s language, by looking up the +translation in a message catalog, and chooses the +appropriate plural form, which depends on the number +COUNT and the language of the message catalog where +the translation was found.

+ +

Display native +language translation of a textual message whose grammatical +form depends on a number.
+-d, +--domain=TEXTDOMAIN

+ +

retrieve translated message +from TEXTDOMAIN

+ +

-c, +--context=CONTEXT

+ +

specify context for MSGID

+ + + + + + + + + + + + + + +
+ + +

-e

 + + +

enable expansion of some escape sequences

 +
+ + +

-E

 + + +

(ignored for compatibility)

 +
+ +

[TEXTDOMAIN]

+ +

retrieve translated message +from TEXTDOMAIN

+ +

MSGID MSGID-PLURAL

+ +

translate MSGID (singular) / +MSGID-PLURAL (plural)

+ + + + + + + + +
+ + +

COUNT

 + + +

choose singular/plural form based on this value

 +
+ +

Informative +output:
+-h, --help

+ +

display this help and exit

+ +

-V, +--version

+ +

display version information and +exit

+ +

If the +TEXTDOMAIN parameter is not given, the domain is determined +from the environment variable TEXTDOMAIN. If the message +catalog is not found in the regular directory, another +location can be specified with the environment variable +TEXTDOMAINDIR. Standard search directory: /home/task_177204486800161/croot/gettext-split_1772044997948/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho/share/locale

+ +

AUTHOR + +

+ + +

Written by +Ulrich Drepper.

+ +

REPORTING BUGS + +

+ + +

Report bugs in +the bug tracker at +<https://savannah.gnu.org/projects/gettext> or by +email to <bug-gettext@gnu.org>.

+ +

COPYRIGHT + +

+ + +

Copyright +© 1995-2025 Free Software Foundation, Inc. +License GPLv3+: GNU GPL version 3 or later +<https://gnu.org/licenses/gpl.html>
+This is free software: you are free to change and +redistribute it. There is NO WARRANTY, to the extent +permitted by law.

+ +

SEE ALSO + +

+ + +

The full +documentation for ngettext is maintained as a Texinfo +manual. If the info and ngettext programs are +properly installed at your site, the command

+ +

info +ngettext

+ +

should give you +access to the complete manual.

+
+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/ngettext.3.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/ngettext.3.html new file mode 100644 index 0000000000000000000000000000000000000000..1e42951d1f2f035a2b6732bc3ab1523813428fd8 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/ngettext.3.html @@ -0,0 +1,138 @@ + + + + + + + + +NGETTEXT + + + + +

NGETTEXT

+ +NAME
+SYNOPSIS
+DESCRIPTION
+RETURN VALUE
+ERRORS
+BUGS
+SEE ALSO
+ +
+ + +

NAME + +

+ + +

ngettext, +dngettext, dcngettext - translate message and choose +plural form

+ +

SYNOPSIS + +

+ + +

#include +<libintl.h>

+ +

char * +ngettext (const char * msgid, const char * +msgid_plural,
+unsigned long int n);
+char * dngettext (const char * domainname, +
+const char * msgid, const char * +msgid_plural,
+unsigned long int n);
+char * dcngettext (const char * domainname, +
+const char * msgid, const char * +msgid_plural,
+unsigned long int n, int +category);

+ +

DESCRIPTION + +

+ + +

The +ngettext, dngettext and dcngettext +functions attempt to translate a text string into the +user’s native language, by looking up the appropriate +plural form of the translation in a message catalog.

+ +

Plural forms +are grammatical variants depending on the a number. Some +languages have two forms, called singular and plural. Other +languages have three forms, called singular, dual and +plural. There are also languages with four forms.

+ +

The +ngettext, dngettext and dcngettext +functions work like the gettext, dgettext and +dcgettext functions, respectively. Additionally, they +choose the appropriate plural form, which depends on the +number n and the language of the message catalog +where the translation was found.

+ +

In the +"C" locale, or if none of the used catalogs +contain a translation for msgid, the ngettext, +dngettext and dcngettext functions return +msgid if n == 1, or msgid_plural if +n != 1.

+ +

RETURN VALUE + +

+ + +

If a +translation was found in one of the specified catalogs, the +appropriate plural form is converted to the locale’s +codeset and returned. The resulting string is statically +allocated and must not be modified or freed. Otherwise +msgid or msgid_plural is returned, as +described above.

+ +

ERRORS + +

+ + +

errno is +not modified.

+ +

BUGS + +

+ + +

The return type +ought to be const char *, but is char * to +avoid warnings in C code predating ANSI C.

+ +

SEE ALSO + +

+ + + +

gettext(3), +dgettext(3), dcgettext(3)

+
+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/recode-sr-latin.1.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/recode-sr-latin.1.html new file mode 100644 index 0000000000000000000000000000000000000000..4e573499ecb1be0dc244f81f3c68738f5953a248 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/recode-sr-latin.1.html @@ -0,0 +1,123 @@ + + + + + + + + +RECODE-SR-LATIN + + + + +

RECODE-SR-LATIN

+ +NAME
+SYNOPSIS
+DESCRIPTION
+AUTHOR
+REPORTING BUGS
+COPYRIGHT
+SEE ALSO
+ +
+ + +

NAME + +

+ + + +

recode-sr-latin +- convert Serbian text from Cyrillic to Latin +script

+ +

SYNOPSIS + +

+ + + +

recode-sr-latin +[OPTION]

+ +

DESCRIPTION + +

+ + +

Recode Serbian +text from Cyrillic to Latin script. The input text is read +from standard input. The converted text is output to +standard output.

+ +

Informative +output:
+-h, --help

+ +

display this help and exit

+ +

-V, +--version

+ +

output version information and +exit

+ +

AUTHOR + +

+ + +

Written by +Danilo Segan and Bruno Haible.

+ +

REPORTING BUGS + +

+ + +

Report bugs in +the bug tracker at +<https://savannah.gnu.org/projects/gettext> or by +email to <bug-gettext@gnu.org>.

+ +

COPYRIGHT + +

+ + +

Copyright +© 2006-2025 Free Software Foundation, Inc. +License GPLv3+: GNU GPL version 3 or later +<https://gnu.org/licenses/gpl.html>
+This is free software: you are free to change and +redistribute it. There is NO WARRANTY, to the extent +permitted by law.

+ +

SEE ALSO + +

+ + +

The full +documentation for recode-sr-latin is maintained as a +Texinfo manual. If the info and +recode-sr-latin programs are properly installed at +your site, the command

+ +

info +recode-sr-latin

+ +

should give you +access to the complete manual.

+
+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/textdomain.3.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/textdomain.3.html new file mode 100644 index 0000000000000000000000000000000000000000..64beae64566eb7d5b25a2fbd5597b6c6e405dfb8 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/textdomain.3.html @@ -0,0 +1,140 @@ + + + + + + + + +TEXTDOMAIN + + + + +

TEXTDOMAIN

+ +NAME
+SYNOPSIS
+DESCRIPTION
+RETURN VALUE
+ERRORS
+BUGS
+SEE ALSO
+ +
+ + +

NAME + +

+ + +

textdomain +- set domain for future gettext() calls

+ +

SYNOPSIS + +

+ + +

#include +<libintl.h>

+ +

char * +textdomain (const char * domainname);

+ +

DESCRIPTION + +

+ + +

The +textdomain function sets or retrieves the current +message domain.

+ +

A message +domain is a set of translatable msgid messages. +Usually, every software package has its own message domain. +The domain name is used to determine the message catalog +where a translation is looked up; it must be a non-empty +string.

+ +

The current +message domain is used by the gettext, +ngettext functions, and by the dgettext, +dcgettext, dngettext and dcngettext +functions when called with a NULL domainname argument.

+ +

If +domainname is not NULL, the current message domain is +set to domainname. The string the function stores +internally is a copy of the domainname argument.

+ +

If +domainname is NULL, the function returns the current +message domain.

+ +

RETURN VALUE + +

+ + +

If successful, +the textdomain function returns the current message +domain, after possibly changing it. The resulting string is +valid until the next textdomain call and must not be +modified or freed. If a memory allocation failure occurs, it +sets errno to ENOMEM and returns NULL.

+ +

ERRORS + +

+ + +

The following +error can occur, among others:

+ + + + + + + + +
+ + +

ENOMEM

 + + +

Not enough memory available.

 +
+ +

BUGS + +

+ + +

The return type +ought to be const char *, but is char * to +avoid warnings in C code predating ANSI C.

+ +

SEE ALSO + +

+ + + +

gettext(3), +ngettext(3), bindtextdomain(3), +bind_textdomain_codeset(3)

+
+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/tutorial.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/tutorial.html new file mode 100644 index 0000000000000000000000000000000000000000..c5685355fdaf8fc44d049743d5ed00881da7c342 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/tutorial.html @@ -0,0 +1,745 @@ + + + + + + +A tutorial on Native Language Support using GNU gettext + + + + + + + + + + + + + + + + + +

A tutorial on Native Language Support using GNU gettext

+ +

G. Mohanty

+

Revision 0.3: 24 July 2004

+
+ +

Abstract:

+
+ The use of the GNU gettext 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 gettext should work +in a similar fashion. + +

+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. +

+

+

+Introduction +

+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 gettext 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. gettext 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. + +

+This article describes how to support native languages under a system using +the GNU gettext utilities. While it should be applicable to other versions of +gettext, the one actually used for the examples here is version +0.12.1. Another system, called catgets, described in the X/Open +Portability Guide, is also in use, but we shall not discuss that here. + +

+ +

+A simple example +

+Our first example of using gettext 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: +
+1    #include <libintl.h>
+2    #include <locale.h>
+3    #include <stdio.h>
+4    #include <stdlib.h>
+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    }
+
+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 gcc -o hello hello.c. 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. + +

+The programmer's viewpoint +

+ As expected, when the hello 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 gettext(string), i.e., to +instead pass the string as an argument to the gettext 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, +
+  #define _(STRING)    gettext(STRING)
+
+and then use _(string) instead of gettext(string). + +

+Let us dissect the program line-by-line. + +

    +
  1. locale.h defines C data structures used to hold locale + information, and is needed by the setlocale function. libintl.h + prototypes the GNU text utilities functions, and is needed here by + bindtextdomain, gettext, and textdomain. +
    2. +
  2. The call to setlocale () 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 setlocale.” +
    3. +
  3. The bindtextdomain 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 bindtextdomain 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 + bindtextdomain” for details. +
    4. +
  4. The textdomain 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. +
    5. +
  5. Finally, on line 10, we have replaced what would normally have been, +
    +  printf( "Hello, world!\n" );
+
    +with, +
    +  printf( gettext( "Hello, world!\n" ) );
+
    +(If you are unfamiliar with C, the +\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. gettextize eases the task of the programmer in adapting a +package to use GNU gettext for the first time, or to upgrade to a newer +version of gettext. +
    6. +
+ +

+Extracting translatable strings +

+ Now, it is time to extract the strings to be translated from the program +source code. This is achieved with xgettext, which can be invoked as follows: +

+  xgettext -d hello -o hello.pot hello.c
+
+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 +textdomain (on line 9 of the program source). Other details on how to use +gettext can be found from “man gettext.” + +

+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 msginit program, which takes care of correctly setting up some +default values, +


+  msginit -l or_IN -o oriya.po -i hello.pot
+
+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 msginit would look like: +
+  # 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 <gora_mohanty@yahoo.co.in>, 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 <gora_mohanty@yahoo.co.in>\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 ""
+
+msginit 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. + +

+It is important to respect the format of the entries in the .po (portable +object) file. Each entry has the following structure: +

+  WHITE-SPACE
+  #  TRANSLATOR-COMMENTS
+  #. AUTOMATIC-COMMENTS
+  #: REFERENCE...
+  #, FLAG...
+  msgid UNTRANSLATED-STRING
+  msgstr TRANSLATED-STRING
+
+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 gettext tools, +with a non-white-space character after the '#.' The msgid line contains +the untranslated (English) string, if there is one for that PO file entry, and +the msgstr 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. A for an +introduction to using the info-browser in Emacs). + +

+Making translations +

+ 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, kbabel, gtranslator, +poedit, etc. Appdx. B describes features of some of +these editors. + +

+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 msginit. 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 msgstr 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 msgid string +for the entry. For example, for the phrase “Hello world! +\n” in +oriya.po, we could enter “ନମସ୍କାର +\n”. The final +oriya.po file might look like: +

+  # 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 <gora_mohanty@yahoo.co.in>, 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 <gora_mohanty@yahoo.co.in>\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 "ନମସ୍କାର\n"
+
+ +

+For editing PO files, I have found the kbabel editor suits me the best. The +only problem is that while Oriya text can be entered directly into kbabel +using the xkb Oriya keyboard layouts [1] and the entries +are saved properly, the text is not displayed correctly in the kbabel 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. yudit +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 kbabel or Emacs po-mode, and then use yudit to enter +the Oriya text on the msgstr lines. + +

+Message catalogs +

+ After completing the translations in the oriya.po file, it must be compiled to +a binary format that can be quickly loaded by the gettext tools. To do that, +use: +

+  msgfmt -c -v -o hello.mo oriya.po
+
+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 bindtextdomain and textdomain on +lines 8 and 9 of the example program in Sec. 2. The .mo +(machine object) file should be stored in the location whose base directory is +given by the second argument to bindtextdomain. 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, +

+  mkdir -p /usr/share/locale/or_IN/LC_MESSAGES
+  cp hello.mo /usr/share/locale/or_IN/LC_MESSAGES
+
+ +

+The user's viewpoint +

+ 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, +

+  echo $LANG
+  export LANG=or_IN
+
+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. + +

+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 -> Character Coding -> +Unicode (UTF-8), or (b) typing “/bin/echo -n -e +' +\033% +\G'” in the terminal, or (c) by running +/bin/unicode_start. Likewise, you can revert to the default locale by (a) +choosing Terminal -> Character Coding -> Current Locale +(ISO-8859-1), or (b) “/bin/echo -n -e ' +\033% +\@',” or +(c) by running /bin/unicode_stop. Now, running the example program (after +compiling with gcc as described in Sec. 2) with, +


+  ./hello
+
+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. + +

+An alternative is to save the program output in a file, and view it with +yudit which will render the glyphs correctly. Thus, +


+  ./hello > junk
+  yudit junk
+
+Do not forget to reset the locale before resuming usual work in the +terminal. Else, your English characters might look funny. + +

+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. + +

+ +

+Adding complications: program upgrade +

+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 printf statement after the first one. Our new hello.c source +code might look like this: +
+1    #include <libintl.h>
+2    #include <locale.h>
+3    #include <stdio.h>
+4    #include <stdlib.h>
+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    }
+
+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 gettext utilities handle the drudgery +of combining the new translations with the old ones. This is indeed possible. + +

+Merging old and new translations +

+ As before, extract the translatable strings from hello.c to a new portable +object template file, hello-new.pot, using xgettext, +

+  xgettext -d hello -o hello-new.pot hello.c
+
+Now, we use a new program, msgmerge, to merge the existing .po file with +translations into the new template file, viz., +

+  msgmerge -U oriya.po hello-new.pot
+
+The -U option updates the existing +.po file, oriya.po. We could have chosen to instead create a new .po file by +using “-o <filename>” instead of -U. The updated .po file will still +have the old translations embedded in it, and new entries with untranslated +msgid lines. For us, the new lines in oriya.po will look like, +
+  #: hello.c:11
+  msgid "How are you?\n"
+  msgstr ""
+
+For the new translation, we could use, “ଆପଣ +କିପରି ଅଛନ୍ତି?” in +place of the English phrase “How are you?” The updated oriya.po file, +including the translation might look like: +
+  # 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 <gora_mohanty@yahoo.co.in>, 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 <gora_mohanty@yahoo.co.in>\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 "ନମସ୍କାର\n"
+
+  #: hello.c:11
+  msgid "How are you?\n"
+  msgstr "ଆପଣ କିପରି ଅଛନ୍ତି?\n"
+
+ +

+Compile oriya.po to a machine object file, and install in the appropriate +place as in Sec. 2.4. Thus, +


+  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
+
+You can test the Oriya output as above, after recompiling hello.c and running +it in an Oriya locale. + +

+ +

+More about gettext +

+The GNU gettext info pages provide a well-organized and complete description +of the gettext 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 gettext 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::. + +

+ +

+The work of translation +

+ 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 [2]. + +

+ +

+Acknowledgments +

+Extensive use has obviously been made of the GNU gettext manual in preparing +this document. I have also been helped by an article in the Linux +Journal [3]. + +

+This work is part of the project for enabling the use of Oriya under Linux. I +thank my uncle, N. M. 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. R. Pansari, +A. Nayak, and M. Chand is much appreciated. + +

+The Emacs info browser +

+You can start up Emacs from the command-line by typing “emacs,” or “emacs +<filename>.” It can be started from the menu in some desktops, e.g., on +my GNOME desktop, it is under Main Menu -> Programming -> +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. + +

+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 gettext menu items, +you can either scroll down to the line, +

+  * gettext: (gettext).                          GNU gettext utilities.
+
+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. + +

+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. + +

+A stand-alone info browser, independent of Emacs, is also available on many +systems. Thus, the gettext info page can also be accessed by typing +“info gettext” in a terminal. xinfo 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 gettext info page. + +

+ +

+PO file editors +

+While the yudit 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, poedit, +kbabel, and gtranslator. + +

+Emacs PO mode +

+ 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. + +

+poedit +

+ XXX: in preparation. + +

+KDE: the kbabel editor +

+ kbabel [4] is a more user-friendly and configurable editor than +either of Emacs po-mode or poedit. 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. + +

+GNOME: the gtranslator editor +

+ XXX: in preparation. + +

+Bibliography +

1 +
+G. Mohanty, +
A practical primer for using Oriya under Linux, v0.3, +
http://oriya.sarovar.org/docs/getting_started/index.html, 2004, +
Sec. 6.2 describes the xkb layouts for Oriya. + +

2 +
+G. Mohanty, +
A plan for Oriya localization, v0.1, +
http://oriya.sarovar.org/docs/translation_plan/index.html, + 2004. + +

3 +
+Linux Journal article on internationalization, +
https://www.linuxjournal.com/article/3023. + +

4 +
+Features of the kbabel editor, +
http://i18n.kde.org/tools/kbabel/features.html. +
+ +

+About this document ... +

+ A tutorial on Native Language Support using GNU gettext

+This document was generated using the +LaTeX2HTML translator Version 2002-2-1 (1.70) +

+Copyright © 1993, 1994, 1995, 1996, +Nikos Drakos, +Computer Based Learning Unit, University of Leeds. +
Copyright © 1997, 1998, 1999, +Ross Moore, +Mathematics Department, Macquarie University, Sydney. +

+The command line arguments were:
+ latex2html -no_math -html_version 4.0,math,unicode,i18n,tables -split 0 memo +

+The translation was initiated by Gora Mohanty on 2004-07-24 +

+ + + +
+Gora Mohanty +2004-07-24 +
+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/xgettext.1.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/xgettext.1.html new file mode 100644 index 0000000000000000000000000000000000000000..7b2b5b9301c02f433b12628bb7ae380ac98f8622 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/gettext/xgettext.1.html @@ -0,0 +1,522 @@ + + + + + + + + +XGETTEXT + + + + +

XGETTEXT

+ +NAME
+SYNOPSIS
+DESCRIPTION
+AUTHOR
+REPORTING BUGS
+COPYRIGHT
+SEE ALSO
+ +
+ + +

NAME + +

+ + +

xgettext +- extract gettext strings from source

+ +

SYNOPSIS + +

+ + + +

xgettext +[OPTION] [INPUTFILE]...

+ +

DESCRIPTION + +

+ + +

Extract +translatable strings from given input files.

+ +

Mandatory +arguments to long options are mandatory for short options +too. Similarly for optional arguments.

+ +

Input file +location:
+INPUTFILE ...

+ +

input files

+ +

-f, +--files-from=FILE

+ +

get list of input files from +FILE

+ +

-D, +--directory=DIRECTORY

+ +

add DIRECTORY to list for input +files search

+ +

If input file +is -, standard input is read.

+ +

Output file +location:
+-d, +--default-domain=NAME

+ +

use NAME.po for output (instead +of messages.po)

+ +

-o, +--output=FILE

+ +

write output to specified +file

+ +

-p, +--output-dir=DIR

+ +

output files will be placed in +directory DIR

+ +

If output file +is -, output is written to standard output.

+ +

Choice of +input file language:
+-L, --language=NAME

+ +

recognise the specified +language (C, C++, ObjectiveC, PO, Python, Java, +JavaProperties, C#, JavaScript, TypeScript, TSX, Scheme, +Guile, Lisp, EmacsLisp, librep, Rust, Go, Ruby, Shell, awk, +Lua, Modula-2, D, Smalltalk, Vala, Tcl, Perl, PHP, +GCC-source, YCP, NXStringTable, RST, RSJ, Glade, +GSettings, Desktop)

+ +

-C, +--c++

+ +

shorthand for +--language=C++

+ +

By default the +language is guessed depending on the input file name +extension.

+ +

Input file +interpretation:
+--from-code=NAME

+ +

encoding of input files (except +for Python, Tcl, Glade)

+ +

By default the +input files are assumed to be in ASCII.

+ +

Operation +mode:
+-j, --join-existing

+ +

join messages with existing +file

+ +

-x, +--exclude-file=FILE.po

+ +

entries from FILE.po are not +extracted

+ +

-cTAG, +--add-comments=TAG

+ +

place comment blocks starting +with TAG and preceding keyword lines in output file

+ +

-c, +--add-comments

+ +

place all comment blocks +preceding keyword lines in output file

+ + +

--check=NAME

+ +

perform syntax check on +messages (ellipsis-unicode, space-ellipsis,

+ + +

quote-unicode, +bullet-unicode)

+ + +

--sentence-end=TYPE

+ +

type describing the end of +sentence (single-space, which is the default,

+ +

or +double-space)

+ +

Language +specific options:
+-a, --extract-all

+ +

extract all strings (only +languages C, C++, ObjectiveC, Python, Java, C#, JavaScript, +TypeScript, TSX, Scheme, Guile, Lisp, EmacsLisp, librep, +Rust, Go, Shell, awk, Lua, Modula-2, D, Vala, Tcl, +Perl, PHP, GCC-source, Glade, GSettings)

+ +

-kWORD, +--keyword=WORD

+ +

look for WORD as an additional +keyword

+ +

-k, +--keyword

+ +

do not to use default keywords +(only languages C, C++, ObjectiveC, Python, Java, C#, +JavaScript, TypeScript, TSX, Scheme, Guile, Lisp, EmacsLisp, +librep, Rust, Go, Shell, awk, Lua, Modula-2, D, Vala, +Tcl, Perl, PHP, GCC-source, Glade, GSettings, +Desktop)

+ + +

--flag=WORD:ARG:FLAG

+ +

additional flag for strings +inside the argument number ARG of keyword WORD

+ +

(only languages C, C++, +ObjectiveC, Python,

+ +

Java, C#, JavaScript, +TypeScript, TSX, Scheme, Guile, Lisp, EmacsLisp, librep, +Rust, Go, Shell, awk, Lua, Modula-2, D, Vala, Tcl, +Perl, PHP, GCC-source, YCP)

+ + +

--tag=WORD:FORMAT

+ +

defines the behaviour of tagged +template literals with tag WORD

+ +

(only language +JavaScript)

+ +

-T, +--trigraphs

+ +

understand ANSI C trigraphs for +input (deprecated; only languages C, C++, ObjectiveC)

+ + +

--its=FILE

+ +

apply ITS rules from FILE (only +XML based languages)

+ + + + + + + + + + + + + + +
+ + +

--qt

 + + +

recognize Qt format strings (only language C++)

 +
+ + +

--kde

 + + +

recognize KDE 4 format strings (only language C++)

 +
+ +

--boost

+ +

recognize Boost format strings +(only language C++)

+ +

--debug

+ +

more detailed formatstring +recognition result

+ +

Output +details:
+--color

+ +

use colors and other text +attributes always

+ + +

--color=WHEN

+ +

use colors and other text +attributes if WHEN. WHEN may be ’always’, +’never’, ’auto’, or +’html’.

+ + +

--style=STYLEFILE

+ +

specify CSS style rule file for +--color

+ +

-e, +--no-escape

+ +

do not use C escapes in output +(default)

+ +

-E, +--escape

+ +

use C escapes in output, no +extended chars

+ + +

--force-po

+ +

write PO file even if empty

+ +

-i, +--indent

+ +

write the .po file using +indented style

+ + +

--no-location

+ +

do not write ’#: +filename:line’ lines

+ +

-n, +--add-location

+ +

generate ’#: +filename:line’ lines (default)

+ + +

--strict

+ +

write out strict Uniforum +conforming .po file

+ + +

--properties-output

+ +

write out a Java .properties +file

+ + +

--stringtable-output

+ +

write out a NeXTstep/GNUstep +.strings file

+ + +

--itstool

+ +

write out itstool comments

+ +

-w, +--width=NUMBER

+ +

set output page width

+ + +

--no-wrap

+ +

do not break long message +lines, longer than the output page width, into several +lines

+ +

-s, +--sort-output

+ +

generate sorted output +(deprecated)

+ +

-F, +--sort-by-file

+ +

sort output by file +location

+ + +

--omit-header

+ +

don’t write header with +’msgid ""’ entry

+ + +

--no-git

+ +

don’t use the git program +to produce a reproducible +’POT-Creation-Date’ field in the +output.

+ + +

--copyright-holder=STRING

+ +

set copyright holder in +output

+ + +

--foreign-user

+ +

omit FSF copyright in output +for foreign user

+ + +

--package-name=PACKAGE

+ +

set package name in output

+ + +

--package-version=VERSION

+ +

set package version in +output

+ + +

--msgid-bugs-address=EMAIL@ADDRESS

+ +

set report address for msgid +bugs

+ + +

--generated=FILE

+ +

Declares that the given FILE is +generated and therefore should not have an influence on the +’POT-Creation-Date’ field in the +output.

+ + +

--reference=FILE

+ +

Declares that the output +depends on the contents of the given FILE. This has an +influence on the ’POT-Creation-Date’ +field in the output.

+ +

-m[STRING], +--msgstr-prefix[=STRING]

+ +

use STRING or "" as +prefix for msgstr values

+ +

-M[STRING], +--msgstr-suffix[=STRING]

+ +

use STRING or "" as +suffix for msgstr values

+ +

Informative +output:
+-h, --help

+ +

display this help and exit

+ +

-V, +--version

+ +

output version information and +exit

+ +

-v, +--verbose

+ +

increase verbosity level

+ +

AUTHOR + +

+ + +

Written by +Ulrich Drepper.

+ +

REPORTING BUGS + +

+ + +

Report bugs in +the bug tracker at +<https://savannah.gnu.org/projects/gettext> or by +email to <bug-gettext@gnu.org>.

+ +

COPYRIGHT + +

+ + +

Copyright +© 1995-2025 Free Software Foundation, Inc. +License GPLv3+: GNU GPL version 3 or later +<https://gnu.org/licenses/gpl.html>
+This is free software: you are free to change and +redistribute it. There is NO WARRANTY, to the extent +permitted by law.

+ +

SEE ALSO + +

+ + +

The full +documentation for xgettext is maintained as a Texinfo +manual. If the info and xgettext programs are +properly installed at your site, the command

+ +

info +xgettext

+ +

should give you +access to the complete manual.

+
+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/libasprintf/autosprintf_all.html b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/libasprintf/autosprintf_all.html new file mode 100644 index 0000000000000000000000000000000000000000..b8760c0795711baa9053fadfe8acf99255a51fc3 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/doc/libasprintf/autosprintf_all.html @@ -0,0 +1,1625 @@ + + + + + +GNU autosprintf + + + + + + + + + + + + + + +

GNU autosprintf

+ +

Table of Contents

+
+ + +
+ + + + +

This manual documents the GNU autosprintf class, version 1.0. +

+ + +
+ + +

1. Introduction

+ +

This package makes the C formatted output routines (fprintf et al.) +usable in C++ programs, for use with the <string> strings and the +<iostream> streams. +

+

It allows to write code like +

+
 
cerr << autosprintf ("syntax error in %s:%d: %s", filename, line, errstring);
+
+ +

instead of +

+
 
cerr << "syntax error in " << filename << ":" << line << ": " << errstring;
+
+ +

The benefits of the autosprintf syntax are: +

+
    +
  • +It reuses the standard POSIX printf facility. Easy migration from C to C++. + +
  • +English sentences are kept together. + +
  • +It makes internationalization possible. Internationalization requires format +strings, because in some cases the translator needs to change the order of a +sentence, and more generally it is easier for the translator to work with a +single string for a sentence than with multiple string pieces. + +
  • +It reduces the risk of programming errors due to forgotten state in the +output stream (e.g. cout << hex; not followed by cout << dec;). +
+ + + + +

2. The autosprintf class

+ +

An instance of class autosprintf just contains a string with the +formatted output result. Such an instance is usually allocated as an +automatic storage variable, i.e. on the stack, not with new on the +heap. +

+

The constructor autosprintf (const char *format, ...) takes a format +string and additional arguments, like the C function printf. +

+

Conversions to char * and std::string are defined that return +the encapsulated string. The conversion to char * returns a freshly +allocated copy of the encapsulated string; it needs to be freed using +delete[]. The conversion to std::string returns a copy of +the encapsulated string, with automatic memory management. +

+

The destructor ~autosprintf () destroys the encapsulated string. +

+

An operator << is provided that outputs the encapsulated string to the +given ostream. +

+ + + +

3. Using autosprintf in own programs

+ +

To use the autosprintf class in your programs, you need to add +

+
 
#include "autosprintf.h"
+using gnu::autosprintf;
+
+ +

to your source code. +The include file defines the class autosprintf, in a namespace called +gnu. The ‘using’ statement makes it possible to use the class +without the (otherwise natural) gnu:: prefix. +

+

When linking your program, you need to link with libasprintf, because +that's where the class is defined. In projects using GNU autoconf, +this means adding ‘AC_LIB_LINKFLAGS([asprintf])’ to configure.in +or configure.ac, and using the @LIBASPRINTF@ Makefile variable that +it provides. +

+ + + +

A. Licenses

+ +

The files of this package are covered by the licenses indicated in each +particular file or directory. Here is a summary: +

+
    +
  • +The libasprintf library is covered by the +GNU Lesser General Public License (LGPL), either version 2.1 of the +License, or (at your option) any later version published by the +Free Software Foundation (FSF). +A copy of the license is included in GNU LESSER GENERAL PUBLIC LICENSE. + +
  • +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 included in GNU Free Documentation License. +
    +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 included in GNU GENERAL PUBLIC LICENSE. +
+ + + + + + +

A.1 GNU LESSER GENERAL PUBLIC LICENSE

+

Version 2.1, February 1999 +

+ +
 
Copyright © 1991, 1999 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.
+
+[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—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. +

+

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. +

+ +

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

+ +
    +
  1. +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. +

    +
  2. +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. +

    +
  3. +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: + +
      +
    1. +The modified work must itself be a software library. + +
    2. +You must cause the files modified to carry prominent notices +stating that you changed the files and the date of any change. + +
    3. +You must cause the whole of the work to be licensed at no +charge to all third parties under the terms of this License. + +
    4. +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. +

    +
  4. +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. + +

    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. +

    +
  5. +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. +

    +
  6. +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. +

    +
  7. +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: +

    +
      +
    1. +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.) + +
    2. +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. + +
    3. +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. + +
    4. +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. + +
    5. +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. +

    +
  8. +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: + +
      +
    1. +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. + +
    2. +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. +
    + +
  9. +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. + +
  10. +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. + +
  11. +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. + +
  12. +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. +

    +
  13. +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. + +
  14. +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. +

    +
  15. +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 +

    +
  16. +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. + +
  17. +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

+ + + +

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 an 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.1 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, see <https://www.gnu.org/licenses/>.
+
+ +

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 Moe Ghoul, 1 April 1990
+Moe Ghoul, President of Vice
+
+ +

That's all there is to it! + +

+ + +

A.2 GNU GENERAL PUBLIC LICENSE

+

Version 2, June 1991 +

+ +
 
Copyright © 1989, 1991 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 licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +License is intended to guarantee your freedom to share and change free +software—to make sure the software is free for all its users. This +General Public License applies to most of the Free Software +Foundation's software and to any other program whose authors commit to +using it. (Some other Free Software Foundation software is covered by +the GNU Lesser General Public License instead.) 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 +this service 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 make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the rights. +These restrictions translate to certain responsibilities for you if you +distribute copies of the software, or if you modify it. +

+

For example, if you distribute copies of such a program, whether +gratis or for a fee, you must give the recipients all the rights that +you have. 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. +

+

We protect your rights with two steps: (1) copyright the software, and +(2) offer you this license which gives you legal permission to copy, +distribute and/or modify the software. +

+

Also, for each author's protection and ours, we want to make certain +that everyone understands that there is no warranty for this free +software. If the software is modified by someone else and passed on, we +want its recipients to know that what they have is not the original, so +that any problems introduced by others will not reflect on the original +authors' reputations. +

+

Finally, any free program is threatened constantly by software +patents. We wish to avoid the danger that redistributors of a free +program will individually obtain patent licenses, in effect making the +program proprietary. To prevent this, we have made it clear that any +patent must be licensed for everyone's free use or not licensed at all. +

+

The precise terms and conditions for copying, distribution and +modification follow. +

+ +

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

+ +
    +
  1. +This License applies to any program or other work which contains +a notice placed by the copyright holder saying it may be distributed +under the terms of this General Public License. The “Program”, below, +refers to any such program or work, and a “work based on the Program” +means either the Program or any derivative work under copyright law: +that is to say, a work containing the Program or a portion of it, +either verbatim or with modifications and/or translated into another +language. (Hereinafter, translation is included without limitation in +the term “modification”.) Each licensee is addressed as “you”. + +

    Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running the Program is not restricted, and the output from the Program +is covered only if its contents constitute a work based on the +Program (independent of having been made by running the Program). +Whether that is true depends on what the Program does. +

    +
  2. +You may copy and distribute 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 and disclaimer of warranty; keep intact all the +notices that refer to this License and to the absence of any warranty; +and give any other recipients of the Program a copy of this License +along with the Program. + +

    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. +

    +
  3. +You may modify your copy or copies of the Program or any portion +of it, thus forming a work based on the Program, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + +
      +
    1. +You must cause the modified files to carry prominent notices +stating that you changed the files and the date of any change. + +
    2. +You must cause any work that you distribute or publish, that in +whole or in part contains or is derived from the Program or any +part thereof, to be licensed as a whole at no charge to all third +parties under the terms of this License. + +
    3. +If the modified program normally reads commands interactively +when run, you must cause it, when started running for such +interactive use in the most ordinary way, to print or display an +announcement including an appropriate copyright notice and a +notice that there is no warranty (or else, saying that you provide +a warranty) and that users may redistribute the program under +these conditions, and telling the user how to view a copy of this +License. (Exception: if the Program itself is interactive but +does not normally print such an announcement, your work based on +the Program is not required to print an announcement.) +
    + +

    These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Program, +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 Program, 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 Program. +

    +

    In addition, mere aggregation of another work not based on the Program +with the Program (or with a work based on the Program) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. +

    +
  4. +You may copy and distribute the Program (or a work based on it, +under Section 2) in object code or executable form under the terms of +Sections 1 and 2 above provided that you also do one of the following: + +
      +
    1. +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; or, + +
    2. +Accompany it with a written offer, valid for at least three +years, to give any third party, for a charge no more than your +cost of physically performing source distribution, a complete +machine-readable copy of the corresponding source code, to be +distributed under the terms of Sections 1 and 2 above on a medium +customarily used for software interchange; or, + +
    3. +Accompany it with the information you received as to the offer +to distribute corresponding source code. (This alternative is +allowed only for noncommercial distribution and only if you +received the program in object code or executable form with such +an offer, in accord with Subsection b above.) +
    + +

    The source code for a work means the preferred form of the work for +making modifications to it. For an executable work, 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 executable. However, as a +special exception, the source code 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. +

    +

    If distribution of executable or 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 counts as +distribution of the source code, even though third parties are not +compelled to copy the source along with the object code. +

    +
  5. +You may not copy, modify, sublicense, or distribute the Program +except as expressly provided under this License. Any attempt +otherwise to copy, modify, sublicense or distribute the Program 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. + +
  6. +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 Program or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Program (or any work based on the +Program), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Program or works based on it. + +
  7. +Each time you redistribute the Program (or any work based on the +Program), the recipient automatically receives a license from the +original licensor to copy, distribute or modify the Program 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 to +this License. + +
  8. +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 Program at all. For example, if a patent +license would not permit royalty-free redistribution of the Program 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 Program. + +

    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. +

    +
  9. +If the distribution and/or use of the Program is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Program 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. + +
  10. +The Free Software Foundation may publish revised and/or new versions +of the 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 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 Program does not specify a version number of +this License, you may choose any version ever published by the Free Software +Foundation. +

    +
  11. +If you wish to incorporate parts of the Program into other free +programs whose distribution conditions are different, 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. + + +
  12. +BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, 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. + +
  13. +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 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. +
+ + + + +

Appendix: 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 +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 program's name and a brief idea of what it does.
+Copyright (C) yyyy  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 2 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 is interactive, make it output a short notice like this +when it starts in an interactive mode: +

+
 
Gnomovision version 69, Copyright (C) year name of author
+Gnomovision 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, the +commands you use may be called something other than ‘show w’ and +‘show c’; they could even be mouse-clicks or menu items—whatever +suits your program. +

+

You should also get your employer (if you work as a programmer) or your +school, if any, to sign a “copyright disclaimer” for the program, if +necessary. Here is a sample; alter the names: +

+
 
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+`Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+signature of Moe Ghoul, 1 April 1989
+Moe Ghoul, President of Vice
+
+ +

This 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. + +

+ + +

A.3 GNU Free Documentation License

+

Version 1.3, 3 November 2008 +

+ +
 
Copyright © 2000, 2001, 2002, 2007, 2008 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.
+
+ +
    +
  1. +PREAMBLE + +

    The purpose of this License is to make a manual, textbook, or other +functional and useful document 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. +

    +
  2. +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 +ASCII without markup, Texinfo input format, LaTeX input +format, SGML or XML using a publicly available +DTD, and standard-conforming simple HTML, +PostScript or PDF designed for human modification. Examples +of transparent image formats include PNG, XCF and +JPG. Opaque formats include proprietary formats that can be +read and edited only by proprietary word processors, SGML or +XML for which the DTD and/or processing tools are +not generally available, and the machine-generated HTML, +PostScript or 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. +

    +

    The “publisher” means any person or entity that distributes copies +of the Document to the public. +

    +

    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. +

    +
  3. +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. +

    +
  4. +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. +

    +
  5. +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: +

    +
      +
    1. +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. + +
    2. +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. + +
    3. +State on the Title page the name of the publisher of the +Modified Version, as the publisher. + +
    4. +Preserve all the copyright notices of the Document. + +
    5. +Add an appropriate copyright notice for your modifications +adjacent to the other copyright notices. + +
    6. +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. + +
    7. +Preserve in that license notice the full lists of Invariant Sections +and required Cover Texts given in the Document's license notice. + +
    8. +Include an unaltered copy of this License. + +
    9. +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. + +
    10. +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. + +
    11. +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. + +
    12. +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. + +
    13. +Delete any section Entitled “Endorsements”. Such a section +may not be included in the Modified Version. + +
    14. +Do not retitle any existing section to be Entitled “Endorsements” or +to conflict in title with any Invariant Section. + +
    15. +Preserve any Warranty Disclaimers. +
    + +

    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. +

    +
  6. +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.” +

    +
  7. +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. +

    +
  8. +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. +

    +
  9. +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. +

    +
  10. +TERMINATION + +

    You may not copy, modify, sublicense, or distribute the Document +except as expressly provided under this License. Any attempt +otherwise to copy, modify, sublicense, or distribute it is void, and +will automatically terminate your rights under this License. +

    +

    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, receipt of a copy of some or all of the same material does +not give you any rights to use it. +

    +
  11. +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 +https://www.gnu.org/licenses/. +

    +

    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. If the Document +specifies that a proxy can decide which future versions of this +License can be used, that proxy's public statement of acceptance of a +version permanently authorizes you to choose that version for the +Document. +

    +
  12. +RELICENSING + +

    “Massive Multiauthor Collaboration Site” (or “MMC Site”) means any +World Wide Web server that publishes copyrightable works and also +provides prominent facilities for anybody to edit those works. A +public wiki that anybody can edit is an example of such a server. A +“Massive Multiauthor Collaboration” (or “MMC”) contained in the +site means any set of copyrightable works thus published on the MMC +site. +

    +

    “CC-BY-SA” means the Creative Commons Attribution-Share Alike 3.0 +license published by Creative Commons Corporation, a not-for-profit +corporation with a principal place of business in San Francisco, +California, as well as future copyleft versions of that license +published by that same organization. +

    +

    “Incorporate” means to publish or republish a Document, in whole or +in part, as part of another Document. +

    +

    An MMC is “eligible for relicensing” if it is licensed under this +License, and if all works that were first published under this License +somewhere other than this MMC, and subsequently incorporated in whole +or in part into the MMC, (1) had no cover texts or invariant sections, +and (2) were thus incorporated prior to November 1, 2008. +

    +

    The operator of an MMC Site may republish an MMC contained in the site +under CC-BY-SA on the same site at any time before August 1, 2009, +provided the MMC is eligible for relicensing. +

    +
+ + + +

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: +

+
 
  Copyright (C)  year  your name.
+  Permission is granted to copy, distribute and/or modify this document
+  under the terms of the GNU Free Documentation License, Version 1.3
+  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''.
+
+ +

If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, +replace the “with…Texts.” line with this: +

+
 
    with the Invariant Sections being list their titles, with
+    the Front-Cover Texts being list, and with the Back-Cover Texts
+    being list.
+
+ +

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. +

+ + +

+ + This document was generated by Bruno Haible on June, 4 2025 using texi2html 1.78a. + +
+ +

+ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/docbook.loc b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/docbook.loc new file mode 100644 index 0000000000000000000000000000000000000000..9baf810610c877b8417426ad5399392241629f37 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/docbook.loc @@ -0,0 +1,42 @@ + + + + + + + + + + + + + + + + + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/docbook4.its b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/docbook4.its new file mode 100644 index 0000000000000000000000000000000000000000..1c39ce21e7a18fa4951b11078845eabb88225f0c --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/docbook4.its @@ -0,0 +1,236 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/docbook5.its b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/docbook5.its new file mode 100644 index 0000000000000000000000000000000000000000..2d448928c3b5d5914bf767d15767f35c538cd242 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/docbook5.its @@ -0,0 +1,224 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/glade.loc b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/glade.loc new file mode 100644 index 0000000000000000000000000000000000000000..eb9b1bc82987f7101c1baa18b2b59f2b4b7753d7 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/glade.loc @@ -0,0 +1,31 @@ + + + + + + + + + + + + + + + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/glade1.its b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/glade1.its new file mode 100644 index 0000000000000000000000000000000000000000..42f73b78031d0d0ac6aa48998587a3959aa88173 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/glade1.its @@ -0,0 +1,37 @@ + + + + + + + + + + + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/glade2.its b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/glade2.its new file mode 100644 index 0000000000000000000000000000000000000000..8b38db7509476355b8482948981b7e874a83bfe9 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/glade2.its @@ -0,0 +1,52 @@ + + + + + + + + + + + + + + + + + + + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/gsettings.its b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/gsettings.its new file mode 100644 index 0000000000000000000000000000000000000000..fe963846b50ed3183ac0ff16dcfd2e982026a1db --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/gsettings.its @@ -0,0 +1,39 @@ + + + + + + + + + + + + + + + + + + + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/gsettings.loc b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/gsettings.loc new file mode 100644 index 0000000000000000000000000000000000000000..308e4517c3f3854b5ac7c027af476a33b26cad25 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/gsettings.loc @@ -0,0 +1,23 @@ + + + + + + + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/gtkbuilder.its b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/gtkbuilder.its new file mode 100644 index 0000000000000000000000000000000000000000..9d28531a78e578f896eba324e576f15306f11ccd --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/gtkbuilder.its @@ -0,0 +1,49 @@ + + + + + + + + + + + + + + + + + + + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/metainfo.its b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/metainfo.its new file mode 100644 index 0000000000000000000000000000000000000000..3923614c52a62c04e0bc704d11f64ddbd7f1900d --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/metainfo.its @@ -0,0 +1,56 @@ + + + + + + + + + + + + + + + + + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/metainfo.loc b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/metainfo.loc new file mode 100644 index 0000000000000000000000000000000000000000..64fff224df0e84e06a150ff7d1a682f1a5877857 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext-0.25.1/its/metainfo.loc @@ -0,0 +1,26 @@ + + + + + + + + + + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/ABOUT-NLS b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/ABOUT-NLS new file mode 100644 index 0000000000000000000000000000000000000000..0a9d56d9e79bf5cd209a6fc6a7c8cddade70b16d --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/ABOUT-NLS @@ -0,0 +1 @@ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/config.rpath b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/config.rpath new file mode 100644 index 0000000000000000000000000000000000000000..43dc3042de2a4bf288baa42f6f3b736e0f7c25f8 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/config.rpath @@ -0,0 +1,751 @@ +#! /bin/sh +# Output a system dependent set of variables, describing how to set the +# run time search path of shared libraries in a binary (executable or +# shared library). +# +# Copyright 1996-2025 Free Software Foundation, Inc. +# Taken from GNU libtool, 2001 +# Originally by Gordon Matzigkeit , 1996 +# +# This file is free software; the Free Software Foundation gives +# unlimited permission to copy and/or distribute it, with or without +# modifications, as long as this notice is preserved. + +# Known limitations: +# - On IRIX 6.5 with CC="cc", the run time search patch must not be longer +# than 256 bytes, otherwise the compiler driver will dump core. The only +# known workaround is to choose shorter directory names for the build +# directory and/or the installation directory. + +# func_usage +# outputs to stdout the --help usage message. +func_usage () +{ + echo "\ +Usage: config.rpath [OPTION] HOST + +Prints shell variable assignments that describe how to hardcode a directory +for the lookup of shared libraries into a binary (executable or shared library). + +The first argument passed to this file is the canonical host specification, + CPU_TYPE-MANUFACTURER-OPERATING_SYSTEM +or + CPU_TYPE-MANUFACTURER-KERNEL-OPERATING_SYSTEM + +The environment variables CC, GCC, LDFLAGS, LD, with_gnu_ld +should be set by the caller. + +The set of defined variables is at the end of this script. + +Options: + --help print this help and exit + --version print version information and exit + +Send patches and bug reports to ." +} + +# func_version +# outputs to stdout the --version message. +func_version () +{ + echo "config.rpath (GNU gnulib, module havelib)" + echo "Copyright (C) 2025 Free Software Foundation, Inc. +License: All-Permissive. +This is free software: you are free to change and redistribute it. +There is NO WARRANTY, to the extent permitted by law." + echo + printf 'Written by %s.\n' "Bruno Haible" +} + +# func_fatal_error message +# outputs to stderr a fatal error message, and terminates the program. +func_fatal_error () +{ + echo "config.rpath: *** $1" 1>&2 + echo "config.rpath: *** Stop." 1>&2 + exit 1 +} + +# Command-line option processing. +while test $# -gt 0; do + case "$1" in + --help | --hel | --he | --h ) + func_usage + exit 0 ;; + --version | --versio | --versi | --vers | --ver | --ve | --v ) + func_version + exit 0 ;; + -- ) # Stop option processing + shift; break ;; + -* ) + func_fatal_error "unrecognized option: $1" + ;; + * ) + break ;; + esac +done + +if test $# -gt 1; then + func_fatal_error "too many arguments" +fi +if test $# -lt 1; then + func_fatal_error "too few arguments" +fi + +# All known linkers require a '.a' archive for static linking (except MSVC, +# which needs '.lib'). +libext=a +shrext=.so + +host="$1" +host_cpu=`echo "$host" | sed 's/^\([^-]*\)-\([^-]*\)-\(.*\)$/\1/'` +host_vendor=`echo "$host" | sed 's/^\([^-]*\)-\([^-]*\)-\(.*\)$/\2/'` +host_os=`echo "$host" | sed 's/^\([^-]*\)-\([^-]*\)-\(.*\)$/\3/'` + +# Code taken from libtool.m4's _LT_CC_BASENAME. + +for cc_temp in $CC""; do + case $cc_temp in + compile | *[\\/]compile | ccache | *[\\/]ccache ) ;; + distcc | *[\\/]distcc | purify | *[\\/]purify ) ;; + \-*) ;; + *) break;; + esac +done +cc_basename=`echo "$cc_temp" | sed -e 's%^.*/%%'` + +# Code taken from libtool.m4's _LT_COMPILER_PIC. + +wl= +if test "$GCC" = yes; then + wl='-Wl,' +else + case "$host_os" in + aix*) + wl='-Wl,' + ;; + mingw* | cygwin* | pw32* | os2* | cegcc*) + ;; + hpux9* | hpux10* | hpux11*) + wl='-Wl,' + ;; + irix5* | irix6* | nonstopux*) + wl='-Wl,' + ;; + linux* | k*bsd*-gnu | kopensolaris*-gnu) + case $cc_basename in + ecc*) + wl='-Wl,' + ;; + icc* | ifort*) + wl='-Wl,' + ;; + lf95*) + wl='-Wl,' + ;; + nagfor*) + wl='-Wl,-Wl,,' + ;; + pgcc* | pgf77* | pgf90* | pgf95* | pgfortran*) + wl='-Wl,' + ;; + ccc*) + wl='-Wl,' + ;; + xl* | bgxl* | bgf* | mpixl*) + wl='-Wl,' + ;; + como) + wl='-lopt=' + ;; + *) + case `$CC -V 2>&1 | sed 5q` in + *Sun\ F* | *Sun*Fortran*) + wl= + ;; + *Sun\ C*) + wl='-Wl,' + ;; + esac + ;; + esac + ;; + newsos6) + ;; + *nto* | *qnx*) + ;; + osf3* | osf4* | osf5*) + wl='-Wl,' + ;; + rdos*) + ;; + solaris*) + case $cc_basename in + f77* | f90* | f95* | sunf77* | sunf90* | sunf95*) + wl='-Qoption ld ' + ;; + *) + wl='-Wl,' + ;; + esac + ;; + sunos4*) + wl='-Qoption ld ' + ;; + sysv4 | sysv4.2uw2* | sysv4.3*) + wl='-Wl,' + ;; + sysv4*MP*) + ;; + sysv5* | unixware* | sco3.2v5* | sco5v6* | OpenUNIX*) + wl='-Wl,' + ;; + unicos*) + wl='-Wl,' + ;; + uts4*) + ;; + esac +fi + +# Code taken from libtool.m4's _LT_LINKER_SHLIBS. + +hardcode_libdir_flag_spec= +hardcode_libdir_separator= +hardcode_direct=no +hardcode_minus_L=no + +case "$host_os" in + cygwin* | mingw* | pw32* | cegcc*) + # FIXME: the MSVC++ port hasn't been tested in a loooong time + # When not using gcc, we currently assume that we are using + # Microsoft Visual C++. + if test "$GCC" != yes; then + with_gnu_ld=no + fi + ;; + interix*) + # we just hope/assume this is gcc and not c89 (= MSVC++) + with_gnu_ld=yes + ;; + openbsd*) + with_gnu_ld=no + ;; +esac + +ld_shlibs=yes +if test "$with_gnu_ld" = yes; then + # Set some defaults for GNU ld with shared library support. These + # are reset later if shared libraries are not supported. Putting them + # here allows them to be overridden if necessary. + # Unlike libtool, we use -rpath here, not --rpath, since the documented + # option of GNU ld is called -rpath, not --rpath. + hardcode_libdir_flag_spec='${wl}-rpath ${wl}$libdir' + case "$host_os" in + aix[3-9]*) + # On AIX/PPC, the GNU linker is very broken + if test "$host_cpu" != ia64; then + ld_shlibs=no + fi + ;; + amigaos*) + case "$host_cpu" in + powerpc) + ;; + m68k) + hardcode_libdir_flag_spec='-L$libdir' + hardcode_minus_L=yes + ;; + esac + ;; + beos*) + if $LD --help 2>&1 | grep ': supported targets:.* elf' > /dev/null; then + : + else + ld_shlibs=no + fi + ;; + cygwin* | mingw* | pw32* | cegcc*) + # hardcode_libdir_flag_spec is actually meaningless, as there is + # no search path for DLLs. + hardcode_libdir_flag_spec='-L$libdir' + if $LD --help 2>&1 | grep 'auto-import' > /dev/null; then + : + else + ld_shlibs=no + fi + ;; + haiku*) + ;; + interix[3-9]*) + hardcode_direct=no + hardcode_libdir_flag_spec='${wl}-rpath,$libdir' + ;; + gnu* | linux* | tpf* | k*bsd*-gnu | kopensolaris*-gnu) + if $LD --help 2>&1 | grep ': supported targets:.* elf' > /dev/null; then + : + else + ld_shlibs=no + fi + ;; + netbsd*) + ;; + solaris*) + if $LD -v 2>&1 | grep 'BFD 2\.8' > /dev/null; then + ld_shlibs=no + elif $LD --help 2>&1 | grep ': supported targets:.* elf' > /dev/null; then + : + else + ld_shlibs=no + fi + ;; + sysv5* | sco3.2v5* | sco5v6* | unixware* | OpenUNIX*) + case `$LD -v 2>&1` in + *\ [01].* | *\ 2.[0-9].* | *\ 2.1[0-5].*) + ld_shlibs=no + ;; + *) + if $LD --help 2>&1 | grep ': supported targets:.* elf' > /dev/null; then + hardcode_libdir_flag_spec='`test -z "$SCOABSPATH" && echo ${wl}-rpath,$libdir`' + else + ld_shlibs=no + fi + ;; + esac + ;; + sunos4*) + hardcode_direct=yes + ;; + *) + if $LD --help 2>&1 | grep ': supported targets:.* elf' > /dev/null; then + : + else + ld_shlibs=no + fi + ;; + esac + if test "$ld_shlibs" = no; then + hardcode_libdir_flag_spec= + fi +else + case "$host_os" in + aix3*) + # Note: this linker hardcodes the directories in LIBPATH if there + # are no directories specified by -L. + hardcode_minus_L=yes + if test "$GCC" = yes; then + # Neither direct hardcoding nor static linking is supported with a + # broken collect2. + hardcode_direct=unsupported + fi + ;; + aix[4-9]*) + if test "$host_cpu" = ia64; then + # On IA64, the linker does run time linking by default, so we don't + # have to do anything special. + aix_use_runtimelinking=no + else + aix_use_runtimelinking=no + # Test if we are trying to use run time linking or normal + # AIX style linking. If -brtl is somewhere in LDFLAGS, we + # need to do runtime linking. + case $host_os in aix4.[23]|aix4.[23].*|aix[5-9]*) + for ld_flag in $LDFLAGS; do + if (test $ld_flag = "-brtl" || test $ld_flag = "-Wl,-brtl"); then + aix_use_runtimelinking=yes + break + fi + done + ;; + esac + fi + hardcode_direct=yes + hardcode_libdir_separator=':' + if test "$GCC" = yes; then + case $host_os in aix4.[012]|aix4.[012].*) + collect2name=`${CC} -print-prog-name=collect2` + if test -f "$collect2name" && \ + strings "$collect2name" | grep resolve_lib_name >/dev/null + then + # We have reworked collect2 + : + else + # We have old collect2 + hardcode_direct=unsupported + hardcode_minus_L=yes + hardcode_libdir_flag_spec='-L$libdir' + hardcode_libdir_separator= + fi + ;; + esac + fi + # Begin _LT_AC_SYS_LIBPATH_AIX. + echo 'int main () { return 0; }' > conftest.c + ${CC} ${LDFLAGS} conftest.c -o conftest + aix_libpath=`dump -H conftest 2>/dev/null | sed -n -e '/Import File Strings/,/^$/ { /^0/ { s/^0 *\(.*\)$/\1/; p; } +}'` + if test -z "$aix_libpath"; then + aix_libpath=`dump -HX64 conftest 2>/dev/null | sed -n -e '/Import File Strings/,/^$/ { /^0/ { s/^0 *\(.*\)$/\1/; p; } +}'` + fi + if test -z "$aix_libpath"; then + aix_libpath="/usr/lib:/lib" + fi + rm -f conftest.c conftest + # End _LT_AC_SYS_LIBPATH_AIX. + if test "$aix_use_runtimelinking" = yes; then + hardcode_libdir_flag_spec='${wl}-blibpath:$libdir:'"$aix_libpath" + else + if test "$host_cpu" = ia64; then + hardcode_libdir_flag_spec='${wl}-R $libdir:/usr/lib:/lib' + else + hardcode_libdir_flag_spec='${wl}-blibpath:$libdir:'"$aix_libpath" + fi + fi + ;; + amigaos*) + case "$host_cpu" in + powerpc) + ;; + m68k) + hardcode_libdir_flag_spec='-L$libdir' + hardcode_minus_L=yes + ;; + esac + ;; + bsdi[45]*) + ;; + cygwin* | mingw* | pw32* | cegcc*) + # When not using gcc, we currently assume that we are using + # Microsoft Visual C++. + # hardcode_libdir_flag_spec is actually meaningless, as there is + # no search path for DLLs. + hardcode_libdir_flag_spec=' ' + libext=lib + ;; + darwin* | rhapsody*) + hardcode_direct=no + if { case $cc_basename in ifort*) true;; *) test "$GCC" = yes;; esac; }; then + : + else + ld_shlibs=no + fi + ;; + dgux*) + hardcode_libdir_flag_spec='-L$libdir' + ;; + freebsd2.[01]*) + hardcode_direct=yes + hardcode_minus_L=yes + ;; + freebsd* | dragonfly* | midnightbsd*) + hardcode_libdir_flag_spec='-R$libdir' + hardcode_direct=yes + ;; + hpux9*) + hardcode_libdir_flag_spec='${wl}+b ${wl}$libdir' + hardcode_libdir_separator=: + hardcode_direct=yes + # hardcode_minus_L: Not really in the search PATH, + # but as the default location of the library. + hardcode_minus_L=yes + ;; + hpux10*) + if test "$with_gnu_ld" = no; then + hardcode_libdir_flag_spec='${wl}+b ${wl}$libdir' + hardcode_libdir_separator=: + hardcode_direct=yes + # hardcode_minus_L: Not really in the search PATH, + # but as the default location of the library. + hardcode_minus_L=yes + fi + ;; + hpux11*) + if test "$with_gnu_ld" = no; then + hardcode_libdir_flag_spec='${wl}+b ${wl}$libdir' + hardcode_libdir_separator=: + case $host_cpu in + hppa*64*|ia64*) + hardcode_direct=no + ;; + *) + hardcode_direct=yes + # hardcode_minus_L: Not really in the search PATH, + # but as the default location of the library. + hardcode_minus_L=yes + ;; + esac + fi + ;; + irix5* | irix6* | nonstopux*) + hardcode_libdir_flag_spec='${wl}-rpath ${wl}$libdir' + hardcode_libdir_separator=: + ;; + netbsd*) + hardcode_libdir_flag_spec='-R$libdir' + hardcode_direct=yes + ;; + newsos6) + hardcode_direct=yes + hardcode_libdir_flag_spec='${wl}-rpath ${wl}$libdir' + hardcode_libdir_separator=: + ;; + *nto* | *qnx*) + ;; + openbsd*) + if test -f /usr/libexec/ld.so; then + hardcode_direct=yes + if test -z "`echo __ELF__ | $CC -E - | grep __ELF__`" || test "$host_os-$host_cpu" = "openbsd2.8-powerpc"; then + hardcode_libdir_flag_spec='${wl}-rpath,$libdir' + else + case "$host_os" in + openbsd[01].* | openbsd2.[0-7] | openbsd2.[0-7].*) + hardcode_libdir_flag_spec='-R$libdir' + ;; + *) + hardcode_libdir_flag_spec='${wl}-rpath,$libdir' + ;; + esac + fi + else + ld_shlibs=no + fi + ;; + os2*) + hardcode_libdir_flag_spec='-L$libdir' + hardcode_minus_L=yes + ;; + osf3*) + hardcode_libdir_flag_spec='${wl}-rpath ${wl}$libdir' + hardcode_libdir_separator=: + ;; + osf4* | osf5*) + if test "$GCC" = yes; then + hardcode_libdir_flag_spec='${wl}-rpath ${wl}$libdir' + else + # Both cc and cxx compiler support -rpath directly + hardcode_libdir_flag_spec='-rpath $libdir' + fi + hardcode_libdir_separator=: + ;; + solaris*) + hardcode_libdir_flag_spec='-R$libdir' + ;; + sunos4*) + hardcode_libdir_flag_spec='-L$libdir' + hardcode_direct=yes + hardcode_minus_L=yes + ;; + sysv4) + case $host_vendor in + sni) + hardcode_direct=yes # is this really true??? + ;; + siemens) + hardcode_direct=no + ;; + motorola) + hardcode_direct=no #Motorola manual says yes, but my tests say they lie + ;; + esac + ;; + sysv4.3*) + ;; + sysv4*MP*) + if test -d /usr/nec; then + ld_shlibs=yes + fi + ;; + sysv4*uw2* | sysv5OpenUNIX* | sysv5UnixWare7.[01].[10]* | unixware7* | sco3.2v5.0.[024]*) + ;; + sysv5* | sco3.2v5* | sco5v6*) + hardcode_libdir_flag_spec='`test -z "$SCOABSPATH" && echo ${wl}-R,$libdir`' + hardcode_libdir_separator=':' + ;; + uts4*) + hardcode_libdir_flag_spec='-L$libdir' + ;; + *) + ld_shlibs=no + ;; + esac +fi + +# Check dynamic linker characteristics +# Code taken from libtool.m4's _LT_SYS_DYNAMIC_LINKER. +# Unlike libtool.m4, here we don't care about _all_ names of the library, but +# only about the one the linker finds when passed -lNAME. This is the last +# element of library_names_spec in libtool.m4, or possibly two of them if the +# linker has special search rules. +library_names_spec= # the last element of library_names_spec in libtool.m4 +libname_spec='lib$name' +case "$host_os" in + aix3*) + library_names_spec='$libname.a' + ;; + aix[4-9]*) + library_names_spec='$libname$shrext' + ;; + amigaos*) + case "$host_cpu" in + powerpc*) + library_names_spec='$libname$shrext' ;; + m68k) + library_names_spec='$libname.a' ;; + esac + ;; + beos*) + library_names_spec='$libname$shrext' + ;; + bsdi[45]*) + library_names_spec='$libname$shrext' + ;; + cygwin* | mingw* | pw32* | cegcc*) + shrext=.dll + library_names_spec='$libname.dll.a $libname.lib' + ;; + darwin* | rhapsody*) + shrext=.dylib + library_names_spec='$libname$shrext' + ;; + dgux*) + library_names_spec='$libname$shrext' + ;; + freebsd[23].*) + library_names_spec='$libname$shrext$versuffix' + ;; + freebsd* | dragonfly* | midnightbsd*) + library_names_spec='$libname$shrext' + ;; + gnu*) + library_names_spec='$libname$shrext' + ;; + haiku*) + library_names_spec='$libname$shrext' + ;; + hpux9* | hpux10* | hpux11*) + case $host_cpu in + ia64*) + shrext=.so + ;; + hppa*64*) + shrext=.sl + ;; + *) + shrext=.sl + ;; + esac + library_names_spec='$libname$shrext' + ;; + interix[3-9]*) + library_names_spec='$libname$shrext' + ;; + irix5* | irix6* | nonstopux*) + library_names_spec='$libname$shrext' + case "$host_os" in + irix5* | nonstopux*) + libsuff= shlibsuff= + ;; + *) + case $LD in + *-32|*"-32 "|*-melf32bsmip|*"-melf32bsmip ") libsuff= shlibsuff= ;; + *-n32|*"-n32 "|*-melf32bmipn32|*"-melf32bmipn32 ") libsuff=32 shlibsuff=N32 ;; + *-64|*"-64 "|*-melf64bmip|*"-melf64bmip ") libsuff=64 shlibsuff=64 ;; + *) libsuff= shlibsuff= ;; + esac + ;; + esac + ;; + linux*oldld* | linux*aout* | linux*coff*) + ;; + linux* | k*bsd*-gnu | kopensolaris*-gnu) + library_names_spec='$libname$shrext' + ;; + knetbsd*-gnu) + library_names_spec='$libname$shrext' + ;; + netbsd*) + library_names_spec='$libname$shrext' + ;; + newsos6) + library_names_spec='$libname$shrext' + ;; + *nto* | *qnx*) + library_names_spec='$libname$shrext' + ;; + openbsd*) + library_names_spec='$libname$shrext$versuffix' + ;; + os2*) + libname_spec='$name' + shrext=.dll + library_names_spec='$libname.a' + ;; + osf3* | osf4* | osf5*) + library_names_spec='$libname$shrext' + ;; + rdos*) + ;; + solaris*) + library_names_spec='$libname$shrext' + ;; + sunos4*) + library_names_spec='$libname$shrext$versuffix' + ;; + sysv4 | sysv4.3*) + library_names_spec='$libname$shrext' + ;; + sysv4*MP*) + library_names_spec='$libname$shrext' + ;; + sysv5* | sco3.2v5* | sco5v6* | unixware* | OpenUNIX* | sysv4*uw2*) + library_names_spec='$libname$shrext' + ;; + tpf*) + library_names_spec='$libname$shrext' + ;; + uts4*) + library_names_spec='$libname$shrext' + ;; +esac + +sed_quote_subst='s/\(["`$\\]\)/\\\1/g' +escaped_wl=`echo "X$wl" | sed -e 's/^X//' -e "$sed_quote_subst"` +shlibext=`echo "$shrext" | sed -e 's,^\.,,'` +escaped_libname_spec=`echo "X$libname_spec" | sed -e 's/^X//' -e "$sed_quote_subst"` +escaped_library_names_spec=`echo "X$library_names_spec" | sed -e 's/^X//' -e "$sed_quote_subst"` +escaped_hardcode_libdir_flag_spec=`echo "X$hardcode_libdir_flag_spec" | sed -e 's/^X//' -e "$sed_quote_subst"` + +LC_ALL=C sed -e 's/^\([a-zA-Z0-9_]*\)=/acl_cv_\1=/' < or fax it to us at +1-617-542-2652. +You can also send it to us via the postal mail if you prefer: + +Attn: Copyright Administrator +Free Software Foundation +31 Milk Street, # 960789 +Boston, MA 02196 +USA + + +Please print your email and snail addresses on the printed disclaimer. +*Don't forget to include the date.* + +In the unlikely event that you are employed on a continuing basis to do +translation, we may need a disclaimer from your employer as well, to assure +your employer does not claim to own this work. Please contact the FSF to +ask for advice if you think this may apply to you. + +Note: if you want the wording modified to cover only a specific category +of programs, or a specific program, we can easily do that. + + + + DISCLAIMER OF COPYRIGHT IN TRANSLATIONS OF PARTS OF PROGRAMS + +I, _____________________________________, a citizen of _____________ +(country), do hereby acknowledge to the Free Software Foundation, a +not-for-profit corporation of Massachusetts, USA, that I disclaim all +copyright interest in my works, which consist of translation of +portions of free software programs from one human language to another +human language, that I have provided to the Foundation or that I will +provide in the future. The programs to which this applies include all +programs for which the Foundation is the copyright holder, and all +other freely redistributable software programs. + +The translations covered by this disclaimer include, without +limitation, translations of textual messages, glossaries, command or +option names, help files, user interface text, and the like, contained +within or made for use via these programs. + + Given as a sealed instrument this ___ day of ______ (month), ______ +(year), at _____________________ (city and country). + + + signed: ___________________________ + + email address: ___________________________ + + postal address: ___________________________ + + ___________________________ + + ___________________________ + + + +I currently expect to translate into the following language (though +this disclaimer applies to all such translations that I may +subsequently provide to the FSF, whatever the language): + + __________________________________________________ + + __________________________________________________ + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/gettext.h b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/gettext.h new file mode 100644 index 0000000000000000000000000000000000000000..e07880bb3d5e8a658b66acf511899bab970aa073 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/gettext.h @@ -0,0 +1,310 @@ +/* Convenience header for conditional use of GNU . + Copyright (C) 1995-2024 Free Software Foundation, Inc. + + This program 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.1 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 Lesser General Public License for more details. + + You should have received a copy of the GNU Lesser General Public License + along with this program. If not, see . */ + +#ifndef _LIBGETTEXT_H +#define _LIBGETTEXT_H 1 + + +/* NLS can be disabled through the configure --disable-nls option + or through "#define ENABLE NLS 0" before including this file. */ +#if defined ENABLE_NLS && ENABLE_NLS + +/* Get declarations of GNU message catalog functions. */ +# include + +/* You can set the DEFAULT_TEXT_DOMAIN macro to specify the domain used by + the gettext() and ngettext() macros. This is an alternative to calling + textdomain(), and is useful for libraries. */ +# ifdef DEFAULT_TEXT_DOMAIN +# undef gettext +# define gettext(Msgid) \ + dgettext (DEFAULT_TEXT_DOMAIN, Msgid) +# undef ngettext +# define ngettext(Msgid1, Msgid2, N) \ + dngettext (DEFAULT_TEXT_DOMAIN, Msgid1, Msgid2, N) +# endif + +#else + +/* Solaris /usr/include/locale.h includes /usr/include/libintl.h, which + chokes if dcgettext is defined as a macro. So include it now, to make + later inclusions of a NOP. We don't include + as well because people using "gettext.h" will not include , + and also including would fail on SunOS 4, whereas + is OK. */ +# if defined(__sun) +# include +# endif + +/* Many header files from the libstdc++ coming with g++ 3.3 or newer include + , which chokes if dcgettext is defined as a macro. So include + it now, to make later inclusions of a NOP. */ +# if defined(__cplusplus) && defined(__GNUG__) && (__GNUC__ >= 3) +# include +# if (__GLIBC__ >= 2 && !defined __UCLIBC__) || _GLIBCXX_HAVE_LIBINTL_H +# include +# endif +# endif + +/* Disabled NLS. + The casts to 'const char *' serve the purpose of producing warnings + for invalid uses of the value returned from these functions. + On pre-ANSI systems without 'const', the config.h file is supposed to + contain "#define const". */ +# undef gettext +# define gettext(Msgid) ((const char *) (Msgid)) +# undef dgettext +# define dgettext(Domainname, Msgid) ((void) (Domainname), gettext (Msgid)) +# undef dcgettext +# define dcgettext(Domainname, Msgid, Category) \ + ((void) (Category), dgettext (Domainname, Msgid)) +# undef ngettext +# define ngettext(Msgid1, Msgid2, N) \ + ((N) == 1 \ + ? ((void) (Msgid2), (const char *) (Msgid1)) \ + : ((void) (Msgid1), (const char *) (Msgid2))) +# undef dngettext +# define dngettext(Domainname, Msgid1, Msgid2, N) \ + ((void) (Domainname), ngettext (Msgid1, Msgid2, N)) +# undef dcngettext +# define dcngettext(Domainname, Msgid1, Msgid2, N, Category) \ + ((void) (Category), dngettext (Domainname, Msgid1, Msgid2, N)) +# undef textdomain +# define textdomain(Domainname) ((const char *) (Domainname)) +# undef bindtextdomain +# define bindtextdomain(Domainname, Dirname) \ + ((void) (Domainname), (const char *) (Dirname)) +# undef bind_textdomain_codeset +# define bind_textdomain_codeset(Domainname, Codeset) \ + ((void) (Domainname), (const char *) (Codeset)) + +#endif + + +/* Prefer gnulib's setlocale override over libintl's setlocale override. */ +#ifdef GNULIB_defined_setlocale +# undef setlocale +# define setlocale rpl_setlocale +#endif + + +/* A pseudo function call that serves as a marker for the automated + extraction of messages, but does not call gettext(). The run-time + translation is done at a different place in the code. + The argument, String, should be a literal string. Concatenated strings + and other string expressions won't work. + The macro's expansion is not parenthesized, so that it is suitable as + initializer for static 'char[]' or 'const char[]' variables. */ +#define gettext_noop(String) String + + +/* The separator between msgctxt and msgid in a .mo file. */ +#define GETTEXT_CONTEXT_GLUE "\004" + +/* Pseudo function calls, taking a MSGCTXT and a MSGID instead of just a + MSGID. MSGCTXT and MSGID must be string literals. MSGCTXT should be + short and rarely need to change. + The letter 'p' stands for 'particular' or 'special'. */ + +#include /* for LC_MESSAGES */ + +#ifdef DEFAULT_TEXT_DOMAIN +# define pgettext(Msgctxt, Msgid) \ + pgettext_aux (DEFAULT_TEXT_DOMAIN, Msgctxt GETTEXT_CONTEXT_GLUE Msgid, Msgid, LC_MESSAGES) +#else +# define pgettext(Msgctxt, Msgid) \ + pgettext_aux (NULL, Msgctxt GETTEXT_CONTEXT_GLUE Msgid, Msgid, LC_MESSAGES) +#endif +#define dpgettext(Domainname, Msgctxt, Msgid) \ + pgettext_aux (Domainname, Msgctxt GETTEXT_CONTEXT_GLUE Msgid, Msgid, LC_MESSAGES) +#define dcpgettext(Domainname, Msgctxt, Msgid, Category) \ + pgettext_aux (Domainname, Msgctxt GETTEXT_CONTEXT_GLUE Msgid, Msgid, Category) +#ifdef DEFAULT_TEXT_DOMAIN +# define npgettext(Msgctxt, Msgid, MsgidPlural, N) \ + npgettext_aux (DEFAULT_TEXT_DOMAIN, Msgctxt GETTEXT_CONTEXT_GLUE Msgid, Msgid, MsgidPlural, N, LC_MESSAGES) +#else +# define npgettext(Msgctxt, Msgid, MsgidPlural, N) \ + npgettext_aux (NULL, Msgctxt GETTEXT_CONTEXT_GLUE Msgid, Msgid, MsgidPlural, N, LC_MESSAGES) +#endif +#define dnpgettext(Domainname, Msgctxt, Msgid, MsgidPlural, N) \ + npgettext_aux (Domainname, Msgctxt GETTEXT_CONTEXT_GLUE Msgid, Msgid, MsgidPlural, N, LC_MESSAGES) +#define dcnpgettext(Domainname, Msgctxt, Msgid, MsgidPlural, N, Category) \ + npgettext_aux (Domainname, Msgctxt GETTEXT_CONTEXT_GLUE Msgid, Msgid, MsgidPlural, N, Category) + +#if defined __GNUC__ || defined __clang__ +__inline +#else +#ifdef __cplusplus +inline +#endif +#endif +static const char * +pgettext_aux (const char *domain, + const char *msg_ctxt_id, const char *msgid, + int category) +{ + const char *translation = dcgettext (domain, msg_ctxt_id, category); + if (translation == msg_ctxt_id) + return msgid; + else + return translation; +} + +#if defined __GNUC__ || defined __clang__ +__inline +#else +#ifdef __cplusplus +inline +#endif +#endif +static const char * +npgettext_aux (const char *domain, + const char *msg_ctxt_id, const char *msgid, + const char *msgid_plural, unsigned long int n, + int category) +{ + const char *translation = + dcngettext (domain, msg_ctxt_id, msgid_plural, n, category); + if (translation == msg_ctxt_id || translation == msgid_plural) + return (n == 1 ? msgid : msgid_plural); + else + return translation; +} + + +/* The same thing extended for non-constant arguments. Here MSGCTXT and MSGID + can be arbitrary expressions. But for string literals these macros are + less efficient than those above. */ + +#include /* for memcpy */ + +/* GNULIB_NO_VLA can be defined to disable use of VLAs even if supported. + This relates to the -Wvla and -Wvla-larger-than warnings, enabled in + the default GCC many warnings set. This allows programs to disable use + of VLAs, which may be unintended, or may be awkward to support portably, + or may have security implications due to non-deterministic stack usage. */ + +#if (!defined GNULIB_NO_VLA \ + && (((__GNUC__ >= 3 || defined __clang__) \ + && !defined __STRICT_ANSI__ && !defined __cplusplus) \ + /* || (__STDC_VERSION__ == 199901L && !defined __HP_cc) + || (__STDC_VERSION__ >= 201112L && !defined __STDC_NO_VLA__) */ )) +# define _LIBGETTEXT_HAVE_VARIABLE_SIZE_ARRAYS 1 +#else +# define _LIBGETTEXT_HAVE_VARIABLE_SIZE_ARRAYS 0 +#endif + +#if !_LIBGETTEXT_HAVE_VARIABLE_SIZE_ARRAYS +# include /* for malloc, free */ +#endif + +#define pgettext_expr(Msgctxt, Msgid) \ + dcpgettext_expr (NULL, Msgctxt, Msgid, LC_MESSAGES) +#define dpgettext_expr(Domainname, Msgctxt, Msgid) \ + dcpgettext_expr (Domainname, Msgctxt, Msgid, LC_MESSAGES) + +#if defined __GNUC__ || defined __clang__ +__inline +#else +#ifdef __cplusplus +inline +#endif +#endif +static const char * +dcpgettext_expr (const char *domain, + const char *msgctxt, const char *msgid, + int category) +{ + size_t msgctxt_len = strlen (msgctxt) + 1; + size_t msgid_len = strlen (msgid) + 1; + const char *translation; +#if _LIBGETTEXT_HAVE_VARIABLE_SIZE_ARRAYS + char msg_ctxt_id[msgctxt_len + msgid_len]; +#else + char buf[1024]; + char *msg_ctxt_id = + (msgctxt_len + msgid_len <= sizeof (buf) + ? buf + : (char *) malloc (msgctxt_len + msgid_len)); + if (msg_ctxt_id != NULL) +#endif + { + int found_translation; + memcpy (msg_ctxt_id, msgctxt, msgctxt_len - 1); + msg_ctxt_id[msgctxt_len - 1] = '\004'; + memcpy (msg_ctxt_id + msgctxt_len, msgid, msgid_len); + translation = dcgettext (domain, msg_ctxt_id, category); + found_translation = (translation != msg_ctxt_id); +#if !_LIBGETTEXT_HAVE_VARIABLE_SIZE_ARRAYS + if (msg_ctxt_id != buf) + free (msg_ctxt_id); +#endif + if (found_translation) + return translation; + } + return msgid; +} + +#define npgettext_expr(Msgctxt, Msgid, MsgidPlural, N) \ + dcnpgettext_expr (NULL, Msgctxt, Msgid, MsgidPlural, N, LC_MESSAGES) +#define dnpgettext_expr(Domainname, Msgctxt, Msgid, MsgidPlural, N) \ + dcnpgettext_expr (Domainname, Msgctxt, Msgid, MsgidPlural, N, LC_MESSAGES) + +#if defined __GNUC__ || defined __clang__ +__inline +#else +#ifdef __cplusplus +inline +#endif +#endif +static const char * +dcnpgettext_expr (const char *domain, + const char *msgctxt, const char *msgid, + const char *msgid_plural, unsigned long int n, + int category) +{ + size_t msgctxt_len = strlen (msgctxt) + 1; + size_t msgid_len = strlen (msgid) + 1; + const char *translation; +#if _LIBGETTEXT_HAVE_VARIABLE_SIZE_ARRAYS + char msg_ctxt_id[msgctxt_len + msgid_len]; +#else + char buf[1024]; + char *msg_ctxt_id = + (msgctxt_len + msgid_len <= sizeof (buf) + ? buf + : (char *) malloc (msgctxt_len + msgid_len)); + if (msg_ctxt_id != NULL) +#endif + { + int found_translation; + memcpy (msg_ctxt_id, msgctxt, msgctxt_len - 1); + msg_ctxt_id[msgctxt_len - 1] = '\004'; + memcpy (msg_ctxt_id + msgctxt_len, msgid, msgid_len); + translation = dcngettext (domain, msg_ctxt_id, msgid_plural, n, category); + found_translation = !(translation == msg_ctxt_id || translation == msgid_plural); +#if !_LIBGETTEXT_HAVE_VARIABLE_SIZE_ARRAYS + if (msg_ctxt_id != buf) + free (msg_ctxt_id); +#endif + if (found_translation) + return translation; + } + return (n == 1 ? msgid : msgid_plural); +} + + +#endif /* _LIBGETTEXT_H */ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/javaversion.class b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/javaversion.class new file mode 100644 index 0000000000000000000000000000000000000000..d62585b0ecd259dc3d661247c323788c927ff140 Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/javaversion.class differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/m4/build-to-host.m4 b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/m4/build-to-host.m4 new file mode 100644 index 0000000000000000000000000000000000000000..01bff8f34f24649e479f1081ccb58f2c87d3491e --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/m4/build-to-host.m4 @@ -0,0 +1,274 @@ +# build-to-host.m4 +# serial 5 +dnl Copyright (C) 2023-2025 Free Software Foundation, Inc. +dnl This file is free software; the Free Software Foundation +dnl gives unlimited permission to copy and/or distribute it, +dnl with or without modifications, as long as this notice is preserved. +dnl This file is offered as-is, without any warranty. + +dnl Written by Bruno Haible. + +dnl When the build environment ($build_os) is different from the target runtime +dnl environment ($host_os), file names may need to be converted from the build +dnl environment syntax to the target runtime environment syntax. This is +dnl because the Makefiles are executed (mostly) by build environment tools and +dnl therefore expect file names in build environment syntax, whereas the runtime +dnl expects file names in target runtime environment syntax. +dnl +dnl For example, if $build_os = cygwin and $host_os = mingw32, filenames need +dnl be converted from Cygwin syntax to native Windows syntax: +dnl /cygdrive/c/foo/bar -> C:\foo\bar +dnl /usr/local/share -> C:\cygwin64\usr\local\share +dnl +dnl gl_BUILD_TO_HOST([somedir]) +dnl This macro takes as input an AC_SUBSTed variable 'somedir', which must +dnl already have its final value assigned, and produces two additional +dnl AC_SUBSTed variables 'somedir_c' and 'somedir_c_make', that designate the +dnl same file name value, just in different syntax: +dnl - somedir_c is the file name in target runtime environment syntax, +dnl as a C string (starting and ending with a double-quote, +dnl and with escaped backslashes and double-quotes in +dnl between). +dnl - somedir_c_make is the same thing, escaped for use in a Makefile. + +AC_DEFUN([gl_BUILD_TO_HOST], +[ + AC_REQUIRE([AC_CANONICAL_BUILD]) + AC_REQUIRE([AC_CANONICAL_HOST]) + AC_REQUIRE([gl_BUILD_TO_HOST_INIT]) + + dnl Define somedir_c. + gl_final_[$1]="$[$1]" + dnl Translate it from build syntax to host syntax. + case "$build_os" in + cygwin*) + case "$host_os" in + mingw* | windows*) + gl_final_[$1]=`cygpath -w "$gl_final_[$1]"` ;; + esac + ;; + esac + dnl Convert it to C string syntax. + [$1]_c=`printf '%s\n' "$gl_final_[$1]" | sed -e "$gl_sed_double_backslashes" -e "$gl_sed_escape_doublequotes" | tr -d "$gl_tr_cr"` + [$1]_c='"'"$[$1]_c"'"' + AC_SUBST([$1_c]) + + dnl Define somedir_c_make. + [$1]_c_make=`printf '%s\n' "$[$1]_c" | sed -e "$gl_sed_escape_for_make_1" -e "$gl_sed_escape_for_make_2" | tr -d "$gl_tr_cr"` + dnl Use the substituted somedir variable, when possible, so that the user + dnl may adjust somedir a posteriori when there are no special characters. + if test "$[$1]_c_make" = '\"'"${gl_final_[$1]}"'\"'; then + [$1]_c_make='\"$([$1])\"' + fi + AC_SUBST([$1_c_make]) +]) + +dnl Some initializations for gl_BUILD_TO_HOST. +AC_DEFUN([gl_BUILD_TO_HOST_INIT], +[ + gl_sed_double_backslashes='s/\\/\\\\/g' + gl_sed_escape_doublequotes='s/"/\\"/g' +changequote(,)dnl + gl_sed_escape_for_make_1="s,\\([ \"&'();<>\\\\\`|]\\),\\\\\\1,g" +changequote([,])dnl + gl_sed_escape_for_make_2='s,\$,\\$$,g' + dnl Find out how to remove carriage returns from output. Solaris /usr/ucb/tr + dnl does not understand '\r'. + case `echo r | tr -d '\r'` in + '') gl_tr_cr='\015' ;; + *) gl_tr_cr='\r' ;; + esac +]) + + +dnl The following macros are convenience invocations of gl_BUILD_TO_HOST +dnl for some of the variables that are defined by Autoconf. +dnl To do so for _all_ the possible variables, use the module 'configmake'. + +dnl Defines bindir_c and bindir_c_make. +AC_DEFUN_ONCE([gl_BUILD_TO_HOST_BINDIR], +[ + dnl Find the final value of bindir. + gl_saved_prefix="${prefix}" + gl_saved_exec_prefix="${exec_prefix}" + gl_saved_bindir="${bindir}" + dnl Unfortunately, prefix and exec_prefix get only finally determined + dnl at the end of configure. + if test "X$prefix" = "XNONE"; then + prefix="$ac_default_prefix" + fi + if test "X$exec_prefix" = "XNONE"; then + exec_prefix='${prefix}' + fi + eval exec_prefix="$exec_prefix" + eval bindir="$bindir" + gl_BUILD_TO_HOST([bindir]) + bindir="${gl_saved_bindir}" + exec_prefix="${gl_saved_exec_prefix}" + prefix="${gl_saved_prefix}" +]) + +dnl Defines datadir_c and datadir_c_make, +dnl where datadir = $(datarootdir) +AC_DEFUN_ONCE([gl_BUILD_TO_HOST_DATADIR], +[ + dnl Find the final value of datadir. + gl_saved_prefix="${prefix}" + gl_saved_datarootdir="${datarootdir}" + gl_saved_datadir="${datadir}" + dnl Unfortunately, prefix gets only finally determined at the end of + dnl configure. + if test "X$prefix" = "XNONE"; then + prefix="$ac_default_prefix" + fi + eval datarootdir="$datarootdir" + eval datadir="$datadir" + gl_BUILD_TO_HOST([datadir]) + datadir="${gl_saved_datadir}" + datarootdir="${gl_saved_datarootdir}" + prefix="${gl_saved_prefix}" +]) + +dnl Defines libdir_c and libdir_c_make. +AC_DEFUN_ONCE([gl_BUILD_TO_HOST_LIBDIR], +[ + dnl Find the final value of libdir. + gl_saved_prefix="${prefix}" + gl_saved_exec_prefix="${exec_prefix}" + gl_saved_libdir="${libdir}" + dnl Unfortunately, prefix and exec_prefix get only finally determined + dnl at the end of configure. + if test "X$prefix" = "XNONE"; then + prefix="$ac_default_prefix" + fi + if test "X$exec_prefix" = "XNONE"; then + exec_prefix='${prefix}' + fi + eval exec_prefix="$exec_prefix" + eval libdir="$libdir" + gl_BUILD_TO_HOST([libdir]) + libdir="${gl_saved_libdir}" + exec_prefix="${gl_saved_exec_prefix}" + prefix="${gl_saved_prefix}" +]) + +dnl Defines libexecdir_c and libexecdir_c_make. +AC_DEFUN_ONCE([gl_BUILD_TO_HOST_LIBEXECDIR], +[ + dnl Find the final value of libexecdir. + gl_saved_prefix="${prefix}" + gl_saved_exec_prefix="${exec_prefix}" + gl_saved_libexecdir="${libexecdir}" + dnl Unfortunately, prefix and exec_prefix get only finally determined + dnl at the end of configure. + if test "X$prefix" = "XNONE"; then + prefix="$ac_default_prefix" + fi + if test "X$exec_prefix" = "XNONE"; then + exec_prefix='${prefix}' + fi + eval exec_prefix="$exec_prefix" + eval libexecdir="$libexecdir" + gl_BUILD_TO_HOST([libexecdir]) + libexecdir="${gl_saved_libexecdir}" + exec_prefix="${gl_saved_exec_prefix}" + prefix="${gl_saved_prefix}" +]) + +dnl Defines localedir_c and localedir_c_make. +AC_DEFUN_ONCE([gl_BUILD_TO_HOST_LOCALEDIR], +[ + dnl Find the final value of localedir. + gl_saved_prefix="${prefix}" + gl_saved_datarootdir="${datarootdir}" + gl_saved_localedir="${localedir}" + dnl Unfortunately, prefix gets only finally determined at the end of + dnl configure. + if test "X$prefix" = "XNONE"; then + prefix="$ac_default_prefix" + fi + eval datarootdir="$datarootdir" + eval localedir="$localedir" + gl_BUILD_TO_HOST([localedir]) + localedir="${gl_saved_localedir}" + datarootdir="${gl_saved_datarootdir}" + prefix="${gl_saved_prefix}" +]) + +dnl Defines pkgdatadir_c and pkgdatadir_c_make, +dnl where pkgdatadir = $(datadir)/$(PACKAGE) +AC_DEFUN_ONCE([gl_BUILD_TO_HOST_PKGDATADIR], +[ + dnl Find the final value of pkgdatadir. + gl_saved_prefix="${prefix}" + gl_saved_datarootdir="${datarootdir}" + gl_saved_datadir="${datadir}" + gl_saved_pkgdatadir="${pkgdatadir}" + dnl Unfortunately, prefix gets only finally determined at the end of + dnl configure. + if test "X$prefix" = "XNONE"; then + prefix="$ac_default_prefix" + fi + eval datarootdir="$datarootdir" + eval datadir="$datadir" + eval pkgdatadir="$pkgdatadir" + gl_BUILD_TO_HOST([pkgdatadir]) + pkgdatadir="${gl_saved_pkgdatadir}" + datadir="${gl_saved_datadir}" + datarootdir="${gl_saved_datarootdir}" + prefix="${gl_saved_prefix}" +]) + +dnl Defines pkglibdir_c and pkglibdir_c_make, +dnl where pkglibdir = $(libdir)/$(PACKAGE) +AC_DEFUN_ONCE([gl_BUILD_TO_HOST_PKGLIBDIR], +[ + dnl Find the final value of pkglibdir. + gl_saved_prefix="${prefix}" + gl_saved_exec_prefix="${exec_prefix}" + gl_saved_libdir="${libdir}" + gl_saved_pkglibdir="${pkglibdir}" + dnl Unfortunately, prefix and exec_prefix get only finally determined + dnl at the end of configure. + if test "X$prefix" = "XNONE"; then + prefix="$ac_default_prefix" + fi + if test "X$exec_prefix" = "XNONE"; then + exec_prefix='${prefix}' + fi + eval exec_prefix="$exec_prefix" + eval libdir="$libdir" + eval pkglibdir="$pkglibdir" + gl_BUILD_TO_HOST([pkglibdir]) + pkglibdir="${gl_saved_pkglibdir}" + libdir="${gl_saved_libdir}" + exec_prefix="${gl_saved_exec_prefix}" + prefix="${gl_saved_prefix}" +]) + +dnl Defines pkglibexecdir_c and pkglibexecdir_c_make, +dnl where pkglibexecdir = $(libexecdir)/$(PACKAGE) +AC_DEFUN_ONCE([gl_BUILD_TO_HOST_PKGLIBEXECDIR], +[ + dnl Find the final value of pkglibexecdir. + gl_saved_prefix="${prefix}" + gl_saved_exec_prefix="${exec_prefix}" + gl_saved_libexecdir="${libexecdir}" + gl_saved_pkglibexecdir="${pkglibexecdir}" + dnl Unfortunately, prefix and exec_prefix get only finally determined + dnl at the end of configure. + if test "X$prefix" = "XNONE"; then + prefix="$ac_default_prefix" + fi + if test "X$exec_prefix" = "XNONE"; then + exec_prefix='${prefix}' + fi + eval exec_prefix="$exec_prefix" + eval libexecdir="$libexecdir" + eval pkglibexecdir="$pkglibexecdir" + gl_BUILD_TO_HOST([pkglibexecdir]) + pkglibexecdir="${gl_saved_pkglibexecdir}" + libexecdir="${gl_saved_libexecdir}" + exec_prefix="${gl_saved_exec_prefix}" + prefix="${gl_saved_prefix}" +]) diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/m4/gettext.m4 b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/m4/gettext.m4 new file mode 100644 index 0000000000000000000000000000000000000000..7de17f99c02c28a2950cc3dd1e565822f3b637a1 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/m4/gettext.m4 @@ -0,0 +1,393 @@ +# gettext.m4 +# serial 81 (gettext-0.24) +dnl Copyright (C) 1995-2025 Free Software Foundation, Inc. +dnl This file is free software; the Free Software Foundation +dnl gives unlimited permission to copy and/or distribute it, +dnl with or without modifications, as long as this notice is preserved. +dnl This file is offered as-is, without any warranty. +dnl +dnl This file can be used in projects which are not available under +dnl the GNU General Public License or the GNU Lesser General Public +dnl License but which still want to provide support for the GNU gettext +dnl functionality. +dnl Please note that the actual code of the GNU gettext library is covered +dnl by the GNU Lesser General Public License, and the rest of the GNU +dnl gettext package is covered by the GNU General Public License. +dnl They are *not* in the public domain. + +dnl Authors: +dnl Ulrich Drepper , 1995-2000. +dnl Bruno Haible , 2000-2024. + +dnl Macro to add for using GNU gettext. + +dnl Usage: AM_GNU_GETTEXT([INTLSYMBOL], [NEEDSYMBOL], [INTLDIR]). +dnl INTLSYMBOL must be one of 'external', 'use-libtool', 'here'. +dnl INTLSYMBOL should be 'external' for packages other than GNU gettext. +dnl It should be 'use-libtool' for the packages 'gettext-runtime' and +dnl 'gettext-tools'. +dnl It should be 'here' for the package 'gettext-runtime/intl'. +dnl If INTLSYMBOL is 'here', then a libtool library +dnl $(top_builddir)/libintl.la will be created (shared and/or static, +dnl depending on --{enable,disable}-{shared,static} and on the presence of +dnl AM-DISABLE-SHARED). +dnl If NEEDSYMBOL is specified and is 'need-ngettext', then GNU gettext +dnl implementations (in libc or libintl) without the ngettext() function +dnl will be ignored. If NEEDSYMBOL is specified and is +dnl 'need-formatstring-macros', then GNU gettext implementations that don't +dnl support the ISO C 99 formatstring macros will be ignored. +dnl INTLDIR is used to find the intl libraries. If empty, +dnl the value '$(top_builddir)/intl/' is used. +dnl +dnl The result of the configuration is one of three cases: +dnl 1) GNU gettext, as included in the intl subdirectory, will be compiled +dnl and used. +dnl Catalog format: GNU --> install in $(datadir) +dnl Catalog extension: .mo after installation, .gmo in source tree +dnl 2) GNU gettext has been found in the system's C library. +dnl Catalog format: GNU --> install in $(datadir) +dnl Catalog extension: .mo after installation, .gmo in source tree +dnl 3) No internationalization, always use English msgid. +dnl Catalog format: none +dnl Catalog extension: none +dnl If INTLSYMBOL is 'external', only cases 2 and 3 can occur. +dnl The use of .gmo is historical (it was needed to avoid overwriting the +dnl GNU format catalogs when building on a platform with an X/Open gettext), +dnl but we keep it in order not to force irrelevant filename changes on the +dnl maintainers. +dnl +AC_DEFUN([AM_GNU_GETTEXT], +[ + dnl Argument checking. + m4_if([$1], [], , [m4_if([$1], [external], , [m4_if([$1], [use-libtool], , [m4_if([$1], [here], , + [errprint([ERROR: invalid first argument to AM_GNU_GETTEXT +])])])])]) + m4_if(m4_if([$1], [], [old])[]m4_if([$1], [no-libtool], [old]), [old], + [errprint([ERROR: Use of AM_GNU_GETTEXT without [external] argument is no longer supported. +])]) + m4_if([$2], [], , [m4_if([$2], [need-ngettext], , [m4_if([$2], [need-formatstring-macros], , + [errprint([ERROR: invalid second argument to AM_GNU_GETTEXT +])])])]) + define([gt_building_libintl_in_same_build_tree], + m4_if([$1], [use-libtool], [yes], [m4_if([$1], [here], [yes], [no])])) + gt_NEEDS_INIT + AM_GNU_GETTEXT_NEED([$2]) + + AC_REQUIRE([AM_PO_SUBDIRS])dnl + + dnl Prerequisites of AC_LIB_LINKFLAGS_BODY. + AC_REQUIRE([AC_LIB_PREPARE_PREFIX]) + AC_REQUIRE([AC_LIB_RPATH]) + + dnl Sometimes libintl requires libiconv, so first search for libiconv. + dnl Ideally we would do this search only after the + dnl if test "$USE_NLS" = "yes"; then + dnl if { eval "gt_val=\$$gt_func_gnugettext_libc"; test "$gt_val" != "yes"; }; then + dnl tests. But if configure.ac invokes AM_ICONV after AM_GNU_GETTEXT + dnl the configure script would need to contain the same shell code + dnl again, outside any 'if'. There are two solutions: + dnl - Invoke AM_ICONV_LINKFLAGS_BODY here, outside any 'if'. + dnl - Control the expansions in more detail using AC_PROVIDE_IFELSE. + dnl Since AC_PROVIDE_IFELSE is not documented, we avoid it. + m4_if(gt_building_libintl_in_same_build_tree, yes, , [ + AC_REQUIRE([AM_ICONV_LINKFLAGS_BODY]) + ]) + + dnl Sometimes, on Mac OS X, libintl requires linking with CoreFoundation. + gt_INTL_MACOSX + + dnl Set USE_NLS. + AC_REQUIRE([AM_NLS]) + + m4_if(gt_building_libintl_in_same_build_tree, yes, [ + USE_INCLUDED_LIBINTL=no + ]) + LIBINTL= + LTLIBINTL= + POSUB= + + dnl Add a version number to the cache macros. + case " $gt_needs " in + *" need-formatstring-macros "*) gt_api_version=3 ;; + *" need-ngettext "*) gt_api_version=2 ;; + *) gt_api_version=1 ;; + esac + gt_func_gnugettext_libc="gt_cv_func_gnugettext${gt_api_version}_libc" + gt_func_gnugettext_libintl="gt_cv_func_gnugettext${gt_api_version}_libintl" + + dnl If we use NLS figure out what method + if test "$USE_NLS" = "yes"; then + gt_use_preinstalled_gnugettext=no + m4_if(gt_building_libintl_in_same_build_tree, yes, [ + AC_MSG_CHECKING([whether included gettext is requested]) + AC_ARG_WITH([included-gettext], + [ --with-included-gettext use the GNU gettext library included here], + nls_cv_force_use_gnu_gettext=$withval, + nls_cv_force_use_gnu_gettext=no) + AC_MSG_RESULT([$nls_cv_force_use_gnu_gettext]) + + nls_cv_use_gnu_gettext="$nls_cv_force_use_gnu_gettext" + if test "$nls_cv_force_use_gnu_gettext" != "yes"; then + ]) + dnl User does not insist on using GNU NLS library. Figure out what + dnl to use. If GNU gettext is available we use this. Else we have + dnl to fall back to GNU NLS library. + + if test $gt_api_version -ge 3; then + gt_revision_test_code=' +#ifndef __GNU_GETTEXT_SUPPORTED_REVISION +#define __GNU_GETTEXT_SUPPORTED_REVISION(major) ((major) == 0 ? 0 : -1) +#endif +changequote(,)dnl +typedef int array [2 * (__GNU_GETTEXT_SUPPORTED_REVISION(0) >= 1) - 1]; +changequote([,])dnl +' + else + gt_revision_test_code= + fi + if test $gt_api_version -ge 2; then + gt_expression_test_code=' + * ngettext ("", "", 0)' + else + gt_expression_test_code= + fi + + AC_CACHE_CHECK([for GNU gettext in libc], [$gt_func_gnugettext_libc], + [AC_LINK_IFELSE( + [AC_LANG_PROGRAM( + [[ +#include +#ifndef __GNU_GETTEXT_SUPPORTED_REVISION +extern int _nl_msg_cat_cntr; +extern int *_nl_domain_bindings; +#define __GNU_GETTEXT_SYMBOL_EXPRESSION (_nl_msg_cat_cntr + *_nl_domain_bindings) +#else +#define __GNU_GETTEXT_SYMBOL_EXPRESSION 0 +#endif +$gt_revision_test_code + ]], + [[ +bindtextdomain ("", ""); +return * gettext ("")$gt_expression_test_code + __GNU_GETTEXT_SYMBOL_EXPRESSION + ]])], + [eval "$gt_func_gnugettext_libc=yes"], + [eval "$gt_func_gnugettext_libc=no"])]) + + if { eval "gt_val=\$$gt_func_gnugettext_libc"; test "$gt_val" != "yes"; }; then + dnl Sometimes libintl requires libiconv, so first search for libiconv. + m4_if(gt_building_libintl_in_same_build_tree, yes, , [ + AM_ICONV_LINK + ]) + dnl Search for libintl and define LIBINTL, LTLIBINTL and INCINTL + dnl accordingly. Don't use AC_LIB_LINKFLAGS_BODY([intl],[iconv]) + dnl because that would add "-liconv" to LIBINTL and LTLIBINTL + dnl even if libiconv doesn't exist. + AC_LIB_LINKFLAGS_BODY([intl]) + AC_CACHE_CHECK([for GNU gettext in libintl], + [$gt_func_gnugettext_libintl], + [gt_saved_CPPFLAGS="$CPPFLAGS" + CPPFLAGS="$CPPFLAGS $INCINTL" + gt_saved_LIBS="$LIBS" + LIBS="$LIBS $LIBINTL" + dnl Now see whether libintl exists and does not depend on libiconv. + AC_LINK_IFELSE( + [AC_LANG_PROGRAM( + [[ +#include +#ifndef __GNU_GETTEXT_SUPPORTED_REVISION +extern int _nl_msg_cat_cntr; +extern +#ifdef __cplusplus +"C" +#endif +const char *_nl_expand_alias (const char *); +#define __GNU_GETTEXT_SYMBOL_EXPRESSION (_nl_msg_cat_cntr + *_nl_expand_alias ("")) +#else +#define __GNU_GETTEXT_SYMBOL_EXPRESSION 0 +#endif +$gt_revision_test_code + ]], + [[ +bindtextdomain ("", ""); +return * gettext ("")$gt_expression_test_code + __GNU_GETTEXT_SYMBOL_EXPRESSION + ]])], + [eval "$gt_func_gnugettext_libintl=yes"], + [eval "$gt_func_gnugettext_libintl=no"]) + dnl Now see whether libintl exists and depends on libiconv or other + dnl OS dependent libraries, specifically on macOS and AIX. + gt_LIBINTL_EXTRA="$INTL_MACOSX_LIBS" + AC_REQUIRE([AC_CANONICAL_HOST]) + case "$host_os" in + aix*) gt_LIBINTL_EXTRA="-lpthread" ;; + esac + if { eval "gt_val=\$$gt_func_gnugettext_libintl"; test "$gt_val" != yes; } \ + && { test -n "$LIBICONV" || test -n "$gt_LIBINTL_EXTRA"; }; then + LIBS="$LIBS $LIBICONV $gt_LIBINTL_EXTRA" + AC_LINK_IFELSE( + [AC_LANG_PROGRAM( + [[ +#include +#ifndef __GNU_GETTEXT_SUPPORTED_REVISION +extern int _nl_msg_cat_cntr; +extern +#ifdef __cplusplus +"C" +#endif +const char *_nl_expand_alias (const char *); +#define __GNU_GETTEXT_SYMBOL_EXPRESSION (_nl_msg_cat_cntr + *_nl_expand_alias ("")) +#else +#define __GNU_GETTEXT_SYMBOL_EXPRESSION 0 +#endif +$gt_revision_test_code + ]], + [[ +bindtextdomain ("", ""); +return * gettext ("")$gt_expression_test_code + __GNU_GETTEXT_SYMBOL_EXPRESSION + ]])], + [LIBINTL="$LIBINTL $LIBICONV $gt_LIBINTL_EXTRA" + LTLIBINTL="$LTLIBINTL $LTLIBICONV $gt_LIBINTL_EXTRA" + eval "$gt_func_gnugettext_libintl=yes" + ]) + fi + CPPFLAGS="$gt_saved_CPPFLAGS" + LIBS="$gt_saved_LIBS"]) + fi + + dnl If an already present or preinstalled GNU gettext() is found, + dnl use it. But if this macro is used in GNU gettext, and GNU + dnl gettext is already preinstalled in libintl, we update this + dnl libintl. (Cf. the install rule in intl/Makefile.in.) + if { eval "gt_val=\$$gt_func_gnugettext_libc"; test "$gt_val" = "yes"; } \ + || { { eval "gt_val=\$$gt_func_gnugettext_libintl"; test "$gt_val" = "yes"; } \ + && test "$PACKAGE" != gettext-runtime \ + && test "$PACKAGE" != gettext-tools \ + && test "$PACKAGE" != libintl; }; then + gt_use_preinstalled_gnugettext=yes + else + dnl Reset the values set by searching for libintl. + LIBINTL= + LTLIBINTL= + INCINTL= + fi + + m4_if(gt_building_libintl_in_same_build_tree, yes, [ + if test "$gt_use_preinstalled_gnugettext" != "yes"; then + dnl GNU gettext is not found in the C library. + dnl Fall back on included GNU gettext library. + nls_cv_use_gnu_gettext=yes + fi + fi + + if test "$nls_cv_use_gnu_gettext" = "yes"; then + dnl Mark actions used to generate GNU NLS library. + USE_INCLUDED_LIBINTL=yes + LIBINTL="m4_if([$3],[],\${top_builddir}/intl,[$3])/libintl.la $LIBICONV $LIBTHREAD" + LTLIBINTL="m4_if([$3],[],\${top_builddir}/intl,[$3])/libintl.la $LTLIBICONV $LTLIBTHREAD" + LIBS=`echo " $LIBS " | sed -e 's/ -lintl / /' -e 's/^ //' -e 's/ $//'` + fi + + CATOBJEXT= + if test "$gt_use_preinstalled_gnugettext" = "yes" \ + || test "$nls_cv_use_gnu_gettext" = "yes"; then + dnl Mark actions to use GNU gettext tools. + CATOBJEXT=.gmo + fi + ]) + + if test -n "$INTL_MACOSX_LIBS"; then + if test "$gt_use_preinstalled_gnugettext" = "yes" \ + || test "$nls_cv_use_gnu_gettext" = "yes"; then + dnl Some extra flags are needed during linking. + LIBINTL="$LIBINTL $INTL_MACOSX_LIBS" + LTLIBINTL="$LTLIBINTL $INTL_MACOSX_LIBS" + fi + fi + + if test "$gt_use_preinstalled_gnugettext" = "yes" \ + || test "$nls_cv_use_gnu_gettext" = "yes"; then + AC_DEFINE([ENABLE_NLS], [1], + [Define to 1 if translation of program messages to the user's native language + is requested.]) + else + USE_NLS=no + fi + fi + + AC_MSG_CHECKING([whether to use NLS]) + AC_MSG_RESULT([$USE_NLS]) + if test "$USE_NLS" = "yes"; then + AC_MSG_CHECKING([where the gettext function comes from]) + if test "$gt_use_preinstalled_gnugettext" = "yes"; then + if { eval "gt_val=\$$gt_func_gnugettext_libintl"; test "$gt_val" = "yes"; }; then + gt_source="external libintl" + else + gt_source="libc" + fi + else + gt_source="included intl directory" + fi + AC_MSG_RESULT([$gt_source]) + fi + + if test "$USE_NLS" = "yes"; then + + if test "$gt_use_preinstalled_gnugettext" = "yes"; then + if { eval "gt_val=\$$gt_func_gnugettext_libintl"; test "$gt_val" = "yes"; }; then + AC_MSG_CHECKING([how to link with libintl]) + AC_MSG_RESULT([$LIBINTL]) + AC_LIB_APPENDTOVAR([CPPFLAGS], [$INCINTL]) + fi + + dnl For backward compatibility. Some packages may be using this. + AC_DEFINE([HAVE_GETTEXT], [1], + [Define if the GNU gettext() function is already present or preinstalled.]) + AC_DEFINE([HAVE_DCGETTEXT], [1], + [Define if the GNU dcgettext() function is already present or preinstalled.]) + fi + + dnl We need to process the po/ directory. + POSUB=po + fi + + m4_if(gt_building_libintl_in_same_build_tree, yes, [ + dnl Make all variables we use known to autoconf. + AC_SUBST([USE_INCLUDED_LIBINTL]) + AC_SUBST([CATOBJEXT]) + ]) + + m4_if(gt_building_libintl_in_same_build_tree, yes, [], [ + dnl For backward compatibility. Some Makefiles may be using this. + INTLLIBS="$LIBINTL" + AC_SUBST([INTLLIBS]) + ]) + + dnl Make all documented variables known to autoconf. + AC_SUBST([LIBINTL]) + AC_SUBST([LTLIBINTL]) + AC_SUBST([POSUB]) + + dnl Define localedir_c and localedir_c_make. + gl_BUILD_TO_HOST_LOCALEDIR +]) + + +dnl gt_NEEDS_INIT ensures that the gt_needs variable is initialized. +m4_define([gt_NEEDS_INIT], +[ + m4_divert_text([DEFAULTS], [gt_needs=]) + m4_define([gt_NEEDS_INIT], []) +]) + + +dnl Usage: AM_GNU_GETTEXT_NEED([NEEDSYMBOL]) +AC_DEFUN([AM_GNU_GETTEXT_NEED], +[ + m4_divert_text([INIT_PREPARE], [gt_needs="$gt_needs $1"]) +]) + + +dnl Usage: AM_GNU_GETTEXT_VERSION([gettext-version]) +AC_DEFUN([AM_GNU_GETTEXT_VERSION], []) + + +dnl Usage: AM_GNU_GETTEXT_REQUIRE_VERSION([gettext-version]) +AC_DEFUN([AM_GNU_GETTEXT_REQUIRE_VERSION], []) diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/m4/host-cpu-c-abi.m4 b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/m4/host-cpu-c-abi.m4 new file mode 100644 index 0000000000000000000000000000000000000000..6ca7721a326a7335a9fdc59e8677fe62f49c120a --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/m4/host-cpu-c-abi.m4 @@ -0,0 +1,532 @@ +# host-cpu-c-abi.m4 +# serial 20 +dnl Copyright (C) 2002-2025 Free Software Foundation, Inc. +dnl This file is free software; the Free Software Foundation +dnl gives unlimited permission to copy and/or distribute it, +dnl with or without modifications, as long as this notice is preserved. +dnl This file is offered as-is, without any warranty. + +dnl From Bruno Haible and Sam Steingold. + +dnl Sets the HOST_CPU variable to the canonical name of the CPU. +dnl Sets the HOST_CPU_C_ABI variable to the canonical name of the CPU with its +dnl C language ABI (application binary interface). +dnl Also defines __${HOST_CPU}__ and __${HOST_CPU_C_ABI}__ as C macros in +dnl config.h. +dnl +dnl This canonical name can be used to select a particular assembly language +dnl source file that will interoperate with C code on the given host. +dnl +dnl For example: +dnl * 'i386' and 'sparc' are different canonical names, because code for i386 +dnl will not run on SPARC CPUs and vice versa. They have different +dnl instruction sets. +dnl * 'sparc' and 'sparc64' are different canonical names, because code for +dnl 'sparc' and code for 'sparc64' cannot be linked together: 'sparc' code +dnl contains 32-bit instructions, whereas 'sparc64' code contains 64-bit +dnl instructions. A process on a SPARC CPU can be in 32-bit mode or in 64-bit +dnl mode, but not both. +dnl * 'mips' and 'mipsn32' are different canonical names, because they use +dnl different argument passing and return conventions for C functions, and +dnl although the instruction set of 'mips' is a large subset of the +dnl instruction set of 'mipsn32'. +dnl * 'mipsn32' and 'mips64' are different canonical names, because they use +dnl different sizes for the C types like 'int' and 'void *', and although +dnl the instruction sets of 'mipsn32' and 'mips64' are the same. +dnl * The same canonical name is used for different endiannesses. You can +dnl determine the endianness through preprocessor symbols: +dnl - 'arm': test __ARMEL__. +dnl - 'mips', 'mipsn32', 'mips64': test _MIPSEB vs. _MIPSEL. +dnl - 'powerpc64': test __BIG_ENDIAN__ vs. __LITTLE_ENDIAN__. +dnl * The same name 'i386' is used for CPUs of type i386, i486, i586 +dnl (Pentium), AMD K7, Pentium II, Pentium IV, etc., because +dnl - Instructions that do not exist on all of these CPUs (cmpxchg, +dnl MMX, SSE, SSE2, 3DNow! etc.) are not frequently used. If your +dnl assembly language source files use such instructions, you will +dnl need to make the distinction. +dnl - Speed of execution of the common instruction set is reasonable across +dnl the entire family of CPUs. If you have assembly language source files +dnl that are optimized for particular CPU types (like GNU gmp has), you +dnl will need to make the distinction. +dnl See . +AC_DEFUN([gl_HOST_CPU_C_ABI], +[ + AC_REQUIRE([AC_CANONICAL_HOST]) + AC_REQUIRE([gl_C_ASM]) + AC_CACHE_CHECK([host CPU and C ABI], [gl_cv_host_cpu_c_abi], + [case "$host_cpu" in + +changequote(,)dnl + i[34567]86 ) +changequote([,])dnl + gl_cv_host_cpu_c_abi=i386 + ;; + + x86_64 ) + # On x86_64 systems, the C compiler may be generating code in one of + # these ABIs: + # - 64-bit instruction set, 64-bit pointers, 64-bit 'long': x86_64. + # - 64-bit instruction set, 64-bit pointers, 32-bit 'long': x86_64 + # with native Windows (mingw, MSVC). + # - 64-bit instruction set, 32-bit pointers, 32-bit 'long': x86_64-x32. + # - 32-bit instruction set, 32-bit pointers, 32-bit 'long': i386. + AC_COMPILE_IFELSE( + [AC_LANG_SOURCE( + [[#if (defined __x86_64__ || defined __amd64__ \ + || defined _M_X64 || defined _M_AMD64) + int ok; + #else + error fail + #endif + ]])], + [AC_COMPILE_IFELSE( + [AC_LANG_SOURCE( + [[#if defined __ILP32__ || defined _ILP32 + int ok; + #else + error fail + #endif + ]])], + [gl_cv_host_cpu_c_abi=x86_64-x32], + [gl_cv_host_cpu_c_abi=x86_64])], + [gl_cv_host_cpu_c_abi=i386]) + ;; + +changequote(,)dnl + alphaev[4-8] | alphaev56 | alphapca5[67] | alphaev6[78] ) +changequote([,])dnl + gl_cv_host_cpu_c_abi=alpha + ;; + + arm* | aarch64 ) + # Assume arm with EABI. + # On arm64 systems, the C compiler may be generating code in one of + # these ABIs: + # - aarch64 instruction set, 64-bit pointers, 64-bit 'long': arm64. + # - aarch64 instruction set, 32-bit pointers, 32-bit 'long': arm64-ilp32. + # - 32-bit instruction set, 32-bit pointers, 32-bit 'long': arm or armhf. + AC_COMPILE_IFELSE( + [AC_LANG_SOURCE( + [[#ifdef __aarch64__ + int ok; + #else + error fail + #endif + ]])], + [AC_COMPILE_IFELSE( + [AC_LANG_SOURCE( + [[#if defined __ILP32__ || defined _ILP32 + int ok; + #else + error fail + #endif + ]])], + [gl_cv_host_cpu_c_abi=arm64-ilp32], + [gl_cv_host_cpu_c_abi=arm64])], + [# Don't distinguish little-endian and big-endian arm, since they + # don't require different machine code for simple operations and + # since the user can distinguish them through the preprocessor + # defines __ARMEL__ vs. __ARMEB__. + # But distinguish arm which passes floating-point arguments and + # return values in integer registers (r0, r1, ...) - this is + # gcc -mfloat-abi=soft or gcc -mfloat-abi=softfp - from arm which + # passes them in float registers (s0, s1, ...) and double registers + # (d0, d1, ...) - this is gcc -mfloat-abi=hard. GCC 4.6 or newer + # sets the preprocessor defines __ARM_PCS (for the first case) and + # __ARM_PCS_VFP (for the second case), but older GCC does not. + echo 'double ddd; void func (double dd) { ddd = dd; }' > conftest.c + # Look for a reference to the register d0 in the .s file. + AC_TRY_COMMAND(${CC-cc} $CFLAGS $CPPFLAGS $gl_c_asm_opt conftest.c) >/dev/null 2>&1 + if LC_ALL=C grep 'd0,' conftest.$gl_asmext >/dev/null; then + gl_cv_host_cpu_c_abi=armhf + else + gl_cv_host_cpu_c_abi=arm + fi + rm -fr conftest* + ]) + ;; + + hppa1.0 | hppa1.1 | hppa2.0* | hppa64 ) + # On hppa, the C compiler may be generating 32-bit code or 64-bit + # code. In the latter case, it defines _LP64 and __LP64__. + AC_COMPILE_IFELSE( + [AC_LANG_SOURCE( + [[#ifdef __LP64__ + int ok; + #else + error fail + #endif + ]])], + [gl_cv_host_cpu_c_abi=hppa64], + [gl_cv_host_cpu_c_abi=hppa]) + ;; + + ia64* ) + # On ia64 on HP-UX, the C compiler may be generating 64-bit code or + # 32-bit code. In the latter case, it defines _ILP32. + AC_COMPILE_IFELSE( + [AC_LANG_SOURCE( + [[#ifdef _ILP32 + int ok; + #else + error fail + #endif + ]])], + [gl_cv_host_cpu_c_abi=ia64-ilp32], + [gl_cv_host_cpu_c_abi=ia64]) + ;; + + mips* ) + # We should also check for (_MIPS_SZPTR == 64), but gcc keeps this + # at 32. + AC_COMPILE_IFELSE( + [AC_LANG_SOURCE( + [[#if defined _MIPS_SZLONG && (_MIPS_SZLONG == 64) + int ok; + #else + error fail + #endif + ]])], + [gl_cv_host_cpu_c_abi=mips64], + [# In the n32 ABI, _ABIN32 is defined, _ABIO32 is not defined (but + # may later get defined by ), and _MIPS_SIM == _ABIN32. + # In the 32 ABI, _ABIO32 is defined, _ABIN32 is not defined (but + # may later get defined by ), and _MIPS_SIM == _ABIO32. + AC_COMPILE_IFELSE( + [AC_LANG_SOURCE( + [[#if (_MIPS_SIM == _ABIN32) + int ok; + #else + error fail + #endif + ]])], + [gl_cv_host_cpu_c_abi=mipsn32], + [gl_cv_host_cpu_c_abi=mips])]) + ;; + + powerpc* ) + # Different ABIs are in use on AIX vs. Mac OS X vs. Linux,*BSD. + # No need to distinguish them here; the caller may distinguish + # them based on the OS. + # On powerpc64 systems, the C compiler may still be generating + # 32-bit code. And on powerpc-ibm-aix systems, the C compiler may + # be generating 64-bit code. + AC_COMPILE_IFELSE( + [AC_LANG_SOURCE( + [[#if defined __powerpc64__ || defined __LP64__ + int ok; + #else + error fail + #endif + ]])], + [# On powerpc64, there are two ABIs on Linux: The AIX compatible + # one and the ELFv2 one. The latter defines _CALL_ELF=2. + AC_COMPILE_IFELSE( + [AC_LANG_SOURCE( + [[#if defined _CALL_ELF && _CALL_ELF == 2 + int ok; + #else + error fail + #endif + ]])], + [gl_cv_host_cpu_c_abi=powerpc64-elfv2], + [gl_cv_host_cpu_c_abi=powerpc64]) + ], + [gl_cv_host_cpu_c_abi=powerpc]) + ;; + + rs6000 ) + gl_cv_host_cpu_c_abi=powerpc + ;; + + riscv32 | riscv64 ) + # There are 2 architectures (with variants): rv32* and rv64*. + AC_COMPILE_IFELSE( + [AC_LANG_SOURCE( + [[#if __riscv_xlen == 64 + int ok; + #else + error fail + #endif + ]])], + [cpu=riscv64], + [cpu=riscv32]) + # There are 6 ABIs: ilp32, ilp32f, ilp32d, lp64, lp64f, lp64d. + # Size of 'long' and 'void *': + AC_COMPILE_IFELSE( + [AC_LANG_SOURCE( + [[#if defined __LP64__ + int ok; + #else + error fail + #endif + ]])], + [main_abi=lp64], + [main_abi=ilp32]) + # Float ABIs: + # __riscv_float_abi_double: + # 'float' and 'double' are passed in floating-point registers. + # __riscv_float_abi_single: + # 'float' are passed in floating-point registers. + # __riscv_float_abi_soft: + # No values are passed in floating-point registers. + AC_COMPILE_IFELSE( + [AC_LANG_SOURCE( + [[#if defined __riscv_float_abi_double + int ok; + #else + error fail + #endif + ]])], + [float_abi=d], + [AC_COMPILE_IFELSE( + [AC_LANG_SOURCE( + [[#if defined __riscv_float_abi_single + int ok; + #else + error fail + #endif + ]])], + [float_abi=f], + [float_abi='']) + ]) + gl_cv_host_cpu_c_abi="${cpu}-${main_abi}${float_abi}" + ;; + + s390* ) + # On s390x, the C compiler may be generating 64-bit (= s390x) code + # or 31-bit (= s390) code. + AC_COMPILE_IFELSE( + [AC_LANG_SOURCE( + [[#if defined __LP64__ || defined __s390x__ + int ok; + #else + error fail + #endif + ]])], + [gl_cv_host_cpu_c_abi=s390x], + [gl_cv_host_cpu_c_abi=s390]) + ;; + + sparc | sparc64 ) + # UltraSPARCs running Linux have `uname -m` = "sparc64", but the + # C compiler still generates 32-bit code. + AC_COMPILE_IFELSE( + [AC_LANG_SOURCE( + [[#if defined __sparcv9 || defined __arch64__ + int ok; + #else + error fail + #endif + ]])], + [gl_cv_host_cpu_c_abi=sparc64], + [gl_cv_host_cpu_c_abi=sparc]) + ;; + + *) + gl_cv_host_cpu_c_abi="$host_cpu" + ;; + esac + ]) + + dnl In most cases, $HOST_CPU and $HOST_CPU_C_ABI are the same. + HOST_CPU=`echo "$gl_cv_host_cpu_c_abi" | sed -e 's/-.*//'` + HOST_CPU_C_ABI="$gl_cv_host_cpu_c_abi" + AC_SUBST([HOST_CPU]) + AC_SUBST([HOST_CPU_C_ABI]) + + # This was + # AC_DEFINE_UNQUOTED([__${HOST_CPU}__]) + # AC_DEFINE_UNQUOTED([__${HOST_CPU_C_ABI}__]) + # earlier, but KAI C++ 3.2d doesn't like this. + sed -e 's/-/_/g' >> confdefs.h <. +dnl Don't make changes that are incompatible with that documentation! + +AC_DEFUN([AM_ICONV_LINKFLAGS_BODY], +[ + dnl Prerequisites of AC_LIB_LINKFLAGS_BODY. + AC_REQUIRE([AC_LIB_PREPARE_PREFIX]) + AC_REQUIRE([AC_LIB_RPATH]) + + dnl Search for libiconv and define LIBICONV, LTLIBICONV and INCICONV + dnl accordingly. + AC_LIB_LINKFLAGS_BODY([iconv]) +]) + +AC_DEFUN([AM_ICONV_LINK], +[ + dnl Some systems have iconv in libc, some have it in libiconv (OSF/1 and + dnl those with the standalone portable GNU libiconv installed). + AC_REQUIRE([AC_CANONICAL_HOST]) dnl for cross-compiles + + dnl Search for libiconv and define LIBICONV, LTLIBICONV and INCICONV + dnl accordingly. + AC_REQUIRE([AM_ICONV_LINKFLAGS_BODY]) + + dnl Add $INCICONV to CPPFLAGS before performing the following checks, + dnl because if the user has installed libiconv and not disabled its use + dnl via --without-libiconv-prefix, he wants to use it. The first + dnl AC_LINK_IFELSE will then fail, the second AC_LINK_IFELSE will succeed. + gl_saved_CPPFLAGS="$CPPFLAGS" + AC_LIB_APPENDTOVAR([CPPFLAGS], [$INCICONV]) + + AC_CACHE_CHECK([for iconv], [am_cv_func_iconv], [ + am_cv_func_iconv="no, consider installing GNU libiconv" + am_cv_lib_iconv=no + AC_LINK_IFELSE( + [AC_LANG_PROGRAM( + [[ +#include +#include + ]], + [[iconv_t cd = iconv_open("",""); + iconv(cd,NULL,NULL,NULL,NULL); + iconv_close(cd);]])], + [am_cv_func_iconv=yes]) + if test "$am_cv_func_iconv" != yes; then + gl_saved_LIBS="$LIBS" + LIBS="$LIBS $LIBICONV" + AC_LINK_IFELSE( + [AC_LANG_PROGRAM( + [[ +#include +#include + ]], + [[iconv_t cd = iconv_open("",""); + iconv(cd,NULL,NULL,NULL,NULL); + iconv_close(cd);]])], + [am_cv_lib_iconv=yes] + [am_cv_func_iconv=yes]) + LIBS="$gl_saved_LIBS" + fi + ]) + if test "$am_cv_func_iconv" = yes; then + AC_CACHE_CHECK([for working iconv], [am_cv_func_iconv_works], [ + dnl This tests against bugs in AIX 5.1, AIX 6.1..7.1, HP-UX 11.11, + dnl Solaris 10, macOS 14.4. + gl_saved_LIBS="$LIBS" + if test $am_cv_lib_iconv = yes; then + LIBS="$LIBS $LIBICONV" + fi + am_cv_func_iconv_works=no + for ac_iconv_const in '' 'const'; do + AC_RUN_IFELSE( + [AC_LANG_PROGRAM( + [[ +#include +#include + +#ifndef ICONV_CONST +# define ICONV_CONST $ac_iconv_const +#endif + ]], + [[int result = 0; + /* Test against AIX 5.1...7.2 bug: Failures are not distinguishable from + successful returns. This is even documented in + */ + { + iconv_t cd_utf8_to_88591 = iconv_open ("ISO8859-1", "UTF-8"); + if (cd_utf8_to_88591 != (iconv_t)(-1)) + { + static ICONV_CONST char input[] = "\342\202\254"; /* EURO SIGN */ + char buf[10]; + ICONV_CONST char *inptr = input; + size_t inbytesleft = strlen (input); + char *outptr = buf; + size_t outbytesleft = sizeof (buf); + size_t res = iconv (cd_utf8_to_88591, + &inptr, &inbytesleft, + &outptr, &outbytesleft); + if (res == 0) + result |= 1; + iconv_close (cd_utf8_to_88591); + } + } + /* Test against macOS 14.4 bug: Failures are not distinguishable from + successful returns. + POSIX:2018 says: "The iconv() function shall ... return the number of + non-identical conversions performed." + But here, the conversion always does transliteration (the suffixes + "//TRANSLIT" and "//IGNORE" have no effect, nor does iconvctl()) and + does not report when it does a non-identical conversion. */ + { + iconv_t cd_utf8_to_88591 = iconv_open ("ISO-8859-1", "UTF-8"); + if (cd_utf8_to_88591 != (iconv_t)(-1)) + { + static ICONV_CONST char input[] = "\305\202"; /* LATIN SMALL LETTER L WITH STROKE */ + char buf[10]; + ICONV_CONST char *inptr = input; + size_t inbytesleft = strlen (input); + char *outptr = buf; + size_t outbytesleft = sizeof (buf); + size_t res = iconv (cd_utf8_to_88591, + &inptr, &inbytesleft, + &outptr, &outbytesleft); + /* Here: + With glibc, GNU libiconv (including macOS up to 13): res == (size_t)-1, errno == EILSEQ. + With musl libc, NetBSD 10, Solaris 11: res == 1. + With macOS 14.4: res == 0, output is "l". */ + if (res == 0) + result |= 2; + iconv_close (cd_utf8_to_88591); + } + } + /* Test against Solaris 10 bug: Failures are not distinguishable from + successful returns. */ + { + iconv_t cd_ascii_to_88591 = iconv_open ("ISO8859-1", "646"); + if (cd_ascii_to_88591 != (iconv_t)(-1)) + { + static ICONV_CONST char input[] = "\263"; + char buf[10]; + ICONV_CONST char *inptr = input; + size_t inbytesleft = strlen (input); + char *outptr = buf; + size_t outbytesleft = sizeof (buf); + size_t res = iconv (cd_ascii_to_88591, + &inptr, &inbytesleft, + &outptr, &outbytesleft); + if (res == 0) + result |= 4; + iconv_close (cd_ascii_to_88591); + } + } + /* Test against AIX 6.1..7.1 bug: Buffer overrun. */ + { + iconv_t cd_88591_to_utf8 = iconv_open ("UTF-8", "ISO-8859-1"); + if (cd_88591_to_utf8 != (iconv_t)(-1)) + { + static ICONV_CONST char input[] = "\304"; + static char buf[2] = { (char)0xDE, (char)0xAD }; + ICONV_CONST char *inptr = input; + size_t inbytesleft = 1; + char *outptr = buf; + size_t outbytesleft = 1; + size_t res = iconv (cd_88591_to_utf8, + &inptr, &inbytesleft, + &outptr, &outbytesleft); + if (res != (size_t)(-1) || outptr - buf > 1 || buf[1] != (char)0xAD) + result |= 8; + iconv_close (cd_88591_to_utf8); + } + } +#if 0 /* This bug could be worked around by the caller. */ + /* Test against HP-UX 11.11 bug: Positive return value instead of 0. */ + { + iconv_t cd_88591_to_utf8 = iconv_open ("utf8", "iso88591"); + if (cd_88591_to_utf8 != (iconv_t)(-1)) + { + static ICONV_CONST char input[] = "\304rger mit b\366sen B\374bchen ohne Augenma\337"; + char buf[50]; + ICONV_CONST char *inptr = input; + size_t inbytesleft = strlen (input); + char *outptr = buf; + size_t outbytesleft = sizeof (buf); + size_t res = iconv (cd_88591_to_utf8, + &inptr, &inbytesleft, + &outptr, &outbytesleft); + if ((int)res > 0) + result |= 16; + iconv_close (cd_88591_to_utf8); + } + } +#endif + /* Test against HP-UX 11.11 bug: No converter from EUC-JP to UTF-8 is + provided. */ + { + /* Try standardized names. */ + iconv_t cd1 = iconv_open ("UTF-8", "EUC-JP"); + /* Try IRIX, OSF/1 names. */ + iconv_t cd2 = iconv_open ("UTF-8", "eucJP"); + /* Try AIX names. */ + iconv_t cd3 = iconv_open ("UTF-8", "IBM-eucJP"); + /* Try HP-UX names. */ + iconv_t cd4 = iconv_open ("utf8", "eucJP"); + if (cd1 == (iconv_t)(-1) && cd2 == (iconv_t)(-1) + && cd3 == (iconv_t)(-1) && cd4 == (iconv_t)(-1)) + result |= 32; + if (cd1 != (iconv_t)(-1)) + iconv_close (cd1); + if (cd2 != (iconv_t)(-1)) + iconv_close (cd2); + if (cd3 != (iconv_t)(-1)) + iconv_close (cd3); + if (cd4 != (iconv_t)(-1)) + iconv_close (cd4); + } + return result; +]])], + [am_cv_func_iconv_works=yes], , + [case "$host_os" in + aix* | hpux*) am_cv_func_iconv_works="guessing no" ;; + *) am_cv_func_iconv_works="guessing yes" ;; + esac]) + test "$am_cv_func_iconv_works" = no || break + done + LIBS="$gl_saved_LIBS" + ]) + case "$am_cv_func_iconv_works" in + *no) am_func_iconv=no am_cv_lib_iconv=no ;; + *) am_func_iconv=yes ;; + esac + else + am_func_iconv=no am_cv_lib_iconv=no + fi + if test "$am_func_iconv" = yes; then + AC_DEFINE([HAVE_ICONV], [1], + [Define if you have the iconv() function and it works.]) + fi + if test "$am_cv_lib_iconv" = yes; then + AC_MSG_CHECKING([how to link with libiconv]) + AC_MSG_RESULT([$LIBICONV]) + else + dnl If $LIBICONV didn't lead to a usable library, we don't need $INCICONV + dnl either. + CPPFLAGS="$gl_saved_CPPFLAGS" + LIBICONV= + LTLIBICONV= + fi + AC_SUBST([LIBICONV]) + AC_SUBST([LTLIBICONV]) +]) + +dnl Define AM_ICONV using AC_DEFUN_ONCE, in order to avoid warnings like +dnl "warning: AC_REQUIRE: `AM_ICONV' was expanded before it was required". +AC_DEFUN_ONCE([AM_ICONV], +[ + AM_ICONV_LINK + if test "$am_cv_func_iconv" = yes; then + AC_CACHE_CHECK([whether iconv is compatible with its POSIX signature], + [gl_cv_iconv_nonconst], + [AC_COMPILE_IFELSE( + [AC_LANG_PROGRAM( + [[ +#include +#include +extern +#ifdef __cplusplus +"C" +#endif +size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft, char * *outbuf, size_t *outbytesleft); + ]], + [[]])], + [gl_cv_iconv_nonconst=yes], + [gl_cv_iconv_nonconst=no]) + ]) + else + dnl When compiling GNU libiconv on a system that does not have iconv yet, + dnl pick the POSIX compliant declaration without 'const'. + gl_cv_iconv_nonconst=yes + fi + if test $gl_cv_iconv_nonconst = yes; then + iconv_arg1="" + else + iconv_arg1="const" + fi + AC_DEFINE_UNQUOTED([ICONV_CONST], [$iconv_arg1], + [Define as const if the declaration of iconv() needs const.]) + dnl Also substitute ICONV_CONST in the gnulib generated . + m4_ifdef([gl_ICONV_H_DEFAULTS], + [AC_REQUIRE([gl_ICONV_H_DEFAULTS]) + if test $gl_cv_iconv_nonconst != yes; then + ICONV_CONST="const" + fi + ]) + + dnl A summary result, for those packages which want to print a summary at the + dnl end of the configuration. + if test "$am_func_iconv" = yes; then + if test -n "$LIBICONV"; then + am_cv_func_iconv_summary='yes, in libiconv' + else + am_cv_func_iconv_summary='yes, in libc' + fi + else + if test "$am_cv_func_iconv" = yes; then + am_cv_func_iconv_summary='not working, consider installing GNU libiconv' + else + am_cv_func_iconv_summary='no, consider installing GNU libiconv' + fi + fi +]) diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/m4/intlmacosx.m4 b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/m4/intlmacosx.m4 new file mode 100644 index 0000000000000000000000000000000000000000..f0920d0ffc536ba550e3575560ed2c478ab69734 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/m4/intlmacosx.m4 @@ -0,0 +1,71 @@ +# intlmacosx.m4 +# serial 10 (gettext-0.23) +dnl Copyright (C) 2004-2014, 2016, 2019-2025 Free Software Foundation, Inc. +dnl This file is free software; the Free Software Foundation +dnl gives unlimited permission to copy and/or distribute it, +dnl with or without modifications, as long as this notice is preserved. +dnl This file is offered as-is, without any warranty. +dnl +dnl This file can be used in projects which are not available under +dnl the GNU General Public License or the GNU Lesser General Public +dnl License but which still want to provide support for the GNU gettext +dnl functionality. +dnl Please note that the actual code of the GNU gettext library is covered +dnl by the GNU Lesser General Public License, and the rest of the GNU +dnl gettext package is covered by the GNU General Public License. +dnl They are *not* in the public domain. + +dnl Checks for special options needed on Mac OS X. +dnl Defines INTL_MACOSX_LIBS. +AC_DEFUN([gt_INTL_MACOSX], +[ + dnl Check for API introduced in Mac OS X 10.4. + AC_CACHE_CHECK([for CFPreferencesCopyAppValue], + [gt_cv_func_CFPreferencesCopyAppValue], + [gt_saved_LIBS="$LIBS" + LIBS="$LIBS -Wl,-framework -Wl,CoreFoundation" + AC_LINK_IFELSE( + [AC_LANG_PROGRAM( + [[#include ]], + [[CFPreferencesCopyAppValue(NULL, NULL)]])], + [gt_cv_func_CFPreferencesCopyAppValue=yes], + [gt_cv_func_CFPreferencesCopyAppValue=no]) + LIBS="$gt_saved_LIBS"]) + if test $gt_cv_func_CFPreferencesCopyAppValue = yes; then + AC_DEFINE([HAVE_CFPREFERENCESCOPYAPPVALUE], [1], + [Define to 1 if you have the Mac OS X function CFPreferencesCopyAppValue in the CoreFoundation framework.]) + fi + dnl Don't check for the API introduced in Mac OS X 10.5, CFLocaleCopyCurrent, + dnl because in macOS 10.13.4 it has the following behaviour: + dnl When two or more languages are specified in the + dnl "System Preferences > Language & Region > Preferred Languages" panel, + dnl it returns en_CC where CC is the territory (even when English is not among + dnl the preferred languages!). What we want instead is what + dnl CFLocaleCopyCurrent returned in earlier macOS releases and what + dnl CFPreferencesCopyAppValue still returns, namely ll_CC where ll is the + dnl first among the preferred languages and CC is the territory. + AC_CACHE_CHECK([for CFLocaleCopyPreferredLanguages], [gt_cv_func_CFLocaleCopyPreferredLanguages], + [gt_saved_LIBS="$LIBS" + LIBS="$LIBS -Wl,-framework -Wl,CoreFoundation" + AC_LINK_IFELSE( + [AC_LANG_PROGRAM( + [[#include ]], + [[CFLocaleCopyPreferredLanguages();]])], + [gt_cv_func_CFLocaleCopyPreferredLanguages=yes], + [gt_cv_func_CFLocaleCopyPreferredLanguages=no]) + LIBS="$gt_saved_LIBS"]) + if test $gt_cv_func_CFLocaleCopyPreferredLanguages = yes; then + AC_DEFINE([HAVE_CFLOCALECOPYPREFERREDLANGUAGES], [1], + [Define to 1 if you have the Mac OS X function CFLocaleCopyPreferredLanguages in the CoreFoundation framework.]) + fi + INTL_MACOSX_LIBS= + if test $gt_cv_func_CFPreferencesCopyAppValue = yes \ + || test $gt_cv_func_CFLocaleCopyPreferredLanguages = yes; then + dnl Starting with macOS version 14, CoreFoundation relies on CoreServices, + dnl and we have to link it in explicitly, otherwise an exception + dnl NSInvalidArgumentException "unrecognized selector sent to instance" + dnl occurs. + INTL_MACOSX_LIBS="-Wl,-framework -Wl,CoreFoundation -Wl,-framework -Wl,CoreServices" + fi + AC_SUBST([INTL_MACOSX_LIBS]) +]) diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/m4/lib-ld.m4 b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/m4/lib-ld.m4 new file mode 100644 index 0000000000000000000000000000000000000000..3714b9ce741d9062e23597461d8ea4806f19bc25 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/m4/lib-ld.m4 @@ -0,0 +1,170 @@ +# lib-ld.m4 +# serial 13 +dnl Copyright (C) 1996-2003, 2009-2025 Free Software Foundation, Inc. +dnl This file is free software; the Free Software Foundation +dnl gives unlimited permission to copy and/or distribute it, +dnl with or without modifications, as long as this notice is preserved. +dnl This file is offered as-is, without any warranty. + +dnl Subroutines of libtool.m4, +dnl with replacements s/_*LT_PATH/AC_LIB_PROG/ and s/lt_/acl_/ to avoid +dnl collision with libtool.m4. + +dnl From libtool-2.4. Sets the variable with_gnu_ld to yes or no. +AC_DEFUN([AC_LIB_PROG_LD_GNU], +[AC_CACHE_CHECK([if the linker ($LD) is GNU ld], [acl_cv_prog_gnu_ld], +[# I'd rather use --version here, but apparently some GNU lds only accept -v. +case `$LD -v 2>&1 /dev/null 2>&1 \ + && { (PATH='/bin:/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 \ + || PATH_SEPARATOR=';' + } +fi + +if test -n "$LD"; then + AC_MSG_CHECKING([for ld]) +elif test "$GCC" = yes; then + AC_MSG_CHECKING([for ld used by $CC]) +elif test "$with_gnu_ld" = yes; then + AC_MSG_CHECKING([for GNU ld]) +else + AC_MSG_CHECKING([for non-GNU ld]) +fi +if test -n "$LD"; then + # Let the user override the test with a path. + : +else + AC_CACHE_VAL([acl_cv_path_LD], + [ + acl_cv_path_LD= # Final result of this test + ac_prog=ld # Program to search in $PATH + if test "$GCC" = yes; then + # Check if gcc -print-prog-name=ld gives a path. + case $host in + *-*-mingw* | windows*) + # gcc leaves a trailing carriage return which upsets mingw + acl_output=`($CC -print-prog-name=ld) 2>&5 | tr -d '\015'` ;; + *) + acl_output=`($CC -print-prog-name=ld) 2>&5` ;; + esac + case $acl_output in + # Accept absolute paths. + [[\\/]]* | ?:[[\\/]]*) + re_direlt='/[[^/]][[^/]]*/\.\./' + # Canonicalize the pathname of ld + acl_output=`echo "$acl_output" | sed 's%\\\\%/%g'` + while echo "$acl_output" | grep "$re_direlt" > /dev/null 2>&1; do + acl_output=`echo $acl_output | sed "s%$re_direlt%/%"` + done + # Got the pathname. No search in PATH is needed. + acl_cv_path_LD="$acl_output" + ac_prog= + ;; + "") + # If it fails, then pretend we aren't using GCC. + ;; + *) + # If it is relative, then search for the first ld in PATH. + with_gnu_ld=unknown + ;; + esac + fi + if test -n "$ac_prog"; then + # Search for $ac_prog in $PATH. + acl_saved_IFS="$IFS"; IFS=$PATH_SEPARATOR + for ac_dir in $PATH; do + IFS="$acl_saved_IFS" + test -z "$ac_dir" && ac_dir=. + if test -f "$ac_dir/$ac_prog" || test -f "$ac_dir/$ac_prog$ac_exeext"; then + acl_cv_path_LD="$ac_dir/$ac_prog" + # Check to see if the program is GNU ld. I'd rather use --version, + # but apparently some variants of GNU ld only accept -v. + # Break only if it was the GNU/non-GNU ld that we prefer. + case `"$acl_cv_path_LD" -v 2>&1 conftest.sh + . ./conftest.sh + rm -f ./conftest.sh + acl_cv_rpath=done + ]) + wl="$acl_cv_wl" + acl_libext="$acl_cv_libext" + acl_shlibext="$acl_cv_shlibext" + acl_libname_spec="$acl_cv_libname_spec" + acl_library_names_spec="$acl_cv_library_names_spec" + acl_hardcode_libdir_flag_spec="$acl_cv_hardcode_libdir_flag_spec" + acl_hardcode_libdir_separator="$acl_cv_hardcode_libdir_separator" + acl_hardcode_direct="$acl_cv_hardcode_direct" + acl_hardcode_minus_L="$acl_cv_hardcode_minus_L" + dnl Determine whether the user wants rpath handling at all. + AC_ARG_ENABLE([rpath], + [ --disable-rpath do not hardcode runtime library paths], + :, enable_rpath=yes) +]) + +dnl AC_LIB_FROMPACKAGE(name, package) +dnl declares that libname comes from the given package. The configure file +dnl will then not have a --with-libname-prefix option but a +dnl --with-package-prefix option. Several libraries can come from the same +dnl package. This declaration must occur before an AC_LIB_LINKFLAGS or similar +dnl macro call that searches for libname. +AC_DEFUN([AC_LIB_FROMPACKAGE], +[ + pushdef([NAME],[m4_translit([$1],[abcdefghijklmnopqrstuvwxyz./+-], + [ABCDEFGHIJKLMNOPQRSTUVWXYZ____])]) + define([acl_frompackage_]NAME, [$2]) + popdef([NAME]) + pushdef([PACK],[$2]) + pushdef([PACKUP],[m4_translit(PACK,[abcdefghijklmnopqrstuvwxyz./+-], + [ABCDEFGHIJKLMNOPQRSTUVWXYZ____])]) + define([acl_libsinpackage_]PACKUP, + m4_ifdef([acl_libsinpackage_]PACKUP, [m4_defn([acl_libsinpackage_]PACKUP)[[, ]]],)[lib$1]) + popdef([PACKUP]) + popdef([PACK]) +]) + +dnl AC_LIB_LINKFLAGS_BODY(name [, dependencies]) searches for libname and +dnl the libraries corresponding to explicit and implicit dependencies. +dnl Sets the LIB${NAME}, LTLIB${NAME} and INC${NAME} variables. +dnl Also, sets the LIB${NAME}_PREFIX variable to nonempty if libname was found +dnl in ${LIB${NAME}_PREFIX}/$acl_libdirstem. +AC_DEFUN([AC_LIB_LINKFLAGS_BODY], +[ + AC_REQUIRE([AC_LIB_PREPARE_MULTILIB]) + pushdef([NAME],[m4_translit([$1],[abcdefghijklmnopqrstuvwxyz./+-], + [ABCDEFGHIJKLMNOPQRSTUVWXYZ____])]) + pushdef([PACK],[m4_ifdef([acl_frompackage_]NAME, [acl_frompackage_]NAME, lib[$1])]) + pushdef([PACKUP],[m4_translit(PACK,[abcdefghijklmnopqrstuvwxyz./+-], + [ABCDEFGHIJKLMNOPQRSTUVWXYZ____])]) + pushdef([PACKLIBS],[m4_ifdef([acl_frompackage_]NAME, [acl_libsinpackage_]PACKUP, lib[$1])]) + dnl By default, look in $includedir and $libdir. + use_additional=yes + AC_LIB_WITH_FINAL_PREFIX([ + eval additional_includedir=\"$includedir\" + eval additional_libdir=\"$libdir\" + eval additional_libdir2=\"$exec_prefix/$acl_libdirstem2\" + eval additional_libdir3=\"$exec_prefix/$acl_libdirstem3\" + ]) + AC_ARG_WITH(PACK[-prefix], +[[ --with-]]PACK[[-prefix[=DIR] search for ]]PACKLIBS[[ in DIR/include and DIR/lib + --without-]]PACK[[-prefix don't search for ]]PACKLIBS[[ in includedir and libdir]], +[ + if test "X$withval" = "Xno"; then + use_additional=no + else + if test "X$withval" = "X"; then + AC_LIB_WITH_FINAL_PREFIX([ + eval additional_includedir=\"$includedir\" + eval additional_libdir=\"$libdir\" + eval additional_libdir2=\"$exec_prefix/$acl_libdirstem2\" + eval additional_libdir3=\"$exec_prefix/$acl_libdirstem3\" + ]) + else + additional_includedir="$withval/include" + additional_libdir="$withval/$acl_libdirstem" + additional_libdir2="$withval/$acl_libdirstem2" + additional_libdir3="$withval/$acl_libdirstem3" + fi + fi +]) + if test "X$additional_libdir2" = "X$additional_libdir"; then + additional_libdir2= + fi + if test "X$additional_libdir3" = "X$additional_libdir"; then + additional_libdir3= + fi + dnl Search the library and its dependencies in $additional_libdir and + dnl $LDFLAGS. Use breadth-first search. + LIB[]NAME= + LTLIB[]NAME= + INC[]NAME= + LIB[]NAME[]_PREFIX= + dnl HAVE_LIB${NAME} is an indicator that LIB${NAME}, LTLIB${NAME} have been + dnl computed. So it has to be reset here. + HAVE_LIB[]NAME= + rpathdirs= + ltrpathdirs= + names_already_handled= + names_next_round='$1 $2' + while test -n "$names_next_round"; do + names_this_round="$names_next_round" + names_next_round= + for name in $names_this_round; do + already_handled= + for n in $names_already_handled; do + if test "$n" = "$name"; then + already_handled=yes + break + fi + done + if test -z "$already_handled"; then + names_already_handled="$names_already_handled $name" + dnl See if it was already located by an earlier AC_LIB_LINKFLAGS + dnl or AC_LIB_HAVE_LINKFLAGS call. + uppername=`echo "$name" | sed -e 'y|abcdefghijklmnopqrstuvwxyz./+-|ABCDEFGHIJKLMNOPQRSTUVWXYZ____|'` + eval value=\"\$HAVE_LIB$uppername\" + if test -n "$value"; then + if test "$value" = yes; then + eval value=\"\$LIB$uppername\" + test -z "$value" || LIB[]NAME="${LIB[]NAME}${LIB[]NAME:+ }$value" + eval value=\"\$LTLIB$uppername\" + test -z "$value" || LTLIB[]NAME="${LTLIB[]NAME}${LTLIB[]NAME:+ }$value" + else + dnl An earlier call to AC_LIB_HAVE_LINKFLAGS has determined + dnl that this library doesn't exist. So just drop it. + : + fi + else + dnl Search the library lib$name in $additional_libdir and $LDFLAGS + dnl and the already constructed $LIBNAME/$LTLIBNAME. + found_dir= + found_la= + found_so= + found_a= + eval libname=\"$acl_libname_spec\" # typically: libname=lib$name + if test -n "$acl_shlibext"; then + shrext=".$acl_shlibext" # typically: shrext=.so + else + shrext= + fi + if test $use_additional = yes; then + for additional_libdir_variable in additional_libdir additional_libdir2 additional_libdir3; do + if test "X$found_dir" = "X"; then + eval dir=\$$additional_libdir_variable + if test -n "$dir"; then + dnl The same code as in the loop below: + dnl First look for a shared library. + if test -n "$acl_shlibext"; then + if test -f "$dir/$libname$shrext" && acl_is_expected_elfclass < "$dir/$libname$shrext"; then + found_dir="$dir" + found_so="$dir/$libname$shrext" + else + if test "$acl_library_names_spec" = '$libname$shrext$versuffix'; then + ver=`(cd "$dir" && \ + for f in "$libname$shrext".*; do echo "$f"; done \ + | sed -e "s,^$libname$shrext\\\\.,," \ + | sort -t '.' -n -r -k1,1 -k2,2 -k3,3 -k4,4 -k5,5 \ + | sed 1q ) 2>/dev/null` + if test -n "$ver" && test -f "$dir/$libname$shrext.$ver" && acl_is_expected_elfclass < "$dir/$libname$shrext.$ver"; then + found_dir="$dir" + found_so="$dir/$libname$shrext.$ver" + fi + else + eval library_names=\"$acl_library_names_spec\" + for f in $library_names; do + if test -f "$dir/$f" && acl_is_expected_elfclass < "$dir/$f"; then + found_dir="$dir" + found_so="$dir/$f" + break + fi + done + fi + fi + fi + dnl Then look for a static library. + if test "X$found_dir" = "X"; then + if test -f "$dir/$libname.$acl_libext" && ${AR-ar} -p "$dir/$libname.$acl_libext" | acl_is_expected_elfclass; then + found_dir="$dir" + found_a="$dir/$libname.$acl_libext" + fi + fi + if test "X$found_dir" != "X"; then + if test -f "$dir/$libname.la"; then + found_la="$dir/$libname.la" + fi + fi + fi + fi + done + fi + if test "X$found_dir" = "X"; then + for x in $LDFLAGS $LTLIB[]NAME; do + AC_LIB_WITH_FINAL_PREFIX([eval x=\"$x\"]) + case "$x" in + -L*) + dir=`echo "X$x" | sed -e 's/^X-L//'` + dnl First look for a shared library. + if test -n "$acl_shlibext"; then + if test -f "$dir/$libname$shrext" && acl_is_expected_elfclass < "$dir/$libname$shrext"; then + found_dir="$dir" + found_so="$dir/$libname$shrext" + else + if test "$acl_library_names_spec" = '$libname$shrext$versuffix'; then + ver=`(cd "$dir" && \ + for f in "$libname$shrext".*; do echo "$f"; done \ + | sed -e "s,^$libname$shrext\\\\.,," \ + | sort -t '.' -n -r -k1,1 -k2,2 -k3,3 -k4,4 -k5,5 \ + | sed 1q ) 2>/dev/null` + if test -n "$ver" && test -f "$dir/$libname$shrext.$ver" && acl_is_expected_elfclass < "$dir/$libname$shrext.$ver"; then + found_dir="$dir" + found_so="$dir/$libname$shrext.$ver" + fi + else + eval library_names=\"$acl_library_names_spec\" + for f in $library_names; do + if test -f "$dir/$f" && acl_is_expected_elfclass < "$dir/$f"; then + found_dir="$dir" + found_so="$dir/$f" + break + fi + done + fi + fi + fi + dnl Then look for a static library. + if test "X$found_dir" = "X"; then + if test -f "$dir/$libname.$acl_libext" && ${AR-ar} -p "$dir/$libname.$acl_libext" | acl_is_expected_elfclass; then + found_dir="$dir" + found_a="$dir/$libname.$acl_libext" + fi + fi + if test "X$found_dir" != "X"; then + if test -f "$dir/$libname.la"; then + found_la="$dir/$libname.la" + fi + fi + ;; + esac + if test "X$found_dir" != "X"; then + break + fi + done + fi + if test "X$found_dir" != "X"; then + dnl Found the library. + LTLIB[]NAME="${LTLIB[]NAME}${LTLIB[]NAME:+ }-L$found_dir -l$name" + if test "X$found_so" != "X"; then + dnl Linking with a shared library. We attempt to hardcode its + dnl directory into the executable's runpath, unless it's the + dnl standard /usr/lib. + if test "$enable_rpath" = no \ + || test "X$found_dir" = "X/usr/$acl_libdirstem" \ + || test "X$found_dir" = "X/usr/$acl_libdirstem2" \ + || test "X$found_dir" = "X/usr/$acl_libdirstem3"; then + dnl No hardcoding is needed. + LIB[]NAME="${LIB[]NAME}${LIB[]NAME:+ }$found_so" + else + dnl Use an explicit option to hardcode DIR into the resulting + dnl binary. + dnl Potentially add DIR to ltrpathdirs. + dnl The ltrpathdirs will be appended to $LTLIBNAME at the end. + haveit= + for x in $ltrpathdirs; do + if test "X$x" = "X$found_dir"; then + haveit=yes + break + fi + done + if test -z "$haveit"; then + ltrpathdirs="$ltrpathdirs $found_dir" + fi + dnl The hardcoding into $LIBNAME is system dependent. + if test "$acl_hardcode_direct" = yes; then + dnl Using DIR/libNAME.so during linking hardcodes DIR into the + dnl resulting binary. + LIB[]NAME="${LIB[]NAME}${LIB[]NAME:+ }$found_so" + else + if test -n "$acl_hardcode_libdir_flag_spec" && test "$acl_hardcode_minus_L" = no; then + dnl Use an explicit option to hardcode DIR into the resulting + dnl binary. + LIB[]NAME="${LIB[]NAME}${LIB[]NAME:+ }$found_so" + dnl Potentially add DIR to rpathdirs. + dnl The rpathdirs will be appended to $LIBNAME at the end. + haveit= + for x in $rpathdirs; do + if test "X$x" = "X$found_dir"; then + haveit=yes + break + fi + done + if test -z "$haveit"; then + rpathdirs="$rpathdirs $found_dir" + fi + else + dnl Rely on "-L$found_dir". + dnl But don't add it if it's already contained in the LDFLAGS + dnl or the already constructed $LIBNAME + haveit= + for x in $LDFLAGS $LIB[]NAME; do + AC_LIB_WITH_FINAL_PREFIX([eval x=\"$x\"]) + if test "X$x" = "X-L$found_dir"; then + haveit=yes + break + fi + done + if test -z "$haveit"; then + LIB[]NAME="${LIB[]NAME}${LIB[]NAME:+ }-L$found_dir" + fi + if test "$acl_hardcode_minus_L" != no; then + dnl FIXME: Not sure whether we should use + dnl "-L$found_dir -l$name" or "-L$found_dir $found_so" + dnl here. + LIB[]NAME="${LIB[]NAME}${LIB[]NAME:+ }$found_so" + else + dnl We cannot use $acl_hardcode_runpath_var and LD_RUN_PATH + dnl here, because this doesn't fit in flags passed to the + dnl compiler. So give up. No hardcoding. This affects only + dnl very old systems. + dnl FIXME: Not sure whether we should use + dnl "-L$found_dir -l$name" or "-L$found_dir $found_so" + dnl here. + LIB[]NAME="${LIB[]NAME}${LIB[]NAME:+ }-l$name" + fi + fi + fi + fi + else + if test "X$found_a" != "X"; then + dnl Linking with a static library. + LIB[]NAME="${LIB[]NAME}${LIB[]NAME:+ }$found_a" + else + dnl We shouldn't come here, but anyway it's good to have a + dnl fallback. + LIB[]NAME="${LIB[]NAME}${LIB[]NAME:+ }-L$found_dir -l$name" + fi + fi + dnl Assume the include files are nearby. + additional_includedir= + case "$found_dir" in + */$acl_libdirstem | */$acl_libdirstem/) + basedir=`echo "X$found_dir" | sed -e 's,^X,,' -e "s,/$acl_libdirstem/"'*$,,'` + if test "$name" = '$1'; then + LIB[]NAME[]_PREFIX="$basedir" + fi + additional_includedir="$basedir/include" + ;; + */$acl_libdirstem2 | */$acl_libdirstem2/) + basedir=`echo "X$found_dir" | sed -e 's,^X,,' -e "s,/$acl_libdirstem2/"'*$,,'` + if test "$name" = '$1'; then + LIB[]NAME[]_PREFIX="$basedir" + fi + additional_includedir="$basedir/include" + ;; + */$acl_libdirstem3 | */$acl_libdirstem3/) + basedir=`echo "X$found_dir" | sed -e 's,^X,,' -e "s,/$acl_libdirstem3/"'*$,,'` + if test "$name" = '$1'; then + LIB[]NAME[]_PREFIX="$basedir" + fi + additional_includedir="$basedir/include" + ;; + esac + if test "X$additional_includedir" != "X"; then + dnl Potentially add $additional_includedir to $INCNAME. + dnl But don't add it + dnl 1. if it's the standard /usr/include, + dnl 2. if it's /usr/local/include and we are using GCC on Linux, + dnl 3. if it's already present in $CPPFLAGS or the already + dnl constructed $INCNAME, + dnl 4. if it doesn't exist as a directory. + if test "X$additional_includedir" != "X/usr/include"; then + haveit= + if test "X$additional_includedir" = "X/usr/local/include"; then + if test -n "$GCC"; then + case $host_os in + linux* | gnu* | k*bsd*-gnu) haveit=yes;; + esac + fi + fi + if test -z "$haveit"; then + for x in $CPPFLAGS $INC[]NAME; do + AC_LIB_WITH_FINAL_PREFIX([eval x=\"$x\"]) + if test "X$x" = "X-I$additional_includedir"; then + haveit=yes + break + fi + done + if test -z "$haveit"; then + if test -d "$additional_includedir"; then + dnl Really add $additional_includedir to $INCNAME. + INC[]NAME="${INC[]NAME}${INC[]NAME:+ }-I$additional_includedir" + fi + fi + fi + fi + fi + dnl Look for dependencies. + if test -n "$found_la"; then + dnl Read the .la file. It defines the variables + dnl dlname, library_names, old_library, dependency_libs, current, + dnl age, revision, installed, dlopen, dlpreopen, libdir. + saved_libdir="$libdir" + case "$found_la" in + */* | *\\*) . "$found_la" ;; + *) . "./$found_la" ;; + esac + libdir="$saved_libdir" + dnl We use only dependency_libs. + for dep in $dependency_libs; do + case "$dep" in + -L*) + dependency_libdir=`echo "X$dep" | sed -e 's/^X-L//'` + dnl Potentially add $dependency_libdir to $LIBNAME and $LTLIBNAME. + dnl But don't add it + dnl 1. if it's the standard /usr/lib, + dnl 2. if it's /usr/local/lib and we are using GCC on Linux, + dnl 3. if it's already present in $LDFLAGS or the already + dnl constructed $LIBNAME, + dnl 4. if it doesn't exist as a directory. + if test "X$dependency_libdir" != "X/usr/$acl_libdirstem" \ + && test "X$dependency_libdir" != "X/usr/$acl_libdirstem2" \ + && test "X$dependency_libdir" != "X/usr/$acl_libdirstem3"; then + haveit= + if test "X$dependency_libdir" = "X/usr/local/$acl_libdirstem" \ + || test "X$dependency_libdir" = "X/usr/local/$acl_libdirstem2" \ + || test "X$dependency_libdir" = "X/usr/local/$acl_libdirstem3"; then + if test -n "$GCC"; then + case $host_os in + linux* | gnu* | k*bsd*-gnu) haveit=yes;; + esac + fi + fi + if test -z "$haveit"; then + haveit= + for x in $LDFLAGS $LIB[]NAME; do + AC_LIB_WITH_FINAL_PREFIX([eval x=\"$x\"]) + if test "X$x" = "X-L$dependency_libdir"; then + haveit=yes + break + fi + done + if test -z "$haveit"; then + if test -d "$dependency_libdir"; then + dnl Really add $dependency_libdir to $LIBNAME. + LIB[]NAME="${LIB[]NAME}${LIB[]NAME:+ }-L$dependency_libdir" + fi + fi + haveit= + for x in $LDFLAGS $LTLIB[]NAME; do + AC_LIB_WITH_FINAL_PREFIX([eval x=\"$x\"]) + if test "X$x" = "X-L$dependency_libdir"; then + haveit=yes + break + fi + done + if test -z "$haveit"; then + if test -d "$dependency_libdir"; then + dnl Really add $dependency_libdir to $LTLIBNAME. + LTLIB[]NAME="${LTLIB[]NAME}${LTLIB[]NAME:+ }-L$dependency_libdir" + fi + fi + fi + fi + ;; + -R*) + dir=`echo "X$dep" | sed -e 's/^X-R//'` + if test "$enable_rpath" != no; then + dnl Potentially add DIR to rpathdirs. + dnl The rpathdirs will be appended to $LIBNAME at the end. + haveit= + for x in $rpathdirs; do + if test "X$x" = "X$dir"; then + haveit=yes + break + fi + done + if test -z "$haveit"; then + rpathdirs="$rpathdirs $dir" + fi + dnl Potentially add DIR to ltrpathdirs. + dnl The ltrpathdirs will be appended to $LTLIBNAME at the end. + haveit= + for x in $ltrpathdirs; do + if test "X$x" = "X$dir"; then + haveit=yes + break + fi + done + if test -z "$haveit"; then + ltrpathdirs="$ltrpathdirs $dir" + fi + fi + ;; + -l*) + dnl Handle this in the next round. + dnl But on GNU systems, ignore -lc options, because + dnl - linking with libc is the default anyway, + dnl - linking with libc.a may produce an error + dnl "/usr/bin/ld: dynamic STT_GNU_IFUNC symbol `strcmp' with pointer equality in `/usr/lib/libc.a(strcmp.o)' can not be used when making an executable; recompile with -fPIE and relink with -pie" + dnl or may produce an executable that always crashes, see + dnl . + dep=`echo "X$dep" | sed -e 's/^X-l//'` + if test "X$dep" != Xc \ + || case $host_os in + linux* | gnu* | k*bsd*-gnu) false ;; + *) true ;; + esac; then + names_next_round="$names_next_round $dep" + fi + ;; + *.la) + dnl Handle this in the next round. Throw away the .la's + dnl directory; it is already contained in a preceding -L + dnl option. + names_next_round="$names_next_round "`echo "X$dep" | sed -e 's,^X.*/,,' -e 's,^lib,,' -e 's,\.la$,,'` + ;; + *) + dnl Most likely an immediate library name. + LIB[]NAME="${LIB[]NAME}${LIB[]NAME:+ }$dep" + LTLIB[]NAME="${LTLIB[]NAME}${LTLIB[]NAME:+ }$dep" + ;; + esac + done + fi + else + dnl Didn't find the library; assume it is in the system directories + dnl known to the linker and runtime loader. (All the system + dnl directories known to the linker should also be known to the + dnl runtime loader, otherwise the system is severely misconfigured.) + LIB[]NAME="${LIB[]NAME}${LIB[]NAME:+ }-l$name" + LTLIB[]NAME="${LTLIB[]NAME}${LTLIB[]NAME:+ }-l$name" + fi + fi + fi + done + done + if test "X$rpathdirs" != "X"; then + if test -n "$acl_hardcode_libdir_separator"; then + dnl Weird platform: only the last -rpath option counts, the user must + dnl pass all path elements in one option. We can arrange that for a + dnl single library, but not when more than one $LIBNAMEs are used. + alldirs= + for found_dir in $rpathdirs; do + alldirs="${alldirs}${alldirs:+$acl_hardcode_libdir_separator}$found_dir" + done + dnl Note: acl_hardcode_libdir_flag_spec uses $libdir and $wl. + acl_saved_libdir="$libdir" + libdir="$alldirs" + eval flag=\"$acl_hardcode_libdir_flag_spec\" + libdir="$acl_saved_libdir" + LIB[]NAME="${LIB[]NAME}${LIB[]NAME:+ }$flag" + else + dnl The -rpath options are cumulative. + for found_dir in $rpathdirs; do + acl_saved_libdir="$libdir" + libdir="$found_dir" + eval flag=\"$acl_hardcode_libdir_flag_spec\" + libdir="$acl_saved_libdir" + LIB[]NAME="${LIB[]NAME}${LIB[]NAME:+ }$flag" + done + fi + fi + if test "X$ltrpathdirs" != "X"; then + dnl When using libtool, the option that works for both libraries and + dnl executables is -R. The -R options are cumulative. + for found_dir in $ltrpathdirs; do + LTLIB[]NAME="${LTLIB[]NAME}${LTLIB[]NAME:+ }-R$found_dir" + done + fi + popdef([PACKLIBS]) + popdef([PACKUP]) + popdef([PACK]) + popdef([NAME]) +]) + +dnl AC_LIB_APPENDTOVAR(VAR, CONTENTS) appends the elements of CONTENTS to VAR, +dnl unless already present in VAR. +dnl Works only for CPPFLAGS, not for LIB* variables because that sometimes +dnl contains two or three consecutive elements that belong together. +AC_DEFUN([AC_LIB_APPENDTOVAR], +[ + for element in [$2]; do + haveit= + for x in $[$1]; do + AC_LIB_WITH_FINAL_PREFIX([eval x=\"$x\"]) + if test "X$x" = "X$element"; then + haveit=yes + break + fi + done + if test -z "$haveit"; then + [$1]="${[$1]}${[$1]:+ }$element" + fi + done +]) + +dnl For those cases where a variable contains several -L and -l options +dnl referring to unknown libraries and directories, this macro determines the +dnl necessary additional linker options for the runtime path. +dnl AC_LIB_LINKFLAGS_FROM_LIBS([LDADDVAR], [LIBSVALUE], [USE-LIBTOOL]) +dnl sets LDADDVAR to linker options needed together with LIBSVALUE. +dnl If USE-LIBTOOL evaluates to non-empty, linking with libtool is assumed, +dnl otherwise linking without libtool is assumed. +AC_DEFUN([AC_LIB_LINKFLAGS_FROM_LIBS], +[ + AC_REQUIRE([AC_LIB_RPATH]) + AC_REQUIRE([AC_LIB_PREPARE_MULTILIB]) + $1= + if test "$enable_rpath" != no; then + if test -n "$acl_hardcode_libdir_flag_spec" && test "$acl_hardcode_minus_L" = no; then + dnl Use an explicit option to hardcode directories into the resulting + dnl binary. + rpathdirs= + next= + for opt in $2; do + if test -n "$next"; then + dir="$next" + dnl No need to hardcode the standard /usr/lib. + if test "X$dir" != "X/usr/$acl_libdirstem" \ + && test "X$dir" != "X/usr/$acl_libdirstem2" \ + && test "X$dir" != "X/usr/$acl_libdirstem3"; then + rpathdirs="$rpathdirs $dir" + fi + next= + else + case $opt in + -L) next=yes ;; + -L*) dir=`echo "X$opt" | sed -e 's,^X-L,,'` + dnl No need to hardcode the standard /usr/lib. + if test "X$dir" != "X/usr/$acl_libdirstem" \ + && test "X$dir" != "X/usr/$acl_libdirstem2" \ + && test "X$dir" != "X/usr/$acl_libdirstem3"; then + rpathdirs="$rpathdirs $dir" + fi + next= ;; + *) next= ;; + esac + fi + done + if test "X$rpathdirs" != "X"; then + if test -n ""$3""; then + dnl libtool is used for linking. Use -R options. + for dir in $rpathdirs; do + $1="${$1}${$1:+ }-R$dir" + done + else + dnl The linker is used for linking directly. + if test -n "$acl_hardcode_libdir_separator"; then + dnl Weird platform: only the last -rpath option counts, the user + dnl must pass all path elements in one option. + alldirs= + for dir in $rpathdirs; do + alldirs="${alldirs}${alldirs:+$acl_hardcode_libdir_separator}$dir" + done + acl_saved_libdir="$libdir" + libdir="$alldirs" + eval flag=\"$acl_hardcode_libdir_flag_spec\" + libdir="$acl_saved_libdir" + $1="$flag" + else + dnl The -rpath options are cumulative. + for dir in $rpathdirs; do + acl_saved_libdir="$libdir" + libdir="$dir" + eval flag=\"$acl_hardcode_libdir_flag_spec\" + libdir="$acl_saved_libdir" + $1="${$1}${$1:+ }$flag" + done + fi + fi + fi + fi + fi + AC_SUBST([$1]) +]) diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/m4/lib-prefix.m4 b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/m4/lib-prefix.m4 new file mode 100644 index 0000000000000000000000000000000000000000..29283534f3fc0e062f872d9f7a6e935223e98903 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/m4/lib-prefix.m4 @@ -0,0 +1,334 @@ +# lib-prefix.m4 +# serial 23 +dnl Copyright (C) 2001-2005, 2008-2025 Free Software Foundation, Inc. +dnl This file is free software; the Free Software Foundation +dnl gives unlimited permission to copy and/or distribute it, +dnl with or without modifications, as long as this notice is preserved. +dnl This file is offered as-is, without any warranty. + +dnl From Bruno Haible. + +dnl AC_LIB_PREFIX adds to the CPPFLAGS and LDFLAGS the flags that are needed +dnl to access previously installed libraries. The basic assumption is that +dnl a user will want packages to use other packages he previously installed +dnl with the same --prefix option. +dnl This macro is not needed if only AC_LIB_LINKFLAGS is used to locate +dnl libraries, but is otherwise very convenient. +AC_DEFUN([AC_LIB_PREFIX], +[ + AC_BEFORE([$0], [AC_LIB_LINKFLAGS]) + AC_REQUIRE([AC_PROG_CC]) + AC_REQUIRE([AC_CANONICAL_HOST]) + AC_REQUIRE([AC_LIB_PREPARE_MULTILIB]) + AC_REQUIRE([AC_LIB_PREPARE_PREFIX]) + dnl By default, look in $includedir and $libdir. + use_additional=yes + AC_LIB_WITH_FINAL_PREFIX([ + eval additional_includedir=\"$includedir\" + eval additional_libdir=\"$libdir\" + ]) + AC_ARG_WITH([lib-prefix], +[[ --with-lib-prefix[=DIR] search for libraries in DIR/include and DIR/lib + --without-lib-prefix don't search for libraries in includedir and libdir]], +[ + if test "X$withval" = "Xno"; then + use_additional=no + else + if test "X$withval" = "X"; then + AC_LIB_WITH_FINAL_PREFIX([ + eval additional_includedir=\"$includedir\" + eval additional_libdir=\"$libdir\" + ]) + else + additional_includedir="$withval/include" + additional_libdir="$withval/$acl_libdirstem" + fi + fi +]) + if test $use_additional = yes; then + dnl Potentially add $additional_includedir to $CPPFLAGS. + dnl But don't add it + dnl 1. if it's the standard /usr/include, + dnl 2. if it's already present in $CPPFLAGS, + dnl 3. if it's /usr/local/include and we are using GCC on Linux, + dnl 4. if it doesn't exist as a directory. + if test "X$additional_includedir" != "X/usr/include"; then + haveit= + for x in $CPPFLAGS; do + AC_LIB_WITH_FINAL_PREFIX([eval x=\"$x\"]) + if test "X$x" = "X-I$additional_includedir"; then + haveit=yes + break + fi + done + if test -z "$haveit"; then + if test "X$additional_includedir" = "X/usr/local/include"; then + if test -n "$GCC"; then + case $host_os in + linux* | gnu* | k*bsd*-gnu) haveit=yes;; + esac + fi + fi + if test -z "$haveit"; then + if test -d "$additional_includedir"; then + dnl Really add $additional_includedir to $CPPFLAGS. + CPPFLAGS="${CPPFLAGS}${CPPFLAGS:+ }-I$additional_includedir" + fi + fi + fi + fi + dnl Potentially add $additional_libdir to $LDFLAGS. + dnl But don't add it + dnl 1. if it's the standard /usr/lib, + dnl 2. if it's already present in $LDFLAGS, + dnl 3. if it's /usr/local/lib and we are using GCC on Linux, + dnl 4. if it doesn't exist as a directory. + if test "X$additional_libdir" != "X/usr/$acl_libdirstem"; then + haveit= + for x in $LDFLAGS; do + AC_LIB_WITH_FINAL_PREFIX([eval x=\"$x\"]) + if test "X$x" = "X-L$additional_libdir"; then + haveit=yes + break + fi + done + if test -z "$haveit"; then + if test "X$additional_libdir" = "X/usr/local/$acl_libdirstem"; then + if test -n "$GCC"; then + case $host_os in + linux*) haveit=yes;; + esac + fi + fi + if test -z "$haveit"; then + if test -d "$additional_libdir"; then + dnl Really add $additional_libdir to $LDFLAGS. + LDFLAGS="${LDFLAGS}${LDFLAGS:+ }-L$additional_libdir" + fi + fi + fi + fi + fi +]) + +dnl AC_LIB_PREPARE_PREFIX creates variables acl_final_prefix, +dnl acl_final_exec_prefix, containing the values to which $prefix and +dnl $exec_prefix will expand at the end of the configure script. +AC_DEFUN([AC_LIB_PREPARE_PREFIX], +[ + dnl Unfortunately, prefix and exec_prefix get only finally determined + dnl at the end of configure. + if test "X$prefix" = "XNONE"; then + acl_final_prefix="$ac_default_prefix" + else + acl_final_prefix="$prefix" + fi + if test "X$exec_prefix" = "XNONE"; then + acl_final_exec_prefix='${prefix}' + else + acl_final_exec_prefix="$exec_prefix" + fi + acl_saved_prefix="$prefix" + prefix="$acl_final_prefix" + eval acl_final_exec_prefix=\"$acl_final_exec_prefix\" + prefix="$acl_saved_prefix" +]) + +dnl AC_LIB_WITH_FINAL_PREFIX([statement]) evaluates statement, with the +dnl variables prefix and exec_prefix bound to the values they will have +dnl at the end of the configure script. +AC_DEFUN([AC_LIB_WITH_FINAL_PREFIX], +[ + acl_saved_prefix="$prefix" + prefix="$acl_final_prefix" + acl_saved_exec_prefix="$exec_prefix" + exec_prefix="$acl_final_exec_prefix" + $1 + exec_prefix="$acl_saved_exec_prefix" + prefix="$acl_saved_prefix" +]) + +dnl AC_LIB_PREPARE_MULTILIB creates +dnl - a function acl_is_expected_elfclass, that tests whether standard input +dn; has a 32-bit or 64-bit ELF header, depending on the host CPU ABI, +dnl - 3 variables acl_libdirstem, acl_libdirstem2, acl_libdirstem3, containing +dnl the basename of the libdir to try in turn, either "lib" or "lib64" or +dnl "lib/64" or "lib32" or "lib/sparcv9" or "lib/amd64" or similar. +AC_DEFUN([AC_LIB_PREPARE_MULTILIB], +[ + dnl There is no formal standard regarding lib, lib32, and lib64. + dnl On most glibc systems, the current practice is that on a system supporting + dnl 32-bit and 64-bit instruction sets or ABIs, 64-bit libraries go under + dnl $prefix/lib64 and 32-bit libraries go under $prefix/lib. However, on + dnl Arch Linux based distributions, it's the opposite: 32-bit libraries go + dnl under $prefix/lib32 and 64-bit libraries go under $prefix/lib. + dnl We determine the compiler's default mode by looking at the compiler's + dnl library search path. If at least one of its elements ends in /lib64 or + dnl points to a directory whose absolute pathname ends in /lib64, we use that + dnl for 64-bit ABIs. Similarly for 32-bit ABIs. Otherwise we use the default, + dnl namely "lib". + dnl On Solaris systems, the current practice is that on a system supporting + dnl 32-bit and 64-bit instruction sets or ABIs, 64-bit libraries go under + dnl $prefix/lib/64 (which is a symlink to either $prefix/lib/sparcv9 or + dnl $prefix/lib/amd64) and 32-bit libraries go under $prefix/lib. + AC_REQUIRE([AC_CANONICAL_HOST]) + AC_REQUIRE([gl_HOST_CPU_C_ABI_32BIT]) + + AC_CACHE_CHECK([for ELF binary format], [gl_cv_elf], + [AC_EGREP_CPP([Extensible Linking Format], + [#if defined __ELF__ || (defined __linux__ && (defined __EDG__ || defined __SUNPRO_C)) + Extensible Linking Format + #endif + ], + [gl_cv_elf=yes], + [gl_cv_elf=no]) + ]) + if test $gl_cv_elf = yes; then + # Extract the ELF class of a file (5th byte) in decimal. + # Cf. https://en.wikipedia.org/wiki/Executable_and_Linkable_Format#File_header + if od -A x < /dev/null >/dev/null 2>/dev/null; then + # Use POSIX od. + func_elfclass () + { + od -A n -t d1 -j 4 -N 1 + } + else + # Use BSD hexdump. + func_elfclass () + { + dd bs=1 count=1 skip=4 2>/dev/null | hexdump -e '1/1 "%3d "' + echo + } + fi + # Use 'expr', not 'test', to compare the values of func_elfclass, because on + # Solaris 11 OpenIndiana and Solaris 11 OmniOS, the result is 001 or 002, + # not 1 or 2. +changequote(,)dnl + case $HOST_CPU_C_ABI_32BIT in + yes) + # 32-bit ABI. + acl_is_expected_elfclass () + { + expr "`func_elfclass | sed -e 's/[ ]//g'`" = 1 > /dev/null + } + ;; + no) + # 64-bit ABI. + acl_is_expected_elfclass () + { + expr "`func_elfclass | sed -e 's/[ ]//g'`" = 2 > /dev/null + } + ;; + *) + # Unknown. + acl_is_expected_elfclass () + { + : + } + ;; + esac +changequote([,])dnl + else + acl_is_expected_elfclass () + { + : + } + fi + + dnl Allow the user to override the result by setting acl_cv_libdirstems. + AC_CACHE_CHECK([for the common suffixes of directories in the library search path], + [acl_cv_libdirstems], + [dnl Try 'lib' first, because that's the default for libdir in GNU, see + dnl . + acl_libdirstem=lib + acl_libdirstem2= + acl_libdirstem3= + case "$host_os" in + solaris*) + dnl See Solaris 10 Software Developer Collection > Solaris 64-bit Developer's Guide > The Development Environment + dnl . + dnl "Portable Makefiles should refer to any library directories using the 64 symbolic link." + dnl But we want to recognize the sparcv9 or amd64 subdirectory also if the + dnl symlink is missing, so we set acl_libdirstem2 too. + if test $HOST_CPU_C_ABI_32BIT = no; then + acl_libdirstem2=lib/64 + case "$host_cpu" in + sparc*) acl_libdirstem3=lib/sparcv9 ;; + i*86 | x86_64) acl_libdirstem3=lib/amd64 ;; + esac + fi + ;; + netbsd*) + dnl On NetBSD/sparc64, there is a 'sparc' subdirectory that contains + dnl 32-bit libraries. + if test $HOST_CPU_C_ABI_32BIT != no; then + case "$host_cpu" in + sparc*) acl_libdirstem2=lib/sparc ;; + esac + fi + ;; + *) + dnl If $CC generates code for a 32-bit ABI, the libraries are + dnl surely under $prefix/lib or $prefix/lib32, not $prefix/lib64. + dnl Similarly, if $CC generates code for a 64-bit ABI, the libraries + dnl are surely under $prefix/lib or $prefix/lib64, not $prefix/lib32. + dnl Find the compiler's search path. However, non-system compilers + dnl sometimes have odd library search paths. But we can't simply invoke + dnl '/usr/bin/gcc -print-search-dirs' because that would not take into + dnl account the -m32/-m31 or -m64 options from the $CC or $CFLAGS. + searchpath=`(LC_ALL=C $CC $CPPFLAGS $CFLAGS -print-search-dirs) 2>/dev/null \ + | sed -n -e 's,^libraries: ,,p' | sed -e 's,^=,,'` + if test $HOST_CPU_C_ABI_32BIT != no; then + # 32-bit or unknown ABI. + if test -d /usr/lib32; then + acl_libdirstem2=lib32 + fi + fi + if test $HOST_CPU_C_ABI_32BIT != yes; then + # 64-bit or unknown ABI. + if test -d /usr/lib64; then + acl_libdirstem3=lib64 + fi + fi + if test -n "$searchpath"; then + acl_saved_IFS="${IFS= }"; IFS=":" + for searchdir in $searchpath; do + if test -d "$searchdir"; then + case "$searchdir" in + */lib32/ | */lib32 ) acl_libdirstem2=lib32 ;; + */lib64/ | */lib64 ) acl_libdirstem3=lib64 ;; + */../ | */.. ) + # Better ignore directories of this form. They are misleading. + ;; + *) searchdir=`cd "$searchdir" && pwd` + case "$searchdir" in + */lib32 ) acl_libdirstem2=lib32 ;; + */lib64 ) acl_libdirstem3=lib64 ;; + esac ;; + esac + fi + done + IFS="$acl_saved_IFS" + if test $HOST_CPU_C_ABI_32BIT = yes; then + # 32-bit ABI. + acl_libdirstem3= + fi + if test $HOST_CPU_C_ABI_32BIT = no; then + # 64-bit ABI. + acl_libdirstem2= + fi + fi + ;; + esac + test -n "$acl_libdirstem2" || acl_libdirstem2="$acl_libdirstem" + test -n "$acl_libdirstem3" || acl_libdirstem3="$acl_libdirstem" + acl_cv_libdirstems="$acl_libdirstem,$acl_libdirstem2,$acl_libdirstem3" + ]) + dnl Decompose acl_cv_libdirstems into acl_libdirstem, acl_libdirstem2, and + dnl acl_libdirstem3. +changequote(,)dnl + acl_libdirstem=`echo "$acl_cv_libdirstems" | sed -e 's/,.*//'` + acl_libdirstem2=`echo "$acl_cv_libdirstems" | sed -e 's/^[^,]*,//' -e 's/,.*//'` + acl_libdirstem3=`echo "$acl_cv_libdirstems" | sed -e 's/^[^,]*,[^,]*,//' -e 's/,.*//'` +changequote([,])dnl +]) diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/m4/nls.m4 b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/m4/nls.m4 new file mode 100644 index 0000000000000000000000000000000000000000..c4601415bb5589537a6e2e8816e5383536ca6e4c --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/m4/nls.m4 @@ -0,0 +1,33 @@ +# nls.m4 +# serial 6 (gettext-0.24) +dnl Copyright (C) 1995-2025 Free Software Foundation, Inc. +dnl This file is free software; the Free Software Foundation +dnl gives unlimited permission to copy and/or distribute it, +dnl with or without modifications, as long as this notice is preserved. +dnl This file is offered as-is, without any warranty. +dnl +dnl This file can be used in projects which are not available under +dnl the GNU General Public License or the GNU Lesser General Public +dnl License but which still want to provide support for the GNU gettext +dnl functionality. +dnl Please note that the actual code of the GNU gettext library is covered +dnl by the GNU Lesser General Public License, and the rest of the GNU +dnl gettext package is covered by the GNU General Public License. +dnl They are *not* in the public domain. + +dnl Authors: +dnl Ulrich Drepper , 1995-2000. +dnl Bruno Haible , 2000-2003. + +AC_PREREQ([2.50]) + +AC_DEFUN([AM_NLS], +[ + AC_MSG_CHECKING([whether NLS is requested]) + dnl Default is enabled NLS + AC_ARG_ENABLE([nls], + [ --disable-nls do not use Native Language Support], + USE_NLS=$enableval, USE_NLS=yes) + AC_MSG_RESULT([$USE_NLS]) + AC_SUBST([USE_NLS]) +]) diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/m4/po.m4 b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/m4/po.m4 new file mode 100644 index 0000000000000000000000000000000000000000..73e0436bd72f3110892b9a30cf6bdbd7862cf891 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/m4/po.m4 @@ -0,0 +1,157 @@ +# po.m4 +# serial 34 (gettext-0.24) +dnl Copyright (C) 1995-2024 Free Software Foundation, Inc. +dnl This file is free software; the Free Software Foundation +dnl gives unlimited permission to copy and/or distribute it, +dnl with or without modifications, as long as this notice is preserved. +dnl This file is offered as-is, without any warranty. +dnl +dnl This file can be used in projects which are not available under +dnl the GNU General Public License or the GNU Lesser General Public +dnl License but which still want to provide support for the GNU gettext +dnl functionality. +dnl Please note that the actual code of the GNU gettext library is covered +dnl by the GNU Lesser General Public License, and the rest of the GNU +dnl gettext package is covered by the GNU General Public License. +dnl They are *not* in the public domain. + +dnl Authors: +dnl Ulrich Drepper , 1995-2000. +dnl Bruno Haible , 2000-2024. + +AC_PREREQ([2.60]) + +dnl Checks for all prerequisites of the po subdirectory. +AC_DEFUN([AM_PO_SUBDIRS], +[ + AC_REQUIRE([AC_PROG_MAKE_SET])dnl + AC_REQUIRE([AC_PROG_INSTALL])dnl + AC_REQUIRE([AC_PROG_MKDIR_P])dnl + AC_REQUIRE([AC_PROG_SED])dnl + AC_REQUIRE([AM_NLS])dnl + + dnl Release version of the gettext macros. This is used to ensure that + dnl the gettext macros and po/Makefile.in.in are in sync. + AC_SUBST([GETTEXT_MACRO_VERSION], [0.24]) + + dnl Perform the following tests also if --disable-nls has been given, + dnl because they are needed for "make dist" to work. + + dnl Search for GNU msgfmt in the PATH. + dnl The first test excludes Solaris msgfmt and early GNU msgfmt versions. + dnl The second test excludes FreeBSD msgfmt. + AM_PATH_PROG_WITH_TEST(MSGFMT, msgfmt, + [$ac_dir/$ac_word --statistics /dev/null >&]AS_MESSAGE_LOG_FD[ 2>&1 && + (if $ac_dir/$ac_word --statistics /dev/null 2>&1 >/dev/null | grep usage >/dev/null; then exit 1; else exit 0; fi)], + :) + AC_PATH_PROG([GMSGFMT], [gmsgfmt], [$MSGFMT]) + + dnl Test whether it is GNU msgfmt >= 0.15. +changequote(,)dnl + case `$GMSGFMT --version | sed 1q | sed -e 's,^[^0-9]*,,'` in + '' | 0.[0-9] | 0.[0-9].* | 0.1[0-4] | 0.1[0-4].*) GMSGFMT_015=: ;; + *) GMSGFMT_015=$GMSGFMT ;; + esac +changequote([,])dnl + AC_SUBST([GMSGFMT_015]) + + dnl Search for GNU xgettext 0.12 or newer in the PATH. + dnl The first test excludes Solaris xgettext and early GNU xgettext versions. + dnl The second test excludes FreeBSD xgettext. + AM_PATH_PROG_WITH_TEST(XGETTEXT, xgettext, + [$ac_dir/$ac_word --omit-header --copyright-holder= --msgid-bugs-address= /dev/null >&]AS_MESSAGE_LOG_FD[ 2>&1 && + (if $ac_dir/$ac_word --omit-header --copyright-holder= --msgid-bugs-address= /dev/null 2>&1 >/dev/null | grep usage >/dev/null; then exit 1; else exit 0; fi)], + :) + dnl Remove leftover from FreeBSD xgettext call. + rm -f messages.po + + dnl Test whether it is GNU xgettext >= 0.15. +changequote(,)dnl + case `$XGETTEXT --version | sed 1q | sed -e 's,^[^0-9]*,,'` in + '' | 0.[0-9] | 0.[0-9].* | 0.1[0-4] | 0.1[0-4].*) XGETTEXT_015=: ;; + *) XGETTEXT_015=$XGETTEXT ;; + esac +changequote([,])dnl + AC_SUBST([XGETTEXT_015]) + + dnl Search for GNU msgmerge 0.11 or newer in the PATH. + AM_PATH_PROG_WITH_TEST(MSGMERGE, msgmerge, + [$ac_dir/$ac_word --update -q /dev/null /dev/null >&]AS_MESSAGE_LOG_FD[ 2>&1], :) + + dnl Test whether it is GNU msgmerge >= 0.20. + if LC_ALL=C $MSGMERGE --help | grep ' --for-msgfmt ' >/dev/null; then + MSGMERGE_FOR_MSGFMT_OPTION='--for-msgfmt' + else + dnl Test whether it is GNU msgmerge >= 0.12. + if LC_ALL=C $MSGMERGE --help | grep ' --no-fuzzy-matching ' >/dev/null; then + MSGMERGE_FOR_MSGFMT_OPTION='--no-fuzzy-matching --no-location --quiet' + else + dnl With these old versions, $(MSGMERGE) $(MSGMERGE_FOR_MSGFMT_OPTION) is + dnl slow. But this is not a big problem, as such old gettext versions are + dnl hardly in use any more. + MSGMERGE_FOR_MSGFMT_OPTION='--no-location --quiet' + fi + fi + AC_SUBST([MSGMERGE_FOR_MSGFMT_OPTION]) + + dnl Support for AM_XGETTEXT_OPTION. + test -n "${XGETTEXT_EXTRA_OPTIONS+set}" || XGETTEXT_EXTRA_OPTIONS= + AC_SUBST([XGETTEXT_EXTRA_OPTIONS]) + + if test -n "$ALL_LINGUAS"; then + test -n "$as_me" && echo "$as_me: setting ALL_LINGUAS in configure.in is obsolete" || echo "setting ALL_LINGUAS in configure.in is obsolete" + fi + + dnl Capture the value of LINGUAS because we need it to compute CATALOGS. + dnl In the Makefile, call it DESIRED_LINGUAS (because there, LINGUAS denotes + dnl the set of available translations, given by the developer). + DESIRED_LINGUAS="${LINGUAS-\$(ALL_LINGUAS)}" + AC_SUBST([DESIRED_LINGUAS]) + + AC_CONFIG_COMMANDS([po-directories], [[ + for ac_file in $CONFIG_FILES; do + # Support "outfile[:infile[:infile...]]" + case "$ac_file" in + *:*) ac_file=`echo "$ac_file"|sed 's%:.*%%'` ;; + esac + # PO directories have a Makefile.in generated from Makefile.in.in. + case "$ac_file" in */Makefile.in) + # Adjust a relative srcdir. + ac_dir=`echo "$ac_file"|sed 's%/[^/][^/]*$%%'` + ac_dir_suffix=/`echo "$ac_dir"|sed 's%^\./%%'` + ac_dots=`echo "$ac_dir_suffix"|sed 's%/[^/]*%../%g'` + # In autoconf-2.13 it is called $ac_given_srcdir. + # In autoconf-2.50 it is called $srcdir. + test -n "$ac_given_srcdir" || ac_given_srcdir="$srcdir" + # Treat a directory as a PO directory if and only if it has a + # POTFILES.in file. This allows packages to have multiple PO + # directories under different names or in different locations. + if test -f "$ac_given_srcdir/$ac_dir/POTFILES.in"; then + test -n "$as_me" && echo "$as_me: creating $ac_dir/Makefile" || echo "creating $ac_dir/Makefile" + cat "$ac_dir/Makefile.in" > "$ac_dir/Makefile" + fi + ;; + esac + done]], + []) +]) + +dnl Postprocesses a Makefile in a directory containing PO files. +AC_DEFUN([AM_POSTPROCESS_PO_MAKEFILE], +[ + sed -e 's,^#distdir:,distdir:,' < "$ac_file" > "$ac_file.tmp" + mv "$ac_file.tmp" "$ac_file" +]) + +dnl Initializes the accumulator used by AM_XGETTEXT_OPTION. +AC_DEFUN([AM_XGETTEXT_OPTION_INIT], +[ + XGETTEXT_EXTRA_OPTIONS= +]) + +dnl Registers an option to be passed to xgettext in the po subdirectory. +AC_DEFUN([AM_XGETTEXT_OPTION], +[ + AC_REQUIRE([AM_XGETTEXT_OPTION_INIT]) + XGETTEXT_EXTRA_OPTIONS="$XGETTEXT_EXTRA_OPTIONS $1" +]) diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/m4/progtest.m4 b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/m4/progtest.m4 new file mode 100644 index 0000000000000000000000000000000000000000..2671eb856edf706e3bb861607a07da24cf91be2b --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/m4/progtest.m4 @@ -0,0 +1,93 @@ +# progtest.m4 +# serial 10 (gettext-0.24) +dnl Copyright (C) 1996-2025 Free Software Foundation, Inc. +dnl This file is free software; the Free Software Foundation +dnl gives unlimited permission to copy and/or distribute it, +dnl with or without modifications, as long as this notice is preserved. +dnl This file is offered as-is, without any warranty. +dnl +dnl This file can be used in projects which are not available under +dnl the GNU General Public License or the GNU Lesser General Public +dnl License but which still want to provide support for the GNU gettext +dnl functionality. +dnl Please note that the actual code of the GNU gettext library is covered +dnl by the GNU Lesser General Public License, and the rest of the GNU +dnl gettext package is covered by the GNU General Public License. +dnl They are *not* in the public domain. + +dnl Authors: +dnl Ulrich Drepper , 1996. + +AC_PREREQ([2.53]) + +# Search path for a program which passes the given test. + +dnl AM_PATH_PROG_WITH_TEST(VARIABLE, PROG-TO-CHECK-FOR, +dnl TEST-PERFORMED-ON-FOUND_PROGRAM [, VALUE-IF-NOT-FOUND [, PATH]]) +AC_DEFUN([AM_PATH_PROG_WITH_TEST], +[ +# Prepare PATH_SEPARATOR. +# The user is always right. +if test "${PATH_SEPARATOR+set}" != set; then + # Determine PATH_SEPARATOR by trying to find /bin/sh in a PATH which + # contains only /bin. Note that ksh looks also at the FPATH variable, + # so we have to set that as well for the test. + PATH_SEPARATOR=: + (PATH='/bin;/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 \ + && { (PATH='/bin:/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 \ + || PATH_SEPARATOR=';' + } +fi + +# Find out how to test for executable files. Don't use a zero-byte file, +# as systems may use methods other than mode bits to determine executability. +cat >conf$$.file <<_ASEOF +#! /bin/sh +exit 0 +_ASEOF +chmod +x conf$$.file +if test -x conf$$.file >/dev/null 2>&1; then + ac_executable_p="test -x" +else + ac_executable_p="test -f" +fi +rm -f conf$$.file + +# Extract the first word of "$2", so it can be a program name with args. +set dummy $2; ac_word=[$]2 +AC_MSG_CHECKING([for $ac_word]) +AC_CACHE_VAL([ac_cv_path_$1], +[case "[$]$1" in + [[\\/]]* | ?:[[\\/]]*) + ac_cv_path_$1="[$]$1" # Let the user override the test with a path. + ;; + *) + gt_saved_IFS="$IFS"; IFS=$PATH_SEPARATOR + for ac_dir in m4_if([$5], , $PATH, [$5]); do + IFS="$gt_saved_IFS" + test -z "$ac_dir" && ac_dir=. + for ac_exec_ext in '' $ac_executable_extensions; do + if $ac_executable_p "$ac_dir/$ac_word$ac_exec_ext"; then + echo "$as_me: trying $ac_dir/$ac_word..." >&AS_MESSAGE_LOG_FD + if [$3]; then + ac_cv_path_$1="$ac_dir/$ac_word$ac_exec_ext" + break 2 + fi + fi + done + done + IFS="$gt_saved_IFS" +dnl If no 4th arg is given, leave the cache variable unset, +dnl so AC_PATH_PROGS will keep looking. +m4_if([$4], , , [ test -z "[$]ac_cv_path_$1" && ac_cv_path_$1="$4" +])dnl + ;; +esac])dnl +$1="$ac_cv_path_$1" +if test m4_if([$4], , [-n "[$]$1"], ["[$]$1" != "$4"]); then + AC_MSG_RESULT([$][$1]) +else + AC_MSG_RESULT([no]) +fi +AC_SUBST([$1])dnl +]) diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/msgunfmt.tcl b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/msgunfmt.tcl new file mode 100644 index 0000000000000000000000000000000000000000..ef32112478d07bc08a785f74c4eac715eeb36c22 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/msgunfmt.tcl @@ -0,0 +1,82 @@ +# Reading tcl/msgcat .msg files. +# Copyright (C) 2002-2024 Free Software Foundation, Inc. +# +# 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 . + +namespace eval msgcat { + namespace export mcset mcdump + variable header "" +} + +proc msgcat::puts_po_string {str} { + # Replace " with \" + regsub -all "\"" $str "\\\"" str + # Replace \ with \\ + regsub -all "\\\\" $str "\\\\\\" str + # Replace newline with \n + regsub -all [subst "\n"] $str "\\n" str + regsub -all [subst "\a"] $str "\\a" str + regsub -all [subst "\b"] $str "\\b" str + regsub -all [subst "\f"] $str "\\f" str + regsub -all [subst "\r"] $str "\\r" str + regsub -all [subst "\t"] $str "\\t" str + regsub -all [subst "\v"] $str "\\v" str + # Output it. + puts -nonewline "\"$str\"" +} + +proc msgcat::write_po_message {msgid msgstr} { + puts -nonewline "msgid " + puts_po_string $msgid + puts "" + puts -nonewline "msgstr " + puts_po_string $msgstr + puts "" + puts "" +} + +# This gets called once for each message in the .msg catalog. +proc msgcat::mcset {locale src {dest ""}} { + msgcat::write_po_message $src $dest +} + +# Main function. +proc msgcat::mcdump {langfile} { + if {[file exists $langfile]} { + # msgunfmt expects the output in UTF-8 encoding. + fconfigure stdout -encoding utf-8 + + set ::msgcat::header "" + + set fd [open $langfile r] + # In newer tcl versions, the .msg files are in UTF-8 encoding. + fconfigure $fd -encoding utf-8 + eval [read $fd] + close $fd + + if {$::msgcat::header == ""} { + # Provide a minimal header. + set ::msgcat::header [subst "MIME-Version: 1.0\nContent-Type: text/plain; charset=UTF-8\nContent-Transfer-Encoding: 8bit\n"] + } + msgcat::write_po_message "" $::msgcat::header + } else { + # Tell msgunfmt to emit an internationalized error message. + exit 2 + } +} + +# Main code: call the main function on the first and only argument. +msgcat::mcdump [lindex $argv 0] + +exit 0 diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/po/Makefile.in.in b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/po/Makefile.in.in new file mode 100644 index 0000000000000000000000000000000000000000..4651c6a9ce092189cd14269badc8215a5454c877 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/po/Makefile.in.in @@ -0,0 +1,580 @@ +# Makefile for PO directory in any package using GNU gettext. +# Copyright (C) 1995-2000 Ulrich Drepper +# Copyright (C) 2000-2025 Free Software Foundation, Inc. +# +# Copying and distribution of this file, with or without modification, +# are permitted in any medium without royalty provided the copyright +# notice and this notice are preserved. This file is offered as-is, +# without any warranty. +# +# Origin: gettext-0.25 +GETTEXT_MACRO_VERSION = 0.24 + +# This Makefile makes use of the variable assignment operator != standardized +# by POSIX:2024 +# . +# It thus requires a 'make' implementation that supports this operator !=. +# As of 2024, these are: GNU make >= 4.0, FreeBSD make, NetBSD make, +# OpenBSD make. This means that building on specific platforms requires +# use of GNU make: +# - On macOS, use /opt/homebrew/bin/gmake. +# - On Solaris 11 OpenIndiana, use /usr/bin/gmake = /usr/gnu/bin/make. +# - On Solaris 11.4, install GNU make yourself. +# - On AIX, use /opt/freeware/bin/make. + +PACKAGE = @PACKAGE@ +VERSION = @VERSION@ +PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@ + +SED = @SED@ +SHELL = /bin/sh +@SET_MAKE@ + +srcdir = @srcdir@ +top_srcdir = @top_srcdir@ +VPATH = @srcdir@ + +prefix = @prefix@ +exec_prefix = @exec_prefix@ +datarootdir = @datarootdir@ +datadir = @datadir@ +localedir = @localedir@ +gettextsrcdir = $(datadir)/gettext/po + +INSTALL = @INSTALL@ +INSTALL_DATA = @INSTALL_DATA@ + +# We use $(mkdir_p). +# In automake <= 1.9.x, $(mkdir_p) is defined either as "mkdir -p --" or as +# "$(mkinstalldirs)" or as "$(install_sh) -d". For these automake versions, +# @install_sh@ does not start with $(SHELL), so we add it. +# In automake >= 1.10, @mkdir_p@ is derived from ${MKDIR_P}, which is defined +# either as "/path/to/mkdir -p" or ".../install-sh -c -d". For these automake +# versions, $(mkinstalldirs) and $(install_sh) are unused. +mkinstalldirs = $(SHELL) @install_sh@ -d +install_sh = $(SHELL) @install_sh@ +MKDIR_P = @MKDIR_P@ +mkdir_p = @mkdir_p@ + +# When building gettext-tools, we prefer to use the built programs +# rather than installed programs. However, we can't do that when we +# are cross compiling. +CROSS_COMPILING = @CROSS_COMPILING@ + +GMSGFMT_ = @GMSGFMT@ +GMSGFMT_no = @GMSGFMT@ +GMSGFMT_yes = @GMSGFMT_015@ +GMSGFMT = $(GMSGFMT_$(USE_MSGCTXT)) +XGETTEXT_ = @XGETTEXT@ +XGETTEXT_no = @XGETTEXT@ +XGETTEXT_yes = @XGETTEXT_015@ +XGETTEXT = $(XGETTEXT_$(USE_MSGCTXT)) +MSGMERGE = @MSGMERGE@ +MSGMERGE_UPDATE = @MSGMERGE@ --update +MSGMERGE_FOR_MSGFMT_OPTION = @MSGMERGE_FOR_MSGFMT_OPTION@ +MSGINIT = msginit +MSGCONV = msgconv +MSGFILTER = msgfilter + +# The list of files which contain translatable strings. +POTFILES != sed -e '/^\#/d' < $(srcdir)/POTFILES.in +# This is computed as $(foreach file, $(POTFILES), $(top_srcdir)/$(file)) +POTFILES_DEPS != for file in $(POTFILES); do echo $(top_srcdir)/$$file; done + +# The set of available translations. +ALL_LINGUAS != if test -f $(srcdir)/LINGUAS; then \ + sed -e '/^\#/d' < $(srcdir)/LINGUAS; \ + else \ + echo $(LINGUAS); \ + fi +# This is computed as $(foreach lang, $(ALL_LINGUAS), $(srcdir)/$(lang).po) +POFILES != for lang in $(ALL_LINGUAS); do echo $(srcdir)/$$lang.po; done +# This is computed as $(foreach lang, $(ALL_LINGUAS), $(srcdir)/$(lang).gmo) +GMOFILES != for lang in $(ALL_LINGUAS); do echo $(srcdir)/$$lang.gmo; done +# This is computed as $(foreach lang, $(ALL_LINGUAS), $(lang).po-update) +UPDATEPOFILES != for lang in $(ALL_LINGUAS); do echo $$lang.po-update; done +# This is computed as $(foreach lang, $(ALL_LINGUAS), $(lang).nop) +DUMMYPOFILES != for lang in $(ALL_LINGUAS); do echo $$lang.nop; done + +DISTFILES.common = \ + Makefile.in.in remove-potcdate.sed \ + $(DISTFILES.common.extra1) $(DISTFILES.common.extra2) \ + $(DISTFILES.common.extra3) $(DISTFILES.common.extra4) \ + $(DISTFILES.common.extra5) $(DISTFILES.common.extra6) +DISTFILES = \ + $(DISTFILES.common) \ + Makevars POTFILES.in \ + $(POFILES) $(GMOFILES) \ + $(DISTFILES.extra1) $(DISTFILES.extra2) \ + $(DISTFILES.extra3) $(DISTFILES.extra4) \ + $(DISTFILES.extra5) $(DISTFILES.extra6) + +# The set of desired translations, as specified by the installer or distributor. +DESIRED_LINGUAS = @DESIRED_LINGUAS@ +# The set of translations to install. This is computed based on $(ALL_LINGUAS) +# and $(DESIRED_LINGUAS). It is a subset of $(ALL_LINGUAS). +# We use the presentlang catalog if desiredlang is +# a. equal to presentlang, or +# b. a variant of presentlang (because in this case, presentlang can be used +# as a fallback for messages which are not translated in the desiredlang +# catalog). +INST_LINGUAS != for presentlang in $(ALL_LINGUAS); do \ + useit=false; \ + for desiredlang in $(DESIRED_LINGUAS); do \ + case "$$desiredlang" in \ + "$$presentlang" | "$$presentlang"_* | "$$presentlang".* | "$$presentlang"@*) \ + useit=true ;; \ + esac; \ + done; \ + if $$useit; then echo $$presentlang; fi; \ + done +# This is computed as $(foreach lang, $(INST_LINGUAS), $(lang).gmo) +CATALOGS != for lang in $(INST_LINGUAS); do echo $$lang.gmo; done + +POFILESDEPS_ = $(srcdir)/$(DOMAIN).pot +POFILESDEPS_yes = $(POFILESDEPS_) +POFILESDEPS_no = +POFILESDEPS = $(POFILESDEPS_$(PO_DEPENDS_ON_POT)) + +DISTFILESDEPS_ = update-po +DISTFILESDEPS_yes = $(DISTFILESDEPS_) +DISTFILESDEPS_no = +DISTFILESDEPS = $(DISTFILESDEPS_$(DIST_DEPENDS_ON_UPDATE_PO)) + +# Include the customization of this po/ directory. +include $(srcdir)/Makevars + +all: all-@USE_NLS@ + + +.SUFFIXES: +.SUFFIXES: .po .gmo .nop .po-create .po-update + +# The .pot file, stamp-po, .po files, and .gmo files appear in release tarballs. +# The GNU Coding Standards say in +# : +# "GNU distributions usually contain some files which are not source files +# ... . Since these files normally appear in the source directory, they +# should always appear in the source directory, not in the build directory. +# So Makefile rules to update them should put the updated files in the +# source directory." +# Therefore we put these files in the source directory, not the build directory. + +# During .po -> .gmo conversion, take into account the most recent changes to +# the .pot file. This eliminates the need to update the .po files when the +# .pot file has changed, which would be troublesome if the .po files are put +# under version control. +$(GMOFILES): $(srcdir)/$(DOMAIN).pot +.po.gmo: + @lang=`echo $* | sed -e 's,.*/,,'`; \ + if test "$(PACKAGE)" = "gettext-tools" && test "$(CROSS_COMPILING)" != "yes"; then PATH=`pwd`/../src:$$PATH; fi; \ + test "$(srcdir)" = . && cdcmd="" || cdcmd="cd $(srcdir) && "; \ + echo "$${cdcmd}rm -f $${lang}.gmo && $(MSGMERGE) $(MSGMERGE_FOR_MSGFMT_OPTION) -o $${lang}.1po $${lang}.po $(DOMAIN).pot && $(GMSGFMT) -c --statistics --verbose -o $${lang}.gmo $${lang}.1po && rm -f $${lang}.1po"; \ + cd $(srcdir) && \ + rm -f $${lang}.gmo && \ + $(MSGMERGE) $(MSGMERGE_FOR_MSGFMT_OPTION) -o $${lang}.1po $${lang}.po $(DOMAIN).pot && \ + $(GMSGFMT) -c --statistics --verbose -o t-$${lang}.gmo $${lang}.1po && \ + mv t-$${lang}.gmo $${lang}.gmo && \ + rm -f $${lang}.1po + + +all-yes: $(srcdir)/stamp-po +all-no: + +# Ensure that the gettext macros and this Makefile.in.in are in sync. +CHECK_MACRO_VERSION = \ + test "$(GETTEXT_MACRO_VERSION)" = "@GETTEXT_MACRO_VERSION@" \ + || { echo "*** error: gettext infrastructure mismatch: using a Makefile.in.in from gettext version $(GETTEXT_MACRO_VERSION) but the autoconf macros are from gettext version @GETTEXT_MACRO_VERSION@" 1>&2; \ + exit 1; \ + } + +# $(srcdir)/$(DOMAIN).pot is only created when needed. When xgettext finds no +# internationalized messages, no $(srcdir)/$(DOMAIN).pot is created (because +# we don't want to bother translators with empty POT files). We assume that +# LINGUAS is empty in this case, i.e. $(POFILES) and $(GMOFILES) are empty. +# In this case, $(srcdir)/stamp-po is a nop (i.e. a phony target). + +# $(srcdir)/stamp-po is a timestamp denoting the last time at which the CATALOGS +# have been loosely updated. Its purpose is that when a developer or translator +# checks out the package from a version control system, and the $(DOMAIN).pot +# file is not under version control, "make" will update the $(DOMAIN).pot and +# the $(CATALOGS), but subsequent invocations of "make" will do nothing. This +# timestamp would not be necessary if updating the $(CATALOGS) would always +# touch them; however, the rule for $(POFILES) has been designed to not touch +# files that don't need to be changed. +$(srcdir)/stamp-po: $(srcdir)/$(DOMAIN).pot + @$(CHECK_MACRO_VERSION) + test ! -f $(srcdir)/$(DOMAIN).pot || \ + test -z "$(GMOFILES)" || $(MAKE) $(GMOFILES) + @test ! -f $(srcdir)/$(DOMAIN).pot || { \ + echo "touch $(srcdir)/stamp-po" && \ + echo timestamp > $(srcdir)/stamp-poT && \ + mv $(srcdir)/stamp-poT $(srcdir)/stamp-po; \ + } + +# This target rebuilds $(DOMAIN).pot; it is an expensive operation. +# Note that $(DOMAIN).pot is not touched if it doesn't need to be changed. +# The determination of whether the package xyz is a GNU one is based on the +# heuristic whether some file in the top level directory mentions "GNU xyz". +# If GNU 'find' is available, we avoid grepping through monster files. +$(DOMAIN).pot-update: $(POTFILES_DEPS) $(srcdir)/POTFILES.in + package_gnu="$(PACKAGE_GNU)"; \ + test -n "$$package_gnu" || { \ + if { if (LC_ALL=C find --version) 2>/dev/null | grep GNU >/dev/null; then \ + LC_ALL=C find -L $(top_srcdir) -maxdepth 1 -type f -size -10000000c -exec grep -i 'GNU @PACKAGE@' /dev/null '{}' ';' 2>/dev/null; \ + else \ + LC_ALL=C grep -i 'GNU @PACKAGE@' $(top_srcdir)/* 2>/dev/null; \ + fi; \ + } | grep -v 'libtool:' >/dev/null; then \ + package_gnu=yes; \ + else \ + package_gnu=no; \ + fi; \ + }; \ + if test "$$package_gnu" = "yes"; then \ + package_prefix='GNU '; \ + else \ + package_prefix=''; \ + fi; \ + if test -n '$(MSGID_BUGS_ADDRESS)' || test '$(PACKAGE_BUGREPORT)' = '@'PACKAGE_BUGREPORT'@'; then \ + msgid_bugs_address='$(MSGID_BUGS_ADDRESS)'; \ + else \ + msgid_bugs_address='$(PACKAGE_BUGREPORT)'; \ + fi; \ + case `$(XGETTEXT) --version | sed 1q | sed -e 's,^[^0-9]*,,'` in \ + '' | 0.[0-9] | 0.[0-9].* | 0.1[0-5] | 0.1[0-5].* | 0.16 | 0.16.[0-1]*) \ + $(XGETTEXT) --default-domain=$(DOMAIN) --directory=$(top_srcdir) \ + --add-comments=TRANSLATORS: \ + --files-from=$(srcdir)/POTFILES.in \ + --copyright-holder='$(COPYRIGHT_HOLDER)' \ + --msgid-bugs-address="$$msgid_bugs_address" \ + $(XGETTEXT_OPTIONS) @XGETTEXT_EXTRA_OPTIONS@ \ + ;; \ + *) \ + $(XGETTEXT) --default-domain=$(DOMAIN) --directory=$(top_srcdir) \ + --add-comments=TRANSLATORS: \ + --files-from=$(srcdir)/POTFILES.in \ + --copyright-holder='$(COPYRIGHT_HOLDER)' \ + --package-name="$${package_prefix}@PACKAGE@" \ + --package-version='@VERSION@' \ + --msgid-bugs-address="$$msgid_bugs_address" \ + $(XGETTEXT_OPTIONS) @XGETTEXT_EXTRA_OPTIONS@ \ + ;; \ + esac + test ! -f $(DOMAIN).po || { \ + if test -f $(srcdir)/$(DOMAIN).pot-header; then \ + sed -e '1,/^#$$/d' < $(DOMAIN).po > $(DOMAIN).1po && \ + cat $(srcdir)/$(DOMAIN).pot-header $(DOMAIN).1po > $(DOMAIN).po && \ + rm -f $(DOMAIN).1po \ + || exit 1; \ + fi; \ + if test -f $(srcdir)/$(DOMAIN).pot; then \ + sed -f $(srcdir)/remove-potcdate.sed < $(srcdir)/$(DOMAIN).pot > $(DOMAIN).1po && \ + sed -f $(srcdir)/remove-potcdate.sed < $(DOMAIN).po > $(DOMAIN).2po && \ + if cmp $(DOMAIN).1po $(DOMAIN).2po >/dev/null 2>&1; then \ + rm -f $(DOMAIN).1po $(DOMAIN).2po $(DOMAIN).po; \ + else \ + rm -f $(DOMAIN).1po $(DOMAIN).2po $(srcdir)/$(DOMAIN).pot && \ + mv $(DOMAIN).po $(srcdir)/$(DOMAIN).pot; \ + fi; \ + else \ + mv $(DOMAIN).po $(srcdir)/$(DOMAIN).pot; \ + fi; \ + } + +# This rule has no dependencies: we don't need to update $(DOMAIN).pot at +# every "make" invocation, only create it when it is missing. +# Only "make $(DOMAIN).pot-update" or "make dist" will force an update. +$(srcdir)/$(DOMAIN).pot: + $(MAKE) $(DOMAIN).pot-update + +# This target rebuilds a PO file if $(DOMAIN).pot has changed. +# Note that a PO file is not touched if it doesn't need to be changed. +$(POFILES): $(POFILESDEPS) + @test -f $(srcdir)/$(DOMAIN).pot || $(MAKE) $(srcdir)/$(DOMAIN).pot + @lang=`echo $@ | sed -e 's,.*/,,' -e 's/\.po$$//'`; \ + if test -f "$(srcdir)/$${lang}.po"; then \ + if test "$(PACKAGE)" = "gettext-tools" && test "$(CROSS_COMPILING)" != "yes"; then PATH=`pwd`/../src:$$PATH; fi; \ + test "$(srcdir)" = . && cdcmd="" || cdcmd="cd $(srcdir) && "; \ + echo "$${cdcmd}$(MSGMERGE_UPDATE) --quiet $(MSGMERGE_OPTIONS) --lang=$${lang} --previous $${lang}.po $(DOMAIN).pot"; \ + cd $(srcdir) \ + && { case `$(MSGMERGE_UPDATE) --version | sed 1q | sed -e 's,^[^0-9]*,,'` in \ + '' | 0.[0-9] | 0.[0-9].* | 0.10 | 0.10.*) \ + $(MSGMERGE_UPDATE) $(MSGMERGE_OPTIONS) $${lang}.po $(DOMAIN).pot;; \ + 0.1[1-5] | 0.1[1-5].*) \ + $(MSGMERGE_UPDATE) --quiet $(MSGMERGE_OPTIONS) $${lang}.po $(DOMAIN).pot;; \ + 0.1[6-7] | 0.1[6-7].*) \ + $(MSGMERGE_UPDATE) --quiet $(MSGMERGE_OPTIONS) --previous $${lang}.po $(DOMAIN).pot;; \ + *) \ + $(MSGMERGE_UPDATE) --quiet $(MSGMERGE_OPTIONS) --lang=$${lang} --previous $${lang}.po $(DOMAIN).pot;; \ + esac; \ + }; \ + else \ + $(MAKE) $${lang}.po-create; \ + fi + + +install: install-exec install-data +install-exec: +install-data: install-data-@USE_NLS@ + if test "$(PACKAGE)" = "gettext-tools"; then \ + $(mkdir_p) $(DESTDIR)$(gettextsrcdir); \ + for file in $(DISTFILES.common) Makevars.template; do \ + $(INSTALL_DATA) $(srcdir)/$$file \ + $(DESTDIR)$(gettextsrcdir)/$$file; \ + done; \ + for file in Makevars; do \ + rm -f $(DESTDIR)$(gettextsrcdir)/$$file; \ + done; \ + else \ + : ; \ + fi +install-data-no: all +install-data-yes: all + @catalogs='$(CATALOGS)'; \ + for cat in $$catalogs; do \ + cat=`basename $$cat`; \ + lang=`echo $$cat | sed -e 's/\.gmo$$//'`; \ + dir=$(localedir)/$$lang/LC_MESSAGES; \ + $(mkdir_p) $(DESTDIR)$$dir; \ + if test -r $$cat; then realcat=$$cat; else realcat=$(srcdir)/$$cat; fi; \ + $(INSTALL_DATA) $$realcat $(DESTDIR)$$dir/$(DOMAIN).mo; \ + echo "installing $$realcat as $(DESTDIR)$$dir/$(DOMAIN).mo"; \ + for lc in '' $(EXTRA_LOCALE_CATEGORIES); do \ + if test -n "$$lc"; then \ + if (cd $(DESTDIR)$(localedir)/$$lang && LC_ALL=C ls -l -d $$lc 2>/dev/null) | grep ' -> ' >/dev/null; then \ + link=`cd $(DESTDIR)$(localedir)/$$lang && LC_ALL=C ls -l -d $$lc | sed -e 's/^.* -> //'`; \ + mv $(DESTDIR)$(localedir)/$$lang/$$lc $(DESTDIR)$(localedir)/$$lang/$$lc.old; \ + mkdir $(DESTDIR)$(localedir)/$$lang/$$lc; \ + (cd $(DESTDIR)$(localedir)/$$lang/$$lc.old && \ + for file in *; do \ + if test -f $$file; then \ + ln -s ../$$link/$$file $(DESTDIR)$(localedir)/$$lang/$$lc/$$file; \ + fi; \ + done); \ + rm -f $(DESTDIR)$(localedir)/$$lang/$$lc.old; \ + else \ + if test -d $(DESTDIR)$(localedir)/$$lang/$$lc; then \ + :; \ + else \ + rm -f $(DESTDIR)$(localedir)/$$lang/$$lc; \ + mkdir $(DESTDIR)$(localedir)/$$lang/$$lc; \ + fi; \ + fi; \ + rm -f $(DESTDIR)$(localedir)/$$lang/$$lc/$(DOMAIN).mo; \ + ln -s ../LC_MESSAGES/$(DOMAIN).mo $(DESTDIR)$(localedir)/$$lang/$$lc/$(DOMAIN).mo 2>/dev/null || \ + ln $(DESTDIR)$(localedir)/$$lang/LC_MESSAGES/$(DOMAIN).mo $(DESTDIR)$(localedir)/$$lang/$$lc/$(DOMAIN).mo 2>/dev/null || \ + cp -p $(DESTDIR)$(localedir)/$$lang/LC_MESSAGES/$(DOMAIN).mo $(DESTDIR)$(localedir)/$$lang/$$lc/$(DOMAIN).mo; \ + echo "installing $$realcat link as $(DESTDIR)$(localedir)/$$lang/$$lc/$(DOMAIN).mo"; \ + fi; \ + done; \ + done + +install-strip: install + +installdirs: installdirs-exec installdirs-data +installdirs-exec: +installdirs-data: installdirs-data-@USE_NLS@ + if test "$(PACKAGE)" = "gettext-tools"; then \ + $(mkdir_p) $(DESTDIR)$(gettextsrcdir); \ + else \ + : ; \ + fi +installdirs-data-no: +installdirs-data-yes: + @catalogs='$(CATALOGS)'; \ + for cat in $$catalogs; do \ + cat=`basename $$cat`; \ + lang=`echo $$cat | sed -e 's/\.gmo$$//'`; \ + dir=$(localedir)/$$lang/LC_MESSAGES; \ + $(mkdir_p) $(DESTDIR)$$dir; \ + for lc in '' $(EXTRA_LOCALE_CATEGORIES); do \ + if test -n "$$lc"; then \ + if (cd $(DESTDIR)$(localedir)/$$lang && LC_ALL=C ls -l -d $$lc 2>/dev/null) | grep ' -> ' >/dev/null; then \ + link=`cd $(DESTDIR)$(localedir)/$$lang && LC_ALL=C ls -l -d $$lc | sed -e 's/^.* -> //'`; \ + mv $(DESTDIR)$(localedir)/$$lang/$$lc $(DESTDIR)$(localedir)/$$lang/$$lc.old; \ + mkdir $(DESTDIR)$(localedir)/$$lang/$$lc; \ + (cd $(DESTDIR)$(localedir)/$$lang/$$lc.old && \ + for file in *; do \ + if test -f $$file; then \ + ln -s ../$$link/$$file $(DESTDIR)$(localedir)/$$lang/$$lc/$$file; \ + fi; \ + done); \ + rm -f $(DESTDIR)$(localedir)/$$lang/$$lc.old; \ + else \ + if test -d $(DESTDIR)$(localedir)/$$lang/$$lc; then \ + :; \ + else \ + rm -f $(DESTDIR)$(localedir)/$$lang/$$lc; \ + mkdir $(DESTDIR)$(localedir)/$$lang/$$lc; \ + fi; \ + fi; \ + fi; \ + done; \ + done + +# Define this as empty until I found a useful application. +installcheck: + +uninstall: uninstall-exec uninstall-data +uninstall-exec: +uninstall-data: uninstall-data-@USE_NLS@ + if test "$(PACKAGE)" = "gettext-tools"; then \ + for file in $(DISTFILES.common) Makevars.template; do \ + rm -f $(DESTDIR)$(gettextsrcdir)/$$file; \ + done; \ + else \ + : ; \ + fi +uninstall-data-no: +uninstall-data-yes: + catalogs='$(CATALOGS)'; \ + for cat in $$catalogs; do \ + cat=`basename $$cat`; \ + lang=`echo $$cat | sed -e 's/\.gmo$$//'`; \ + for lc in LC_MESSAGES $(EXTRA_LOCALE_CATEGORIES); do \ + rm -f $(DESTDIR)$(localedir)/$$lang/$$lc/$(DOMAIN).mo; \ + done; \ + done + +check: all + +info dvi ps pdf html tags TAGS ctags CTAGS ID: + +install-dvi install-ps install-pdf install-html: + +mostlyclean: + rm -f $(srcdir)/stamp-poT + rm -f core core.* $(DOMAIN).po $(DOMAIN).1po $(DOMAIN).2po *.new.po + rm -fr *.o + +clean: mostlyclean + +distclean: clean + rm -f Makefile Makefile.in + +maintainer-clean: distclean + @echo "This command is intended for maintainers to use;" + @echo "it deletes files that may require special tools to rebuild." + rm -f $(srcdir)/$(DOMAIN).pot $(srcdir)/stamp-po $(GMOFILES) + +distdir = $(top_builddir)/$(PACKAGE)-$(VERSION)/$(subdir) +dist distdir: + test -z "$(DISTFILESDEPS)" || $(MAKE) $(DISTFILESDEPS) + @$(MAKE) dist2 +# This is a separate target because 'update-po' must be executed before. +dist2: $(srcdir)/stamp-po $(DISTFILES) + @dists="$(DISTFILES)"; \ + if test "$(PACKAGE)" = "gettext-tools"; then \ + dists="$$dists Makevars.template"; \ + fi; \ + if test -f $(srcdir)/$(DOMAIN).pot; then \ + dists="$$dists $(DOMAIN).pot stamp-po"; \ + else \ + case $(XGETTEXT) in \ + :) echo "Warning: Creating a tarball without '$(DOMAIN).pot', because a suitable 'xgettext' program was not found in PATH." 1>&2;; \ + *) echo "Warning: Creating a tarball without '$(DOMAIN).pot', because 'xgettext' found no strings to extract. Check the contents of the POTFILES.in file and the XGETTEXT_OPTIONS in the Makevars file." 1>&2;; \ + esac; \ + fi; \ + if test -f $(srcdir)/ChangeLog; then \ + dists="$$dists ChangeLog"; \ + fi; \ + for i in 0 1 2 3 4 5 6 7 8 9; do \ + if test -f $(srcdir)/ChangeLog.$$i; then \ + dists="$$dists ChangeLog.$$i"; \ + fi; \ + done; \ + if test -f $(srcdir)/LINGUAS; then dists="$$dists LINGUAS"; fi; \ + for file in $$dists; do \ + if test -f $$file; then \ + cp -p $$file $(distdir) || exit 1; \ + else \ + cp -p $(srcdir)/$$file $(distdir) || exit 1; \ + fi; \ + done + +update-po: Makefile + $(MAKE) $(DOMAIN).pot-update + test -z "$(UPDATEPOFILES)" || $(MAKE) $(UPDATEPOFILES) + $(MAKE) update-gmo + +# General rule for creating PO files. + +.nop.po-create: + @lang=`echo $@ | sed -e 's/\.po-create$$//'`; \ + echo "File $$lang.po does not exist. If you are a translator, you can create it through 'msginit'." 1>&2; \ + exit 1 + +# General rule for updating PO files. + +.nop.po-update: + @lang=`echo $@ | sed -e 's/\.po-update$$//'`; \ + if test "$(PACKAGE)" = "gettext-tools" && test "$(CROSS_COMPILING)" != "yes"; then PATH=`pwd`/../src:$$PATH; fi; \ + tmpdir=`pwd`; \ + echo "$$lang:"; \ + test "$(srcdir)" = . && cdcmd="" || cdcmd="cd $(srcdir) && "; \ + echo "$${cdcmd}$(MSGMERGE) --quiet $(MSGMERGE_OPTIONS) --lang=$$lang --previous $$lang.po $(DOMAIN).pot -o $$lang.new.po"; \ + cd $(srcdir); \ + if { case `$(MSGMERGE) --version | sed 1q | sed -e 's,^[^0-9]*,,'` in \ + '' | 0.[0-9] | 0.[0-9].* | 0.10 | 0.10.*) \ + $(MSGMERGE) $(MSGMERGE_OPTIONS) -o $$tmpdir/$$lang.new.po $$lang.po $(DOMAIN).pot;; \ + 0.1[1-5] | 0.1[1-5].*) \ + $(MSGMERGE) --quiet $(MSGMERGE_OPTIONS) -o $$tmpdir/$$lang.new.po $$lang.po $(DOMAIN).pot;; \ + 0.1[6-7] | 0.1[6-7].*) \ + $(MSGMERGE) --quiet $(MSGMERGE_OPTIONS) --previous -o $$tmpdir/$$lang.new.po $$lang.po $(DOMAIN).pot;; \ + *) \ + $(MSGMERGE) --quiet $(MSGMERGE_OPTIONS) --lang=$$lang --previous -o $$tmpdir/$$lang.new.po $$lang.po $(DOMAIN).pot;; \ + esac; \ + }; then \ + if cmp $$lang.po $$tmpdir/$$lang.new.po >/dev/null 2>&1; then \ + rm -f $$tmpdir/$$lang.new.po; \ + else \ + if mv -f $$tmpdir/$$lang.new.po $$lang.po; then \ + :; \ + else \ + echo "msgmerge for $$lang.po failed: cannot move $$tmpdir/$$lang.new.po to $$lang.po" 1>&2; \ + exit 1; \ + fi; \ + fi; \ + else \ + echo "msgmerge for $$lang.po failed!" 1>&2; \ + rm -f $$tmpdir/$$lang.new.po; \ + fi + +$(DUMMYPOFILES): + +update-gmo: Makefile $(GMOFILES) + @: + +# Include all the Rules-* extensions. Documented in +# +RULES_FILES != cd $(srcdir) \ + && for file in Rules-*; do \ + if test -f "$$file"; then \ + case "$$file" in \ + *.orig | *.bak | *~) ;; \ + *) echo $(srcdir)/"$$file" ;; \ + esac; \ + fi; \ + done +include $(RULES_FILES) + +# Recreate Makefile by invoking config.status. Explicitly invoke the shell, +# because execution permission bits may not work on the current file system. +# Use @SHELL@, which is the shell determined by autoconf for the use by its +# scripts, not $(SHELL) which is hardwired to /bin/sh and may be deficient. +Makefile: Makefile.in.in Makevars $(top_builddir)/config.status + cd $(top_builddir) \ + && @SHELL@ ./config.status $(subdir)/$@.in po-directories + +force: + +# Tell versions [3.59,3.63) of GNU make not to export all variables. +# Otherwise a system limit (for SysV at least) may be exceeded. +.NOEXPORT: + +# This Makefile contains rules which don't work with parallel make, +# namely dist2. +# See . +# So, turn off parallel execution in this Makefile. +.NOTPARALLEL: diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/po/Makevars.template b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/po/Makevars.template new file mode 100644 index 0000000000000000000000000000000000000000..d1532a95c9f28a3187c1a33b375100d80d96b1c5 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/po/Makevars.template @@ -0,0 +1,82 @@ +# Makefile variables for PO directory in any package using GNU gettext. +# +# Copyright (C) 2003-2025 Free Software Foundation, Inc. +# This file is free software; the Free Software Foundation gives +# unlimited permission to use, copy, distribute, and modify it. + +# Usually the message domain is the same as the package name. +DOMAIN = $(PACKAGE) + +# These two variables depend on the location of this directory. +subdir = po +top_builddir = .. + +# These options get passed to xgettext. +XGETTEXT_OPTIONS = --keyword=_ --keyword=N_ + +# This is the copyright holder that gets inserted into the header of the +# $(DOMAIN).pot file. Set this to the copyright holder of the surrounding +# package. (Note that the msgid strings, extracted from the package's +# sources, belong to the copyright holder of the package.) Translators are +# expected to transfer the copyright for their translations to this person +# or entity, or to disclaim their copyright. The empty string stands for +# the public domain; in this case the translators are expected to disclaim +# their copyright. +COPYRIGHT_HOLDER = Free Software Foundation, Inc. + +# This tells whether or not to prepend "GNU " prefix to the package +# name that gets inserted into the header of the $(DOMAIN).pot file. +# Possible values are "yes", "no", or empty. If it is empty, try to +# detect it automatically by scanning the files in $(top_srcdir) for +# "GNU packagename" string. +PACKAGE_GNU = + +# This is the email address or URL to which the translators shall report +# bugs in the untranslated strings: +# - Strings which are not entire sentences, see the maintainer guidelines +# in the GNU gettext documentation, section 'Preparing Strings'. +# - Strings which use unclear terms or require additional context to be +# understood. +# - Strings which make invalid assumptions about notation of date, time or +# money. +# - Pluralisation problems. +# - Incorrect English spelling. +# - Incorrect formatting. +# It can be your email address, or a mailing list address where translators +# can write to without being subscribed, or the URL of a web page through +# which the translators can contact you. +MSGID_BUGS_ADDRESS = + +# This is the list of locale categories, beyond LC_MESSAGES, for which the +# message catalogs shall be used. It is usually empty. +EXTRA_LOCALE_CATEGORIES = + +# This tells whether the $(DOMAIN).pot file contains messages with an 'msgctxt' +# context. Possible values are "yes" and "no". Set this to yes if the +# package uses functions taking also a message context, like pgettext(), or +# if in $(XGETTEXT_OPTIONS) you define keywords with a context argument. +USE_MSGCTXT = no + +# These options get passed to msgmerge. +# Useful options are in particular: +# --previous to keep previous msgids of translated messages, +# --quiet to reduce the verbosity. +MSGMERGE_OPTIONS = + +# These options get passed to msginit. +# If you want to disable line wrapping when writing PO files, add +# --no-wrap to MSGMERGE_OPTIONS, XGETTEXT_OPTIONS, and +# MSGINIT_OPTIONS. +MSGINIT_OPTIONS = + +# This tells whether or not to regenerate a PO file when $(DOMAIN).pot +# has changed. Possible values are "yes" and "no". Set this to no if +# the POT file is checked in the repository and the version control +# program ignores timestamps. +PO_DEPENDS_ON_POT = yes + +# This tells whether or not to forcibly update $(DOMAIN).pot and +# regenerate PO files on "make dist". Possible values are "yes" and +# "no". Set this to no if the POT file and PO files are maintained +# externally. +DIST_DEPENDS_ON_UPDATE_PO = yes diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/po/Rules-quot b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/po/Rules-quot new file mode 100644 index 0000000000000000000000000000000000000000..9e1305407934796f5a0df7bcf6ec1100631d8254 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/po/Rules-quot @@ -0,0 +1,66 @@ +# Special Makefile rules for English message catalogs with quotation marks. +# +# Copyright (C) 2001-2024 Free Software Foundation, Inc. +# This file is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. +# This file is offered as-is, without any warranty. +# +# Written by Bruno Haible , 2001. + +DISTFILES.common.extra1 = quot.sed boldquot.sed en@quot.header en@boldquot.header insert-header.sed Rules-quot + +.SUFFIXES: .insert-header .po-update-en + +en@quot.po-create: + $(MAKE) en@quot.po-update +en@boldquot.po-create: + $(MAKE) en@boldquot.po-update + +en@quot.po-update: en@quot.po-update-en +en@boldquot.po-update: en@boldquot.po-update-en + +.insert-header.po-update-en: + @lang=`echo $@ | sed -e 's/\.po-update-en$$//'`; \ + if test "$(PACKAGE)" = "gettext-tools" && test "$(CROSS_COMPILING)" != "yes"; then PATH=`pwd`/../src:$$PATH; GETTEXTLIBDIR=`cd $(top_srcdir)/src && pwd`; export GETTEXTLIBDIR; fi; \ + tmpdir=`pwd`; \ + echo "$$lang:"; \ + ll=`echo $$lang | sed -e 's/@.*//'`; \ + LC_ALL=C; export LC_ALL; \ + cd $(srcdir); \ + if $(MSGINIT) $(MSGINIT_OPTIONS) -i $(DOMAIN).pot --no-translator -l $$lang -o - 2>/dev/null \ + | $(SED) -f $$tmpdir/$$lang.insert-header | $(SED) -e '/^%%/d' \ + | $(MSGCONV) -t UTF-8 | \ + { case `$(MSGFILTER) --version | sed 1q | sed -e 's,^[^0-9]*,,'` in \ + '' | 0.[0-9] | 0.[0-9].* | 0.1[0-8] | 0.1[0-8].*) \ + $(MSGFILTER) $(SED) -f `echo $$lang | sed -e 's/.*@//'`.sed \ + ;; \ + *) \ + $(MSGFILTER) `echo $$lang | sed -e 's/.*@//'` \ + ;; \ + esac } 2>/dev/null > $$tmpdir/$$lang.new.po \ + ; then \ + if cmp $$lang.po $$tmpdir/$$lang.new.po >/dev/null 2>&1; then \ + rm -f $$tmpdir/$$lang.new.po; \ + else \ + if mv -f $$tmpdir/$$lang.new.po $$lang.po; then \ + :; \ + else \ + echo "creation of $$lang.po failed: cannot move $$tmpdir/$$lang.new.po to $$lang.po" 1>&2; \ + exit 1; \ + fi; \ + fi; \ + else \ + echo "creation of $$lang.po failed!" 1>&2; \ + rm -f $$tmpdir/$$lang.new.po; \ + fi + +en@quot.insert-header: insert-header.sed + sed -e 's/HEADER/en@quot.header/g' $(srcdir)/insert-header.sed > en@quot.insert-header + +en@boldquot.insert-header: insert-header.sed + sed -e 's/HEADER/en@boldquot.header/g' $(srcdir)/insert-header.sed > en@boldquot.insert-header + +mostlyclean: mostlyclean-quot +mostlyclean-quot: + rm -f *.insert-header diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/po/boldquot.sed b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/po/boldquot.sed new file mode 100644 index 0000000000000000000000000000000000000000..3c1de54e66e4500a95c29f78c9db06fbaa59aeb5 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/po/boldquot.sed @@ -0,0 +1,21 @@ +# Sed script that converts quotations, by replacing ASCII quotation marks +# with Unicode quotation marks and highlighting the quotations in bold face. +# +# Copyright (C) 2001 Free Software Foundation, Inc. +# This file is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. +# This file is offered as-is, without any warranty. +# +# Written by Bruno Haible , 2001. +# +s/"\([^"]*\)"/“\1”/g +s/`\([^`']*\)'/‘\1’/g +s/ '\([^`']*\)' / ‘\1’ /g +s/ '\([^`']*\)'$/ ‘\1’/g +s/^'\([^`']*\)' /‘\1’ /g +s/“”/""/g +s/“/“/g +s/”/”/g +s/‘/‘/g +s/’/’/g diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/po/en@boldquot.header b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/po/en@boldquot.header new file mode 100644 index 0000000000000000000000000000000000000000..ac96ad9f36ee27a09491803d5eeb3b17da367e47 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/po/en@boldquot.header @@ -0,0 +1,35 @@ +%% A header that gets inserted into message catalogs named en@boldquot.po. +%% +%% Copyright (C) 2001 Free Software Foundation, Inc. +%% This file is free software; the Free Software Foundation +%% gives unlimited permission to copy and/or distribute it, +%% with or without modifications, as long as this notice is preserved. +%% This file is offered as-is, without any warranty. +%% +%% Written by Bruno Haible , 2001. +%% +# All this catalog "translates" are quotation characters. +# The msgids must be ASCII and therefore cannot contain real quotation +# characters, only substitutes like grave accent (0x60), apostrophe (0x27) +# and double quote (0x22). These substitutes look strange; see +# https://www.cl.cam.ac.uk/~mgk25/ucs/quotes.html +# +# This catalog translates grave accent (0x60) and apostrophe (0x27) to +# left single quotation mark (U+2018) and right single quotation mark (U+2019). +# It also translates pairs of apostrophe (0x27) to +# left single quotation mark (U+2018) and right single quotation mark (U+2019) +# and pairs of quotation mark (0x22) to +# left double quotation mark (U+201C) and right double quotation mark (U+201D). +# +# When output to an UTF-8 terminal, the quotation characters appear perfectly. +# When output to an ISO-8859-1 terminal, the single quotation marks are +# transliterated to apostrophes (by iconv in glibc 2.2 or newer) or to +# grave/acute accent (by libiconv), and the double quotation marks are +# transliterated to 0x22. +# When output to an ASCII terminal, the single quotation marks are +# transliterated to apostrophes, and the double quotation marks are +# transliterated to 0x22. +# +# This catalog furthermore displays the text between the quotation marks in +# bold face, assuming the VT100/XTerm escape sequences. +# diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/po/en@quot.header b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/po/en@quot.header new file mode 100644 index 0000000000000000000000000000000000000000..287e2e735b91018e0fec016f079e824f68241fbd --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/po/en@quot.header @@ -0,0 +1,32 @@ +%% A header that gets inserted into message catalogs named en@quot.po. +%% +%% Copyright (C) 2001 Free Software Foundation, Inc. +%% This file is free software; the Free Software Foundation +%% gives unlimited permission to copy and/or distribute it, +%% with or without modifications, as long as this notice is preserved. +%% This file is offered as-is, without any warranty. +%% +%% Written by Bruno Haible , 2001. +%% +# All this catalog "translates" are quotation characters. +# The msgids must be ASCII and therefore cannot contain real quotation +# characters, only substitutes like grave accent (0x60), apostrophe (0x27) +# and double quote (0x22). These substitutes look strange; see +# https://www.cl.cam.ac.uk/~mgk25/ucs/quotes.html +# +# This catalog translates grave accent (0x60) and apostrophe (0x27) to +# left single quotation mark (U+2018) and right single quotation mark (U+2019). +# It also translates pairs of apostrophe (0x27) to +# left single quotation mark (U+2018) and right single quotation mark (U+2019) +# and pairs of quotation mark (0x22) to +# left double quotation mark (U+201C) and right double quotation mark (U+201D). +# +# When output to an UTF-8 terminal, the quotation characters appear perfectly. +# When output to an ISO-8859-1 terminal, the single quotation marks are +# transliterated to apostrophes (by iconv in glibc 2.2 or newer) or to +# grave/acute accent (by libiconv), and the double quotation marks are +# transliterated to 0x22. +# When output to an ASCII terminal, the single quotation marks are +# transliterated to apostrophes, and the double quotation marks are +# transliterated to 0x22. +# diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/po/insert-header.sed b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/po/insert-header.sed new file mode 100644 index 0000000000000000000000000000000000000000..f9534e7edf9d4652ee0abedf47b308a3ff58b963 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/po/insert-header.sed @@ -0,0 +1,31 @@ +# Sed script that inserts the file called HEADER before the header entry. +# +# Copyright (C) 2001 Free Software Foundation, Inc. +# This file is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. +# This file is offered as-is, without any warranty. +# +# Written by Bruno Haible , 2001. +# +# At each occurrence of a line starting with "msgid ", we execute the following +# commands. At the first occurrence, insert the file. At the following +# occurrences, do nothing. The distinction between the first and the following +# occurrences is achieved by looking at the hold space. +/^msgid /{ +x +# Test if the hold space is empty. +s/m/m/ +ta +# Yes it was empty. First occurrence. Read the file. +r HEADER +# Output the file's contents by reading the next line. But don't lose the +# current line while doing this. +g +N +bb +:a +# The hold space was nonempty. Following occurrences. Do nothing. +x +:b +} diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/po/quot.sed b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/po/quot.sed new file mode 100644 index 0000000000000000000000000000000000000000..eb0e08dad08f82b535aaf739ce1efb5752e3b1ae --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/po/quot.sed @@ -0,0 +1,17 @@ +# Sed script that converts quotations, by replacing ASCII quotation marks +# with Unicode quotation marks. +# +# Copyright (C) 2001 Free Software Foundation, Inc. +# This file is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. +# This file is offered as-is, without any warranty. +# +# Written by Bruno Haible , 2001. +# +s/"\([^"]*\)"/“\1”/g +s/`\([^`']*\)'/‘\1’/g +s/ '\([^`']*\)' / ‘\1’ /g +s/ '\([^`']*\)'$/ ‘\1’/g +s/^'\([^`']*\)' /‘\1’ /g +s/“”/""/g diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/po/remove-potcdate.sed b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/po/remove-potcdate.sed new file mode 100644 index 0000000000000000000000000000000000000000..8c70dfbf1488022cd0da639ad521ade041d31c27 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/po/remove-potcdate.sed @@ -0,0 +1,25 @@ +# Sed script that removes the POT-Creation-Date line in the header entry +# from a POT file. +# +# Copyright (C) 2002 Free Software Foundation, Inc. +# Copying and distribution of this file, with or without modification, +# are permitted in any medium without royalty provided the copyright +# notice and this notice are preserved. This file is offered as-is, +# without any warranty. +# +# The distinction between the first and the following occurrences of the +# pattern is achieved by looking at the hold space. +/^"POT-Creation-Date: .*"$/{ +x +# Test if the hold space is empty. +s/P/P/ +ta +# Yes it was empty. First occurrence. Remove the line. +g +d +bb +:a +# The hold space was nonempty. Following occurrences. Do nothing. +x +:b +} diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/schema/its-extensions.xsd b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/schema/its-extensions.xsd new file mode 100644 index 0000000000000000000000000000000000000000..97cc703f3e6fbcf04fa6717de9cbf73cf97b04fc --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/schema/its-extensions.xsd @@ -0,0 +1,75 @@ + + + + + XML schema extensions for *.its files, as understood by GNU gettext. + +Copyright (C) 2015-2024 Free Software Foundation, Inc. + +This file 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 file 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/>. + +Written by Bruno Haible <bruno@clisp.org>, 2024. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/schema/its.xsd10 b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/schema/its.xsd10 new file mode 100644 index 0000000000000000000000000000000000000000..326edfbe177933016f9fc0b5ce5a43beba5e2abf --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/schema/its.xsd10 @@ -0,0 +1,139 @@ + + + + + XML schema 1.0 of *.its files, as understood by GNU gettext. + +Copyright (C) 2015-2024 Free Software Foundation, Inc. + +This file 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 file 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/>. + +Written by Bruno Haible <bruno@clisp.org>, 2024. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Note: An instance should not have both the 'locNotePointer' attribute and a 'locNote' child at the same time. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/schema/its.xsd11 b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/schema/its.xsd11 new file mode 100644 index 0000000000000000000000000000000000000000..5280bbaf3bb16e868b121b64ca096264a546a8e6 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/schema/its.xsd11 @@ -0,0 +1,115 @@ + + + + + XML schema 1.1 of *.its files, as understood by GNU gettext. + +Copyright (C) 2015-2024 Free Software Foundation, Inc. + +This file 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 file 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/>. + +Written by Bruno Haible <bruno@clisp.org>, 2024. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Note: An instance should not have both the 'locNotePointer' attribute and a 'locNote' child at the same time. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/schema/locating-rules.xsd10 b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/schema/locating-rules.xsd10 new file mode 100644 index 0000000000000000000000000000000000000000..1795e6ea4a7112bd4c45e5077915b393758c1301 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/schema/locating-rules.xsd10 @@ -0,0 +1,88 @@ + + + + + XML schema 1.0 of *.loc files, as understood by GNU gettext. + +Copyright (C) 2015-2024 Free Software Foundation, Inc. + +This file 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 file 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/>. + +Written by Bruno Haible <bruno@clisp.org>, 2024. + + + + + + + + + + + Example: +<locatingRules> + <locatingRule name="Glade" pattern="*.glade"> + <documentRule localName="GTK-Interface" target="glade1.its"/> + <documentRule localName="glade-interface" target="glade2.its"/> + <documentRule localName="interface" target="gtkbuilder.its"/> + </locatingRule> + <locatingRule name="Glade" pattern="*.glade2"> + <documentRule localName="glade-interface" target="glade2.its"/> + </locatingRule> + <locatingRule name="Glade" pattern="*.ui"> + <documentRule localName="interface" target="gtkbuilder.its"/> + </locatingRule> +</locatingRules> + + + + + + + + + + + + Example: +&lt;locatingRule name=&quot;Glade&quot; pattern=&quot;*.glade&quot;&gt; + &lt;documentRule localName=&quot;GTK-Interface&quot; target=&quot;glade1.its&quot;/&gt; + &lt;documentRule localName=&quot;glade-interface&quot; target=&quot;glade2.its&quot;/&gt; + &lt;documentRule localName=&quot;interface&quot; target=&quot;gtkbuilder.its&quot;/&gt; +&lt;/locatingRule&gt; + +Note: An instance should not have both the 'target' attribute and a 'documentRule' child at the same time. + + + + + + + + + + + + + Example: +<documentRule localName="GTK-Interface" target="glade1.its"/> + + + + + + + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/schema/locating-rules.xsd11 b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/schema/locating-rules.xsd11 new file mode 100644 index 0000000000000000000000000000000000000000..d4bac98bbbaa446a92cd122cec9fdbbae5093cba --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/schema/locating-rules.xsd11 @@ -0,0 +1,87 @@ + + + + + XML schema 1.1 of *.loc files, as understood by GNU gettext. + +Copyright (C) 2015-2024 Free Software Foundation, Inc. + +This file 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 file 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/>. + +Written by Bruno Haible <bruno@clisp.org>, 2024. + + + + + + + + + + + Example: +<locatingRules> + <locatingRule name="Glade" pattern="*.glade"> + <documentRule localName="GTK-Interface" target="glade1.its"/> + <documentRule localName="glade-interface" target="glade2.its"/> + <documentRule localName="interface" target="gtkbuilder.its"/> + </locatingRule> + <locatingRule name="Glade" pattern="*.glade2"> + <documentRule localName="glade-interface" target="glade2.its"/> + </locatingRule> + <locatingRule name="Glade" pattern="*.ui"> + <documentRule localName="interface" target="gtkbuilder.its"/> + </locatingRule> +</locatingRules> + + + + + + + + + + + + Example: +&lt;locatingRule name=&quot;Glade&quot; pattern=&quot;*.glade&quot;&gt; + &lt;documentRule localName=&quot;GTK-Interface&quot; target=&quot;glade1.its&quot;/&gt; + &lt;documentRule localName=&quot;glade-interface&quot; target=&quot;glade2.its&quot;/&gt; + &lt;documentRule localName=&quot;interface&quot; target=&quot;gtkbuilder.its&quot;/&gt; +&lt;/locatingRule&gt; + +Note: An instance should not have both the 'target' attribute and a 'documentRule' child at the same time. + + + + + + + + + + + + + + Example: +<documentRule localName="GTK-Interface" target="glade1.its"/> + + + + + + + diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/styles/po-default.css b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/styles/po-default.css new file mode 100644 index 0000000000000000000000000000000000000000..c120c508363f4567bf5ff979175fe1c078ace5c9 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/styles/po-default.css @@ -0,0 +1,26 @@ +/* Default styling rules for PO files when doing terminal output. + Copyright (C) 2006-2007 Free Software Foundation, Inc. + + 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 . */ + +.translator-comment { color : green; } +.obsolete { color : green; } +.extracted-comment { color : green; font-weight: bold; } +.flag { text-decoration : underline; } +.fuzzy-flag { text-decoration : none; } +.text { color : magenta; } +.msgstr .text { color : blue; } +.fuzzy .msgstr .text { color : red; } +.format-directive { font-weight: bold; } +.invalid-format-directive { background-color : red; color : white; font-weight: bold; } diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/styles/po-emacs-x.css b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/styles/po-emacs-x.css new file mode 100644 index 0000000000000000000000000000000000000000..eb876e8eb61f72d4d5a3ddfc3fe9b707e11de78d --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/styles/po-emacs-x.css @@ -0,0 +1,24 @@ +/* Styling rules for PO files, imitating emacs 21 and 22 in an X window. + Copyright (C) 2006-2007 Free Software Foundation, Inc. + + 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 . */ + +.comment { color : rgb(178,34,34); } +.reference { color : rgb(95,158,160); } +.flag { color : rgb(0,0,0); } +.keyword { color : rgb(160,32,240); } +.string { color : rgb(160,32,240); } +.text { color : rgb(0,0,0); } +.escape-sequence { color : rgb(184,134,11); } +.format-directive { color : rgb(184,134,11); } diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/styles/po-emacs-xterm.css b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/styles/po-emacs-xterm.css new file mode 100644 index 0000000000000000000000000000000000000000..a5efdbe241aaa903b9d7748689544e633bbcda3b --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/styles/po-emacs-xterm.css @@ -0,0 +1,22 @@ +/* Styling rules for PO files, imitating emacs 22 in an xterm terminal. + Copyright (C) 2006-2007 Free Software Foundation, Inc. + + 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 . */ + +.reference { color : rgb(205,0,205); } +.keyword { color : rgb(0,255,255); font-weight : bold; } +.string { color : rgb(0,255,255); font-weight : bold; } +.text { color : rgb(0,0,0); font-weight : normal; } +.escape-sequence { color : rgb(205,205,0); } +.format-directive { color : rgb(205,205,0); } diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/styles/po-emacs-xterm16.css b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/styles/po-emacs-xterm16.css new file mode 100644 index 0000000000000000000000000000000000000000..4c8caa26d2e2531bdb761eb4c1aac619db149f46 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/styles/po-emacs-xterm16.css @@ -0,0 +1,24 @@ +/* Styling rules for PO files, imitating emacs 22 in an xterm-16color terminal. + Copyright (C) 2006-2007 Free Software Foundation, Inc. + + 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 . */ + +.comment { color : rgb(205,0,0); } +.reference { color : rgb(0,205,205); } +.flag { color : rgb(0,0,0); } +.keyword { color : rgb(205,0,205); } +.string { color : rgb(205,0,205); } +.text { color : rgb(0,0,0); } +.escape-sequence { color : rgb(205,205,0); } +.format-directive { color : rgb(205,205,0); } diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/styles/po-emacs-xterm256.css b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/styles/po-emacs-xterm256.css new file mode 100644 index 0000000000000000000000000000000000000000..a1aaf3be8715b8ce878a1c5ca12e34010bf351bf --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/styles/po-emacs-xterm256.css @@ -0,0 +1,24 @@ +/* Styling rules for PO files, imitating emacs 22 in an xterm-256color terminal. + Copyright (C) 2006-2007 Free Software Foundation, Inc. + + 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 . */ + +.comment { color : rgb(175,0,0); } +.reference { color : rgb(95,175,175); } +.flag { color : rgb(0,0,0); } +.keyword { color : rgb(175,0,255); } +.string { color : rgb(175,0,255); } +.text { color : rgb(0,0,0); } +.escape-sequence { color : rgb(175,135,0); } +.format-directive { color : rgb(175,135,0); } diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/styles/po-vim.css b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/styles/po-vim.css new file mode 100644 index 0000000000000000000000000000000000000000..ae593208fbaae0fc97b78399cf24f4453bca151f --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/gettext/styles/po-vim.css @@ -0,0 +1,24 @@ +/* Styling rules for PO files, imitating vim 7. + Copyright (C) 2006-2007 Free Software Foundation, Inc. + + 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 . */ + +.comment { color : rgb(0,0,205); } +.reference-comment { color : rgb(205,0,205); } +.flag-comment { color : rgb(205,0,205); } +.fuzzy-flag { color : rgb(0,0,0); background-color : rgb(205,205,0); } +.keyword { color : rgb(205,205,0); } +.string { color : rgb(205,0,0); } +.escape-sequence { color : rgb(205,0,205); } +.format-directive { color : rgb(205,0,205); } diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/info/autosprintf.info b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/info/autosprintf.info new file mode 100644 index 0000000000000000000000000000000000000000..11b15c8e7cdd0b4c4c642684a4cf1123b8f0f9b5 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/info/autosprintf.info @@ -0,0 +1,1546 @@ +This is autosprintf.info, produced by makeinfo version 7.1 from +autosprintf.texi. + + Copyright (C) 2002-2003, 2006-2007, 2018-2019 Free Software +Foundation, Inc. + + 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.3 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 +. + + 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 . +INFO-DIR-SECTION C++ libraries +START-INFO-DIR-ENTRY +* autosprintf: (autosprintf). Support for printf format strings in C++. +END-INFO-DIR-ENTRY + + This file provides documentation for GNU ‘autosprintf’ library. + + +File: autosprintf.info, Node: Top, Next: Introduction, Up: (dir) + +GNU autosprintf +*************** + + This manual documents the GNU autosprintf class, version 1.0. + +* Menu: + +* Introduction:: Introduction +* Class autosprintf:: The ‘autosprintf’ class +* Using autosprintf:: Using ‘autosprintf’ in own programs +* Licenses:: + + +File: autosprintf.info, Node: Introduction, Next: Class autosprintf, Prev: Top, Up: Top + +1 Introduction +************** + + This package makes the C formatted output routines (‘fprintf’ et al.) +usable in C++ programs, for use with the ‘’ strings and the +‘’ streams. + + It allows to write code like + + cerr << autosprintf ("syntax error in %s:%d: %s", filename, line, errstring); + +instead of + + cerr << "syntax error in " << filename << ":" << line << ": " << errstring; + + The benefits of the autosprintf syntax are: + + • It reuses the standard POSIX printf facility. Easy migration from + C to C++. + + • English sentences are kept together. + + • It makes internationalization possible. Internationalization + requires format strings, because in some cases the translator needs + to change the order of a sentence, and more generally it is easier + for the translator to work with a single string for a sentence than + with multiple string pieces. + + • It reduces the risk of programming errors due to forgotten state in + the output stream (e.g. ‘cout << hex;’ not followed by ‘cout << + dec;’). + + +File: autosprintf.info, Node: Class autosprintf, Next: Using autosprintf, Prev: Introduction, Up: Top + +2 The ‘autosprintf’ class +************************* + + An instance of class ‘autosprintf’ just contains a string with the +formatted output result. Such an instance is usually allocated as an +automatic storage variable, i.e. on the stack, not with ‘new’ on the +heap. + + The constructor ‘autosprintf (const char *format, ...)’ takes a +format string and additional arguments, like the C function ‘printf’. + + Conversions to ‘char *’ and ‘std::string’ are defined that return the +encapsulated string. The conversion to ‘char *’ returns a freshly +allocated copy of the encapsulated string; it needs to be freed using +‘delete[]’. The conversion to ‘std::string’ returns a copy of the +encapsulated string, with automatic memory management. + + The destructor ‘~autosprintf ()’ destroys the encapsulated string. + + An ‘operator <<’ is provided that outputs the encapsulated string to +the given ‘ostream’. + + +File: autosprintf.info, Node: Using autosprintf, Next: Licenses, Prev: Class autosprintf, Up: Top + +3 Using ‘autosprintf’ in own programs +************************************* + + To use the ‘autosprintf’ class in your programs, you need to add + + #include "autosprintf.h" + using gnu::autosprintf; + +to your source code. The include file defines the class ‘autosprintf’, +in a namespace called ‘gnu’. The ‘using’ statement makes it possible to +use the class without the (otherwise natural) ‘gnu::’ prefix. + + When linking your program, you need to link with ‘libasprintf’, +because that's where the class is defined. In projects using GNU +‘autoconf’, this means adding ‘AC_LIB_LINKFLAGS([asprintf])’ to +‘configure.in’ or ‘configure.ac’, and using the @LIBASPRINTF@ Makefile +variable that it provides. + + +File: autosprintf.info, Node: Licenses, Prev: Using autosprintf, Up: Top + +Appendix A Licenses +******************* + + The files of this package are covered by the licenses indicated in +each particular file or directory. Here is a summary: + + • The ‘libasprintf’ library is covered by the GNU Lesser General + Public License (LGPL), either version 2.1 of the License, or (at + your option) any later version published by the Free Software + Foundation (FSF). A copy of the license is included in *note GNU + LGPL::. + + • 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 included in *note GNU FDL::. + 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 included in *note GNU GPL::. + +* Menu: + +* GNU LGPL:: GNU Lesser General Public License +* GNU GPL:: GNU General Public License +* GNU FDL:: GNU Free Documentation License + + +File: autosprintf.info, Node: GNU LGPL, Next: GNU GPL, Up: Licenses + +A.1 GNU LESSER GENERAL PUBLIC LICENSE +===================================== + + Version 2.1, February 1999 + + Copyright © 1991, 1999 Free Software Foundation, Inc. + + + 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--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. + + 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. + +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. + + 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. + + 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. + + 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. + + 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. + + 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 +--------------------------- + +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 AN 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.1 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, see . + + 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 MOE GHOUL, 1 April 1990 + Moe Ghoul, President of Vice + + That's all there is to it! + + +File: autosprintf.info, Node: GNU GPL, Next: GNU FDL, Prev: GNU LGPL, Up: Licenses + +A.2 GNU GENERAL PUBLIC LICENSE +============================== + + Version 2, June 1991 + + Copyright © 1989, 1991 Free Software Foundation, Inc. + + + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + +Preamble +======== + + The licenses for most software are designed to take away your freedom +to share and change it. By contrast, the GNU General Public License is +intended to guarantee your freedom to share and change free software--to +make sure the software is free for all its users. This General Public +License applies to most of the Free Software Foundation's software and +to any other program whose authors commit to using it. (Some other Free +Software Foundation software is covered by the GNU Lesser General Public +License instead.) 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 +this service 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 make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the rights. +These restrictions translate to certain responsibilities for you if you +distribute copies of the software, or if you modify it. + + For example, if you distribute copies of such a program, whether +gratis or for a fee, you must give the recipients all the rights that +you have. 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. + + We protect your rights with two steps: (1) copyright the software, +and (2) offer you this license which gives you legal permission to copy, +distribute and/or modify the software. + + Also, for each author's protection and ours, we want to make certain +that everyone understands that there is no warranty for this free +software. If the software is modified by someone else and passed on, we +want its recipients to know that what they have is not the original, so +that any problems introduced by others will not reflect on the original +authors' reputations. + + Finally, any free program is threatened constantly by software +patents. We wish to avoid the danger that redistributors of a free +program will individually obtain patent licenses, in effect making the +program proprietary. To prevent this, we have made it clear that any +patent must be licensed for everyone's free use or not licensed at all. + + The precise terms and conditions for copying, distribution and +modification follow. + +TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION +=============================================================== + + 0. This License applies to any program or other work which contains a + notice placed by the copyright holder saying it may be distributed + under the terms of this General Public License. The "Program", + below, refers to any such program or work, and a "work based on the + Program" means either the Program or any derivative work under + copyright law: that is to say, a work containing the Program or a + portion of it, either verbatim or with modifications and/or + translated into another language. (Hereinafter, translation is + included without limitation in the term "modification".) Each + licensee is addressed as "you". + + Activities other than copying, distribution and modification are + not covered by this License; they are outside its scope. The act + of running the Program is not restricted, and the output from the + Program is covered only if its contents constitute a work based on + the Program (independent of having been made by running the + Program). Whether that is true depends on what the Program does. + + 1. You may copy and distribute 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 and disclaimer of warranty; keep intact all the + notices that refer to this License and to the absence of any + warranty; and give any other recipients of the Program a copy of + this License along with the Program. + + 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 Program or any portion of + it, thus forming a work based on the Program, 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. You must cause the modified files to carry prominent notices + stating that you changed the files and the date of any change. + + b. You must cause any work that you distribute or publish, that + in whole or in part contains or is derived from the Program or + any part thereof, to be licensed as a whole at no charge to + all third parties under the terms of this License. + + c. If the modified program normally reads commands interactively + when run, you must cause it, when started running for such + interactive use in the most ordinary way, to print or display + an announcement including an appropriate copyright notice and + a notice that there is no warranty (or else, saying that you + provide a warranty) and that users may redistribute the + program under these conditions, and telling the user how to + view a copy of this License. (Exception: if the Program + itself is interactive but does not normally print such an + announcement, your work based on the Program is not required + to print an announcement.) + + These requirements apply to the modified work as a whole. If + identifiable sections of that work are not derived from the + Program, 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 Program, 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 Program. + + In addition, mere aggregation of another work not based on the + Program with the Program (or with a work based on the Program) on a + volume of a storage or distribution medium does not bring the other + work under the scope of this License. + + 3. You may copy and distribute the Program (or a work based on it, + under Section 2) in object code or executable form under the terms + of Sections 1 and 2 above provided that you also do one of the + following: + + a. 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; or, + + b. Accompany it with a written offer, valid for at least three + years, to give any third party, for a charge no more than your + cost of physically performing source distribution, a complete + machine-readable copy of the corresponding source code, to be + distributed under the terms of Sections 1 and 2 above on a + medium customarily used for software interchange; or, + + c. Accompany it with the information you received as to the offer + to distribute corresponding source code. (This alternative is + allowed only for noncommercial distribution and only if you + received the program in object code or executable form with + such an offer, in accord with Subsection b above.) + + The source code for a work means the preferred form of the work for + making modifications to it. For an executable work, 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 executable. + However, as a special exception, the source code 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. + + If distribution of executable or 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 counts as + distribution of the source code, even though third parties are not + compelled to copy the source along with the object code. + + 4. You may not copy, modify, sublicense, or distribute the Program + except as expressly provided under this License. Any attempt + otherwise to copy, modify, sublicense or distribute the Program 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. + + 5. 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 Program or its derivative works. These actions + are prohibited by law if you do not accept this License. + Therefore, by modifying or distributing the Program (or any work + based on the Program), you indicate your acceptance of this License + to do so, and all its terms and conditions for copying, + distributing or modifying the Program or works based on it. + + 6. Each time you redistribute the Program (or any work based on the + Program), the recipient automatically receives a license from the + original licensor to copy, distribute or modify the Program 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 to this License. + + 7. 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 + Program at all. For example, if a patent license would not permit + royalty-free redistribution of the Program 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 Program. + + 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. + + 8. If the distribution and/or use of the Program is restricted in + certain countries either by patents or by copyrighted interfaces, + the original copyright holder who places the Program 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. + + 9. The Free Software Foundation may publish revised and/or new + versions of the 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 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 Program does not + specify a version number of this License, you may choose any + version ever published by the Free Software Foundation. + + 10. If you wish to incorporate parts of the Program into other free + programs whose distribution conditions are different, 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 + + 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, 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. + + 12. 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 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. + + END OF TERMS AND CONDITIONS + +Appendix: 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 +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 PROGRAM'S NAME AND A BRIEF IDEA OF WHAT IT DOES. + Copyright (C) YYYY 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 2 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 . + + Also add information on how to contact you by electronic and paper +mail. + + If the program is interactive, make it output a short notice like +this when it starts in an interactive mode: + + Gnomovision version 69, Copyright (C) YEAR NAME OF AUTHOR + Gnomovision 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, the +commands you use may be called something other than ‘show w’ and ‘show +c’; they could even be mouse-clicks or menu items--whatever suits your +program. + + You should also get your employer (if you work as a programmer) or +your school, if any, to sign a "copyright disclaimer" for the program, +if necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the program + `Gnomovision' (which makes passes at compilers) written by James Hacker. + + SIGNATURE OF MOE GHOUL, 1 April 1989 + Moe Ghoul, President of Vice + + This 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. + + +File: autosprintf.info, Node: GNU FDL, Prev: GNU GPL, Up: Licenses + +A.3 GNU Free Documentation License +================================== + + Version 1.3, 3 November 2008 + + Copyright © 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. + + + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + 0. PREAMBLE + + The purpose of this License is to make a manual, textbook, or other + functional and useful document “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. + + 1. 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 + ASCII without markup, Texinfo input format, LaTeX input format, + SGML or XML using a publicly available DTD, and standard-conforming + simple HTML, PostScript or PDF designed for human modification. + Examples of transparent image formats include PNG, XCF and JPG. + Opaque formats include proprietary formats that can be read and + edited only by proprietary word processors, SGML or XML for which + the DTD and/or processing tools are not generally available, and + the machine-generated HTML, PostScript or 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. + + The "publisher" means any person or entity that distributes copies + of the Document to the public. + + 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. + + 2. 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. + + 3. 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. + + 4. 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: + + A. 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. + + B. 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. + + C. State on the Title page the name of the publisher of the + Modified Version, as the publisher. + + D. Preserve all the copyright notices of the Document. + + E. Add an appropriate copyright notice for your modifications + adjacent to the other copyright notices. + + F. 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. + + G. Preserve in that license notice the full lists of Invariant + Sections and required Cover Texts given in the Document's + license notice. + + H. Include an unaltered copy of this License. + + I. 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. + + J. 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. + + K. 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. + + L. 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. + + M. Delete any section Entitled "Endorsements". Such a section + may not be included in the Modified Version. + + N. Do not retitle any existing section to be Entitled + "Endorsements" or to conflict in title with any Invariant + Section. + + O. Preserve any Warranty Disclaimers. + + 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. + + 5. 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." + + 6. 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. + + 7. 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. + + 8. 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. + + 9. TERMINATION + + You may not copy, modify, sublicense, or distribute the Document + except as expressly provided under this License. Any attempt + otherwise to copy, modify, sublicense, or distribute it is void, + and will automatically terminate your rights under this License. + + 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, receipt of a copy of some or all of the + same material does not give you any rights to use it. + + 10. 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 + . + + 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. If the Document specifies that a proxy can + decide which future versions of this License can be used, that + proxy's public statement of acceptance of a version permanently + authorizes you to choose that version for the Document. + + 11. RELICENSING + + "Massive Multiauthor Collaboration Site" (or "MMC Site") means any + World Wide Web server that publishes copyrightable works and also + provides prominent facilities for anybody to edit those works. A + public wiki that anybody can edit is an example of such a server. + A "Massive Multiauthor Collaboration" (or "MMC") contained in the + site means any set of copyrightable works thus published on the MMC + site. + + "CC-BY-SA" means the Creative Commons Attribution-Share Alike 3.0 + license published by Creative Commons Corporation, a not-for-profit + corporation with a principal place of business in San Francisco, + California, as well as future copyleft versions of that license + published by that same organization. + + "Incorporate" means to publish or republish a Document, in whole or + in part, as part of another Document. + + An MMC is "eligible for relicensing" if it is licensed under this + License, and if all works that were first published under this + License somewhere other than this MMC, and subsequently + incorporated in whole or in part into the MMC, (1) had no cover + texts or invariant sections, and (2) were thus incorporated prior + to November 1, 2008. + + The operator of an MMC Site may republish an MMC contained in the + site under CC-BY-SA on the same site at any time before August 1, + 2009, provided the MMC is eligible for relicensing. + +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: + + Copyright (C) YEAR YOUR NAME. + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.3 + 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''. + + If you have Invariant Sections, Front-Cover Texts and Back-Cover +Texts, replace the "with...Texts." line with this: + + with the Invariant Sections being LIST THEIR TITLES, with + the Front-Cover Texts being LIST, and with the Back-Cover Texts + being LIST. + + 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. + + + +Tag Table: +Node: Top1359 +Node: Introduction1729 +Node: Class autosprintf2913 +Node: Using autosprintf3979 +Node: Licenses4838 +Node: GNU LGPL6591 +Node: GNU GPL34608 +Node: GNU FDL53772 + +End Tag Table + + +Local Variables: +coding: utf-8 +End: diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/info/gettext.info b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/info/gettext.info new file mode 100644 index 0000000000000000000000000000000000000000..03d92bd2bd72d25b84262009c7eaad16d7d30d1c --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/info/gettext.info @@ -0,0 +1,21938 @@ +This is gettext.info, produced by makeinfo version 7.1 from +gettext.texi. + + Copyright (C) 1995-1998, 2001-2025 Free Software Foundation, Inc. + + 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 included in *note GNU FDL::. + + 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 included in *note GNU GPL::. +INFO-DIR-SECTION GNU Gettext Utilities +START-INFO-DIR-ENTRY +* gettext: (gettext). GNU gettext utilities. +* autopoint: (gettext)autopoint Invocation. Copy gettext infrastructure. +* envsubst: (gettext)envsubst Invocation. Expand environment variables. +* gettextize: (gettext)gettextize Invocation. Prepare a package for gettext. +* msgattrib: (gettext)msgattrib Invocation. Select part of a PO file. +* msgcat: (gettext)msgcat Invocation. Combine several PO files. +* msgcmp: (gettext)msgcmp Invocation. Compare a PO file and template. +* msgcomm: (gettext)msgcomm Invocation. Match two PO files. +* msgconv: (gettext)msgconv Invocation. Convert PO file to encoding. +* msgen: (gettext)msgen Invocation. Create an English PO file. +* msgexec: (gettext)msgexec Invocation. Process a PO file. +* msgfilter: (gettext)msgfilter Invocation. Pipe a PO file through a filter. +* msgfmt: (gettext)msgfmt Invocation. Make MO files out of PO files. +* msggrep: (gettext)msggrep Invocation. Select part of a PO file. +* msginit: (gettext)msginit Invocation. Create a fresh PO file. +* msgmerge: (gettext)msgmerge Invocation. Update a PO file from template. +* msgunfmt: (gettext)msgunfmt Invocation. Uncompile MO file into PO file. +* msguniq: (gettext)msguniq Invocation. Unify duplicates for PO file. +* ngettext: (gettext)ngettext Invocation. Translate a message with plural. +* xgettext: (gettext)xgettext Invocation. Extract strings into a PO file. +* ISO639: (gettext)Language Codes. ISO 639 language codes. +* ISO3166: (gettext)Country Codes. ISO 3166 country codes. +END-INFO-DIR-ENTRY + + This file provides documentation for GNU ‘gettext’ utilities. It +also serves as a reference for the free Translation Project. + + +File: gettext.info, Node: Top, Next: Introduction, Up: (dir) + +GNU ‘gettext’ utilities +*********************** + + This manual documents the GNU gettext tools and the GNU libintl +library, version 0.25.1. + +* Menu: + +* Introduction:: Introduction +* Users:: The User's View +* PO Files:: The Format of PO Files +* Sources:: Preparing Program Sources +* Template:: Making the PO Template File +* Creating:: Creating a New PO File +* Updating:: Updating Existing PO Files +* Editing:: Editing PO Files +* Manipulating:: Manipulating PO Files +* Binaries:: Producing Binary MO Files +* Programmers:: The Programmer's View +* Translators:: The Translator's View +* Maintainers:: The Maintainer's View +* Installers:: The Installer's and Distributor's View +* Programming Languages:: Other Programming Languages +* Data Formats:: Other Data Formats +* Conclusion:: Concluding Remarks + +* Language Codes:: ISO 639 language codes +* Country Codes:: ISO 3166 country codes +* Licenses:: Licenses + +* Program Index:: Index of Programs +* Option Index:: Index of Command-Line Options +* Variable Index:: Index of Environment Variables +* PO Mode Index:: Index of Emacs PO Mode Commands +* Autoconf Macro Index:: Index of Autoconf Macros +* Index:: General Index + + -- The Detailed Node Listing -- + +Introduction + +* Why:: The Purpose of GNU ‘gettext’ +* Concepts:: I18n, L10n, and Such +* Aspects:: Aspects in Native Language Support +* Files:: Files Conveying Translations +* Overview:: Overview of GNU ‘gettext’ + +The User's View + +* System Installation:: Questions During Operating System Installation +* Setting the GUI Locale:: How to Specify the Locale Used by GUI Programs +* Setting the POSIX Locale:: How to Specify the Locale According to POSIX +* Working in a Windows console:: Obtaining good output in a Windows console +* Installing Localizations:: How to Install Additional Translations + +Setting the Locale through Environment Variables + +* Locale Names:: How a Locale Specification Looks Like +* Locale Environment Variables:: Which Environment Variable Specfies What +* The LANGUAGE variable:: How to Specify a Priority List of Languages + +Preparing Program Sources + +* Importing:: Importing the ‘gettext’ declaration +* Triggering:: Triggering ‘gettext’ Operations +* Preparing Strings:: Preparing Translatable Strings +* Mark Keywords:: How Marks Appear in Sources +* Marking:: Marking Translatable Strings +* Translator advice:: Adding advice for translators +* c-format Flag:: Telling something about the following string +* Special cases:: Special Cases of Translatable Strings +* Bug Report Address:: Letting Users Report Translation Bugs +* Names:: Marking Proper Names for Translation +* Libraries:: Preparing Library Sources + +Making the PO Template File + +* xgettext Invocation:: Invoking the ‘xgettext’ Program +* Combining POTs:: Combining PO Template Files + +Creating a New PO File + +* msginit Invocation:: Invoking the ‘msginit’ Program +* Header Entry:: Filling in the Header Entry + +Updating Existing PO Files + +* msgmerge Invocation:: Invoking the ‘msgmerge’ Program + +Editing PO Files + +* Web based localization:: Web-based PO editing +* Lokalize:: KDE's PO File Editor +* Gtranslator:: GNOME's PO File Editor +* Poedit:: A simple PO File Editor +* OmegaT:: A powerful Translation Editor +* Virtaal:: The Virtaal Translation Editor +* PO Mode:: Emacs's PO File Editor +* Vim:: Editing PO Files in vim +* Compendium:: Using Translation Compendia + +Emacs's PO File Editor + +* Installation:: Completing GNU ‘gettext’ Installation +* Main PO Commands:: Main Commands +* Entry Positioning:: Entry Positioning +* Normalizing:: Normalizing Strings in Entries +* Translated Entries:: Translated Entries +* Fuzzy Entries:: Fuzzy Entries +* Untranslated Entries:: Untranslated Entries +* Obsolete Entries:: Obsolete Entries +* Modifying Translations:: Modifying Translations +* Modifying Comments:: Modifying Comments +* Subedit:: Mode for Editing Translations +* C Sources Context:: C Sources Context +* Auxiliary:: Consulting Auxiliary PO Files + +Using Translation Compendia + +* Creating Compendia:: Merging translations for later use +* Using Compendia:: Using older translations if they fit + +Manipulating PO Files + +* msgcat Invocation:: Invoking the ‘msgcat’ Program +* msgconv Invocation:: Invoking the ‘msgconv’ Program +* msggrep Invocation:: Invoking the ‘msggrep’ Program +* msgfilter Invocation:: Invoking the ‘msgfilter’ Program +* msguniq Invocation:: Invoking the ‘msguniq’ Program +* msgcomm Invocation:: Invoking the ‘msgcomm’ Program +* msgcmp Invocation:: Invoking the ‘msgcmp’ Program +* msgattrib Invocation:: Invoking the ‘msgattrib’ Program +* msgen Invocation:: Invoking the ‘msgen’ Program +* msgexec Invocation:: Invoking the ‘msgexec’ Program +* Colorizing:: Highlighting parts of PO files +* Other tools:: Other tools for manipulating PO files +* libgettextpo:: Writing your own programs that process PO files + +Highlighting parts of PO files + +* The --color option:: Triggering colorized output +* The TERM variable:: The environment variable ‘TERM’ +* The --style option:: The ‘--style’ option +* Style rules:: Style rules for PO files +* Customizing less:: Customizing ‘less’ for viewing PO files + +Producing Binary MO Files + +* msgfmt Invocation:: Invoking the ‘msgfmt’ Program +* msgunfmt Invocation:: Invoking the ‘msgunfmt’ Program +* MO Files:: The Format of GNU MO Files + +The Programmer's View + +* catgets:: About ‘catgets’ +* gettext:: About ‘gettext’ +* Comparison:: Comparing the two interfaces +* Using libintl.a:: Using libintl.a in own programs +* gettext grok:: Being a ‘gettext’ grok +* Temp Programmers:: Temporary Notes for the Programmers Chapter + +About ‘catgets’ + +* Interface to catgets:: The interface +* Problems with catgets:: Problems with the ‘catgets’ interface?! + +About ‘gettext’ + +* Interface to gettext:: The interface +* Ambiguities:: Solving ambiguities +* Locating Catalogs:: Locating message catalog files +* Charset conversion:: How to request conversion to Unicode +* Contexts:: Solving ambiguities in GUI programs +* Plural forms:: Additional functions for handling plurals +* Optimized gettext:: Optimization of the *gettext functions + +Temporary Notes for the Programmers Chapter + +* Temp Implementations:: Temporary - Two Possible Implementations +* Temp catgets:: Temporary - About ‘catgets’ +* Temp WSI:: Temporary - Why a single implementation +* Temp Notes:: Temporary - Notes + +The Translator's View + +* Organization:: Organization +* Responsibilities:: Responsibilities in the Translation Project +* Dialects:: Language dialects +* Translating plural forms:: How to fill in ‘msgstr[0]’, ‘msgstr[1]’ +* Prioritizing messages:: How to find which messages to translate first + +The Maintainer's View + +* Flat and Non-Flat:: Flat or Non-Flat Directory Structures +* Prerequisites:: Prerequisite Works +* gettextize Invocation:: Invoking the ‘gettextize’ Program +* Adjusting Files:: Files You Must Create or Alter +* autoconf macros:: Autoconf macros for use in ‘configure.ac’ +* Version Control Issues:: +* Release Management:: Creating a Distribution Tarball + +Files You Must Create or Alter + +* po/POTFILES.in:: ‘POTFILES.in’ in ‘po/’ +* po/LINGUAS:: ‘LINGUAS’ in ‘po/’ +* po/Makevars:: ‘Makevars’ in ‘po/’ +* po/Rules-*:: Extending ‘Makefile’ in ‘po/’ +* configure.ac:: ‘configure.ac’ at top level +* config.guess:: ‘config.guess’, ‘config.sub’ at top level +* mkinstalldirs:: ‘mkinstalldirs’ at top level +* aclocal:: ‘aclocal.m4’ at top level +* config.h.in:: ‘config.h.in’ at top level +* Makefile:: ‘Makefile.in’ at top level +* src/Makefile:: ‘Makefile.in’ in ‘src/’ +* lib/gettext.h:: ‘gettext.h’ in ‘lib/’ + +Autoconf macros for use in ‘configure.ac’ + +* AM_GNU_GETTEXT:: AM_GNU_GETTEXT in ‘gettext.m4’ +* AM_GNU_GETTEXT_VERSION:: AM_GNU_GETTEXT_VERSION in ‘gettext.m4’ +* AM_GNU_GETTEXT_NEED:: AM_GNU_GETTEXT_NEED in ‘gettext.m4’ +* AM_PO_SUBDIRS:: AM_PO_SUBDIRS in ‘po.m4’ +* AM_XGETTEXT_OPTION:: AM_XGETTEXT_OPTION in ‘po.m4’ +* AM_ICONV:: AM_ICONV in ‘iconv.m4’ + +Integrating with Version Control Systems + +* Distributed Development:: Avoiding version mismatch in distributed development +* Files under Version Control:: Files to put under version control +* Translations under Version Control:: Put PO Files under Version Control +* autopoint Invocation:: Invoking the ‘autopoint’ Program + +Other Programming Languages + +* Language Implementors:: The Language Implementor's View +* Programmers for other Languages:: The Programmer's View +* Translators for other Languages:: The Translator's View +* Maintainers for other Languages:: The Maintainer's View +* List of Programming Languages:: Individual Programming Languages + +The Translator's View + +* c-format:: C Format Strings +* objc-format:: Objective C Format Strings +* c++-format:: C++ Format Strings +* python-format:: Python Format Strings +* java-format:: Java Format Strings +* csharp-format:: C# Format Strings +* javascript-format:: JavaScript Format Strings +* scheme-format:: Scheme Format Strings +* lisp-format:: Lisp Format Strings +* elisp-format:: Emacs Lisp Format Strings +* librep-format:: librep Format Strings +* rust-format:: Rust Format Strings +* go-format:: Go Format Strings +* ruby-format:: Ruby Format Strings +* sh-format:: Shell Format Strings +* awk-format:: awk Format Strings +* lua-format:: Lua Format Strings +* object-pascal-format:: Object Pascal Format Strings +* modula2-format:: Modula-2 Format Strings +* d-format:: D Format Strings +* smalltalk-format:: Smalltalk Format Strings +* qt-format:: Qt Format Strings +* qt-plural-format:: Qt Plural Format Strings +* kde-format:: KDE Format Strings +* kde-kuit-format:: KUIT Format Strings +* boost-format:: Boost Format Strings +* tcl-format:: Tcl Format Strings +* perl-format:: Perl Format Strings +* php-format:: PHP Format Strings +* gcc-internal-format:: GCC internal Format Strings +* gfc-internal-format:: GFC internal Format Strings +* ycp-format:: YCP Format Strings + +Individual Programming Languages + +* C:: C, C++, Objective C +* Python:: Python +* Java:: Java +* C#:: C# +* JavaScript:: JavaScript +* TypeScript:: TypeScript +* Scheme:: GNU guile - Scheme +* Common Lisp:: GNU clisp - Common Lisp +* clisp C:: GNU clisp C sources +* Emacs Lisp:: Emacs Lisp +* librep:: librep +* Rust:: Rust +* Go:: Go +* Ruby:: Ruby +* sh:: sh - Shell Script +* bash:: bash - Bourne-Again Shell Script +* gawk:: GNU awk +* Lua:: Lua +* Pascal:: Pascal - Free Pascal Compiler +* Modula-2:: Modula-2 +* Smalltalk:: GNU Smalltalk +* Vala:: Vala +* wxWidgets:: wxWidgets library +* Tcl:: Tcl - Tk's scripting language +* Perl:: Perl +* PHP:: PHP Hypertext Preprocessor +* Pike:: Pike +* GCC-source:: GNU Compiler Collection sources +* YCP:: YCP - YaST2 scripting language + +sh - Shell Script + +* Preparing Shell Scripts:: Preparing Shell Scripts for Internationalization +* gettext.sh:: Contents of ‘gettext.sh’ +* gettext Invocation:: Invoking the ‘gettext’ program +* ngettext Invocation:: Invoking the ‘ngettext’ program +* envsubst Invocation:: Invoking the ‘envsubst’ program +* eval_gettext Invocation:: Invoking the ‘eval_gettext’ function +* eval_ngettext Invocation:: Invoking the ‘eval_ngettext’ function +* eval_pgettext Invocation:: Invoking the ‘eval_pgettext’ function +* eval_npgettext Invocation:: Invoking the ‘eval_npgettext’ function + +Perl + +* General Problems:: General Problems Parsing Perl Code +* Default Keywords:: Which Keywords Will xgettext Look For? +* Special Keywords:: How to Extract Hash Keys +* Quote-like Expressions:: What are Strings And Quote-like Expressions? +* Interpolation I:: Unsupported String Interpolation +* Interpolation II:: Valid String Interpolation +* Parentheses:: When To Use Parentheses +* Long Lines:: How To Grok with Long Lines +* Perl Pitfalls:: Bugs, Pitfalls, and Things That Do Not Work + +Other Data Formats + +* Internationalizable Data:: Internationalizable Data Formats +* Localized Data:: Localized Data Formats + +Internationalizable Data Formats + +* POT:: POT - Portable Object Template +* RST:: Resource String Table +* Glade:: Glade - GNOME user interface description +* GSettings:: GSettings - GNOME user configuration schema +* AppData:: AppData - freedesktop.org application description +* Preparing ITS Rules:: Preparing Rules for XML Internationalization + +Preparing Rules for XML Internationalization + +* ITS Rules:: Specifying ITS Rules +* Locating Rules:: Specifying where to find the ITS Rules + +Localized Data Formats + +* Editable Message Catalogs:: Editable Message Catalogs +* Compiled Message Catalogs:: Compiled Message Catalogs +* Desktop Entry:: Desktop Entry files +* XML:: XML files + +Editable Message Catalogs + +* PO:: PO - Portable Object +* Java .properties:: Java .properties +* GNUstep .strings:: NeXTstep/GNUstep .strings + +Compiled Message Catalogs + +* MO:: MO - Machine Object +* Java ResourceBundle:: Java ResourceBundle +* C# Satellite Assembly:: C# Satellite Assembly +* C# Resource:: C# Resource +* Tcl message catalog:: Tcl message catalog +* Qt message catalog:: Qt message catalog + +Concluding Remarks + +* History:: History of GNU ‘gettext’ +* The original ABOUT-NLS:: Historical introduction +* References:: Related Readings + +Language Codes + +* Usual Language Codes:: Two-letter ISO 639 language codes +* Rare Language Codes:: Three-letter ISO 639 language codes + +Licenses + +* GNU GPL:: GNU General Public License +* GNU LGPL:: GNU Lesser General Public License +* GNU FDL:: GNU Free Documentation License + + + +File: gettext.info, Node: Introduction, Next: Users, Prev: Top, Up: Top + +1 Introduction +************** + + This chapter explains the goals sought in the creation of GNU +‘gettext’ and the free Translation Project. Then, it explains a few +broad concepts around Native Language Support, and positions message +translation with regard to other aspects of national and cultural +variance, as they apply to programs. It also surveys those files used +to convey the translations. It explains how the various tools interact +in the initial generation of these files, and later, how the maintenance +cycle should usually operate. + + In this manual, we use _he_ when speaking of the programmer or +maintainer, _she_ when speaking of the translator, and _they_ when +speaking of the installers or end users of the translated program. This +is only a convenience for clarifying the documentation. It is +_absolutely_ not meant to imply that some roles are more appropriate to +males or females. Besides, as you might guess, GNU ‘gettext’ is meant +to be useful for people using computers, whatever their sex, race, +religion or nationality! + + Please submit suggestions and corrections + • either in the bug tracker at + + • or by email to ‘bug-gettext@gnu.org’. + +Please include the manual's edition number and update date in your +messages. + +* Menu: + +* Why:: The Purpose of GNU ‘gettext’ +* Concepts:: I18n, L10n, and Such +* Aspects:: Aspects in Native Language Support +* Files:: Files Conveying Translations +* Overview:: Overview of GNU ‘gettext’ + + +File: gettext.info, Node: Why, Next: Concepts, Up: Introduction + +1.1 The Purpose of GNU ‘gettext’ +================================ + + Usually, programs are written and documented in English, and use +English at execution time to interact with users. This is true not only +of GNU software, but also of a great deal of proprietary and free +software. Using a common language is quite handy for communication +between developers, maintainers and users from all countries. On the +other hand, most people are less comfortable with English than with +their own native language, and would prefer to use their mother tongue +for day to day's work, as far as possible. Many would simply _love_ to +see their computer screen showing a lot less of English, and far more of +their own language. + + However, to many people, this dream might appear so far fetched that +they may believe it is not even worth spending time thinking about it. +They have no confidence at all that the dream might ever become true. +Yet some have not lost hope, and have organized themselves. The +Translation Project is a formalization of this hope into a workable +structure, which has a good chance to get all of us nearer the +achievement of a truly multi-lingual set of programs. + + GNU ‘gettext’ is an important step for the Translation Project, as it +is an asset on which we may build many other steps. This package offers +to programmers, translators and even users, a well integrated set of +tools and documentation. Specifically, the GNU ‘gettext’ utilities are +a set of tools that provides a framework within which other free +packages may produce multi-lingual messages. These tools include + + • A set of conventions about how programs should be written to + support message catalogs. + + • A directory and file naming organization for the message catalogs + themselves. + + • A runtime library supporting the retrieval of translated messages. + + • A few stand-alone programs to massage in various ways the sets of + translatable strings, or already translated strings. + + • A library supporting the parsing and creation of files containing + translated messages. + + • A special mode for Emacs(1) which helps preparing these sets and + bringing them up to date. + + GNU ‘gettext’ is designed to minimize the impact of +internationalization on program sources, keeping this impact as small +and hardly noticeable as possible. Internationalization has better +chances of succeeding if it is very light weighted, or at least, appear +to be so, when looking at program sources. + + The Translation Project also uses the GNU ‘gettext’ distribution as a +vehicle for documenting its structure and methods. This goes beyond the +strict technicalities of documenting the GNU ‘gettext’ proper. By so +doing, translators will find in a single place, as far as possible, all +they need to know for properly doing their translating work. Also, this +supplemental documentation might also help programmers, and even curious +users, in understanding how GNU ‘gettext’ is related to the remainder of +the Translation Project, and consequently, have a glimpse at the _big +picture_. + + ---------- Footnotes ---------- + + (1) In this manual, all mentions of Emacs refers to either GNU Emacs +or to XEmacs, which people sometimes call FSF Emacs and Lucid Emacs, +respectively. + + +File: gettext.info, Node: Concepts, Next: Aspects, Prev: Why, Up: Introduction + +1.2 I18n, L10n, and Such +======================== + + Two long words appear all the time when we discuss support of native +language in programs, and these words have a precise meaning, worth +being explained here, once and for all in this document. The words are +_internationalization_ and _localization_. Many people, tired of +writing these long words over and over again, took the habit of writing +“i18n” and “l10n” instead, quoting the first and last letter of each +word, and replacing the run of intermediate letters by a number merely +telling how many such letters there are. But in this manual, in the +sake of clarity, we will patiently write the names in full, each time... + + By “internationalization”, one refers to the operation by which a +program, or a set of programs turned into a package, is made aware of +and able to support multiple languages. This is a generalization +process, by which the programs are untied from calling only English +strings or other English specific habits, and connected to generic ways +of doing the same, instead. Program developers may use various +techniques to internationalize their programs. Some of these have been +standardized. GNU ‘gettext’ offers one of these standards. *Note +Programmers::. + + By “localization”, one means the operation by which, in a set of +programs already internationalized, one gives the program all needed +information so that it can adapt itself to handle its input and output +in a fashion which is correct for some native language and cultural +habits. This is a particularisation process, by which generic methods +already implemented in an internationalized program are used in specific +ways. The programming environment puts several functions to the +programmers disposal which allow this runtime configuration. The formal +description of specific set of cultural habits for some country, +together with all associated translations targeted to the same native +language, is called the “locale” for this language or country. Users +achieve localization of programs by setting proper values to special +environment variables, prior to executing those programs, identifying +which locale should be used. + + In fact, locale message support is only one component of the cultural +data that makes up a particular locale. There are a whole host of +routines and functions provided to aid programmers in developing +internationalized software and which allow them to access the data +stored in a particular locale. When someone presently refers to a +particular locale, they are obviously referring to the data stored +within that particular locale. Similarly, if a programmer is referring +to "accessing the locale routines", they are referring to the complete +suite of routines that access all of the locale's information. + + One uses the expression “Native Language Support”, or merely NLS, for +speaking of the overall activity or feature encompassing both +internationalization and localization, allowing for multi-lingual +interactions in a program. In a nutshell, one could say that +internationalization is the operation by which further localizations are +made possible. + + Also, very roughly said, when it comes to multi-lingual messages, +internationalization is usually taken care of by programmers, and +localization is usually taken care of by translators. + + +File: gettext.info, Node: Aspects, Next: Files, Prev: Concepts, Up: Introduction + +1.3 Aspects in Native Language Support +====================================== + + For a totally multi-lingual distribution, there are many things to +translate beyond output messages. + + • As of today, GNU ‘gettext’ offers a complete toolset for + translating messages output by C programs. Perl scripts and shell + scripts will also need to be translated. Even if there are today + some hooks by which this can be done, these hooks are not + integrated as well as they should be. + + • Some programs, like ‘autoconf’ or ‘bison’, are able to produce + other programs (or scripts). Even if the generating programs + themselves are internationalized, the generated programs they + produce may need internationalization on their own, and this + indirect internationalization could be automated right from the + generating program. In fact, quite usually, generating and + generated programs could be internationalized independently, as the + effort needed is fairly orthogonal. + + • A few programs include textual tables which might need translation + themselves, independently of the strings contained in the program + itself. For example, RFC 1345 gives an English description for + each character which the ‘recode’ program is able to reconstruct at + execution. Since these descriptions are extracted from the RFC by + mechanical means, translating them properly would require a prior + translation of the RFC itself. + + • Almost all programs accept options, which are often worded out so + to be descriptive for the English readers; one might want to + consider offering translated versions for program options as well. + + • Many programs read, interpret, compile, or are somewhat driven by + input files which are texts containing keywords, identifiers, or + replies which are inherently translatable. For example, one may + want ‘gcc’ to allow diacriticized characters in identifiers or use + translated keywords; ‘rm -i’ might accept something else than ‘y’ + or ‘n’ for replies, etc. Even if the program will eventually make + most of its output in the foreign languages, one has to decide + whether the input syntax, option values, etc., are to be localized + or not. + + • The manual accompanying a package, as well as all documentation + files in the distribution, could surely be translated, too. + Translating a manual, with the intent of later keeping up with + updates, is a major undertaking in itself, generally. + + As we already stressed, translation is only one aspect of locales. +Other internationalization aspects are system services and are handled +in GNU ‘libc’. There are many attributes that are needed to define a +country's cultural conventions. These attributes include beside the +country's native language, the formatting of the date and time, the +representation of numbers, the symbols for currency, etc. These local +“rules” are termed the country's locale. The locale represents the +knowledge needed to support the country's native attributes. + + There are a few major areas which may vary between countries and +hence, define what a locale must describe. The following list helps +putting multi-lingual messages into the proper context of other tasks +related to locales. See the GNU ‘libc’ manual for details. + +_Characters and Codesets_ + + The codeset most commonly used through out the USA and most English + speaking parts of the world is the ASCII codeset. However, there + are many characters needed by various locales that are not found + within this codeset. The 8-bit ISO 8859-1 code set has most of the + special characters needed to handle the major European languages. + However, in many cases, choosing ISO 8859-1 is nevertheless not + adequate: it doesn't even handle the major European currency. + Hence each locale will need to specify which codeset they need to + use and will need to have the appropriate character handling + routines to cope with the codeset. + +_Currency_ + + The symbols used vary from country to country as does the position + used by the symbol. Software needs to be able to transparently + display currency figures in the native mode for each locale. + +_Dates_ + + The format of date varies between locales. For example, Christmas + day in 1994 is written as 12/25/94 in the USA and as 25/12/94 in + Australia. Other countries might use ISO 8601 dates, etc. + + Time of the day may be noted as HH:MM, HH.MM, or otherwise. Some + locales require time to be specified in 24-hour mode rather than as + AM or PM. Further, the nature and yearly extent of the Daylight + Saving correction vary widely between countries. + +_Numbers_ + + Numbers can be represented differently in different locales. For + example, the following numbers are all written correctly for their + respective locales: + + 12,345.67 English + 12.345,67 German + 12345,67 French + 1,2345.67 Asia + + Some programs could go further and use different unit systems, like + English units or Metric units, or even take into account variants + about how numbers are spelled in full. + +_Messages_ + + The most obvious area is the language support within a locale. + This is where GNU ‘gettext’ provides the means for developers and + users to easily change the language that the software uses to + communicate to the user. + + These areas of cultural conventions are called _locale categories_. +It is an unfortunate term; _locale aspects_ or _locale feature +categories_ would be a better term, because each "locale category" +describes an area or task that requires localization. The concrete data +that describes the cultural conventions for such an area and for a +particular culture is also called a _locale category_. In this sense, a +locale is composed of several locale categories: the locale category +describing the codeset, the locale category describing the formatting of +numbers, the locale category containing the translated messages, and so +on. + + Components of locale outside of message handling are standardized in +the ISO C standard and the POSIX:2001 standard (also known as the SUSV3 +specification). GNU ‘libc’ fully implements this, and most other modern +systems provide a more or less reasonable support for at least some of +the missing components. + + +File: gettext.info, Node: Files, Next: Overview, Prev: Aspects, Up: Introduction + +1.4 Files Conveying Translations +================================ + + The letters PO in ‘.po’ files means Portable Object, to distinguish +it from ‘.mo’ files, where MO stands for Machine Object. This paradigm, +as well as the PO file format, is inspired by the NLS standard developed +by Uniforum, and first implemented by Sun in their Solaris system. + + PO files are meant to be read and edited by humans, and associate +each original, translatable string of a given package with its +translation in a particular target language. A single PO file is +dedicated to a single target language. If a package supports many +languages, there is one such PO file per language supported, and each +package has its own set of PO files. These PO files are best created by +the ‘xgettext’ program, and later updated or refreshed through the +‘msgmerge’ program. Program ‘xgettext’ extracts all marked messages +from a set of C files and initializes a PO file with empty translations. +Program ‘msgmerge’ takes care of adjusting PO files between releases of +the corresponding sources, commenting obsolete entries, initializing new +ones, and updating all source line references. Files ending with ‘.pot’ +are kind of base translation files found in distributions, in PO file +format. + + MO files are meant to be read by programs, and are binary in nature. +A few systems already offer tools for creating and handling MO files as +part of the Native Language Support coming with the system, but the +format of these MO files is often different from system to system, and +non-portable. The tools already provided with these systems don't +support all the features of GNU ‘gettext’. Therefore GNU ‘gettext’ uses +its own format for MO files. Files ending with ‘.gmo’ are really MO +files, when it is known that these files use the GNU format. + + +File: gettext.info, Node: Overview, Prev: Files, Up: Introduction + +1.5 Overview of GNU ‘gettext’ +============================= + + The following diagram summarizes the relation between the files +handled by GNU ‘gettext’ and the tools acting on these files. It is +followed by somewhat detailed explanations, which you should read while +keeping an eye on the diagram. Having a clear understanding of these +interrelations will surely help programmers, translators and +maintainers. + + Original C Sources ---> Preparation ---> Marked C Sources ---. + | + .---------<--- GNU gettext Library | + .--- make <---+ | + | `---------<--------------------+---------------' + | | + | .-----<--- PACKAGE.pot <--- xgettext <---' .---<--- PO Compendium + | | | ^ + | | `---. | + | `---. +---> PO editor ---. + | +----> msgmerge ------> LANG.po ---->--------' | + | .---' | + | | | + | `-------------<---------------. | + | +--- New LANG.po <--------------------' + | .--- LANG.gmo <--- msgfmt <---' + | | + | `---> install ---> /.../LANG/PACKAGE.mo ---. + | +---> "Hello world!" + `-------> install ---> /.../bin/PROGRAM -------' + + As a programmer, the first step to bringing GNU ‘gettext’ into your +package is identifying, right in the C sources, those strings which are +meant to be translatable, and those which are untranslatable. This +tedious job can be done a little more comfortably using emacs PO mode, +but you can use any means familiar to you for modifying your C sources. +Beside this some other simple, standard changes are needed to properly +initialize the translation library. *Note Sources::, for more +information about all this. + + For newly written software the strings of course can and should be +marked while writing it. The ‘gettext’ approach makes this very easy. +Simply put the following lines at the beginning of each file or in a +central header file: + + #define _(String) (String) + #define N_(String) String + #define textdomain(Domain) + #define bindtextdomain(Package, Directory) + +Doing this allows you to prepare the sources for internationalization. +Later when you feel ready for the step to use the ‘gettext’ library +simply replace these definitions by the following: + + #include + #define _(String) gettext (String) + #define gettext_noop(String) String + #define N_(String) gettext_noop (String) + +and link against ‘libintl.a’ or ‘libintl.so’. Note that on GNU systems, +you don't need to link with ‘libintl’ because the ‘gettext’ library +functions are already contained in GNU libc. That is all you have to +change. + + Once the C sources have been modified, the ‘xgettext’ program is used +to find and extract all translatable strings, and create a PO template +file out of all these. This ‘PACKAGE.pot’ file contains all original +program strings. It has sets of pointers to exactly where in C sources +each string is used. All translations are set to empty. The letter ‘t’ +in ‘.pot’ marks this as a Template PO file, not yet oriented towards any +particular language. *Note xgettext Invocation::, for more details +about how one calls the ‘xgettext’ program. If you are _really_ lazy, +you might be interested at working a lot more right away, and preparing +the whole distribution setup (*note Maintainers::). By doing so, you +spare yourself typing the ‘xgettext’ command, as ‘make’ should now +generate the proper things automatically for you! + + The first time through, there is no ‘LANG.po’ yet, so the ‘msgmerge’ +step may be skipped and replaced by a mere copy of ‘PACKAGE.pot’ to +‘LANG.po’, where LANG represents the target language. See *note +Creating:: for details. + + Then comes the initial translation of messages. Translation in +itself is a whole matter, still exclusively meant for humans, and whose +complexity far overwhelms the level of this manual. Nevertheless, a few +hints are given in some other chapter of this manual (*note +Translators::). You will also find there indications about how to +contact translating teams, or becoming part of them, for sharing your +translating concerns with others who target the same native language. + + While adding the translated messages into the ‘LANG.po’ PO file, if +you are not using one of the dedicated PO file editors (*note +Editing::), you are on your own for ensuring that your efforts fully +respect the PO file format, and quoting conventions (*note PO Files::). +This is surely not an impossible task, as this is the way many people +have handled PO files around 1995. On the other hand, by using a PO +file editor, most details of PO file format are taken care of for you, +but you have to acquire some familiarity with PO file editor itself. + + If some common translations have already been saved into a compendium +PO file, translators may use PO mode for initializing untranslated +entries from the compendium, and also save selected translations into +the compendium, updating it (*note Compendium::). Compendium files are +meant to be exchanged between members of a given translation team. + + Programs, or packages of programs, are dynamic in nature: users write +bug reports and suggestion for improvements, maintainers react by +modifying programs in various ways. The fact that a package has already +been internationalized should not make maintainers shy of adding new +strings, or modifying strings already translated. They just do their +job the best they can. For the Translation Project to work smoothly, it +is important that maintainers do not carry translation concerns on their +already loaded shoulders, and that translators be kept as free as +possible of programming concerns. + + The only concern maintainers should have is carefully marking new +strings as translatable, when they should be, and do not otherwise worry +about them being translated, as this will come in proper time. +Consequently, when programs and their strings are adjusted in various +ways by maintainers, and for matters usually unrelated to translation, +‘xgettext’ would construct ‘PACKAGE.pot’ files which are evolving over +time, so the translations carried by ‘LANG.po’ are slowly fading out of +date. + + It is important for translators (and even maintainers) to understand +that package translation is a continuous process in the lifetime of a +package, and not something which is done once and for all at the start. +After an initial burst of translation activity for a given package, +interventions are needed once in a while, because here and there, +translated entries become obsolete, and new untranslated entries appear, +needing translation. + + The ‘msgmerge’ program has the purpose of refreshing an already +existing ‘LANG.po’ file, by comparing it with a newer ‘PACKAGE.pot’ +template file, extracted by ‘xgettext’ out of recent C sources. The +refreshing operation adjusts all references to C source locations for +strings, since these strings move as programs are modified. Also, +‘msgmerge’ comments out as obsolete, in ‘LANG.po’, those already +translated entries which are no longer used in the program sources +(*note Obsolete Entries::). It finally discovers new strings and +inserts them in the resulting PO file as untranslated entries (*note +Untranslated Entries::). *Note msgmerge Invocation::, for more +information about what ‘msgmerge’ really does. + + Whatever route or means taken, the goal is to obtain an updated +‘LANG.po’ file offering translations for all strings. + + The temporal mobility, or fluidity of PO files, is an integral part +of the translation game, and should be well understood, and accepted. +People resisting it will have a hard time participating in the +Translation Project, or will give a hard time to other participants! In +particular, maintainers should relax and include all available official +PO files in their distributions, even if these have not recently been +updated, without exerting pressure on the translator teams to get the +job done. The pressure should rather come from the community of users +speaking a particular language, and maintainers should consider +themselves fairly relieved of any concern about the adequacy of +translation files. On the other hand, translators should reasonably try +updating the PO files they are responsible for, while the package is +undergoing pretest, prior to an official distribution. + + Once the PO file is complete and dependable, the ‘msgfmt’ program is +used for turning the PO file into a machine-oriented format, which may +yield efficient retrieval of translations by the programs of the +package, whenever needed at runtime (*note MO Files::). *Note msgfmt +Invocation::, for more information about all modes of execution for the +‘msgfmt’ program. + + Finally, the modified and marked C sources are compiled and linked +with the GNU ‘gettext’ library, usually through the operation of ‘make’, +given a suitable ‘Makefile’ exists for the project, and the resulting +executable is installed somewhere users will find it. The MO files +themselves should also be properly installed. Given the appropriate +environment variables are set (*note Setting the POSIX Locale::), the +program should localize itself automatically, whenever it executes. + + Shipping the MO files as separate files, as opposed to embedding them +in the executable, has three advantages: + • For the users: It allows users to prepare and install new + translations, without needing to rebuild the package (which may + require developer skills). + • For the distributors: It allows distributions to ship translations + that were produced after the release of the package. + • For the vendors of complex packages: When lengthy quality assurance + steps are required before making a release, this quality assurance + can start before the translators have produced the translations, + shortening the critical path of the release schedule by a week or + two. +Embedding the translations in the executable, whether by the ISO C +‘#embed’ directive or through other means, would deprive users without +developer skills of the ability to fix translation mistakes and add new +translations. + + The remainder of this manual has the purpose of explaining in depth +the various steps outlined above. + + +File: gettext.info, Node: Users, Next: PO Files, Prev: Introduction, Up: Top + +2 The User's View +***************** + + Nowadays, when users log into a computer, they usually find that all +their programs show messages in their native language - at least for +users of languages with an active free software community, like French +or German; to a lesser extent for languages with a smaller participation +in free software and the GNU project, like Hindi and Filipino. + + How does this work? How can the user influence the language that is +used by the programs? This chapter will answer it. + +* Menu: + +* System Installation:: Questions During Operating System Installation +* Setting the GUI Locale:: How to Specify the Locale Used by GUI Programs +* Setting the POSIX Locale:: How to Specify the Locale According to POSIX +* Working in a Windows console:: Obtaining good output in a Windows console +* Installing Localizations:: How to Install Additional Translations + + +File: gettext.info, Node: System Installation, Next: Setting the GUI Locale, Up: Users + +2.1 Operating System Installation +================================= + + The default language is often already specified during operating +system installation. When the operating system is installed, the +installer typically asks for the language used for the installation +process and, separately, for the language to use in the installed +system. Some OS installers only ask for the language once. + + This determines the system-wide default language for all users. But +the installers often give the possibility to install extra localizations +for additional languages. For example, the localizations of KDE (the K +Desktop Environment) and LibreOffice are often bundled separately, as +one installable package per language. + + At this point it is good to consider the intended use of the machine: +If it is a machine designated for personal use, additional localizations +are probably not necessary. If, however, the machine is in use in an +organization or company that has international relationships, one can +consider the needs of guest users. If you have a guest from abroad, for +a week, what could be his preferred locales? It may be worth installing +these additional localizations ahead of time, since they cost only a bit +of disk space at this point. + + The system-wide default language is the locale configuration that is +used when a new user account is created. But the user can have his own +locale configuration that is different from the one of the other users +of the same machine. He can specify it, typically after the first +login, as described in the next section. + + +File: gettext.info, Node: Setting the GUI Locale, Next: Setting the POSIX Locale, Prev: System Installation, Up: Users + +2.2 Setting the Locale Used by GUI Programs +=========================================== + + The immediately available programs in a user's desktop come from a +group of programs called a "desktop environment"; it usually includes +the window manager, a web browser, a text editor, and more. The most +common free desktop environments are KDE, GNOME, and Xfce. + + The locale used by GUI programs of the desktop environment can be +specified in a configuration screen called "control center", "language +settings" or "country settings". + + Individual GUI programs that are not part of the desktop environment +can have their locale specified either in a settings panel, or through +environment variables. + + For some programs, it is possible to specify the locale through +environment variables, possibly even to a different locale than the +desktop's locale. This means, instead of starting a program through a +menu or from the file system, you can start it from the command-line, +after having set some environment variables. The environment variables +can be those specified in the next section (*note Setting the POSIX +Locale::); for some versions of KDE, however, the locale is specified +through a variable ‘KDE_LANG’, rather than ‘LANG’ or ‘LC_ALL’. + + +File: gettext.info, Node: Setting the POSIX Locale, Next: Working in a Windows console, Prev: Setting the GUI Locale, Up: Users + +2.3 Setting the Locale through Environment Variables +==================================================== + + As a user, if your language has been installed for this package, in +the simplest case, you only have to set the ‘LANG’ environment variable +to the appropriate ‘LL_CC’ combination. For example, let's suppose that +you speak German and live in Germany. At the shell prompt, merely +execute ‘setenv LANG de_DE’ (in ‘csh’), ‘export LANG; LANG=de_DE’ (in +‘sh’) or ‘export LANG=de_DE’ (in ‘bash’). This can be done from your +‘.login’ or ‘.profile’ file, once and for all. + +* Menu: + +* Locale Names:: How a Locale Specification Looks Like +* Locale Environment Variables:: Which Environment Variable Specfies What +* The LANGUAGE variable:: How to Specify a Priority List of Languages + + +File: gettext.info, Node: Locale Names, Next: Locale Environment Variables, Up: Setting the POSIX Locale + +2.3.1 Locale Names +------------------ + + A locale name usually has the form ‘LL_CC’. Here + + • ‘LL’ is an ISO 639 two-letter language code. For some languages, a + two-letter code does not exist, and a three-letter code is used + instead. + • ‘CC’ is an ISO 3166 two-letter code of a country or territory. + +For example, for German in Germany, LL is ‘de’, and CC is ‘DE’. You +find a list of the language codes in appendix *note Language Codes:: and +a list of the country codes in appendix *note Country Codes::. + + You might think that the country code specification is redundant. +But in fact, some languages have dialects in different countries. For +example, ‘de_AT’ is used for Austria, and ‘pt_BR’ for Brazil. The +country code serves to distinguish the dialects. + + Many locale names have an extended syntax ‘LL_CC.ENCODING’ that also +specifies the character encoding. These are in use because between 2000 +and 2005, most users have switched to locales in UTF-8 encoding. For +example, the German locale on glibc systems is nowadays ‘de_DE.UTF-8’. +The older name ‘de_DE’ still refers to the German locale as of 2000 that +stores characters in ISO-8859-1 encoding - a text encoding that cannot +even accommodate the Euro currency sign. + + Some locale names use ‘LL_CC@VARIANT’ instead of ‘LL_CC’. The +‘@VARIANT’ can denote any kind of characteristics that is not already +implied by the language LL and the country CC. It can denote a +particular monetary unit. For example, on glibc systems, ‘de_DE@euro’ +denotes the locale that uses the Euro currency, in contrast to the older +locale ‘de_DE’ which implies the use of the currency before 2002. It +can also denote a dialect of the language, or the script used to write +text (for example, ‘sr_RS@latin’ uses the Latin script, whereas ‘sr_RS’ +uses the Cyrillic script to write Serbian), or the orthography rules, or +similar. + + On other systems, some variations of this scheme are used, such as +‘LL’. You can get the list of locales supported by your system for your +language by running the command ‘locale -a | grep '^LL'’. + + There are also two special locales: + • The locale called ‘C’. + When it is used, it disables all localization: in this locale, all + programs standardized by POSIX use English messages and an + unspecified character encoding (often US-ASCII, but sometimes also + ISO-8859-1 or UTF-8, depending on the operating system). + • The locale called ‘C.UTF-8’. + This locale exists on all modern GNU and Unix systems, but not on + all operating systems. When it is used, it disables all + localization as well. It uses UTF-8 as character encoding. + + +File: gettext.info, Node: Locale Environment Variables, Next: The LANGUAGE variable, Prev: Locale Names, Up: Setting the POSIX Locale + +2.3.2 Locale Environment Variables +---------------------------------- + + A locale is composed of several _locale categories_, see *note +Aspects::. When a program looks up locale dependent values, it does +this according to the following environment variables, in priority +order: + + 1. ‘LANGUAGE’ + 2. ‘LC_ALL’ + 3. ‘LC_xxx’, according to selected locale category: ‘LC_CTYPE’, + ‘LC_NUMERIC’, ‘LC_TIME’, ‘LC_COLLATE’, ‘LC_MONETARY’, + ‘LC_MESSAGES’, ... + 4. ‘LANG’ + + Variables whose value is set but is empty are ignored in this lookup. + + ‘LANG’ is the normal environment variable for specifying a locale. +As a user, you normally set this variable (unless some of the other +variables have already been set by the system, in ‘/etc/profile’ or +similar initialization files). + + ‘LC_CTYPE’, ‘LC_NUMERIC’, ‘LC_TIME’, ‘LC_COLLATE’, ‘LC_MONETARY’, +‘LC_MESSAGES’, and so on, are the environment variables meant to +override ‘LANG’ and affecting a single locale category only. For +example, assume you are a Swedish user in Spain, and you want your +programs to handle numbers and dates according to Spanish conventions, +and only the messages should be in Swedish. Then you could create a +locale named ‘sv_ES’ or ‘sv_ES.UTF-8’ by use of the ‘localedef’ program. +But it is simpler, and achieves the same effect, to set the ‘LANG’ +variable to ‘es_ES.UTF-8’ and the ‘LC_MESSAGES’ variable to +‘sv_SE.UTF-8’; these two locales come already preinstalled with the +operating system. + + ‘LC_ALL’ is an environment variable that overrides all of these. It +is typically used in scripts that run particular programs. For example, +‘configure’ scripts generated by GNU autoconf use ‘LC_ALL’ to make sure +that the configuration tests don't operate in locale dependent ways. + + Some systems, unfortunately, set ‘LC_ALL’ in ‘/etc/profile’ or in +similar initialization files. As a user, you therefore have to unset +this variable if you want to set ‘LANG’ and optionally some of the other +‘LC_xxx’ variables. + + The ‘LANGUAGE’ variable is described in the next subsection. + + +File: gettext.info, Node: The LANGUAGE variable, Prev: Locale Environment Variables, Up: Setting the POSIX Locale + +2.3.3 Specifying a Priority List of Languages +--------------------------------------------- + + Not all programs have translations for all languages. By default, an +English message is shown in place of a nonexistent translation. If you +understand other languages, you can set up a priority list of languages. +This is done through a different environment variable, called +‘LANGUAGE’. GNU ‘gettext’ gives preference to ‘LANGUAGE’ over ‘LC_ALL’ +and ‘LANG’ for the purpose of message handling, but you still need to +have ‘LANG’ (or ‘LC_ALL’) set to the primary language; this is required +by other parts of the system libraries. For example, some Swedish users +who would rather read translations in German than English for when +Swedish is not available, set ‘LANGUAGE’ to ‘sv:de’ while leaving ‘LANG’ +to ‘sv_SE’. + + Special advice for Norwegian users: The language code for Norwegian +bokmål changed from ‘no’ to ‘nb’ back in 2003. Most of the message +catalogs for this language are installed under ‘nb’. But in order to +also use the older ones installed under ‘no’, it is recommended for +Norwegian users to set ‘LANGUAGE’ to ‘nb:no’. + + In the ‘LANGUAGE’ environment variable, but not in the other +environment variables, ‘LL_CC’ combinations can be abbreviated as ‘LL’ +to denote the language's main dialect. For example, ‘de’ is equivalent +to ‘de_DE’ (German as spoken in Germany), and ‘pt’ to ‘pt_PT’ +(Portuguese as spoken in Portugal) in this context. + + Special advice for Chinese users: Users who want to see translations +with Simplified Chinese characters should set ‘LANGUAGE’ to ‘zh_CN’, +whereas users who want to see translations with Traditional Chinese +characters should set ‘LANGUAGE’ to ‘zh_TW’. Chinese users in Singapore +will want to set it to ‘zh_SG:zh_CN’, Chinese users in Hong Kong will +want to set it to ‘zh_HK:zh_TW’, and Chinese users in Macao will want to +set it to ‘zh_MO:zh_TW’. Here ‘zh_CN’ or ‘zh_TW’, respectively, acts as +fallback, since only few packages have translations for ‘zh_SG’, +‘zh_HK’, or ‘zh_MO’. + + Note: The variable ‘LANGUAGE’ is ignored if the locale is set to ‘C’. +In other words, you have to first enable localization, by setting ‘LANG’ +(or ‘LC_ALL’) to a value other than ‘C’, before you can use a language +priority list through the ‘LANGUAGE’ variable. + + +File: gettext.info, Node: Working in a Windows console, Next: Installing Localizations, Prev: Setting the POSIX Locale, Up: Users + +2.4 Obtaining good output in a Windows console +============================================== + + On Windows, consoles such as the one started by the ‘cmd.exe’ program +do input and output in an encoding, called "OEM code page", that is +different from the encoding that text-mode programs usually use, called +"ANSI code page". (Note: This problem does not exist for Cygwin +consoles; these consoles do input and output in the UTF-8 encoding.) As +a workaround, you may request that the programs produce output in this +"OEM" encoding. To do so, set the environment variable ‘OUTPUT_CHARSET’ +to the "OEM" encoding, through a command such as + set OUTPUT_CHARSET=CP850 + Note: This has an effect only on strings looked up in message +catalogs; other categories of text are usually not affected by this +setting. Note also that this environment variable also affects output +sent to a file or to a pipe; output to a file is most often expected to +be in the "ANSI" or in the UTF-8 encoding. + + Here are examples of the "ANSI" and "OEM" code pages: + +Territories ANSI encoding OEM encoding + +--------------------------------------------------------------------------- +Western Europe CP1252 CP850 +Slavic countries (Latin 2) CP1250 CP852 +Baltic countries CP1257 CP775 +Russia CP1251 CP866 + + +File: gettext.info, Node: Installing Localizations, Prev: Working in a Windows console, Up: Users + +2.5 Installing Translations for Particular Programs +=================================================== + + Languages are not equally well supported in all packages using GNU +‘gettext’, and more translations are added over time. Usually, you use +the translations that are shipped with the operating system or with +particular packages that you install afterwards. But you can also +install newer localizations directly. For doing this, you will need an +understanding where each localization file is stored on the file system. + + For programs that participate in the Translation Project, you can +start looking for translations here: +. + + For programs that are part of the KDE project, the starting point is: +. + + For programs that are part of the GNOME project, the starting point +is: . + + For other programs, you may check whether the program's source code +package contains some ‘LL.po’ files; often they are kept together in a +directory called ‘po/’. Each ‘LL.po’ file contains the message +translations for the language whose abbreviation of LL. + + +File: gettext.info, Node: PO Files, Next: Sources, Prev: Users, Up: Top + +3 The Format of PO Files +************************ + + The GNU ‘gettext’ toolset helps programmers and translators at +producing, updating and using translation files, mainly those PO files +which are textual, editable files. This chapter explains the format of +PO files. + + A PO file is made up of many entries, each entry holding the relation +between an original untranslated string and its corresponding +translation. All entries in a given PO file usually pertain to a single +project, and all translations are expressed in a single target language. +One PO file “entry” has the following schematic structure: + + WHITE-SPACE + # TRANSLATOR-COMMENTS + #. EXTRACTED-COMMENTS + #: REFERENCE... + #, FLAG... + #| msgid PREVIOUS-UNTRANSLATED-STRING + msgid UNTRANSLATED-STRING + msgstr TRANSLATED-STRING + + The general structure of a PO file should be well understood by the +translator. When using PO mode, very little has to be known about the +format details, as PO mode takes care of them for her. + + A simple entry can look like this: + + #: lib/error.c:116 + msgid "Unknown system error" + msgstr "Error desconegut del sistema" + + Entries begin with some optional white space. Usually, when +generated through GNU ‘gettext’ tools, there is exactly one blank line +between entries. Then comments follow, on lines all starting with the +character ‘#’. There are two kinds of comments: those which have some +white space immediately following the ‘#’ - the TRANSLATOR COMMENTS -, +which comments are created and maintained exclusively by the translator, +and those which have some non-white character just after the ‘#’ - the +AUTOMATIC COMMENTS -, which comments are created and maintained +automatically by GNU ‘gettext’ tools. Comment lines starting with ‘#.’ +contain comments given by the programmer, directed at the translator; +these comments are called EXTRACTED COMMENTS because the ‘xgettext’ +program extracts them from the program's source code. Comment lines +starting with ‘#:’ contain references to the program's source code. +Comment lines starting with ‘#,’ contain flags; more about these below. +Comment lines starting with ‘#|’ contain the previous untranslated +string for which the translator gave a translation. + + All comments, of either kind, are optional. + + References to the program's source code, in lines that start with +‘#:’, are of the form ‘FILE_NAME:LINE_NUMBER’ or just FILE_NAME. If the +FILE_NAME contains spaces. it is enclosed within Unicode characters +U+2068 and U+2069. + + After white space and comments, entries show two strings, namely +first the untranslated string as it appears in the original program +sources, and then, the translation of this string. The original string +is introduced by the keyword ‘msgid’, and the translation, by ‘msgstr’. +The two strings, untranslated and translated, are quoted in various ways +in the PO file, using ‘"’ delimiters and ‘\’ escapes, but the translator +does not really have to pay attention to the precise quoting format, as +PO mode fully takes care of quoting for her. + + The ‘msgid’ strings, as well as automatic comments, are produced and +managed by other GNU ‘gettext’ tools, and PO mode does not provide means +for the translator to alter these. The most she can do is merely +deleting them, and only by deleting the whole entry. On the other hand, +the ‘msgstr’ string, as well as translator comments, are really meant +for the translator, and PO mode gives her the full control she needs. + + The comment lines beginning with ‘#,’ are special because they are +not completely ignored by the programs as comments generally are. The +comma separated list of FLAGs is used by the ‘msgfmt’ program to give +the user some better diagnostic messages. Currently there are two forms +of flags defined: + +‘fuzzy’ + This flag can be generated by the ‘msgmerge’ program or it can be + inserted by the translator herself. It shows that the ‘msgstr’ + string might not be a correct translation (anymore). Only the + translator can judge if the translation requires further + modification, or is acceptable as is. Once satisfied with the + translation, she then removes this ‘fuzzy’ attribute. The + ‘msgmerge’ program inserts this when it combined the ‘msgid’ and + ‘msgstr’ entries after fuzzy search only. *Note Fuzzy Entries::. + +‘c-format’ +‘no-c-format’ + These flags should not be added by a human. Instead only the + ‘xgettext’ program adds them. In an automated PO file processing + system as proposed here, the user's changes would be thrown away + again as soon as the ‘xgettext’ program generates a new template + file. + + The ‘c-format’ flag indicates that the untranslated string and the + translation are supposed to be C format strings. The ‘no-c-format’ + flag indicates that they are not C format strings, even though the + untranslated string happens to look like a C format string (with + ‘%’ directives). + + When the ‘c-format’ flag is given for a string the ‘msgfmt’ program + does some more tests to check the validity of the translation. + *Note msgfmt Invocation::, *note c-format Flag:: and *note + c-format::. + +‘objc-format’ +‘no-objc-format’ + Likewise for Objective C, see *note objc-format::. + +‘c++-format’ +‘no-c++-format’ + Likewise for C++, see *note c++-format::. + +‘python-format’ +‘no-python-format’ + Likewise for Python, see *note python-format::. + +‘python-brace-format’ +‘no-python-brace-format’ + Likewise for Python brace, see *note python-format::. + +‘java-format’ +‘no-java-format’ + Likewise for Java ‘MessageFormat’ format strings, see *note + java-format::. + +‘java-printf-format’ +‘no-java-printf-format’ + Likewise for Java ‘printf’ format strings, see *note java-format::. + +‘csharp-format’ +‘no-csharp-format’ + Likewise for C#, see *note csharp-format::. + +‘javascript-format’ +‘no-javascript-format’ + Likewise for JavaScript, see *note javascript-format::. + +‘scheme-format’ +‘no-scheme-format’ + Likewise for Scheme, see *note scheme-format::. + +‘lisp-format’ +‘no-lisp-format’ + Likewise for Lisp, see *note lisp-format::. + +‘elisp-format’ +‘no-elisp-format’ + Likewise for Emacs Lisp, see *note elisp-format::. + +‘librep-format’ +‘no-librep-format’ + Likewise for librep, see *note librep-format::. + +‘rust-format’ +‘no-rust-format’ + Likewise for Rust, see *note rust-format::. + +‘go-format’ +‘no-go-format’ + Likewise for Go, see *note go-format::. + +‘ruby-format’ +‘no-ruby-format’ + Likewise for Ruby, see *note ruby-format::. + +‘sh-format’ +‘no-sh-format’ + Likewise for Shell, see *note sh-format::. + +‘awk-format’ +‘no-awk-format’ + Likewise for awk, see *note awk-format::. + +‘lua-format’ +‘no-lua-format’ + Likewise for Lua, see *note lua-format::. + +‘object-pascal-format’ +‘no-object-pascal-format’ + Likewise for Object Pascal, see *note object-pascal-format::. + +‘modula2-format’ +‘no-modula2-format’ + Likewise for Modula-2, see *note modula2-format::. + +‘d-format’ +‘no-d-format’ + Likewise for D, see *note d-format::. + +‘smalltalk-format’ +‘no-smalltalk-format’ + Likewise for Smalltalk, see *note smalltalk-format::. + +‘qt-format’ +‘no-qt-format’ + Likewise for Qt, see *note qt-format::. + +‘qt-plural-format’ +‘no-qt-plural-format’ + Likewise for Qt plural forms, see *note qt-plural-format::. + +‘kde-format’ +‘no-kde-format’ + Likewise for KDE, see *note kde-format::. + +‘boost-format’ +‘no-boost-format’ + Likewise for Boost, see *note boost-format::. + +‘tcl-format’ +‘no-tcl-format’ + Likewise for Tcl, see *note tcl-format::. + +‘perl-format’ +‘no-perl-format’ + Likewise for Perl, see *note perl-format::. + +‘perl-brace-format’ +‘no-perl-brace-format’ + Likewise for Perl brace, see *note perl-format::. + +‘php-format’ +‘no-php-format’ + Likewise for PHP, see *note php-format::. + +‘gcc-internal-format’ +‘no-gcc-internal-format’ + Likewise for the GCC sources, see *note gcc-internal-format::. + +‘gfc-internal-format’ +‘no-gfc-internal-format’ + Likewise for the GNU Fortran Compiler sources, see *note + gfc-internal-format::. + +‘ycp-format’ +‘no-ycp-format’ + Likewise for YCP, see *note ycp-format::. + + It is also possible to have entries with a context specifier. They +look like this: + + WHITE-SPACE + # TRANSLATOR-COMMENTS + #. EXTRACTED-COMMENTS + #: REFERENCE... + #, FLAG... + #| msgctxt PREVIOUS-CONTEXT + #| msgid PREVIOUS-UNTRANSLATED-STRING + msgctxt CONTEXT + msgid UNTRANSLATED-STRING + msgstr TRANSLATED-STRING + + The context serves to disambiguate messages with the same +UNTRANSLATED-STRING. It is possible to have several entries with the +same UNTRANSLATED-STRING in a PO file, provided that they each have a +different CONTEXT. Note that an empty CONTEXT string and an absent +‘msgctxt’ line do not mean the same thing. + + A different kind of entries is used for translations which involve +plural forms. + + WHITE-SPACE + # TRANSLATOR-COMMENTS + #. EXTRACTED-COMMENTS + #: REFERENCE... + #, FLAG... + #| msgid PREVIOUS-UNTRANSLATED-STRING-SINGULAR + #| msgid_plural PREVIOUS-UNTRANSLATED-STRING-PLURAL + msgid UNTRANSLATED-STRING-SINGULAR + msgid_plural UNTRANSLATED-STRING-PLURAL + msgstr[0] TRANSLATED-STRING-CASE-0 + ... + msgstr[N] TRANSLATED-STRING-CASE-N + + Such an entry can look like this: + + #: src/msgcmp.c:338 src/po-lex.c:699 + #, c-format + msgid "found %d fatal error" + msgid_plural "found %d fatal errors" + msgstr[0] "s'ha trobat %d error fatal" + msgstr[1] "s'han trobat %d errors fatals" + + Here also, a ‘msgctxt’ context can be specified before ‘msgid’, like +above. + + Here, additional kinds of flags can be used: + +‘range:’ + This flag is followed by a range of non-negative numbers, using the + syntax ‘range: MINIMUM-VALUE..MAXIMUM-VALUE’. It designates the + possible values that the numeric parameter of the message can take. + In some languages, translators may produce slightly better + translations if they know that the value can only take on values + between 0 and 10, for example. + + The PREVIOUS-UNTRANSLATED-STRING is optionally inserted by the +‘msgmerge’ program, at the same time when it marks a message fuzzy. It +helps the translator to see which changes were done by the developers on +the UNTRANSLATED-STRING. + + It happens that some lines, usually whitespace or comments, follow +the very last entry of a PO file. Such lines are not part of any entry, +and will be dropped when the PO file is processed by the tools, or may +disturb some PO file editors. + + The remainder of this section may be safely skipped by those using a +PO file editor, yet it may be interesting for everybody to have a better +idea of the precise format of a PO file. On the other hand, those +wishing to modify PO files by hand should carefully continue reading on. + + An empty UNTRANSLATED-STRING is reserved to contain the header entry +with the meta information (*note Header Entry::). This header entry +should be the first entry of the file. The empty UNTRANSLATED-STRING is +reserved for this purpose and must not be used anywhere else. + + Each of UNTRANSLATED-STRING and TRANSLATED-STRING respects the C +syntax for a character string, including the surrounding quotes and +embedded backslashed escape sequences, except that universal character +escape sequences (‘\u’ and ‘\U’) are not allowed. When the time comes +to write multi-line strings, one should not use escaped newlines. +Instead, a closing quote should follow the last character on the line to +be continued, and an opening quote should resume the string at the +beginning of the following PO file line. For example: + + msgid "" + "Here is an example of how one might continue a very long string\n" + "for the common case the string represents multi-line output.\n" + +In this example, the empty string is used on the first line, to allow +better alignment of the ‘H’ from the word ‘Here’ over the ‘f’ from the +word ‘for’. In this example, the ‘msgid’ keyword is followed by three +strings, which are meant to be concatenated. Concatenating the empty +string does not change the resulting overall string, but it is a way for +us to comply with the necessity of ‘msgid’ to be followed by a string on +the same line, while keeping the multi-line presentation left-justified, +as we find this to be a cleaner disposition. The empty string could +have been omitted, but only if the string starting with ‘Here’ was +promoted on the first line, right after ‘msgid’.(1) It was not really +necessary either to switch between the two last quoted strings +immediately after the newline ‘\n’, the switch could have occurred after +_any_ other character, we just did it this way because it is neater. + + One should carefully distinguish between end of lines marked as ‘\n’ +_inside_ quotes, which are part of the represented string, and end of +lines in the PO file itself, outside string quotes, which have no +incidence on the represented string. + + Outside strings, white lines and comments may be used freely. +Comments start at the beginning of a line with ‘#’ and extend until the +end of the PO file line. Comments written by translators should have +the initial ‘#’ immediately followed by some white space. If the ‘#’ is +not immediately followed by white space, this comment is most likely +generated and managed by specialized GNU tools, and might disappear or +be replaced unexpectedly when the PO file is given to ‘msgmerge’. + + For a PO file to be valid, no two entries without ‘msgctxt’ may have +the same UNTRANSLATED-STRING or UNTRANSLATED-STRING-SINGULAR. +Similarly, no two entries may have the same ‘msgctxt’ and the same +UNTRANSLATED-STRING or UNTRANSLATED-STRING-SINGULAR. + + ---------- Footnotes ---------- + + (1) This limitation is not imposed by GNU ‘gettext’, but is for +compatibility with the ‘msgfmt’ implementation on Solaris. + + +File: gettext.info, Node: Sources, Next: Template, Prev: PO Files, Up: Top + +4 Preparing Program Sources +*************************** + + For the programmer, changes to the C source code fall into three +categories. First, you have to make the localization functions known to +all modules needing message translation. Second, you should properly +trigger the operation of GNU ‘gettext’ when the program initializes, +usually from the ‘main’ function. Last, you should identify, adjust and +mark all constant strings in your program needing translation. + +* Menu: + +* Importing:: Importing the ‘gettext’ declaration +* Triggering:: Triggering ‘gettext’ Operations +* Preparing Strings:: Preparing Translatable Strings +* Mark Keywords:: How Marks Appear in Sources +* Marking:: Marking Translatable Strings +* Translator advice:: Adding advice for translators +* c-format Flag:: Telling something about the following string +* Special cases:: Special Cases of Translatable Strings +* Bug Report Address:: Letting Users Report Translation Bugs +* Names:: Marking Proper Names for Translation +* Libraries:: Preparing Library Sources + + +File: gettext.info, Node: Importing, Next: Triggering, Up: Sources + +4.1 Importing the ‘gettext’ declaration +======================================= + + Presuming that your set of programs, or package, has been adjusted so +all needed GNU ‘gettext’ files are available, and your ‘Makefile’ files +are adjusted (*note Maintainers::), each C module having translated C +strings should contain the line: + + #include + + Similarly, each C module containing ‘printf()’/‘fprintf()’/... calls +with a format string that could be a translated C string (even if the C +string comes from a different C module) should contain the line: + + #include + + +File: gettext.info, Node: Triggering, Next: Preparing Strings, Prev: Importing, Up: Sources + +4.2 Triggering ‘gettext’ Operations +=================================== + + The initialization of locale data should be done with more or less +the same code in every program, as demonstrated below: + + int + main (int argc, char *argv[]) + { + ... + setlocale (LC_ALL, ""); + bindtextdomain (PACKAGE, LOCALEDIR); + textdomain (PACKAGE); + ... + } + + PACKAGE and LOCALEDIR should be provided either by ‘config.h’ or by +the Makefile. For now consult the ‘gettext’ or ‘hello’ sources for more +information. + + The use of ‘LC_ALL’ might not be appropriate for you. ‘LC_ALL’ +includes all locale categories and especially ‘LC_CTYPE’. This latter +category is responsible for determining character classes with the +‘isalnum’ etc. functions from ‘ctype.h’ which could especially for +programs, which process some kind of input language, be wrong. For +example this would mean that a source code using the ç (c-cedilla +character) is runnable in France but not in the U.S. + + Some systems also have problems with parsing numbers using the +‘scanf’ functions if an other but the ‘LC_ALL’ locale category is used. +The standards say that additional formats but the one known in the ‘"C"’ +locale might be recognized. But some systems seem to reject numbers in +the ‘"C"’ locale format. In some situation, it might also be a problem +with the notation itself which makes it impossible to recognize whether +the number is in the ‘"C"’ locale or the local format. This can happen +if thousands separator characters are used. Some locales define this +character according to the national conventions to ‘'.'’ which is the +same character used in the ‘"C"’ locale to denote the decimal point. + + So it is sometimes necessary to replace the ‘LC_ALL’ line in the code +above by a sequence of ‘setlocale’ lines + + { + ... + setlocale (LC_CTYPE, ""); + setlocale (LC_MESSAGES, ""); + ... + } + +On all POSIX conformant systems the locale categories ‘LC_CTYPE’, +‘LC_MESSAGES’, ‘LC_COLLATE’, ‘LC_MONETARY’, ‘LC_NUMERIC’, and ‘LC_TIME’ +are available. On some systems which are only ISO C compliant, +‘LC_MESSAGES’ is missing, but a substitute for it is defined in GNU +gettext's ‘’ and in GNU gnulib's ‘’. + + Note that changing the ‘LC_CTYPE’ also affects the functions declared +in the ‘’ standard header and some functions declared in the +‘’ and ‘’ standard headers. If this is not +desirable in your application (for example in a compiler's parser), you +can use a set of substitute functions which hardwire the C locale, such +as found in the modules ‘c-ctype’, ‘c-strcase’, ‘c-strcasestr’, +‘c-snprintf’, ‘c-strtod’, ‘c-strtold’, ‘c-dtoastr’, ‘c-ldtoastr’ in the +GNU gnulib source distribution. + + It is also possible to switch the locale forth and back between the +environment dependent locale and the C locale, but this approach is +normally avoided because a ‘setlocale’ call is expensive, because it is +tedious to determine the places where a locale switch is needed in a +large program's source, and because switching a locale is not +multithread-safe. + + +File: gettext.info, Node: Preparing Strings, Next: Mark Keywords, Prev: Triggering, Up: Sources + +4.3 Preparing Translatable Strings +================================== + + Before strings can be marked for translations, they sometimes need to +be adjusted. Usually preparing a string for translation is done right +before marking it, during the marking phase which is described in the +next sections. What you have to keep in mind while doing that is the +following. + + • Decent English style. + + • Entire sentences. + + • Split at paragraphs. + + • Use format strings instead of string concatenation. + + • Use placeholders in format strings instead of embedded URLs. + + • Use placeholders in format strings instead of programmer-defined + format string directives. + + • Avoid unusual markup and unusual control characters. + +Let's look at some examples of these guidelines. + +* Menu: + +* Decent English style:: +* Entire sentences:: +* Split at paragraphs:: +* No string concatenation:: +* No embedded URLs:: +* No custom format directives:: +* No unusual markup:: + + +File: gettext.info, Node: Decent English style, Next: Entire sentences, Up: Preparing Strings + +4.3.1 Decent English style +-------------------------- + + Translatable strings should be in good English style. If slang +language with abbreviations and shortcuts is used, often translators +will not understand the message and will produce very inappropriate +translations. + + "%s: is parameter\n" + +This is nearly untranslatable: Is the displayed item _a_ parameter or +_the_ parameter? + + "No match" + +The ambiguity in this message makes it unintelligible: Is the program +attempting to set something on fire? Does it mean "The given object +does not match the template"? Does it mean "The template does not fit +for any of the objects"? + + In both cases, adding more words to the message will help both the +translator and the English speaking user. + + +File: gettext.info, Node: Entire sentences, Next: Split at paragraphs, Prev: Decent English style, Up: Preparing Strings + +4.3.2 Entire sentences +---------------------- + + Translatable strings should be entire sentences. It is often not +possible to translate single verbs or adjectives in a substitutable way. + + printf ("File %s is %s protected", filename, rw ? "write" : "read"); + +Most translators will not look at the source and will thus only see the +string ‘"File %s is %s protected"’, which is unintelligible. Change +this to + + printf (rw ? "File %s is write protected" : "File %s is read protected", + filename); + +This way the translator will not only understand the message, she will +also be able to find the appropriate grammatical construction. A French +translator for example translates "write protected" like "protected +against writing". + + Entire sentences are also important because in many languages, the +declination of some word in a sentence depends on the gender or the +number (singular/plural) of another part of the sentence. There are +usually more interdependencies between words than in English. The +consequence is that asking a translator to translate two half-sentences +and then combining these two half-sentences through dumb string +concatenation will not work, for many languages, even though it would +work for English. That's why translators need to handle entire +sentences. + + Often sentences don't fit into a single line. If a sentence is +output using two subsequent ‘printf’ statements, like this + + printf ("Locale charset \"%s\" is different from\n", lcharset); + printf ("input file charset \"%s\".\n", fcharset); + +the translator would have to translate two half sentences, but nothing +in the POT file would tell her that the two half sentences belong +together. It is necessary to merge the two ‘printf’ statements so that +the translator can handle the entire sentence at once and decide at +which place to insert a line break in the translation (if at all): + + printf ("Locale charset \"%s\" is different from\n\ + input file charset \"%s\".\n", lcharset, fcharset); + + You may now ask: how about two or more adjacent sentences? Like in +this case: + + puts ("Apollo 13 scenario: Stack overflow handling failed."); + puts ("On the next stack overflow we will crash!!!"); + +Should these two statements merged into a single one? I would recommend +to merge them if the two sentences are related to each other, because +then it makes it easier for the translator to understand and translate +both. On the other hand, if one of the two messages is a stereotypic +one, occurring in other places as well, you will do a favour to the +translator by not merging the two. (Identical messages occurring in +several places are combined by ‘xgettext’, so the translator has to +handle them once only.) + + +File: gettext.info, Node: Split at paragraphs, Next: No string concatenation, Prev: Entire sentences, Up: Preparing Strings + +4.3.3 Split at paragraphs +------------------------- + + Translatable strings should be limited to one paragraph; don't let a +single message be longer than ten lines. The reason is that when the +translatable string changes, the translator is faced with the task of +updating the entire translated string. Maybe only a single word will +have changed in the English string, but the translator doesn't see that +(with the current translation tools), therefore she has to proofread the +entire message. + + Many GNU programs have a ‘--help’ output that extends over several +screen pages. It is a courtesy towards the translators to split such a +message into several ones of five to ten lines each. While doing that, +you can also attempt to split the documented options into groups, such +as the input options, the output options, and the informative output +options. This will help every user to find the option he is looking +for. + + +File: gettext.info, Node: No string concatenation, Next: No embedded URLs, Prev: Split at paragraphs, Up: Preparing Strings + +4.3.4 No string concatenation +----------------------------- + + Hardcoded string concatenation is sometimes used to construct English +strings: + + strcpy (s, "Replace "); + strcat (s, object1); + strcat (s, " with "); + strcat (s, object2); + strcat (s, "?"); + +In order to present to the translator only entire sentences, and also +because in some languages the translator might want to swap the order of +‘object1’ and ‘object2’, it is necessary to change this to use a format +string: + + sprintf (s, "Replace %s with %s?", object1, object2); + +String concatenation operator +----------------------------- + + In many programming languages, a particular operator denotes string +concatenation at runtime (or possibly at compile time, if the compiler +supports that). + + • In C++, string concatenation of ‘std::string’ objects is denoted by + the ‘+’ operator. + • In Python, string concatenation is denoted by the ‘+’ operator. + • In Java, string concatenation is denoted by the ‘+’ operator. + • In C#, string concatenation is denoted by the ‘+’ operator. + • In JavaScript and TypeScript, string concatenation is denoted by + the ‘+’ operator. + • In Go, string concatenation is denoted by the ‘+’ operator. + • In Ruby, string concatenation is denoted by the ‘+’ operator. + • In Shell, string concatenation is denoted by mere juxtaposition of + strings. + • In awk, string concatenation is denoted by mere juxtaposition of + strings. + • In Lua, string concatenation is denoted by the ‘..’ operator. + • In Modula-2, string concatenation is denoted by the ‘+’ operator. + • In D, string concatenation is denoted by the ‘~’ operator. + • In Smalltalk, string concatenation is denoted by the ‘,’ operator. + • In Vala, string concatenation is denoted by the ‘+’ operator. + • In Perl, string concatenation is denoted by the ‘.’ operator. + • In PHP, string concatenation is denoted by the ‘.’ operator. + + So, for example, in Java, you would change + + System.out.println("Replace "+object1+" with "+object2+"?"); + +into a statement involving a format string: + + System.out.println( + MessageFormat.format("Replace {0} with {1}?", + new Object[] { object1, object2 })); + +Similarly, in C#, you would change + + Console.WriteLine("Replace "+object1+" with "+object2+"?"); + +into a statement involving a format string: + + Console.WriteLine( + String.Format("Replace {0} with {1}?", object1, object2)); + +Strings with embedded expressions +--------------------------------- + + In some programming languages, it is possible to have strings with +embedded expressions. The expressions can refer to variables of the +program. The value of such an expression is converted to a string and +inserted in place of the expression; but no formatting function is +called. + + • In Python, _f-strings_ can contain expressions. Such as ‘f"Hello, + {name}!"’. + • In C#, since C# 6.0, _interpolated strings_ can contain + expressions. Such as ‘$"Hello, {name}!"’. + • In JavaScript, since ES6, and in TypeScript, _template literals_ + can contain expressions. Such as ‘`Hello, ${name}!`’. + • In Ruby, _interpolated strings_ can contain expressions. Such as + ‘"Hello, #{name}!"’. + • In Shell language, double-quoted strings can contain references to + variables, along with default values and string operations. Such + as ‘"Hello, $name!"’ or ‘"Hello, ${name}!"’. + • In D, _interpolation expression sequences_ can contain expressions. + Such as ‘i"Hello, $(name)!"’. + • In Tcl, strings are subject to _variable substitution_. Such as + ‘"Hello, $name!"’. + • In Perl, _interpolated strings_ can contain expressions. Such as + ‘"Hello, $name!"’. + • In PHP, string literals are subject to _variable parsing_. Such as + ‘"Hello, $name!"’. + + These cases are effectively string concatenation as well, just with a +different syntax. + + So, for example, in Python, you would change + + print (f'Replace {object1.name} with {object2.name}?') + +into a statement involving a format string: + + print ('Replace %(name1)s with %(name2)s?' + % { 'name1': object1.name, 'name2': object2.name }) + +or equivalently + print ('Replace {name1} with {name2}?' + .format(name1 = object1.name, name2 = object2.name)) + + And in JavaScript, you would change + + print (`Replace ${object1.name} with ${object2.name}?`) + +into a statement involving a format string: + + print ('Replace %s with %s?'.format(object1.name, object2.name)) + +Specifically in JavaScript, an alternative is to use a _tagged_ template +literal: + + print (TAG`Replace ${object1.name} with ${object2.name}?`) + +and pass an option ‘--tag=TAG:FORMAT’ to ‘xgettext’. + +Format strings with embedded named references +--------------------------------------------- + + Format strings with embedded named references are different: They are +suitable for internationalization, because it is possible to insert a +call to the ‘gettext’ function (that will return a translated format +string) _before_ the argument values are inserted in place of the +placeholders. + + The format string types that allow embedded named references are: + + • *note Shell format strings: sh-format. + • In Python, those *note Python format strings: python-format. that + take a dictionary as argument, and the *note Python brace format + strings: python-format. + • In Ruby, those *note Ruby format strings: ruby-format. that take a + hash table as argument. + • In Perl, the *note Perl brace format strings: perl-format. + +The ‘’ macros +------------------------- + + A similar case is compile time concatenation of strings. The ISO C +99 include file ‘’ contains a macro ‘PRId64’ that can be +used as a formatting directive for outputting an ‘int64_t’ integer +through ‘printf’. It expands to a constant string, usually "d" or "ld" +or "lld" or something like this, depending on the platform. Assume you +have code like + + printf ("The amount is %0" PRId64 "\n", number); + +The ‘gettext’ tools and library have special support for these +‘’ macros. You can therefore simply write + + printf (gettext ("The amount is %0" PRId64 "\n"), number); + +The PO file will contain the string "The amount is %0\n". The +translators will provide a translation containing "%0" as well, +and at runtime the ‘gettext’ function's result will contain the +appropriate constant string, "d" or "ld" or "lld". + + This works only for the predefined ‘’ macros. If you +have defined your own similar macros, let's say ‘MYPRId64’, that are not +known to ‘xgettext’, the solution for this problem is to change the code +like this: + + char buf1[100]; + sprintf (buf1, "%0" MYPRId64, number); + printf (gettext ("The amount is %s\n"), buf1); + + This means, you put the platform dependent code in one statement, and +the internationalization code in a different statement. Note that a +buffer length of 100 is safe, because all available hardware integer +types are limited to 128 bits, and to print a 128 bit integer one needs +at most 54 characters, regardless whether in decimal, octal or +hexadecimal. + + +File: gettext.info, Node: No embedded URLs, Next: No custom format directives, Prev: No string concatenation, Up: Preparing Strings + +4.3.5 No embedded URLs +---------------------- + + It is good to not embed URLs in translatable strings, for several +reasons: + • It avoids possible mistakes during copy and paste. + • Translators cannot translate the URLs or, by mistake, use the URLs + from other packages that are present in their compendium. + • When the URLs change, translators don't need to revisit the + translation of the string. + + The same holds for email addresses. + + So, you would change + + fputs (_("GNU GPL version 3 \n"), + stream); + +to + + fprintf (stream, _("GNU GPL version 3 <%s>\n"), + "https://gnu.org/licenses/gpl.html"); + + +File: gettext.info, Node: No custom format directives, Next: No unusual markup, Prev: No embedded URLs, Up: Preparing Strings + +4.3.6 No programmer-defined format string directives +---------------------------------------------------- + + The GNU C Library's ‘’ facility and the C++ standard +library's ‘’ header file make it possible for the programmer to +define their own format string directives. However, such format +directives cannot be used in translatable strings, for two reasons: + • There is no reference documentation for format strings with such + directives, that the translators could consult. They would + therefore have to guess where the directive starts and where it + ends. + • An ‘msgfmt -c’ invocation cannot check whether the translator has + produced a compatible translation of the format string. As a + consequence, when a format string contains a programmer-defined + directive, the program may crash at runtime when it uses the + translated format string. + + To avoid this situation, you need to move the formatting with the +custom directive into a format string that does not get translated. + + For example, assuming code that makes use of a ‘%r’ directive: + + fprintf (stream, _("The contents is: %r"), data); + +you would rewrite it to: + + char *tmp; + if (asprintf (&tmp, "%r", data) < 0) + error (...); + fprintf (stream, _("The contents is: %s"), tmp); + free (tmp); + + Similarly, in C++, assuming you have defined a custom ‘formatter’ for +the type of ‘data’, the code + + cout << format (_("The contents is: {:#$#}"), data); + +should be rewritten to: + + string tmp = format ("{:#$#}", data); + cout << format (_("The contents is: {}"), tmp); + + +File: gettext.info, Node: No unusual markup, Prev: No custom format directives, Up: Preparing Strings + +4.3.7 No unusual markup +----------------------- + + Unusual markup or control characters should not be used in +translatable strings. Translators will likely not understand the +particular meaning of the markup or control characters. + + For example, if you have a convention that ‘|’ delimits the left-hand +and right-hand part of some GUI elements, translators will often not +understand it without specific comments. It might be better to have the +translator translate the left-hand and right-hand part separately. + + Another example is the ‘argp’ convention to use a single ‘\v’ +(vertical tab) control character to delimit two sections inside a +string. This is flawed. Some translators may convert it to a simple +newline, some to blank lines. With some PO file editors it may not be +easy to even enter a vertical tab control character. So, you cannot be +sure that the translation will contain a ‘\v’ character, at the +corresponding position. The solution is, again, to let the translator +translate two separate strings and combine at run-time the two +translated strings with the ‘\v’ required by the convention. + + HTML markup, however, is common enough that it's probably ok to use +in translatable strings. But please bear in mind that the GNU gettext +tools don't verify that the translations are well-formed HTML. + + +File: gettext.info, Node: Mark Keywords, Next: Marking, Prev: Preparing Strings, Up: Sources + +4.4 How Marks Appear in Sources +=============================== + + All strings requiring translation should be marked in the C sources. +Marking is done in such a way that each translatable string appears to +be the sole argument of some function or preprocessor macro. There are +only a few such possible functions or macros meant for translation, and +their names are said to be marking keywords. The marking is attached to +strings themselves, rather than to what we do with them. This approach +has more uses. A blatant example is an error message produced by +formatting. The format string needs translation, as well as some +strings inserted through some ‘%s’ specification in the format, while +the result from ‘sprintf’ may have so many different instances that it +is impractical to list them all in some ‘error_string_out()’ routine, +say. + + This marking operation has two goals. The first goal of marking is +for triggering the retrieval of the translation, at run time. The +keyword is possibly resolved into a routine able to dynamically return +the proper translation, as far as possible or wanted, for the argument +string. Most localizable strings are found in executable positions, +that is, attached to variables or given as parameters to functions. But +this is not universal usage, and some translatable strings appear in +structured initializations. *Note Special cases::. + + The second goal of the marking operation is to help ‘xgettext’ at +properly extracting all translatable strings when it scans a set of +program sources and produces PO file templates. + + The canonical keyword for marking translatable strings is ‘gettext’, +it gave its name to the whole GNU ‘gettext’ package. For packages +making only light use of the ‘gettext’ keyword, macro or function, it is +easily used _as is_. However, for packages using the ‘gettext’ +interface more heavily, it is usually more convenient to give the main +keyword a shorter, less obtrusive name. Indeed, the keyword might +appear on a lot of strings all over the package, and programmers usually +do not want nor need their program sources to remind them forcefully, +all the time, that they are internationalized. Further, a long keyword +has the disadvantage of using more horizontal space, forcing more +indentation work on sources for those trying to keep them within 79 or +80 columns. + + Many packages use ‘_’ (a simple underline) as a keyword, and write +‘_("Translatable string")’ instead of ‘gettext ("Translatable string")’. +Further, the coding rule, from GNU standards, wanting that there is a +space between the keyword and the opening parenthesis is relaxed, in +practice, for this particular usage. So, the textual overhead per +translatable string is reduced to only three characters: the underline +and the two parentheses. However, even if GNU ‘gettext’ uses this +convention internally, it does not offer it officially. The real, +genuine keyword is truly ‘gettext’ indeed. It is fairly easy for those +wanting to use ‘_’ instead of ‘gettext’ to declare: + + #include + #define _(String) gettext (String) + +instead of merely using ‘#include ’. + + The marking keywords ‘gettext’ and ‘_’ take the translatable string +as sole argument. It is also possible to define marking functions that +take it at another argument position. It is even possible to make the +marked argument position depend on the total number of arguments of the +function call; this is useful in C++. All this is achieved using +‘xgettext’'s ‘--keyword’ option. How to pass such an option to +‘xgettext’, assuming that ‘gettextize’ is used, is described in *note +po/Makevars:: and *note AM_XGETTEXT_OPTION::. + + Note also that long strings can be split across lines, into multiple +adjacent string tokens. Automatic string concatenation is performed at +compile time according to ISO C and ISO C++; ‘xgettext’ also supports +this syntax. + + In C++, marking a C++ format string requires a small code change, +because the first argument to ‘std::format’ must be a constant +expression. For example, + std::format ("{} {}!", "Hello", "world") +needs to be changed to + std::vformat (gettext ("{} {}!"), std::make_format_args("Hello", "world")) + + Later on, the maintenance is relatively easy. If, as a programmer, +you add or modify a string, you will have to ask yourself if the new or +altered string requires translation, and include it within ‘_()’ if you +think it should be translated. For example, ‘"%s"’ is an example of +string _not_ requiring translation. But ‘"%s: %d"’ _does_ require +translation, because in French, unlike in English, it's customary to put +a space before a colon. + + +File: gettext.info, Node: Marking, Next: Translator advice, Prev: Mark Keywords, Up: Sources + +4.5 Marking Translatable Strings +================================ + + In PO mode, one set of features is meant more for the programmer than +for the translator, and allows him to interactively mark which strings, +in a set of program sources, are translatable, and which are not. Even +if it is a fairly easy job for a programmer to find and mark such +strings by other means, using any editor of his choice, PO mode makes +this work more comfortable. Further, this gives translators who feel a +little like programmers, or programmers who feel a little like +translators, a tool letting them work at marking translatable strings in +the program sources, while simultaneously producing a set of translation +in some language, for the package being internationalized. + + The set of program sources, targeted by the PO mode commands describe +here, should have an Emacs tags table constructed for your project, +prior to using these PO file commands. This is easy to do. In any +shell window, change the directory to the root of your project, then +execute a command resembling: + + etags src/*.[hc] lib/*.[hc] + +presuming here you want to process all ‘.h’ and ‘.c’ files from the +‘src/’ and ‘lib/’ directories. This command will explore all said files +and create a ‘TAGS’ file in your root directory, somewhat summarizing +the contents using a special file format Emacs can understand. + + For packages following the GNU coding standards, there is a make goal +‘tags’ or ‘TAGS’ which constructs the tag files in all directories and +for all files containing source code. + + Once your ‘TAGS’ file is ready, the following commands assist the +programmer at marking translatable strings in his set of sources. But +these commands are necessarily driven from within a PO file window, and +it is likely that you do not even have such a PO file yet. This is not +a problem at all, as you may safely open a new, empty PO file, mainly +for using these commands. This empty PO file will slowly fill in while +you mark strings as translatable in your program sources. + +‘,’ + Search through program sources for a string which looks like a + candidate for translation (‘po-tags-search’). + +‘M-,’ + Mark the last string found with ‘_()’ (‘po-mark-translatable’). + +‘M-.’ + Mark the last string found with a keyword taken from a set of + possible keywords. This command with a prefix allows some + management of these keywords (‘po-select-mark-and-mark’). + + The ‘,’ (‘po-tags-search’) command searches for the next occurrence +of a string which looks like a possible candidate for translation, and +displays the program source in another Emacs window, positioned in such +a way that the string is near the top of this other window. If the +string is too big to fit whole in this window, it is positioned so only +its end is shown. In any case, the cursor is left in the PO file +window. If the shown string would be better presented differently in +different native languages, you may mark it using ‘M-,’ or ‘M-.’. +Otherwise, you might rather ignore it and skip to the next string by +merely repeating the ‘,’ command. + + A string is a good candidate for translation if it contains a +sequence of three or more letters. A string containing at most two +letters in a row will be considered as a candidate if it has more +letters than non-letters. The command disregards strings containing no +letters, or isolated letters only. It also disregards strings within +comments, or strings already marked with some keyword PO mode knows (see +below). + + If you have never told Emacs about some ‘TAGS’ file to use, the +command will request that you specify one from the minibuffer, the first +time you use the command. You may later change your ‘TAGS’ file by +using the regular Emacs command ‘M-x visit-tags-table’, which will ask +you to name the precise ‘TAGS’ file you want to use. *Note Tag Tables: +(emacs)Tags. + + Each time you use the ‘,’ command, the search resumes from where it +was left by the previous search, and goes through all program sources, +obeying the ‘TAGS’ file, until all sources have been processed. +However, by giving a prefix argument to the command (‘C-u ,’), you may +request that the search be restarted all over again from the first +program source; but in this case, strings that you recently marked as +translatable will be automatically skipped. + + Using this ‘,’ command does not prevent using of other regular Emacs +tags commands. For example, regular ‘tags-search’ or +‘tags-query-replace’ commands may be used without disrupting the +independent ‘,’ search sequence. However, as implemented, the _initial_ +‘,’ command (or the ‘,’ command is used with a prefix) might also +reinitialize the regular Emacs tags searching to the first tags file, +this reinitialization might be considered spurious. + + The ‘M-,’ (‘po-mark-translatable’) command will mark the recently +found string with the ‘_’ keyword. The ‘M-.’ +(‘po-select-mark-and-mark’) command will request that you type one +keyword from the minibuffer and use that keyword for marking the string. +Both commands will automatically create a new PO file untranslated entry +for the string being marked, and make it the current entry (making it +easy for you to immediately proceed to its translation, if you feel like +doing it right away). It is possible that the modifications made to the +program source by ‘M-,’ or ‘M-.’ render some source line longer than 80 +columns, forcing you to break and re-indent this line differently. You +may use the ‘O’ command from PO mode, or any other window changing +command from Emacs, to break out into the program source window, and do +any needed adjustments. You will have to use some regular Emacs command +to return the cursor to the PO file window, if you want command ‘,’ for +the next string, say. + + The ‘M-.’ command has a few built-in speedups, so you do not have to +explicitly type all keywords all the time. The first such speedup is +that you are presented with a _preferred_ keyword, which you may accept +by merely typing ‘’ at the prompt. The second speedup is that you +may type any non-ambiguous prefix of the keyword you really mean, and +the command will complete it automatically for you. This also means +that PO mode has to _know_ all your possible keywords, and that it will +not accept mistyped keywords. + + If you reply ‘?’ to the keyword request, the command gives a list of +all known keywords, from which you may choose. When the command is +prefixed by an argument (‘C-u M-.’), it inhibits updating any program +source or PO file buffer, and does some simple keyword management +instead. In this case, the command asks for a keyword, written in full, +which becomes a new allowed keyword for later ‘M-.’ commands. Moreover, +this new keyword automatically becomes the _preferred_ keyword for later +commands. By typing an already known keyword in response to ‘C-u M-.’, +one merely changes the _preferred_ keyword and does nothing more. + + All keywords known for ‘M-.’ are recognized by the ‘,’ command when +scanning for strings, and strings already marked by any of those known +keywords are automatically skipped. If many PO files are opened +simultaneously, each one has its own independent set of known keywords. +There is no provision in PO mode, currently, for deleting a known +keyword, you have to quit the file (maybe using ‘q’) and reopen it +afresh. When a PO file is newly brought up in an Emacs window, only +‘gettext’ and ‘_’ are known as keywords, and ‘gettext’ is preferred for +the ‘M-.’ command. In fact, this is not useful to prefer ‘_’, as this +one is already built in the ‘M-,’ command. + + +File: gettext.info, Node: Translator advice, Next: c-format Flag, Prev: Marking, Up: Sources + +4.6 Adding advice for translators +================================= + + Sometimes you might want to add advice for the translators to a +particular message. For example: + • The translatable string might be decent English but nevertheless + ambiguous. + • The translatable string refers to something in English culture + (such as a film's name) that is different in other cultures. + • The translator should make an adjustment that is specific to her + locale. + + The way to do this is to add comments, before the ‘gettext’ +invocation or inside the ‘gettext’ invocation but before the string, +that start with the substring ‘TRANSLATORS:’. These comments will be +extracted into the POT file, so that translators can see them. For +example, when you write + + /* TRANSLATORS: This is an English idiom, + meaning not to reveal a secret. */ + puts (gettext ("Don't spill the beans!")); + +the POT file will contain: + + #. TRANSLATORS: This is an English idiom, + #. meaning not to reveal a secret. + #: source.c:213 + msgid "Don't spill the beans!" + msgstr "" + +and the translators will be shown the advice in a particular place in +their translation tool. + + Only comments that immediately precede the ‘gettext’ invocation or +the translatable string are considered. Intervening blank lines are OK, +but if there is other code between the comment and the translatable +string, the comment no longer applies. + + Note: The string ‘TRANSLATORS:’ is a convention, enabled by the +‘Makefile.in.in’ file that is part of a package's build system. It is +not enabled by default in ‘xgettext’. If you are using ‘xgettext’ +without the ‘Makefile.in.in’ infrastructure, you will need to pass the +option ‘--add-comments=TRANSLATORS:’ yourself. + + +File: gettext.info, Node: c-format Flag, Next: Special cases, Prev: Translator advice, Up: Sources + +4.7 Special Comments preceding Keywords +======================================= + + In C programs strings are often used within calls of functions from +the ‘printf’ family. The special thing about these format strings is +that they can contain format specifiers introduced with ‘%’. Assume we +have the code + + printf (gettext ("String `%s' has %d characters\n"), s, strlen (s)); + +A possible German translation for the above string might be: + + "%d Zeichen lang ist die Zeichenkette `%s'" + + A C programmer, even if he cannot speak German, will recognize that +there is something wrong here. The order of the two format specifiers +is changed but of course the arguments in the ‘printf’ don't have. This +will most probably lead to problems because now the length of the string +is regarded as the address. + + To prevent errors at runtime caused by translations, the ‘msgfmt’ +tool can check statically whether the arguments in the original and the +translation string match in type and number. If this is not the case +and the ‘-c’ option has been passed to ‘msgfmt’, ‘msgfmt’ will give an +error and refuse to produce a MO file. Thus consistent use of ‘msgfmt +-c’ will catch the error, so that it cannot cause problems at runtime. + +If the word order in the above German translation would be correct one +would have to write + + "%2$d Zeichen lang ist die Zeichenkette `%1$s'" + +The routines in ‘msgfmt’ know about this special notation. + + Because not all strings in a program will be format strings, it is +not useful for ‘msgfmt’ to test all the strings in the ‘.po’ file. This +might cause problems because the string might contain what looks like a +format specifier, but the string is not used in ‘printf’. + + Therefore ‘xgettext’ adds a special tag to those messages it thinks +might be a format string. There is no absolute rule for this, only a +heuristic. In the ‘.po’ file the entry is marked using the ‘c-format’ +flag in the ‘#,’ comment line (*note PO Files::). + + The careful reader now might say that this again can cause problems. +The heuristic might guess it wrong. This is true and therefore +‘xgettext’ knows about a special kind of comment which lets the +programmer take over the decision. If in the same line as or the +immediately preceding line to the ‘gettext’ keyword the ‘xgettext’ +program finds a comment containing the words ‘xgettext:c-format’, it +will mark the string in any case with the ‘c-format’ flag. This kind of +comment should be used when ‘xgettext’ does not recognize the string as +a format string but it really is one and it should be tested. Please +note that when the comment is in the same line as the ‘gettext’ keyword, +it must be before the string to be translated. Also note that a comment +such as ‘xgettext:c-format’ applies only to the first string in the same +or the next line, not to multiple strings. + + This situation happens quite often. The ‘printf’ function is often +called with strings which do not contain a format specifier. Of course +one would normally use ‘fputs’ but it does happen. In this case +‘xgettext’ does not recognize this as a format string but what happens +if the translation introduces a valid format specifier? The ‘printf’ +function will try to access one of the parameters but none exists +because the original code does not pass any parameters. + + ‘xgettext’ of course could make a wrong decision the other way round, +i.e. a string marked as a format string actually is not a format string. +In this case the ‘msgfmt’ might give too many warnings and would prevent +translating the ‘.po’ file. The method to prevent this wrong decision +is similar to the one used above, only the comment to use must contain +the string ‘xgettext:no-c-format’. + + If a string is marked with ‘c-format’ and this is not correct the +user can find out who is responsible for the decision. See *note +xgettext Invocation:: to see how the ‘--debug’ option can be used for +solving this problem. + + +File: gettext.info, Node: Special cases, Next: Bug Report Address, Prev: c-format Flag, Up: Sources + +4.8 Special Cases of Translatable Strings +========================================= + + The attentive reader might now point out that it is not always +possible to mark translatable string with ‘gettext’ or something like +this. Consider the following case: + + { + static const char *messages[] = { + "some very meaningful message", + "and another one" + }; + const char *string; + ... + string + = index > 1 ? "a default message" : messages[index]; + + fputs (string); + ... + } + + While it is no problem to mark the string ‘"a default message"’ it is +not possible to mark the string initializers for ‘messages’. What is to +be done? We have to fulfill two tasks. First we have to mark the +strings so that the ‘xgettext’ program (*note xgettext Invocation::) can +find them, and second we have to translate the string at runtime before +printing them. + + The first task can be fulfilled by creating a new keyword, which +names a no-op. For the second we have to mark all access points to a +string from the array. So one solution can look like this: + + #define gettext_noop(String) String + + { + static const char *messages[] = { + gettext_noop ("some very meaningful message"), + gettext_noop ("and another one") + }; + const char *string; + ... + string + = index > 1 ? gettext ("a default message") : gettext (messages[index]); + + fputs (string); + ... + } + + Please convince yourself that the string which is written by ‘fputs’ +is translated in any case. How to get ‘xgettext’ know the additional +keyword ‘gettext_noop’ is explained in *note xgettext Invocation::. + + The above is of course not the only solution. You could also come +along with the following one: + + #define gettext_noop(String) String + + { + static const char *messages[] = { + gettext_noop ("some very meaningful message"), + gettext_noop ("and another one") + }; + const char *string; + ... + string + = index > 1 ? gettext_noop ("a default message") : messages[index]; + + fputs (gettext (string)); + ... + } + + But this has a drawback. The programmer has to take care that he +uses ‘gettext_noop’ for the string ‘"a default message"’. A use of +‘gettext’ could have in rare cases unpredictable results. + + One advantage is that you need not make control flow analysis to make +sure the output is really translated in any case. But this analysis is +generally not very difficult. If it should be in any situation you can +use this second method in this situation. + + +File: gettext.info, Node: Bug Report Address, Next: Names, Prev: Special cases, Up: Sources + +4.9 Letting Users Report Translation Bugs +========================================= + + Code sometimes has bugs, but translations sometimes have bugs too. +The users need to be able to report them. Reporting translation bugs to +the programmer or maintainer of a package is not very useful, since the +maintainer must never change a translation, except on behalf of the +translator. Hence the translation bugs must be reported to the +translators. + + Here is a way to organize this so that the maintainer does not need +to forward translation bug reports, nor even keep a list of the +addresses of the translators or their translation teams. + + Every program has a place where is shows the bug report address. For +GNU programs, it is the code which handles the "-help" option, typically +in a function called "usage". In this place, instruct the translator to +add her own bug reporting address. For example, if that code has a +statement + + printf (_("Report bugs to <%s>.\n"), PACKAGE_BUGREPORT); + + you can add some translator instructions like this: + + /* TRANSLATORS: The placeholder indicates the bug-reporting address + for this package. Please add _another line_ saying + "Report translation bugs to <...>\n" with the address for translation + bugs (typically your translation team's web or email address). */ + printf (_("Report bugs to <%s>.\n"), PACKAGE_BUGREPORT); + + These will be extracted by ‘xgettext’, leading to a .pot file that +contains this: + + #. TRANSLATORS: The placeholder indicates the bug-reporting address + #. for this package. Please add _another line_ saying + #. "Report translation bugs to <...>\n" with the address for translation + #. bugs (typically your translation team's web or email address). + #: src/hello.c:178 + #, c-format + msgid "Report bugs to <%s>.\n" + msgstr "" + + +File: gettext.info, Node: Names, Next: Libraries, Prev: Bug Report Address, Up: Sources + +4.10 Marking Proper Names for Translation +========================================= + + Should names of persons, cities, locations etc. be marked for +translation or not? People who only know languages that can be written +with Latin letters (English, Spanish, French, German, etc.) are tempted +to say "no", because names usually do not change when transported +between these languages. However, in general when translating from one +script to another, names are translated too, usually phonetically or by +transliteration. For example, Russian or Greek names are converted to +the Latin alphabet when being translated to English, and English or +French names are converted to the Katakana script when being translated +to Japanese. This is necessary because the speakers of the target +language in general cannot read the script the name is originally +written in. + + As a programmer, you should therefore make sure that names are marked +for translation, with a special comment telling the translators that it +is a proper name and how to pronounce it. In its simple form, it looks +like this: + + printf (_("Written by %s.\n"), + /* TRANSLATORS: This is a proper name. See the gettext + manual, section Names. Note this is actually a non-ASCII + name: The first name is (with Unicode escapes) + "Fran\u00e7ois" or (with HTML entities) "François". + Pronunciation is like "fraa-swa pee-nar". */ + _("Francois Pinard")); + +The GNU gnulib library offers a module ‘propername’ +() +which takes care to automatically append the original name, in +parentheses, to the translated name. For names that cannot be written +in ASCII, it also frees the translator from the task of entering the +appropriate non-ASCII characters if no script change is needed. In this +more comfortable form, it looks like this: + + printf (_("Written by %s and %s.\n"), + proper_name ("Ulrich Drepper"), + /* TRANSLATORS: This is a proper name. See the gettext + manual, section Names. Note this is actually a non-ASCII + name: The first name is (with Unicode escapes) + "Fran\u00e7ois" or (with HTML entities) "François". + Pronunciation is like "fraa-swa pee-nar". */ + proper_name_utf8 ("Francois Pinard", "Fran\303\247ois Pinard")); + +You can also write the original name directly in Unicode (rather than +with Unicode escapes or HTML entities) and denote the pronunciation +using the International Phonetic Alphabet (see +). + + As a translator, you should use some care when translating names, +because it is frustrating if people see their names mutilated or +distorted. + + If your language uses the Latin script, all you need to do is to +reproduce the name as perfectly as you can within the usual character +set of your language. In this particular case, this means to provide a +translation containing the c-cedilla character. If your language uses a +different script and the people speaking it don't usually read Latin +words, it means transliteration. If the programmer used the simple +case, you should still give, in parentheses, the original writing of the +name - for the sake of the people that do read the Latin script. If the +programmer used the ‘propername’ module mentioned above, you don't need +to give the original writing of the name in parentheses, because the +program will already do so. Here is an example, using Greek as the +target script: + + #. This is a proper name. See the gettext + #. manual, section Names. Note this is actually a non-ASCII + #. name: The first name is (with Unicode escapes) + #. "Fran\u00e7ois" or (with HTML entities) "François". + #. Pronunciation is like "fraa-swa pee-nar". + msgid "Francois Pinard" + msgstr "\phi\rho\alpha\sigma\omicron\alpha \pi\iota\nu\alpha\rho" + " (Francois Pinard)" + + Because translation of names is such a sensitive domain, it is a good +idea to test your translation before submitting it. + + +File: gettext.info, Node: Libraries, Prev: Names, Up: Sources + +4.11 Preparing Library Sources +============================== + + When you are preparing a library, not a program, for the use of +‘gettext’, only a few details are different. Here we assume that the +library has a translation domain and a POT file of its own. (If it uses +the translation domain and POT file of the main program, then the +previous sections apply without changes.) + + 1. The library code doesn't call ‘setlocale (LC_ALL, "")’. It's the + responsibility of the main program to set the locale. The + library's documentation should mention this fact, so that + developers of programs using the library are aware of it. + + 2. The library code doesn't call ‘textdomain (PACKAGE)’, because it + would interfere with the text domain set by the main program. + + 3. The initialization code for a program was + + setlocale (LC_ALL, ""); + bindtextdomain (PACKAGE, LOCALEDIR); + textdomain (PACKAGE); + + For a library it is reduced to + + bindtextdomain (PACKAGE, LOCALEDIR); + + If your library's API doesn't already have an initialization + function, you need to create one, containing at least the + ‘bindtextdomain’ invocation. However, you usually don't need to + export and document this initialization function: It is sufficient + that all entry points of the library call the initialization + function if it hasn't been called before. The typical idiom used + to achieve this is a static boolean variable that indicates whether + the initialization function has been called. If the library is + meant to be used in multithreaded applications, this variable needs + to be marked ‘volatile’, so that its value get propagated between + threads. Like this: + + static volatile bool libfoo_initialized; + + static void + libfoo_initialize (void) + { + bindtextdomain (PACKAGE, LOCALEDIR); + libfoo_initialized = true; + } + + /* This function is part of the exported API. */ + struct foo * + create_foo (...) + { + /* Must ensure the initialization is performed. */ + if (!libfoo_initialized) + libfoo_initialize (); + ... + } + + /* This function is part of the exported API. The argument must be + non-NULL and have been created through create_foo(). */ + int + foo_refcount (struct foo *argument) + { + /* No need to invoke the initialization function here, because + create_foo() must already have been called before. */ + ... + } + + The more general solution for initialization functions, POSIX + ‘pthread_once’, is not needed in this case. + + 4. The usual declaration of the ‘_’ macro in each source file was + + #include + #define _(String) gettext (String) + + for a program. For a library, which has its own translation + domain, it reads like this: + + #include + #define _(String) dgettext (PACKAGE, String) + + In other words, ‘dgettext’ is used instead of ‘gettext’. + Similarly, the ‘dngettext’ function should be used in place of the + ‘ngettext’ function. + + +File: gettext.info, Node: Template, Next: Creating, Prev: Sources, Up: Top + +5 Making the PO Template File +***************************** + + After preparing the sources, the programmer creates a PO template +file. This section explains how to use ‘xgettext’ for this purpose. + + ‘xgettext’ creates a file named ‘DOMAINNAME.po’. You should then +rename it to ‘DOMAINNAME.pot’. (Why doesn't ‘xgettext’ create it under +the name ‘DOMAINNAME.pot’ right away? The answer is: for historical +reasons. When ‘xgettext’ was specified, the distinction between a PO +file and PO file template was fuzzy, and the suffix ‘.pot’ wasn't in use +at that time.) + +* Menu: + +* xgettext Invocation:: Invoking the ‘xgettext’ Program +* Combining POTs:: Combining PO Template Files + + +File: gettext.info, Node: xgettext Invocation, Next: Combining POTs, Up: Template + +5.1 Invoking the ‘xgettext’ Program +=================================== + + xgettext [OPTION] [INPUTFILE] ... + + The ‘xgettext’ program extracts translatable strings from given input +files. + +5.1.1 Input file location +------------------------- + +‘INPUTFILE ...’ + Input files. + +‘-f FILE’ +‘--files-from=FILE’ + Read the names of the input files from FILE instead of getting them + from the command line. + + Often FILE is a temporary file, generated during the build process. + In this case, you should also pass the ‘--generated=FILE’ option. + +‘-D DIRECTORY’ +‘--directory=DIRECTORY’ + Add DIRECTORY to the list of directories. Source files are + searched relative to this list of directories. The resulting ‘.po’ + file will be written relative to the current directory, though. + + If INPUTFILE is ‘-’, standard input is read. + +5.1.2 Output file location +-------------------------- + +‘-d NAME’ +‘--default-domain=NAME’ + Use ‘NAME.po’ for output (instead of ‘messages.po’). + +‘-o FILE’ +‘--output=FILE’ + Write output to specified file (instead of ‘NAME.po’ or + ‘messages.po’). + +‘-p DIR’ +‘--output-dir=DIR’ + Output files will be placed in directory DIR. + + If the output FILE is ‘-’ or ‘/dev/stdout’, the output is written to +standard output. + +5.1.3 Choice of input file language +----------------------------------- + +‘-L NAME’ +‘--language=NAME’ + Specifies the language of the input files. The supported languages + are ‘C’, ‘C++’, ‘ObjectiveC’, ‘PO’, ‘Python’, ‘Java’, + ‘JavaProperties’, ‘C#’, ‘JavaScript’, ‘TypeScript’, ‘TSX’, + ‘Scheme’, ‘Guile’, ‘Lisp’, ‘EmacsLisp’, ‘librep’, ‘Rust’, ‘Go’, + ‘Ruby’, ‘Shell’, ‘awk’, ‘Lua’, ‘Modula-2’, ‘D’, ‘Smalltalk’, + ‘Vala’, ‘Tcl’, ‘Perl’, ‘PHP’, ‘GCC-source’, ‘YCP’, ‘NXStringTable’, + ‘RST’, ‘RSJ’, ‘Glade’, ‘GSettings’, ‘Desktop’. + +‘-C’ +‘--c++’ + This is a shorthand for ‘--language=C++’. + + By default the language is guessed depending on the input file name +extension. + +5.1.4 Input file interpretation +------------------------------- + +‘--from-code=NAME’ + Specifies the encoding of the input files. This option is needed + only if some untranslated message strings or their corresponding + comments contain non-ASCII characters. Note that Tcl and Glade + input files are always assumed to be in UTF-8, regardless of this + option. + + By default the input files are assumed to be in ASCII. + +5.1.5 Operation mode +-------------------- + +‘-j’ +‘--join-existing’ + Join messages with existing file. + +‘-x FILE’ +‘--exclude-file=FILE’ + Entries from FILE are not extracted. FILE should be a PO or POT + file. + +‘-c[TAG]’ +‘--add-comments[=TAG]’ + Place comment blocks starting with TAG and preceding keyword lines + in the output file. Without a TAG, the option means to put _all_ + comment blocks preceding keyword lines in the output file. + + Note that comment blocks are only extracted if there is no program + code between the comment and the string that gets extracted. For + example, in the following C source code: + + /* This is the first comment. */ + gettext ("foo"); + + /* This is the second comment: not extracted */ + gettext ( + "bar"); + + gettext ( + /* This is the third comment. */ + "baz"); + + /* This is the fourth comment. */ + + gettext ("I love blank lines in my programs"); + + the second comment line will not be extracted, because there is a + line with some tokens between the comment line and the line that + contains the string. But the fourth comment is extracted, because + between it and the line with the string there is merely a blank + line. + +‘--check[=CHECK]’ + Perform a syntax check on msgid and msgid_plural. The supported + checks are: + + ‘ellipsis-unicode’ + Prefer Unicode ellipsis character over ASCII ‘...’ + + ‘space-ellipsis’ + Prohibit whitespace before an ellipsis character + + ‘quote-unicode’ + Prefer Unicode quotation marks over ASCII ‘"'`’ + + ‘bullet-unicode’ + Prefer Unicode bullet character over ASCII ‘*’ or ‘-’ + + The option has an effect on all input files. To enable or disable + checks for a certain string, you can mark it with an ‘xgettext:’ + special comment in the source file. For example, if you specify + the ‘--check=space-ellipsis’ option, but want to suppress the check + on a particular string, add the following comment: + + /* xgettext: no-space-ellipsis-check */ + gettext ("We really want a space before ellipsis here ..."); + + The ‘xgettext:’ comment can be followed by flags separated with a + comma. The possible flags are of the form ‘[no-]NAME-check’, where + NAME is the name of a valid syntax check. If a flag is prefixed by + ‘no-’, the meaning is negated. + + Some tests apply the checks to each sentence within the msgid, + rather than the whole string. xgettext detects the end of sentence + by performing a pattern match, which usually looks for a period + followed by a certain number of spaces. The number is specified + with the ‘--sentence-end’ option. + +‘--sentence-end[=TYPE]’ + The supported values are: + + ‘single-space’ + Expect at least one whitespace after a period + + ‘double-space’ + Expect at least two whitespaces after a period + +5.1.6 Language specific options +------------------------------- + +‘-a’ +‘--extract-all’ + Extract all strings. + + This option has an effect with most languages, namely C, C++, + ObjectiveC, Python, Java, C#, JavaScript, Scheme, Guile, Lisp, + EmacsLisp, librep, Rust, Go, Shell, awk, Lua, Modula-2, D, Vala, + Tcl, Perl, PHP, GCC-source, Glade, GSettings. + +‘-k[KEYWORDSPEC]’ +‘--keyword[=KEYWORDSPEC]’ + Specify KEYWORDSPEC as an additional keyword to be looked for. + Without a KEYWORDSPEC, the option means to not use default + keywords. + + If KEYWORDSPEC is a C identifier ID, ‘xgettext’ looks for strings + in the first argument of each call to the function or macro ID. If + KEYWORDSPEC is of the form ‘ID:ARGNUM’, ‘xgettext’ looks for + strings in the ARGNUMth argument of the call. If KEYWORDSPEC is of + the form ‘ID:ARGNUM1,ARGNUM2’, ‘xgettext’ looks for strings in the + ARGNUM1st argument and in the ARGNUM2nd argument of the call, and + treats them as singular/plural variants for a message with plural + handling. Also, if KEYWORDSPEC is of the form + ‘ID:CONTEXTARGNUMc,ARGNUM’ or ‘ID:ARGNUM,CONTEXTARGNUMc’, + ‘xgettext’ treats strings in the CONTEXTARGNUMth argument as a + context specifier. And, as a special-purpose support for GNOME, if + KEYWORDSPEC is of the form ‘ID:ARGNUMg’, ‘xgettext’ recognizes the + ARGNUMth argument as a string with context, using the GNOME ‘glib’ + syntax ‘"msgctxt|msgid"’. + Furthermore, if KEYWORDSPEC is of the form ‘ID:...,TOTALNUMARGSt’, + ‘xgettext’ recognizes this argument specification only if the + number of actual arguments is equal to TOTALNUMARGS. This is + useful for disambiguating overloaded function calls in C++. + Finally, if KEYWORDSPEC is of the form ‘ID:ARGNUM...,"XCOMMENT"’, + ‘xgettext’, when extracting a message from the specified argument + strings, adds an extracted comment XCOMMENT to the message. Note + that when used through a normal shell command line, the + double-quotes around the XCOMMENT need to be escaped. + + This option has an effect with most languages, namely C, C++, + ObjectiveC, Python, Java, C#, JavaScript, TypeScript, TSX, Scheme, + Guile, Lisp, EmacsLisp, librep, Rust, Go, Shell, awk, Lua, + Modula-2, D, Vala, Tcl, Perl, PHP, GCC-source, Glade, GSettings, + Desktop. + + The default keyword specifications, which are always looked for if + not explicitly disabled, are language dependent. They are: + + • For C, C++, and GCC-source: ‘gettext’, ‘dgettext:2’, + ‘dcgettext:2’, ‘ngettext:1,2’, ‘dngettext:2,3’, + ‘dcngettext:2,3’, ‘gettext_noop’, and ‘pgettext:1c,2’, + ‘dpgettext:2c,3’, ‘dcpgettext:2c,3’, ‘npgettext:1c,2,3’, + ‘dnpgettext:2c,3,4’, ‘dcnpgettext:2c,3,4’. + + • For Objective C: Like for C, and also ‘NSLocalizedString’, + ‘_’, ‘NSLocalizedStaticString’, ‘__’. + + • For Shell scripts: ‘gettext’, ‘ngettext:1,2’, ‘eval_gettext’, + ‘eval_ngettext:1,2’, ‘eval_pgettext:1c,2’, + ‘eval_npgettext:1c,2,3’. + + • For Python: ‘gettext’, ‘ugettext’, ‘dgettext:2’, + ‘ngettext:1,2’, ‘ungettext:1,2’, ‘dngettext:2,3’, ‘_’. + + • For Lisp: ‘gettext’, ‘ngettext:1,2’, ‘gettext-noop’. + + • For EmacsLisp: ‘_’. + + • For librep: ‘_’. + + • For Scheme and Guile: ‘gettext’, ‘ngettext:1,2’, + ‘gettext-noop’. + + • For Java: ‘GettextResource.gettext:2’, + ‘GettextResource.ngettext:2,3’, + ‘GettextResource.pgettext:2c,3’, + ‘GettextResource.npgettext:2c,3,4’, ‘gettext’, ‘ngettext:1,2’, + ‘pgettext:1c,2’, ‘npgettext:1c,2,3’, ‘getString’. + + • For C#: ‘GetString’, ‘GetPluralString:1,2’, + ‘GetParticularString:1c,2’, + ‘GetParticularPluralString:1c,2,3’. + + • For awk: ‘dcgettext’, ‘dcngettext:1,2’. + + • For Tcl: ‘::msgcat::mc’. + + • For Perl: ‘gettext’, ‘%gettext’, ‘$gettext’, ‘dgettext:2’, + ‘dcgettext:2’, ‘ngettext:1,2’, ‘dngettext:2,3’, + ‘dcngettext:2,3’, ‘gettext_noop’. + + • For PHP: ‘_’, ‘gettext’, ‘dgettext:2’, ‘dcgettext:2’, + ‘ngettext:1,2’, ‘dngettext:2,3’, ‘dcngettext:2,3’. + + • For Glade 1: ‘label’, ‘title’, ‘text’, ‘format’, ‘copyright’, + ‘comments’, ‘preview_text’, ‘tooltip’. + + • For Lua: ‘_’, ‘gettext.gettext’, ‘gettext.dgettext:2’, + ‘gettext.dcgettext:2’, ‘gettext.ngettext:1,2’, + ‘gettext.dngettext:2,3’, ‘gettext.dcngettext:2,3’. + + • For D: ‘gettext’, ‘dgettext:2’, ‘dcgettext:2’, ‘ngettext:1,2’, + ‘dngettext:2,3’, ‘dcngettext:2,3’. + + • For JavaScript, TypeScript, TSX: ‘_’, ‘gettext’, ‘dgettext:2’, + ‘dcgettext:2’, ‘ngettext:1,2’, ‘dngettext:2,3’, + ‘pgettext:1c,2’, ‘dpgettext:2c,3’. + + • For Vala: ‘_’, ‘Q_’, ‘N_’, ‘NC_’, ‘dgettext:2’, ‘dcgettext:2’, + ‘ngettext:1,2’, ‘dngettext:2,3’, ‘dpgettext:2c,3’, + ‘dpgettext2:2c,3’. + + • For Desktop: ‘Name’, ‘GenericName’, ‘Comment’, ‘Keywords’. + + To disable the default keyword specifications, the option ‘-k’ or + ‘--keyword’ or ‘--keyword=’, without a KEYWORDSPEC, can be used. + +‘--flag=WORD:ARG:FLAG’ + Specifies additional flags for strings occurring as part of the + ARGth argument of the function WORD. The possible flags are the + possible format string indicators, such as ‘c-format’, and their + negations, such as ‘no-c-format’, possibly prefixed with ‘pass-’. + The meaning of ‘--flag=FUNCTION:ARG:LANG-format’ is that in + language LANG, the specified FUNCTION expects as ARGth argument a + format string. (For those of you familiar with GCC function + attributes, ‘--flag=FUNCTION:ARG:c-format’ is roughly equivalent to + the declaration ‘__attribute__ ((__format__ (__printf__, ARG, + ...)))’ attached to FUNCTION in a C source file.) For example, if + you use the ‘error’ function from GNU libc, you can specify its + behaviour through ‘--flag=error:3:c-format’. The effect of this + specification is that ‘xgettext’ will mark as format strings all + ‘gettext’ invocations that occur as ARGth argument of FUNCTION. + This is useful when such strings contain no format string + directives: together with the checks done by ‘msgfmt -c’ it will + ensure that translators cannot accidentally use format string + directives that would lead to a crash at runtime. + The meaning of ‘--flag=FUNCTION:ARG:pass-LANG-format’ is that in + language LANG, if the FUNCTION call occurs in a position that must + yield a format string, then its ARGth argument must yield a format + string of the same type as well. (If you know GCC function + attributes, the ‘--flag=FUNCTION:ARG:pass-c-format’ option is + roughly equivalent to the declaration ‘__attribute__ + ((__format_arg__ (ARG)))’ attached to FUNCTION in a C source file.) + For example, if you use the ‘_’ shortcut for the ‘gettext’ + function, you should use ‘--flag=_:1:pass-c-format’. The effect of + this specification is that ‘xgettext’ will propagate a format + string requirement for a ‘_("string")’ call to its first argument, + the literal ‘"string"’, and thus mark it as a format string. This + is useful when such strings contain no format string directives: + together with the checks done by ‘msgfmt -c’ it will ensure that + translators cannot accidentally use format string directives that + would lead to a crash at runtime. + This option has an effect with most languages, namely C, C++, + ObjectiveC, Python, Java, C#, JavaScript, TypeScript, TSX, Scheme, + Guile, Lisp, EmacsLisp, librep, Rust, Go, Shell, awk, Lua, + Modula-2, D, Vala, Tcl, Perl, PHP, GCC-source, YCP. + +‘--tag=WORD:FORMAT’ + Defines the behaviour of tagged template literals with tag WORD. + This option has an effect only with language JavaScript. + FORMAT is a symbolic description of the first step of the + JavaScript function named WORD, namely how this function constructs + a format string based on the parts of the template literal. + Currently only one value is supported: ‘javascript-gnome-format’, + which describes the construction of a format string with numbered + placeholders ‘{0}’, ‘{1}’, ‘{2}’, etc. For example, + ‘javascript-gnome-format’ transforms the template literal ‘WORD`My + name is ${id.name} and I am ${id.age} years old.`’ into the format + string ‘"My name is {0} and I am {1} years old."’. + +‘-T’ +‘--trigraphs’ + Understand ANSI C trigraphs for input (deprecated, since trigraphs + have been removed from ISO C 23). + This option has an effect only with the languages C, C++, + ObjectiveC. + +‘--qt’ + Recognize Qt format strings. + This option has an effect only with the language C++. + +‘--kde’ + Recognize KDE 4 format strings. + This option has an effect only with the language C++. + +‘--boost’ + Recognize Boost format strings. + This option has an effect only with the language C++. + +‘--debug’ + Use the flags ‘c-format’ and ‘possible-c-format’ to show who was + responsible for marking a message as a format string. The latter + form is used if the ‘xgettext’ program decided, the former form is + used if the programmer prescribed it. + + By default only the ‘c-format’ form is used. The translator should + not have to care about these details. + + This implementation of ‘xgettext’ is able to process a few awkward +cases, like strings in preprocessor macros, ANSI concatenation of +adjacent strings, and escaped end of lines for continued strings. + +5.1.7 Options for XML input files +--------------------------------- + + When some of the input files are XML files and they are not of one of +the types covered by the system-wide installed *.its files, a *.its file +is needed for each such file type, so that ‘xgettext’ can handle them. +There are two ways to specify such a file: + + • ‘--its=FILE’ + Use the ITS rules defined in FILE. + + • The environment variable ‘GETTEXTDATADIRS’. Together with the + *.its file, you need a corresponding *.loc file (*note Preparing + ITS Rules::). Furthermore you need to store these files in a + directory ‘PARENT_DIR/its/’ and set the environment variable + ‘GETTEXTDATADIRS’ to include ‘PARENT_DIR’. More generally, the + value of ‘GETTEXTDATADIRS’ should be a colon-separated list of + directory names. + + Note that when the option ‘--its’ is specified, the system-wide +installed *.its files are ignored and the environment variable +‘GETTEXTDATADIRS’ has no effect either. + +5.1.8 Output details +-------------------- + +‘--color’ +‘--color=WHEN’ + Specify whether or when to use colors and other text attributes. + See *note The --color option:: for details. + +‘--style=STYLE_FILE’ + Specify the CSS style rule file to use for ‘--color’. See *note + The --style option:: for details. + +‘--force-po’ + Always write an output file even if no message is defined. + +‘-i’ +‘--indent’ + Write the .po file using indented style. + +‘--no-location’ + Do not write ‘#: FILENAME:LINE’ lines. Note that using this option + makes it harder for technically skilled translators to understand + each message's context. + +‘-n’ +‘--add-location=TYPE’ + Generate ‘#: FILENAME:LINE’ lines (default). + + The optional TYPE can be either ‘full’, ‘file’, or ‘never’. If it + is not given or ‘full’, it generates the lines with both file name + and line number. If it is ‘file’, the line number part is omitted. + If it is ‘never’, it completely suppresses the lines (same as + ‘--no-location’). + +‘--strict’ + Write out a strict Uniforum conforming PO file. Note that this + Uniforum format should be avoided because it doesn't support the + GNU extensions. + +‘--properties-output’ + Write out a Java ResourceBundle in Java ‘.properties’ syntax. Note + that this file format doesn't support plural forms and silently + drops obsolete messages. + +‘--stringtable-output’ + Write out a NeXTstep/GNUstep localized resource file in ‘.strings’ + syntax. Note that this file format doesn't support plural forms. + +‘--itstool’ + Write out comments recognized by itstool (). + Note that this is only effective with XML files. + +‘-w NUMBER’ +‘--width=NUMBER’ + Set the output page width. Long strings in the output files will + be split across multiple lines in order to ensure that each line's + width (= number of screen columns) is less or equal to the given + NUMBER. + +‘--no-wrap’ + Do not break long message lines. Message lines whose width exceeds + the output page width will not be split into several lines. Only + file reference lines which are wider than the output page width + will be split. + +‘-s’ +‘--sort-output’ + Generate sorted output (deprecated). Note that using this option + makes it much harder for the translator to understand each + message's context. + +‘-F’ +‘--sort-by-file’ + Sort output by file location. + +‘--omit-header’ + Don't write header with ‘msgid ""’ entry. Note: Using this option + may lead to an error in subsequent operations if the output + contains non-ASCII characters. + + This is useful for testing purposes because it eliminates a source + of variance for generated ‘.gmo’ files. With ‘--omit-header’, two + invocations of ‘xgettext’ on the same files with the same options + at different times are guaranteed to produce the same results. + + Note that using this option will lead to an error if the resulting + file would not entirely be in ASCII. + +‘--no-git’ + Don't use the ‘git’ program to produce a reproducible + ‘POT-Creation-Date’ field in the output. + + Use this option, for speed, if your project has a very long ‘Git’ + history (hundreds of thousands of commits) or you are specifying + thousands of input files. + + By default, ‘xgettext’ determines the ‘POT-Creation-Date’ as the + maximum version-controlled modification time among all the given + input files. With this option, you can specify that it should + instead use the maximum modification time (time stamp on disk) + among all the given input files. + + By "version control", here we mean the ‘Git’ version control + system. + +‘--copyright-holder=STRING’ + Set the copyright holder in the output. STRING should be the + copyright holder of the surrounding package. (Note that the + ‘msgid’ strings, extracted from the package's sources, belong to + the copyright holder of the package.) Translators are expected to + transfer or disclaim the copyright for their translations, so that + package maintainers can distribute them without legal risk. If + STRING is empty, the output files are marked as being in the public + domain; in this case, the translators are expected to disclaim + their copyright, again so that package maintainers can distribute + them without legal risk. + + The default value for STRING is the Free Software Foundation, Inc., + simply because ‘xgettext’ was first used in the GNU project. + +‘--foreign-user’ + Omit FSF copyright in output. This option is equivalent to + ‘--copyright-holder=''’. It can be useful for packages outside the + GNU project that want their translations to be in the public + domain. + +‘--package-name=PACKAGE’ + Set the package name in the header of the output. + +‘--package-version=VERSION’ + Set the package version in the header of the output. This option + has an effect only if the ‘--package-name’ option is also used. + +‘--msgid-bugs-address=EMAIL@ADDRESS’ + Set the reporting address for msgid bugs. This is the email + address or URL to which the translators shall report bugs in the + untranslated strings: + + - Strings which are not entire sentences; see the maintainer + guidelines in *note Preparing Strings::. + - Strings which use unclear terms or require additional context + to be understood. + - Strings which make invalid assumptions about notation of date, + time or money. + - Pluralisation problems. + - Incorrect English spelling. + - Incorrect formatting. + + It can be your email address, or a mailing list address where + translators can write to without being subscribed, or the URL of a + web page through which the translators can contact you. + + The default value is empty, which means that translators will be + clueless! Don't forget to specify this option. + +‘--generated=FILE’ + + Declares that the given FILE is generated and therefore should not + have an influence on the ‘POT-Creation-Date’ field in the output. + + When you specify this option, you should also specify one or more + ‘--reference’ options, to indicate the files from which the given + FILE was generated. + +‘--reference=FILE’ + + Declares that the output depends on the contents of the given FILE. + This has an influence on the ‘POT-Creation-Date’ field in the + output. + + By default, ‘xgettext’ determines the ‘POT-Creation-Date’ as the + maximum version-controlled modification time among all the given + input files. With this option, you can specify that the output + depends also on some other files. For example, use this option + when some of the input files is not under version control but + instead is generated from one or more files that are under version + control. + + By "version control", here we mean the ‘Git’ version control + system. + +‘-m[STRING]’ +‘--msgstr-prefix[=STRING]’ + Use STRING (or "" if not specified) as prefix for msgstr values. + +‘-M[STRING]’ +‘--msgstr-suffix[=STRING]’ + Use STRING (or "" if not specified) as suffix for msgstr values. + +5.1.9 Informative output +------------------------ + +‘-h’ +‘--help’ + Display this help and exit. + +‘-V’ +‘--version’ + Output version information and exit. + +‘-v’ +‘--verbose’ + Increase verbosity level. + +5.1.10 Example +-------------- + + A sample invocation of ‘xgettext’, in a project that has a single +source file ‘src/hello.c’ that uses ‘_’ as shorthand for the ‘gettext’ +function, could be: + + xgettext -o hello.pot \ + --add-comments=TRANSLATORS: \ + --keyword=_ --flag=_:1:pass-c-format \ + --directory=.. \ + src/hello.c + + +File: gettext.info, Node: Combining POTs, Prev: xgettext Invocation, Up: Template + +5.2 Combining PO Template Files +=============================== + + When a package contains sources in different programming languages +and different, incompatible ‘xgettext’ command line options are required +for these different parts of the package, the solution is to create +intermediate PO template files for each of the parts and then combine +(merge) them together. + + For example, assume you have two source files ‘a.c’ and ‘b.py’, and +want to extract their translatable strings in separate steps. + + Each of the following command sequences does this. The output is the +same. + + • This command sequence creates intermediate POT files and then + combines them. + xgettext -o part-c.pot a.c + xgettext -o part-py.pot b.py + xgettext -o all.pot part-c.pot part-py.pot + • This command sequence does several ‘xgettext’ invocations, with a + single POT file that accumulates the translatable strings. + xgettext -o all.pot a.c + xgettext -o all.pot --join-existing b.py + • Likewise here, but a ‘--default-domain’ option is used to denote + the output file rather than a ‘-o’ option. + xgettext --default-domain=all a.c + xgettext --default-domain=all --join-existing b.py + mv all.po all.pot + + One might be tempted to think that ‘msgcat’ can do the same thing, +through a command sequence such as: + xgettext -o part-c.pot a.c + xgettext -o part-py.pot b.py + msgcat -o all.pot part-c.pot part-py.pot +But no, this does not work reliably, because sometimes ‘part-c.pot’ and +‘part-py.pot’ will contain different ‘POT-Creation-Date’ values, and +‘msgcat’ then produces an ‘all.pot’ file that has conflict markers in +the header entry. This is because ‘msgcat’ generally is meant to +produce PO files that are to be reviewed and edited by a translator; +this is not desired here. + + +File: gettext.info, Node: Creating, Next: Updating, Prev: Template, Up: Top + +6 Creating a New PO File +************************ + + When starting a new translation, the translator creates a file called +‘LANG.po’, as a copy of the ‘PACKAGE.pot’ template file with +modifications in the initial comments (at the beginning of the file) and +in the header entry (the first entry, near the beginning of the file). + + The easiest way to do so is by use of the ‘msginit’ program. For +example: + + $ cd PACKAGE-VERSION + $ cd po + $ msginit + + The alternative way is to do the copy and modifications by hand. To +do so, the translator copies ‘PACKAGE.pot’ to ‘LANG.po’. Then she +modifies the initial comments and the header entry of this file. + +* Menu: + +* msginit Invocation:: Invoking the ‘msginit’ Program +* Header Entry:: Filling in the Header Entry + + +File: gettext.info, Node: msginit Invocation, Next: Header Entry, Up: Creating + +6.1 Invoking the ‘msginit’ Program +================================== + + msginit [OPTION] + + The ‘msginit’ program creates a new PO file, initializing the meta +information with values from the user's environment. + + Here are more details. The following header fields of a PO file are +automatically filled, when possible. + +‘Project-Id-Version’ + The value is guessed from the ‘configure’ script or any other files + in the current directory. + +‘PO-Revision-Date’ + The value is taken from the ‘PO-Creation-Data’ in the input POT + file, or the current date is used. + +‘Last-Translator’ + The value is taken from user's password file entry and the mailer + configuration files. + +‘Language-Team, Language’ + These values are set according to the current locale and the + predefined list of translation teams. + +‘MIME-Version, Content-Type, Content-Transfer-Encoding’ + These values are set according to the content of the POT file and + the current locale. If the POT file contains charset=UTF-8, it + means that the POT file contains non-ASCII characters, and we keep + the UTF-8 encoding. Otherwise, when the POT file is plain ASCII, + we use the locale's encoding. + +‘Plural-Forms’ + The value is first looked up from the embedded table. + + As an experimental feature, you can instruct ‘msginit’ to use the + information from Unicode CLDR, by setting the ‘GETTEXTCLDRDIR’ + environment variable. The program will look for a file named + ‘common/supplemental/plurals.xml’ under that directory. You can + get the CLDR data from . + +6.1.1 Input file location +------------------------- + +‘-i INPUTFILE’ +‘--input=INPUTFILE’ + Input POT file. + + If no INPUTFILE is given, the current directory is searched for the +POT file. If it is ‘-’, standard input is read. + +6.1.2 Output file location +-------------------------- + +‘-o FILE’ +‘--output-file=FILE’ + Write output to specified PO file. + + If no output file is given, it depends on the ‘--locale’ option or +the user's locale setting. If it is ‘-’, the results are written to +standard output. + +6.1.3 Input file syntax +----------------------- + +‘-P’ +‘--properties-input’ + Assume the input file is a Java ResourceBundle in Java + ‘.properties’ syntax, not in PO file syntax. + +‘--stringtable-input’ + Assume the input file is a NeXTstep/GNUstep localized resource file + in ‘.strings’ syntax, not in PO file syntax. + +6.1.4 Output details +-------------------- + +‘-l LL_CC[.ENCODING]’ +‘--locale=LL_CC[.ENCODING]’ + Set target locale. LL should be a language code, and CC should be + a country code. The optional part .ENCODING specifies the encoding + of the locale; most often this part is ‘.UTF-8’. The command + ‘locale -a’ can be used to output a list of all installed locales. + The default is the user's locale setting. + +‘--no-translator’ + Declares that the PO file will not have a human translator and is + instead automatically generated. + +‘--color’ +‘--color=WHEN’ + Specify whether or when to use colors and other text attributes. + See *note The --color option:: for details. + +‘--style=STYLE_FILE’ + Specify the CSS style rule file to use for ‘--color’. See *note + The --style option:: for details. + +‘-p’ +‘--properties-output’ + Write out a Java ResourceBundle in Java ‘.properties’ syntax. Note + that this file format doesn't support plural forms and silently + drops obsolete messages. + +‘--stringtable-output’ + Write out a NeXTstep/GNUstep localized resource file in ‘.strings’ + syntax. Note that this file format doesn't support plural forms. + +‘-w NUMBER’ +‘--width=NUMBER’ + Set the output page width. Long strings in the output files will + be split across multiple lines in order to ensure that each line's + width (= number of screen columns) is less or equal to the given + NUMBER. + +‘--no-wrap’ + Do not break long message lines. Message lines whose width exceeds + the output page width will not be split into several lines. Only + file reference lines which are wider than the output page width + will be split. + +6.1.5 Informative output +------------------------ + +‘-h’ +‘--help’ + Display this help and exit. + +‘-V’ +‘--version’ + Output version information and exit. + + +File: gettext.info, Node: Header Entry, Prev: msginit Invocation, Up: Creating + +6.2 Filling in the Header Entry +=============================== + + The initial comments "SOME DESCRIPTIVE TITLE", "YEAR" and "FIRST +AUTHOR , YEAR" ought to be replaced by sensible +information. This can be done in any text editor; if Emacs is used and +it switched to PO mode automatically (because it has recognized the +file's suffix), you can disable it by typing ‘M-x fundamental-mode’. + + Modifying the header entry can already be done using PO mode: in +Emacs, type ‘M-x po-mode RET’ and then ‘RET’ again to start editing the +entry. You should fill in the following fields. + +Project-Id-Version + This is the name and version of the package. Fill it in if it has + not already been filled in by ‘xgettext’. + +Report-Msgid-Bugs-To + This has already been filled in by ‘xgettext’. It contains an + email address or URL where you can report bugs in the untranslated + strings: + + - Strings which are not entire sentences, see the maintainer + guidelines in *note Preparing Strings::. + - Strings which use unclear terms or require additional context + to be understood. + - Strings which make invalid assumptions about notation of date, + time or money. + - Pluralisation problems. + - Incorrect English spelling. + - Incorrect formatting. + +POT-Creation-Date + This has already been filled in by ‘xgettext’. + +PO-Revision-Date + You don't need to fill this in. It will be filled by the PO file + editor when you save the file. + +Last-Translator + Fill in your name and email address (without double quotes). + +Language-Team + Fill in the English name of the language, and the email address or + homepage URL of the language team you are part of. + + Before starting a translation, it is a good idea to get in touch + with your translation team, not only to make sure you don't do + duplicated work, but also to coordinate difficult linguistic + issues. + + In the Free Translation Project, each translation team has its own + mailing list. The up-to-date list of teams can be found at the + Free Translation Project's homepage, + , in the "Teams" area. + +Language + Fill in the language code of the language. This can be in one of + three forms: + + - ‘LL’, an ISO 639 two-letter language code (lowercase). For + some languages, a two-letter code does not exist, and a + three-letter code is used instead. See *note Language Codes:: + for the list of codes. + + - ‘LL_CC’, where ‘LL’ is an ISO 639 two-letter or three-letter + language code (lowercase) and ‘CC’ is an ISO 3166 two-letter + country code (uppercase). The country code specification is + not redundant: Some languages have dialects in different + countries. For example, ‘de_AT’ is used for Austria, and + ‘pt_BR’ for Brazil. The country code serves to distinguish + the dialects. See *note Language Codes:: and *note Country + Codes:: for the lists of codes. + + - ‘LL_CC@VARIANT’, where ‘LL’ is an ISO 639 two-letter or + three-letter language code (lowercase), ‘CC’ is an ISO 3166 + two-letter country code (uppercase), and ‘VARIANT’ is a + variant designator. The variant designator (lowercase) can be + a script designator, such as ‘latin’ or ‘cyrillic’. + + The naming convention ‘LL_CC’ is also the way locales are named on + systems based on GNU libc. But there are three important + differences: + + • In this PO file field, but not in locale names, ‘LL_CC’ + combinations denoting a language's main dialect are + abbreviated as ‘LL’. For example, ‘de’ is equivalent to + ‘de_DE’ (German as spoken in Germany), and ‘pt’ to ‘pt_PT’ + (Portuguese as spoken in Portugal) in this context. + + • In this PO file field, suffixes like ‘.ENCODING’ are not used. + + • In this PO file field, variant designators that are not + relevant to message translation, such as ‘@euro’, are not + used. + + So, if your locale name is ‘de_DE.UTF-8’, the language + specification in PO files is just ‘de’. + +Content-Type + Replace ‘CHARSET’ with the character encoding used for your + language, in your locale, or UTF-8. This field is needed for + correct operation of the ‘msgmerge’ and ‘msgfmt’ programs, as well + as for users whose locale's character encoding differs from yours + (see *note Charset conversion::). + + You get the character encoding of your locale by running the shell + command ‘locale charmap’. If the result is ‘C’ or + ‘ANSI_X3.4-1968’, which is equivalent to ‘ASCII’ (= ‘US-ASCII’), it + means that your locale is not correctly configured. In this case, + ask your translation team which charset to use. ‘ASCII’ is not + usable for any language except Latin. + + Because the PO files must be portable to operating systems with + less advanced internationalization facilities, the character + encodings that can be used are limited to those supported by both + GNU ‘libc’ and GNU ‘libiconv’. These are: ‘ASCII’, ‘ISO-8859-1’, + ‘ISO-8859-2’, ‘ISO-8859-3’, ‘ISO-8859-4’, ‘ISO-8859-5’, + ‘ISO-8859-6’, ‘ISO-8859-7’, ‘ISO-8859-8’, ‘ISO-8859-9’, + ‘ISO-8859-13’, ‘ISO-8859-14’, ‘ISO-8859-15’, ‘KOI8-R’, ‘KOI8-U’, + ‘KOI8-T’, ‘CP850’, ‘CP866’, ‘CP874’, ‘CP932’, ‘CP949’, ‘CP950’, + ‘CP1250’, ‘CP1251’, ‘CP1252’, ‘CP1253’, ‘CP1254’, ‘CP1255’, + ‘CP1256’, ‘CP1257’, ‘GB2312’, ‘EUC-JP’, ‘EUC-KR’, ‘EUC-TW’, ‘BIG5’, + ‘BIG5-HKSCS’, ‘GBK’, ‘GB18030’, ‘SHIFT_JIS’, ‘JOHAB’, ‘TIS-620’, + ‘VISCII’, ‘GEORGIAN-PS’, ‘UTF-8’. + + In the GNU system, the following encodings are frequently used for + the corresponding languages. + + • ‘ISO-8859-1’ for Afrikaans, Albanian, Basque, Breton, Catalan, + Cornish, Danish, Dutch, English, Estonian, Faroese, Finnish, + French, Galician, German, Greenlandic, Icelandic, Indonesian, + Irish, Italian, Malay, Manx, Norwegian, Occitan, Portuguese, + Spanish, Swedish, Tagalog, Uzbek, Walloon, + • ‘ISO-8859-2’ for Bosnian, Croatian, Czech, Hungarian, Polish, + Romanian, Serbian, Slovak, Slovenian, + • ‘ISO-8859-3’ for Maltese, + • ‘ISO-8859-5’ for Macedonian, Serbian, + • ‘ISO-8859-6’ for Arabic, + • ‘ISO-8859-7’ for Greek, + • ‘ISO-8859-8’ for Hebrew, + • ‘ISO-8859-9’ for Turkish, + • ‘ISO-8859-13’ for Latvian, Lithuanian, Maori, + • ‘ISO-8859-14’ for Welsh, + • ‘ISO-8859-15’ for Basque, Catalan, Dutch, English, Finnish, + French, Galician, German, Irish, Italian, Portuguese, Spanish, + Swedish, Walloon, + • ‘KOI8-R’ for Russian, + • ‘KOI8-U’ for Ukrainian, + • ‘KOI8-T’ for Tajik, + • ‘CP1251’ for Bulgarian, Belarusian, + • ‘GB2312’, ‘GBK’, ‘GB18030’ for simplified writing of Chinese, + • ‘BIG5’, ‘BIG5-HKSCS’ for traditional writing of Chinese, + • ‘EUC-JP’ for Japanese, + • ‘EUC-KR’ for Korean, + • ‘TIS-620’ for Thai, + • ‘GEORGIAN-PS’ for Georgian, + • ‘UTF-8’ for any language, including those listed above. + + When single quote characters or double quote characters are used in + translations for your language, and your locale's encoding is one + of the ISO-8859-* charsets, it is best if you create your PO files + in UTF-8 encoding, instead of your locale's encoding. This is + because in UTF-8 the real quote characters can be represented + (single quote characters: U+2018, U+2019, double quote characters: + U+201C, U+201D), whereas none of ISO-8859-* charsets has them all. + Users in UTF-8 locales will see the real quote characters, whereas + users in ISO-8859-* locales will see the vertical apostrophe and + the vertical double quote instead (because that's what the + character set conversion will transliterate them to). + + To enter such quote characters under X11, you can change your + keyboard mapping using the ‘xmodmap’ program. The X11 names of the + quote characters are "leftsinglequotemark", "rightsinglequotemark", + "leftdoublequotemark", "rightdoublequotemark", + "singlelowquotemark", "doublelowquotemark". + + The character encoding name can be written in either upper or lower + case. Usually upper case is preferred. + +Content-Transfer-Encoding + Set this to ‘8bit’. + +Plural-Forms + This field is optional. It is only needed if the PO file has + plural forms. You can find them by searching for the + ‘msgid_plural’ keyword. The format of the plural forms field is + described in *note Plural forms:: and *note Translating plural + forms::. + + +File: gettext.info, Node: Updating, Next: Editing, Prev: Creating, Up: Top + +7 Updating Existing PO Files +**************************** + +* Menu: + +* msgmerge Invocation:: Invoking the ‘msgmerge’ Program + + +File: gettext.info, Node: msgmerge Invocation, Up: Updating + +7.1 Invoking the ‘msgmerge’ Program +=================================== + + msgmerge [OPTION] DEF.po REF.pot + + The ‘msgmerge’ program merges two Uniforum style .po files together. +The DEF.po file is an existing PO file with translations which will be +taken over to the newly created file as long as they still match; +comments will be preserved, but extracted comments and file positions +will be discarded. The REF.pot file is the last created PO file with +up-to-date source references but old translations, or a PO Template file +(generally created by ‘xgettext’); any translations or comments in the +file will be discarded, however dot comments and file positions will be +preserved. Where an exact match cannot be found, fuzzy matching is used +to produce better results. + +7.1.1 Input file location +------------------------- + +‘DEF.po’ + Translations referring to old sources. + +‘REF.pot’ + References to the new sources. + +‘-D DIRECTORY’ +‘--directory=DIRECTORY’ + Add DIRECTORY to the list of directories. Source files are + searched relative to this list of directories. The resulting ‘.po’ + file will be written relative to the current directory, though. + +‘-C FILE’ +‘--compendium=FILE’ + Specify an additional library of message translations. *Note + Compendium::. This option may be specified more than once. + +7.1.2 Operation mode +-------------------- + +‘-U’ +‘--update’ + Update DEF.po. Do nothing if DEF.po is already up to date. + +7.1.3 Output file location +-------------------------- + +‘-o FILE’ +‘--output-file=FILE’ + Write output to specified file. + + The results are written to standard output if no output file is +specified or if it is ‘-’. + +7.1.4 Output file location in update mode +----------------------------------------- + + The result is written back to DEF.po. + +‘--backup=CONTROL’ + Make a backup of DEF.po + +‘--suffix=SUFFIX’ + Override the usual backup suffix. + + The version control method may be selected via the ‘--backup’ option +or through the ‘VERSION_CONTROL’ environment variable. Here are the +values: + +‘none’ +‘off’ + Never make backups (even if ‘--backup’ is given). + +‘numbered’ +‘t’ + Make numbered backups. + +‘existing’ +‘nil’ + Make numbered backups if numbered backups for this file already + exist, otherwise make simple backups. + +‘simple’ +‘never’ + Always make simple backups. + + The backup suffix is ‘~’, unless set with ‘--suffix’ or the +‘SIMPLE_BACKUP_SUFFIX’ environment variable. + +7.1.5 Operation modifiers +------------------------- + +‘-m’ +‘--multi-domain’ + Apply REF.pot to each of the domains in DEF.po. + +‘--for-msgfmt’ + Produce a PO file meant for ‘msgfmt’ only, not for a translator. + This option omits untranslated messages, fuzzy messages (except the + header entry), and obsolete messages from the output. Also, it + omits translator comments and ‘#: FILENAME:LINE’ lines from the + output. In particular, this option implies ‘--no-fuzzy-matching’. + +‘-N’ +‘--no-fuzzy-matching’ + Do not use fuzzy matching when an exact match is not found. This + may speed up the operation considerably. + +‘--previous’ + Keep the previous msgids of translated messages, marked with ‘#|’, + when adding the fuzzy marker to such messages. + +7.1.6 Input file syntax +----------------------- + +‘-P’ +‘--properties-input’ + Assume the input files are Java ResourceBundles in Java + ‘.properties’ syntax, not in PO file syntax. + +‘--stringtable-input’ + Assume the input files are NeXTstep/GNUstep localized resource + files in ‘.strings’ syntax, not in PO file syntax. + +7.1.7 Output details +-------------------- + +‘--lang=CATALOGNAME’ + Specify the ‘Language’ field to be used in the header entry. See + *note Header Entry:: for the meaning of this field. Note: The + ‘Language-Team’ and ‘Plural-Forms’ fields are left unchanged. If + this option is not specified, the ‘Language’ field is inferred, as + best as possible, from the ‘Language-Team’ field. + +‘--color’ +‘--color=WHEN’ + Specify whether or when to use colors and other text attributes. + See *note The --color option:: for details. + +‘--style=STYLE_FILE’ + Specify the CSS style rule file to use for ‘--color’. See *note + The --style option:: for details. + +‘--force-po’ + Always write an output file even if it contains no message. + +‘-i’ +‘--indent’ + Write the .po file using indented style. + +‘--no-location’ + Do not write ‘#: FILENAME:LINE’ lines. + +‘-n’ +‘--add-location=TYPE’ + Generate ‘#: FILENAME:LINE’ lines (default). + + The optional TYPE can be either ‘full’, ‘file’, or ‘never’. If it + is not given or ‘full’, it generates the lines with both file name + and line number. If it is ‘file’, the line number part is omitted. + If it is ‘never’, it completely suppresses the lines (same as + ‘--no-location’). + +‘--strict’ + Write out a strict Uniforum conforming PO file. Note that this + Uniforum format should be avoided because it doesn't support the + GNU extensions. + +‘-p’ +‘--properties-output’ + Write out a Java ResourceBundle in Java ‘.properties’ syntax. Note + that this file format doesn't support plural forms and silently + drops obsolete messages. + +‘--stringtable-output’ + Write out a NeXTstep/GNUstep localized resource file in ‘.strings’ + syntax. Note that this file format doesn't support plural forms. + +‘-w NUMBER’ +‘--width=NUMBER’ + Set the output page width. Long strings in the output files will + be split across multiple lines in order to ensure that each line's + width (= number of screen columns) is less or equal to the given + NUMBER. + +‘--no-wrap’ + Do not break long message lines. Message lines whose width exceeds + the output page width will not be split into several lines. Only + file reference lines which are wider than the output page width + will be split. + +‘-s’ +‘--sort-output’ + Generate sorted output (deprecated). Note that using this option + makes it much harder for the translator to understand each + message's context. + +‘-F’ +‘--sort-by-file’ + Sort output by file location. + +7.1.8 Informative output +------------------------ + +‘-h’ +‘--help’ + Display this help and exit. + +‘-V’ +‘--version’ + Output version information and exit. + +‘-v’ +‘--verbose’ + Increase verbosity level. + +‘-q’ +‘--quiet’ +‘--silent’ + Suppress progress indicators. + + +File: gettext.info, Node: Editing, Next: Manipulating, Prev: Updating, Up: Top + +8 Editing PO Files +****************** + + As a translator, you will typically edit a PO file in an editor that +has built-in knowledge about the PO file format. You most probably +won't want to edit a PO file in a text editor for plain-text files, +because that would be cumbersome regarding cursor navigation and would +also easily lead to syntax mistakes. + +* Menu: + +* Web based localization:: Web-based PO editing +* Lokalize:: KDE's PO File Editor +* Gtranslator:: GNOME's PO File Editor +* Poedit:: A simple PO File Editor +* OmegaT:: A powerful Translation Editor +* Virtaal:: The Virtaal Translation Editor +* PO Mode:: Emacs's PO File Editor +* Vim:: Editing PO Files in vim +* Compendium:: Using Translation Compendia + + +File: gettext.info, Node: Web based localization, Next: Lokalize, Up: Editing + +8.1 Web-based PO editing +======================== + + There are two ways to edit a PO file: either through a web-based PO +editor, in a browser, or through a PO editor that you can install on +your computer. Which one you choose, depends on your habits. + + Typically, the software project for which you want to provide +translations has set up a workflow that you, as a translator, have to +follow. + + • There are projects which use the Weblate (https://weblate.org/) + localization suite. In this case, you have the choice between a + web-based PO editor + (https://docs.weblate.org/en/latest/user/translating.html) and a + workflow (https://docs.weblate.org/en/latest/user/files.html) where + you download the previous translation, update it with your + preferred PO editor, and then upload it back. + + • There are projects which offer you only a web-based PO editor, as + only choice. Since web-based tools restrict your freedom as a user + - you cannot make modifications on your own to that tool -, you + should complain to that project and claim the choice of using a + locally installed PO editor, because that is the only way that can + guarantee your freedom of choice and freedom to modify the + software. + + • There are projects which do not support web-based localizations. + In this case, pick a PO file editor as listed in the next few + sections. Examples for such projects are the Free Translation + Project (https://translationproject.org/), as well as projects + where you directly interact with the version control system of the + project. + + +File: gettext.info, Node: Lokalize, Next: Gtranslator, Prev: Web based localization, Up: Editing + +8.2 KDE's PO File Editor +======================== + + Lokalize () is the PO file editor +made by the KDE project. It is present in many +(https://repology.org/project/lokalize/versions) GNU/Linux +distributions. + + +File: gettext.info, Node: Gtranslator, Next: Poedit, Prev: Lokalize, Up: Editing + +8.3 GNOME's PO File Editor +========================== + + Gtranslator () is the PO +file editor made by the GNOME project. It is present in many +(https://repology.org/project/gtranslator/versions) GNU/Linux +distributions. + + +File: gettext.info, Node: Poedit, Next: OmegaT, Prev: Gtranslator, Up: Editing + +8.4 Poedit +========== + + Poedit () is another decent PO +file editor. It works on all major desktop OSes and is present in many +(https://repology.org/project/poedit/versions) GNU/Linux distributions. + + +File: gettext.info, Node: OmegaT, Next: Virtaal, Prev: Poedit, Up: Editing + +8.5 OmegaT +========== + + OmegaT (Wikipedia: , home page: +, code: ) is +a translation editor that focuses on speeding up the translator's work +through advanced features like translation memory, spell-checking, +glossaries, dictionaries. It supports not only PO files, but also +direct translation of various file formats (such as plain text, web +pages, OpenDocument files, DocBook XML, etc.) without using +intermediate files. It is present in many +(https://repology.org/omegat/poedit/versions) GNU/Linux distributions. + + +File: gettext.info, Node: Virtaal, Next: PO Mode, Prev: OmegaT, Up: Editing + +8.6 The Virtaal Translation Editor +================================== + + Virtaal (Wikipedia: , home +page: , code: +) is a translation editor that +supports not only PO files but also XLIFF files. It is present in some +(https://repology.org/project/virtaal/versions) GNU/Linux distributions, +such as Debian up to Debian 11. + + +File: gettext.info, Node: PO Mode, Next: Vim, Prev: Virtaal, Up: Editing + +8.7 Emacs's PO File Editor +========================== + + For those of you being the lucky users of Emacs, PO mode has been +specifically created for providing a cozy environment for editing or +modifying PO files. While editing a PO file, PO mode allows for the +easy browsing of auxiliary and compendium PO files, as well as for +following references into the set of C program sources from which PO +files have been derived. It has a few special features, among which are +the interactive marking of program strings as translatable, and the +validation of PO files with easy repositioning to PO file lines showing +errors. + + For the beginning, besides main PO mode commands (*note Main PO +Commands::), you should know how to move between entries (*note Entry +Positioning::), and how to handle untranslated entries (*note +Untranslated Entries::). + +* Menu: + +* Installation:: Completing GNU ‘gettext’ Installation +* Main PO Commands:: Main Commands +* Entry Positioning:: Entry Positioning +* Normalizing:: Normalizing Strings in Entries +* Translated Entries:: Translated Entries +* Fuzzy Entries:: Fuzzy Entries +* Untranslated Entries:: Untranslated Entries +* Obsolete Entries:: Obsolete Entries +* Modifying Translations:: Modifying Translations +* Modifying Comments:: Modifying Comments +* Subedit:: Mode for Editing Translations +* C Sources Context:: C Sources Context +* Auxiliary:: Consulting Auxiliary PO Files + + +File: gettext.info, Node: Installation, Next: Main PO Commands, Up: PO Mode + +8.7.1 Completing GNU ‘gettext’ Installation +------------------------------------------- + + Once you have received, unpacked, configured and compiled the GNU +‘gettext’ distribution, the ‘make install’ command puts in place the +programs ‘xgettext’, ‘msgfmt’, ‘gettext’, and ‘msgmerge’, as well as +their available message catalogs. To top off a comfortable +installation, you might also want to make the PO mode available to your +Emacs users. + + During the installation of the PO mode, you might want to modify your +file ‘.emacs’, once and for all, so it contains a few lines looking +like: + + (setq auto-mode-alist + (cons '("\\.po\\'\\|\\.po\\." . po-mode) auto-mode-alist)) + (autoload 'po-mode "po-mode" "Major mode for translators to edit PO files" t) + + Later, whenever you edit some ‘.po’ file, or any file having the +string ‘.po.’ within its name, Emacs loads ‘po-mode.elc’ (or +‘po-mode.el’) as needed, and automatically activates PO mode commands +for the associated buffer. The string _PO_ appears in the mode line for +any buffer for which PO mode is active. Many PO files may be active at +once in a single Emacs session. + + If you are using Emacs version 20 or newer, and have already +installed the appropriate international fonts on your system, you may +also tell Emacs how to determine automatically the coding system of +every PO file. This will often (but not always) cause the necessary +fonts to be loaded and used for displaying the translations on your +Emacs screen. For this to happen, add the lines: + + (modify-coding-system-alist 'file "\\.po\\'\\|\\.po\\." + 'po-find-file-coding-system) + (autoload 'po-find-file-coding-system "po-mode") + +to your ‘.emacs’ file. If, with this, you still see boxes instead of +international characters, try a different font set (via Shift Mouse +button 1). + + +File: gettext.info, Node: Main PO Commands, Next: Entry Positioning, Prev: Installation, Up: PO Mode + +8.7.2 Main PO mode Commands +--------------------------- + + After setting up Emacs with something similar to the lines in *note +Installation::, PO mode is activated for a window when Emacs finds a PO +file in that window. This puts the window read-only and establishes a +po-mode-map, which is a genuine Emacs mode, in a way that is not derived +from text mode in any way. Functions found on ‘po-mode-hook’, if any, +will be executed. + + When PO mode is active in a window, the letters ‘PO’ appear in the +mode line for that window. The mode line also displays how many entries +of each kind are held in the PO file. For example, the string +‘132t+3f+10u+2o’ would tell the translator that the PO mode contains 132 +translated entries (*note Translated Entries::, 3 fuzzy entries (*note +Fuzzy Entries::), 10 untranslated entries (*note Untranslated Entries::) +and 2 obsolete entries (*note Obsolete Entries::). Zero-coefficients +items are not shown. So, in this example, if the fuzzy entries were +unfuzzied, the untranslated entries were translated and the obsolete +entries were deleted, the mode line would merely display ‘145t’ for the +counters. + + The main PO commands are those which do not fit into the other +categories of subsequent sections. These allow for quitting PO mode or +for managing windows in special ways. + +‘_’ + Undo last modification to the PO file (‘po-undo’). + +‘Q’ + Quit processing and save the PO file (‘po-quit’). + +‘q’ + Quit processing, possibly after confirmation + (‘po-confirm-and-quit’). + +‘0’ + Temporary leave the PO file window (‘po-other-window’). + +‘?’ +‘h’ + Show help about PO mode (‘po-help’). + +‘=’ + Give some PO file statistics (‘po-statistics’). + +‘V’ + Batch validate the format of the whole PO file (‘po-validate’). + + The command ‘_’ (‘po-undo’) interfaces to the Emacs _undo_ facility. +*Note Undoing Changes: (emacs)Undo. Each time ‘_’ is typed, +modifications which the translator did to the PO file are undone a +little more. For the purpose of undoing, each PO mode command is +atomic. This is especially true for the ‘’ command: the whole +edition made by using a single use of this command is undone at once, +even if the edition itself implied several actions. However, while in +the editing window, one can undo the edition work quite parsimoniously. + + The commands ‘Q’ (‘po-quit’) and ‘q’ (‘po-confirm-and-quit’) are used +when the translator is done with the PO file. The former is a bit less +verbose than the latter. If the file has been modified, it is saved to +disk first. In both cases, and prior to all this, the commands check if +any untranslated messages remain in the PO file and, if so, the +translator is asked if she really wants to leave off working with this +PO file. This is the preferred way of getting rid of an Emacs PO file +buffer. Merely killing it through the usual command ‘C-x k’ +(‘kill-buffer’) is not the tidiest way to proceed. + + The command ‘0’ (‘po-other-window’) is another, softer way, to leave +PO mode, temporarily. It just moves the cursor to some other Emacs +window, and pops one if necessary. For example, if the translator just +got PO mode to show some source context in some other, she might +discover some apparent bug in the program source that needs correction. +This command allows the translator to change sex, become a programmer, +and have the cursor right into the window containing the program she (or +rather _he_) wants to modify. By later getting the cursor back in the +PO file window, or by asking Emacs to edit this file once again, PO mode +is then recovered. + + The command ‘h’ (‘po-help’) displays a summary of all available PO +mode commands. The translator should then type any character to resume +normal PO mode operations. The command ‘?’ has the same effect as ‘h’. + + The command ‘=’ (‘po-statistics’) computes the total number of +entries in the PO file, the ordinal of the current entry (counted from +1), the number of untranslated entries, the number of obsolete entries, +and displays all these numbers. + + The command ‘V’ (‘po-validate’) launches ‘msgfmt’ in checking and +verbose mode over the current PO file. This command first offers to +save the current PO file on disk. The ‘msgfmt’ tool, from GNU +‘gettext’, has the purpose of creating a MO file out of a PO file, and +PO mode uses the features of this program for checking the overall +format of a PO file, as well as all individual entries. + + The program ‘msgfmt’ runs asynchronously with Emacs, so the +translator regains control immediately while her PO file is being +studied. Error output is collected in the Emacs ‘*compilation*’ buffer, +displayed in another window. The regular Emacs command ‘C-x`’ +(‘next-error’), as well as other usual compile commands, allow the +translator to reposition quickly to the offending parts of the PO file. +Once the cursor is on the line in error, the translator may decide on +any PO mode action which would help correcting the error. + + +File: gettext.info, Node: Entry Positioning, Next: Normalizing, Prev: Main PO Commands, Up: PO Mode + +8.7.3 Entry Positioning +----------------------- + + The cursor in a PO file window is almost always part of an entry. +The only exceptions are the special case when the cursor is after the +last entry in the file, or when the PO file is empty. The entry where +the cursor is found to be is said to be the current entry. Many PO mode +commands operate on the current entry, so moving the cursor does more +than allowing the translator to browse the PO file, this also selects on +which entry commands operate. + + Some PO mode commands alter the position of the cursor in a +specialized way. A few of those special purpose positioning are +described here, the others are described in following sections (for a +complete list try ‘C-h m’): + +‘.’ + Redisplay the current entry (‘po-current-entry’). + +‘n’ + Select the entry after the current one (‘po-next-entry’). + +‘p’ + Select the entry before the current one (‘po-previous-entry’). + +‘<’ + Select the first entry in the PO file (‘po-first-entry’). + +‘>’ + Select the last entry in the PO file (‘po-last-entry’). + +‘m’ + Record the location of the current entry for later use + (‘po-push-location’). + +‘r’ + Return to a previously saved entry location (‘po-pop-location’). + +‘x’ + Exchange the current entry location with the previously saved one + (‘po-exchange-location’). + + Any Emacs command able to reposition the cursor may be used to select +the current entry in PO mode, including commands which move by +characters, lines, paragraphs, screens or pages, and search commands. +However, there is a kind of standard way to display the current entry in +PO mode, which usual Emacs commands moving the cursor do not especially +try to enforce. The command ‘.’ (‘po-current-entry’) has the sole +purpose of redisplaying the current entry properly, after the current +entry has been changed by means external to PO mode, or the Emacs screen +otherwise altered. + + It is yet to be decided if PO mode helps the translator, or otherwise +irritates her, by forcing a rigid window disposition while she is doing +her work. We originally had quite precise ideas about how windows +should behave, but on the other hand, anyone used to Emacs is often +happy to keep full control. Maybe a fixed window disposition might be +offered as a PO mode option that the translator might activate or +deactivate at will, so it could be offered on an experimental basis. If +nobody feels a real need for using it, or a compulsion for writing it, +we should drop this whole idea. The incentive for doing it should come +from translators rather than programmers, as opinions from an +experienced translator are surely more worth to me than opinions from +programmers _thinking_ about how _others_ should do translation. + + The commands ‘n’ (‘po-next-entry’) and ‘p’ (‘po-previous-entry’) move +the cursor the entry following, or preceding, the current one. If ‘n’ +is given while the cursor is on the last entry of the PO file, or if ‘p’ +is given while the cursor is on the first entry, no move is done. + + The commands ‘<’ (‘po-first-entry’) and ‘>’ (‘po-last-entry’) move +the cursor to the first entry, or last entry, of the PO file. When the +cursor is located past the last entry in a PO file, most PO mode +commands will return an error saying ‘After last entry’. Moreover, the +commands ‘<’ and ‘>’ have the special property of being able to work +even when the cursor is not into some PO file entry, and one may use +them for nicely correcting this situation. But even these commands will +fail on a truly empty PO file. There are development plans for the PO +mode for it to interactively fill an empty PO file from sources. *Note +Marking::. + + The translator may decide, before working at the translation of a +particular entry, that she needs to browse the remainder of the PO file, +maybe for finding the terminology or phraseology used in related +entries. She can of course use the standard Emacs idioms for saving the +current cursor location in some register, and use that register for +getting back, or else, use the location ring. + + PO mode offers another approach, by which cursor locations may be +saved onto a special stack. The command ‘m’ (‘po-push-location’) merely +adds the location of current entry to the stack, pushing the already +saved locations under the new one. The command ‘r’ (‘po-pop-location’) +consumes the top stack element and repositions the cursor to the entry +associated with that top element. This position is then lost, for the +next ‘r’ will move the cursor to the previously saved location, and so +on until no locations remain on the stack. + + If the translator wants the position to be kept on the location +stack, maybe for taking a look at the entry associated with the top +element, then go elsewhere with the intent of getting back later, she +ought to use ‘m’ immediately after ‘r’. + + The command ‘x’ (‘po-exchange-location’) simultaneously repositions +the cursor to the entry associated with the top element of the stack of +saved locations, and replaces that top element with the location of the +current entry before the move. Consequently, repeating the ‘x’ command +toggles alternatively between two entries. For achieving this, the +translator will position the cursor on the first entry, use ‘m’, then +position to the second entry, and merely use ‘x’ for making the switch. + + +File: gettext.info, Node: Normalizing, Next: Translated Entries, Prev: Entry Positioning, Up: PO Mode + +8.7.4 Normalizing Strings in Entries +------------------------------------ + + There are many different ways for encoding a particular string into a +PO file entry, because there are so many different ways to split and +quote multi-line strings, and even, to represent special characters by +backslashed escaped sequences. Some features of PO mode rely on the +ability for PO mode to scan an already existing PO file for a particular +string encoded into the ‘msgid’ field of some entry. Even if PO mode +has internally all the built-in machinery for implementing this +recognition easily, doing it fast is technically difficult. To +facilitate a solution to this efficiency problem, we decided on a +canonical representation for strings. + + A conventional representation of strings in a PO file is currently +under discussion, and PO mode experiments with a canonical +representation. Having both ‘xgettext’ and PO mode converging towards a +uniform way of representing equivalent strings would be useful, as the +internal normalization needed by PO mode could be automatically +satisfied when using ‘xgettext’ from GNU ‘gettext’. An explicit PO mode +normalization should then be only necessary for PO files imported from +elsewhere, or for when the convention itself evolves. + + So, for achieving normalization of at least the strings of a given PO +file needing a canonical representation, the following PO mode command +is available: + +‘M-x po-normalize’ + Tidy the whole PO file by making entries more uniform. + + The special command ‘M-x po-normalize’, which has no associated keys, +revises all entries, ensuring that strings of both original and +translated entries use uniform internal quoting in the PO file. It also +removes any crumb after the last entry. This command may be useful for +PO files freshly imported from elsewhere, or if we ever improve on the +canonical quoting format we use. This canonical format is not only +meant for getting cleaner PO files, but also for greatly speeding up +‘msgid’ string lookup for some other PO mode commands. + + ‘M-x po-normalize’ presently makes three passes over the entries. +The first implements heuristics for converting PO files for GNU +‘gettext’ 0.6 and earlier, in which ‘msgid’ and ‘msgstr’ fields were +using K&R style C string syntax for multi-line strings. These +heuristics may fail for comments not related to obsolete entries and +ending with a backslash; they also depend on subsequent passes for +finalizing the proper commenting of continued lines for obsolete +entries. This first pass might disappear once all oldish PO files would +have been adjusted. The second and third pass normalize all ‘msgid’ and +‘msgstr’ strings respectively. They also clean out those trailing +backslashes used by XView's ‘msgfmt’ for continued lines. + + Having such an explicit normalizing command allows for importing PO +files from other sources, but also eases the evolution of the current +convention, evolution driven mostly by aesthetic concerns, as of now. +It is easy to make suggested adjustments at a later time, as the +normalizing command and eventually, other GNU ‘gettext’ tools should +greatly automate conformance. A description of the canonical string +format is given below, for the particular benefit of those not having +Emacs handy, and who would nevertheless want to handcraft their PO files +in nice ways. + + Right now, in PO mode, strings are single line or multi-line. A +string goes multi-line if and only if it has _embedded_ newlines, that +is, if it matches ‘[^\n]\n+[^\n]’. So, we would have: + + msgstr "\n\nHello, world!\n\n\n" + + but, replacing the space by a newline, this becomes: + + msgstr "" + "\n" + "\n" + "Hello,\n" + "world!\n" + "\n" + "\n" + + We are deliberately using a caricatural example, here, to make the +point clearer. Usually, multi-lines are not that bad looking. It is +probable that we will implement the following suggestion. We might lump +together all initial newlines into the empty string, and also all +newlines introducing empty lines (that is, for N > 1, the N-1'th last +newlines would go together on a separate string), so making the previous +example appear: + + msgstr "\n\n" + "Hello,\n" + "world!\n" + "\n\n" + + There are a few yet undecided little points about string +normalization, to be documented in this manual, once these questions +settle. + + +File: gettext.info, Node: Translated Entries, Next: Fuzzy Entries, Prev: Normalizing, Up: PO Mode + +8.7.5 Translated Entries +------------------------ + + Each PO file entry for which the ‘msgstr’ field has been filled with +a translation, and which is not marked as fuzzy (*note Fuzzy Entries::), +is said to be a “translated” entry. Only translated entries will later +be compiled by GNU ‘msgfmt’ and become usable in programs. Other entry +types will be excluded; translation will not occur for them. + + Some commands are more specifically related to translated entry +processing. + +‘t’ + Find the next translated entry (‘po-next-translated-entry’). + +‘T’ + Find the previous translated entry + (‘po-previous-translated-entry’). + + The commands ‘t’ (‘po-next-translated-entry’) and ‘T’ +(‘po-previous-translated-entry’) move forwards or backwards, chasing for +an translated entry. If none is found, the search is extended and wraps +around in the PO file buffer. + + Translated entries usually result from the translator having edited +in a translation for them, *note Modifying Translations::. However, if +the variable ‘po-auto-fuzzy-on-edit’ is not ‘nil’, the entry having +received a new translation first becomes a fuzzy entry, which ought to +be later unfuzzied before becoming an official, genuine translated +entry. *Note Fuzzy Entries::. + + +File: gettext.info, Node: Fuzzy Entries, Next: Untranslated Entries, Prev: Translated Entries, Up: PO Mode + +8.7.6 Fuzzy Entries +------------------- + + Each PO file entry may have a set of “attributes”, which are +qualities given a name and explicitly associated with the translation, +using a special system comment. One of these attributes has the name +‘fuzzy’, and entries having this attribute are said to have a fuzzy +translation. They are called fuzzy entries, for short. + + Fuzzy entries, even if they account for translated entries for most +other purposes, usually call for revision by the translator. Those may +be produced by applying the program ‘msgmerge’ to update an older +translated PO files according to a new PO template file, when this tool +hypothesises that some new ‘msgid’ has been modified only slightly out +of an older one, and chooses to pair what it thinks to be the old +translation for the new modified entry. The slight alteration in the +original string (the ‘msgid’ string) should often be reflected in the +translated string, and this requires the intervention of the translator. +For this reason, ‘msgmerge’ might mark some entries as being fuzzy. + + Also, the translator may decide herself to mark an entry as fuzzy for +her own convenience, when she wants to remember that the entry has to be +later revisited. So, some commands are more specifically related to +fuzzy entry processing. + +‘f’ + Find the next fuzzy entry (‘po-next-fuzzy-entry’). + +‘F’ + Find the previous fuzzy entry (‘po-previous-fuzzy-entry’). + +‘’ + Remove the fuzzy attribute of the current entry (‘po-unfuzzy’). + + The commands ‘f’ (‘po-next-fuzzy-entry’) and ‘F’ +(‘po-previous-fuzzy-entry’) move forwards or backwards, chasing for a +fuzzy entry. If none is found, the search is extended and wraps around +in the PO file buffer. + + The command ‘’ (‘po-unfuzzy’) removes the fuzzy attribute +associated with an entry, usually leaving it translated. Further, if +the variable ‘po-auto-select-on-unfuzzy’ has not the ‘nil’ value, the +‘’ command will automatically chase for another interesting entry +to work on. The initial value of ‘po-auto-select-on-unfuzzy’ is ‘nil’. + + The initial value of ‘po-auto-fuzzy-on-edit’ is ‘nil’. However, if +the variable ‘po-auto-fuzzy-on-edit’ is set to ‘t’, any entry edited +through the ‘’ command is marked fuzzy, as a way to ensure some +kind of double check, later. In this case, the usual paradigm is that +an entry becomes fuzzy (if not already) whenever the translator modifies +it. If she is satisfied with the translation, she then uses ‘’ to +pick another entry to work on, clearing the fuzzy attribute on the same +blow. If she is not satisfied yet, she merely uses ‘’ to chase +another entry, leaving the entry fuzzy. + + The translator may also use the ‘’ command (‘po-fade-out-entry’) +over any translated entry to mark it as being fuzzy, when she wants to +easily leave a trace she wants to later return working at this entry. + + Also, when time comes to quit working on a PO file buffer with the +‘q’ command, the translator is asked for confirmation, if fuzzy string +still exists. + + +File: gettext.info, Node: Untranslated Entries, Next: Obsolete Entries, Prev: Fuzzy Entries, Up: PO Mode + +8.7.7 Untranslated Entries +-------------------------- + + When ‘xgettext’ originally creates a PO file, unless told otherwise, +it initializes the ‘msgid’ field with the untranslated string, and +leaves the ‘msgstr’ string to be empty. Such entries, having an empty +translation, are said to be “untranslated” entries. Later, when the +programmer slightly modifies some string right in the program, this +change is later reflected in the PO file by the appearance of a new +untranslated entry for the modified string. + + The usual commands moving from entry to entry consider untranslated +entries on the same level as active entries. Untranslated entries are +easily recognizable by the fact they end with ‘msgstr ""’. + + The work of the translator might be (quite naively) seen as the +process of seeking for an untranslated entry, editing a translation for +it, and repeating these actions until no untranslated entries remain. +Some commands are more specifically related to untranslated entry +processing. + +‘u’ + Find the next untranslated entry (‘po-next-untranslated-entry’). + +‘U’ + Find the previous untranslated entry + (‘po-previous-untransted-entry’). + +‘k’ + Turn the current entry into an untranslated one (‘po-kill-msgstr’). + + The commands ‘u’ (‘po-next-untranslated-entry’) and ‘U’ +(‘po-previous-untransted-entry’) move forwards or backwards, chasing for +an untranslated entry. If none is found, the search is extended and +wraps around in the PO file buffer. + + An entry can be turned back into an untranslated entry by merely +emptying its translation, using the command ‘k’ (‘po-kill-msgstr’). +*Note Modifying Translations::. + + Also, when time comes to quit working on a PO file buffer with the +‘q’ command, the translator is asked for confirmation, if some +untranslated string still exists. + + +File: gettext.info, Node: Obsolete Entries, Next: Modifying Translations, Prev: Untranslated Entries, Up: PO Mode + +8.7.8 Obsolete Entries +---------------------- + + By “obsolete” PO file entries, we mean those entries which are +commented out, usually by ‘msgmerge’ when it found that the translation +is not needed anymore by the package being localized. + + The usual commands moving from entry to entry consider obsolete +entries on the same level as active entries. Obsolete entries are +easily recognizable by the fact that all their lines start with ‘#’, +even those lines containing ‘msgid’ or ‘msgstr’. + + Commands exist for emptying the translation or reinitializing it to +the original untranslated string. Commands interfacing with the kill +ring may force some previously saved text into the translation. The +user may interactively edit the translation. All these commands may +apply to obsolete entries, carefully leaving the entry obsolete after +the fact. + + Moreover, some commands are more specifically related to obsolete +entry processing. + +‘o’ + Find the next obsolete entry (‘po-next-obsolete-entry’). + +‘O’ + Find the previous obsolete entry (‘po-previous-obsolete-entry’). + +‘’ + Make an active entry obsolete, or zap out an obsolete entry + (‘po-fade-out-entry’). + + The commands ‘o’ (‘po-next-obsolete-entry’) and ‘O’ +(‘po-previous-obsolete-entry’) move forwards or backwards, chasing for +an obsolete entry. If none is found, the search is extended and wraps +around in the PO file buffer. + + PO mode does not provide ways for un-commenting an obsolete entry and +making it active, because this would reintroduce an original +untranslated string which does not correspond to any marked string in +the program sources. This goes with the philosophy of never introducing +useless ‘msgid’ values. + + However, it is possible to comment out an active entry, so making it +obsolete. GNU ‘gettext’ utilities will later react to the disappearance +of a translation by using the untranslated string. The command ‘’ +(‘po-fade-out-entry’) pushes the current entry a little further towards +annihilation. If the entry is active (it is a translated entry), then +it is first made fuzzy. If it is already fuzzy, then the entry is +merely commented out, with confirmation. If the entry is already +obsolete, then it is completely deleted from the PO file. It is easy to +recycle the translation so deleted into some other PO file entry, +usually one which is untranslated. *Note Modifying Translations::. + + Here is a quite interesting problem to solve for later development of +PO mode, for those nights you are not sleepy. The idea would be that PO +mode might become bright enough, one of these days, to make good guesses +at retrieving the most probable candidate, among all obsolete entries, +for initializing the translation of a newly appeared string. I think it +might be a quite hard problem to do this algorithmically, as we have to +develop good and efficient measures of string similarity. Right now, PO +mode completely lets the decision to the translator, when the time comes +to find the adequate obsolete translation, it merely tries to provide +handy tools for helping her to do so. + + +File: gettext.info, Node: Modifying Translations, Next: Modifying Comments, Prev: Obsolete Entries, Up: PO Mode + +8.7.9 Modifying Translations +---------------------------- + + PO mode prevents direct modification of the PO file, by the usual +means Emacs gives for altering a buffer's contents. By doing so, it +pretends helping the translator to avoid little clerical errors about +the overall file format, or the proper quoting of strings, as those +errors would be easily made. Other kinds of errors are still possible, +but some may be caught and diagnosed by the batch validation process, +which the translator may always trigger by the ‘V’ command. For all +other errors, the translator has to rely on her own judgment, and also +on the linguistic reports submitted to her by the users of the +translated package, having the same mother tongue. + + When the time comes to create a translation, correct an error +diagnosed mechanically or reported by a user, the translators have to +resort to using the following commands for modifying the translations. + +‘’ + Interactively edit the translation (‘po-edit-msgstr’). + +‘’ +‘C-j’ + Reinitialize the translation with the original, untranslated string + (‘po-msgid-to-msgstr’). + +‘k’ + Save the translation on the kill ring, and delete it + (‘po-kill-msgstr’). + +‘w’ + Save the translation on the kill ring, without deleting it + (‘po-kill-ring-save-msgstr’). + +‘y’ + Replace the translation, taking the new from the kill ring + (‘po-yank-msgstr’). + + The command ‘’ (‘po-edit-msgstr’) opens a new Emacs window meant +to edit in a new translation, or to modify an already existing +translation. The new window contains a copy of the translation taken +from the current PO file entry, all ready for edition, expunged of all +quoting marks, fully modifiable and with the complete extent of Emacs +modifying commands. When the translator is done with her modifications, +she may use ‘C-c C-c’ to close the subedit window with the automatically +requoted results, or ‘C-c C-k’ to abort her modifications. *Note +Subedit::, for more information. + + The command ‘’ (‘po-msgid-to-msgstr’) initializes, or +reinitializes the translation with the original string. This command is +normally used when the translator wants to redo a fresh translation of +the original string, disregarding any previous work. + + It is possible to arrange so, whenever editing an untranslated entry, +the ‘’ command be automatically executed. If you set +‘po-auto-edit-with-msgid’ to ‘t’, the translation gets initialised with +the original string, in case none exists already. The default value for +‘po-auto-edit-with-msgid’ is ‘nil’. + + In fact, whether it is best to start a translation with an empty +string, or rather with a copy of the original string, is a matter of +taste or habit. Sometimes, the source language and the target language +are so different that is simply best to start writing on an empty page. +At other times, the source and target languages are so close that it +would be a waste to retype a number of words already being written in +the original string. A translator may also like having the original +string right under her eyes, as she will progressively overwrite the +original text with the translation, even if this requires some extra +editing work to get rid of the original. + + The command ‘k’ (‘po-kill-msgstr’) merely empties the translation +string, so turning the entry into an untranslated one. But while doing +so, its previous contents is put apart in a special place, known as the +kill ring. The command ‘w’ (‘po-kill-ring-save-msgstr’) has also the +effect of taking a copy of the translation onto the kill ring, but it +otherwise leaves the entry alone, and does _not_ remove the translation +from the entry. Both commands use exactly the Emacs kill ring, which is +shared between buffers, and which is well known already to Emacs lovers. + + The translator may use ‘k’ or ‘w’ many times in the course of her +work, as the kill ring may hold several saved translations. From the +kill ring, strings may later be reinserted in various Emacs buffers. In +particular, the kill ring may be used for moving translation strings +between different entries of a single PO file buffer, or if the +translator is handling many such buffers at once, even between PO files. + + To facilitate exchanges with buffers which are not in PO mode, the +translation string put on the kill ring by the ‘k’ command is fully +unquoted before being saved: external quotes are removed, multi-line +strings are concatenated, and backslash escaped sequences are turned +into their corresponding characters. In the special case of obsolete +entries, the translation is also uncommented prior to saving. + + The command ‘y’ (‘po-yank-msgstr’) completely replaces the +translation of the current entry by a string taken from the kill ring. +Following Emacs terminology, we then say that the replacement string is +“yanked” into the PO file buffer. *Note (emacs)Yanking::. The first +time ‘y’ is used, the translation receives the value of the most recent +addition to the kill ring. If ‘y’ is typed once again, immediately, +without intervening keystrokes, the translation just inserted is taken +away and replaced by the second most recent addition to the kill ring. +By repeating ‘y’ many times in a row, the translator may travel along +the kill ring for saved strings, until she finds the string she really +wanted. + + When a string is yanked into a PO file entry, it is fully and +automatically requoted for complying with the format PO files should +have. Further, if the entry is obsolete, PO mode then appropriately +push the inserted string inside comments. Once again, translators +should not burden themselves with quoting considerations besides, of +course, the necessity of the translated string itself respective to the +program using it. + + Note that ‘k’ or ‘w’ are not the only commands pushing strings on the +kill ring, as almost any PO mode command replacing translation strings +(or the translator comments) automatically saves the old string on the +kill ring. The main exceptions to this general rule are the yanking +commands themselves. + + To better illustrate the operation of killing and yanking, let's use +an actual example, taken from a common situation. When the programmer +slightly modifies some string right in the program, his change is later +reflected in the PO file by the appearance of a new untranslated entry +for the modified string, and the fact that the entry translating the +original or unmodified string becomes obsolete. In many cases, the +translator might spare herself some work by retrieving the unmodified +translation from the obsolete entry, then initializing the untranslated +entry ‘msgstr’ field with this retrieved translation. Once this done, +the obsolete entry is not wanted anymore, and may be safely deleted. + + When the translator finds an untranslated entry and suspects that a +slight variant of the translation exists, she immediately uses ‘m’ to +mark the current entry location, then starts chasing obsolete entries +with ‘o’, hoping to find some translation corresponding to the +unmodified string. Once found, she uses the ‘’ command for +deleting the obsolete entry, knowing that ‘’ also _kills_ the +translation, that is, pushes the translation on the kill ring. Then, +‘r’ returns to the initial untranslated entry, and ‘y’ then _yanks_ the +saved translation right into the ‘msgstr’ field. The translator is then +free to use ‘’ for fine tuning the translation contents, and maybe +to later use ‘u’, then ‘m’ again, for going on with the next +untranslated string. + + When some sequence of keys has to be typed over and over again, the +translator may find it useful to become better acquainted with the Emacs +capability of learning these sequences and playing them back under +request. *Note (emacs)Keyboard Macros::. + + +File: gettext.info, Node: Modifying Comments, Next: Subedit, Prev: Modifying Translations, Up: PO Mode + +8.7.10 Modifying Comments +------------------------- + + Any translation work done seriously will raise many linguistic +difficulties, for which decisions have to be made, and the choices +further documented. These documents may be saved within the PO file in +form of translator comments, which the translator is free to create, +delete, or modify at will. These comments may be useful to herself when +she returns to this PO file after a while. + + Comments not having whitespace after the initial ‘#’, for example, +those beginning with ‘#.’ or ‘#:’, are _not_ translator comments, they +are exclusively created by other ‘gettext’ tools. So, the commands +below will never alter such system added comments, they are not meant +for the translator to modify. *Note PO Files::. + + The following commands are somewhat similar to those modifying +translations, so the general indications given for those apply here. +*Note Modifying Translations::. + +‘#’ + Interactively edit the translator comments (‘po-edit-comment’). + +‘K’ + Save the translator comments on the kill ring, and delete it + (‘po-kill-comment’). + +‘W’ + Save the translator comments on the kill ring, without deleting it + (‘po-kill-ring-save-comment’). + +‘Y’ + Replace the translator comments, taking the new from the kill ring + (‘po-yank-comment’). + + These commands parallel PO mode commands for modifying the +translation strings, and behave much the same way as they do, except +that they handle this part of PO file comments meant for translator +usage, rather than the translation strings. So, if the descriptions +given below are slightly succinct, it is because the full details have +already been given. *Note Modifying Translations::. + + The command ‘#’ (‘po-edit-comment’) opens a new Emacs window +containing a copy of the translator comments on the current PO file +entry. If there are no such comments, PO mode understands that the +translator wants to add a comment to the entry, and she is presented +with an empty screen. Comment marks (‘#’) and the space following them +are automatically removed before edition, and reinstated after. For +translator comments pertaining to obsolete entries, the uncommenting and +recommenting operations are done twice. Once in the editing window, the +keys ‘C-c C-c’ allow the translator to tell she is finished with editing +the comment. *Note Subedit::, for further details. + + Functions found on ‘po-subedit-mode-hook’, if any, are executed after +the string has been inserted in the edit buffer. + + The command ‘K’ (‘po-kill-comment’) gets rid of all translator +comments, while saving those comments on the kill ring. The command ‘W’ +(‘po-kill-ring-save-comment’) takes a copy of the translator comments on +the kill ring, but leaves them undisturbed in the current entry. The +command ‘Y’ (‘po-yank-comment’) completely replaces the translator +comments by a string taken at the front of the kill ring. When this +command is immediately repeated, the comments just inserted are +withdrawn, and replaced by other strings taken along the kill ring. + + On the kill ring, all strings have the same nature. There is no +distinction between _translation_ strings and _translator comments_ +strings. So, for example, let's presume the translator has just +finished editing a translation, and wants to create a new translator +comment to document why the previous translation was not good, just to +remember what was the problem. Foreseeing that she will do that in her +documentation, the translator may want to quote the previous translation +in her translator comments. To do so, she may initialize the translator +comments with the previous translation, still at the head of the kill +ring. Because editing already pushed the previous translation on the +kill ring, she merely has to type ‘M-w’ prior to ‘#’, and the previous +translation will be right there, all ready for being introduced by some +explanatory text. + + On the other hand, presume there are some translator comments already +and that the translator wants to add to those comments, instead of +wholly replacing them. Then, she should edit the comment right away +with ‘#’. Once inside the editing window, she can use the regular Emacs +commands ‘C-y’ (‘yank’) and ‘M-y’ (‘yank-pop’) to get the previous +translation where she likes. + + +File: gettext.info, Node: Subedit, Next: C Sources Context, Prev: Modifying Comments, Up: PO Mode + +8.7.11 Details of Sub Edition +----------------------------- + + The PO subedit minor mode has a few peculiarities worth being +described in fuller detail. It installs a few commands over the usual +editing set of Emacs, which are described below. + +‘C-c C-c’ + Complete edition (‘po-subedit-exit’). + +‘C-c C-k’ + Abort edition (‘po-subedit-abort’). + +‘C-c C-a’ + Consult auxiliary PO files (‘po-subedit-cycle-auxiliary’). + + The window's contents represents a translation for a given message, +or a translator comment. The translator may modify this window to her +heart's content. Once this is done, the command ‘C-c C-c’ +(‘po-subedit-exit’) may be used to return the edited translation into +the PO file, replacing the original translation, even if it moved out of +sight or if buffers were switched. + + If the translator becomes unsatisfied with her translation or +comment, to the extent she prefers keeping what was existent prior to +the ‘’ or ‘#’ command, she may use the command ‘C-c C-k’ +(‘po-subedit-abort’) to merely get rid of edition, while preserving the +original translation or comment. Another way would be for her to exit +normally with ‘C-c C-c’, then type ‘U’ once for undoing the whole effect +of last edition. + + The command ‘C-c C-a’ (‘po-subedit-cycle-auxiliary’) allows for +glancing through translations already achieved in other languages, +directly while editing the current translation. This may be quite +convenient when the translator is fluent at many languages, but of +course, only makes sense when such completed auxiliary PO files are +already available to her (*note Auxiliary::). + + Functions found on ‘po-subedit-mode-hook’, if any, are executed after +the string has been inserted in the edit buffer. + + While editing her translation, the translator should pay attention to +not inserting unwanted ‘’ (newline) characters at the end of the +translated string if those are not meant to be there, or to removing +such characters when they are required. Since these characters are not +visible in the editing buffer, they are easily introduced by mistake. +To help her, ‘’ automatically puts the character ‘<’ at the end of +the string being edited, but this ‘<’ is not really part of the string. +On exiting the editing window with ‘C-c C-c’, PO mode automatically +removes such ‘<’ and all whitespace added after it. If the translator +adds characters after the terminating ‘<’, it looses its delimiting +property and integrally becomes part of the string. If she removes the +delimiting ‘<’, then the edited string is taken _as is_, with all +trailing newlines, even if invisible. Also, if the translated string +ought to end itself with a genuine ‘<’, then the delimiting ‘<’ may not +be removed; so the string should appear, in the editing window, as +ending with two ‘<’ in a row. + + When a translation (or a comment) is being edited, the translator may +move the cursor back into the PO file buffer and freely move to other +entries, browsing at will. If, with an edition pending, the translator +wanders in the PO file buffer, she may decide to start modifying another +entry. Each entry being edited has its own subedit buffer. It is +possible to simultaneously edit the translation _and_ the comment of a +single entry, or to edit entries in different PO files, all at once. +Typing ‘’ on a field already being edited merely resumes that +particular edit. Yet, the translator should better be comfortable at +handling many Emacs windows! + + Pending subedits may be completed or aborted in any order, regardless +of how or when they were started. When many subedits are pending and +the translator asks for quitting the PO file (with the ‘q’ command), +subedits are automatically resumed one at a time, so she may decide for +each of them. + + +File: gettext.info, Node: C Sources Context, Next: Auxiliary, Prev: Subedit, Up: PO Mode + +8.7.12 C Sources Context +------------------------ + + PO mode is particularly powerful when used with PO files created +through GNU ‘gettext’ utilities, as those utilities insert special +comments in the PO files they generate. Some of these special comments +relate the PO file entry to exactly where the untranslated string +appears in the program sources. + + When the translator gets to an untranslated entry, she is fairly +often faced with an original string which is not as informative as it +normally should be, being succinct, cryptic, or otherwise ambiguous. +Before choosing how to translate the string, she needs to understand +better what the string really means and how tight the translation has to +be. Most of the time, when problems arise, the only way left to make +her judgment is looking at the true program sources from where this +string originated, searching for surrounding comments the programmer +might have put in there, and looking around for helping clues of _any_ +kind. + + Surely, when looking at program sources, the translator will receive +more help if she is a fluent programmer. However, even if she is not +versed in programming and feels a little lost in C code, the translator +should not be shy at taking a look, once in a while. It is most +probable that she will still be able to find some of the hints she +needs. She will learn quickly to not feel uncomfortable in program +code, paying more attention to programmer's comments, variable and +function names (if he dared choosing them well), and overall +organization, than to the program code itself. + + The following commands are meant to help the translator at getting +program source context for a PO file entry. + +‘s’ + Resume the display of a program source context, or cycle through + them (‘po-cycle-source-reference’). + +‘M-s’ + Display of a program source context selected by menu + (‘po-select-source-reference’). + +‘S’ + Add a directory to the search path for source files + (‘po-consider-source-path’). + +‘M-S’ + Delete a directory from the search path for source files + (‘po-ignore-source-path’). + + The commands ‘s’ (‘po-cycle-source-reference’) and ‘M-s’ +(‘po-select-source-reference’) both open another window displaying some +source program file, and already positioned in such a way that it shows +an actual use of the string to be translated. By doing so, the command +gives source program context for the string. But if the entry has no +source context references, or if all references are unresolved along the +search path for program sources, then the command diagnoses this as an +error. + + Even if ‘s’ (or ‘M-s’) opens a new window, the cursor stays in the PO +file window. If the translator really wants to get into the program +source window, she ought to do it explicitly, maybe by using command +‘O’. + + When ‘s’ is typed for the first time, or for a PO file entry which is +different of the last one used for getting source context, then the +command reacts by giving the first context available for this entry, if +any. If some context has already been recently displayed for the +current PO file entry, and the translator wandered off to do other +things, typing ‘s’ again will merely resume, in another window, the +context last displayed. In particular, if the translator moved the +cursor away from the context in the source file, the command will bring +the cursor back to the context. By using ‘s’ many times in a row, with +no other commands intervening, PO mode will cycle to the next available +contexts for this particular entry, getting back to the first context +once the last has been shown. + + The command ‘M-s’ behaves differently. Instead of cycling through +references, it lets the translator choose a particular reference among +many, and displays that reference. It is best used with completion, if +the translator types ‘’ immediately after ‘M-s’, in response to the +question, she will be offered a menu of all possible references, as a +reminder of which are the acceptable answers. This command is useful +only where there are really many contexts available for a single string +to translate. + + Program source files are usually found relative to where the PO file +stands. As a special provision, when this fails, the file is also +looked for, but relative to the directory immediately above it. Those +two cases take proper care of most PO files. However, it might happen +that a PO file has been moved, or is edited in a different place than +its normal location. When this happens, the translator should tell PO +mode in which directory normally sits the genuine PO file. Many such +directories may be specified, and all together, they constitute what is +called the “search path” for program sources. The command ‘S’ +(‘po-consider-source-path’) is used to interactively enter a new +directory at the front of the search path, and the command ‘M-S’ +(‘po-ignore-source-path’) is used to select, with completion, one of the +directories she does not want anymore on the search path. + + +File: gettext.info, Node: Auxiliary, Prev: C Sources Context, Up: PO Mode + +8.7.13 Consulting Auxiliary PO Files +------------------------------------ + + PO mode is able to help the knowledgeable translator, being fluent in +many languages, at taking advantage of translations already achieved in +other languages she just happens to know. It provides these other +language translations as additional context for her own work. Moreover, +it has features to ease the production of translations for many +languages at once, for translators preferring to work in this way. + + An “auxiliary” PO file is an existing PO file meant for the same +package the translator is working on, but targeted to a different mother +tongue language. Commands exist for declaring and handling auxiliary PO +files, and also for showing contexts for the entry under work. + + Here are the auxiliary file commands available in PO mode. + +‘a’ + Seek auxiliary files for another translation for the same entry + (‘po-cycle-auxiliary’). + +‘C-c C-a’ + Switch to a particular auxiliary file (‘po-select-auxiliary’). + +‘A’ + Declare this PO file as an auxiliary file + (‘po-consider-as-auxiliary’). + +‘M-A’ + Remove this PO file from the list of auxiliary files + (‘po-ignore-as-auxiliary’). + + Command ‘A’ (‘po-consider-as-auxiliary’) adds the current PO file to +the list of auxiliary files, while command ‘M-A’ +(‘po-ignore-as-auxiliary’ just removes it. + + The command ‘a’ (‘po-cycle-auxiliary’) seeks all auxiliary PO files, +round-robin, searching for a translated entry in some other language +having an ‘msgid’ field identical as the one for the current entry. The +found PO file, if any, takes the place of the current PO file in the +display (its window gets on top). Before doing so, the current PO file +is also made into an auxiliary file, if not already. So, ‘a’ in this +newly displayed PO file will seek another PO file, and so on, so +repeating ‘a’ will eventually yield back the original PO file. + + The command ‘C-c C-a’ (‘po-select-auxiliary’) asks the translator for +her choice of a particular auxiliary file, with completion, and then +switches to that selected PO file. The command also checks if the +selected file has an ‘msgid’ field identical as the one for the current +entry, and if yes, this entry becomes current. Otherwise, the cursor of +the selected file is left undisturbed. + + For all this to work fully, auxiliary PO files will have to be +normalized, in that way that ‘msgid’ fields should be written _exactly_ +the same way. It is possible to write ‘msgid’ fields in various ways +for representing the same string, different writing would break the +proper behaviour of the auxiliary file commands of PO mode. This is not +expected to be much a problem in practice, as most existing PO files +have their ‘msgid’ entries written by the same GNU ‘gettext’ tools. + + However, PO files initially created by PO mode itself, while marking +strings in source files, are normalised differently. So are PO files +resulting of the ‘M-x normalize’ command. Until these discrepancies +between PO mode and other GNU ‘gettext’ tools get fully resolved, the +translator should stay aware of normalisation issues. + + +File: gettext.info, Node: Vim, Next: Compendium, Prev: PO Mode, Up: Editing + +8.8 Editing PO Files in vim +=========================== + + FIXME: Try these scripts. Do they work well? How do they compare? + + There are two ‘vim’ plugins for editing PO files in ‘vim’: + + • The one by Aleksandar Jelenak (2005), at + . + + • A fork of it (2009), at + . + + Additionally, if you only need syntax highlighting, not editing, of +PO files, there is a ‘vim’ script for that at +. + + +File: gettext.info, Node: Compendium, Prev: Vim, Up: Editing + +8.9 Using Translation Compendia +=============================== + + A “compendium” is a special PO file containing a set of translations +recurring in many different packages. The translator can use gettext +tools to build a new compendium, to add entries to her compendium, and +to initialize untranslated entries, or to update already translated +entries, from translations kept in the compendium. + +* Menu: + +* Creating Compendia:: Merging translations for later use +* Using Compendia:: Using older translations if they fit + + +File: gettext.info, Node: Creating Compendia, Next: Using Compendia, Up: Compendium + +8.9.1 Creating Compendia +------------------------ + + Basically every PO file consisting of translated entries only can be +declared as a valid compendium. Often the translator wants to have +special compendia; let's consider two cases: ‘concatenating PO files’ +and ‘extracting a message subset from a PO file’. + +8.9.1.1 Concatenate PO Files +............................ + + To concatenate several valid PO files into one compendium file you +can use ‘msgcomm’ or ‘msgcat’ (the latter preferred): + + msgcat -o compendium.po file1.po file2.po + + By default, ‘msgcat’ will accumulate divergent translations for the +same string. Those occurrences will be marked as ‘fuzzy’ and highly +visible decorated; calling ‘msgcat’ on ‘file1.po’: + + #: src/hello.c:200 + #, c-format + msgid "Report bugs to <%s>.\n" + msgstr "Comunicar `bugs' a <%s>.\n" + +and ‘file2.po’: + + #: src/bye.c:100 + #, c-format + msgid "Report bugs to <%s>.\n" + msgstr "Comunicar \"bugs\" a <%s>.\n" + +will result in: + + #: src/hello.c:200 src/bye.c:100 + #, fuzzy, c-format + msgid "Report bugs to <%s>.\n" + msgstr "" + "#-#-#-#-# file1.po #-#-#-#-#\n" + "Comunicar `bugs' a <%s>.\n" + "#-#-#-#-# file2.po #-#-#-#-#\n" + "Comunicar \"bugs\" a <%s>.\n" + +The translator will have to resolve this "conflict" manually; she has to +decide whether the first or the second version is appropriate (or +provide a new translation), to delete the "marker lines", and finally to +remove the ‘fuzzy’ mark. + + If the translator knows in advance the first found translation of a +message is always the best translation she can make use to the +‘--use-first’ switch: + + msgcat --use-first -o compendium.po file1.po file2.po + + A good compendium file must not contain ‘fuzzy’ or untranslated +entries. If input files are "dirty" you must preprocess the input files +or postprocess the result using ‘msgattrib --translated --no-fuzzy’. + +8.9.1.2 Extract a Message Subset from a PO File +............................................... + + Nobody wants to translate the same messages again and again; thus you +may wish to have a compendium file containing ‘getopt.c’ messages. + + To extract a message subset (e.g., all ‘getopt.c’ messages) from an +existing PO file into one compendium file you can use ‘msggrep’: + + msggrep --location src/getopt.c -o compendium.po file.po + + +File: gettext.info, Node: Using Compendia, Prev: Creating Compendia, Up: Compendium + +8.9.2 Using Compendia +--------------------- + + You can use a compendium file to initialize a translation from +scratch or to update an already existing translation. + +8.9.2.1 Initialize a New Translation File +......................................... + + Since a PO file with translations does not exist the translator can +merely use ‘/dev/null’ to fake the "old" translation file. + + msgmerge --compendium compendium.po -o file.po /dev/null file.pot + +8.9.2.2 Update an Existing Translation File +........................................... + + Concatenate the compendium file(s) and the existing PO, merge the +result with the POT file and remove the obsolete entries (optional, here +done using ‘msgattrib’): + + msgcat --use-first -o update.po compendium1.po compendium2.po file.po + msgmerge update.po file.pot | msgattrib --no-obsolete > file.po + + +File: gettext.info, Node: Manipulating, Next: Binaries, Prev: Editing, Up: Top + +9 Manipulating PO Files +*********************** + + Sometimes it is necessary to manipulate PO files in a way that is +better performed automatically than by hand. GNU ‘gettext’ includes a +complete set of tools for this purpose. + + When merging two packages into a single package, the resulting POT +file will be the concatenation of the two packages' POT files. Thus the +maintainer must concatenate the two existing package translations into a +single translation catalog, for each language. This is best performed +using ‘msgcat’. It is then the translators' duty to deal with any +possible conflicts that arose during the merge. + + When a translator takes over the translation job from another +translator, but she uses a different character encoding in her locale, +she will convert the catalog to her character encoding. This is best +done through the ‘msgconv’ program. + + When a maintainer takes a source file with tagged messages from +another package, he should also take the existing translations for this +source file (and not let the translators do the same job twice). One +way to do this is through ‘msggrep’, another is to create a POT file for +that source file and use ‘msgmerge’. + + When a translator wants to adjust some translation catalog for a +special dialect or orthography -- for example, German as written in +Switzerland versus German as written in Germany -- she needs to apply +some text processing to every message in the catalog. The tool for +doing this is ‘msgfilter’. + + Another use of ‘msgfilter’ is to produce approximately the POT file +for which a given PO file was made. This can be done through a filter +command like ‘msgfilter sed -e d | sed -e '/^# /d'’. Note that the +original POT file may have had different comments and different plural +message counts, that's why it's better to use the original POT file if +available. + + When a translator wants to check her translations, for example +according to orthography rules or using a non-interactive spell checker, +she can do so using the ‘msgexec’ program. + + When third party tools create PO or POT files, sometimes duplicates +cannot be avoided. But the GNU ‘gettext’ tools give an error when they +encounter duplicate msgids in the same file and in the same domain. To +merge duplicates, the ‘msguniq’ program can be used. + + ‘msgcomm’ is a more general tool for keeping or throwing away +duplicates, occurring in different files. + + ‘msgcmp’ can be used to check whether a translation catalog is +completely translated. + + ‘msgattrib’ can be used to select and extract only the fuzzy or +untranslated messages of a translation catalog. + + ‘msgen’ is useful as a first step for preparing English translation +catalogs. It copies each message's msgid to its msgstr. + + Finally, for those applications where all these various programs are +not sufficient, a library ‘libgettextpo’ is provided that can be used to +write other specialized programs that process PO files. + +* Menu: + +* msgcat Invocation:: Invoking the ‘msgcat’ Program +* msgconv Invocation:: Invoking the ‘msgconv’ Program +* msggrep Invocation:: Invoking the ‘msggrep’ Program +* msgfilter Invocation:: Invoking the ‘msgfilter’ Program +* msguniq Invocation:: Invoking the ‘msguniq’ Program +* msgcomm Invocation:: Invoking the ‘msgcomm’ Program +* msgcmp Invocation:: Invoking the ‘msgcmp’ Program +* msgattrib Invocation:: Invoking the ‘msgattrib’ Program +* msgen Invocation:: Invoking the ‘msgen’ Program +* msgexec Invocation:: Invoking the ‘msgexec’ Program +* Colorizing:: Highlighting parts of PO files +* Other tools:: Other tools for manipulating PO files +* libgettextpo:: Writing your own programs that process PO files + + +File: gettext.info, Node: msgcat Invocation, Next: msgconv Invocation, Up: Manipulating + +9.1 Invoking the ‘msgcat’ Program +================================= + + msgcat [OPTION] [INPUTFILE]... + + The ‘msgcat’ program concatenates and merges the specified PO files. +It finds messages which are common to two or more of the specified PO +files. By using the ‘--more-than’ option, greater commonality may be +requested before messages are printed. Conversely, the ‘--less-than’ +option may be used to specify less commonality before messages are +printed (i.e. ‘--less-than=2’ will only print the unique messages). +Translations, comments, extracted comments, and file positions will be +cumulated, except that if ‘--use-first’ is specified, they will be taken +from the first PO file to define them. + + To concatenate POT files, better use ‘xgettext’, not ‘msgcat’, +because ‘msgcat’ would choke on the undefined charsets in the specified +POT files. + +9.1.1 Input file location +------------------------- + +‘INPUTFILE ...’ + Input files. + +‘-f FILE’ +‘--files-from=FILE’ + Read the names of the input files from FILE instead of getting them + from the command line. + +‘-D DIRECTORY’ +‘--directory=DIRECTORY’ + Add DIRECTORY to the list of directories. Source files are + searched relative to this list of directories. The resulting ‘.po’ + file will be written relative to the current directory, though. + + If INPUTFILE is ‘-’, standard input is read. + +9.1.2 Output file location +-------------------------- + +‘-o FILE’ +‘--output-file=FILE’ + Write output to specified file. + + The results are written to standard output if no output file is +specified or if it is ‘-’. + +9.1.3 Message selection +----------------------- + +‘-< NUMBER’ +‘--less-than=NUMBER’ + Print messages with less than NUMBER definitions, defaults to + infinite if not set. + +‘-> NUMBER’ +‘--more-than=NUMBER’ + Print messages with more than NUMBER definitions, defaults to 0 if + not set. + +‘-u’ +‘--unique’ + Shorthand for ‘--less-than=2’. Requests that only unique messages + be printed. + +9.1.4 Input file syntax +----------------------- + +‘-P’ +‘--properties-input’ + Assume the input files are Java ResourceBundles in Java + ‘.properties’ syntax, not in PO file syntax. + +‘--stringtable-input’ + Assume the input files are NeXTstep/GNUstep localized resource + files in ‘.strings’ syntax, not in PO file syntax. + +9.1.5 Output details +-------------------- + +‘-t’ +‘--to-code=NAME’ + Specify encoding for output. + +‘--use-first’ + Use first available translation for each message. Don't merge + several translations into one. + +‘--lang=CATALOGNAME’ + Specify the ‘Language’ field to be used in the header entry. See + *note Header Entry:: for the meaning of this field. Note: The + ‘Language-Team’ and ‘Plural-Forms’ fields are left unchanged. + +‘--color’ +‘--color=WHEN’ + Specify whether or when to use colors and other text attributes. + See *note The --color option:: for details. + +‘--style=STYLE_FILE’ + Specify the CSS style rule file to use for ‘--color’. See *note + The --style option:: for details. + +‘--force-po’ + Always write an output file even if it contains no message. + +‘-i’ +‘--indent’ + Write the .po file using indented style. + +‘--no-location’ + Do not write ‘#: FILENAME:LINE’ lines. + +‘-n’ +‘--add-location=TYPE’ + Generate ‘#: FILENAME:LINE’ lines (default). + + The optional TYPE can be either ‘full’, ‘file’, or ‘never’. If it + is not given or ‘full’, it generates the lines with both file name + and line number. If it is ‘file’, the line number part is omitted. + If it is ‘never’, it completely suppresses the lines (same as + ‘--no-location’). + +‘--strict’ + Write out a strict Uniforum conforming PO file. Note that this + Uniforum format should be avoided because it doesn't support the + GNU extensions. + +‘-p’ +‘--properties-output’ + Write out a Java ResourceBundle in Java ‘.properties’ syntax. Note + that this file format doesn't support plural forms and silently + drops obsolete messages. + +‘--stringtable-output’ + Write out a NeXTstep/GNUstep localized resource file in ‘.strings’ + syntax. Note that this file format doesn't support plural forms. + +‘-w NUMBER’ +‘--width=NUMBER’ + Set the output page width. Long strings in the output files will + be split across multiple lines in order to ensure that each line's + width (= number of screen columns) is less or equal to the given + NUMBER. + +‘--no-wrap’ + Do not break long message lines. Message lines whose width exceeds + the output page width will not be split into several lines. Only + file reference lines which are wider than the output page width + will be split. + +‘-s’ +‘--sort-output’ + Generate sorted output. Note that using this option makes it much + harder for the translator to understand each message's context. + +‘-F’ +‘--sort-by-file’ + Sort output by file location. + +9.1.6 Informative output +------------------------ + +‘-h’ +‘--help’ + Display this help and exit. + +‘-V’ +‘--version’ + Output version information and exit. + + +File: gettext.info, Node: msgconv Invocation, Next: msggrep Invocation, Prev: msgcat Invocation, Up: Manipulating + +9.2 Invoking the ‘msgconv’ Program +================================== + + msgconv [OPTION] [INPUTFILE] + + The ‘msgconv’ program converts a translation catalog to a different +character encoding. + +9.2.1 Input file location +------------------------- + +‘INPUTFILE’ + Input PO file. + +‘-D DIRECTORY’ +‘--directory=DIRECTORY’ + Add DIRECTORY to the list of directories. Source files are + searched relative to this list of directories. The resulting ‘.po’ + file will be written relative to the current directory, though. + + If no INPUTFILE is given or if it is ‘-’, standard input is read. + +9.2.2 Output file location +-------------------------- + +‘-o FILE’ +‘--output-file=FILE’ + Write output to specified file. + + The results are written to standard output if no output file is +specified or if it is ‘-’. + +9.2.3 Conversion target +----------------------- + +‘-t’ +‘--to-code=NAME’ + Specify encoding for output. + + The default encoding is the current locale's encoding. + +9.2.4 Input file syntax +----------------------- + +‘-P’ +‘--properties-input’ + Assume the input file is a Java ResourceBundle in Java + ‘.properties’ syntax, not in PO file syntax. + +‘--stringtable-input’ + Assume the input file is a NeXTstep/GNUstep localized resource file + in ‘.strings’ syntax, not in PO file syntax. + +9.2.5 Output details +-------------------- + +‘--color’ +‘--color=WHEN’ + Specify whether or when to use colors and other text attributes. + See *note The --color option:: for details. + +‘--style=STYLE_FILE’ + Specify the CSS style rule file to use for ‘--color’. See *note + The --style option:: for details. + +‘--force-po’ + Always write an output file even if it contains no message. + +‘-i’ +‘--indent’ + Write the .po file using indented style. + +‘--no-location’ + Do not write ‘#: FILENAME:LINE’ lines. + +‘-n’ +‘--add-location=TYPE’ + Generate ‘#: FILENAME:LINE’ lines (default). + + The optional TYPE can be either ‘full’, ‘file’, or ‘never’. If it + is not given or ‘full’, it generates the lines with both file name + and line number. If it is ‘file’, the line number part is omitted. + If it is ‘never’, it completely suppresses the lines (same as + ‘--no-location’). + +‘--strict’ + Write out a strict Uniforum conforming PO file. Note that this + Uniforum format should be avoided because it doesn't support the + GNU extensions. + +‘-p’ +‘--properties-output’ + Write out a Java ResourceBundle in Java ‘.properties’ syntax. Note + that this file format doesn't support plural forms and silently + drops obsolete messages. + +‘--stringtable-output’ + Write out a NeXTstep/GNUstep localized resource file in ‘.strings’ + syntax. Note that this file format doesn't support plural forms. + +‘-w NUMBER’ +‘--width=NUMBER’ + Set the output page width. Long strings in the output files will + be split across multiple lines in order to ensure that each line's + width (= number of screen columns) is less or equal to the given + NUMBER. + +‘--no-wrap’ + Do not break long message lines. Message lines whose width exceeds + the output page width will not be split into several lines. Only + file reference lines which are wider than the output page width + will be split. + +‘-s’ +‘--sort-output’ + Generate sorted output. Note that using this option makes it much + harder for the translator to understand each message's context. + +‘-F’ +‘--sort-by-file’ + Sort output by file location. + +9.2.6 Informative output +------------------------ + +‘-h’ +‘--help’ + Display this help and exit. + +‘-V’ +‘--version’ + Output version information and exit. + + +File: gettext.info, Node: msggrep Invocation, Next: msgfilter Invocation, Prev: msgconv Invocation, Up: Manipulating + +9.3 Invoking the ‘msggrep’ Program +================================== + + msggrep [OPTION] [INPUTFILE] + + The ‘msggrep’ program extracts all messages of a translation catalog +that match a given pattern or belong to some given source files. + +9.3.1 Input file location +------------------------- + +‘INPUTFILE’ + Input PO file. + +‘-D DIRECTORY’ +‘--directory=DIRECTORY’ + Add DIRECTORY to the list of directories. Source files are + searched relative to this list of directories. The resulting ‘.po’ + file will be written relative to the current directory, though. + + If no INPUTFILE is given or if it is ‘-’, standard input is read. + +9.3.2 Output file location +-------------------------- + +‘-o FILE’ +‘--output-file=FILE’ + Write output to specified file. + + The results are written to standard output if no output file is +specified or if it is ‘-’. + +9.3.3 Message selection +----------------------- + + [-N SOURCEFILE]... [-M DOMAINNAME]... + [-J MSGCTXT-PATTERN] [-K MSGID-PATTERN] [-T MSGSTR-PATTERN] + [-C COMMENT-PATTERN] + + A message is selected if + • it comes from one of the specified source files, + • or if it comes from one of the specified domains, + • or if ‘-J’ is given and its context (msgctxt) matches + MSGCTXT-PATTERN, + • or if ‘-K’ is given and its key (msgid or msgid_plural) matches + MSGID-PATTERN, + • or if ‘-T’ is given and its translation (msgstr) matches + MSGSTR-PATTERN, + • or if ‘-C’ is given and the translator's comment matches + COMMENT-PATTERN. + + When more than one selection criterion is specified, the set of +selected messages is the union of the selected messages of each +criterion. + + MSGCTXT-PATTERN or MSGID-PATTERN or MSGSTR-PATTERN syntax: + [-E | -F] [-e PATTERN | -f FILE]... + PATTERNs are basic regular expressions by default, or extended +regular expressions if -E is given, or fixed strings if -F is given. + +‘-N SOURCEFILE’ +‘--location=SOURCEFILE’ + Select messages extracted from SOURCEFILE. SOURCEFILE can be + either a literal file name or a wildcard pattern. + +‘-M DOMAINNAME’ +‘--domain=DOMAINNAME’ + Select messages belonging to domain DOMAINNAME. + +‘-J’ +‘--msgctxt’ + Start of patterns for the msgctxt. + +‘-K’ +‘--msgid’ + Start of patterns for the msgid. + +‘-T’ +‘--msgstr’ + Start of patterns for the msgstr. + +‘-C’ +‘--comment’ + Start of patterns for the translator's comment. + +‘-X’ +‘--extracted-comment’ + Start of patterns for the extracted comments. + +‘-E’ +‘--extended-regexp’ + Specify that PATTERN is an extended regular expression. + +‘-F’ +‘--fixed-strings’ + Specify that PATTERN is a set of newline-separated strings. + +‘-e PATTERN’ +‘--regexp=PATTERN’ + Use PATTERN as a regular expression. + +‘-f FILE’ +‘--file=FILE’ + Obtain PATTERN from FILE. + +‘-i’ +‘--ignore-case’ + Ignore case distinctions. + +‘-v’ +‘--invert-match’ + Output only the messages that do not match any selection criterion, + instead of the messages that match a selection criterion. + +9.3.4 Input file syntax +----------------------- + +‘-P’ +‘--properties-input’ + Assume the input file is a Java ResourceBundle in Java + ‘.properties’ syntax, not in PO file syntax. + +‘--stringtable-input’ + Assume the input file is a NeXTstep/GNUstep localized resource file + in ‘.strings’ syntax, not in PO file syntax. + +9.3.5 Output details +-------------------- + +‘--color’ +‘--color=WHEN’ + Specify whether or when to use colors and other text attributes. + See *note The --color option:: for details. + +‘--style=STYLE_FILE’ + Specify the CSS style rule file to use for ‘--color’. See *note + The --style option:: for details. + +‘--force-po’ + Always write an output file even if it contains no message. + +‘--indent’ + Write the .po file using indented style. + +‘--no-location’ + Do not write ‘#: FILENAME:LINE’ lines. + +‘-n’ +‘--add-location=TYPE’ + Generate ‘#: FILENAME:LINE’ lines (default). + + The optional TYPE can be either ‘full’, ‘file’, or ‘never’. If it + is not given or ‘full’, it generates the lines with both file name + and line number. If it is ‘file’, the line number part is omitted. + If it is ‘never’, it completely suppresses the lines (same as + ‘--no-location’). + +‘--strict’ + Write out a strict Uniforum conforming PO file. Note that this + Uniforum format should be avoided because it doesn't support the + GNU extensions. + +‘-p’ +‘--properties-output’ + Write out a Java ResourceBundle in Java ‘.properties’ syntax. Note + that this file format doesn't support plural forms and silently + drops obsolete messages. + +‘--stringtable-output’ + Write out a NeXTstep/GNUstep localized resource file in ‘.strings’ + syntax. Note that this file format doesn't support plural forms. + +‘-w NUMBER’ +‘--width=NUMBER’ + Set the output page width. Long strings in the output files will + be split across multiple lines in order to ensure that each line's + width (= number of screen columns) is less or equal to the given + NUMBER. + +‘--no-wrap’ + Do not break long message lines. Message lines whose width exceeds + the output page width will not be split into several lines. Only + file reference lines which are wider than the output page width + will be split. + +‘--sort-output’ + Generate sorted output. Note that using this option makes it much + harder for the translator to understand each message's context. + +‘--sort-by-file’ + Sort output by file location. + +9.3.6 Informative output +------------------------ + +‘-h’ +‘--help’ + Display this help and exit. + +‘-V’ +‘--version’ + Output version information and exit. + +9.3.7 Examples +-------------- + + To extract the messages that come from the source files +‘gnulib-lib/error.c’ and ‘gnulib-lib/getopt.c’: + + msggrep -N gnulib-lib/error.c -N gnulib-lib/getopt.c input.po + + To extract the messages that contain the string "Please specify" in +the original string: + + msggrep --msgid -F -e 'Please specify' input.po + + To extract the messages that have a context specifier of either +"Menu>File" or "Menu>Edit" or a submenu of them: + + msggrep --msgctxt -E -e '^Menu>(File|Edit)' input.po + + To extract the messages whose translation contains one of the strings +in the file ‘wordlist.txt’: + + msggrep --msgstr -F -f wordlist.txt input.po + + +File: gettext.info, Node: msgfilter Invocation, Next: msguniq Invocation, Prev: msggrep Invocation, Up: Manipulating + +9.4 Invoking the ‘msgfilter’ Program +==================================== + + msgfilter [OPTION] FILTER [FILTER-OPTION] + + The ‘msgfilter’ program applies a filter to all translations of a +translation catalog. + + During each FILTER invocation, the environment variable +‘MSGFILTER_MSGID’ is bound to the message's msgid, and the environment +variable ‘MSGFILTER_LOCATION’ is bound to the location in the PO file of +the message. If the message has a context, the environment variable +‘MSGFILTER_MSGCTXT’ is bound to the message's msgctxt, otherwise it is +unbound. If the message has a plural form, environment variable +‘MSGFILTER_MSGID_PLURAL’ is bound to the message's msgid_plural and +‘MSGFILTER_PLURAL_FORM’ is bound to the order number of the plural +actually processed (starting with 0), otherwise both are unbound. If +the message has a previous msgid (added by ‘msgmerge’), environment +variable ‘MSGFILTER_PREV_MSGCTXT’ is bound to the message's previous +msgctxt, ‘MSGFILTER_PREV_MSGID’ is bound to the previous msgid, and +‘MSGFILTER_PREV_MSGID_PLURAL’ is bound to the previous msgid_plural. + +9.4.1 Input file location +------------------------- + +‘-i INPUTFILE’ +‘--input=INPUTFILE’ + Input PO file. + +‘-D DIRECTORY’ +‘--directory=DIRECTORY’ + Add DIRECTORY to the list of directories. Source files are + searched relative to this list of directories. The resulting ‘.po’ + file will be written relative to the current directory, though. + + If no INPUTFILE is given or if it is ‘-’, standard input is read. + +9.4.2 Output file location +-------------------------- + +‘-o FILE’ +‘--output-file=FILE’ + Write output to specified file. + + The results are written to standard output if no output file is +specified or if it is ‘-’. + +9.4.3 The filter +---------------- + + The FILTER can be any program that reads a translation from standard +input and writes a modified translation to standard output. A +frequently used filter is ‘sed’. A few particular built-in filters are +also recognized. + +‘--newline’ + Add newline at the end of each input line and also strip the ending + newline from the output line. + + Note: If the filter is not a built-in filter, you have to care about +encodings: It is your responsibility to ensure that the FILTER can cope +with input encoded in the translation catalog's encoding. If the FILTER +wants input in a particular encoding, you can in a first step convert +the translation catalog to that encoding using the ‘msgconv’ program, +before invoking ‘msgfilter’. If the FILTER wants input in the locale's +encoding, but you want to avoid the locale's encoding, then you can +first convert the translation catalog to UTF-8 using the ‘msgconv’ +program and then make ‘msgfilter’ work in an UTF-8 locale, by using the +‘LC_ALL’ environment variable. + + Note: Most translations in a translation catalog don't end with a +newline character. For this reason, unless the ‘--newline’ option is +used, it is important that the FILTER recognizes its last input line +even if it ends without a newline, and that it doesn't add an undesired +trailing newline at the end. The ‘sed’ program on some platforms is +known to ignore the last line of input if it is not terminated with a +newline. You can use GNU ‘sed’ instead; it does not have this +limitation. + +9.4.4 Useful FILTER-OPTIONs when the FILTER is ‘sed’ +---------------------------------------------------- + +‘-e SCRIPT’ +‘--expression=SCRIPT’ + Add SCRIPT to the commands to be executed. + +‘-f SCRIPTFILE’ +‘--file=SCRIPTFILE’ + Add the contents of SCRIPTFILE to the commands to be executed. + +‘-n’ +‘--quiet’ +‘--silent’ + Suppress automatic printing of pattern space. + +9.4.5 Built-in FILTERs +---------------------- + + The filter ‘recode-sr-latin’ is recognized as a built-in filter. The +command ‘recode-sr-latin’ converts Serbian text, written in the Cyrillic +script, to the Latin script. The command ‘msgfilter recode-sr-latin’ +applies this conversion to the translations of a PO file. Thus, it can +be used to convert an ‘sr.po’ file to an ‘sr@latin.po’ file. + + The filter ‘quot’ is recognized as a built-in filter. The command +‘msgfilter quot’ converts any quotations surrounded by a pair of ‘"’, +‘'’, and ‘`’. + + The filter ‘boldquot’ is recognized as a built-in filter. The +command ‘msgfilter boldquot’ converts any quotations surrounded by a +pair of ‘"’, ‘'’, and ‘`’, also adding the VT100 escape sequences to the +text to decorate it as bold. + + The use of built-in filters is not sensitive to the current locale's +encoding. Moreover, when used with a built-in filter, ‘msgfilter’ can +automatically convert the message catalog to the UTF-8 encoding when +needed. + +9.4.6 Input file syntax +----------------------- + +‘-P’ +‘--properties-input’ + Assume the input file is a Java ResourceBundle in Java + ‘.properties’ syntax, not in PO file syntax. + +‘--stringtable-input’ + Assume the input file is a NeXTstep/GNUstep localized resource file + in ‘.strings’ syntax, not in PO file syntax. + +9.4.7 Output details +-------------------- + +‘--color’ +‘--color=WHEN’ + Specify whether or when to use colors and other text attributes. + See *note The --color option:: for details. + +‘--style=STYLE_FILE’ + Specify the CSS style rule file to use for ‘--color’. See *note + The --style option:: for details. + +‘--force-po’ + Always write an output file even if it contains no message. + +‘--indent’ + Write the .po file using indented style. + +‘--keep-header’ + Keep the header entry, i.e. the message with ‘msgid ""’, + unmodified, instead of filtering it. By default, the header entry + is subject to filtering like any other message. + +‘--no-location’ + Do not write ‘#: FILENAME:LINE’ lines. + +‘-n’ +‘--add-location=TYPE’ + Generate ‘#: FILENAME:LINE’ lines (default). + + The optional TYPE can be either ‘full’, ‘file’, or ‘never’. If it + is not given or ‘full’, it generates the lines with both file name + and line number. If it is ‘file’, the line number part is omitted. + If it is ‘never’, it completely suppresses the lines (same as + ‘--no-location’). + +‘--strict’ + Write out a strict Uniforum conforming PO file. Note that this + Uniforum format should be avoided because it doesn't support the + GNU extensions. + +‘-p’ +‘--properties-output’ + Write out a Java ResourceBundle in Java ‘.properties’ syntax. Note + that this file format doesn't support plural forms and silently + drops obsolete messages. + +‘--stringtable-output’ + Write out a NeXTstep/GNUstep localized resource file in ‘.strings’ + syntax. Note that this file format doesn't support plural forms. + +‘-w NUMBER’ +‘--width=NUMBER’ + Set the output page width. Long strings in the output files will + be split across multiple lines in order to ensure that each line's + width (= number of screen columns) is less or equal to the given + NUMBER. + +‘--no-wrap’ + Do not break long message lines. Message lines whose width exceeds + the output page width will not be split into several lines. Only + file reference lines which are wider than the output page width + will be split. + +‘-s’ +‘--sort-output’ + Generate sorted output. Note that using this option makes it much + harder for the translator to understand each message's context. + +‘-F’ +‘--sort-by-file’ + Sort output by file location. + +9.4.8 Informative output +------------------------ + +‘-h’ +‘--help’ + Display this help and exit. + +‘-V’ +‘--version’ + Output version information and exit. + +9.4.9 Examples +-------------- + + To convert German translations to Swiss orthography (in an UTF-8 +locale): + + msgconv -t UTF-8 de.po | msgfilter sed -e 's/ß/ss/g' + + To convert Serbian translations in Cyrillic script to Latin script: + + msgfilter recode-sr-latin < sr.po + + +File: gettext.info, Node: msguniq Invocation, Next: msgcomm Invocation, Prev: msgfilter Invocation, Up: Manipulating + +9.5 Invoking the ‘msguniq’ Program +================================== + + msguniq [OPTION] [INPUTFILE] + + The ‘msguniq’ program unifies duplicate translations in a translation +catalog. It finds duplicate translations of the same message ID. Such +duplicates are invalid input for other programs like ‘msgfmt’, +‘msgmerge’ or ‘msgcat’. By default, duplicates are merged together. +When using the ‘--repeated’ option, only duplicates are output, and all +other messages are discarded. Comments and extracted comments will be +cumulated, except that if ‘--use-first’ is specified, they will be taken +from the first translation. File positions will be cumulated. When +using the ‘--unique’ option, duplicates are discarded. + +9.5.1 Input file location +------------------------- + +‘INPUTFILE’ + Input PO file. + +‘-D DIRECTORY’ +‘--directory=DIRECTORY’ + Add DIRECTORY to the list of directories. Source files are + searched relative to this list of directories. The resulting ‘.po’ + file will be written relative to the current directory, though. + + If no INPUTFILE is given or if it is ‘-’, standard input is read. + +9.5.2 Output file location +-------------------------- + +‘-o FILE’ +‘--output-file=FILE’ + Write output to specified file. + + The results are written to standard output if no output file is +specified or if it is ‘-’. + +9.5.3 Message selection +----------------------- + +‘-d’ +‘--repeated’ + Print only duplicates. + +‘-u’ +‘--unique’ + Print only unique messages, discard duplicates. + +9.5.4 Input file syntax +----------------------- + +‘-P’ +‘--properties-input’ + Assume the input file is a Java ResourceBundle in Java + ‘.properties’ syntax, not in PO file syntax. + +‘--stringtable-input’ + Assume the input file is a NeXTstep/GNUstep localized resource file + in ‘.strings’ syntax, not in PO file syntax. + +9.5.5 Output details +-------------------- + +‘-t’ +‘--to-code=NAME’ + Specify encoding for output. + +‘--use-first’ + Use first available translation for each message. Don't merge + several translations into one. + +‘--color’ +‘--color=WHEN’ + Specify whether or when to use colors and other text attributes. + See *note The --color option:: for details. + +‘--style=STYLE_FILE’ + Specify the CSS style rule file to use for ‘--color’. See *note + The --style option:: for details. + +‘--force-po’ + Always write an output file even if it contains no message. + +‘-i’ +‘--indent’ + Write the .po file using indented style. + +‘--no-location’ + Do not write ‘#: FILENAME:LINE’ lines. + +‘-n’ +‘--add-location=TYPE’ + Generate ‘#: FILENAME:LINE’ lines (default). + + The optional TYPE can be either ‘full’, ‘file’, or ‘never’. If it + is not given or ‘full’, it generates the lines with both file name + and line number. If it is ‘file’, the line number part is omitted. + If it is ‘never’, it completely suppresses the lines (same as + ‘--no-location’). + +‘--strict’ + Write out a strict Uniforum conforming PO file. Note that this + Uniforum format should be avoided because it doesn't support the + GNU extensions. + +‘-p’ +‘--properties-output’ + Write out a Java ResourceBundle in Java ‘.properties’ syntax. Note + that this file format doesn't support plural forms and silently + drops obsolete messages. + +‘--stringtable-output’ + Write out a NeXTstep/GNUstep localized resource file in ‘.strings’ + syntax. Note that this file format doesn't support plural forms. + +‘-w NUMBER’ +‘--width=NUMBER’ + Set the output page width. Long strings in the output files will + be split across multiple lines in order to ensure that each line's + width (= number of screen columns) is less or equal to the given + NUMBER. + +‘--no-wrap’ + Do not break long message lines. Message lines whose width exceeds + the output page width will not be split into several lines. Only + file reference lines which are wider than the output page width + will be split. + +‘-s’ +‘--sort-output’ + Generate sorted output. Note that using this option makes it much + harder for the translator to understand each message's context. + +‘-F’ +‘--sort-by-file’ + Sort output by file location. + +9.5.6 Informative output +------------------------ + +‘-h’ +‘--help’ + Display this help and exit. + +‘-V’ +‘--version’ + Output version information and exit. + + +File: gettext.info, Node: msgcomm Invocation, Next: msgcmp Invocation, Prev: msguniq Invocation, Up: Manipulating + +9.6 Invoking the ‘msgcomm’ Program +================================== + + msgcomm [OPTION] [INPUTFILE]... + + The ‘msgcomm’ program finds messages which are common to two or more +of the specified PO files. By using the ‘--more-than’ option, greater +commonality may be requested before messages are printed. Conversely, +the ‘--less-than’ option may be used to specify less commonality before +messages are printed (i.e. ‘--less-than=2’ will only print the unique +messages). Translations, comments and extracted comments will be +preserved, but only from the first PO file to define them. File +positions from all PO files will be cumulated. + +9.6.1 Input file location +------------------------- + +‘INPUTFILE ...’ + Input files. + +‘-f FILE’ +‘--files-from=FILE’ + Read the names of the input files from FILE instead of getting them + from the command line. + +‘-D DIRECTORY’ +‘--directory=DIRECTORY’ + Add DIRECTORY to the list of directories. Source files are + searched relative to this list of directories. The resulting ‘.po’ + file will be written relative to the current directory, though. + + If INPUTFILE is ‘-’, standard input is read. + +9.6.2 Output file location +-------------------------- + +‘-o FILE’ +‘--output-file=FILE’ + Write output to specified file. + + The results are written to standard output if no output file is +specified or if it is ‘-’. + +9.6.3 Message selection +----------------------- + +‘-< NUMBER’ +‘--less-than=NUMBER’ + Print messages with less than NUMBER definitions, defaults to + infinite if not set. + +‘-> NUMBER’ +‘--more-than=NUMBER’ + Print messages with more than NUMBER definitions, defaults to 1 if + not set. + +‘-u’ +‘--unique’ + Shorthand for ‘--less-than=2’. Requests that only unique messages + be printed. + +9.6.4 Input file syntax +----------------------- + +‘-P’ +‘--properties-input’ + Assume the input files are Java ResourceBundles in Java + ‘.properties’ syntax, not in PO file syntax. + +‘--stringtable-input’ + Assume the input files are NeXTstep/GNUstep localized resource + files in ‘.strings’ syntax, not in PO file syntax. + +9.6.5 Output details +-------------------- + +‘--color’ +‘--color=WHEN’ + Specify whether or when to use colors and other text attributes. + See *note The --color option:: for details. + +‘--style=STYLE_FILE’ + Specify the CSS style rule file to use for ‘--color’. See *note + The --style option:: for details. + +‘--force-po’ + Always write an output file even if it contains no message. + +‘-i’ +‘--indent’ + Write the .po file using indented style. + +‘--no-location’ + Do not write ‘#: FILENAME:LINE’ lines. + +‘-n’ +‘--add-location=TYPE’ + Generate ‘#: FILENAME:LINE’ lines (default). + + The optional TYPE can be either ‘full’, ‘file’, or ‘never’. If it + is not given or ‘full’, it generates the lines with both file name + and line number. If it is ‘file’, the line number part is omitted. + If it is ‘never’, it completely suppresses the lines (same as + ‘--no-location’). + +‘--strict’ + Write out a strict Uniforum conforming PO file. Note that this + Uniforum format should be avoided because it doesn't support the + GNU extensions. + +‘-p’ +‘--properties-output’ + Write out a Java ResourceBundle in Java ‘.properties’ syntax. Note + that this file format doesn't support plural forms and silently + drops obsolete messages. + +‘--stringtable-output’ + Write out a NeXTstep/GNUstep localized resource file in ‘.strings’ + syntax. Note that this file format doesn't support plural forms. + +‘-w NUMBER’ +‘--width=NUMBER’ + Set the output page width. Long strings in the output files will + be split across multiple lines in order to ensure that each line's + width (= number of screen columns) is less or equal to the given + NUMBER. + +‘--no-wrap’ + Do not break long message lines. Message lines whose width exceeds + the output page width will not be split into several lines. Only + file reference lines which are wider than the output page width + will be split. + +‘-s’ +‘--sort-output’ + Generate sorted output. Note that using this option makes it much + harder for the translator to understand each message's context. + +‘-F’ +‘--sort-by-file’ + Sort output by file location. + +‘--omit-header’ + Don't write header with ‘msgid ""’ entry. Note: Using this option + may lead to an error in subsequent operations if the output + contains non-ASCII characters. + +9.6.6 Informative output +------------------------ + +‘-h’ +‘--help’ + Display this help and exit. + +‘-V’ +‘--version’ + Output version information and exit. + + +File: gettext.info, Node: msgcmp Invocation, Next: msgattrib Invocation, Prev: msgcomm Invocation, Up: Manipulating + +9.7 Invoking the ‘msgcmp’ Program +================================= + + msgcmp [OPTION] DEF.po REF.pot + + The ‘msgcmp’ program compares two Uniforum style .po files to check +that both contain the same set of msgid strings. The DEF.po file is an +existing PO file with the translations. The REF.pot file is the last +created PO file, or a PO Template file (generally created by +‘xgettext’). This is useful for checking that you have translated each +and every message in your program. Where an exact match cannot be +found, fuzzy matching is used to produce better diagnostics. + +9.7.1 Input file location +------------------------- + +‘DEF.po’ + Translations. + +‘REF.pot’ + References to the sources. + +‘-D DIRECTORY’ +‘--directory=DIRECTORY’ + Add DIRECTORY to the list of directories. Source files are + searched relative to this list of directories. + +9.7.2 Operation modifiers +------------------------- + +‘-m’ +‘--multi-domain’ + Apply REF.pot to each of the domains in DEF.po. + +‘-N’ +‘--no-fuzzy-matching’ + Do not use fuzzy matching when an exact match is not found. This + may speed up the operation considerably. + +‘--use-fuzzy’ + Consider fuzzy messages in the DEF.po file like translated + messages. Note that using this option is usually wrong, because + fuzzy messages are exactly those which have not been validated by a + human translator. + +‘--use-untranslated’ + Consider untranslated messages in the DEF.po file like translated + messages. Note that using this option is usually wrong. + +9.7.3 Input file syntax +----------------------- + +‘-P’ +‘--properties-input’ + Assume the input files are Java ResourceBundles in Java + ‘.properties’ syntax, not in PO file syntax. + +‘--stringtable-input’ + Assume the input files are NeXTstep/GNUstep localized resource + files in ‘.strings’ syntax, not in PO file syntax. + +9.7.4 Informative output +------------------------ + +‘-h’ +‘--help’ + Display this help and exit. + +‘-V’ +‘--version’ + Output version information and exit. + + +File: gettext.info, Node: msgattrib Invocation, Next: msgen Invocation, Prev: msgcmp Invocation, Up: Manipulating + +9.8 Invoking the ‘msgattrib’ Program +==================================== + + msgattrib [OPTION] [INPUTFILE] + + The ‘msgattrib’ program filters the messages of a translation catalog +according to their attributes, and manipulates the attributes. + +9.8.1 Input file location +------------------------- + +‘INPUTFILE’ + Input PO file. + +‘-D DIRECTORY’ +‘--directory=DIRECTORY’ + Add DIRECTORY to the list of directories. Source files are + searched relative to this list of directories. The resulting ‘.po’ + file will be written relative to the current directory, though. + + If no INPUTFILE is given or if it is ‘-’, standard input is read. + +9.8.2 Output file location +-------------------------- + +‘-o FILE’ +‘--output-file=FILE’ + Write output to specified file. + + The results are written to standard output if no output file is +specified or if it is ‘-’. + +9.8.3 Message selection +----------------------- + +‘--translated’ + Keep translated messages, remove untranslated messages. + +‘--untranslated’ + Keep untranslated messages, remove translated messages. + +‘--no-fuzzy’ + Remove 'fuzzy' marked messages. + +‘--only-fuzzy’ + Keep 'fuzzy' marked messages, remove all other messages. + +‘--no-obsolete’ + Remove obsolete #~ messages. + +‘--only-obsolete’ + Keep obsolete #~ messages, remove all other messages. + +9.8.4 Attribute manipulation +---------------------------- + + Attributes are modified after the message selection/removal has been +performed. If the ‘--only-file’ or ‘--ignore-file’ option is specified, +the attribute modification is applied only to those messages that are +listed in the ONLY-FILE and not listed in the IGNORE-FILE. + +‘--set-fuzzy’ + Set all messages 'fuzzy'. + +‘--clear-fuzzy’ + Set all messages non-'fuzzy'. + +‘--set-obsolete’ + Set all messages obsolete. + +‘--clear-obsolete’ + Set all messages non-obsolete. + +‘--previous’ + When setting 'fuzzy' mark, keep "previous msgid" of translated + messages. + +‘--clear-previous’ + Remove the "previous msgid" (‘#|’) comments from all messages. + +‘--empty’ + When removing 'fuzzy' mark, also set msgstr empty. + +‘--only-file=FILE’ + Limit the attribute changes to entries that are listed in FILE. + FILE should be a PO or POT file. + +‘--ignore-file=FILE’ + Limit the attribute changes to entries that are not listed in FILE. + FILE should be a PO or POT file. + +‘--fuzzy’ + Synonym for ‘--only-fuzzy --clear-fuzzy’: It keeps only the fuzzy + messages and removes their 'fuzzy' mark. + +‘--obsolete’ + Synonym for ‘--only-obsolete --clear-obsolete’: It keeps only the + obsolete messages and makes them non-obsolete. + +9.8.5 Input file syntax +----------------------- + +‘-P’ +‘--properties-input’ + Assume the input file is a Java ResourceBundle in Java + ‘.properties’ syntax, not in PO file syntax. + +‘--stringtable-input’ + Assume the input file is a NeXTstep/GNUstep localized resource file + in ‘.strings’ syntax, not in PO file syntax. + +9.8.6 Output details +-------------------- + +‘--color’ +‘--color=WHEN’ + Specify whether or when to use colors and other text attributes. + See *note The --color option:: for details. + +‘--style=STYLE_FILE’ + Specify the CSS style rule file to use for ‘--color’. See *note + The --style option:: for details. + +‘--force-po’ + Always write an output file even if it contains no message. + +‘-i’ +‘--indent’ + Write the .po file using indented style. + +‘--no-location’ + Do not write ‘#: FILENAME:LINE’ lines. + +‘-n’ +‘--add-location=TYPE’ + Generate ‘#: FILENAME:LINE’ lines (default). + + The optional TYPE can be either ‘full’, ‘file’, or ‘never’. If it + is not given or ‘full’, it generates the lines with both file name + and line number. If it is ‘file’, the line number part is omitted. + If it is ‘never’, it completely suppresses the lines (same as + ‘--no-location’). + +‘--strict’ + Write out a strict Uniforum conforming PO file. Note that this + Uniforum format should be avoided because it doesn't support the + GNU extensions. + +‘-p’ +‘--properties-output’ + Write out a Java ResourceBundle in Java ‘.properties’ syntax. Note + that this file format doesn't support plural forms and silently + drops obsolete messages. + +‘--stringtable-output’ + Write out a NeXTstep/GNUstep localized resource file in ‘.strings’ + syntax. Note that this file format doesn't support plural forms. + +‘-w NUMBER’ +‘--width=NUMBER’ + Set the output page width. Long strings in the output files will + be split across multiple lines in order to ensure that each line's + width (= number of screen columns) is less or equal to the given + NUMBER. + +‘--no-wrap’ + Do not break long message lines. Message lines whose width exceeds + the output page width will not be split into several lines. Only + file reference lines which are wider than the output page width + will be split. + +‘-s’ +‘--sort-output’ + Generate sorted output. Note that using this option makes it much + harder for the translator to understand each message's context. + +‘-F’ +‘--sort-by-file’ + Sort output by file location. + +9.8.7 Informative output +------------------------ + +‘-h’ +‘--help’ + Display this help and exit. + +‘-V’ +‘--version’ + Output version information and exit. + + +File: gettext.info, Node: msgen Invocation, Next: msgexec Invocation, Prev: msgattrib Invocation, Up: Manipulating + +9.9 Invoking the ‘msgen’ Program +================================ + + msgen [OPTION] INPUTFILE + + The ‘msgen’ program creates an English translation catalog. The +input file is the last created English PO file, or a PO Template file +(generally created by xgettext). Untranslated entries are assigned a +translation that is identical to the msgid. + + Note: ‘msginit --no-translator --locale=en’ performs a very similar +task. The main difference is that ‘msginit’ cares specially about the +header entry, whereas ‘msgen’ doesn't. + +9.9.1 Input file location +------------------------- + +‘INPUTFILE’ + Input PO or POT file. + +‘-D DIRECTORY’ +‘--directory=DIRECTORY’ + Add DIRECTORY to the list of directories. Source files are + searched relative to this list of directories. The resulting ‘.po’ + file will be written relative to the current directory, though. + + If INPUTFILE is ‘-’, standard input is read. + +9.9.2 Output file location +-------------------------- + +‘-o FILE’ +‘--output-file=FILE’ + Write output to specified file. + + The results are written to standard output if no output file is +specified or if it is ‘-’. + +9.9.3 Input file syntax +----------------------- + +‘-P’ +‘--properties-input’ + Assume the input file is a Java ResourceBundle in Java + ‘.properties’ syntax, not in PO file syntax. + +‘--stringtable-input’ + Assume the input file is a NeXTstep/GNUstep localized resource file + in ‘.strings’ syntax, not in PO file syntax. + +9.9.4 Output details +-------------------- + +‘--lang=CATALOGNAME’ + Specify the ‘Language’ field to be used in the header entry. See + *note Header Entry:: for the meaning of this field. Note: The + ‘Language-Team’ and ‘Plural-Forms’ fields are not set by this + option. + +‘--color’ +‘--color=WHEN’ + Specify whether or when to use colors and other text attributes. + See *note The --color option:: for details. + +‘--style=STYLE_FILE’ + Specify the CSS style rule file to use for ‘--color’. See *note + The --style option:: for details. + +‘--force-po’ + Always write an output file even if it contains no message. + +‘-i’ +‘--indent’ + Write the .po file using indented style. + +‘--no-location’ + Do not write ‘#: FILENAME:LINE’ lines. + +‘-n’ +‘--add-location=TYPE’ + Generate ‘#: FILENAME:LINE’ lines (default). + + The optional TYPE can be either ‘full’, ‘file’, or ‘never’. If it + is not given or ‘full’, it generates the lines with both file name + and line number. If it is ‘file’, the line number part is omitted. + If it is ‘never’, it completely suppresses the lines (same as + ‘--no-location’). + +‘--strict’ + Write out a strict Uniforum conforming PO file. Note that this + Uniforum format should be avoided because it doesn't support the + GNU extensions. + +‘-p’ +‘--properties-output’ + Write out a Java ResourceBundle in Java ‘.properties’ syntax. Note + that this file format doesn't support plural forms and silently + drops obsolete messages. + +‘--stringtable-output’ + Write out a NeXTstep/GNUstep localized resource file in ‘.strings’ + syntax. Note that this file format doesn't support plural forms. + +‘-w NUMBER’ +‘--width=NUMBER’ + Set the output page width. Long strings in the output files will + be split across multiple lines in order to ensure that each line's + width (= number of screen columns) is less or equal to the given + NUMBER. + +‘--no-wrap’ + Do not break long message lines. Message lines whose width exceeds + the output page width will not be split into several lines. Only + file reference lines which are wider than the output page width + will be split. + +‘-s’ +‘--sort-output’ + Generate sorted output. Note that using this option makes it much + harder for the translator to understand each message's context. + +‘-F’ +‘--sort-by-file’ + Sort output by file location. + +9.9.5 Informative output +------------------------ + +‘-h’ +‘--help’ + Display this help and exit. + +‘-V’ +‘--version’ + Output version information and exit. + + +File: gettext.info, Node: msgexec Invocation, Next: Colorizing, Prev: msgen Invocation, Up: Manipulating + +9.10 Invoking the ‘msgexec’ Program +=================================== + + msgexec [OPTION] COMMAND [COMMAND-OPTION] + + The ‘msgexec’ program applies a command to all translations of a +translation catalog. The COMMAND can be any program that reads a +translation from standard input. It is invoked once for each +translation. Its output becomes msgexec's output. ‘msgexec’'s return +code is the maximum return code across all invocations. + + A special builtin command called ‘0’ outputs the translation, +followed by a null byte. The output of ‘msgexec 0’ is suitable as input +for ‘xargs -0’. + +‘--newline’ + Add newline at the end of each input line. + + During each COMMAND invocation, the environment variable +‘MSGEXEC_MSGID’ is bound to the message's msgid, and the environment +variable ‘MSGEXEC_LOCATION’ is bound to the location in the PO file of +the message. If the message has a context, the environment variable +‘MSGEXEC_MSGCTXT’ is bound to the message's msgctxt, otherwise it is +unbound. If the message has a plural form, environment variable +‘MSGEXEC_MSGID_PLURAL’ is bound to the message's msgid_plural and +‘MSGEXEC_PLURAL_FORM’ is bound to the order number of the plural +actually processed (starting with 0), otherwise both are unbound. If +the message has a previous msgid (added by ‘msgmerge’), environment +variable ‘MSGEXEC_PREV_MSGCTXT’ is bound to the message's previous +msgctxt, ‘MSGEXEC_PREV_MSGID’ is bound to the previous msgid, and +‘MSGEXEC_PREV_MSGID_PLURAL’ is bound to the previous msgid_plural. + + Note: It is your responsibility to ensure that the COMMAND can cope +with input encoded in the translation catalog's encoding. If the +COMMAND wants input in a particular encoding, you can in a first step +convert the translation catalog to that encoding using the ‘msgconv’ +program, before invoking ‘msgexec’. If the COMMAND wants input in the +locale's encoding, but you want to avoid the locale's encoding, then you +can first convert the translation catalog to UTF-8 using the ‘msgconv’ +program and then make ‘msgexec’ work in an UTF-8 locale, by using the +‘LC_ALL’ environment variable. + +9.10.1 Input file location +-------------------------- + +‘-i INPUTFILE’ +‘--input=INPUTFILE’ + Input PO file. + +‘-D DIRECTORY’ +‘--directory=DIRECTORY’ + Add DIRECTORY to the list of directories. Source files are + searched relative to this list of directories. The resulting ‘.po’ + file will be written relative to the current directory, though. + + If no INPUTFILE is given or if it is ‘-’, standard input is read. + +9.10.2 Input file syntax +------------------------ + +‘-P’ +‘--properties-input’ + Assume the input file is a Java ResourceBundle in Java + ‘.properties’ syntax, not in PO file syntax. + +‘--stringtable-input’ + Assume the input file is a NeXTstep/GNUstep localized resource file + in ‘.strings’ syntax, not in PO file syntax. + +9.10.3 Informative output +------------------------- + +‘-h’ +‘--help’ + Display this help and exit. + +‘-V’ +‘--version’ + Output version information and exit. + + +File: gettext.info, Node: Colorizing, Next: Other tools, Prev: msgexec Invocation, Up: Manipulating + +9.11 Highlighting parts of PO files +=================================== + + Translators are usually only interested in seeing the untranslated +and fuzzy messages of a PO file. Also, when a message is set fuzzy +because the msgid changed, they want to see the differences between the +previous msgid and the current one (especially if the msgid is long and +only few words in it have changed). Finally, it's always welcome to +highlight the different sections of a message in a PO file (comments, +msgid, msgstr, etc.). + + Such highlighting is possible through the options ‘--color’ and +‘--style’. They are supported by all the programs that produce a PO +file on standard output, such as ‘msgcat’, ‘msgmerge’, and ‘msgunfmt’. + +* Menu: + +* The --color option:: Triggering colorized output +* The TERM variable:: The environment variable ‘TERM’ +* The --style option:: The ‘--style’ option +* Style rules:: Style rules for PO files +* Customizing less:: Customizing ‘less’ for viewing PO files + + +File: gettext.info, Node: The --color option, Next: The TERM variable, Up: Colorizing + +9.11.1 The ‘--color’ option +--------------------------- + + The ‘--color=WHEN’ option specifies under which conditions colorized +output should be generated. The WHEN part can be one of the following: + +‘always’ +‘yes’ + The output will be colorized. + +‘never’ +‘no’ + The output will not be colorized. + +‘auto’ +‘tty’ + The output will be colorized if the output device is a tty, i.e. + when the output goes directly to a text screen or terminal emulator + window. + +‘html’ + The output will be colorized and be in HTML format. + +‘test’ + This is a special value, understood only by the ‘msgcat’ program. + It is explained in the next section (*note The TERM variable::). + +‘--color’ is equivalent to ‘--color=yes’. The default is +‘--color=auto’. + + Thus, a command like ‘msgcat vi.po’ will produce colorized output +when called by itself in a command window. Whereas in a pipe, such as +‘msgcat vi.po | less -R’, it will not produce colorized output. To get +colorized output in this situation nevertheless, use the command ‘msgcat +--color vi.po | less -R’. + + The ‘--color=html’ option will produce output that can be viewed in a +browser. This can be useful, for example, for Indic languages, because +the renderic of Indic scripts in browsers is usually better than in +terminal emulators. + + Note that the output produced with the ‘--color’ option is _not_ a +valid PO file in itself. It contains additional terminal-specific +escape sequences or HTML tags. A PO file reader will give a syntax +error when confronted with such content. Except for the ‘--color=html’ +case, you therefore normally don't need to save output produced with the +‘--color’ option in a file. + + +File: gettext.info, Node: The TERM variable, Next: The --style option, Prev: The --color option, Up: Colorizing + +9.11.2 The environment variable ‘TERM’ +-------------------------------------- + + The environment variable ‘TERM’ contains a identifier for the text +window's capabilities. You can get a detailed list of these +cababilities by using the ‘infocmp’ command, using ‘man 5 terminfo’ as a +reference. + + When producing text with embedded color directives, ‘msgcat’ looks at +the ‘TERM’ variable. Text windows today typically support at least 8 +colors. Often, however, the text window supports 16 or more colors, +even though the ‘TERM’ variable is set to a identifier denoting only 8 +supported colors. It can be worth setting the ‘TERM’ variable to a +different value in these cases: + +‘xterm’ + ‘xterm’ is in most cases built with support for 16 colors. It can + also be built with support for 88 or 256 colors (but not both). + You can try to set ‘TERM’ to either ‘xterm-16color’, + ‘xterm-88color’, or ‘xterm-256color’. + +‘rxvt’ + ‘rxvt’ is often built with support for 16 colors. You can try to + set ‘TERM’ to ‘rxvt-16color’. + +‘konsole’ + ‘konsole’ too is often built with support for 16 colors. You can + try to set ‘TERM’ to ‘konsole-16color’ or ‘xterm-16color’. + + After setting ‘TERM’, you can verify it by invoking ‘msgcat +--color=test’ and seeing whether the output looks like a reasonable +color map. + + +File: gettext.info, Node: The --style option, Next: Style rules, Prev: The TERM variable, Up: Colorizing + +9.11.3 The ‘--style’ option +--------------------------- + + The ‘--style=STYLE_FILE’ option specifies the style file to use when +colorizing. It has an effect only when the ‘--color’ option is +effective. + + If the ‘--style’ option is not specified, the environment variable +‘PO_STYLE’ is considered. It is meant to point to the user's preferred +style for PO files. + + The default style file is +‘$prefix/share/gettext/styles/po-default.css’, where ‘$prefix’ is the +installation location. + + A few style files are predefined: +‘po-vim.css’ + This style imitates the look used by vim 7. + +‘po-emacs-x.css’ + This style imitates the look used by GNU Emacs 21 and 22 in an X11 + window. + +‘po-emacs-xterm.css’ +‘po-emacs-xterm16.css’ +‘po-emacs-xterm256.css’ + This style imitates the look used by GNU Emacs 22 in a terminal of + type ‘xterm’ (8 colors) or ‘xterm-16color’ (16 colors) or + ‘xterm-256color’ (256 colors), respectively. + +You can use these styles without specifying a directory. They are +actually located in ‘$prefix/share/gettext/styles/’, where ‘$prefix’ is +the installation location. + + You can also design your own styles. This is described in the next +section. + + +File: gettext.info, Node: Style rules, Next: Customizing less, Prev: The --style option, Up: Colorizing + +9.11.4 Style rules for PO files +------------------------------- + + The same style file can be used for styling of a PO file, for +terminal output and for HTML output. It is written in CSS (Cascading +Style Sheet) syntax. See for a +formal definition of CSS. Many HTML authoring tutorials also contain +explanations of CSS. + + In the case of HTML output, the style file is embedded in the HTML +output. In the case of text output, the style file is interpreted by +the ‘msgcat’ program. This means, in particular, that when ‘@import’ is +used with relative file names, the file names are + + − relative to the resulting HTML file, in the case of HTML output, + + − relative to the style sheet containing the ‘@import’, in the case + of text output. (Actually, ‘@import’s are not yet supported in + this case, due to a limitation in ‘libcroco’.) + + CSS rules are built up from selectors and declarations. The +declarations specify graphical properties; the selectors specify when +they apply. + + In PO files, the following simple selectors (based on "CSS classes", +see the CSS2 spec, section 5.8.3) are supported. + + • Selectors that apply to entire messages: + + ‘.header’ + This matches the header entry of a PO file. + + ‘.translated’ + This matches a translated message. + + ‘.untranslated’ + This matches an untranslated message (i.e. a message with + empty translation). + + ‘.fuzzy’ + This matches a fuzzy message (i.e. a message which has a + translation that needs review by the translator). + + ‘.obsolete’ + This matches an obsolete message (i.e. a message that was + translated but is not needed by the current POT file any + more). + + • Selectors that apply to parts of a message in PO syntax. Recall + the general structure of a message in PO syntax: + + WHITE-SPACE + # TRANSLATOR-COMMENTS + #. EXTRACTED-COMMENTS + #: REFERENCE... + #, FLAG... + #| msgid PREVIOUS-UNTRANSLATED-STRING + msgid UNTRANSLATED-STRING + msgstr TRANSLATED-STRING + + ‘.comment’ + This matches all comments (translator comments, extracted + comments, source file reference comments, flag comments, + previous message comments, as well as the entire obsolete + messages). + + ‘.translator-comment’ + This matches the translator comments. + + ‘.extracted-comment’ + This matches the extracted comments, i.e. the comments placed + by the programmer at the attention of the translator. + + ‘.reference-comment’ + This matches the source file reference comments (entire + lines). + + ‘.reference’ + This matches the individual source file references inside the + source file reference comment lines. + + ‘.flag-comment’ + This matches the flag comment lines (entire lines). + + ‘.flag’ + This matches the individual flags inside flag comment lines. + + ‘.fuzzy-flag’ + This matches the 'fuzzy' flag inside flag comment lines. + + ‘.previous-comment’ + This matches the comments containing the previous untranslated + string (entire lines). + + ‘.previous’ + This matches the previous untranslated string including the + string delimiters, the associated keywords (‘msgid’ etc.) and + the spaces between them. + + ‘.msgid’ + This matches the untranslated string including the string + delimiters, the associated keywords (‘msgid’ etc.) and the + spaces between them. + + ‘.msgstr’ + This matches the translated string including the string + delimiters, the associated keywords (‘msgstr’ etc.) and the + spaces between them. + + ‘.keyword’ + This matches the keywords (‘msgid’, ‘msgstr’, etc.). + + ‘.string’ + This matches strings, including the string delimiters (double + quotes). + + • Selectors that apply to parts of strings: + + ‘.text’ + This matches the entire contents of a string (excluding the + string delimiters, i.e. the double quotes). + + ‘.escape-sequence’ + This matches an escape sequence (starting with a backslash). + + ‘.format-directive’ + This matches a format string directive (starting with a ‘%’ + sign in the case of most programming languages, with a ‘{’ in + the case of ‘java-format’ and ‘csharp-format’, with a ‘~’ in + the case of ‘lisp-format’ and ‘scheme-format’, or with ‘$’ in + the case of ‘sh-format’). + + ‘.invalid-format-directive’ + This matches an invalid format string directive. + + ‘.added’ + In an untranslated string, this matches a part of the string + that was not present in the previous untranslated string. + (Not yet implemented in this release.) + + ‘.changed’ + In an untranslated string or in a previous untranslated + string, this matches a part of the string that is changed or + replaced. (Not yet implemented in this release.) + + ‘.removed’ + In a previous untranslated string, this matches a part of the + string that is not present in the current untranslated string. + (Not yet implemented in this release.) + + These selectors can be combined to hierarchical selectors. For +example, + + .msgstr .invalid-format-directive { color: red; } + +will highlight the invalid format directives in the translated strings. + + In text mode, pseudo-classes (CSS2 spec, section 5.11) and +pseudo-elements (CSS2 spec, section 5.12) are not supported. + + The declarations in HTML mode are not limited; any graphical +attribute supported by the browsers can be used. + + The declarations in text mode are limited to the following +properties. Other properties will be silently ignored. + +‘color’ (CSS2 spec, section 14.1) +‘background-color’ (CSS2 spec, section 14.2.1) + These properties is supported. Colors will be adjusted to match + the terminal's capabilities. Note that many terminals support only + 8 colors. + +‘font-weight’ (CSS2 spec, section 15.2.3) + This property is supported, but most terminals can only render two + different weights: ‘normal’ and ‘bold’. Values >= 600 are rendered + as ‘bold’. + +‘font-style’ (CSS2 spec, section 15.2.3) + This property is supported. The values ‘italic’ and ‘oblique’ are + rendered the same way. + +‘text-decoration’ (CSS2 spec, section 16.3.1) + This property is supported, limited to the values ‘none’ and + ‘underline’. + + +File: gettext.info, Node: Customizing less, Prev: Style rules, Up: Colorizing + +9.11.5 Customizing ‘less’ for viewing PO files +---------------------------------------------- + + The ‘less’ program is a popular text file browser for use in a text +screen or terminal emulator. It also supports text with embedded escape +sequences for colors and text decorations. + + You can use ‘less’ to view a PO file like this (assuming an UTF-8 +environment): + + msgcat --to-code=UTF-8 --color xyz.po | less -R + + You can simplify this to this simple command: + + less xyz.po + +after these three preparations: + + 1. Add the options ‘-R’ and ‘-f’ to the ‘LESS’ environment variable. + In sh shells: + $ LESS="$LESS -R -f" + $ export LESS + + 2. If your system does not already have the ‘lessopen.sh’ and + ‘lessclose.sh’ scripts, create them and set the ‘LESSOPEN’ and + ‘LESSCLOSE’ environment variables, as indicated in the manual page + (‘man less’). + + 3. Add to ‘lessopen.sh’ a piece of script that recognizes PO files + through their file extension and invokes ‘msgcat’ on them, + producing a temporary file. Like this: + + case "$1" in + *.po) + tmpfile=`mktemp "${TMPDIR-/tmp}/less.XXXXXX"` + msgcat --to-code=UTF-8 --color "$1" > "$tmpfile" + echo "$tmpfile" + exit 0 + ;; + esac + + +File: gettext.info, Node: Other tools, Next: libgettextpo, Prev: Colorizing, Up: Manipulating + +9.12 Other tools for manipulating PO files +========================================== + +Pology +------ + + The "Pology" package is a Free Software package for manipulating PO +files. It features, in particular: + + • Examination and in-place modification of collections of PO files. + • Format-aware diffing and patching of PO files. + • Handling of version-control branches. + • Fine-grained asynchronous review workflow. + • Custom translation validation. + • Language and project specific support. + + Its home page is at . + +Translate Toolkit +----------------- + + The "Translate Toolkit" is a Free Software package. It contains a +set of programs to convert between PO files and other file formats, +merge translations, and perform various checks. + + Its home page is at . The code +is at . + + +File: gettext.info, Node: libgettextpo, Prev: Other tools, Up: Manipulating + +9.13 Writing your own programs that process PO files +==================================================== + + For the tasks for which a combination of ‘msgattrib’, ‘msgcat’ etc. +is not sufficient, a set of C functions is provided in a library, to +make it possible to process PO files in your own programs. When you use +this library, you don't need to write routines to parse the PO file; +instead, you retrieve a pointer in memory to each of messages contained +in the PO file. Functions for writing those memory structures to a file +after working with them are provided too. + + The functions are declared in the header file ‘’, and +are defined in a library called ‘libgettextpo’. + + The library is multithread-safe in the following sense: Different +threads can safely use the various functions simultaneously on unrelated +data objects. For example, if several threads have created separate +‘po_file_t’ objects, each of them can safely work on its respective +‘po_file_t’ object, without caring about the other threads. + +* Menu: + +* Error Handling:: Error handling functions +* po_file_t API:: File management +* po_message_iterator_t API:: Message iteration +* po_message_t API:: The basic units of the file +* PO Header Entry API:: Meta information of the file +* po_filepos_t API:: References to the sources +* Format Type API:: Supported format types +* Checking API:: Enforcing constraints + + The following example shows code how these functions can be used. +Error handling code is omitted, as its implementation is delegated to +the user provided functions. + + struct po_xerror_handler handler = + { + .xerror = ..., + .xerror2 = ... + }; + const char *filename = ...; + /* Read the file into memory. */ + po_file_t file = po_file_read (filename, &handler); + + { + const char * const *domains = po_file_domains (file); + const char * const *domainp; + + /* Iterate the domains contained in the file. */ + for (domainp = domains; *domainp; domainp++) + { + po_message_t *message; + const char *domain = *domainp; + po_message_iterator_t iterator = po_message_iterator (file, domain); + + /* Iterate each message inside the domain. */ + while ((message = po_next_message (iterator)) != NULL) + { + /* Read data from the message ... */ + const char *msgid = po_message_msgid (message); + const char *msgstr = po_message_msgstr (message); + + ... + + /* Modify its contents ... */ + if (perform_some_tests (msgid, msgstr)) + po_message_set_fuzzy (message, 1); + + ... + } + /* Always release returned po_message_iterator_t. */ + po_message_iterator_free (iterator); + } + + /* Write back the result. */ + po_file_t result = po_file_write (file, filename, &handler); + } + + /* Always release the returned po_file_t. */ + po_file_free (file); + + +File: gettext.info, Node: Error Handling, Next: po_file_t API, Up: libgettextpo + +9.13.1 Error Handling +--------------------- + + Error management is performed through callbacks provided by the user +of the library. They are provided through a parameter with the +following type: + + -- Data Type: struct po_xerror_handler + Its pointer is defined as ‘po_xerror_handler_t’. Contains two + fields, ‘xerror’ and ‘xerror2’, with the following function + signatures. + + -- Function: void xerror (int SEVERITY, po_message_t MESSAGE, + const char *FILENAME, size_t LINENO, size_t COLUMN, + int MULTILINE_P, const char *MESSAGE_TEXT) + + This function is called to signal a problem of the given SEVERITY. + It _must not return_ if SEVERITY is ‘PO_SEVERITY_FATAL_ERROR’. + + MESSAGE_TEXT is the problem description. When MULTILINE_P is true, + it can contain multiple lines of text, each terminated with a + newline, otherwise a single line. + + MESSAGE and/or FILENAME and LINENO indicate where the problem + occurred: + + • If FILENAME is ‘NULL’, FILENAME and LINENO and COLUMN should + be ignored. + + • If LINENO is ‘(size_t)(-1)’, LINENO and COLUMN should be + ignored. + + • If COLUMN is ‘(size_t)(-1)’, it should be ignored. + + -- Function: void xerror2 (int SEVERITY, po_message_t MESSAGE1, + const char *FILENAME1, size_t LINENO1, size_t COLUMN1, + int MULTILINE_P1, const char *MESSAGE_TEXT1, + po_message_t MESSAGE2, const char *FILENAME2, size_t LINENO2, + size_t COLUMN2, int MULTILINE_P2, const char *MESSAGE_TEXT2) + + This function is called to signal a problem of the given SEVERITY + that refers to two messages. It _must not return_ if SEVERITY is + ‘PO_SEVERITY_FATAL_ERROR’. + + It is similar to two calls to xerror. If possible, an ellipsis can + be appended to MESSAGE_TEXT1 and prepended to MESSAGE_TEXT2. + + +File: gettext.info, Node: po_file_t API, Next: po_message_iterator_t API, Prev: Error Handling, Up: libgettextpo + +9.13.2 po_file_t API +-------------------- + + -- Data Type: po_file_t + This is a pointer type that refers to the contents of a PO file, + after it has been read into memory. + + -- Function: po_file_t po_file_create () + The ‘po_file_create’ function creates an empty PO file + representation in memory. + + -- Function: po_file_t po_file_read (const char *FILENAME, + struct po_xerror_handler *HANDLER) + The ‘po_file_read’ function reads a PO file into memory. The file + name is given as argument. The return value is a handle to the PO + file's contents, valid until ‘po_file_free’ is called on it. In + case of error, the functions from HANDLER are called to signal it. + + This function is exported as ‘po_file_read_v3’ at ABI level, but is + defined as ‘po_file_read’ in C code after the inclusion of + ‘’. + + -- Function: po_file_t po_file_write (po_file_t FILE, + const char *FILENAME, struct po_xerror_handler *HANDLER) + The ‘po_file_write’ function writes the contents of the memory + structure FILE the FILENAME given. The return value is FILE after + a successful operation. In case of error, the functions from + HANDLER are called to signal it. + + This function is exported as ‘po_file_write_v2’ at ABI level, but + is defined as ‘po_file_write’ in C code after the inclusion of + ‘’. + + -- Function: void po_file_free (po_file_t FILE) + The ‘po_file_free’ function frees a PO file's contents from memory, + including all messages that are only implicitly accessible through + iterators. + + -- Function: const char * const * po_file_domains (po_file_t FILE) + The ‘po_file_domains’ function returns the domains for which the + given PO file has messages. The return value is a ‘NULL’ + terminated array which is valid as long as the FILE handle is + valid. For PO files which contain no ‘domain’ directive, the + return value contains only one domain, namely the default domain + ‘"messages"’. + + +File: gettext.info, Node: po_message_iterator_t API, Next: po_message_t API, Prev: po_file_t API, Up: libgettextpo + +9.13.3 po_message_iterator_t API +-------------------------------- + + -- Data Type: po_message_iterator_t + This is a pointer type that refers to an iterator that produces a + sequence of messages. + + -- Function: po_message_iterator_t po_message_iterator (po_file_t FILE, + const char *DOMAIN) + The ‘po_message_iterator’ returns an iterator that will produce the + messages of FILE that belong to the given DOMAIN. If DOMAIN is + ‘NULL’, the default domain is used instead. To list the messages, + use the function ‘po_next_message’ repeatedly. + + -- Function: void po_message_iterator_free + (po_message_iterator_t ITERATOR) + The ‘po_message_iterator_free’ function frees an iterator + previously allocated through the ‘po_message_iterator’ function. + + -- Function: po_message_t po_next_message + (po_message_iterator_t ITERATOR) + The ‘po_next_message’ function returns the next message from + ITERATOR and advances the iterator. It returns ‘NULL’ when the + iterator has reached the end of its message list. + + +File: gettext.info, Node: po_message_t API, Next: PO Header Entry API, Prev: po_message_iterator_t API, Up: libgettextpo + +9.13.4 po_message_t API +----------------------- + + -- Data Type: po_message_t + This is a pointer type that refers to a message of a PO file, + including its translation. + + -- Function: po_message_t po_message_create (void) + Returns a freshly constructed message. To finish initializing the + message, you must set the ‘msgid’ and ‘msgstr’. It _must_ be + inserted into a file to manage its memory, as there is no + ‘po_message_free’ available to the user of the library. + + The following functions access details of a ‘po_message_t’. Recall +that the results are valid as long as the FILE handle is valid. + + -- Function: const char * po_message_msgctxt (po_message_t MESSAGE) + The ‘po_message_msgctxt’ function returns the ‘msgctxt’, the + context of MESSAGE. Returns ‘NULL’ for a message not restricted to + a context. + + -- Function: void po_message_set_msgctxt (po_message_t MESSAGE, + const char *MSGCTXT) + The ‘po_message_set_msgctxt’ function changes the ‘msgctxt’, the + context of the message, to the value provided through MSGCTXT. The + value ‘NULL’ removes the restriction. + + -- Function: const char * po_message_msgid (po_message_t MESSAGE) + The ‘po_message_msgid’ function returns the ‘msgid’ (untranslated + English string) of MESSAGE. This is guaranteed to be non-‘NULL’. + + -- Function: void po_message_set_msgid (po_message_t MESSAGE, + const char *MSGID) + The ‘po_message_set_msgid’ function changes the ‘msgid’ + (untranslated English string) of MESSAGE to the value provided + through MSGID, a non-‘NULL’ string. + + -- Function: const char * po_message_msgid_plural + (po_message_t MESSAGE) + The ‘po_message_msgid_plural’ function returns the ‘msgid_plural’ + (untranslated English plural string) of MESSAGE, a message with + plurals, or ‘NULL’ for a message without plural. + + -- Function: void po_message_set_msgid_plural (po_message_t MESSAGE, + const char *MSGID_PLURAL) + The ‘po_message_set_msgid_plural’ function changes the + ‘msgid_plural’ (untranslated English plural string) of a message to + the value provided through MSGID_PLURAL, or removes the plurals if + ‘NULL’ is provided as MSGID_PLURAL. + + -- Function: const char * po_message_msgstr (po_message_t MESSAGE) + The ‘po_message_msgstr’ function returns the ‘msgstr’ (translation) + of MESSAGE. For an untranslated message, the return value is an + empty string. + + -- Function: void po_message_set_msgstr (po_message_t MESSAGE, + const char *MSGSTR) + The ‘po_message_set_msgstr’ function changes the ‘msgstr’ + (translation) of MESSAGE to the value provided through MSGSTR, a + non-‘NULL’ string. + + -- Function: const char * po_message_msgstr_plural + (po_message_t MESSAGE, int INDEX) + The ‘po_message_msgstr_plural’ function returns the ‘msgstr[INDEX]’ + of MESSAGE, a message with plurals, or ‘NULL’ when the INDEX is out + of range or for a message without plural. + + -- Function: void po_message_set_msgstr_plural (po_message_t MESSAGE, + int INDEX, const char *MSGSTR_PLURAL) + The ‘po_message_set_msgstr_plural’ function changes the + ‘msgstr[INDEX]’ of MESSAGE, a message with plurals, to the value + provided through MSGSTR_PLURAL. MESSAGE must be a message with + plurals. Use ‘NULL’ as the value of MSGSTR_PLURAL with INDEX + pointing to the last element to reduce the number of plural forms. + + -- Function: const char * po_message_comments (po_message_t MESSAGE) + The ‘po_message_comments’ function returns the comments of MESSAGE, + a multiline string, ending in a newline, or a non-‘NULL’ empty + string. + + -- Function: void po_message_set_comments (po_message_t MESSAGE, + const char *COMMENTS) + The ‘po_message_set_comments’ function changes the comments of + MESSAGE to the value COMMENTS, a multiline string, ending in a + newline, or a non-‘NULL’ empty string. + + -- Function: const char * po_message_extracted_comments + (po_message_t MESSAGE) + The ‘po_message_extracted_comments’ function returns the extracted + comments of MESSAGE, a multiline string, ending in a newline, or a + non-‘NULL’ empty string. + + -- Function: void po_message_set_extracted_comments + (po_message_t MESSAGE, const char *EXTRACTED_COMMENTS) + The ‘po_message_set_extracted_comments’ function changes the + comments of MESSAGE to the value EXTRACTED_COMMENTS, a multiline + string, ending in a newline, or a non-‘NULL’ empty string. + + -- Function: const char * po_message_prev_msgctxt + (po_message_t MESSAGE) + The ‘po_message_prev_msgctxt’ function returns the previous + ‘msgctxt’, the previous context of MESSAGE. Return ‘NULL’ for a + message that does not have a previous context. + + -- Function: void po_message_set_prev_msgctxt (po_message_t MESSAGE, + const char *PREV_MSGCTXT) + The ‘po_message_set_prev_msgctxt’ function changes the previous + ‘msgctxt’, the context of the message, to the value provided + through PREV_MSGCTXT. The value ‘NULL’ removes the stored previous + msgctxt. + + -- Function: const char * po_message_prev_msgid (po_message_t MESSAGE) + The ‘po_message_prev_msgid’ function returns the previous ‘msgid’ + (untranslated English string) of MESSAGE, or ‘NULL’ if there is no + previous ‘msgid’ stored. + + -- Function: void po_message_set_prev_msgid (po_message_t MESSAGE, + const char *PREV_MSGID) + The ‘po_message_set_prev_msgid’ function changes the previous + ‘msgid’ (untranslated English string) of MESSAGE to the value + provided through PREV_MSGID, or removes the message when it is + ‘NULL’. + + -- Function: const char * po_message_prev_msgid_plural + (po_message_t MESSAGE) + The ‘po_message_prev_msgid_plural’ function returns the previous + ‘msgid_plural’ (untranslated English plural string) of MESSAGE, a + message with plurals, or ‘NULL’ for a message without plural + without any stored previous ‘msgid_plural’. + + -- Function: void po_message_set_prev_msgid_plural + (po_message_t MESSAGE, const char *PREV_MSGID_PLURAL) + The ‘po_message_set_prev_msgid_plural’ function changes the + previous ‘msgid_plural’ (untranslated English plural string) of a + message to the value provided through PREV_MSGID_PLURAL, or removes + the stored previous ‘msgid_plural’ if ‘NULL’ is provided as + PREV_MSGID_PLURAL. + + -- Function: int po_message_is_obsolete (po_message_t MESSAGE) + The ‘po_message_is_obsolete’ function returns true when MESSAGE is + marked as obsolete. + + -- Function: void po_message_set_obsolete (po_message_t MESSAGE, + int OBSOLETE) + The ‘po_message_set_obsolete’ function changes the obsolete mark of + MESSAGE. + + -- Function: int po_message_is_fuzzy (po_message_t MESSAGE) + The ‘po_message_is_fuzzy’ function returns true when MESSAGE is + marked as fuzzy. + + -- Function: void po_message_set_fuzzy (po_message_t MESSAGE, + int FUZZY) + The ‘po_message_set_fuzzy’ function changes the fuzzy mark of + MESSAGE. + + -- Function: int po_message_is_format (po_message_t MESSAGE, + const char *FORMAT_TYPE) + The ‘po_message_is_format’ function returns true when the message + is marked as being a format string of FORMAT_TYPE. + + -- Function: void po_message_set_format (po_message_t MESSAGE, + const char *FORMAT_TYPE, int VALUE) + The ‘po_message_set_format’ function changes the format string mark + of the message for the FORMAT_TYPE provided. Pass VALUE = 1 to + assert the format string mark (leading to e.g. ‘c-format’), VALUE + = 0 to assert the opposite (leading to e.g. ‘no-c-format’), or + VALUE = -1 to remove the format string mark and its opposite. + + -- Function: int po_message_is_range (po_message_t MESSAGE, int *MINP, + int *MAXP) + The ‘po_message_is_range’ function returns true when the message + has a numeric range set, and stores the minimum and maximum value + in the locations pointed by MINP and MAXP respectively. + + -- Function: void po_message_set_range (po_message_t MESSAGE, int MIN, + int MAX) + The ‘po_message_set_range’ function changes the numeric range of + the message. MIN and MAX must be non-negative, with MIN < MAX. + Use MIN and MAX with value ‘-1’ to remove the numeric range of + MESSAGE. + + +File: gettext.info, Node: PO Header Entry API, Next: po_filepos_t API, Prev: po_message_t API, Up: libgettextpo + +9.13.5 PO Header Entry API +-------------------------- + + The following functions provide an interface to extract and +manipulate the header entry (*note Header Entry::) from a file loaded in +memory. The meta information must be written back into the domain +message with the empty string as ‘msgid’. + + -- Function: const char * po_file_domain_header (po_file_t FILE, + const char *DOMAIN) + Returns the header entry of a domain from FILE, a PO file loaded in + memory. The value ‘NULL’ provided as DOMAIN denotes the default + domain. Returns ‘NULL’ if there is no header entry. + + -- Function: char * po_header_field (const char *HEADER, + const char *FIELD) + Returns the value of FIELD in the HEADER entry. The return value + is either a freshly allocated string, to be freed by the caller, or + ‘NULL’. + + -- Function: char * po_header_set_field (const char *HEADER, + const char *FIELD, const char *VALUE) + Returns a freshly allocated string which contains the entry from + HEADER with FIELD set to VALUE. The field is added if necessary. + + +File: gettext.info, Node: po_filepos_t API, Next: Format Type API, Prev: PO Header Entry API, Up: libgettextpo + +9.13.6 po_filepos_t API +----------------------- + + -- Data Type: po_filepos_t + This is a pointer type that refers to a string's position within a + source file. + + The following functions provide an interface to extract and +manipulate these references. + + -- Function: po_filepos_t po_message_filepos (po_message_t MESSAGE, + int INDEX) + Returns the file reference in position INDEX from the message. If + INDEX is out of range, returns ‘NULL’. + + -- Function: void po_message_remove_filepos (po_message_t MESSAGE, + int INDEX) + Removes the file reference in position INDEX from the message. It + moves all references following INDEX one position backwards. + + -- Function: void po_message_add_filepos (po_message_t MESSAGE, + const char *FILE, size_t START_LINE) + Adds a reference to the string from FILE starting at START_LINE, if + it is not already present for the message. The value + ‘(size_t)(-1)’ for START_LINE denotes that the line number is not + available. + + +File: gettext.info, Node: Format Type API, Next: Checking API, Prev: po_filepos_t API, Up: libgettextpo + +9.13.7 Format Type API +---------------------- + + -- Function: const char * const * po_format_list (void) + Returns a ‘NULL’ terminated array of the supported format types. + + -- Function: const char * po_format_pretty_name + (const char *FORMAT_TYPE) + Returns the pretty name associated with FORMAT_TYPE. For example, + it returns "C#" when FORMAT_TYPE is "csharp_format". Return ‘NULL’ + if FORMAT_TYPE is not a supported format type. + + +File: gettext.info, Node: Checking API, Prev: Format Type API, Up: libgettextpo + +9.13.8 Checking API +------------------- + + -- Function: void po_file_check_all (po_file_t FILE, + po_xerror_handler_t HANDLER) + Tests whether the entire FILE is valid, like ‘msgfmt’ does it. If + it is invalid, passes the reasons to HANDLER. + + -- Function: void po_message_check_all (po_message_t MESSAGE, + po_message_iterator_t ITERATOR, po_xerror_handler_t HANDLER) + Tests MESSAGE, to be inserted at ITERATOR in a PO file in memory, + like ‘msgfmt’ does it. If it is invalid, passes the reasons to + HANDLER. ITERATOR is not modified by this call; it only specifies + the file and the domain. + + -- Function: void po_message_check_format (po_message_t MESSAGE, + po_xerror_handler_t HANDLER) + Tests whether the message translation from MESSAGE is a valid + format string if the message is marked as being a format string. + If it is invalid, passes the reasons to HANDLER. + + This function is exported as ‘po_message_check_format_v2’ at ABI + level, but is defined as ‘po_message_check_format’ in C code after + the inclusion of ‘’. + + +File: gettext.info, Node: Binaries, Next: Programmers, Prev: Manipulating, Up: Top + +10 Producing Binary MO Files +**************************** + +* Menu: + +* msgfmt Invocation:: Invoking the ‘msgfmt’ Program +* msgunfmt Invocation:: Invoking the ‘msgunfmt’ Program +* MO Files:: The Format of GNU MO Files + + +File: gettext.info, Node: msgfmt Invocation, Next: msgunfmt Invocation, Up: Binaries + +10.1 Invoking the ‘msgfmt’ Program +================================== + + msgfmt [OPTION] FILENAME.po ... + + The ‘msgfmt’ programs generates a binary message catalog from a +textual translation description. + +10.1.1 Input file location +-------------------------- + +‘FILENAME.po ...’ + +‘-D DIRECTORY’ +‘--directory=DIRECTORY’ + Add DIRECTORY to the list of directories. Source files are + searched relative to this list of directories. The resulting + binary file will be written relative to the current directory, + though. + + If an input file is ‘-’, standard input is read. + +10.1.2 Operation mode +--------------------- + +‘-j’ +‘--java’ + Java mode: generate a Java ‘ResourceBundle’ class. + +‘--java2’ + Like -java, and assume Java2 (JDK 1.2 or higher). + +‘--csharp’ + C# mode: generate a .NET .dll file containing a subclass of + ‘GettextResourceSet’. + +‘--csharp-resources’ + C# resources mode: generate a .NET ‘.resources’ file. + +‘--tcl’ + Tcl mode: generate a tcl/msgcat ‘.msg’ file. + +‘--qt’ + Qt mode: generate a Qt ‘.qm’ file. + +‘--desktop’ + Desktop Entry mode: generate a ‘.desktop’ file. + +‘--xml’ + XML mode: generate an XML file. + +10.1.3 Output file location +--------------------------- + +‘-o FILE’ +‘--output-file=FILE’ + Write output to specified file. + +‘--strict’ + Direct the program to work strictly following the Uniforum/Sun + implementation. Currently this only affects the naming of the + output file. If this option is not given the name of the output + file is the same as the domain name. If the strict Uniforum mode + is enabled the suffix ‘.mo’ is added to the file name if it is not + already present. + + We find this behaviour of Sun's implementation rather silly and so + by default this mode is _not_ selected. + + If the output FILE is ‘-’, output is written to standard output. + +10.1.4 Output file location in Java mode +---------------------------------------- + +‘-r RESOURCE’ +‘--resource=RESOURCE’ + Specify the resource name. + +‘-l LOCALE’ +‘--locale=LOCALE’ + Specify the locale name, either a language specification of the + form LL or a combined language and country specification of the + form LL_CC. + +‘-d DIRECTORY’ + Specify the base directory of classes directory hierarchy. + +‘--source’ + Produce a .java source file, instead of a compiled .class file. + + The class name is determined by appending the locale name to the +resource name, separated with an underscore. The ‘-d’ option is +mandatory. The class is written under the specified directory. + +10.1.5 Output file location in C# mode +-------------------------------------- + +‘-r RESOURCE’ +‘--resource=RESOURCE’ + Specify the resource name. + +‘-l LOCALE’ +‘--locale=LOCALE’ + Specify the locale name, either a language specification of the + form LL or a combined language and country specification of the + form LL_CC. + +‘-d DIRECTORY’ + Specify the base directory for locale dependent ‘.dll’ files. + + The ‘-l’ and ‘-d’ options are mandatory. The ‘.dll’ file is written +in a subdirectory of the specified directory whose name depends on the +locale. + +10.1.6 Output file location in Tcl mode +--------------------------------------- + +‘-l LOCALE’ +‘--locale=LOCALE’ + Specify the locale name, either a language specification of the + form LL or a combined language and country specification of the + form LL_CC. + +‘-d DIRECTORY’ + Specify the base directory of ‘.msg’ message catalogs. + + The ‘-l’ and ‘-d’ options are mandatory. The ‘.msg’ file is written +in the specified directory. + +10.1.7 Desktop Entry mode options +--------------------------------- + +‘--template=TEMPLATE’ + Specify a .desktop file used as a template. + +‘-k[KEYWORDSPEC]’ +‘--keyword[=KEYWORDSPEC]’ + Specify KEYWORDSPEC as an additional keyword to be looked for. + Without a KEYWORDSPEC, the option means to not use default + keywords. + +‘-l LOCALE’ +‘--locale=LOCALE’ + Specify the locale name, either a language specification of the + form LL or a combined language and country specification of the + form LL_CC. + +‘-d DIRECTORY’ + Specify the directory where PO files are read. The directory must + contain the ‘LINGUAS’ file. + + To generate a ‘.desktop’ file for a single locale, you can use it as +follows. + + msgfmt --desktop --template=TEMPLATE --locale=LOCALE \ + -o FILE FILENAME.po ... + + msgfmt provides a special "bulk" operation mode to process multiple +‘.po’ files at a time. + + msgfmt --desktop --template=TEMPLATE -d DIRECTORY -o FILE + + msgfmt first reads the ‘LINGUAS’ file under DIRECTORY, and then +processes all ‘.po’ files listed there. You can also limit the locales +to a subset, through the ‘LINGUAS’ environment variable. + + For either operation modes, the ‘-o’ and ‘--template’ options are +mandatory. + +10.1.8 XML mode options +----------------------- + +‘--template=TEMPLATE’ + Specify an XML file used as a template. + +‘-L NAME’ +‘--language=NAME’ + Specifies the language of the input files. + +‘-l LOCALE’ +‘--locale=LOCALE’ + Specify the locale name, either a language specification of the + form LL or a combined language and country specification of the + form LL_CC. + +‘-d DIRECTORY’ + Specify the base directory of ‘.po’ message catalogs. + +‘--replace-text’ + Output XML with translated text replacing the original text, not + augmenting the original text. With this option, ‘msgfmt’ produces + a mono-lingual XML file. Without this option, it produces a + multi-lingual XML file. + + To generate an XML file for a single locale, you can use it as +follows. + + msgfmt --xml --template=TEMPLATE --locale=LOCALE \ + -o FILE FILENAME.po ... + + msgfmt provides a special "bulk" operation mode to process multiple +‘.po’ files at a time. + + msgfmt --xml --template=TEMPLATE -d DIRECTORY -o FILE + + msgfmt first reads the ‘LINGUAS’ file under DIRECTORY, and then +processes all ‘.po’ files listed there. You can also limit the locales +to a subset, through the ‘LINGUAS’ environment variable. + + For either operation modes, the ‘-o’ and ‘--template’ options are +mandatory. + + If your XML file is not of one of the types covered by the +system-wide installed *.its files, you need a particular *.its file and +a corresponding *.loc file (*note Preparing ITS Rules::). Furthermore +you need to store these files in a directory ‘PARENT_DIR/its/’ and set +the environment variable ‘GETTEXTDATADIRS’ to include ‘PARENT_DIR’. +More generally, the value of ‘GETTEXTDATADIRS’ should be a +colon-separated list of directory names. + +10.1.9 Input file syntax +------------------------ + +‘-P’ +‘--properties-input’ + Assume the input files are Java ResourceBundles in Java + ‘.properties’ syntax, not in PO file syntax. + +‘--stringtable-input’ + Assume the input files are NeXTstep/GNUstep localized resource + files in ‘.strings’ syntax, not in PO file syntax. + +10.1.10 Input file interpretation +--------------------------------- + +‘-c’ +‘--check’ + Perform all the checks implied by ‘--check-format’, + ‘--check-header’, ‘--check-domain’. + +‘--check-format’ + Check language dependent format strings. + + If the string represents a format string used in a ‘printf’-like + function both strings should have the same number of ‘%’ format + specifiers, with matching types. If the flag ‘c-format’ or + ‘possible-c-format’ appears in the special comment <#,> for this + entry a check is performed. For example, the check will diagnose + using ‘%.*s’ against ‘%s’, or ‘%d’ against ‘%s’, or ‘%d’ against + ‘%x’. It can even handle positional parameters. + + Normally the ‘xgettext’ program automatically decides whether a + string is a format string or not. This algorithm is not perfect, + though. It might regard a string as a format string though it is + not used in a ‘printf’-like function and so ‘msgfmt’ might report + errors where there are none. + + To solve this problem the programmer can dictate the decision to + the ‘xgettext’ program (*note c-format::). The translator should + not consider removing the flag from the <#,> line. This "fix" + would be reversed again as soon as ‘msgmerge’ is called the next + time. + +‘--check-header’ + Verify presence and contents of the header entry. *Note Header + Entry::, for a description of the various fields in the header + entry. + +‘--check-domain’ + Check for conflicts between domain directives and the + ‘--output-file’ option + +‘-C’ +‘--check-compatibility’ + Check that GNU msgfmt behaves like X/Open msgfmt. This will give + an error when attempting to use the GNU extensions. + +‘--check-accelerators[=CHAR]’ + Check presence of keyboard accelerators for menu items. This is + based on the convention used in some GUIs that a keyboard + accelerator in a menu item string is designated by an immediately + preceding ‘&’ character. Sometimes a keyboard accelerator is also + called "keyboard mnemonic". This check verifies that if the + untranslated string has exactly one ‘&’ character, the translated + string has exactly one ‘&’ as well. If this option is given with a + CHAR argument, this CHAR should be a non-alphanumeric character and + is used as keyboard accelerator mark instead of ‘&’. + +‘-f’ +‘--use-fuzzy’ + Use fuzzy entries in output. Note that using this option is + usually wrong, because fuzzy messages are exactly those which have + not been validated by a human translator. + +10.1.11 Output details +---------------------- + +‘--no-convert’ + Don't convert the messages to UTF-8 encoding. By default, messages + are converted to UTF-8 encoding before being stored in a MO file; + this helps avoiding conversions at run time, since nowadays most + locales use the UTF-8 encoding. + +‘--no-redundancy’ + Don't pre-expand ISO C 99 format string directive + macros. By default, messages that are marked as ‘c-format’ and + contain ISO C 99 format string directive macros are + pre-expanded for selected platforms, and these redundant expansions + are stored in the MO file. These redundant expansions make the + translations of these messages work with the ‘gettext’ + implementation in the ‘libc’ of that platform, without requiring + GNU ‘gettext’'s ‘libintl’. The platforms that benefit from this + pre-expansion are those with the musl libc. + +‘-a NUMBER’ +‘--alignment=NUMBER’ + Align strings to NUMBER bytes (default: 1). + +‘--endianness=BYTEORDER’ + Write out 32-bit numbers in the given byte order. The possible + values are ‘big’ and ‘little’. The default is ‘little’. + + MO files of any endianness can be used on any platform. When a MO + file has an endianness other than the platform's one, the 32-bit + numbers from the MO file are swapped at runtime. The performance + impact is negligible. + + This option can be useful to produce MO files that are optimized + for one platform. + +‘--no-hash’ + Don't include a hash table in the binary file. Lookup will be more + expensive at run time (binary search instead of hash table lookup). + +10.1.12 Informative output +-------------------------- + +‘-h’ +‘--help’ + Display this help and exit. + +‘-V’ +‘--version’ + Output version information and exit. + +‘--statistics’ + Print statistics about translations. When the option ‘--verbose’ + is used in combination with ‘--statistics’, the input file name is + printed in front of the statistics line. + +‘-v’ +‘--verbose’ + Increase verbosity level. + + +File: gettext.info, Node: msgunfmt Invocation, Next: MO Files, Prev: msgfmt Invocation, Up: Binaries + +10.2 Invoking the ‘msgunfmt’ Program +==================================== + + msgunfmt [OPTION] [FILE]... + + The ‘msgunfmt’ program converts a binary message catalog to a +Uniforum style .po file. + +10.2.1 Operation mode +--------------------- + +‘-j’ +‘--java’ + Java mode: input is a Java ‘ResourceBundle’ class. + +‘--csharp’ + C# mode: input is a .NET .dll file containing a subclass of + ‘GettextResourceSet’. + +‘--csharp-resources’ + C# resources mode: input is a .NET ‘.resources’ file. + +‘--tcl’ + Tcl mode: input is a tcl/msgcat ‘.msg’ file. + +10.2.2 Input file location +-------------------------- + +‘FILE ...’ + Input .mo files. + + If no input FILE is given or if it is ‘-’, standard input is read. + +10.2.3 Input file location in Java mode +--------------------------------------- + +‘-r RESOURCE’ +‘--resource=RESOURCE’ + Specify the resource name. + +‘-l LOCALE’ +‘--locale=LOCALE’ + Specify the locale name, either a language specification of the + form LL or a combined language and country specification of the + form LL_CC. + + The class name is determined by appending the locale name to the +resource name, separated with an underscore. The class is located using +the ‘CLASSPATH’. + +10.2.4 Input file location in C# mode +------------------------------------- + +‘-r RESOURCE’ +‘--resource=RESOURCE’ + Specify the resource name. + +‘-l LOCALE’ +‘--locale=LOCALE’ + Specify the locale name, either a language specification of the + form LL or a combined language and country specification of the + form LL_CC. + +‘-d DIRECTORY’ + Specify the base directory for locale dependent ‘.dll’ files. + + The ‘-l’ and ‘-d’ options are mandatory. The ‘.msg’ file is located +in a subdirectory of the specified directory whose name depends on the +locale. + +10.2.5 Input file location in Tcl mode +-------------------------------------- + +‘-l LOCALE’ +‘--locale=LOCALE’ + Specify the locale name, either a language specification of the + form LL or a combined language and country specification of the + form LL_CC. + +‘-d DIRECTORY’ + Specify the base directory of ‘.msg’ message catalogs. + + The ‘-l’ and ‘-d’ options are mandatory. The ‘.msg’ file is located +in the specified directory. + +10.2.6 Output file location +--------------------------- + +‘-o FILE’ +‘--output-file=FILE’ + Write output to specified file. + + The results are written to standard output if no output file is +specified or if it is ‘-’. + +10.2.7 Output details +--------------------- + +‘--color’ +‘--color=WHEN’ + Specify whether or when to use colors and other text attributes. + See *note The --color option:: for details. + +‘--style=STYLE_FILE’ + Specify the CSS style rule file to use for ‘--color’. See *note + The --style option:: for details. + +‘--force-po’ + Always write an output file even if it contains no message. + +‘-i’ +‘--indent’ + Write the .po file using indented style. + +‘--strict’ + Write out a strict Uniforum conforming PO file. Note that this + Uniforum format should be avoided because it doesn't support the + GNU extensions. + +‘-p’ +‘--properties-output’ + Write out a Java ResourceBundle in Java ‘.properties’ syntax. Note + that this file format doesn't support plural forms and silently + drops obsolete messages. + +‘--stringtable-output’ + Write out a NeXTstep/GNUstep localized resource file in ‘.strings’ + syntax. Note that this file format doesn't support plural forms. + +‘-w NUMBER’ +‘--width=NUMBER’ + Set the output page width. Long strings in the output files will + be split across multiple lines in order to ensure that each line's + width (= number of screen columns) is less or equal to the given + NUMBER. + +‘--no-wrap’ + Do not break long message lines. Message lines whose width exceeds + the output page width will not be split into several lines. Only + file reference lines which are wider than the output page width + will be split. + +‘-s’ +‘--sort-output’ + Generate sorted output. Note that using this option makes it much + harder for the translator to understand each message's context. + +10.2.8 Informative output +------------------------- + +‘-h’ +‘--help’ + Display this help and exit. + +‘-V’ +‘--version’ + Output version information and exit. + +‘-v’ +‘--verbose’ + Increase verbosity level. + + +File: gettext.info, Node: MO Files, Prev: msgunfmt Invocation, Up: Binaries + +10.3 The Format of GNU MO Files +=============================== + + The format of the generated MO files is best described by a picture, +which appears below. + + The first two words serve the identification of the file. The magic +number will always signal GNU MO files. The number is stored in the +byte order used when the MO file was generated, so the magic number +really is two numbers: ‘0x950412de’ and ‘0xde120495’. + + The second word describes the current revision of the file format, +composed of a major and a minor revision number. The revision numbers +ensure that the readers of MO files can distinguish new formats from old +ones and handle their contents, as far as possible. For now the major +revision is 0 or 1, and the minor revision is also 0 or 1. More +revisions might be added in the future. A program seeing an unexpected +major revision number should stop reading the MO file entirely; whereas +an unexpected minor revision number means that the file can be read but +will not reveal its full contents, when parsed by a program that +supports only smaller minor revision numbers. + + The version is kept separate from the magic number, instead of using +different magic numbers for different formats, mainly because +‘/etc/magic’ is not updated often. + + Follow a number of pointers to later tables in the file, allowing for +the extension of the prefix part of MO files without having to recompile +programs reading them. This might become useful for later inserting a +few flag bits, indication about the charset used, new tables, or other +things. + + Then, at offset O and offset T in the picture, two tables of string +descriptors can be found. In both tables, each string descriptor uses +two 32 bits integers, one for the string length, another for the offset +of the string in the MO file, counting in bytes from the start of the +file. The first table contains descriptors for the original strings, +and is sorted so the original strings are in increasing lexicographical +order. The second table contains descriptors for the translated +strings, and is parallel to the first table: to find the corresponding +translation one has to access the array slot in the second array with +the same index. + + Having the original strings sorted enables the use of simple binary +search, for when the MO file does not contain an hashing table, or for +when it is not practical to use the hashing table provided in the MO +file. This also has another advantage, as the empty string in a PO file +GNU ‘gettext’ is usually _translated_ into some system information +attached to that particular MO file, and the empty string necessarily +becomes the first in both the original and translated tables, making the +system information very easy to find. + + The size S of the hash table can be zero. In this case, the hash +table itself is not contained in the MO file. Some people might prefer +this because a precomputed hashing table takes disk space, and does not +win _that_ much speed. The hash table contains indices to the sorted +array of strings in the MO file. Conflict resolution is done by double +hashing. The precise hashing algorithm used is fairly dependent on GNU +‘gettext’ code, and is not documented here. + + As for the strings themselves, they follow the hash file, and each is +terminated with a , and this is not counted in the length +which appears in the string descriptor. The ‘msgfmt’ program has an +option selecting the alignment for MO file strings. With this option, +each string is separately aligned so it starts at an offset which is a +multiple of the alignment value. On some RISC machines, a correct +alignment will speed things up. + + Contexts are stored by storing the concatenation of the context, a + byte, and the original string, instead of the original string. + + Plural forms are stored by letting the plural of the original string +follow the singular of the original string, separated through a +byte. The length which appears in the string descriptor includes both. +However, only the singular of the original string takes part in the hash +table lookup. The plural variants of the translation are all stored +consecutively, separated through a byte. Here also, the length in +the string descriptor includes all of them. + + The character encoding of the strings can be any standard +ASCII-compatible encoding, such as UTF-8, ISO-8859-1, EUC-JP, etc., as +long as the encoding's name is stated in the header entry (*note Header +Entry::). Starting with GNU ‘gettext’ version 0.22, the MO files +produced by ‘msgfmt’ have them in UTF-8 encoding, unless the ‘msgfmt’ +option ‘--no-convert’ is used. + + Nothing prevents a MO file from having embedded s in strings. +However, the program interface currently used already presumes that +strings are terminated, so embedded s are somewhat useless. +But the MO file format is general enough so other interfaces would be +later possible, if for example, we ever want to implement wide +characters right in MO files, where bytes may accidentally appear. +(No, we don't want to have wide characters in MO files. They would make +the file unnecessarily large, and the ‘wchar_t’ type being platform +dependent, MO files would be platform dependent as well.) + + This particular issue has been strongly debated in the GNU ‘gettext’ +development forum, and it is expectable that MO file format will evolve +or change over time. It is even possible that many formats may later be +supported concurrently. But surely, we have to start somewhere, and the +MO file format described here is a good start. Nothing is cast in +concrete, and the format may later evolve fairly easily, so we should +feel comfortable with the current approach. + + byte + +------------------------------------------+ + 0 | magic number = 0x950412de | + | | + 4 | file format revision = 0 | + | | + 8 | number of strings | == N + | | + 12 | offset of table with original strings | == O + | | + 16 | offset of table with translation strings | == T + | | + 20 | size of hashing table | == S + | | + 24 | offset of hashing table | == H + | | + . . + . (possibly more entries later) . + . . + | | + O | length & offset 0th string ----------------. + O + 8 | length & offset 1st string ------------------. + ... ... | | + O + ((N-1)*8)| length & offset (N-1)th string | | | + | | | | + T | length & offset 0th translation ---------------. + T + 8 | length & offset 1st translation -----------------. + ... ... | | | | + T + ((N-1)*8)| length & offset (N-1)th translation | | | | | + | | | | | | + H | start hash table | | | | | + ... ... | | | | + H + S * 4 | end hash table | | | | | + | | | | | | + | NUL terminated 0th string <----------------' | | | + | | | | | + | NUL terminated 1st string <------------------' | | + | | | | + ... ... | | + | | | | + | NUL terminated 0th translation <---------------' | + | | | + | NUL terminated 1st translation <-----------------' + | | + ... ... + | | + +------------------------------------------+ + + +File: gettext.info, Node: Programmers, Next: Translators, Prev: Binaries, Up: Top + +11 The Programmer's View +************************ + + One aim of the current message catalog implementation provided by GNU +‘gettext’ was to use the system's message catalog handling, if the +installer wishes to do so. So we perhaps should first take a look at +the solutions we know about. The people in the POSIX committee did not +manage to agree on one of the semi-official standards which we'll +describe below. In fact they couldn't agree on anything, so they +decided only to include an example of an interface. The major Unix +vendors are split in the usage of the two most important specifications: +X/Open's catgets vs. Uniforum's gettext interface. We'll describe them +both and later explain our solution of this dilemma. + +* Menu: + +* catgets:: About ‘catgets’ +* gettext:: About ‘gettext’ +* Comparison:: Comparing the two interfaces +* Using libintl.a:: Using libintl.a in own programs +* gettext grok:: Being a ‘gettext’ grok +* Temp Programmers:: Temporary Notes for the Programmers Chapter + + +File: gettext.info, Node: catgets, Next: gettext, Up: Programmers + +11.1 About ‘catgets’ +==================== + + The ‘catgets’ implementation is defined in the X/Open Portability +Guide, Volume 3, XSI Supplementary Definitions, Chapter 5. But the +process of creating this standard seemed to be too slow for some of the +Unix vendors so they created their implementations on preliminary +versions of the standard. Of course this leads again to problems while +writing platform independent programs: even the usage of ‘catgets’ does +not guarantee a unique interface. + + Another, personal comment on this that only a bunch of committee +members could have made this interface. They never really tried to +program using this interface. It is a fast, memory-saving +implementation, an user can happily live with it. But programmers hate +it (at least I and some others do...) + + But we must not forget one point: after all the trouble with +transferring the rights on Unix they at last came to X/Open, the very +same who published this specification. This leads me to making the +prediction that this interface will be in future Unix standards (e.g. +Spec1170) and therefore part of all Unix implementation +(implementations, which are _allowed_ to wear this name). + +* Menu: + +* Interface to catgets:: The interface +* Problems with catgets:: Problems with the ‘catgets’ interface?! + + +File: gettext.info, Node: Interface to catgets, Next: Problems with catgets, Up: catgets + +11.1.1 The Interface +-------------------- + + The interface to the ‘catgets’ implementation consists of three +functions which correspond to those used in file access: ‘catopen’ to +open the catalog for using, ‘catgets’ for accessing the message tables, +and ‘catclose’ for closing after work is done. Prototypes for the +functions and the needed definitions are in the ‘’ header +file. + + ‘catopen’ is used like in this: + + nl_catd catd = catopen ("catalog_name", 0); + + The function takes as the argument the name of the catalog. This +usual refers to the name of the program or the package. The second +parameter is not further specified in the standard. I don't even know +whether it is implemented consistently among various systems. So the +common advice is to use ‘0’ as the value. The return value is a handle +to the message catalog, equivalent to handles to file returned by +‘open’. + + This handle is of course used in the ‘catgets’ function which can be +used like this: + + char *translation = catgets (catd, set_no, msg_id, "original string"); + + The first parameter is this catalog descriptor. The second parameter +specifies the set of messages in this catalog, in which the message +described by ‘msg_id’ is obtained. ‘catgets’ therefore uses a +three-stage addressing: + + catalog name ⇒ set number ⇒ message ID ⇒ translation + + The fourth argument is not used to address the translation. It is +given as a default value in case when one of the addressing stages fail. +One important thing to remember is that although the return type of +catgets is ‘char *’ the resulting string _must not_ be changed. It +should better be ‘const char *’, but the standard is published in 1988, +one year before ANSI C. + +The last of these functions is used and behaves as expected: + + catclose (catd); + + After this no ‘catgets’ call using the descriptor is legal anymore. + + +File: gettext.info, Node: Problems with catgets, Prev: Interface to catgets, Up: catgets + +11.1.2 Problems with the ‘catgets’ Interface?! +---------------------------------------------- + + Now that this description seemed to be really easy -- where are the +problems we speak of? In fact the interface could be used in a +reasonable way, but constructing the message catalogs is a pain. The +reason for this lies in the third argument of ‘catgets’: the unique +message ID. This has to be a numeric value for all messages in a single +set. Perhaps you could imagine the problems keeping such a list while +changing the source code. Add a new message here, remove one there. Of +course there have been developed a lot of tools helping to organize this +chaos but one as the other fails in one aspect or the other. We don't +want to say that the other approach has no problems but they are far +more easy to manage. + + +File: gettext.info, Node: gettext, Next: Comparison, Prev: catgets, Up: Programmers + +11.2 About ‘gettext’ +==================== + + The definition of the ‘gettext’ interface comes from a Uniforum +proposal. It was submitted there by Sun, who had implemented the +‘gettext’ function in SunOS 4, around 1990. Nowadays, the ‘gettext’ +interface is specified by the OpenI18N standard. + + The main point about this solution is that it does not follow the +method of normal file handling (open-use-close) and that it does not +burden the programmer with so many tasks, especially the unique key +handling. Of course here also a unique key is needed, but this key is +the message itself (how long or short it is). See *note Comparison:: +for a more detailed comparison of the two methods. + + The following section contains a rather detailed description of the +interface. We make it that detailed because this is the interface we +chose for the GNU ‘gettext’ Library. Programmers interested in using +this library will be interested in this description. + +* Menu: + +* Interface to gettext:: The interface +* Ambiguities:: Solving ambiguities +* Locating Catalogs:: Locating message catalog files +* Charset conversion:: How to request conversion to Unicode +* Contexts:: Solving ambiguities in GUI programs +* Plural forms:: Additional functions for handling plurals +* Optimized gettext:: Optimization of the *gettext functions + + +File: gettext.info, Node: Interface to gettext, Next: Ambiguities, Up: gettext + +11.2.1 The Interface +-------------------- + + The minimal functionality an interface must have is a) to select a +domain the strings are coming from (a single domain for all programs is +not reasonable because its construction and maintenance is difficult, +perhaps impossible) and b) to access a string in a selected domain. + + This is principally the description of the ‘gettext’ interface. It +has a global domain which unqualified usages reference. Of course this +domain is selectable by the user. + + char *textdomain (const char *domain_name); + + This provides the possibility to change or query the current status +of the current global domain of the ‘LC_MESSAGE’ category. The argument +is a null-terminated string, whose characters must be legal in the use +in filenames. If the DOMAIN_NAME argument is ‘NULL’, the function +returns the current value. If no value has been set before, the name of +the default domain is returned: _messages_. Please note that although +the return value of ‘textdomain’ is of type ‘char *’ no changing is +allowed. It is also important to know that no checks of the +availability are made. If the name is not available you will see this +by the fact that no translations are provided. + +To use a domain set by ‘textdomain’ the function + + char *gettext (const char *msgid); + +is to be used. This is the simplest reasonable form one can imagine. +The translation of the string MSGID is returned if it is available in +the current domain. If it is not available, the argument itself is +returned. If the argument is ‘NULL’ the result is undefined. + + One thing which should come into mind is that no explicit dependency +to the used domain is given. The current value of the domain is used. +If this changes between two executions of the same ‘gettext’ call in the +program, both calls reference a different message catalog. + + For the easiest case, which is normally used in internationalized +packages, once at the beginning of execution a call to ‘textdomain’ is +issued, setting the domain to a unique name, normally the package name. +In the following code all strings which have to be translated are +filtered through the gettext function. That's all, the package speaks +your language. + + +File: gettext.info, Node: Ambiguities, Next: Locating Catalogs, Prev: Interface to gettext, Up: gettext + +11.2.2 Solving Ambiguities +-------------------------- + + While this single name domain works well for most applications there +might be the need to get translations from more than one domain. Of +course one could switch between different domains with calls to +‘textdomain’, but this is really not convenient nor is it fast. A +possible situation could be one case subject to discussion during this +writing: all error messages of functions in the set of common used +functions should go into a separate domain ‘error’. By this mean we +would only need to translate them once. Another case are messages from +a library, as these _have_ to be independent of the current domain set +by the application. + +For this reasons there are two more functions to retrieve strings: + + char *dgettext (const char *domain_name, const char *msgid); + char *dcgettext (const char *domain_name, const char *msgid, + int category); + + Both take an additional argument at the first place, which +corresponds to the argument of ‘textdomain’. The third argument of +‘dcgettext’ allows to use another locale category but ‘LC_MESSAGES’. +But I really don't know where this can be useful. If the DOMAIN_NAME is +‘NULL’ or CATEGORY has an value beside the known ones, the result is +undefined. It should also be noted that this function is not part of +the second known implementation of this function family, the one found +in Solaris. + + A second ambiguity can arise by the fact, that perhaps more than one +domain has the same name. This can be solved by specifying where the +needed message catalog files can be found. + + char *bindtextdomain (const char *domain_name, + const char *dir_name); + + Calling this function binds the given domain to a file in the +specified directory (how this file is determined follows below). +Especially a file in the systems default place is not favored against +the specified file anymore (as it would be by solely using +‘textdomain’). A ‘NULL’ pointer for the DIR_NAME parameter returns the +binding associated with DOMAIN_NAME. If DOMAIN_NAME itself is ‘NULL’ +nothing happens and a ‘NULL’ pointer is returned. Here again as for all +the other functions is true that none of the return value must be +changed! + + It is important to remember that relative path names for the DIR_NAME +parameter can be trouble. Since the path is always computed relative to +the current directory different results will be achieved when the +program executes a ‘chdir’ command. Relative paths should always be +avoided to avoid dependencies and unreliabilities. + + wchar_t *wbindtextdomain (const char *domain_name, + const wchar_t *dir_name); + + This function is provided only on native Windows platforms. It is +like ‘bindtextdomain’, except that the DIR_NAME parameter is a wide +string (in UTF-16 encoding, as usual on Windows). + + +File: gettext.info, Node: Locating Catalogs, Next: Charset conversion, Prev: Ambiguities, Up: gettext + +11.2.3 Locating Message Catalog Files +------------------------------------- + + Because many different languages for many different packages have to +be stored we need some way to add these information to file message +catalog files. The way usually used in Unix environments is have this +encoding in the file name. This is also done here. The directory name +given in ‘bindtextdomain’s second argument (or the default directory), +followed by the name of the locale, the locale category, and the domain +name are concatenated: + + DIR_NAME/LOCALE/LC_CATEGORY/DOMAIN_NAME.mo + + The default value for DIR_NAME is system specific. For the GNU +library, and for packages adhering to its conventions, it's: + /usr/local/share/locale + +LOCALE is the name of the locale category which is designated by +‘LC_CATEGORY’. For ‘gettext’ and ‘dgettext’ this ‘LC_CATEGORY’ is +always ‘LC_MESSAGES’.(1) The name of the locale category is determined +through ‘setlocale (LC_CATEGORY, NULL)’. (2) When using the function +‘dcgettext’, you can specify the locale category through the third +argument. + + ---------- Footnotes ---------- + + (1) Some system, e.g. mingw, don't have ‘LC_MESSAGES’. Here we use a +more or less arbitrary value for it, namely 1729, the smallest positive +integer which can be represented in two different ways as the sum of two +cubes. + + (2) When the system does not support ‘setlocale’ its behavior in +setting the locale values is simulated by looking at the environment +variables. + + +File: gettext.info, Node: Charset conversion, Next: Contexts, Prev: Locating Catalogs, Up: gettext + +11.2.4 How to specify the output character set ‘gettext’ uses +------------------------------------------------------------- + + ‘gettext’ not only looks up a translation in a message catalog. It +also converts the translation on the fly to the desired output character +set. This is useful if the user is working in a different character set +than the translator who created the message catalog, because it avoids +distributing variants of message catalogs which differ only in the +character set. + + The output character set is, by default, the value of ‘nl_langinfo +(CODESET)’, which depends on the ‘LC_CTYPE’ part of the current locale. +But programs which store strings in a locale independent way (e.g. +UTF-8) can request that ‘gettext’ and related functions return the +translations in that encoding, by use of the ‘bind_textdomain_codeset’ +function. + + Note that the MSGID argument to ‘gettext’ is not subject to character +set conversion. Also, when ‘gettext’ does not find a translation for +MSGID, it returns MSGID unchanged - independently of the current output +character set. It is therefore recommended that all MSGIDs be US-ASCII +strings. + + -- Function: char * bind_textdomain_codeset (const char *DOMAINNAME, + const char *CODESET) + The ‘bind_textdomain_codeset’ function can be used to specify the + output character set for message catalogs for domain DOMAINNAME. + The CODESET argument must be a valid codeset name which can be used + for the ‘iconv_open’ function, or a null pointer. + + If the CODESET parameter is the null pointer, + ‘bind_textdomain_codeset’ returns the currently selected codeset + for the domain with the name DOMAINNAME. It returns ‘NULL’ if no + codeset has yet been selected. + + The ‘bind_textdomain_codeset’ function can be used several times. + If used multiple times with the same DOMAINNAME argument, the later + call overrides the settings made by the earlier one. + + The ‘bind_textdomain_codeset’ function returns a pointer to a + string containing the name of the selected codeset. The string is + allocated internally in the function and must not be changed by the + user. If the system went out of core during the execution of + ‘bind_textdomain_codeset’, the return value is ‘NULL’ and the + global variable ERRNO is set accordingly. + + +File: gettext.info, Node: Contexts, Next: Plural forms, Prev: Charset conversion, Up: gettext + +11.2.5 Using contexts for solving ambiguities +--------------------------------------------- + + One place where the ‘gettext’ functions, if used normally, have big +problems is within programs with graphical user interfaces (GUIs). The +problem is that many of the strings which have to be translated are very +short. They have to appear in pull-down menus which restricts the +length. But strings which are not containing entire sentences or at +least large fragments of a sentence may appear in more than one +situation in the program but might have different translations. This is +especially true for the one-word strings which are frequently used in +GUI programs. + + As a consequence many people say that the ‘gettext’ approach is wrong +and instead ‘catgets’ should be used which indeed does not have this +problem. But there is a very simple and powerful method to handle this +kind of problems with the ‘gettext’ functions. + + Contexts can be added to strings to be translated. A context +dependent translation lookup is when a translation for a given string is +searched, that is limited to a given context. The translation for the +same string in a different context can be different. The different +translations of the same string in different contexts can be stored in +the in the same MO file, and can be edited by the translator in the same +PO file. + + The ‘gettext.h’ include file contains the lookup macros for strings +with contexts. They are implemented as thin macros and inline functions +over the functions from ‘’. + + const char *pgettext (const char *msgctxt, const char *msgid); + + In a call of this macro, MSGCTXT and MSGID must be string literals. +The macro returns the translation of MSGID, restricted to the context +given by MSGCTXT. + + The MSGCTXT string is visible in the PO file to the translator. You +should try to make it somehow canonical and never changing. Because +every time you change an MSGCTXT, the translator will have to review the +translation of MSGID. + + Finding a canonical MSGCTXT string that doesn't change over time can +be hard. But you shouldn't use the file name or class name containing +the ‘pgettext’ call - because it is a common development task to rename +a file or a class, and it shouldn't cause translator work. Also you +shouldn't use a comment in the form of a complete English sentence as +MSGCTXT - because orthography or grammar changes are often applied to +such sentences, and again, it shouldn't force the translator to do a +review. + + The ‘p’ in ‘pgettext’ stands for "particular": ‘pgettext’ fetches a +particular translation of the MSGID. + + const char *dpgettext (const char *domain_name, + const char *msgctxt, const char *msgid); + const char *dcpgettext (const char *domain_name, + const char *msgctxt, const char *msgid, + int category); + + These are generalizations of ‘pgettext’. They behave similarly to +‘dgettext’ and ‘dcgettext’, respectively. The DOMAIN_NAME argument +defines the translation domain. The CATEGORY argument allows to use +another locale category than ‘LC_MESSAGES’. + + As as example consider the following fictional situation. A GUI +program has a menu bar with the following entries: + + +------------+------------+--------------------------------------+ + | File | Printer | | + +------------+------------+--------------------------------------+ + | Open | | Select | + | New | | Open | + +----------+ | Connect | + +----------+ + + To have the strings ‘File’, ‘Printer’, ‘Open’, ‘New’, ‘Select’, and +‘Connect’ translated there has to be at some point in the code a call to +a function of the ‘gettext’ family. But in two places the string passed +into the function would be ‘Open’. The translations might not be the +same and therefore we are in the dilemma described above. + + What distinguishes the two places is the menu path from the menu root +to the particular menu entries: + + Menu|File + Menu|Printer + Menu|File|Open + Menu|File|New + Menu|Printer|Select + Menu|Printer|Open + Menu|Printer|Connect + + The context is thus the menu path without its last part. So, the +calls look like this: + + pgettext ("Menu|", "File") + pgettext ("Menu|", "Printer") + pgettext ("Menu|File|", "Open") + pgettext ("Menu|File|", "New") + pgettext ("Menu|Printer|", "Select") + pgettext ("Menu|Printer|", "Open") + pgettext ("Menu|Printer|", "Connect") + + Whether or not to use the ‘|’ character at the end of the context is +a matter of style. + + For more complex cases, where the MSGCTXT or MSGID are not string +literals, more general macros are available: + + const char *pgettext_expr (const char *msgctxt, const char *msgid); + const char *dpgettext_expr (const char *domain_name, + const char *msgctxt, const char *msgid); + const char *dcpgettext_expr (const char *domain_name, + const char *msgctxt, const char *msgid, + int category); + + Here MSGCTXT and MSGID can be arbitrary string-valued expressions. +These macros are more general. But in the case that both argument +expressions are string literals, the macros without the ‘_expr’ suffix +are more efficient. + + +File: gettext.info, Node: Plural forms, Next: Optimized gettext, Prev: Contexts, Up: gettext + +11.2.6 Additional functions for plural forms +-------------------------------------------- + + The functions of the ‘gettext’ family described so far (and all the +‘catgets’ functions as well) have one problem in the real world which +have been neglected completely in all existing approaches. What is +meant here is the handling of plural forms. + + Looking through Unix source code before the time anybody thought +about internationalization (and, sadly, even afterwards) one can often +find code similar to the following: + + printf ("%d file%s deleted", n, n == 1 ? "" : "s"); + +After the first complaints from people internationalizing the code +people either completely avoided formulations like this or used strings +like ‘"file(s)"’. Both look unnatural and should be avoided. First +tries to solve the problem correctly looked like this: + + if (n == 1) + printf ("%d file deleted", n); + else + printf ("%d files deleted", n); + + But this does not solve the problem. It helps languages where the +plural form of a noun is not simply constructed by adding an 's' but +that is all. Once again people fell into the trap of believing the +rules their language is using are universal. But the handling of plural +forms differs widely between the language families. For example, Rafal +Maszkowski ‘’ reports: + + In Polish we use e.g. plik (file) this way: + 1 plik + 2,3,4 pliki + 5-21 pliko'w + 22-24 pliki + 25-31 pliko'w + and so on (o' means 8859-2 oacute which should be rather okreska, + similar to aogonek). + + There are two things which can differ between languages (and even +inside language families); + + • The form how plural forms are built differs. This is a problem + with languages which have many irregularities. German, for + instance, is a drastic case. Though English and German are part of + the same language family (Germanic), the almost regular forming of + plural noun forms (appending an 's') is hardly found in German. + + • The number of plural forms differ. This is somewhat surprising for + those who only have experiences with Romanic and Germanic languages + since here the number is the same (there are two). + + But other language families have only one form or many forms. More + information on this in an extra section. + + The consequence of this is that application writers should not try to +solve the problem in their code. This would be localization since it is +only usable for certain, hardcoded language environments. Instead the +extended ‘gettext’ interface should be used. + + These extra functions are taking instead of the one key string two +strings and a numerical argument. The idea behind this is that using +the numerical argument and the first string as a key, the implementation +can select using rules specified by the translator the right plural +form. The two string arguments then will be used to provide a return +value in case no message catalog is found (similar to the normal +‘gettext’ behavior). In this case the rules for Germanic language is +used and it is assumed that the first string argument is the singular +form, the second the plural form. + + This has the consequence that programs without language catalogs can +display the correct strings only if the program itself is written using +a Germanic language. This is a limitation but since the GNU C library +(as well as the GNU ‘gettext’ package) are written as part of the GNU +package and the coding standards for the GNU project require program +being written in English, this solution nevertheless fulfills its +purpose. + + -- Function: char * ngettext (const char *MSGID1, const char *MSGID2, + unsigned long int N) + The ‘ngettext’ function is similar to the ‘gettext’ function as it + finds the message catalogs in the same way. But it takes two extra + arguments. The MSGID1 parameter must contain the singular form of + the string to be converted. It is also used as the key for the + search in the catalog. The MSGID2 parameter is the plural form. + The parameter N is used to determine the plural form. If no + message catalog is found MSGID1 is returned if ‘n == 1’, otherwise + ‘msgid2’. + + An example for the use of this function is: + + printf (ngettext ("%d file removed", "%d files removed", n), n); + + Please note that the numeric value N has to be passed to the + ‘printf’ function as well. It is not sufficient to pass it only to + ‘ngettext’. + + In the English singular case, the number - always 1 - can be + replaced with "one": + + printf (ngettext ("One file removed", "%d files removed", n), n); + + This works because the ‘printf’ function discards excess arguments + that are not consumed by the format string. + + If this function is meant to yield a format string that takes two + or more arguments, you can not use it like this: + + printf (ngettext ("%d file removed from directory %s", + "%d files removed from directory %s", + n), + n, dir); + + because in many languages the translators want to replace the ‘%d’ + with an explicit word in the singular case, just like "one" in + English, and C format strings cannot consume the second argument + but skip the first argument. Instead, you have to reorder the + arguments so that ‘n’ comes last: + + printf (ngettext ("%2$d file removed from directory %1$s", + "%2$d files removed from directory %1$s", + n), + dir, n); + + See *note c-format:: for details about this argument reordering + syntax. + + When you know that the value of ‘n’ is within a given range, you + can specify it as a comment directed to the ‘xgettext’ tool. This + information may help translators to use more adequate translations. + Like this: + + if (days > 7 && days < 14) + /* xgettext: range: 1..6 */ + printf (ngettext ("one week and one day", "one week and %d days", + days - 7), + days - 7); + + There is one case where using ‘ngettext’ is *not* appropriate, + however: namely, when neither of the two strings contains a + cardinal number. Consider the following example: + + puts (ngettext ("Delete the selected file?", + "Delete the selected files?", + n)); + The Russian language translator would need to provide separate + translations for the following count forms: + • 1, 21, 31, 41, 51, 61, 71, 81, 91... + • 2-4, 22-24, 32-34, 42-44... + • 5-20, 25-30, 35-40... + As you can see, the case ‘n == 1’ cannot be expressed with the + Russian plural forms. Instead, in this case, you need to use + separate calls to ‘gettext’: + puts (n == 1 ? gettext ("Delete the selected file?") + : gettext ("Delete the selected files?")); + The translator will then use the right grammar constructs for + singular and plural _without_ a number. + + -- Function: char * dngettext (const char *DOMAIN, const char *MSGID1, + const char *MSGID2, unsigned long int N) + The ‘dngettext’ is similar to the ‘dgettext’ function in the way + the message catalog is selected. The difference is that it takes + two extra parameter to provide the correct plural form. These two + parameters are handled in the same way ‘ngettext’ handles them. + + -- Function: char * dcngettext (const char *DOMAIN, const char *MSGID1, + const char *MSGID2, unsigned long int N, int CATEGORY) + The ‘dcngettext’ is similar to the ‘dcgettext’ function in the way + the message catalog is selected. The difference is that it takes + two extra parameter to provide the correct plural form. These two + parameters are handled in the same way ‘ngettext’ handles them. + + Now, how do these functions solve the problem of the plural forms? +Without the input of linguists (which was not available) it was not +possible to determine whether there are only a few different forms in +which plural forms are formed or whether the number can increase with +every new supported language. + + Therefore the solution implemented is to allow the translator to +specify the rules of how to select the plural form. Since the formula +varies with every language this is the only viable solution except for +hardcoding the information in the code (which still would require the +possibility of extensions to not prevent the use of new languages). + + The information about the plural form selection has to be stored in +the header entry of the PO file (the one with the empty ‘msgid’ string). +The plural form information looks like this: + + Plural-Forms: nplurals=2; plural=n == 1 ? 0 : 1; + + The ‘nplurals’ value must be a decimal number which specifies how +many different plural forms exist for this language. The string +following ‘plural’ is an expression which is using the C language +syntax. Exceptions are that no negative numbers are allowed, numbers +must be decimal, and the only variable allowed is ‘n’. Spaces are +allowed in the expression, but backslash-newlines are not; in the +examples below the backslash-newlines are present for formatting +purposes only. This expression will be evaluated whenever one of the +functions ‘ngettext’, ‘dngettext’, or ‘dcngettext’ is called. The +numeric value passed to these functions is then substituted for all uses +of the variable ‘n’ in the expression. The resulting value then must be +greater or equal to zero and smaller than the value given as the value +of ‘nplurals’. + +The following rules are known at this point. The language with families +are listed. But this does not necessarily mean the information can be +generalized for the whole family (as can be easily seen in the table +below).(1) + +Only one form: + Some languages only require one single form. There is no + distinction between the singular and plural form. An appropriate + header entry would look like this: + + Plural-Forms: nplurals=1; plural=0; + + Languages with this property include: + + Asian family + Japanese, Vietnamese, Korean + Tai-Kadai family + Thai + +Two forms, singular used for one only + This is the form used in most existing programs since it is what + English is using. A header entry would look like this: + + Plural-Forms: nplurals=2; plural=n != 1; + + (Note: this uses the feature of C expressions that boolean + expressions have to value zero or one.) + + Languages with this property include: + + Germanic family + English, German, Dutch, Swedish, Danish, Norwegian, Faroese + Romanic family + Spanish, Portuguese, Italian + Latin/Greek family + Greek + Slavic family + Bulgarian + Finno-Ugric family + Finnish, Estonian + Semitic family + Hebrew + Austronesian family + Bahasa Indonesian + Artificial + Esperanto + + Other languages using the same header entry are: + + Finno-Ugric family + Hungarian + Turkic/Altaic family + Turkish + + Hungarian does not appear to have a plural if you look at sentences + involving cardinal numbers. For example, "1 apple" is "1 alma", + and "123 apples" is "123 alma". But when the number is not + explicit, the distinction between singular and plural exists: "the + apple" is "az alma", and "the apples" is "az almák". Since + ‘ngettext’ has to support both types of sentences, it is classified + here, under "two forms". + + The same holds for Turkish: "1 apple" is "1 elma", and "123 apples" + is "123 elma". But when the number is omitted, the distinction + between singular and plural exists: "the apple" is "elma", and "the + apples" is "elmalar". + +Two forms, singular used for zero and one + Exceptional case in the language family. The header entry would + be: + + Plural-Forms: nplurals=2; plural=n>1; + + Languages with this property include: + + Romanic family + Brazilian Portuguese, French + +Three forms, special case for zero + The header entry would be: + + Plural-Forms: nplurals=3; plural=n%10==1 && n%100!=11 ? 0 : n != 0 ? 1 : 2; + + Languages with this property include: + + Baltic family + Latvian + +Three forms, special cases for one and two + The header entry would be: + + Plural-Forms: nplurals=3; plural=n==1 ? 0 : n==2 ? 1 : 2; + + Languages with this property include: + + Celtic + Gaeilge (Irish) + +Three forms, special case for numbers ending in 00 or [2-9][0-9] + The header entry would be: + + Plural-Forms: nplurals=3; \ + plural=n==1 ? 0 : (n==0 || (n%100 > 0 && n%100 < 20)) ? 1 : 2; + + Languages with this property include: + + Romanic family + Romanian + +Three forms, special case for numbers ending in 1[2-9] + The header entry would look like this: + + Plural-Forms: nplurals=3; \ + plural=n%10==1 && n%100!=11 ? 0 : \ + n%10>=2 && (n%100<10 || n%100>=20) ? 1 : 2; + + Languages with this property include: + + Baltic family + Lithuanian + +Three forms, special cases for numbers ending in 1 and 2, 3, 4, except those ending in 1[1-4] + The header entry would look like this: + + Plural-Forms: nplurals=3; \ + plural=n%10==1 && n%100!=11 ? 0 : \ + n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2; + + Languages with this property include: + + Slavic family + Russian, Ukrainian, Belarusian, Serbian, Croatian + +Three forms, special cases for 1 and 2, 3, 4 + The header entry would look like this: + + Plural-Forms: nplurals=3; \ + plural=(n==1) ? 0 : (n>=2 && n<=4) ? 1 : 2; + + Languages with this property include: + + Slavic family + Czech, Slovak + +Three forms, special case for one and some numbers ending in 2, 3, or 4 + The header entry would look like this: + + Plural-Forms: nplurals=3; \ + plural=n==1 ? 0 : \ + n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2; + + Languages with this property include: + + Slavic family + Polish + +Four forms, special case for one and all numbers ending in 02, 03, or 04 + The header entry would look like this: + + Plural-Forms: nplurals=4; \ + plural=n%100==1 ? 0 : n%100==2 ? 1 : n%100==3 || n%100==4 ? 2 : 3; + + Languages with this property include: + + Slavic family + Slovenian + +Six forms, special cases for one, two, all numbers ending in 02, 03, ... 10, all numbers ending in 11 ... 99, and others + The header entry would look like this: + + Plural-Forms: nplurals=6; \ + plural=n==0 ? 0 : n==1 ? 1 : n==2 ? 2 : n%100>=3 && n%100<=10 ? 3 \ + : n%100>=11 ? 4 : 5; + + Languages with this property include: + + Afroasiatic family + Arabic + + You might now ask, ‘ngettext’ handles only numbers N of type +‘unsigned long’. What about larger integer types? What about negative +numbers? What about floating-point numbers? + + About larger integer types, such as ‘uintmax_t’ or ‘unsigned long +long’: they can be handled by reducing the value to a range that fits in +an ‘unsigned long’. Simply casting the value to ‘unsigned long’ would +not do the right thing, since it would treat ‘ULONG_MAX + 1’ like zero, +‘ULONG_MAX + 2’ like singular, and the like. Here you can exploit the +fact that all mentioned plural form formulas eventually become periodic, +with a period that is a divisor of 100 (or 1000 or 1000000). So, when +you reduce a large value to another one in the range [1000000, 1999999] +that ends in the same 6 decimal digits, you can assume that it will lead +to the same plural form selection. This code does this: + + #include + uintmax_t nbytes = ...; + printf (ngettext ("The file has %"PRIuMAX" byte.", + "The file has %"PRIuMAX" bytes.", + (nbytes > ULONG_MAX + ? (nbytes % 1000000) + 1000000 + : nbytes)), + nbytes); + + Negative and floating-point values usually represent physical +entities for which singular and plural don't clearly apply. In such +cases, there is no need to use ‘ngettext’; a simple ‘gettext’ call with +a form suitable for all values will do. For example: + + printf (gettext ("Time elapsed: %.3f seconds"), + num_milliseconds * 0.001); + +Even if NUM_MILLISECONDS happens to be a multiple of 1000, the output + Time elapsed: 1.000 seconds +is acceptable in English, and similarly for other languages. + + The translators' perspective regarding plural forms is explained in +*note Translating plural forms::. + + ---------- Footnotes ---------- + + (1) Additions are welcome. Send appropriate information to + and . The Unicode CLDR +Project () provides a comprehensive set of +plural forms in a different format. The ‘msginit’ program has +preliminary support for the format so you can use it as a baseline +(*note msginit Invocation::). + + +File: gettext.info, Node: Optimized gettext, Prev: Plural forms, Up: gettext + +11.2.7 Optimization of the *gettext functions +--------------------------------------------- + + At this point of the discussion we should talk about an advantage of +the GNU ‘gettext’ implementation. Some readers might have pointed out +that an internationalized program might have a poor performance if some +string has to be translated in an inner loop. While this is unavoidable +when the string varies from one run of the loop to the other it is +simply a waste of time when the string is always the same. Take the +following example: + + { + while (...) + { + puts (gettext ("Hello world")); + } + } + +When the locale selection does not change between two runs the resulting +string is always the same. One way to use this is: + + { + str = gettext ("Hello world"); + while (...) + { + puts (str); + } + } + +But this solution is not usable in all situation (e.g. when the locale +selection changes) nor does it lead to legible code. + + For this reason, GNU ‘gettext’ caches previous translation results. +When the same translation is requested twice, with no new message +catalogs being loaded in between, ‘gettext’ will, the second time, find +the result through a single cache lookup. + + +File: gettext.info, Node: Comparison, Next: Using libintl.a, Prev: gettext, Up: Programmers + +11.3 Comparing the Two Interfaces +================================= + + The following discussion is perhaps a little bit colored. As said +above we implemented GNU ‘gettext’ following the Uniforum proposal and +this surely has its reasons. But it should show how we came to this +decision. + + First we take a look at the developing process. When we write an +application using NLS provided by ‘gettext’ we proceed as always. Only +when we come to a string which might be seen by the users and thus has +to be translated we use ‘gettext("...")’ instead of ‘"..."’. At the +beginning of each source file (or in a central header file) we define + + #define gettext(String) (String) + + Even this definition can be avoided when the system supports the +‘gettext’ function in its C library. When we compile this code the +result is the same as if no NLS code is used. When you take a look at +the GNU ‘gettext’ code you will see that we use ‘_("...")’ instead of +‘gettext("...")’. This reduces the number of additional characters per +translatable string to _3_ (in words: three). + + When now a production version of the program is needed we simply +replace the definition + + #define _(String) (String) + +by + + #include + #define _(String) gettext (String) + +Additionally we run the program ‘xgettext’ on all source code file which +contain translatable strings and that's it: we have a running program +which does not depend on translations to be available, but which can use +any that becomes available. + + The same procedure can be done for the ‘gettext_noop’ invocations +(*note Special cases::). One usually defines ‘gettext_noop’ as a no-op +macro. So you should consider the following code for your project: + + #define gettext_noop(String) String + #define N_(String) gettext_noop (String) + + ‘N_’ is a short form similar to ‘_’. The ‘Makefile’ in the ‘po/’ +directory of GNU ‘gettext’ knows by default both of the mentioned short +forms so you are invited to follow this proposal for your own ease. + + Now to ‘catgets’. The main problem is the work for the programmer. +Every time he comes to a translatable string he has to define a number +(or a symbolic constant) which has also be defined in the message +catalog file. He also has to take care for duplicate entries, duplicate +message IDs etc. If he wants to have the same quality in the message +catalog as the GNU ‘gettext’ program provides he also has to put the +descriptive comments for the strings and the location in all source code +files in the message catalog. This is nearly a Mission: Impossible. + + But there are also some points people might call advantages speaking +for ‘catgets’. If you have a single word in a string and this string is +used in different contexts it is likely that in one or the other +language the word has different translations. Example: + + printf ("%s: %d", gettext ("number"), number_of_errors) + + printf ("you should see %d %s", number_count, + number_count == 1 ? gettext ("number") : gettext ("numbers")) + + Here we have to translate two times the string ‘"number"’. Even if +you do not speak a language beside English it might be possible to +recognize that the two words have a different meaning. In German the +first appearance has to be translated to ‘"Anzahl"’ and the second to +‘"Zahl"’. + + Now you can say that this example is really esoteric. And you are +right! This is exactly how we felt about this problem and decide that +it does not weight that much. The solution for the above problem could +be very easy: + + printf ("%s %d", gettext ("number:"), number_of_errors) + + printf (number_count == 1 ? gettext ("you should see %d number") + : gettext ("you should see %d numbers"), + number_count) + + We believe that we can solve all conflicts with this method. If it +is difficult one can also consider changing one of the conflicting +string a little bit. But it is not impossible to overcome. + + ‘catgets’ allows same original entry to have different translations, +but ‘gettext’ has another, scalable approach for solving ambiguities of +this kind: *Note Ambiguities::. + + +File: gettext.info, Node: Using libintl.a, Next: gettext grok, Prev: Comparison, Up: Programmers + +11.4 Using libintl.a in own programs +==================================== + + Starting with version 0.9.4 the library ‘libintl.h’ should be +self-contained. I.e., you can use it in your own programs without +providing additional functions. The ‘Makefile’ will put the header and +the library in directories selected using the ‘$(prefix)’. + + +File: gettext.info, Node: gettext grok, Next: Temp Programmers, Prev: Using libintl.a, Up: Programmers + +11.5 Being a ‘gettext’ grok +=========================== + + * NOTE: * This documentation section is outdated and needs to be +revised. + + To fully exploit the functionality of the GNU ‘gettext’ library it is +surely helpful to read the source code. But for those who don't want to +spend that much time in reading the (sometimes complicated) code here is +a list comments: + + • Changing the language at runtime + + For interactive programs it might be useful to offer a selection of + the used language at runtime. To understand how to do this one + need to know how the used language is determined while executing + the ‘gettext’ function. The method which is presented here only + works correctly with the GNU implementation of the ‘gettext’ + functions. + + In the function ‘dcgettext’ at every call the current setting of + the highest priority environment variable is determined and used. + Highest priority means here the following list with decreasing + priority: + + 1. ‘LANGUAGE’ + 2. ‘LC_ALL’ + 3. ‘LC_xxx’, according to selected locale category + 4. ‘LANG’ + + Afterwards the path is constructed using the found value and the + translation file is loaded if available. + + What happens now when the value for, say, ‘LANGUAGE’ changes? + According to the process explained above the new value of this + variable is found as soon as the ‘dcgettext’ function is called. + But this also means the (perhaps) different message catalog file is + loaded. In other words: the used language is changed. + + But there is one little hook. The code for gcc-2.7.0 and up + provides some optimization. This optimization normally prevents + the calling of the ‘dcgettext’ function as long as no new catalog + is loaded. But if ‘dcgettext’ is not called the program also + cannot find the ‘LANGUAGE’ variable be changed (*note Optimized + gettext::). A solution for this is very easy. Include the + following code in the language switching function. + + /* Change language. */ + setenv ("LANGUAGE", "fr", 1); + + /* Make change known. */ + { + extern int _nl_msg_cat_cntr; + ++_nl_msg_cat_cntr; + } + + The variable ‘_nl_msg_cat_cntr’ is defined in ‘loadmsgcat.c’. You + don't need to know what this is for. But it can be used to detect + whether a ‘gettext’ implementation is GNU gettext and not non-GNU + system's native gettext implementation. + + +File: gettext.info, Node: Temp Programmers, Prev: gettext grok, Up: Programmers + +11.6 Temporary Notes for the Programmers Chapter +================================================ + + * NOTE: * This documentation section is outdated and needs to be +revised. + +* Menu: + +* Temp Implementations:: Temporary - Two Possible Implementations +* Temp catgets:: Temporary - About ‘catgets’ +* Temp WSI:: Temporary - Why a single implementation +* Temp Notes:: Temporary - Notes + + +File: gettext.info, Node: Temp Implementations, Next: Temp catgets, Up: Temp Programmers + +11.6.1 Temporary - Two Possible Implementations +----------------------------------------------- + + There are two competing methods for language independent messages: +the X/Open ‘catgets’ method, and the Uniforum ‘gettext’ method. The +‘catgets’ method indexes messages by integers; the ‘gettext’ method +indexes them by their English translations. The ‘catgets’ method has +been around longer and is supported by more vendors. The ‘gettext’ +method is supported by Sun, and it has been heard that the COSE +multi-vendor initiative is supporting it. Neither method is a POSIX +standard; the POSIX.1 committee had a lot of disagreement in this area. + + Neither one is in the POSIX standard. There was much disagreement in +the POSIX.1 committee about using the ‘gettext’ routines vs. ‘catgets’ +(XPG). In the end the committee couldn't agree on anything, so no +messaging system was included as part of the standard. I believe the +informative annex of the standard includes the XPG3 messaging +interfaces, "...as an example of a messaging system that has been +implemented..." + + They were very careful not to say anywhere that you should use one +set of interfaces over the other. For more on this topic please see the +Programming for Internationalization FAQ. + + +File: gettext.info, Node: Temp catgets, Next: Temp WSI, Prev: Temp Implementations, Up: Temp Programmers + +11.6.2 Temporary - About ‘catgets’ +---------------------------------- + + There have been a few discussions of late on the use of ‘catgets’ as +a base. I think it important to present both sides of the argument and +hence am opting to play devil's advocate for a little bit. + + I'll not deny the fact that ‘catgets’ could have been designed a lot +better. It currently has quite a number of limitations and these have +already been pointed out. + + However there is a great deal to be said for consistency and +standardization. A common recurring problem when writing Unix software +is the myriad portability problems across Unix platforms. It seems as +if every Unix vendor had a look at the operating system and found parts +they could improve upon. Undoubtedly, these modifications are probably +innovative and solve real problems. However, software developers have a +hard time keeping up with all these changes across so many platforms. + + And this has prompted the Unix vendors to begin to standardize their +systems. Hence the impetus for Spec1170. Every major Unix vendor has +committed to supporting this standard and every Unix software developer +waits with glee the day they can write software to this standard and +simply recompile (without having to use autoconf) across different +platforms. + + As I understand it, Spec1170 is roughly based upon version 4 of the +X/Open Portability Guidelines (XPG4). Because ‘catgets’ and friends are +defined in XPG4, I'm led to believe that ‘catgets’ is a part of Spec1170 +and hence will become a standardized component of all Unix systems. + + +File: gettext.info, Node: Temp WSI, Next: Temp Notes, Prev: Temp catgets, Up: Temp Programmers + +11.6.3 Temporary - Why a single implementation +---------------------------------------------- + + Now it seems kind of wasteful to me to have two different systems +installed for accessing message catalogs. If we do want to remedy +‘catgets’ deficiencies why don't we try to expand ‘catgets’ (in a +compatible manner) rather than implement an entirely new system. +Otherwise, we'll end up with two message catalog access systems +installed with an operating system - one set of routines for packages +using GNU ‘gettext’ for their internationalization, and another set of +routines (catgets) for all other software. Bloated? + + Supposing another catalog access system is implemented. Which do we +recommend? At least for Linux, we need to attract as many software +developers as possible. Hence we need to make it as easy for them to +port their software as possible. Which means supporting ‘catgets’. We +will be implementing the ‘libintl’ code within our ‘libc’, but does this +mean we also have to incorporate another message catalog access scheme +within our ‘libc’ as well? And what about people who are going to be +using the ‘libintl’ + non-‘catgets’ routines. When they port their +software to other platforms, they're now going to have to include the +front-end (‘libintl’) code plus the back-end code (the non-‘catgets’ +access routines) with their software instead of just including the +‘libintl’ code with their software. + + Message catalog support is however only the tip of the iceberg. What +about the data for the other locale categories? They also have a number +of deficiencies. Are we going to abandon them as well and develop +another duplicate set of routines (should ‘libintl’ expand beyond +message catalog support)? + + Like many parts of Unix that can be improved upon, we're stuck with +balancing compatibility with the past with useful improvements and +innovations for the future. + + +File: gettext.info, Node: Temp Notes, Prev: Temp WSI, Up: Temp Programmers + +11.6.4 Temporary - Notes +------------------------ + + X/Open agreed very late on the standard form so that many +implementations differ from the final form. Both of my system (old +Linux catgets and Ultrix-4) have a strange variation. + + OK. After incorporating the last changes I have to spend some time on +making the GNU/Linux ‘libc’ ‘gettext’ functions. So in future Solaris +is not the only system having ‘gettext’. + + +File: gettext.info, Node: Translators, Next: Maintainers, Prev: Programmers, Up: Top + +12 The Translator's View +************************ + +* Menu: + +* Organization:: Organization +* Responsibilities:: Responsibilities in the Translation Project +* Dialects:: Language dialects +* Translating plural forms:: How to fill in ‘msgstr[0]’, ‘msgstr[1]’ +* Prioritizing messages:: How to find which messages to translate first + + +File: gettext.info, Node: Organization, Next: Responsibilities, Up: Translators + +12.1 Organization +================= + + For some software packages, each translator works on her own and +communicates directly with the developers of the package. For some +other software packages, on the other hand, translators are organized +into _translation projects_ and _translation teams_. + + A _translation project_ applies to a group of software packages and +shares procedures and methodologies regarding the translation. + + There are currently three major translation projects: + + • The "Translation Project", which is used by all kinds of Free + Software packages, but in particular by GNU packages. It has its + home at . + + • The "KDE Localization Project", which is used by KDE packages. It + is at . + + • The "GNOME Localization Project", which is used by GNOME packages. + It is at . + + A _translation team_ is a group of translators for a single language, +in the scope of a translation project. + + +File: gettext.info, Node: Responsibilities, Next: Dialects, Prev: Organization, Up: Translators + +12.2 Responsibilities in the Translation Project +================================================ + + The following rules and habits apply to the Translation Project. + + The translator's responsibilities are: + • She submits a translations disclaimer to the Free Software + Foundation (once only, and only when she wants to translate a + package that requires a disclaimer). + + A disclaimer is a legal document that allows the software package + to distribute her translation work. It is not as strong as a + copyright assignment. Merely, it says that the signer will never + make use of the copyright on her translations: will never forbid + copying them, and will never ask for some kind of compensation. + This guarantees that the FSF (and everyone else) will always be + allowed to freely distribute these translations. The FSF wishes to + have this guarantee in a legally binding manner, to be on the safe + side. + + There are two ways to submit the disclaimer: Either online through + this form on the FSF's web site, or by printing, signing, and + submitting the file ‘disclaim-translations.txt’ found in the GNU + gettext distribution. + + • Agree with the other translators of the same team who is "in + charge" for the translations of a particular package. + + The Translation Project has a coordinator. He can be reached at +‘coordinator@translationproject.org’. His responsibilities are: + • He maintains the web site . + • When he receives a release or prerelease announcement from one of + the software package maintainers, he extracts the POT file(s) and + sends notifications to all translation teams about it. + + The responsibilities of the package maintainers are: + • To incorporate the translations in the software package before a + release. + • To forward bug reports about the translations to the respective + translation team. A developer or maintainer should never apply a + translation fix himself, because that would cause conflicts with + the translation team. + + +File: gettext.info, Node: Dialects, Next: Translating plural forms, Prev: Responsibilities, Up: Translators + +12.3 Language dialects +====================== + + For many languages, a translation into the main dialect is +intelligible by all speakers of the language. Speakers of another +dialect can have a separate translation if they wish so. In fact, since +the fallback mechanism implemented in GNU libc and GNU libintl applies +on a per-message basis, the message catalog for the dialect needs only +to contain the translations that differ from those in the main language. + + For example, French speakers in Canada (that is, users in the locale +‘fr_CA’) can use and do accept translations produced by French speakers +in France (typical file name: ‘fr.po’). Nevertheless, the translation +system with PO files enables them to produce special message catalogs +(file name: ‘fr_CA.po’) that will take priority over ‘fr.po’ for users +in that locale. Similarly for users in Austria, where message catalogs +‘de_AT.po’ take priority over the catalogs named ‘de.po’ that reflect +German as spoken in Germany. + + The situation is different for Chinese, though: Since users in the +People's Republic of China and in Singapore want translations with +Simplified Chinese characters, whereas Chinese users in other +territories (such as Taiwan, Hong Kong, and Macao) want translations +with Traditional Chinese characters, no translator should ever submit a +file named ‘zh.po’. Instead, there will typically be two separate +translation teams: a team that produces translations with Simplified +Chinese characters (file name ‘zh_CN.po’) and a team that produces +translations with Traditional Chinese characters (file name ‘zh_TW.po’). + + +File: gettext.info, Node: Translating plural forms, Next: Prioritizing messages, Prev: Dialects, Up: Translators + +12.4 Translating plural forms +============================= + + Suppose you are translating a PO file, and it contains an entry like +this: + + #, c-format + msgid "One file removed" + msgid_plural "%d files removed" + msgstr[0] "" + msgstr[1] "" + +What does this mean? How do you fill it in? + + Such an entry denotes a message with plural forms, that is, a message +where the text depends on a cardinal number. The general form of the +message, in English, is the ‘msgid_plural’ line. The ‘msgid’ line is +the English singular form, that is, the form for when the number is +equal to 1. More details about plural forms are explained in *note +Plural forms::. + + The first thing you need to look at is the ‘Plural-Forms’ line in the +header entry of the PO file. It contains the number of plural forms and +a formula. If the PO file does not yet have such a line, you have to +add it. It only depends on the language into which you are translating. +You can get this info by using the ‘msginit’ command (see *note +Creating::) - it contains a database of known plural formulas - or by +asking other members of your translation team. + + Suppose the line looks as follows: + + "Plural-Forms: nplurals=3; plural=n%10==1 && n%100!=11 ? 0 : n%10>=2 && n" + "%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2;\n" + + It's logically one line; recall that the PO file formatting is +allowed to break long lines so that each physical line fits in 80 +monospaced columns. + + The value of ‘nplurals’ here tells you that there are three plural +forms. The first thing you need to do is to ensure that the entry +contains an ‘msgstr’ line for each of the forms: + + #, c-format + msgid "One file removed" + msgid_plural "%d files removed" + msgstr[0] "" + msgstr[1] "" + msgstr[2] "" + + Then translate the ‘msgid_plural’ line and fill it in into each +‘msgstr’ line: + + #, c-format + msgid "One file removed" + msgid_plural "%d files removed" + msgstr[0] "%d slika uklonjenih" + msgstr[1] "%d slika uklonjenih" + msgstr[2] "%d slika uklonjenih" + + Now you can refine the translation so that it matches the plural +form. According to the formula above, ‘msgstr[0]’ is used when the +number ends in 1 but does not end in 11; ‘msgstr[1]’ is used when the +number ends in 2, 3, 4, but not in 12, 13, 14; and ‘msgstr[2]’ is used +in all other cases. With this knowledge, you can refine the +translations: + + #, c-format + msgid "One file removed" + msgid_plural "%d files removed" + msgstr[0] "%d slika je uklonjena" + msgstr[1] "%d datoteke uklonjenih" + msgstr[2] "%d slika uklonjenih" + + You noticed that in the English singular form (‘msgid’) the number +placeholder could be omitted and replaced by the numeral word "one". +Can you do this in your translation as well? + + msgstr[0] "jednom datotekom je uklonjen" + +Well, it depends on whether ‘msgstr[0]’ applies only to the number 1, or +to other numbers as well. If, according to the plural formula, +‘msgstr[0]’ applies only to ‘n == 1’, then you can use the specialized +translation without the number placeholder. In our case, however, +‘msgstr[0]’ also applies to the numbers 21, 31, 41, etc., and therefore +you cannot omit the placeholder. + + +File: gettext.info, Node: Prioritizing messages, Prev: Translating plural forms, Up: Translators + +12.5 Prioritizing messages: How to determine which messages to translate first +============================================================================== + + A translator sometimes has only a limited amount of time per week to +spend on a package, and some packages have quite large message catalogs +(over 1000 messages). Therefore she wishes to translate the messages +first that are the most visible to the user, or that occur most +frequently. This section describes how to determine these "most urgent" +messages. It also applies to determine the "next most urgent" messages +after the message catalog has already been partially translated. + + In a first step, she uses the programs like a user would do. While +she does this, the GNU ‘gettext’ library logs into a file the not yet +translated messages for which a translation was requested from the +program. + + In a second step, she uses the PO mode to translate precisely this +set of messages. + + Here are more details. The GNU ‘libintl’ library (but not the +corresponding functions in GNU ‘libc’) supports an environment variable +‘GETTEXT_LOG_UNTRANSLATED’. The GNU ‘libintl’ library will log into +this file the messages for which ‘gettext()’ and related functions +couldn't find the translation. If the file doesn't exist, it will be +created as needed. On systems with GNU ‘libc’ a shared library +‘preloadable_libintl.so’ is provided that can be used with the ELF +‘LD_PRELOAD’ mechanism. + + So, in the first step, the translator uses these commands on systems +with GNU ‘libc’: + + $ LD_PRELOAD=/usr/local/lib/preloadable_libintl.so + $ export LD_PRELOAD + $ GETTEXT_LOG_UNTRANSLATED=$HOME/gettextlogused + $ export GETTEXT_LOG_UNTRANSLATED + +and these commands on other systems: + + $ GETTEXT_LOG_UNTRANSLATED=$HOME/gettextlogused + $ export GETTEXT_LOG_UNTRANSLATED + + Then she uses and peruses the programs. (It is a good and +recommended practice to use the programs for which you provide +translations: it gives you the needed context.) When done, she removes +the environment variables: + + $ unset LD_PRELOAD + $ unset GETTEXT_LOG_UNTRANSLATED + + The second step starts with removing duplicates: + + $ msguniq $HOME/gettextlogused > missing.po + + The result is a PO file, but needs some preprocessing before a PO +file editor can be used with it. First, it is a multi-domain PO file, +containing messages from many translation domains. Second, it lacks all +translator comments and source references. Here is how to get a list of +the affected translation domains: + + $ sed -n -e 's,^domain "\(.*\)"$,\1,p' < missing.po | sort | uniq + + Then the translator can handle the domains one by one. For +simplicity, let's use environment variables to denote the language, +domain and source package. + + $ lang=nl # your language + $ domain=coreutils # the name of the domain to be handled + $ package=/usr/src/gnu/coreutils-4.5.4 # the package where it comes from + + She takes the latest copy of ‘$lang.po’ from the Translation Project, +or from the package (in most cases, ‘$package/po/$lang.po’), or creates +a fresh one if she's the first translator (see *note Creating::). She +then uses the following commands to mark the not urgent messages as +"obsolete". (This doesn't mean that these messages - translated and +untranslated ones - will go away. It simply means that the PO file +editor will ignore them in the following editing session.) + + $ msggrep --domain=$domain missing.po | grep -v '^domain' \ + > $domain-missing.po + $ msgattrib --set-obsolete --ignore-file $domain-missing.po $domain.$lang.po \ + > $domain.$lang-urgent.po + + Then she translates ‘$domain.$lang-urgent.po’ by use of a PO file +editor (*note Editing::). (FIXME: I don't know whether ‘Lokalize’ and +‘gtranslator’ also preserve obsolete messages, as they should.) Finally +she restores the not urgent messages (with their earlier translations, +for those which were already translated) through this command: + + $ msgmerge --no-fuzzy-matching $domain.$lang-urgent.po $package/po/$domain.pot \ + > $domain.$lang.po + + Then she can submit ‘$domain.$lang.po’ and proceed to the next +domain. + + +File: gettext.info, Node: Maintainers, Next: Installers, Prev: Translators, Up: Top + +13 The Maintainer's View +************************ + + The maintainer of a package has many responsibilities. One of them +is ensuring that the package will install easily on many platforms, and +that the magic we described earlier (*note Users::) will work for +installers and end users. + + Of course, there are many possible ways by which GNU ‘gettext’ might +be integrated in a distribution, and this chapter does not cover them in +all generality. Instead, it details one possible approach which is +especially adequate for many free software distributions following GNU +standards, or even better, Gnits standards, because GNU ‘gettext’ is +purposely for helping the internationalization of the whole GNU project, +and as many other good free packages as possible. So, the maintainer's +view presented here presumes that the package already has a +‘configure.ac’ file and uses GNU Autoconf. + + Nevertheless, GNU ‘gettext’ may surely be useful for free packages +not following GNU standards and conventions, but the maintainers of such +packages might have to show imagination and initiative in organizing +their distributions so ‘gettext’ work for them in all situations. There +are surely many, out there. + + Even if ‘gettext’ methods are now stabilizing, slight adjustments +might be needed between successive ‘gettext’ versions, so you should +ideally revise this chapter in subsequent releases, looking for changes. + +* Menu: + +* Flat and Non-Flat:: Flat or Non-Flat Directory Structures +* Prerequisites:: Prerequisite Works +* gettextize Invocation:: Invoking the ‘gettextize’ Program +* Adjusting Files:: Files You Must Create or Alter +* autoconf macros:: Autoconf macros for use in ‘configure.ac’ +* Version Control Issues:: +* Release Management:: Creating a Distribution Tarball + + +File: gettext.info, Node: Flat and Non-Flat, Next: Prerequisites, Up: Maintainers + +13.1 Flat or Non-Flat Directory Structures +========================================== + + Some free software packages are distributed as ‘tar’ files which +unpack in a single directory, these are said to be “flat” distributions. +Other free software packages have a one level hierarchy of +subdirectories, using for example a subdirectory named ‘doc/’ for the +Texinfo manual and man pages, another called ‘lib/’ for holding +functions meant to replace or complement C libraries, and a subdirectory +‘src/’ for holding the proper sources for the package. These other +distributions are said to be “non-flat”. + + We cannot say much about flat distributions. A flat directory +structure has the disadvantage of increasing the difficulty of updating +to a new version of GNU ‘gettext’. Also, if you have many PO files, +this could somewhat pollute your single directory. Also, GNU +‘gettext’'s libintl sources consist of C sources, shell scripts, ‘sed’ +scripts and complicated Makefile rules, which don't fit well into an +existing flat structure. For these reasons, we recommend to use +non-flat approach in this case as well. + + Maybe because GNU ‘gettext’ itself has a non-flat structure, we have +more experience with this approach, and this is what will be described +in the remaining of this chapter. Some maintainers might use this as an +opportunity to unflatten their package structure. + + +File: gettext.info, Node: Prerequisites, Next: gettextize Invocation, Prev: Flat and Non-Flat, Up: Maintainers + +13.2 Prerequisite Works +======================= + + There are some works which are required for using GNU ‘gettext’ in +one of your package. These works have some kind of generality that +escape the point by point descriptions used in the remainder of this +chapter. So, we describe them here. + + • Before attempting to use ‘gettextize’ you should install some other + packages first. Ensure that recent versions of GNU ‘m4’, GNU + Autoconf and GNU ‘gettext’ are already installed at your site, and + if not, proceed to do this first. If you get to install these + things, beware that GNU ‘m4’ must be fully installed before GNU + Autoconf is even _configured_. + + To further ease the task of a package maintainer the ‘automake’ + package was designed and implemented. GNU ‘gettext’ now uses this + tool and the ‘Makefile’ in the ‘po/’ directory therefore knows + about all the goals necessary for using ‘automake’. + + Those four packages are only needed by you, as a maintainer; the + installers of your own package and end users do not really need any + of GNU ‘m4’, GNU Autoconf, GNU ‘gettext’, or GNU ‘automake’ for + successfully installing and running your package, with messages + properly translated. But this is not completely true if you + provide internationalized shell scripts within your own package: + GNU ‘gettext’ shall then be installed at the user site if the end + users want to see the translation of shell script messages. + + • Your package should use Autoconf and have a ‘configure.ac’ or + ‘configure.in’ file. If it does not, you have to learn how. The + Autoconf documentation is quite well written, it is a good idea + that you print it and get familiar with it. + + • Your C sources should have already been modified according to + instructions given earlier in this manual. *Note Sources::. + + • Your ‘po/’ directory should receive all PO files submitted to you + by the translator teams, each having ‘LL.po’ as a name. This is + not usually easy to get translation work done before your package + gets internationalized and available! Since the cycle has to start + somewhere, the easiest for the maintainer is to start with + absolutely no PO files, and wait until various translator teams get + interested in your package, and submit PO files. + + It is worth adding here a few words about how the maintainer should +ideally behave with PO files submissions. As a maintainer, your role is +to authenticate the origin of the submission as being the representative +of the appropriate translating teams of the Translation Project (forward +the submission to ‘coordinator@translationproject.org’ in case of +doubt), to ensure that the PO file format is not severely broken and +does not prevent successful installation, and for the rest, to merely +put these PO files in ‘po/’ for distribution. + + As a maintainer, you do not have to take on your shoulders the +responsibility of checking if the translations are adequate or complete, +and should avoid diving into linguistic matters. Translation teams +drive themselves and are fully responsible of their linguistic choices +for the Translation Project. Keep in mind that translator teams are +_not_ driven by maintainers. You can help by carefully redirecting all +communications and reports from users about linguistic matters to the +appropriate translation team, or explain users how to reach or join +their team. + + Maintainers should _never ever_ apply PO file bug reports themselves, +short-cutting translation teams. If some translator has difficulty to +get some of her points through her team, it should not be an option for +her to directly negotiate translations with maintainers. Teams ought to +settle their problems themselves, if any. If you, as a maintainer, ever +think there is a real problem with a team, please never try to _solve_ a +team's problem on your own. + + +File: gettext.info, Node: gettextize Invocation, Next: Adjusting Files, Prev: Prerequisites, Up: Maintainers + +13.3 Invoking the ‘gettextize’ Program +====================================== + + The ‘gettextize’ program is an interactive tool that helps the +maintainer of a package internationalized through GNU ‘gettext’. It is +used for two purposes: + + • As a wizard, when a package is modified to use GNU ‘gettext’ for + the first time. + + • As a migration tool, for upgrading the GNU ‘gettext’ support in a + package from a previous to a newer version of GNU ‘gettext’. + + This program performs the following tasks: + + • It copies into the package some files that are consistently and + identically needed in every package internationalized through GNU + ‘gettext’. + + • It performs as many of the tasks mentioned in the next section + *note Adjusting Files:: as can be performed automatically. + + • It removes obsolete files and idioms used for previous GNU + ‘gettext’ versions to the form recommended for the current GNU + ‘gettext’ version. + + • It prints a summary of the tasks that ought to be done manually and + could not be done automatically by ‘gettextize’. + + It can be invoked as follows: + + gettextize [ OPTION... ] [ DIRECTORY ] + +and accepts the following options: + +‘-f’ +‘--force’ + Force replacement of files which already exist. + +‘--po-dir=DIR’ + Specify a directory containing PO files. Such a directory contains + the translations into various languages of a particular POT file. + This option can be specified multiple times, once for each + translation domain. If it is not specified, the directory named + ‘po/’ is updated. + +‘--no-changelog’ + Don't update or create ChangeLog files. By default, ‘gettextize’ + logs all changes (file additions, modifications and removals) in a + file called ‘ChangeLog’ in each affected directory. + +‘--symlink’ + Make symbolic links instead of copying the needed files. This can + be useful to save a few kilobytes of disk space, but it requires + extra effort to create self-contained tarballs, it may disturb some + mechanism the maintainer applies to the sources, and it is likely + to introduce bugs when a newer version of ‘gettext’ is installed on + the system. + +‘-n’ +‘--dry-run’ + Print modifications but don't perform them. All actions that + ‘gettextize’ would normally execute are inhibited and instead only + listed on standard output. + +‘--help’ + Display this help and exit. + +‘--version’ + Output version information and exit. + + If DIRECTORY is given, this is the top level directory of a package +to prepare for using GNU ‘gettext’. If not given, it is assumed that +the current directory is the top level directory of such a package. + + The program ‘gettextize’ provides the following files. However, no +existing file will be replaced unless the option ‘--force’ (‘-f’) is +specified. + + 1. The ‘ABOUT-NLS’ file is copied in the main directory of your + package, the one being at the top level. This file contains a + reference to the GNU gettext documentation. It also avoids an + error from Automake in packages that use the Automake option + ‘gnits’: "error: required file './ABOUT-NLS' not found". + + 2. A ‘po/’ directory is created for eventually holding all translation + files, but initially only containing the file ‘po/Makefile.in.in’ + from the GNU ‘gettext’ distribution (beware the double ‘.in’ in the + file name) and a few auxiliary files. If the ‘po/’ directory + already exists, it will be preserved along with the files it + contains, and only ‘Makefile.in.in’ and the auxiliary files will be + overwritten. + + If ‘--po-dir’ has been specified, this holds for every directory + specified through ‘--po-dir’, instead of ‘po/’. + + 3. The file ‘config.rpath’ is copied into the directory containing + configuration support files. It is needed by the ‘AM_GNU_GETTEXT’ + autoconf macro. + + 4. Only if the project is using GNU ‘automake’: A set of ‘autoconf’ + macro files is copied into the package's ‘autoconf’ macro + repository, usually in a directory called ‘m4/’. + + If your site support symbolic links, ‘gettextize’ will not actually +copy the files into your package, but establish symbolic links instead. +This avoids duplicating the disk space needed in all packages. Merely +using the ‘-h’ option while creating the ‘tar’ archive of your +distribution will resolve each link by an actual copy in the +distribution archive. So, to insist, you really should use ‘-h’ option +with ‘tar’ within your ‘dist’ goal of your main ‘Makefile.in’. + + Furthermore, ‘gettextize’ will update all ‘Makefile.am’ files in each +affected directory, as well as the top level ‘configure.ac’ or +‘configure.in’ file. + + It is interesting to understand that most new files for supporting +GNU ‘gettext’ facilities in one package go in ‘po/’ and ‘m4/’ +subdirectories. Still, these directories will mostly contain package +dependent files. + + The ‘gettextize’ program makes backup files for all files it replaces +or changes, and also write ChangeLog entries about these changes. This +way, the careful maintainer can check after running ‘gettextize’ whether +its changes are acceptable to him, and possibly adjust them. An +exception to this rule is the ‘intl/’ directory, which is removed as a +whole if it still existed. + + It is important to understand that ‘gettextize’ can not do the entire +job of adapting a package for using GNU ‘gettext’. The amount of +remaining work depends on whether the package uses GNU ‘automake’ or +not. But in any case, the maintainer should still read the section +*note Adjusting Files:: after invoking ‘gettextize’. + + In particular, if after using ‘gettexize’, you get an error +‘AC_COMPILE_IFELSE was called before AC_GNU_SOURCE’ or ‘AC_RUN_IFELSE +was called before AC_GNU_SOURCE’, you can fix it by modifying +‘configure.ac’, as described in *note configure.ac::. + + It is also important to understand that ‘gettextize’ is not part of +the GNU build system, in the sense that it should not be invoked +automatically, and not be invoked by someone who doesn't assume the +responsibilities of a package maintainer. For the latter purpose, a +separate tool is provided, see *note autopoint Invocation::. + + +File: gettext.info, Node: Adjusting Files, Next: autoconf macros, Prev: gettextize Invocation, Up: Maintainers + +13.4 Files You Must Create or Alter +=================================== + + Besides files which are automatically added through ‘gettextize’, +there are many files needing revision for properly interacting with GNU +‘gettext’. If you are closely following GNU standards for Makefile +engineering and auto-configuration, the adaptations should be easier to +achieve. Here is a point by point description of the changes needed in +each. + + So, here comes a list of files, each one followed by a description of +all alterations it needs. Many examples are taken out from the GNU +‘gettext’ 0.25.1 distribution itself, or from the GNU ‘hello’ +distribution (). You may indeed +refer to the source code of the GNU ‘gettext’ and GNU ‘hello’ packages, +as they are intended to be good examples for using GNU gettext +functionality. + +* Menu: + +* po/POTFILES.in:: ‘POTFILES.in’ in ‘po/’ +* po/LINGUAS:: ‘LINGUAS’ in ‘po/’ +* po/Makevars:: ‘Makevars’ in ‘po/’ +* po/Rules-*:: Extending ‘Makefile’ in ‘po/’ +* configure.ac:: ‘configure.ac’ at top level +* config.guess:: ‘config.guess’, ‘config.sub’ at top level +* mkinstalldirs:: ‘mkinstalldirs’ at top level +* aclocal:: ‘aclocal.m4’ at top level +* config.h.in:: ‘config.h.in’ at top level +* Makefile:: ‘Makefile.in’ at top level +* src/Makefile:: ‘Makefile.in’ in ‘src/’ +* lib/gettext.h:: ‘gettext.h’ in ‘lib/’ + + +File: gettext.info, Node: po/POTFILES.in, Next: po/LINGUAS, Up: Adjusting Files + +13.4.1 ‘POTFILES.in’ in ‘po/’ +----------------------------- + + The ‘po/’ directory should receive a file named ‘POTFILES.in’. This +file tells which files, among all program sources, have marked strings +needing translation. Here is an example of such a file: + + # List of source files containing translatable strings. + # Copyright (C) 1995 Free Software Foundation, Inc. + + # Common library files + lib/error.c + lib/getopt.c + lib/xmalloc.c + + # Package source files + src/gettext.c + src/msgfmt.c + src/xgettext.c + +Hash-marked comments and white lines are ignored. All other lines list +those source files containing strings marked for translation (*note Mark +Keywords::), in a notation relative to the top level of your whole +distribution, rather than the location of the ‘POTFILES.in’ file itself. + + When a C file is automatically generated by a tool, like ‘flex’ or +‘bison’, that doesn't introduce translatable strings by itself, it is +recommended to list in ‘po/POTFILES.in’ the real source file (ending in +‘.l’ in the case of ‘flex’, or in ‘.y’ in the case of ‘bison’), not the +generated C file. + + +File: gettext.info, Node: po/LINGUAS, Next: po/Makevars, Prev: po/POTFILES.in, Up: Adjusting Files + +13.4.2 ‘LINGUAS’ in ‘po/’ +------------------------- + + The ‘po/’ directory should also receive a file named ‘LINGUAS’. This +file contains the list of available translations. It is a whitespace +separated list. Hash-marked comments and white lines are ignored. Here +is an example file: + + # Set of available languages. + de fr + +This example means that German and French PO files are available, so +that these languages are currently supported by your package. If you +want to further restrict, at installation time, the set of installed +languages, this should not be done by modifying the ‘LINGUAS’ file, but +rather by using the ‘LINGUAS’ environment variable (*note Installers::). + + It is recommended that you add the "languages" ‘en@quot’ and +‘en@boldquot’ to the ‘LINGUAS’ file. ‘en@quot’ is a variant of English +message catalogs (‘en’) which uses real quotation marks instead of the +ugly looking asymmetric ASCII substitutes ‘`’ and ‘'’. ‘en@boldquot’ is +a variant of ‘en@quot’ that additionally outputs quoted pieces of text +in a bold font, when used in a terminal emulator which supports the +VT100 escape sequences (such as ‘xterm’ or the Linux console, but not +Emacs in ‘M-x shell’ mode). + + These extra message catalogs ‘en@quot’ and ‘en@boldquot’ are +constructed automatically, not by translators; to support them, you need +the files ‘Rules-quot’, ‘quot.sed’, ‘boldquot.sed’, ‘en@quot.header’, +‘en@boldquot.header’, ‘insert-header.sed’ in the ‘po/’ directory. You +can copy them from GNU gettext's ‘po/’ directory; they are also +installed by running ‘gettextize’. + + +File: gettext.info, Node: po/Makevars, Next: po/Rules-*, Prev: po/LINGUAS, Up: Adjusting Files + +13.4.3 ‘Makevars’ in ‘po/’ +-------------------------- + + The ‘po/’ directory also has a file named ‘Makevars’. It contains +variables that are specific to your project. ‘po/Makevars’ gets +inserted into the ‘po/Makefile’ when the latter is created. The +variables thus take effect when the POT file is created or updated, and +when the message catalogs get installed. + + The first three variables can be left unmodified if your package has +a single message domain and, accordingly, a single ‘po/’ directory. +Only packages which have multiple ‘po/’ directories at different +locations need to adjust the three first variables defined in +‘Makevars’. + + As an alternative to the ‘XGETTEXT_OPTIONS’ variable, it is also +possible to specify ‘xgettext’ options through the ‘AM_XGETTEXT_OPTION’ +autoconf macro. See *note AM_XGETTEXT_OPTION::. + + +File: gettext.info, Node: po/Rules-*, Next: configure.ac, Prev: po/Makevars, Up: Adjusting Files + +13.4.4 Extending ‘Makefile’ in ‘po/’ +------------------------------------ + + All files called ‘Rules-*’ in the ‘po/’ directory get appended to the +‘po/Makefile’ when it is created. They present an opportunity to add +rules for special PO files to the Makefile, without needing to mess with +‘po/Makefile.in.in’. + + GNU gettext comes with a ‘Rules-quot’ file, containing rules for +building catalogs ‘en@quot.po’ and ‘en@boldquot.po’. The effect of +‘en@quot.po’ is that people who set their ‘LANGUAGE’ environment +variable to ‘en@quot’ will get messages with proper looking symmetric +Unicode quotation marks instead of abusing the ASCII grave accent and +the ASCII apostrophe for indicating quotations. To enable this catalog, +simply add ‘en@quot’ to the ‘po/LINGUAS’ file. The effect of +‘en@boldquot.po’ is that people who set ‘LANGUAGE’ to ‘en@boldquot’ will +get not only proper quotation marks, but also the quoted text will be +shown in a bold font on terminals and consoles. This catalog is useful +only for command-line programs, not GUI programs. To enable it, +similarly add ‘en@boldquot’ to the ‘po/LINGUAS’ file. + + Similarly, you can create rules for building message catalogs for the +‘sr@latin’ locale - Serbian written with the Latin alphabet - from those +for the ‘sr’ locale - Serbian written with Cyrillic letters. See *note +msgfilter Invocation::. + + +File: gettext.info, Node: configure.ac, Next: config.guess, Prev: po/Rules-*, Up: Adjusting Files + +13.4.5 ‘configure.ac’ at top level +---------------------------------- + + ‘configure.ac’ or ‘configure.in’ - this is the source from which +‘autoconf’ generates the ‘configure’ script. + + 1. Declare the package and version. + + This is done by a set of lines like these: + + PACKAGE=gettext + VERSION=0.25.1 + AC_DEFINE_UNQUOTED(PACKAGE, "$PACKAGE") + AC_DEFINE_UNQUOTED(VERSION, "$VERSION") + AC_SUBST(PACKAGE) + AC_SUBST(VERSION) + + or, if you are using GNU ‘automake’, by a line like this: + + AM_INIT_AUTOMAKE(gettext, 0.25.1) + + Of course, you replace ‘gettext’ with the name of your package, and + ‘0.25.1’ by its version numbers, exactly as they should appear in + the packaged ‘tar’ file name of your distribution + (‘gettext-0.25.1.tar.gz’, here). + + 2. Check for internationalization support. + + Here is the main ‘m4’ macro for triggering internationalization + support. Just add this line to ‘configure.ac’: + + AM_GNU_GETTEXT([external]) + + This call is purposely simple, even if it generates a lot of + configure time checking and actions. + + 3. Have output files created. + + The ‘AC_OUTPUT’ directive, at the end of your ‘configure.ac’ file, + needs to be modified in two ways: + + AC_OUTPUT([EXISTING CONFIGURATION FILES po/Makefile.in], + [EXISTING ADDITIONAL ACTIONS]) + + The modification to the first argument to ‘AC_OUTPUT’ asks for + substitution in the ‘po/’ directory. Note the ‘.in’ suffix used + for ‘po/’ only. This is because the distributed file is really + ‘po/Makefile.in.in’. + + +File: gettext.info, Node: config.guess, Next: mkinstalldirs, Prev: configure.ac, Up: Adjusting Files + +13.4.6 ‘config.guess’, ‘config.sub’ at top level +------------------------------------------------ + + You need to add the GNU ‘config.guess’ and ‘config.sub’ files to your +distribution. They are needed because the ‘AM_ICONV’ macro contains +knowledge about specific platforms and therefore needs to identify the +platform. + + You can obtain the newest version of ‘config.guess’ and ‘config.sub’ +from the ‘config’ project at ‘https://savannah.gnu.org/’. The commands +to fetch them are + $ wget -O config.guess 'https://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD' + $ wget -O config.sub 'https://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.sub;hb=HEAD' +Less recent versions are also contained in the GNU ‘automake’ and GNU +‘libtool’ packages. + + Normally, ‘config.guess’ and ‘config.sub’ are put at the top level of +a distribution. But it is also possible to put them in a subdirectory, +altogether with other configuration support files like ‘install-sh’, +‘ltconfig’, ‘ltmain.sh’ or ‘missing’. All you need to do, other than +moving the files, is to add the following line to your ‘configure.ac’. + + AC_CONFIG_AUX_DIR([SUBDIR]) + + +File: gettext.info, Node: mkinstalldirs, Next: aclocal, Prev: config.guess, Up: Adjusting Files + +13.4.7 ‘mkinstalldirs’ at top level +----------------------------------- + + With earlier versions of GNU gettext, you needed to add the GNU +‘mkinstalldirs’ script to your distribution. This is not needed any +more. You can remove it. + + +File: gettext.info, Node: aclocal, Next: config.h.in, Prev: mkinstalldirs, Up: Adjusting Files + +13.4.8 ‘aclocal.m4’ at top level +-------------------------------- + + If you do not have an ‘aclocal.m4’ file in your distribution, the +simplest is to concatenate the files ‘build-to-host.m4’, ‘gettext.m4’, +‘host-cpu-c-abi.m4’, ‘intlmacosx.m4’, ‘iconv.m4’, ‘lib-ld.m4’, +‘lib-link.m4’, ‘lib-prefix.m4’, ‘nls.m4’, ‘po.m4’, ‘progtest.m4’ from +GNU ‘gettext’'s ‘PREFIX/share/gettext/m4/’ directory into a single file. + + If you already have an ‘aclocal.m4’ file, then you will have to merge +the said macro files into your ‘aclocal.m4’. Note that if you are +upgrading from a previous release of GNU ‘gettext’, you should most +probably _replace_ the macros (‘AM_GNU_GETTEXT’, etc.), as they usually +change a little from one release of GNU ‘gettext’ to the next. Their +contents may vary as we get more experience with strange systems out +there. + + You should be using GNU ‘automake’ 1.9 or newer. With it, you need +to copy the files ‘build-to-host.m4’, ‘gettext.m4’, ‘host-cpu-c-abi.m4’, +‘intlmacosx.m4’, ‘iconv.m4’, ‘lib-ld.m4’, ‘lib-link.m4’, +‘lib-prefix.m4’, ‘nls.m4’, ‘po.m4’, ‘progtest.m4’ from GNU ‘gettext’'s +‘PREFIX/share/gettext/m4/’ directory to a subdirectory named ‘m4/’ and +add the line + + ACLOCAL_AMFLAGS = -I m4 + +to your top level ‘Makefile.am’. + + If you are using GNU ‘automake’ 1.12 or newer, it is even easier: Add +the line + + ACLOCAL_AMFLAGS = -I m4 + +to your top level ‘Makefile.am’, and run ‘aclocal --install +--system-acdir=PREFIX/share/gettext/m4 -I m4’. This will copy the +needed files to the ‘m4/’ subdirectory automatically, before updating +‘aclocal.m4’. + + Note: This ‘--system-acdir’ option should only be used here, once. +If you were to use it after ‘autopoint’ has been run, it would destroy +the consistency that ‘autopoint’ guarantees and lead to all sorts of +malfunction at build time. + + These macros check for the internationalization support functions and +related information. + + +File: gettext.info, Node: config.h.in, Next: Makefile, Prev: aclocal, Up: Adjusting Files + +13.4.9 ‘config.h.in’ at top level +--------------------------------- + + The include file template that holds the C macros to be defined by +‘configure’ is usually called ‘config.h.in’ and may be maintained either +manually or automatically. + + If it is maintained automatically, by use of the ‘autoheader’ +program, you need to do nothing about it. This is the case in +particular if you are using GNU ‘automake’. + + If it is maintained manually, you can get away by adding the +following lines to ‘config.h.in’: + + /* Define to 1 if translation of program messages to the user's + native language is requested. */ + #undef ENABLE_NLS + + +File: gettext.info, Node: Makefile, Next: src/Makefile, Prev: config.h.in, Up: Adjusting Files + +13.4.10 ‘Makefile.in’ at top level +---------------------------------- + + Here are a few modifications you need to make to your main, top-level +‘Makefile.in’ file. + + 1. Add the following lines near the beginning of your ‘Makefile.in’, + so the ‘dist:’ goal will work properly (as explained further down): + + PACKAGE = @PACKAGE@ + VERSION = @VERSION@ + + 2. Wherever you process subdirectories in your ‘Makefile.in’, be sure + you also process the subdirectory ‘po’. Special rules in the + ‘Makefiles’ take care for the case where no internationalization is + wanted. + + If you are using Makefiles, either generated by automake, or + hand-written so they carefully follow the GNU coding standards, the + effected goals for which the new subdirectories must be handled + include ‘installdirs’, ‘install’, ‘uninstall’, ‘clean’, + ‘distclean’. + + Here is an example of a canonical order of processing. In this + example, we also define ‘SUBDIRS’ in ‘Makefile.in’ for it to be + further used in the ‘dist:’ goal. + + SUBDIRS = doc lib src po + + 3. A delicate point is the ‘dist:’ goal, as ‘po/Makefile’ will later + assume that the proper directory has been set up from the main + ‘Makefile’. Here is an example at what the ‘dist:’ goal might look + like: + + distdir = $(PACKAGE)-$(VERSION) + dist: Makefile + rm -fr $(distdir) + mkdir $(distdir) + chmod 777 $(distdir) + for file in $(DISTFILES); do \ + ln $$file $(distdir) 2>/dev/null || cp -p $$file $(distdir); \ + done + for subdir in $(SUBDIRS); do \ + mkdir $(distdir)/$$subdir || exit 1; \ + chmod 777 $(distdir)/$$subdir; \ + (cd $$subdir && $(MAKE) $@) || exit 1; \ + done + tar chozf $(distdir).tar.gz $(distdir) + rm -fr $(distdir) + + Note that if you are using GNU ‘automake’, ‘Makefile.in’ is +automatically generated from ‘Makefile.am’, and all needed changes to +‘Makefile.am’ are already made by running ‘gettextize’. + + +File: gettext.info, Node: src/Makefile, Next: lib/gettext.h, Prev: Makefile, Up: Adjusting Files + +13.4.11 ‘Makefile.in’ in ‘src/’ +------------------------------- + + Some of the modifications made in the main ‘Makefile.in’ will also be +needed in the ‘Makefile.in’ from your package sources, which we assume +here to be in the ‘src/’ subdirectory. Here are all the modifications +needed in ‘src/Makefile.in’: + + 1. In view of the ‘dist:’ goal, you should have these lines near the + beginning of ‘src/Makefile.in’: + + PACKAGE = @PACKAGE@ + VERSION = @VERSION@ + + 2. If not done already, you should guarantee that ‘top_srcdir’ gets + defined. This will serve for ‘cpp’ include files. Just add the + line: + + top_srcdir = @top_srcdir@ + + 3. You might also want to define ‘subdir’ as ‘src’, later allowing for + almost uniform ‘dist:’ goals in all your ‘Makefile.in’. At list, + the ‘dist:’ goal below assume that you used: + + subdir = src + + 4. The ‘main’ function of your program will normally call + ‘bindtextdomain’ (see *note Triggering::), like this: + + bindtextdomain (PACKAGE, LOCALEDIR); + textdomain (PACKAGE); + + On native Windows platforms, the ‘main’ function may call + ‘wbindtextdomain’ instead of ‘bindtextdomain’. + + To make LOCALEDIR known to the program, add the following lines to + ‘Makefile.in’: + + datadir = @datadir@ + datarootdir= @datarootdir@ + localedir = @localedir@ + DEFS = -DLOCALEDIR=$(localedir_c_make) @DEFS@ + + ‘$(localedir_c_make)’ expands to the value of ‘localedir’, in C + syntax, escaped for use in a ‘Makefile’. Note that ‘@datadir@’ + defaults to ‘$(prefix)/share’, and ‘$(localedir)’ defaults to + ‘$(prefix)/share/locale’. + + 5. You should ensure that the final linking will use ‘@LIBINTL@’ or + ‘@LTLIBINTL@’ as a library. ‘@LIBINTL@’ is for use without + ‘libtool’, ‘@LTLIBINTL@’ is for use with ‘libtool’. An easy way to + achieve this is to manage that it gets into ‘LIBS’, like this: + + LIBS = @LIBINTL@ @LIBS@ + + In most packages internationalized with GNU ‘gettext’, one will + find a directory ‘lib/’ in which a library containing some helper + functions will be build. (You need at least the few functions + which the GNU ‘gettext’ Library itself needs.) However some of the + functions in the ‘lib/’ also give messages to the user which of + course should be translated, too. Taking care of this, the support + library (say ‘libsupport.a’) should be placed before ‘@LIBINTL@’ + and ‘@LIBS@’ in the above example. So one has to write this: + + LIBS = ../lib/libsupport.a @LIBINTL@ @LIBS@ + + 6. Your ‘dist:’ goal has to conform with others. Here is a reasonable + definition for it: + + distdir = ../$(PACKAGE)-$(VERSION)/$(subdir) + dist: Makefile $(DISTFILES) + for file in $(DISTFILES); do \ + ln $$file $(distdir) 2>/dev/null || cp -p $$file $(distdir) || exit 1; \ + done + + Note that if you are using GNU ‘automake’, ‘Makefile.in’ is +automatically generated from ‘Makefile.am’, and the first three changes +and the last change are not necessary. The remaining needed +‘Makefile.am’ modifications are the following: + + 1. To make LOCALEDIR known to the program, add the following to + ‘Makefile.am’: + + _CPPFLAGS = -DLOCALEDIR=$(localedir_c_make) + + for each specific module or compilation unit, or + + AM_CPPFLAGS = -DLOCALEDIR=$(localedir_c_make) + + for all modules and compilation units together. + + 2. To ensure that the final linking will use ‘@LIBINTL@’ or + ‘@LTLIBINTL@’ as a library, add the following to ‘Makefile.am’: + + _LDADD = @LIBINTL@ + + for each specific program, or + + LDADD = @LIBINTL@ + + for all programs together. Remember that when you use ‘libtool’ to + link a program, you need to use @LTLIBINTL@ instead of @LIBINTL@ + for that program. + + +File: gettext.info, Node: lib/gettext.h, Prev: src/Makefile, Up: Adjusting Files + +13.4.12 ‘gettext.h’ in ‘lib/’ +----------------------------- + + Internationalization of packages, as provided by GNU ‘gettext’, is +optional. It can be turned off in two situations: + + • When the installer has specified ‘./configure --disable-nls’. This + can be useful when small binaries are more important than features, + for example when building utilities for boot diskettes. It can + also be useful in order to get some specific C compiler warnings + about code quality with some older versions of GCC (older than + 3.0). + + • When the libintl.h header (with its associated libintl library, if + any) is not already installed on the system, it is preferable that + the package builds without internationalization support, rather + than to give a compilation error. + + A C preprocessor macro can be used to detect these two cases. +Usually, when ‘libintl.h’ was found and not explicitly disabled, the +‘ENABLE_NLS’ macro will be defined to 1 in the autoconf generated +configuration file (usually called ‘config.h’). In the two negative +situations, however, this macro will not be defined, thus it will +evaluate to 0 in C preprocessor expressions. + + ‘gettext.h’ is a convenience header file for conditional use of +‘’, depending on the ‘ENABLE_NLS’ macro. If ‘ENABLE_NLS’ is +set, it includes ‘’; otherwise it defines no-op substitutes +for the libintl.h functions. We recommend the use of ‘"gettext.h"’ over +direct use of ‘’, so that portability to older systems is +guaranteed and installers can turn off internationalization if they want +to. In the C code, you will then write + + #include "gettext.h" + +instead of + + #include + + The location of ‘gettext.h’ is usually in a directory containing +auxiliary include files. In many GNU packages, there is a directory +‘lib/’ containing helper functions; ‘gettext.h’ fits there. In other +packages, it can go into the ‘src’ directory. + + Do not install the ‘gettext.h’ file in public locations. Every +package that needs it should contain a copy of it on its own. + + +File: gettext.info, Node: autoconf macros, Next: Version Control Issues, Prev: Adjusting Files, Up: Maintainers + +13.5 Autoconf macros for use in ‘configure.ac’ +============================================== + + GNU ‘gettext’ installs macros for use in a package's ‘configure.ac’ +or ‘configure.in’. *Note Introduction: (autoconf)Top. + + In order to copy these macros into your package, use the ‘gettextize’ +or ‘autopoint’ programs. See *note gettextize Invocation:: or *note +autopoint Invocation::. Attempts to use the ‘autoreconf’ program for +this purpose are unreliable. + + The primary macro is, of course, ‘AM_GNU_GETTEXT’. + +* Menu: + +* AM_GNU_GETTEXT:: AM_GNU_GETTEXT in ‘gettext.m4’ +* AM_GNU_GETTEXT_VERSION:: AM_GNU_GETTEXT_VERSION in ‘gettext.m4’ +* AM_GNU_GETTEXT_NEED:: AM_GNU_GETTEXT_NEED in ‘gettext.m4’ +* AM_PO_SUBDIRS:: AM_PO_SUBDIRS in ‘po.m4’ +* AM_XGETTEXT_OPTION:: AM_XGETTEXT_OPTION in ‘po.m4’ +* AM_ICONV:: AM_ICONV in ‘iconv.m4’ + + +File: gettext.info, Node: AM_GNU_GETTEXT, Next: AM_GNU_GETTEXT_VERSION, Up: autoconf macros + +13.5.1 AM_GNU_GETTEXT in ‘gettext.m4’ +------------------------------------- + + The ‘AM_GNU_GETTEXT’ macro tests for the presence of the GNU gettext +function family in either the C library or a separate ‘libintl’ library +(shared or static libraries are both supported). It also invokes +‘AM_PO_SUBDIRS’, thus preparing the ‘po/’ directories of the package for +building. + + ‘AM_GNU_GETTEXT’ accepts up to two optional arguments. The general +syntax is + + AM_GNU_GETTEXT([INTLSYMBOL], [NEEDSYMBOL]) + + INTLSYMBOL should always be ‘external’. + + If NEEDSYMBOL is specified and is ‘need-ngettext’, then GNU gettext +implementations (in libc or libintl) without the ‘ngettext()’ function +will be ignored. If NEEDSYMBOL is specified and is +‘need-formatstring-macros’, then GNU gettext implementations that don't +support the ISO C 99 ‘’ formatstring macros will be ignored. +Only one NEEDSYMBOL can be specified. These requirements can also be +specified by using the macro ‘AM_GNU_GETTEXT_NEED’ elsewhere. To +specify more than one requirement, just specify the strongest one among +them, or invoke the ‘AM_GNU_GETTEXT_NEED’ macro several times. The +hierarchy among the various alternatives is as follows: +‘need-formatstring-macros’ implies ‘need-ngettext’. + + The ‘AM_GNU_GETTEXT’ macro determines whether GNU gettext is +available and should be used. If so, it sets the ‘USE_NLS’ variable to +‘yes’; it defines ‘ENABLE_NLS’ to 1 in the autoconf generated +configuration file (usually called ‘config.h’); it sets the variables +‘LIBINTL’ and ‘LTLIBINTL’ to the linker options for use in a Makefile +(‘LIBINTL’ for use without libtool, ‘LTLIBINTL’ for use with libtool); +it adds an ‘-I’ option to ‘CPPFLAGS’ if necessary. In the negative +case, it sets ‘USE_NLS’ to ‘no’; it sets ‘LIBINTL’ and ‘LTLIBINTL’ to +empty and doesn't change ‘CPPFLAGS’. + + The complexities that ‘AM_GNU_GETTEXT’ deals with are the following: + + • Some operating systems have ‘gettext’ in the C library, for example + glibc. Some have it in a separate library ‘libintl’. GNU + ‘libintl’ might have been installed as part of the GNU ‘gettext’ + package. + + • GNU ‘libintl’, if installed, is not necessarily already in the + search path (‘CPPFLAGS’ for the include file search path, ‘LDFLAGS’ + for the library search path). + + • Except for glibc and the Solaris 11 libc, the operating system's + native ‘gettext’ cannot exploit the GNU mo files, doesn't have the + necessary locale dependency features, and cannot convert messages + from the catalog's text encoding to the user's locale encoding. + + • GNU ‘libintl’, if installed, is not necessarily already in the run + time library search path. To avoid the need for setting an + environment variable like ‘LD_LIBRARY_PATH’, the macro adds the + appropriate run time search path options to the ‘LIBINTL’ and + ‘LTLIBINTL’ variables. This works on most systems, but not on some + operating systems with limited shared library support, like SCO. + + • GNU ‘libintl’ relies on POSIX/XSI ‘iconv’. The macro checks for + linker options needed to use iconv and appends them to the + ‘LIBINTL’ and ‘LTLIBINTL’ variables. + + Additionally, the ‘AM_GNU_GETTEXT’ macro sets two variables, for +convenience. Both are derived from the ‘--localedir’ configure option. +They are correct even on native Windows, where directories frequently +contain backslashes. +‘localedir_c’ + This is the value of ‘localedir’, in C syntax. This variable is + meant to be substituted into C or C++ code through + ‘AC_CONFIG_FILES’. + +‘localedir_c_make’ + This is the value of ‘localedir’, in C syntax, escaped for use in a + ‘Makefile’. This variable is meant to be used in Makefiles, for + example for defining a C macro named ‘LOCALEDIR’: + AM_CPPFLAGS = ... -DLOCALEDIR=$(localedir_c_make) ... + + +File: gettext.info, Node: AM_GNU_GETTEXT_VERSION, Next: AM_GNU_GETTEXT_NEED, Prev: AM_GNU_GETTEXT, Up: autoconf macros + +13.5.2 AM_GNU_GETTEXT_VERSION in ‘gettext.m4’ +--------------------------------------------- + + The ‘AM_GNU_GETTEXT_VERSION’ macro declares the version number of the +GNU gettext infrastructure that is used by the package. + + The use of this macro is optional; only the ‘autopoint’ program makes +use of it (*note Version Control Issues::). + + +File: gettext.info, Node: AM_GNU_GETTEXT_NEED, Next: AM_PO_SUBDIRS, Prev: AM_GNU_GETTEXT_VERSION, Up: autoconf macros + +13.5.3 AM_GNU_GETTEXT_NEED in ‘gettext.m4’ +------------------------------------------ + + The ‘AM_GNU_GETTEXT_NEED’ macro declares a constraint regarding the +GNU gettext implementation. The syntax is + + AM_GNU_GETTEXT_NEED([NEEDSYMBOL]) + + If NEEDSYMBOL is ‘need-ngettext’, then GNU gettext implementations +(in libc or libintl) without the ‘ngettext()’ function will be ignored. +If NEEDSYMBOL is ‘need-formatstring-macros’, then GNU gettext +implementations that don't support the ISO C 99 ‘’ +formatstring macros will be ignored. + + The optional second argument of ‘AM_GNU_GETTEXT’ is also taken into +account. + + The ‘AM_GNU_GETTEXT_NEED’ invocations can occur before or after the +‘AM_GNU_GETTEXT’ invocation; the order doesn't matter. + + +File: gettext.info, Node: AM_PO_SUBDIRS, Next: AM_XGETTEXT_OPTION, Prev: AM_GNU_GETTEXT_NEED, Up: autoconf macros + +13.5.4 AM_PO_SUBDIRS in ‘po.m4’ +------------------------------- + + The ‘AM_PO_SUBDIRS’ macro prepares the ‘po/’ directories of the +package for building. This macro should be used in internationalized +programs written in other programming languages than C, C++, Objective +C, for example ‘sh’, ‘Python’, ‘Lisp’. See *note Programming +Languages:: for a list of programming languages that support +localization through PO files. + + The ‘AM_PO_SUBDIRS’ macro determines whether internationalization +should be used. If so, it sets the ‘USE_NLS’ variable to ‘yes’, +otherwise to ‘no’. It also determines the right values for Makefile +variables in each ‘po/’ directory. + + +File: gettext.info, Node: AM_XGETTEXT_OPTION, Next: AM_ICONV, Prev: AM_PO_SUBDIRS, Up: autoconf macros + +13.5.5 AM_XGETTEXT_OPTION in ‘po.m4’ +------------------------------------ + + The ‘AM_XGETTEXT_OPTION’ macro registers a command-line option to be +used in the invocations of ‘xgettext’ in the ‘po/’ directories of the +package. + + For example, if you have a source file that defines a function +‘error_at_line’ whose fifth argument is a format string, you can use + AM_XGETTEXT_OPTION([--flag=error_at_line:5:c-format]) +to instruct ‘xgettext’ to mark all translatable strings in ‘gettext’ +invocations that occur as fifth argument to this function as ‘c-format’. + + See *note xgettext Invocation:: for the list of options that +‘xgettext’ accepts. + + The use of this macro is an alternative to the use of the +‘XGETTEXT_OPTIONS’ variable in ‘po/Makevars’. + + +File: gettext.info, Node: AM_ICONV, Prev: AM_XGETTEXT_OPTION, Up: autoconf macros + +13.5.6 AM_ICONV in ‘iconv.m4’ +----------------------------- + + The ‘AM_ICONV’ macro tests for the presence of the POSIX/XSI ‘iconv’ +function family in either the C library or a separate ‘libiconv’ +library. If found, it sets the ‘am_cv_func_iconv’ variable to ‘yes’; it +defines ‘HAVE_ICONV’ to 1 in the autoconf generated configuration file +(usually called ‘config.h’); it defines ‘ICONV_CONST’ to ‘const’ or to +empty, depending on whether the second argument of ‘iconv()’ is of type +‘const char **’ or ‘char **’; it sets the variables ‘LIBICONV’ and +‘LTLIBICONV’ to the linker options for use in a Makefile (‘LIBICONV’ for +use without libtool, ‘LTLIBICONV’ for use with libtool); it adds an ‘-I’ +option to ‘CPPFLAGS’ if necessary. If not found, it sets ‘LIBICONV’ and +‘LTLIBICONV’ to empty and doesn't change ‘CPPFLAGS’. + + The complexities that ‘AM_ICONV’ deals with are the following: + + • Some operating systems have ‘iconv’ in the C library, for example + glibc. Some have it in a separate library ‘libiconv’, for example + OSF/1 or FreeBSD. Regardless of the operating system, GNU + ‘libiconv’ might have been installed. In that case, it should be + used instead of the operating system's native ‘iconv’. + + • GNU ‘libiconv’, if installed, is not necessarily already in the + search path (‘CPPFLAGS’ for the include file search path, ‘LDFLAGS’ + for the library search path). + + • GNU ‘libiconv’ is binary incompatible with some operating system's + native ‘iconv’, for example on FreeBSD. Use of an ‘iconv.h’ and + ‘libiconv.so’ that don't fit together would produce program + crashes. + + • GNU ‘libiconv’, if installed, is not necessarily already in the run + time library search path. To avoid the need for setting an + environment variable like ‘LD_LIBRARY_PATH’, the macro adds the + appropriate run time search path options to the ‘LIBICONV’ + variable. This works on most systems, but not on some operating + systems with limited shared library support, like SCO. + + ‘iconv.m4’ is distributed with the GNU gettext package because +‘gettext.m4’ relies on it. + + +File: gettext.info, Node: Version Control Issues, Next: Release Management, Prev: autoconf macros, Up: Maintainers + +13.6 Integrating with Version Control Systems +============================================= + + Many projects use version control systems for distributed development +and source backup. This section gives some advice how to manage the +uses of ‘gettextize’, ‘autopoint’ and ‘autoconf’ on version controlled +files. + +* Menu: + +* Distributed Development:: Avoiding version mismatch in distributed development +* Files under Version Control:: Files to put under version control +* Translations under Version Control:: Put PO Files under Version Control +* autopoint Invocation:: Invoking the ‘autopoint’ Program + + +File: gettext.info, Node: Distributed Development, Next: Files under Version Control, Up: Version Control Issues + +13.6.1 Avoiding version mismatch in distributed development +----------------------------------------------------------- + + In a project development with multiple developers, there should be a +single developer who occasionally - when there is desire to upgrade to a +new ‘gettext’ version - runs ‘gettextize’ and performs the changes +listed in *note Adjusting Files::, and then commits his changes to the +repository. + + It is highly recommended that all developers on a project use the +same version of GNU ‘gettext’ in the package. In other words, if a +developer runs ‘gettextize’, he should go the whole way, make the +necessary remaining changes and commit his changes to the repository. +Otherwise the following damages will likely occur: + + • Apparent version mismatch between developers. Since some ‘gettext’ + specific portions in ‘configure.ac’, ‘configure.in’ and + ‘Makefile.am’, ‘Makefile.in’ files depend on the ‘gettext’ version, + the use of infrastructure files belonging to different ‘gettext’ + versions can easily lead to build errors. + + • Hidden version mismatch. Such version mismatch can also lead to + malfunctioning of the package, that may be undiscovered by the + developers. The worst case of hidden version mismatch is that + internationalization of the package doesn't work at all. + + • Release risks. All developers implicitly perform constant testing + on a package. This is important in the days and weeks before a + release. If the guy who makes the release tar files uses a + different version of GNU ‘gettext’ than the other developers, the + distribution will be less well tested than if all had been using + the same ‘gettext’ version. For example, it is possible that a + platform specific bug goes undiscovered due to this constellation. + + +File: gettext.info, Node: Files under Version Control, Next: Translations under Version Control, Prev: Distributed Development, Up: Version Control Issues + +13.6.2 Files to put under version control +----------------------------------------- + + There are basically three ways to deal with generated files in the +context of a version controlled repository, such as ‘configure’ +generated from ‘configure.ac’, ‘PARSER.c’ generated from ‘PARSER.y’, or +‘po/Makefile.in.in’ autoinstalled by ‘gettextize’ or ‘autopoint’. + + 1. All generated files are always committed into the repository. + + 2. All generated files are committed into the repository occasionally, + for example each time a release is made. + + 3. Generated files are never committed into the repository. + + Each of these three approaches has different advantages and +drawbacks. + + 1. The advantage is that anyone can check out the source at any moment + and gets a working build. The drawbacks are: 1a. It requires some + frequent "push" actions by the maintainers. 1b. The repository + grows in size quite fast. + + 2. The advantage is that anyone can check out the source, and the + usual "./configure; make" will work. The drawbacks are: 2a. The + one who checks out the repository needs tools like GNU ‘automake’, + GNU ‘autoconf’, GNU ‘m4’ installed in his PATH; sometimes he even + needs particular versions of them. 2b. When a release is made and + a commit is made on the generated files, the other developers get + conflicts on the generated files when merging the local work back + to the repository. Although these conflicts are easy to resolve, + they are annoying. + + 3. The advantage is less work for the maintainers. The drawback is + that anyone who checks out the source not only needs tools like GNU + ‘automake’, GNU ‘autoconf’, GNU ‘m4’ installed in his PATH, but + also that he needs to perform a package specific pre-build step + before being able to "./configure; make". + + For the first and second approach, all files modified or brought in +by the occasional ‘gettextize’ invocation and update should be committed +into the repository. + + For the third approach, the maintainer can omit from the repository +all the files that ‘gettextize’ mentions as "copy". Instead, he adds to +the ‘configure.ac’ or ‘configure.in’ a line of the form + + AM_GNU_GETTEXT_VERSION(0.25.1) + +and adds to the package's pre-build script an invocation of ‘autopoint’. +For everyone who checks out the source, this ‘autopoint’ invocation will +copy into the right place the ‘gettext’ infrastructure files that have +been omitted from the repository. + + The version number used as argument to ‘AM_GNU_GETTEXT_VERSION’ is +the version of the ‘gettext’ infrastructure that the package wants to +use. It is also the minimum version number of the ‘autopoint’ program. +So, if you write ‘AM_GNU_GETTEXT_VERSION(0.11.5)’ then the developers +can have any version >= 0.11.5 installed; the package will work with the +0.11.5 infrastructure in all developers' builds. When the maintainer +then runs gettextize from, say, version 0.12.1 on the package, the +occurrence of ‘AM_GNU_GETTEXT_VERSION(0.11.5)’ will be changed into +‘AM_GNU_GETTEXT_VERSION(0.12.1)’, and all other developers that use the +CVS will henceforth need to have GNU ‘gettext’ 0.12.1 or newer +installed. + + +File: gettext.info, Node: Translations under Version Control, Next: autopoint Invocation, Prev: Files under Version Control, Up: Version Control Issues + +13.6.3 Put PO Files under Version Control +----------------------------------------- + + Since translations are valuable assets as well as the source code, it +would make sense to put them under version control. The GNU gettext +infrastructure supports two ways to deal with translations in the +context of a version controlled repository. + + 1. Both POT file and PO files are committed into the repository. + + 2. Only PO files are committed into the repository. + + If a POT file is absent when building, it will be generated by +scanning the source files with ‘xgettext’, and then the PO files are +regenerated as a dependency. On the other hand, some maintainers want +to keep the POT file unchanged during the development phase. So, even +if a POT file is present and older than the source code, it won't be +updated automatically. You can manually update it with ‘make +$(DOMAIN).pot-update’, and commit it at certain point. + + Special advices for particular version control systems: + + • Recent version control systems, Git for instance, ignore file's + timestamp. In that case, PO files can be accidentally updated even + if a POT file is not updated. To prevent this, you can set + ‘PO_DEPENDS_ON_POT’ variable to ‘no’ in the ‘Makevars’ file and do + ‘make update-po’ manually. + + • Location comments such as ‘#: lib/error.c:116’ are sometimes + annoying, since these comments are volatile and may introduce + unwanted change to the working copy when building. To mitigate + this, you can decide to omit those comments from the PO files in + the repository. + + This is possible with the ‘--no-location’ option of the ‘msgmerge’ + command (1). The drawback is that, if the location information is + needed, translators have to recover the location comments by + running ‘msgmerge’ again. + + ---------- Footnotes ---------- + + (1) you can also use it through the ‘MSGMERGE_OPTIONS’ option from +‘Makevars’ + + +File: gettext.info, Node: autopoint Invocation, Prev: Translations under Version Control, Up: Version Control Issues + +13.6.4 Invoking the ‘autopoint’ Program +--------------------------------------- + + autopoint [OPTION]... + + The ‘autopoint’ program copies standard gettext infrastructure files +into a source package. It extracts from a macro call of the form +‘AM_GNU_GETTEXT_VERSION(VERSION)’, found in the package's ‘configure.in’ +or ‘configure.ac’ file, the gettext version used by the package, and +copies the infrastructure files belonging to this version into the +package. + + To extract the latest available infrastructure which satisfies a +version requirement, then you can use the form +‘AM_GNU_GETTEXT_REQUIRE_VERSION(VERSION)’ instead. For example, if +gettext 0.25.1 is installed on your system and ‘0.19.1’ is requested, +then the infrastructure files of version 0.25.1 will be copied into a +source package. + +13.6.4.1 Options +................ + +‘-f’ +‘--force’ + Force overwriting of files that already exist. + +‘-n’ +‘--dry-run’ + Print modifications but don't perform them. All file copying + actions that ‘autopoint’ would normally execute are inhibited and + instead only listed on standard output. + +13.6.4.2 Informative output +........................... + +‘--help’ + Display this help and exit. + +‘--version’ + Output version information and exit. + + ‘autopoint’ supports the GNU ‘gettext’ versions from 0.10.35 to the +current one, 0.25.1. In order to apply ‘autopoint’ to a package using a +‘gettext’ version newer than 0.25.1, you need to install this same +version of GNU ‘gettext’ at least. + + In packages using GNU ‘automake’, an invocation of ‘autopoint’ should +be followed by invocations of ‘aclocal’ and then ‘autoconf’ and +‘autoheader’. The reason is that ‘autopoint’ installs some autoconf +macro files, which are used by ‘aclocal’ to create ‘aclocal.m4’, and the +latter is used by ‘autoconf’ to create the package's ‘configure’ script +and by ‘autoheader’ to create the package's ‘config.h.in’ include file +template. + + The name ‘autopoint’ is an abbreviation of ‘auto-po-intl-m4’; in +earlier versions, the tool copied or updated mostly files in the ‘po’, +‘intl’, ‘m4’ directories. + + +File: gettext.info, Node: Release Management, Prev: Version Control Issues, Up: Maintainers + +13.7 Creating a Distribution Tarball +==================================== + + In projects that use GNU ‘automake’, the usual commands for creating +a distribution tarball, ‘make dist’ or ‘make distcheck’, automatically +update the PO files as needed. + + If GNU ‘automake’ is not used, the maintainer needs to perform this +update before making a release: + + $ ./configure + $ (cd po; make update-po) + $ make distclean + + +File: gettext.info, Node: Installers, Next: Programming Languages, Prev: Maintainers, Up: Top + +14 The Installer's and Distributor's View +***************************************** + + By default, packages fully using GNU ‘gettext’, internally, are +installed in such a way as to allow translation of messages. At +_configuration_ time, those packages should automatically detect whether +the underlying host system already provides the GNU ‘gettext’ functions. +If not, the GNU ‘gettext’ library should be automatically prepared and +used. Installers may use special options at configuration time for +changing this behavior. The command ‘./configure +--with-included-gettext’ bypasses system ‘gettext’ to use the included +GNU ‘gettext’ instead, while ‘./configure --disable-nls’ produces +programs totally unable to translate messages. + + Internationalized packages have usually many ‘LL.po’ or ‘LL_CC.po’ +files, where + + • LL gives an ISO 639 two-letter code identifying the language. For + some languages, a two-letter code does not exist, and a + three-letter code is used instead. + • The optional CC is an ISO 3166 two-letter code of a country or + territory. + +Unless translations are disabled, all those available are installed +together with the package. However, the environment variable ‘LINGUAS’ +may be set, prior to configuration, to limit the installed set. +‘LINGUAS’ should then contain a space separated list of locale names (of +the form ‘LL’ or ‘LL_CC’), stating which languages or language variants +are allowed. + + GNU ‘gettext’ uses *.its and *.loc files (*note Preparing ITS +Rules::) from other packages, provided they are installed in +‘PREFIX/share/gettext/its/’, where ‘PREFIX’ is the value of the +‘--prefix’ option passed to ‘gettext’'s ‘configure’ script. So, this is +the canonical location for installing *.its and *.loc files from other +packages. + + +File: gettext.info, Node: Programming Languages, Next: Data Formats, Prev: Installers, Up: Top + +15 Other Programming Languages +****************************** + + While the presentation of ‘gettext’ focuses mostly on C and +implicitly applies to C++ as well, its scope is far broader than that: +Many programming languages, scripting languages and other textual data +like GUI resources or package descriptions can make use of the gettext +approach. + +* Menu: + +* Language Implementors:: The Language Implementor's View +* Programmers for other Languages:: The Programmer's View +* Translators for other Languages:: The Translator's View +* Maintainers for other Languages:: The Maintainer's View +* List of Programming Languages:: Individual Programming Languages + + +File: gettext.info, Node: Language Implementors, Next: Programmers for other Languages, Up: Programming Languages + +15.1 The Language Implementor's View +==================================== + + All programming and scripting languages that have the notion of +strings are eligible to supporting ‘gettext’. Supporting ‘gettext’ +means the following: + + 1. You should add to the language a syntax for translatable strings. + In principle, a function call of ‘gettext’ would do, but a + shorthand syntax helps keeping the legibility of internationalized + programs. For example, in C we use the syntax ‘_("string")’, and + in GNU awk we use the shorthand ‘_"string"’. + + 2. You should arrange that evaluation of such a translatable string at + runtime calls the ‘gettext’ function, or performs equivalent + processing. + + 3. Similarly, you should make the functions ‘ngettext’, ‘dcgettext’, + ‘dcngettext’ available from within the language. These functions + are less often used, but are nevertheless necessary for particular + purposes: ‘ngettext’ for correct plural handling, and ‘dcgettext’ + and ‘dcngettext’ for obeying other locale-related environment + variables than ‘LC_MESSAGES’, such as ‘LC_TIME’ or ‘LC_MONETARY’. + For these latter functions, you need to make the ‘LC_*’ constants, + available in the C header ‘’, referenceable from within + the language, usually either as enumeration values or as strings. + + 4. You should allow the programmer to designate a message domain, + either by making the ‘textdomain’ function available from within + the language, or by introducing a magic variable called + ‘TEXTDOMAIN’. Similarly, you should allow the programmer to + designate where to search for message catalogs, by providing access + to the ‘bindtextdomain’ function or -- on native Windows platforms + -- to the ‘wbindtextdomain’ function. + + 5. You should either perform a ‘setlocale (LC_ALL, "")’ call during + the startup of your language runtime, or allow the programmer to do + so. Remember that gettext will act as a no-op if the ‘LC_MESSAGES’ + and ‘LC_CTYPE’ locale categories are not both set. + + 6. A programmer should have a way to extract translatable strings from + a program into a PO file. The GNU ‘xgettext’ program is being + extended to support very different programming languages. Please + contact the GNU ‘gettext’ maintainers to help them doing this. The + GNU ‘gettext’ maintainers will need from you a formal description + of the lexical structure of source files. It should answer the + questions: + • What does a token look like? + • What does a string literal look like? What escape characters + exist inside a string? + • What escape characters exist outside of strings? If Unicode + escapes are supported, are they applied before or after + tokenization? + • What is the syntax for function calls? How are consecutive + arguments in the same function call separated? + • What is the syntax for comments? + Based on this description, the GNU ‘gettext’ maintainers can add + support to ‘xgettext’. + + If the string extractor is best integrated into your language's + parser, GNU ‘xgettext’ can function as a front end to your string + extractor. + + 7. The language's library should have a string formatting facility. + Additionally: + 1. There must be a way, in the format string, to denote the + arguments by a positional number or a name. This is needed + because for some languages and some messages with more than + one substitutable argument, the translation will need to + output the substituted arguments in different order. *Note + c-format Flag::. + 2. The syntax of format strings must be documented in a way that + translators can understand. The GNU ‘gettext’ manual will be + extended to include a pointer to this documentation. + Based on this, the GNU ‘gettext’ maintainers can add a format + string equivalence checker to ‘msgfmt’, so that translators get + told immediately when they have made a mistake during the + translation of a format string. + + 8. If the language has more than one implementation, and not all of + the implementations use ‘gettext’, but the programs should be + portable across implementations, you should provide a no-i18n + emulation, that makes the other implementations accept programs + written for yours, without actually translating the strings. + + 9. To help the programmer in the task of marking translatable strings, + which is sometimes performed using the Emacs PO mode (*note + Marking::), you are welcome to contact the GNU ‘gettext’ + maintainers, so they can add support for your language to + ‘po-mode.el’. + + On the implementation side, two approaches are possible, with +different effects on portability and copyright: + + • You may link against GNU ‘gettext’ functions if they are found in + the C library. For example, an autoconf test for ‘gettext()’ and + ‘ngettext()’ will detect this situation. For the moment, this test + will succeed on GNU systems and on Solaris 11 platforms. No severe + copyright restrictions apply, except if you want to distribute + statically linked binaries. + + • You may emulate or reimplement the GNU ‘gettext’ functionality. + This has the advantage of full portability and no copyright + restrictions, but also the drawback that you have to reimplement + the GNU ‘gettext’ features (such as the ‘LANGUAGE’ environment + variable, the locale aliases database, the automatic charset + conversion, and plural handling). + + +File: gettext.info, Node: Programmers for other Languages, Next: Translators for other Languages, Prev: Language Implementors, Up: Programming Languages + +15.2 The Programmer's View +========================== + + For the programmer, the general procedure is the same as for the C +language. The Emacs PO mode marking supports other languages, and the +GNU ‘xgettext’ string extractor recognizes other languages based on the +file extension or a command-line option. In some languages, ‘setlocale’ +is not needed because it is already performed by the underlying language +runtime. + + +File: gettext.info, Node: Translators for other Languages, Next: Maintainers for other Languages, Prev: Programmers for other Languages, Up: Programming Languages + +15.3 The Translator's View +========================== + + The translator works exactly as in the C language case. The only +difference is that when translating format strings, she has to be aware +of the language's particular syntax for positional arguments in format +strings. + +* Menu: + +* c-format:: C Format Strings +* objc-format:: Objective C Format Strings +* c++-format:: C++ Format Strings +* python-format:: Python Format Strings +* java-format:: Java Format Strings +* csharp-format:: C# Format Strings +* javascript-format:: JavaScript Format Strings +* scheme-format:: Scheme Format Strings +* lisp-format:: Lisp Format Strings +* elisp-format:: Emacs Lisp Format Strings +* librep-format:: librep Format Strings +* rust-format:: Rust Format Strings +* go-format:: Go Format Strings +* ruby-format:: Ruby Format Strings +* sh-format:: Shell Format Strings +* awk-format:: awk Format Strings +* lua-format:: Lua Format Strings +* object-pascal-format:: Object Pascal Format Strings +* modula2-format:: Modula-2 Format Strings +* d-format:: D Format Strings +* smalltalk-format:: Smalltalk Format Strings +* qt-format:: Qt Format Strings +* qt-plural-format:: Qt Plural Format Strings +* kde-format:: KDE Format Strings +* kde-kuit-format:: KUIT Format Strings +* boost-format:: Boost Format Strings +* tcl-format:: Tcl Format Strings +* perl-format:: Perl Format Strings +* php-format:: PHP Format Strings +* gcc-internal-format:: GCC internal Format Strings +* gfc-internal-format:: GFC internal Format Strings +* ycp-format:: YCP Format Strings + + +File: gettext.info, Node: c-format, Next: objc-format, Up: Translators for other Languages + +15.3.1 C Format Strings +----------------------- + + C format strings are described in POSIX (IEEE P1003.1 2001), section +XSH 3 fprintf(), +. +See also the fprintf() manual page man fprintf. + + Although format strings with positions that reorder arguments, such +as + + "Only %2$d bytes free on '%1$s'." + +which is semantically equivalent to + + "'%s' has only %d bytes free." + +are a POSIX/XSI feature and not specified by ISO C 99, translators can +rely on this reordering ability: On the few platforms where ‘printf()’, +‘fprintf()’ etc. don't support this feature natively, ‘libintl.a’ or +‘libintl.so’ provides replacement functions, and GNU ‘’ +activates these replacement functions automatically. + + C format strings can contain placeholders that reference macros +defined in ISO C 99 ‘’. For example, ‘’ references +the macro ‘PRId64’. The value of such a macro is system-dependent, but +programmers and translators do not need to know this value. ISO C 23 +specifies system-independent format string elements, for example, +‘"%w64d"’ instead of ‘"%" PRId64’; however, as of 2024, these are not +implemented across systems and therefore cannot be used portably. + + As a special feature for Farsi (Persian) and maybe Arabic, +translators can insert an ‘I’ flag into numeric format directives. For +example, the translation of ‘"%d"’ can be ‘"%Id"’. The effect of this +flag, on systems with GNU ‘libc’, is that in the output, the ASCII +digits are replaced with the ‘outdigits’ defined in the ‘LC_CTYPE’ +locale category. On other systems, the ‘gettext’ function removes this +flag, so that it has no effect. + + Note that the programmer should _not_ put this flag into the +untranslated string. (Putting the ‘I’ format directive flag into an +MSGID string would lead to undefined behaviour on platforms without +glibc when NLS is disabled.) + + +File: gettext.info, Node: objc-format, Next: c++-format, Prev: c-format, Up: Translators for other Languages + +15.3.2 Objective C Format Strings +--------------------------------- + + Objective C format strings are like C format strings. They support +an additional format directive: "%@", which when executed consumes an +argument of type ‘Object *’. + + Objective C format strings, like C format strings, can contain +placeholders that reference macros defined in ISO C 99 ‘’. + + +File: gettext.info, Node: c++-format, Next: python-format, Prev: objc-format, Up: Translators for other Languages + +15.3.3 C++ Format Strings +------------------------- + + C++ format strings are described in ISO C++ 20, namely in +, +section 20.20.2 Format string [format.string]. + + An easier-to-read description is found at + and +. + + +File: gettext.info, Node: python-format, Next: java-format, Prev: c++-format, Up: Translators for other Languages + +15.3.4 Python Format Strings +---------------------------- + + There are two kinds of format strings in Python: those acceptable to +the Python built-in format operator ‘%’, labelled as ‘python-format’, +and those acceptable to the ‘format’ method of the ‘str’ object. + + Python ‘%’ format strings are described in Python Library reference / +5. Built-in Types / 5.6. Sequence Types / +5.6.2. String Formatting Operations. +. + + Python brace format strings are described in +PEP 3101 - Advanced String Formatting, +. + + +File: gettext.info, Node: java-format, Next: csharp-format, Prev: python-format, Up: Translators for other Languages + +15.3.5 Java Format Strings +-------------------------- + + There are two kinds of format strings in Java: those acceptable to +the ‘MessageFormat.format’ function, labelled as ‘java-format’, and +those acceptable to the ‘String.format’ and ‘PrintStream.printf’ +functions, labelled as ‘java-printf-format’. + + Java format strings are described in the JDK documentation for class +‘java.text.MessageFormat’, +. +See also the ICU documentation +. + + Java ‘printf’ format strings are described in the JDK documentation +for class ‘java.util.Formatter’, +. + + +File: gettext.info, Node: csharp-format, Next: javascript-format, Prev: java-format, Up: Translators for other Languages + +15.3.6 C# Format Strings +------------------------ + + C# format strings are described in the .NET documentation for class +‘System.String’ and in +. + + +File: gettext.info, Node: javascript-format, Next: scheme-format, Prev: csharp-format, Up: Translators for other Languages + +15.3.7 JavaScript Format Strings +-------------------------------- + + Although JavaScript specification itself does not define any format +strings, many JavaScript implementations provide printf-like functions. +‘xgettext’ understands a set of common format strings used in popular +JavaScript implementations including Gjs, Seed, and Node.JS. In such a +format string, a directive starts with ‘%’ and is finished by a +specifier: ‘%’ denotes a literal percent sign, ‘c’ denotes a character, +‘s’ denotes a string, ‘b’, ‘d’, ‘o’, ‘x’, ‘X’ denote an integer, ‘f’ +denotes floating-point number, ‘j’ denotes a JSON object. + + +File: gettext.info, Node: scheme-format, Next: lisp-format, Prev: javascript-format, Up: Translators for other Languages + +15.3.8 Scheme Format Strings +---------------------------- + + Scheme format strings are documented in the SLIB manual, section +Format Specification. + + +File: gettext.info, Node: lisp-format, Next: elisp-format, Prev: scheme-format, Up: Translators for other Languages + +15.3.9 Lisp Format Strings +-------------------------- + + Lisp format strings are described in the Common Lisp HyperSpec, +chapter 22.3 Formatted Output, +. + + +File: gettext.info, Node: elisp-format, Next: librep-format, Prev: lisp-format, Up: Translators for other Languages + +15.3.10 Emacs Lisp Format Strings +--------------------------------- + + Emacs Lisp format strings are documented in the Emacs Lisp reference, +section Formatting Strings, +. +Note that as of version 21, XEmacs supports numbered argument +specifications in format strings while FSF Emacs doesn't. + + +File: gettext.info, Node: librep-format, Next: rust-format, Prev: elisp-format, Up: Translators for other Languages + +15.3.11 librep Format Strings +----------------------------- + + librep format strings are documented in the librep manual, section +Formatted Output, +, +. + + +File: gettext.info, Node: rust-format, Next: go-format, Prev: librep-format, Up: Translators for other Languages + +15.3.12 Rust Format Strings +--------------------------- + + Rust format strings are those supported by the ‘formatx’ library +. These are those supported by the +‘format!’ built-in with the +restrictions listed in , section +"Limitations". + + A Rust format string consists of + • an opening brace ‘{’, + • an optional non-empty sequence of digits or an optional identifier, + • optionally, a ‘:’ and a format specifier, where a format specifier + is of the form + ‘[[FILL]ALIGN][SIGN][#][0][MINIMUMWIDTH][.PRECISION][TYPE]’ where + - the FILL character is any character, + - the ALIGN flag is one of ‘<’, ‘>’, ‘^’, + - the SIGN is one of ‘+’, ‘-’, + - the # flag is ‘#’, + - the 0 flag is ‘0’, + - MINIMUMWIDTH is a non-empty sequence of digits, + - PRECISION is a non-empty sequence of digits, + - TYPE is ‘?’, + • optional white-space, + • a closing brace ‘}’. +Brace characters ‘{’ and ‘}’ can be escaped by doubling them: ‘{{’ and +‘}}’. + + +File: gettext.info, Node: go-format, Next: ruby-format, Prev: rust-format, Up: Translators for other Languages + +15.3.13 Go Format Strings +------------------------- + + Go format strings are documented on the Go packages site, for package +‘fmt’, at . + + +File: gettext.info, Node: ruby-format, Next: sh-format, Prev: go-format, Up: Translators for other Languages + +15.3.14 Ruby Format Strings +--------------------------- + + Ruby format strings are described in the documentation of the Ruby +functions ‘format’ and ‘sprintf’, in +. + + There are two kinds of format strings in Ruby: + • Those that take a list of arguments without names. They support + argument reordering by use of the ‘%N$’ syntax. Note that if one + argument uses this syntax, all must use this syntax. + • Those that take a hash table, containing named arguments. The + syntax is ‘%’. Note that ‘%{NAME}’ is equivalent to + ‘%s’. + + +File: gettext.info, Node: sh-format, Next: awk-format, Prev: ruby-format, Up: Translators for other Languages + +15.3.15 Shell Format Strings +---------------------------- + + Shell format strings, as supported by GNU gettext and the ‘envsubst’ +program, are strings with references to shell variables in the form +‘$VARIABLE’ or ‘${VARIABLE}’. References of the form +‘${VARIABLE-DEFAULT}’, ‘${VARIABLE:-DEFAULT}’, ‘${VARIABLE=DEFAULT}’, +‘${VARIABLE:=DEFAULT}’, ‘${VARIABLE+REPLACEMENT}’, +‘${VARIABLE:+REPLACEMENT}’, ‘${VARIABLE?IGNORED}’, +‘${VARIABLE:?IGNORED}’, that would be valid inside shell scripts, are +not supported. The VARIABLE names must consist solely of alphanumeric +or underscore ASCII characters, not start with a digit and be nonempty; +otherwise such a variable reference is ignored. + + +File: gettext.info, Node: awk-format, Next: lua-format, Prev: sh-format, Up: Translators for other Languages + +15.3.16 awk Format Strings +-------------------------- + + awk format strings are described in the gawk documentation, section +Printf, . + + +File: gettext.info, Node: lua-format, Next: object-pascal-format, Prev: awk-format, Up: Translators for other Languages + +15.3.17 Lua Format Strings +-------------------------- + + Lua format strings are described in the Lua reference manual, section +String Manipulation, +. + + +File: gettext.info, Node: object-pascal-format, Next: modula2-format, Prev: lua-format, Up: Translators for other Languages + +15.3.18 Object Pascal Format Strings +------------------------------------ + + Object Pascal format strings are described in the documentation of +the Free Pascal runtime library, section Format, +. + + +File: gettext.info, Node: modula2-format, Next: d-format, Prev: object-pascal-format, Up: Translators for other Languages + +15.3.19 Modula-2 Format Strings +------------------------------- + + Modula-2 format strings are defined as follows: + 1. Escape sequences are processed. These escape sequences are + understood: ‘\a’, ‘\b’, ‘\e’, ‘\f’, ‘\n’, ‘\r’, ‘\xHEX-DIGITS’, + ‘\OCTAL-DIGITS’. Other than that, a backslash is ignored. + 2. A directive consists of + • a ‘%’ character, + • optionally a flag character ‘-’, + • optionally a flag character ‘0’, + • optionally a width specification (a nonnegative integer), + • and finally a specifier: ‘s’ that formats a string, ‘c’ that + formats a character, ‘d’ and ‘u’, that format a + (signed/unsigned) integer in decimal, or ‘x’, that formats an + unsigned integer in hexadecimal. + There is also the directive ‘%%’, that produces a single percent + character. + + +File: gettext.info, Node: d-format, Next: smalltalk-format, Prev: modula2-format, Up: Translators for other Languages + +15.3.20 D Format Strings +------------------------ + + D format strings are described in the documentation of the D module +‘std.format’, at . + + +File: gettext.info, Node: smalltalk-format, Next: qt-format, Prev: d-format, Up: Translators for other Languages + +15.3.21 Smalltalk Format Strings +-------------------------------- + + Smalltalk format strings are described in the GNU Smalltalk +documentation, class ‘CharArray’, methods ‘bindWith:’ and +‘bindWithArguments:’. +. +In summary, a directive starts with ‘%’ and is followed by ‘%’ or a +nonzero digit (‘1’ to ‘9’). + + +File: gettext.info, Node: qt-format, Next: qt-plural-format, Prev: smalltalk-format, Up: Translators for other Languages + +15.3.22 Qt Format Strings +------------------------- + + Qt format strings are described in the documentation of the QString +class . In summary, a +directive consists of a ‘%’ followed by a digit. The same directive +cannot occur more than once in a format string. + + +File: gettext.info, Node: qt-plural-format, Next: kde-format, Prev: qt-format, Up: Translators for other Languages + +15.3.23 Qt Format Strings +------------------------- + + Qt format strings are described in the documentation of the +QObject::tr method . In +summary, the only allowed directive is ‘%n’. + + +File: gettext.info, Node: kde-format, Next: kde-kuit-format, Prev: qt-plural-format, Up: Translators for other Languages + +15.3.24 KDE Format Strings +-------------------------- + + KDE 4 format strings are defined as follows: A directive consists of +a ‘%’ followed by a non-zero decimal number. If a ‘%n’ occurs in a +format strings, all of ‘%1’, ..., ‘%(n-1)’ must occur as well, except +possibly one of them. + + +File: gettext.info, Node: kde-kuit-format, Next: boost-format, Prev: kde-format, Up: Translators for other Languages + +15.3.25 KUIT Format Strings +--------------------------- + + KUIT (KDE User Interface Text) is compatible with KDE 4 format +strings, while it also allows programmers to add semantic information to +a format string, through XML markup tags. For example, if the first +format directive in a string is a filename, programmers could indicate +that with a ‘filename’ tag, like ‘%1’. + + KUIT format strings are described in +. + + +File: gettext.info, Node: boost-format, Next: tcl-format, Prev: kde-kuit-format, Up: Translators for other Languages + +15.3.26 Boost Format Strings +---------------------------- + + Boost format strings are described in the documentation of the +‘boost::format’ class, at +. In summary, a +directive has either the same syntax as in a C format string, such as +‘%1$+5d’, or may be surrounded by vertical bars, such as ‘%|1$+5d|’ or +‘%|1$+5|’, or consists of just an argument number between percent signs, +such as ‘%1%’. + + +File: gettext.info, Node: tcl-format, Next: perl-format, Prev: boost-format, Up: Translators for other Languages + +15.3.27 Tcl Format Strings +-------------------------- + + Tcl format strings are described in the ‘format.n’ manual page, +. + + +File: gettext.info, Node: perl-format, Next: php-format, Prev: tcl-format, Up: Translators for other Languages + +15.3.28 Perl Format Strings +--------------------------- + + There are two kinds of format strings in Perl: those acceptable to +the Perl built-in function ‘printf’, labelled as ‘perl-format’, and +those acceptable to the ‘libintl-perl’ function ‘__x’, labelled as +‘perl-brace-format’. + + Perl ‘printf’ format strings are described in the ‘sprintf’ section +of ‘man perlfunc’. + + Perl brace format strings are described in the +‘Locale::TextDomain(3pm)’ manual page of the CPAN package libintl-perl. +In brief, Perl format uses placeholders put between braces (‘{’ and +‘}’). The placeholder must have the syntax of simple identifiers. + + +File: gettext.info, Node: php-format, Next: gcc-internal-format, Prev: perl-format, Up: Translators for other Languages + +15.3.29 PHP Format Strings +-------------------------- + + PHP format strings are described in the documentation of the PHP +function ‘sprintf’, in ‘phpdoc/manual/function.sprintf.html’ or +. + + +File: gettext.info, Node: gcc-internal-format, Next: gfc-internal-format, Prev: php-format, Up: Translators for other Languages + +15.3.30 GCC internal Format Strings +----------------------------------- + + These format strings are used inside the GCC sources. In such a +format string, a directive starts with ‘%’, is optionally followed by a +size specifier ‘l’, an optional flag ‘+’, another optional flag ‘#’, and +is finished by a specifier: ‘%’ denotes a literal percent sign, ‘c’ +denotes a character, ‘s’ denotes a string, ‘i’ and ‘d’ denote an +integer, ‘o’, ‘u’, ‘x’ denote an unsigned integer, ‘.*s’ denotes a +string preceded by a width specification, ‘H’ denotes a ‘location_t *’ +pointer, ‘D’ denotes a general declaration, ‘F’ denotes a function +declaration, ‘T’ denotes a type, ‘A’ denotes a function argument, ‘C’ +denotes a tree code, ‘E’ denotes an expression, ‘L’ denotes a +programming language, ‘O’ denotes a binary operator, ‘P’ denotes a +function parameter, ‘Q’ denotes an assignment operator, ‘V’ denotes a +const/volatile qualifier. + + +File: gettext.info, Node: gfc-internal-format, Next: ycp-format, Prev: gcc-internal-format, Up: Translators for other Languages + +15.3.31 GFC internal Format Strings +----------------------------------- + + These format strings are used inside the GNU Fortran Compiler +sources, that is, the Fortran frontend in the GCC sources. In such a +format string, a directive starts with ‘%’ and is finished by a +specifier: ‘%’ denotes a literal percent sign, ‘C’ denotes the current +source location, ‘L’ denotes a source location, ‘c’ denotes a character, +‘s’ denotes a string, ‘i’ and ‘d’ denote an integer, ‘u’ denotes an +unsigned integer. ‘i’, ‘d’, and ‘u’ may be preceded by a size specifier +‘l’. + + +File: gettext.info, Node: ycp-format, Prev: gfc-internal-format, Up: Translators for other Languages + +15.3.32 YCP Format Strings +-------------------------- + + YCP sformat strings are described in the libycp documentation +. In summary, a +directive starts with ‘%’ and is followed by ‘%’ or a nonzero digit (‘1’ +to ‘9’). + + +File: gettext.info, Node: Maintainers for other Languages, Next: List of Programming Languages, Prev: Translators for other Languages, Up: Programming Languages + +15.4 The Maintainer's View +========================== + + For the maintainer, the general procedure differs from the C language +case: + + • If only a single programming language is used, the + ‘XGETTEXT_OPTIONS’ variable in ‘po/Makevars’ (*note po/Makevars::) + should be adjusted to match the ‘xgettext’ options for that + particular programming language. If the package uses more than one + programming language with ‘gettext’ support, it becomes necessary + to change the POT file construction rule in ‘po/Makefile.in.in’. + It is recommended to make one ‘xgettext’ invocation per programming + language, each with the options appropriate for that language, and + to combine the resulting files using ‘msgcat’. + + +File: gettext.info, Node: List of Programming Languages, Prev: Maintainers for other Languages, Up: Programming Languages + +15.5 Individual Programming Languages +===================================== + +* Menu: + +* C:: C, C++, Objective C +* Python:: Python +* Java:: Java +* C#:: C# +* JavaScript:: JavaScript +* TypeScript:: TypeScript +* Scheme:: GNU guile - Scheme +* Common Lisp:: GNU clisp - Common Lisp +* clisp C:: GNU clisp C sources +* Emacs Lisp:: Emacs Lisp +* librep:: librep +* Rust:: Rust +* Go:: Go +* Ruby:: Ruby +* sh:: sh - Shell Script +* bash:: bash - Bourne-Again Shell Script +* gawk:: GNU awk +* Lua:: Lua +* Pascal:: Pascal - Free Pascal Compiler +* Modula-2:: Modula-2 +* D:: D +* Smalltalk:: GNU Smalltalk +* Vala:: Vala +* wxWidgets:: wxWidgets library +* Tcl:: Tcl - Tk's scripting language +* Perl:: Perl +* PHP:: PHP Hypertext Preprocessor +* Pike:: Pike +* GCC-source:: GNU Compiler Collection sources +* YCP:: YCP - YaST2 scripting language + + +File: gettext.info, Node: C, Next: Python, Up: List of Programming Languages + +15.5.1 C, C++, Objective C +-------------------------- + +RPMs + gcc, gpp, gobjc, glibc, gettext + +Ubuntu packages + gcc, g++, gobjc, libc6-dev, libasprintf-dev + +File extension + For C: ‘c’, ‘h’. + For C++: ‘C’, ‘c++’, ‘cc’, ‘cxx’, ‘cpp’, ‘hpp’. + For Objective C: ‘m’. + +String syntax + ‘"abc"’ + +gettext shorthand + ‘_("abc")’ + +gettext/ngettext functions + ‘gettext’, ‘dgettext’, ‘dcgettext’, ‘ngettext’, ‘dngettext’, + ‘dcngettext’ + +textdomain + ‘textdomain’ function + +bindtextdomain + ‘bindtextdomain’ and ‘wbindtextdomain’ functions + +setlocale + Programmer must call ‘setlocale (LC_ALL, "")’ + +Prerequisite + ‘#include ’ + ‘#include ’ + ‘#define _(string) gettext (string)’ + +Use or emulate GNU gettext + Use + +Extractor + ‘xgettext -k_’ + +Formatting with positions + ‘fprintf "%2$d %1$d"’ + In C++: ‘autosprintf "%2$d %1$d"’ (*note Introduction: + (autosprintf)Top.) + In C++ 20 or newer: ‘std::vformat "{1} {0}"’ + +Portability + autoconf (gettext.m4) and #if ENABLE_NLS + +po-mode marking + yes + + The following examples are available in the ‘examples’ directory: +‘hello-c’, ‘hello-c-gnome2’, ‘hello-c-gnome3’, ‘hello-c-http’, +‘hello-c++’, ‘hello-c++20’, ‘hello-c++-qt’, ‘hello-c++-kde’, +‘hello-c++-gnome2’, ‘hello-c++-gnome3’, ‘hello-c++-wxwidgets’, +‘hello-objc’, ‘hello-objc-gnustep’, ‘hello-objc-gnome2’. + + +File: gettext.info, Node: Python, Next: Java, Prev: C, Up: List of Programming Languages + +15.5.2 Python +------------- + +RPMs + python + +Ubuntu packages + python + +File extension + ‘py’ + +String syntax + ‘'abc'’, ‘u'abc'’, ‘r'abc'’, ‘ur'abc'’, + ‘"abc"’, ‘u"abc"’, ‘r"abc"’, ‘ur"abc"’, + ‘'''abc'''’, ‘u'''abc'''’, ‘r'''abc'''’, ‘ur'''abc'''’, + ‘"""abc"""’, ‘u"""abc"""’, ‘r"""abc"""’, ‘ur"""abc"""’ + +gettext shorthand + ‘_('abc')’ etc. + +gettext/ngettext functions + ‘gettext.gettext’, ‘gettext.dgettext’, ‘gettext.ngettext’, + ‘gettext.dngettext’, also ‘ugettext’, ‘ungettext’ + +textdomain + ‘gettext.textdomain’ function, or ‘gettext.install(DOMAIN)’ + function + +bindtextdomain + ‘gettext.bindtextdomain’ function, or + ‘gettext.install(DOMAIN,LOCALEDIR)’ function + +setlocale + not used by the gettext emulation + +Prerequisite + ‘import gettext’ + +Use or emulate GNU gettext + emulate + +Extractor + ‘xgettext’ + +Formatting with positions + ‘'...%(ident)d...' % { 'ident': value }’ + ‘'...{ident}...'.format(ident=value)’ (see PEP 3101) + +Portability + fully portable + +po-mode marking + -- + + An example is available in the ‘examples’ directory: ‘hello-python’. + + A note about format strings: Python supports format strings with +unnamed arguments, such as ‘'...%d...'’, and format strings with named +arguments, such as ‘'...%(ident)d...'’. The latter are preferable for +internationalized programs, for two reasons: + + • When a format string takes more than one argument, the translator + can provide a translation that uses the arguments in a different + order, if the format string uses named arguments. For example, the + translator can reformulate + "'%(volume)s' has only %(freespace)d bytes free." + to + "Only %(freespace)d bytes free on '%(volume)s'." + Additionally, the identifiers also provide some context to the + translator. + + • In the context of plural forms, the format string used for the + singular form does not use the numeric argument in many languages. + Even in English, one prefers to write ‘"one hour"’ instead of ‘"1 + hour"’. Omitting individual arguments from format strings like + this is only possible with the named argument syntax. (With + unnamed arguments, Python - unlike C - verifies that the format + string uses all supplied arguments.) + + A note about f-strings (PEP 498): ‘xgettext’ + • syntactically recognizes f-strings, + • is able to extract f-strings that contain no sub-expressions. +However, ‘xgettext’ does not extract f-strings marked for translation +that contain sub-expressions. This will not work as expected: + _(f"The file {file[i]} does not exist.") +because the translator is generally not a programmer and should thus not +be confronted with expressions from the programming language. + +Related software +---------------- + + An internationalization system based on GNU gettext and PO files is +Babel (https://babel.pocoo.org/). + + +File: gettext.info, Node: Java, Next: C#, Prev: Python, Up: List of Programming Languages + +15.5.3 Java +----------- + +RPMs + java, java2 + +Ubuntu packages + default-jdk + +File extension + ‘java’ + +String syntax + "abc", """text block""" + +gettext shorthand + i18n("abc") + +gettext/ngettext functions + ‘GettextResource.gettext’, ‘GettextResource.ngettext’, + ‘GettextResource.pgettext’, ‘GettextResource.npgettext’ + +textdomain + --, use ‘ResourceBundle.getResource’ instead + +bindtextdomain + --, use CLASSPATH instead + +setlocale + automatic + +Prerequisite + -- + +Use or emulate GNU gettext + --, uses a Java specific message catalog format + +Extractor + ‘xgettext -ki18n’ + +Formatting with positions + ‘MessageFormat.format "{1,number} {0,number}"’ or ‘String.format + "%2$d %1$d"’ + +Portability + fully portable + +po-mode marking + -- + + Before marking strings as internationalizable, uses of the string +concatenation operator need to be converted to ‘MessageFormat’ +applications. For example, ‘"file "+filename+" not found"’ becomes +‘MessageFormat.format("file {0} not found", new Object[] { filename })’. +Only after this is done, can the strings be marked and extracted. + + GNU gettext uses the native Java internationalization mechanism, +namely ‘ResourceBundle’s. There are two formats of ‘ResourceBundle’s: +‘.properties’ files and ‘.class’ files. The ‘.properties’ format is a +text file which the translators can directly edit, like PO files, but +which doesn't support plural forms. Whereas the ‘.class’ format is +compiled from ‘.java’ source code and can support plural forms (provided +it is accessed through an appropriate API, see below). + + To convert a PO file to a ‘.properties’ file, the ‘msgcat’ program +can be used with the option ‘--properties-output’. To convert a +‘.properties’ file back to a PO file, the ‘msgcat’ program can be used +with the option ‘--properties-input’. All the tools that manipulate PO +files can work with ‘.properties’ files as well, if given the +‘--properties-input’ and/or ‘--properties-output’ option. + + To convert a PO file to a ResourceBundle class, the ‘msgfmt’ program +can be used with the option ‘--java’ or ‘--java2’. To convert a +ResourceBundle back to a PO file, the ‘msgunfmt’ program can be used +with the option ‘--java’. + + Two different programmatic APIs can be used to access +ResourceBundles. Note that both APIs work with all kinds of +ResourceBundles, whether GNU gettext generated classes, or other +‘.class’ or ‘.properties’ files. + + 1. The ‘java.util.ResourceBundle’ API. + + In particular, its ‘getString’ function returns a string + translation. Note that a missing translation yields a + ‘MissingResourceException’. + + This has the advantage of being the standard API. And it does not + require any additional libraries, only the ‘msgcat’ generated + ‘.properties’ files or the ‘msgfmt’ generated ‘.class’ files. But + it cannot do plural handling, even if the resource was generated by + ‘msgfmt’ from a PO file with plural handling. + + 2. The ‘gnu.gettext.GettextResource’ API. + + Reference documentation in Javadoc 1.1 style format is in the + javadoc2 directory (javadoc2/index.html). + + Its ‘gettext’ function returns a string translation. Note that + when a translation is missing, the MSGID argument is returned + unchanged. + + This has the advantage of having the ‘ngettext’ function for plural + handling and the ‘pgettext’ and ‘npgettext’ for strings constraint + to a particular context. + + To use this API, one needs the ‘libintl.jar’ file which is part of + the GNU gettext package and distributed under the LGPL. + + Four examples, using the second API, are available in the ‘examples’ +directory: ‘hello-java’, ‘hello-java-awt’, ‘hello-java-swing’, +‘hello-java-qtjambi’. + + Now, to make use of the API and define a shorthand for ‘getString’, +there are three idioms that you can choose from: + + • (This one assumes Java 1.5 or newer.) In a unique class of your + project, say ‘Util’, define a static variable holding the + ‘ResourceBundle’ instance and the shorthand: + + private static ResourceBundle myResources = + ResourceBundle.getBundle("domain-name"); + public static String i18n(String s) { + return myResources.getString(s); + } + + All classes containing internationalized strings then contain + + import static Util.i18n; + + and the shorthand is used like this: + + System.out.println(i18n("Operation completed.")); + + • In a unique class of your project, say ‘Util’, define a static + variable holding the ‘ResourceBundle’ instance: + + public static ResourceBundle myResources = + ResourceBundle.getBundle("domain-name"); + + All classes containing internationalized strings then contain + + private static ResourceBundle res = Util.myResources; + private static String i18n(String s) { return res.getString(s); } + + and the shorthand is used like this: + + System.out.println(i18n("Operation completed.")); + + • You add a class with a very short name, say ‘S’, containing just + the definition of the resource bundle and of the shorthand: + + public class S { + public static ResourceBundle myResources = + ResourceBundle.getBundle("domain-name"); + public static String i18n(String s) { + return myResources.getString(s); + } + } + + and the shorthand is used like this: + + System.out.println(S.i18n("Operation completed.")); + + Which of the three idioms you choose, will depend on whether your +project requires portability to Java versions prior to Java 1.5 and, if +so, whether copying two lines of codes into every class is more +acceptable in your project than a class with a single-letter name. + + +File: gettext.info, Node: C#, Next: JavaScript, Prev: Java, Up: List of Programming Languages + +15.5.4 C# +--------- + +RPMs + mono or dotnet8.0 + +Ubuntu packages + mono-mcs or dotnet8 + +File extension + ‘cs’ + +String syntax + ‘"abc"’, ‘@"abc"’ + +gettext shorthand + _("abc") + +gettext/ngettext functions + ‘GettextResourceManager.GetString’, + ‘GettextResourceManager.GetPluralString’ + ‘GettextResourceManager.GetParticularString’ + ‘GettextResourceManager.GetParticularPluralString’ + +textdomain + ‘new GettextResourceManager(domain)’ + +bindtextdomain + --, compiled message catalogs are located in subdirectories of the + directory containing the executable + +setlocale + automatic + +Prerequisite + -- + +Use or emulate GNU gettext + --, uses a C# specific message catalog format + +Extractor + ‘xgettext -k_’ + +Formatting with positions + ‘String.Format "{1} {0}"’ + +Portability + fully portable + +po-mode marking + -- + + Before marking strings as internationalizable, uses of the string +concatenation operator need to be converted to ‘String.Format’ +invocations. For example, ‘"file "+filename+" not found"’ becomes +‘String.Format("file {0} not found", filename)’. Only after this is +done, can the strings be marked and extracted. + + GNU gettext uses the native C#/.NET internationalization mechanism, +namely the classes ‘ResourceManager’ and ‘ResourceSet’. Applications +use the ‘ResourceManager’ methods to retrieve the native language +translation of strings. An instance of ‘ResourceSet’ is the in-memory +representation of a message catalog file. The ‘ResourceManager’ loads +and accesses ‘ResourceSet’ instances as needed to look up the +translations. + + There are two formats of ‘ResourceSet’s that can be directly loaded +by the C# runtime: ‘.resources’ files and ‘.dll’ files. + + • The ‘.resources’ format is a binary file usually generated through + the ‘resgen’ or ‘monoresgen’ utility, but which doesn't support + plural forms. ‘.resources’ files can also be embedded in .NET + ‘.exe’ files. This only affects whether a file system access is + performed to load the message catalog; it doesn't affect the + contents of the message catalog. + + • On the other hand, the ‘.dll’ format is a binary file that is + compiled from ‘.cs’ source code and can support plural forms + (provided it is accessed through the GNU gettext API, see below). + + Note that these .NET ‘.dll’ and ‘.exe’ files are not tied to a +particular platform; their file format and GNU gettext for C# can be +used on any platform. + + To convert a PO file to a ‘.resources’ file, the ‘msgfmt’ program can +be used with the option ‘--csharp-resources’. To convert a ‘.resources’ +file back to a PO file, the ‘msgunfmt’ program can be used with the +option ‘--csharp-resources’. You can also, in some cases, use the +‘monoresgen’ program (from the ‘mono’/‘mcs’ package). This program can +also convert a ‘.resources’ file back to a PO file. But beware: as of +this writing (January 2004), the ‘monoresgen’ converter is quite buggy. + + To convert a PO file to a ‘.dll’ file, the ‘msgfmt’ program can be +used with the option ‘--csharp’. The result will be a ‘.dll’ file +containing a subclass of ‘GettextResourceSet’, which itself is a +subclass of ‘ResourceSet’. To convert a ‘.dll’ file containing a +‘GettextResourceSet’ subclass back to a PO file, the ‘msgunfmt’ program +can be used with the option ‘--csharp’. + + The advantages of the ‘.dll’ format over the ‘.resources’ format are: + + 1. Freedom to localize: Users can add their own translations to an + application after it has been built and distributed. Whereas when + the programmer uses a ‘ResourceManager’ constructor provided by the + system, the set of ‘.resources’ files for an application must be + specified when the application is built and cannot be extended + afterwards. + + 2. Plural handling: A message catalog in ‘.dll’ format supports the + plural handling function ‘GetPluralString’. Whereas ‘.resources’ + files can only contain data and only support lookups that depend on + a single string. + + 3. Context handling: A message catalog in ‘.dll’ format supports the + query-with-context functions ‘GetParticularString’ and + ‘GetParticularPluralString’. Whereas ‘.resources’ files can only + contain data and only support lookups that depend on a single + string. + + 4. The ‘GettextResourceManager’ that loads the message catalogs in + ‘.dll’ format also provides for inheritance on a per-message basis. + For example, in Austrian (‘de_AT’) locale, translations from the + German (‘de’) message catalog will be used for messages not found + in the Austrian message catalog. This has the consequence that the + Austrian translators need only translate those few messages for + which the translation into Austrian differs from the German one. + Whereas when working with ‘.resources’ files, each message catalog + must provide the translations of all messages by itself. + + 5. The ‘GettextResourceManager’ that loads the message catalogs in + ‘.dll’ format also provides for a fallback: The English MSGID is + returned when no translation can be found. Whereas when working + with ‘.resources’ files, a language-neutral ‘.resources’ file must + explicitly be provided as a fallback. + + On the side of the programmatic APIs, the programmer can use either +the standard ‘ResourceManager’ API and the GNU ‘GettextResourceManager’ +API. The latter is an extension of the former, because +‘GettextResourceManager’ is a subclass of ‘ResourceManager’. + + 1. The ‘System.Resources.ResourceManager’ API. + + This API works with resources in ‘.resources’ format. + + The creation of the ‘ResourceManager’ is done through + new ResourceManager(domainname, Assembly.GetExecutingAssembly()) + + The ‘GetString’ function returns a string's translation. Note that + this function returns null when a translation is missing (i.e. not + even found in the fallback resource file). + + 2. The ‘GNU.Gettext.GettextResourceManager’ API. + + This API works with resources in ‘.dll’ format. + + Reference documentation is in the csharpdoc directory + (csharpdoc/index.html). + + The creation of the ‘ResourceManager’ is done through + new GettextResourceManager(domainname) + + The ‘GetString’ function returns a string's translation. Note that + when a translation is missing, the MSGID argument is returned + unchanged. + + The ‘GetPluralString’ function returns a string translation with + plural handling, like the ‘ngettext’ function in C. + + The ‘GetParticularString’ function returns a string's translation, + specific to a particular context, like the ‘pgettext’ function in + C. Note that when a translation is missing, the MSGID argument is + returned unchanged. + + The ‘GetParticularPluralString’ function returns a string + translation, specific to a particular context, with plural + handling, like the ‘npgettext’ function in C. + + To use this API, one needs the ‘GNU.Gettext.dll’ file which is part + of the GNU gettext package and distributed under the LGPL. + + You can also mix both approaches: use the +‘GNU.Gettext.GettextResourceManager’ constructor, but otherwise use only +the ‘ResourceManager’ type and only the ‘GetString’ method. This is +appropriate when you want to profit from the tools for PO files, but +don't want to change an existing source code that uses ‘ResourceManager’ +and don't (yet) need the ‘GetPluralString’ method. + + Two examples, using the second API, are available in the ‘examples’ +directory: ‘hello-csharp’, ‘hello-csharp-forms’. + + Now, to make use of the API and define a shorthand for ‘GetString’, +there are two idioms that you can choose from: + + • In a unique class of your project, say ‘Util’, define a static + variable holding the ‘ResourceManager’ instance: + + public static GettextResourceManager MyResourceManager = + new GettextResourceManager("domain-name"); + + All classes containing internationalized strings then contain + + private static GettextResourceManager Res = Util.MyResourceManager; + private static String _(String s) { return Res.GetString(s); } + + and the shorthand is used like this: + + Console.WriteLine(_("Operation completed.")); + + • You add a class with a very short name, say ‘S’, containing just + the definition of the resource manager and of the shorthand: + + public class S { + public static GettextResourceManager MyResourceManager = + new GettextResourceManager("domain-name"); + public static String _(String s) { + return MyResourceManager.GetString(s); + } + } + + and the shorthand is used like this: + + Console.WriteLine(S._("Operation completed.")); + + Which of the two idioms you choose, will depend on whether copying +two lines of codes into every class is more acceptable in your project +than a class with a single-letter name. + + +File: gettext.info, Node: JavaScript, Next: TypeScript, Prev: C#, Up: List of Programming Languages + +15.5.5 JavaScript +----------------- + +RPMs + js + +Ubuntu packages + gjs + +File extension + ‘js’ + +String syntax + + • ‘"abc"’ + + • ‘'abc'’ + + • ‘`abc`’ + + • ‘TAG`abc${EXPRESSION}def{EXPRESSION}...`’, see the description + of ‘--tag’ in *note xgettext Invocation::. + +gettext shorthand + ‘_("abc")’ + +gettext/ngettext functions + ‘gettext’, ‘dgettext’, ‘dcgettext’, ‘ngettext’, ‘dngettext’ + +textdomain + ‘textdomain’ function + +bindtextdomain + ‘bindtextdomain’ function + +setlocale + automatic + +Prerequisite + -- + +Use or emulate GNU gettext + use, or emulate + +Extractor + ‘xgettext’ + +Formatting with positions + A ‘format’ method on strings can be used. But since it is not + standard in JavaScript, you have to enable it yourself, through + + const Format = imports.format; + String.prototype.format = Format.format; + +Portability + On platforms without gettext, the functions are not available. + +po-mode marking + -- + + +File: gettext.info, Node: TypeScript, Next: Scheme, Prev: JavaScript, Up: List of Programming Languages + +15.5.6 TypeScript and TSX +------------------------- + +RPMs + js + +Ubuntu packages + gjs + +File extension + ‘ts’ for TypeScript, ‘tsx’ for TSX (TypeScript with JSX) + +String syntax + + • ‘"abc"’ + + • ‘'abc'’ + + • ‘`abc`’ + +gettext shorthand + ‘_("abc")’ + +gettext/ngettext functions + ‘gettext’, ‘dgettext’, ‘dcgettext’, ‘ngettext’, ‘dngettext’ + +textdomain + ‘textdomain’ function + +bindtextdomain + ‘bindtextdomain’ function + +setlocale + automatic + +Prerequisite + unknown + +Use or emulate GNU gettext + use, or emulate + +Extractor + ‘xgettext’ + +Formatting with positions + A ‘format’ method on strings can be used. But since it is not + standard in TypeScript, you have to enable it yourself. + +Portability + On platforms without gettext, the functions are not available. + +po-mode marking + -- + + +File: gettext.info, Node: Scheme, Next: Common Lisp, Prev: TypeScript, Up: List of Programming Languages + +15.5.7 GNU guile - Scheme +------------------------- + +RPMs + guile + +Ubuntu packages + guile-2.0 + +File extension + ‘scm’ + +String syntax + ‘"abc"’ + +gettext shorthand + ‘(_ "abc")’, ‘_"abc"’ (GIMP script-fu extension) + +gettext/ngettext functions + ‘gettext’, ‘ngettext’ + +textdomain + ‘textdomain’ + +bindtextdomain + ‘bindtextdomain’ + +setlocale + ‘(catch #t (lambda () (setlocale LC_ALL "")) (lambda args #f))’ + +Prerequisite + ‘(use-modules (ice-9 format))’ + +Use or emulate GNU gettext + use + +Extractor + ‘xgettext -L Guile -k_’ + + ‘xgettext -L Scheme’ and ‘xgettext -L Guile’ are nearly equivalent. + They differ in the interpretation of escape sequences in string + literals: While ‘xgettext -L Scheme’ assumes the R6RS and R7RS + syntax of string literals, ‘xgettext -L Guile’ assumes the syntax + of string literals understood by Guile 2.x and 3.0 (without + command-line option ‘--r6rs’ or ‘--r7rs’, and before a ‘#!r6rs’ + directive is seen). After a ‘#!r6rs’ directive, there is no + difference any more between ‘xgettext -L Scheme’ and ‘xgettext -L + Guile’ for the rest of the file. + +Formatting with positions + -- + +Portability + On platforms without gettext, no translation. + +po-mode marking + -- + + An example is available in the ‘examples’ directory: ‘hello-guile’. + + +File: gettext.info, Node: Common Lisp, Next: clisp C, Prev: Scheme, Up: List of Programming Languages + +15.5.8 GNU clisp - Common Lisp +------------------------------ + +RPMs + clisp 2.28 or newer + +Ubuntu packages + clisp + +File extension + ‘lisp’ + +String syntax + ‘"abc"’ + +gettext shorthand + ‘(_ "abc")’, ‘(ENGLISH "abc")’ + +gettext/ngettext functions + ‘i18n:gettext’, ‘i18n:ngettext’ + +textdomain + ‘i18n:textdomain’ + +bindtextdomain + ‘i18n:textdomaindir’ + +setlocale + automatic + +Prerequisite + -- + +Use or emulate GNU gettext + use + +Extractor + ‘xgettext -k_ -kENGLISH’ + +Formatting with positions + ‘format "~1@*~D ~0@*~D"’ + +Portability + On platforms without gettext, no translation. + +po-mode marking + -- + + An example is available in the ‘examples’ directory: ‘hello-clisp’. + + +File: gettext.info, Node: clisp C, Next: Emacs Lisp, Prev: Common Lisp, Up: List of Programming Languages + +15.5.9 GNU clisp C sources +-------------------------- + +RPMs + clisp + +Ubuntu packages + clisp + +File extension + ‘d’ + +String syntax + ‘"abc"’ + +gettext shorthand + ‘ENGLISH ? "abc" : ""’ + ‘GETTEXT("abc")’ + ‘GETTEXTL("abc")’ + +gettext/ngettext functions + ‘clgettext’, ‘clgettextl’ + +textdomain + -- + +bindtextdomain + -- + +setlocale + automatic + +Prerequisite + ‘#include "lispbibl.c"’ + +Use or emulate GNU gettext + use + +Extractor + ‘clisp-xgettext’ + +Formatting with positions + ‘fprintf "%2$d %1$d"’ + +Portability + On platforms without gettext, no translation. + +po-mode marking + -- + + +File: gettext.info, Node: Emacs Lisp, Next: librep, Prev: clisp C, Up: List of Programming Languages + +15.5.10 Emacs Lisp +------------------ + +RPMs + emacs, xemacs + +Ubuntu packages + emacs, xemacs21 + +File extension + ‘el’ + +String syntax + ‘"abc"’ + +gettext shorthand + ‘(_"abc")’ + +gettext/ngettext functions + ‘gettext’, ‘dgettext’ (xemacs only) + +textdomain + ‘domain’ special form (xemacs only) + +bindtextdomain + ‘bind-text-domain’ function (xemacs only) + +setlocale + automatic + +Prerequisite + -- + +Use or emulate GNU gettext + use + +Extractor + ‘xgettext’ + +Formatting with positions + ‘format "%2$d %1$d"’ + +Portability + Only XEmacs. Without ‘I18N3’ defined at build time, no + translation. + +po-mode marking + -- + + +File: gettext.info, Node: librep, Next: Rust, Prev: Emacs Lisp, Up: List of Programming Languages + +15.5.11 librep +-------------- + +RPMs + librep 0.15.3 or newer + +Ubuntu packages + librep16 + +File extension + ‘jl’ + +String syntax + ‘"abc"’ + +gettext shorthand + ‘(_"abc")’ + +gettext/ngettext functions + ‘gettext’ + +textdomain + ‘textdomain’ function + +bindtextdomain + ‘bindtextdomain’ function + +setlocale + -- + +Prerequisite + ‘(require 'rep.i18n.gettext)’ + +Use or emulate GNU gettext + use + +Extractor + ‘xgettext’ + +Formatting with positions + ‘format "%2$d %1$d"’ + +Portability + On platforms without gettext, no translation. + +po-mode marking + -- + + An example is available in the ‘examples’ directory: ‘hello-librep’. + + +File: gettext.info, Node: Rust, Next: Go, Prev: librep, Up: List of Programming Languages + +15.5.12 Rust +------------ + +RPMs + rust, rust-cargo + +Ubuntu packages + rustc, cargo + +File extension + ‘rs’ + +String syntax + ‘"abc"’, ‘r"abc"’, ‘r#"abc"#’ etc. + +gettext shorthand + -- + +gettext/ngettext functions + ‘gettext’, ‘ngettext’ + +textdomain + ‘textdomain’ function + +bindtextdomain + ‘bindtextdomain’ function + +setlocale + ‘setlocale’ function + +Prerequisite + ‘$ cargo add gettext-rs’ + + ‘use gettextrs::*;’ + + Note: We recommend the ‘gettext-rs’ crate. We do not recommend the + ‘gettext’ crate, because (as of 2025) it does not handle catalog + fallback (e.g. from ‘de_AT’ to ‘de’) nor the ‘LANGUAGE’ + environment variable. + +Use or emulate GNU gettext + use + +Extractor + ‘xgettext’ + +Formatting with positions + There are three common ways of doing string formatting in Rust: + • Using the built-ins ‘format!’, ‘println!’, etc. This facility + supports only constant strings, known at compile-time. Thus + it cannot be used with translated format strings. You would + get an error such as "error: format argument must be a string + literal". + • Using the ‘strfmt’ library. The facility cannot be + recommended, because it does not support the case where some + of the values are strings and some of the values are numbers + (without an excessive amount of contortions). + • Using the ‘formatx’ library. This is the one we recommend. + + So, you have to convert the ‘format!’, ‘println!’, etc. + invocations to use ‘formatx’. For example, + println!("Hello {}, you got {} coins.", name, left); + becomes + println!("{}", formatx!(gettext("Hello {}, you got {} coins."), + name, left) + .unwrap()); + + For swapped positions, a translator may translate ‘"Hello {}, you + got {} coins."’ with ‘"Hello, {1} coins are left for you, {0}."’ + +Portability + fully portable + +po-mode marking + -- + + An example is available in the ‘examples’ directory: ‘hello-rust’. + + +File: gettext.info, Node: Go, Next: Ruby, Prev: Rust, Up: List of Programming Languages + +15.5.13 Go +---------- + + Three packages are available, that can be used for message +localization with PO files: + • The ‘github.com/leonelquinteros/gotext’ package. + + Documentation: + + + Source code: + • The ‘github.com/gosexy/gettext’ package. + + Documentation: + + Source code: + • The ‘github.com/snapcore/go-gettext’ package. + + Documentation: + + Source code: + + Go programs can be classified as one of: + • _Single-locale_ programs, that use the same locale across all + threads of the program. Example: Most command-line programs. + • _Multi-locale_ programs, that use one locale per thread. Example: + Web servers. + + The three different packages support these two classes of programs +differently: + • ‘github.com/leonelquinteros/gotext’ package: It has two different + APIs, one for the single-locale case and one for the multi-locale + case. + • ‘github.com/gosexy/gettext’ package: Its API supports only the + single-locale case. + • ‘github.com/snapcore/go-gettext’ package: Its API supports the + single-locale case and the multi-locale case in the same way. + +Gettext support characteristics: +-------------------------------- + +RPMs + golang + +Ubuntu packages + golang-go (which provides the ‘go’ program), or gccgo (which + provides a ‘go-VERSION’ command). + gccgo has better portability; for example it works on SPARC CPUs. + +File extension + ‘go’ + +String syntax + ‘"abc"’, ‘`abc`’ + +gettext shorthand + -- + +gettext/ngettext functions + This depends on the API: + • ‘github.com/leonelquinteros/gotext’ API: ‘Get’, ‘GetD’, + ‘GetN’, ‘GetND’ + • ‘github.com/gosexy/gettext’ API: ‘Gettext’, ‘DGettext’, + ‘DCGettext’, ‘NGettext’, ‘DNGettext’, ‘DCNGettext’ + • ‘github.com/snapcore/go-gettext’ API: ‘Gettext’, ‘NGettext’ + + Note that the ‘ngettext’-like functions need to take two argument + strings that consume the same number of arguments. For example, + you cannot write ‘fmt.Sprintf(gotext.GetN("a piece", "%d pieces", + n), n)’ because in the singular case, ‘fmt.Sprintf’ would treat the + unused argument as an error and produce ‘"a piece%!(EXTRA int=1)"’ + instead of the desired ‘"a piece"’. As a workaround, you need to + convert ‘n’ to a string and format that string with precision zero: + ‘fmt.Sprintf(gotext.GetN("%.0sa piece", "%s pieces", n), + strconv.Itoa(n))’ + +textdomain + This depends on the API: + • ‘github.com/leonelquinteros/gotext’ API: ‘Locale.AddDomain’ + method or ‘gotext.Configure’ function + • ‘github.com/gosexy/gettext’ API: ‘Textdomain’ function + • ‘github.com/snapcore/go-gettext’ API: ‘TextDomain’ constructor + +bindtextdomain + This depends on the API: + • ‘github.com/leonelquinteros/gotext’ API: ‘gotext.NewLocale’ + function or ‘gotext.Configure’ function + • ‘github.com/gosexy/gettext’ API: ‘BindTextdomain’ function + • ‘github.com/snapcore/go-gettext’ API: ‘TextDomain’ constructor + +setlocale + This depends on the API: + • ‘github.com/leonelquinteros/gotext’ API: Programmer must + determine the appropriate locale and pass it to the + ‘gotext.NewLocale’ function or ‘gotext.Configure’ function. + • ‘github.com/gosexy/gettext’ API: Programmer must call + ‘gettext.SetLocale(gettext.LcAll, "")’. + • ‘github.com/snapcore/go-gettext’ API: Programmer must + determine the appropriate locale and pass it to the + ‘TextDomain.Locale’ method. + +Prerequisite + This depends on the API: + • ‘github.com/leonelquinteros/gotext’ API: ‘import + ("github.com/leonelquinteros/gotext")’ + • ‘github.com/gosexy/gettext’ API: ‘import + ("github.com/gosexy/gettext")’ + • ‘github.com/snapcore/go-gettext’ API: ‘import + ("github.com/snapcore/go-gettext")’ + +Use or emulate GNU gettext + This depends on the API: + • ‘github.com/leonelquinteros/gotext’ API: Emulate + • ‘github.com/gosexy/gettext’ API: Use + • ‘github.com/snapcore/go-gettext’ API: Emulate + +Extractor + ‘xgettext’ + +Formatting with positions + ‘fmt.Sprintf("%[2]d %[1]d", ...)’ + +Portability + fully portable + +po-mode marking + -- + + Two examples are available in the ‘examples’ directory: ‘hello-go’ +and ‘hello-go-http’. + + +File: gettext.info, Node: Ruby, Next: sh, Prev: Go, Up: List of Programming Languages + +15.5.14 Ruby +------------ + +RPMs + ruby, ruby-gettext + +Ubuntu packages + ruby, ruby-gettext + +File extension + ‘rb’ + +String syntax + ‘"abc"’, ‘'abc'’, ‘%q/abc/’ etc., ‘%q(abc)’, ‘%q[abc]’, ‘%q{abc}’ + +gettext shorthand + ‘_("abc")’ + +gettext/ngettext functions + ‘gettext’, ‘ngettext’ + +textdomain + -- + +bindtextdomain + ‘bindtextdomain’ function + +setlocale + -- + +Prerequisite + ‘require 'gettext'’ ‘include GetText’ + +Use or emulate GNU gettext + emulate + +Extractor + ‘xgettext’ + +Formatting with positions + ‘sprintf("%2$d %1$d", x, y)’ + ‘"%{new} replaces %{old}" % {:old => oldvalue, :new => newvalue}’ + +Portability + fully portable + +po-mode marking + -- + + An example is available in the ‘examples’ directory: ‘hello-ruby’. + + +File: gettext.info, Node: sh, Next: bash, Prev: Ruby, Up: List of Programming Languages + +15.5.15 sh - Shell Script +------------------------- + +RPMs + bash, gettext + +Ubuntu packages + bash, gettext-base + +File extension + ‘sh’ + +String syntax + ‘"abc"’, ‘'abc'’, ‘abc’ + +gettext shorthand + ‘"`gettext \"abc\"`"’ + +gettext/ngettext functions + ‘gettext’, ‘ngettext’ programs + ‘eval_gettext’, ‘eval_ngettext’, ‘eval_pgettext’, ‘eval_npgettext’ + shell functions + +textdomain + environment variable ‘TEXTDOMAIN’ + +bindtextdomain + environment variable ‘TEXTDOMAINDIR’ + +setlocale + automatic + +Prerequisite + ‘. gettext.sh’ + +Use or emulate GNU gettext + use + +Extractor + ‘xgettext’ + +Formatting with positions + -- + +Portability + fully portable + +po-mode marking + -- + + An example is available in the ‘examples’ directory: ‘hello-sh’. + +* Menu: + +* Preparing Shell Scripts:: Preparing Shell Scripts for Internationalization +* gettext.sh:: Contents of ‘gettext.sh’ +* gettext Invocation:: Invoking the ‘gettext’ program +* ngettext Invocation:: Invoking the ‘ngettext’ program +* envsubst Invocation:: Invoking the ‘envsubst’ program +* eval_gettext Invocation:: Invoking the ‘eval_gettext’ function +* eval_ngettext Invocation:: Invoking the ‘eval_ngettext’ function +* eval_pgettext Invocation:: Invoking the ‘eval_pgettext’ function +* eval_npgettext Invocation:: Invoking the ‘eval_npgettext’ function + + +File: gettext.info, Node: Preparing Shell Scripts, Next: gettext.sh, Up: sh + +15.5.15.1 Preparing Shell Scripts for Internationalization +.......................................................... + + Preparing a shell script for internationalization is conceptually +similar to the steps described in *note Sources::. The concrete steps +for shell scripts are as follows. + + 1. Insert the line + + . gettext.sh + + near the top of the script. ‘gettext.sh’ is a shell function + library that provides the functions ‘eval_gettext’ (see *note + eval_gettext Invocation::), ‘eval_ngettext’ (see *note + eval_ngettext Invocation::), ‘eval_pgettext’ (see *note + eval_pgettext Invocation::), and ‘eval_npgettext’ (see *note + eval_npgettext Invocation::). You have to ensure that ‘gettext.sh’ + can be found in the ‘PATH’. + + 2. Set and export the ‘TEXTDOMAIN’ and ‘TEXTDOMAINDIR’ environment + variables. Usually ‘TEXTDOMAIN’ is the package or program name, + and ‘TEXTDOMAINDIR’ is the absolute pathname corresponding to + ‘$prefix/share/locale’, where ‘$prefix’ is the installation + location. + + TEXTDOMAIN=@PACKAGE@ + export TEXTDOMAIN + TEXTDOMAINDIR=@LOCALEDIR@ + export TEXTDOMAINDIR + + 3. Prepare the strings for translation, as described in *note + Preparing Strings::. + + 4. Simplify translatable strings so that they don't contain command + substitution (‘"`...`"’ or ‘"$(...)"’), variable access with + defaulting (like ‘${VARIABLE-DEFAULT}’), access to positional + arguments (like ‘$0’, ‘$1’, ...) or highly volatile shell + variables (like ‘$?’). This can always be done through simple + local code restructuring. For example, + + echo "Usage: $0 [OPTION] FILE..." + + becomes + + program_name=$0 + echo "Usage: $program_name [OPTION] FILE..." + + Similarly, + + echo "Remaining files: `ls | wc -l`" + + becomes + + filecount="`ls | wc -l`" + echo "Remaining files: $filecount" + + 5. For each translatable string, change the output command ‘echo’ or + ‘$echo’ to ‘gettext’ (if the string contains no references to shell + variables) or to ‘eval_gettext’ (if it refers to shell variables), + followed by a no-argument ‘echo’ command (to account for the + terminating newline). Similarly, for cases with plural handling, + replace a conditional ‘echo’ command with an invocation of + ‘ngettext’ or ‘eval_ngettext’, followed by a no-argument ‘echo’ + command. + + When doing this, you also need to add an extra backslash before the + dollar sign in references to shell variables, so that the + ‘eval_gettext’ function receives the translatable string before the + variable values are substituted into it. For example, + + echo "Remaining files: $filecount" + + becomes + + eval_gettext "Remaining files: \$filecount"; echo + + If the output command is not ‘echo’, you can make it use ‘echo’ + nevertheless, through the use of backquotes. However, note that + inside backquotes, backslashes must be doubled to be effective + (because the backquoting eats one level of backslashes). For + example, assuming that ‘error’ is a shell function that signals an + error, + + error "file not found: $filename" + + is first transformed into + + error "`echo \"file not found: \$filename\"`" + + which then becomes + + error "`eval_gettext \"file not found: \\\$filename\"`" + + +File: gettext.info, Node: gettext.sh, Next: gettext Invocation, Prev: Preparing Shell Scripts, Up: sh + +15.5.15.2 Contents of ‘gettext.sh’ +.................................. + + ‘gettext.sh’, contained in the run-time package of GNU gettext, +provides the following: + + • $echo The variable ‘echo’ is set to a command that outputs its + first argument and a newline, without interpreting backslashes in + the argument string. + + • eval_gettext See *note eval_gettext Invocation::. + + • eval_ngettext See *note eval_ngettext Invocation::. + + • eval_pgettext See *note eval_pgettext Invocation::. + + • eval_npgettext See *note eval_npgettext Invocation::. + + +File: gettext.info, Node: gettext Invocation, Next: ngettext Invocation, Prev: gettext.sh, Up: sh + +15.5.15.3 Invoking the ‘gettext’ program +........................................ + + gettext [OPTION] [[TEXTDOMAIN] MSGID] + gettext [OPTION] -s [MSGID]... + + The ‘gettext’ program displays the native language translation of a +textual message. + +*Arguments* + +‘-c CONTEXT’ +‘--context=CONTEXT’ + Specify the context for the messages to be translated. See *note + Contexts:: for details. + +‘-d TEXTDOMAIN’ +‘--domain=TEXTDOMAIN’ + Retrieve translated messages from TEXTDOMAIN. Usually a TEXTDOMAIN + corresponds to a package, a program, or a module of a program. + +‘-e’ + Enable expansion of some escape sequences. This option is for + compatibility with the ‘echo’ program or shell built-in. The + escape sequences ‘\a’, ‘\b’, ‘\c’, ‘\f’, ‘\n’, ‘\r’, ‘\t’, ‘\v’, + ‘\\’, and ‘\’ followed by one to three octal digits, are + interpreted like the System V ‘echo’ program did. + +‘-E’ + This option is only for compatibility with the ‘echo’ program or + shell built-in. It has no effect. + +‘-h’ +‘--help’ + Display this help and exit. + +‘-n’ + This option has only an effect if the ‘-s’ option is given. It + suppresses the additional newline at the end. + +‘-V’ +‘--version’ + Output version information and exit. + +‘[TEXTDOMAIN] MSGID’ + Retrieve translated message corresponding to MSGID from TEXTDOMAIN. + + If the TEXTDOMAIN parameter is not given, the domain is determined +from the environment variable ‘TEXTDOMAIN’. If the message catalog is +not found in the regular directory, another location can be specified +with the environment variable ‘TEXTDOMAINDIR’. + + When used with the ‘-s’ option the program behaves like the ‘echo’ +command. But it does not simply copy its arguments to stdout. Instead +those messages found in the selected catalog are translated. Also, a +newline is added at the end, unless either the option ‘-n’ is specified +or the option ‘-e’ is specified and some of the argument strings +contains a ‘\c’ escape sequence. + + Note: ‘xgettext’ supports only the one-argument form of the ‘gettext’ +invocation, where no options are present and the TEXTDOMAIN is implicit, +from the environment. + + +File: gettext.info, Node: ngettext Invocation, Next: envsubst Invocation, Prev: gettext Invocation, Up: sh + +15.5.15.4 Invoking the ‘ngettext’ program +......................................... + + ngettext [OPTION] [TEXTDOMAIN] MSGID MSGID-PLURAL COUNT + + The ‘ngettext’ program displays the native language translation of a +textual message whose grammatical form depends on a number. + +*Arguments* + +‘-c CONTEXT’ +‘--context=CONTEXT’ + Specify the context for the messages to be translated. See *note + Contexts:: for details. + +‘-d TEXTDOMAIN’ +‘--domain=TEXTDOMAIN’ + Retrieve translated messages from TEXTDOMAIN. Usually a TEXTDOMAIN + corresponds to a package, a program, or a module of a program. + +‘-e’ + Enable expansion of some escape sequences. This option is for + compatibility with the ‘gettext’ program. The escape sequences + ‘\a’, ‘\b’, ‘\f’, ‘\n’, ‘\r’, ‘\t’, ‘\v’, ‘\\’, and ‘\’ followed by + one to three octal digits, are interpreted like the System V ‘echo’ + program did. + +‘-E’ + This option is only for compatibility with the ‘gettext’ program. + It has no effect. + +‘-h’ +‘--help’ + Display this help and exit. + +‘-V’ +‘--version’ + Output version information and exit. + +‘TEXTDOMAIN’ + Retrieve translated message from TEXTDOMAIN. + +‘MSGID MSGID-PLURAL’ + Translate MSGID (English singular) / MSGID-PLURAL (English plural). + +‘COUNT’ + Choose singular/plural form based on this value. + + If the TEXTDOMAIN parameter is not given, the domain is determined +from the environment variable ‘TEXTDOMAIN’. If the message catalog is +not found in the regular directory, another location can be specified +with the environment variable ‘TEXTDOMAINDIR’. + + Note: ‘xgettext’ supports only the three-arguments form of the +‘ngettext’ invocation, where no options are present and the TEXTDOMAIN +is implicit, from the environment. + + +File: gettext.info, Node: envsubst Invocation, Next: eval_gettext Invocation, Prev: ngettext Invocation, Up: sh + +15.5.15.5 Invoking the ‘envsubst’ program +......................................... + + envsubst [OPTION] [SHELL-FORMAT] + + The ‘envsubst’ program substitutes the values of environment +variables. + +*Operation mode* + +‘-v’ +‘--variables’ + Output the variables occurring in SHELL-FORMAT. + +*Informative output* + +‘-h’ +‘--help’ + Display this help and exit. + +‘-V’ +‘--version’ + Output version information and exit. + + In normal operation mode, standard input is copied to standard +output, with references to environment variables of the form ‘$VARIABLE’ +or ‘${VARIABLE}’ being replaced with the corresponding values. If a +SHELL-FORMAT is given, only those environment variables that are +referenced in SHELL-FORMAT are substituted; otherwise all environment +variables references occurring in standard input are substituted. + + These substitutions are a subset of the substitutions that a shell +performs on unquoted and double-quoted strings. Other kinds of +substitutions done by a shell, such as ‘${VARIABLE-DEFAULT}’ or +‘$(COMMAND-LIST)’ or ‘`COMMAND-LIST`’, are not performed by the +‘envsubst’ program, due to security reasons. + + When ‘--variables’ is used, standard input is ignored, and the output +consists of the environment variables that are referenced in +SHELL-FORMAT, one per line. + + +File: gettext.info, Node: eval_gettext Invocation, Next: eval_ngettext Invocation, Prev: envsubst Invocation, Up: sh + +15.5.15.6 Invoking the ‘eval_gettext’ function +.............................................. + + eval_gettext MSGID + + This function outputs the native language translation of a textual +message, performing dollar-substitution on the result. Note that only +shell variables mentioned in MSGID will be dollar-substituted in the +result. + + +File: gettext.info, Node: eval_ngettext Invocation, Next: eval_pgettext Invocation, Prev: eval_gettext Invocation, Up: sh + +15.5.15.7 Invoking the ‘eval_ngettext’ function +............................................... + + eval_ngettext MSGID MSGID-PLURAL COUNT + + This function outputs the native language translation of a textual +message whose grammatical form depends on a number, performing +dollar-substitution on the result. Note that only shell variables +mentioned in MSGID or MSGID-PLURAL will be dollar-substituted in the +result. + + +File: gettext.info, Node: eval_pgettext Invocation, Next: eval_npgettext Invocation, Prev: eval_ngettext Invocation, Up: sh + +15.5.15.8 Invoking the ‘eval_pgettext’ function +............................................... + + eval_pgettext MSGCTXT MSGID + + This function outputs the native language translation of a textual +message in the given context MSGCTXT (see *note Contexts::), performing +dollar-substitution on the result. Note that only shell variables +mentioned in MSGID will be dollar-substituted in the result. + + +File: gettext.info, Node: eval_npgettext Invocation, Prev: eval_pgettext Invocation, Up: sh + +15.5.15.9 Invoking the ‘eval_npgettext’ function +................................................ + + eval_npgettext MSGCTXT MSGID MSGID-PLURAL COUNT + + This function outputs the native language translation of a textual +message whose grammatical form depends on a number in the given context +MSGCTXT (see *note Contexts::), performing dollar-substitution on the +result. Note that only shell variables mentioned in MSGID or +MSGID-PLURAL will be dollar-substituted in the result. + + +File: gettext.info, Node: bash, Next: gawk, Prev: sh, Up: List of Programming Languages + +15.5.16 bash - Bourne-Again Shell Script +---------------------------------------- + + GNU ‘bash’ 2.0 or newer has a special shorthand for translating a +string and substituting variable values in it: ‘$"msgid"’. But the use +of this construct is *discouraged*, due to the security holes it opens +and due to its portability problems. + + The security holes of ‘$"..."’ come from the fact that after looking +up the translation of the string, ‘bash’ processes it like it processes +any double-quoted string: dollar and backquote processing, like ‘eval’ +does. + + 1. In a locale whose encoding is one of BIG5, BIG5-HKSCS, GBK, + GB18030, SHIFT_JIS, JOHAB, some double-byte characters have a + second byte whose value is ‘0x60’. For example, the byte sequence + ‘\xe0\x60’ is a single character in these locales. Many versions + of ‘bash’ (all versions up to bash-2.05, and newer versions on + platforms without ‘mbsrtowcs()’ function) don't know about + character boundaries and see a backquote character where there is + only a particular Chinese character. Thus it can start executing + part of the translation as a command list. This situation can + occur even without the translator being aware of it: if the + translator provides translations in the UTF-8 encoding, it is the + ‘gettext()’ function which will, during its conversion from the + translator's encoding to the user's locale's encoding, produce the + dangerous ‘\x60’ bytes. + + 2. A translator could - voluntarily or inadvertently - use backquotes + ‘"`...`"’ or dollar-parentheses ‘"$(...)"’ in her translations. + The enclosed strings would be executed as command lists by the + shell. + + The portability problem is that ‘bash’ must be built with +internationalization support; this is normally not the case on systems +that don't have the ‘gettext()’ function in libc. + + +File: gettext.info, Node: gawk, Next: Lua, Prev: bash, Up: List of Programming Languages + +15.5.17 GNU awk +--------------- + +RPMs + gawk 3.1 or newer + +Ubuntu packages + gawk + +File extension + ‘awk’, ‘gawk’, ‘twjr’. The file extension ‘twjr’ is used by + TexiWeb Jr (). + +String syntax + ‘"abc"’ + +gettext shorthand + ‘_"abc"’ + +gettext/ngettext functions + ‘dcgettext’, missing ‘dcngettext’ in gawk-3.1.0 + +textdomain + ‘TEXTDOMAIN’ variable + +bindtextdomain + ‘bindtextdomain’ function + +setlocale + automatic, but missing ‘setlocale (LC_MESSAGES, "")’ in gawk-3.1.0 + +Prerequisite + -- + +Use or emulate GNU gettext + use + +Extractor + ‘xgettext’ + +Formatting with positions + ‘printf "%2$d %1$d"’ (GNU awk only) + +Portability + On platforms without gettext, no translation. On non-GNU awks, you + must define ‘dcgettext’, ‘dcngettext’ and ‘bindtextdomain’ + yourself. + +po-mode marking + -- + + An example is available in the ‘examples’ directory: ‘hello-gawk’. + + +File: gettext.info, Node: Lua, Next: Pascal, Prev: gawk, Up: List of Programming Languages + +15.5.18 Lua +----------- + +RPMs + lua + +Ubuntu packages + lua, lua-gettext + You need to install the ‘lua-gettext’ package from + . + Debian and Ubuntu packages of it are available. Download the + appropriate one, and install it through ‘sudo dpkg -i + lua-gettext_0.0+nmu1_amd64.deb’. + +File extension + ‘lua’ + +String syntax + + • ‘"abc"’ + + • ‘'abc'’ + + • ‘[[abc]]’ + + • ‘[=[abc]=]’ + + • ‘[==[abc]==]’ + + • ... + +gettext shorthand + ‘_("abc")’ + +gettext/ngettext functions + ‘gettext.gettext’, ‘gettext.dgettext’, ‘gettext.dcgettext’, + ‘gettext.ngettext’, ‘gettext.dngettext’, ‘gettext.dcngettext’ + +textdomain + ‘textdomain’ function + +bindtextdomain + ‘bindtextdomain’ function + +setlocale + automatic + +Prerequisite + ‘require 'gettext'’ or running lua interpreter with ‘-l gettext’ + option + +Use or emulate GNU gettext + use + +Extractor + ‘xgettext’ + +Formatting with positions + -- + +Portability + On platforms without gettext, the functions are not available. + +po-mode marking + -- + + +File: gettext.info, Node: Pascal, Next: Modula-2, Prev: Lua, Up: List of Programming Languages + +15.5.19 Pascal - Free Pascal Compiler +------------------------------------- + +RPMs + fpc + +Ubuntu packages + fp-compiler, fp-units-fcl + +File extension + ‘pp’, ‘pas’ + +String syntax + ‘'abc'’ + +gettext shorthand + automatic + +gettext/ngettext functions + --, use ‘ResourceString’ data type instead + +textdomain + --, use ‘TranslateResourceStrings’ function instead + +bindtextdomain + --, use ‘TranslateResourceStrings’ function instead + +setlocale + automatic, but uses only LANG, not LC_MESSAGES or LC_ALL + +Prerequisite + ‘{$mode delphi}’ or ‘{$mode objfpc}’ + ‘uses gettext;’ + +Use or emulate GNU gettext + emulate partially + +Extractor + ‘ppc386’ followed by ‘xgettext’ or ‘rstconv’ + +Formatting with positions + ‘uses sysutils;’ + ‘format "%1:d %0:d"’ + +Portability + ? + +po-mode marking + -- + + The Pascal compiler has special support for the ‘ResourceString’ data +type. It generates a ‘.rst’ file. This is then converted to a ‘.pot’ +file by use of ‘xgettext’ or ‘rstconv’. At runtime, a ‘.mo’ file +corresponding to translations of this ‘.pot’ file can be loaded using +the ‘TranslateResourceStrings’ function in the ‘gettext’ unit. + + An example is available in the ‘examples’ directory: ‘hello-pascal’. + + +File: gettext.info, Node: Modula-2, Next: D, Prev: Pascal, Up: List of Programming Languages + +15.5.20 Modula-2 +---------------- + +RPMs + gcc-gm2, libgm2 + +Ubuntu packages + gm2 + +File extension + ‘mod’, ‘def’ + +String syntax + ‘'abc'’, ‘"abc"’ + +gettext shorthand + -- + +gettext/ngettext functions + ‘Gettext’, ‘DGettext’, ‘DCGettext’, ‘NGettext’, ‘DNGettext’, + ‘DCNGettext’ + +textdomain + ‘TextDomain’ function + +bindtextdomain + ‘BindTextDomain’ function + +setlocale + Programmer must call ‘SetLocale (LC_ALL, "")’ + +Prerequisite + ‘FROM Libintl IMPORT Gettext ...;’ + +Use or emulate GNU gettext + Use + +Extractor + ‘xgettext’ + +Formatting with positions + -- + +Portability + fully portable to all platforms supported by GNU Modula-2 + +po-mode marking + -- + + An example is available in the ‘examples’ directory: ‘hello-modula2’. + + +File: gettext.info, Node: D, Next: Smalltalk, Prev: Modula-2, Up: List of Programming Languages + +15.5.21 D +--------- + +RPMs + gcc-gdc or ldc + +Ubuntu packages + gdc or ldc + +File extension + ‘d’ + +String syntax + ‘r"abc"’, ‘`abc`’, ‘"abc"’, ‘q"[abc]"’, ‘q"(abc)"’, ‘q""’, + ‘q"{abc}"’, ‘q{abc}’, ‘x"6A 6B 6C"’ + +gettext shorthand + ‘_("abc")’ + +gettext/ngettext functions + ‘gettext’, ‘dgettext’, ‘dcgettext’, ‘ngettext’, ‘dngettext’, + ‘dcngettext’ + + Note that the ‘ngettext’-like functions need to take two argument + strings that consume the same number of arguments. For example, + you cannot write ‘format(ngettext("a piece", "%d pieces", n), n)’ + because in the singular case, ‘format’ would treat the unused + argument as an error and throw an exception. As a workaround, you + need to convert ‘n’ to a string and format that string with + precision zero: ‘format(ngettext("%.0sa piece", "%s pieces", n), + to!string(n))’ or ‘format(ngettext("%.0sa piece", "%s pieces", n), + text(n))’ + +textdomain + ‘textdomain’ function + +bindtextdomain + ‘bindtextdomain’ function + +setlocale + Programmer must call ‘setlocale (LC_ALL, "")’ + +Prerequisite + ‘import gnu.libintl;’ + ‘alias _ = gettext;’ + +Use or emulate GNU gettext + Use + +Extractor + ‘xgettext -k_ --flag=_:1:pass-c-format --flag=_:1:pass-d-format’ + +Formatting with positions + ‘fprintf "%2$d %1$d"’, ‘format "%2$d %1$d"’ + +Portability + fully portable + +po-mode marking + -- + + An example is available in the ‘examples’ directory: ‘hello-d’. + + +File: gettext.info, Node: Smalltalk, Next: Vala, Prev: D, Up: List of Programming Languages + +15.5.22 GNU Smalltalk +--------------------- + +RPMs + smalltalk + +Ubuntu packages + gnu-smalltalk + +File extension + ‘st’ + +String syntax + ‘'abc'’ + +gettext shorthand + ‘NLS ? 'abc'’ + +gettext/ngettext functions + ‘LcMessagesDomain>>#at:’, ‘LcMessagesDomain>>#at:plural:with:’ + +textdomain + ‘LcMessages>>#domain:localeDirectory:’ (returns a + ‘LcMessagesDomain’ object). + Example: ‘I18N Locale default messages domain: 'gettext' + localeDirectory: /usr/local/share/locale'’ + +bindtextdomain + ‘LcMessages>>#domain:localeDirectory:’, see above. + +setlocale + Automatic if you use ‘I18N Locale default’. + +Prerequisite + ‘PackageLoader fileInPackage: 'I18N'!’ + +Use or emulate GNU gettext + emulate + +Extractor + ‘xgettext’ + +Formatting with positions + ‘'%1 %2' bindWith: 'Hello' with: 'world'’ + +Portability + fully portable + +po-mode marking + -- + + An example is available in the ‘examples’ directory: +‘hello-smalltalk’. + + +File: gettext.info, Node: Vala, Next: wxWidgets, Prev: Smalltalk, Up: List of Programming Languages + +15.5.23 Vala +------------ + +RPMs + vala + +Ubuntu packages + valac + +File extension + ‘vala’ + +String syntax + + • ‘"abc"’ + + • ‘"""abc"""’ + +gettext shorthand + ‘_("abc")’ + +gettext/ngettext functions + ‘gettext’, ‘dgettext’, ‘dcgettext’, ‘ngettext’, ‘dngettext’, + ‘dpgettext’, ‘dpgettext2’ + +textdomain + ‘textdomain’ function, defined under the ‘Intl’ namespace + +bindtextdomain + ‘bindtextdomain’ function, defined under the ‘Intl’ namespace + +setlocale + Programmer must call ‘Intl.setlocale (LocaleCategory.ALL, "")’ + +Prerequisite + -- + +Use or emulate GNU gettext + Use + +Extractor + ‘xgettext’ + +Formatting with positions + Same as for the C language. + +Portability + autoconf (gettext.m4) and #if ENABLE_NLS + +po-mode marking + yes + + +File: gettext.info, Node: wxWidgets, Next: Tcl, Prev: Vala, Up: List of Programming Languages + +15.5.24 wxWidgets library +------------------------- + +RPMs + wxGTK, gettext + +Ubuntu packages + libwxgtk3.0-dev or libwxgtk3.2-dev + +File extension + ‘cpp’ + +String syntax + ‘"abc"’ + +gettext shorthand + ‘_("abc")’ + +gettext/ngettext functions + ‘wxLocale::GetString’, ‘wxGetTranslation’ + +textdomain + ‘wxLocale::AddCatalog’ + +bindtextdomain + ‘wxLocale::AddCatalogLookupPathPrefix’ + +setlocale + ‘wxLocale::Init’, ‘wxSetLocale’ + +Prerequisite + ‘#include ’ + +Use or emulate GNU gettext + emulate, see ‘include/wx/intl.h’ and ‘src/common/intl.cpp’ + +Extractor + ‘xgettext’ + +Formatting with positions + wxString::Format supports positions if and only if the system has + ‘wprintf()’, ‘vswprintf()’ functions and they support positions + according to POSIX. + +Portability + fully portable + +po-mode marking + yes + + +File: gettext.info, Node: Tcl, Next: Perl, Prev: wxWidgets, Up: List of Programming Languages + +15.5.25 Tcl - Tk's scripting language +------------------------------------- + +RPMs + tcl + +Ubuntu packages + tcl + +File extension + ‘tcl’ + +String syntax + ‘"abc"’ + +gettext shorthand + ‘[_ "abc"]’ + +gettext/ngettext functions + ‘::msgcat::mc’ + +textdomain + -- + +bindtextdomain + --, use ‘::msgcat::mcload’ instead + +setlocale + automatic, uses LANG, but ignores LC_MESSAGES and LC_ALL + +Prerequisite + ‘package require msgcat’ + ‘proc _ {s} {return [::msgcat::mc $s]}’ + +Use or emulate GNU gettext + --, uses a Tcl specific message catalog format + +Extractor + ‘xgettext -k_’ + +Formatting with positions + ‘format "%2\$d %1\$d"’ + +Portability + fully portable + +po-mode marking + -- + + Two examples are available in the ‘examples’ directory: ‘hello-tcl’, +‘hello-tcl-tk’. + + Before marking strings as internationalizable, substitutions of +variables into the string need to be converted to ‘format’ applications. +For example, ‘"file $filename not found"’ becomes ‘[format "file %s not +found" $filename]’. Only after this is done, can the strings be marked +and extracted. After marking, this example becomes ‘[format [_ "file %s +not found"] $filename]’ or ‘[msgcat::mc "file %s not found" $filename]’. +Note that the ‘msgcat::mc’ function implicitly calls ‘format’ when more +than one argument is given. + + +File: gettext.info, Node: Perl, Next: PHP, Prev: Tcl, Up: List of Programming Languages + +15.5.26 Perl +------------ + +RPMs + perl + +Ubuntu packages + perl, libintl-perl + +File extension + ‘pl’, ‘PL’, ‘pm’, ‘perl’, ‘cgi’ + +String syntax + + • ‘"abc"’ + + • ‘'abc'’ + + • ‘qq (abc)’ + + • ‘q (abc)’ + + • ‘qr /abc/’ + + • ‘qx (/bin/date)’ + + • ‘/pattern match/’ + + • ‘?pattern match?’ + + • ‘s/substitution/operators/’ + + • ‘$tied_hash{"message"}’ + + • ‘$tied_hash_reference->{"message"}’ + + • etc., issue the command ‘man perlsyn’ for details + +gettext shorthand + ‘__’ (double underscore) + +gettext/ngettext functions + ‘gettext’, ‘dgettext’, ‘dcgettext’, ‘ngettext’, ‘dngettext’, + ‘dcngettext’, ‘pgettext’, ‘dpgettext’, ‘dcpgettext’, ‘npgettext’, + ‘dnpgettext’, ‘dcnpgettext’ + +textdomain + ‘textdomain’ function + +bindtextdomain + ‘bindtextdomain’ function + +bind_textdomain_codeset + ‘bind_textdomain_codeset’ function + +setlocale + Use ‘setlocale (LC_ALL, "");’ + +Prerequisite + ‘use POSIX;’ + ‘use Locale::TextDomain;’ (included in the package libintl-perl + which is available on the Comprehensive Perl Archive Network CPAN, + https://www.cpan.org/). + +Use or emulate GNU gettext + platform dependent: gettext_pp emulates, gettext_xs uses GNU + gettext + +Extractor + ‘xgettext -k__ -k\$__ -k%__ -k__x -k__n:1,2 -k__nx:1,2 -k__xn:1,2 + -kN__ -kN__n:1,2 -k__p:1c,2 -k__np:1c,2,3 -kN__p:1c,2 + -kN__np:1c,2,3’ + +Formatting with positions + Both kinds of format strings support formatting with positions. + ‘printf "%2\$d %1\$d", ...’ (requires Perl 5.8.0 or newer) + ‘__expand("[new] replaces [old]", old => $oldvalue, new => + $newvalue)’ + +Portability + The ‘libintl-perl’ package is platform independent but is not part + of the Perl core. The programmer is responsible for providing a + dummy implementation of the required functions if the package is + not installed on the target system. + +po-mode marking + -- + +Documentation + Included in ‘libintl-perl’, available on CPAN + (https://www.cpan.org/). + + An example is available in the ‘examples’ directory: ‘hello-perl’. + + The ‘xgettext’ parser backend for Perl differs significantly from the +parser backends for other programming languages, just as Perl itself +differs significantly from other programming languages. The Perl parser +backend offers many more string marking facilities than the other +backends but it also has some Perl specific limitations, the worst +probably being its imperfectness. + +* Menu: + +* General Problems:: General Problems Parsing Perl Code +* Default Keywords:: Which Keywords Will xgettext Look For? +* Special Keywords:: How to Extract Hash Keys +* Quote-like Expressions:: What are Strings And Quote-like Expressions? +* Interpolation I:: Unsupported String Interpolation +* Interpolation II:: Valid String Interpolation +* Parentheses:: When To Use Parentheses +* Long Lines:: How To Grok with Long Lines +* Perl Pitfalls:: Bugs, Pitfalls, and Things That Do Not Work + + +File: gettext.info, Node: General Problems, Next: Default Keywords, Up: Perl + +15.5.26.1 General Problems Parsing Perl Code +............................................ + + It is often heard that only Perl can parse Perl. This is not true. +Perl cannot be _parsed_ at all, it can only be _executed_. Perl has +various built-in ambiguities that can only be resolved at runtime. + + The following example may illustrate one common problem: + + print gettext "Hello World!"; + + Although this example looks like a bullet-proof case of a function +invocation, it is not: + + open gettext, ">testfile" or die; + print gettext "Hello world!" + + In this context, the string ‘gettext’ looks more like a file handle. +But not necessarily: + + use Locale::Messages qw (:libintl_h); + open gettext ">testfile" or die; + print gettext "Hello world!"; + + Now, the file is probably syntactically incorrect, provided that the +module ‘Locale::Messages’ found first in the Perl include path exports a +function ‘gettext’. But what if the module ‘Locale::Messages’ really +looks like this? + + use vars qw (*gettext); + + 1; + + In this case, the string ‘gettext’ will be interpreted as a file +handle again, and the above example will create a file ‘testfile’ and +write the string "Hello world!" into it. Even advanced control flow +analysis will not really help: + + if (0.5 < rand) { + eval "use Sane"; + } else { + eval "use InSane"; + } + print gettext "Hello world!"; + + If the module ‘Sane’ exports a function ‘gettext’ that does what we +expect, and the module ‘InSane’ opens a file for writing and associates +the _handle_ ‘gettext’ with this output stream, we are clueless again +about what will happen at runtime. It is completely unpredictable. The +truth is that Perl has so many ways to fill its symbol table at runtime +that it is impossible to interpret a particular piece of code without +executing it. + + Of course, ‘xgettext’ will not execute your Perl sources while +scanning for translatable strings, but rather use heuristics in order to +guess what you meant. + + Another problem is the ambiguity of the slash and the question mark. +Their interpretation depends on the context: + + # A pattern match. + print "OK\n" if /foobar/; + + # A division. + print 1 / 2; + + # Another pattern match. + print "OK\n" if ?foobar?; + + # Conditional. + print $x ? "foo" : "bar"; + + The slash may either act as the division operator or introduce a +pattern match, whereas the question mark may act as the ternary +conditional operator or as a pattern match, too. Other programming +languages like ‘awk’ present similar problems, but the consequences of a +misinterpretation are particularly nasty with Perl sources. In ‘awk’ +for instance, a statement can never exceed one line and the parser can +recover from a parsing error at the next newline and interpret the rest +of the input stream correctly. Perl is different, as a pattern match is +terminated by the next appearance of the delimiter (the slash or the +question mark) in the input stream, regardless of the semantic context. +If a slash is really a division sign but mis-interpreted as a pattern +match, the rest of the input file is most probably parsed incorrectly. + + There are certain cases, where the ambiguity cannot be resolved at +all: + + $x = wantarray ? 1 : 0; + + The Perl built-in function ‘wantarray’ does not accept any arguments. +The Perl parser therefore knows that the question mark does not start a +regular expression but is the ternary conditional operator. + + sub wantarrays {} + $x = wantarrays ? 1 : 0; + + Now the situation is different. The function ‘wantarrays’ takes a +variable number of arguments (like any non-prototyped Perl function). +The question mark is now the delimiter of a pattern match, and hence the +piece of code does not compile. + + sub wantarrays() {} + $x = wantarrays ? 1 : 0; + + Now the function is prototyped, Perl knows that it does not accept +any arguments, and the question mark is therefore interpreted as the +ternaray operator again. But that unfortunately outsmarts ‘xgettext’. + + The Perl parser in ‘xgettext’ cannot know whether a function has a +prototype and what that prototype would look like. It therefore makes +an educated guess. If a function is known to be a Perl built-in and +this function does not accept any arguments, a following question mark +or slash is treated as an operator, otherwise as the delimiter of a +following regular expression. The Perl built-ins that do not accept +arguments are ‘wantarray’, ‘fork’, ‘time’, ‘times’, ‘getlogin’, +‘getppid’, ‘getpwent’, ‘getgrent’, ‘gethostent’, ‘getnetent’, +‘getprotoent’, ‘getservent’, ‘setpwent’, ‘setgrent’, ‘endpwent’, +‘endgrent’, ‘endhostent’, ‘endnetent’, ‘endprotoent’, and ‘endservent’. + + If you find that ‘xgettext’ fails to extract strings from portions of +your sources, you should therefore look out for slashes and/or question +marks preceding these sections. You may have come across a bug in +‘xgettext’'s Perl parser (and of course you should report that bug). In +the meantime you should consider to reformulate your code in a manner +less challenging to ‘xgettext’. + + In particular, if the parser is too dumb to see that a function does +not accept arguments, use parentheses: + + $x = somefunc() ? 1 : 0; + $y = (somefunc) ? 1 : 0; + + In fact the Perl parser itself has similar problems and warns you +about such constructs. + + +File: gettext.info, Node: Default Keywords, Next: Special Keywords, Prev: General Problems, Up: Perl + +15.5.26.2 Which keywords will xgettext look for? +................................................ + + Unless you instruct ‘xgettext’ otherwise by invoking it with one of +the options ‘--keyword’ or ‘-k’, it will recognize the following +keywords in your Perl sources: + + • ‘gettext’ + + • ‘dgettext:2’ + + The second argument will be extracted. + + • ‘dcgettext:2’ + + The second argument will be extracted. + + • ‘ngettext:1,2’ + + The first (singular) and the second (plural) argument will be + extracted. + + • ‘dngettext:2,3’ + + The second (singular) and the third (plural) argument will be + extracted. + + • ‘dcngettext:2,3’ + + The second (singular) and the third (plural) argument will be + extracted. + + • ‘pgettext:1c,2’ + + The first (message context) and the second argument will be + extracted. + + • ‘dpgettext:2c,3’ + + The second (message context) and the third argument will be + extracted. + + • ‘dcpgettext:2c,3’ + + The second (message context) and the third argument will be + extracted. + + • ‘npgettext:1c,2,3’ + + The first (message context), second (singular), and third (plural) + argument will be extracted. + + • ‘dnpgettext:2c,3,4’ + + The second (message context), third (singular), and fourth (plural) + argument will be extracted. + + • ‘dcnpgettext:2c,3,4’ + + The second (message context), third (singular), and fourth (plural) + argument will be extracted. + + • ‘gettext_noop’ + + • ‘%gettext’ + + The keys of lookups into the hash ‘%gettext’ will be extracted. + + • ‘$gettext’ + + The keys of lookups into the hash reference ‘$gettext’ will be + extracted. + + +File: gettext.info, Node: Special Keywords, Next: Quote-like Expressions, Prev: Default Keywords, Up: Perl + +15.5.26.3 How to Extract Hash Keys +.................................. + + Translating messages at runtime is normally performed by looking up +the original string in the translation database and returning the +translated version. The "natural" Perl implementation is a hash lookup, +and, of course, ‘xgettext’ supports such practice. + + print __"Hello world!"; + print $__{"Hello world!"}; + print $__->{"Hello world!"}; + print $$__{"Hello world!"}; + + The above four lines all do the same thing. The Perl module +‘Locale::TextDomain’ exports by default a hash ‘%__’ that is tied to the +function ‘__()’. It also exports a reference ‘$__’ to ‘%__’. + + If an argument to the ‘xgettext’ option ‘--keyword’, resp. ‘-k’ +starts with a percent sign, the rest of the keyword is interpreted as +the name of a hash. If it starts with a dollar sign, the rest of the +keyword is interpreted as a reference to a hash. + + Note that you can omit the quotation marks (single or double) around +the hash key (almost) whenever Perl itself allows it: + + print $gettext{Error}; + + The exact rule is: You can omit the surrounding quotes, when the hash +key is a valid C (!) identifier, i.e. when it starts with an underscore +or an ASCII letter and is followed by an arbitrary number of +underscores, ASCII letters or digits. Other Unicode characters are +_not_ allowed, regardless of the ‘use utf8’ pragma. + + +File: gettext.info, Node: Quote-like Expressions, Next: Interpolation I, Prev: Special Keywords, Up: Perl + +15.5.26.4 What are Strings And Quote-like Expressions? +...................................................... + + Perl offers a plethora of different string constructs. Those that +can be used either as arguments to functions or inside braces for hash +lookups are generally supported by ‘xgettext’. + + • *double-quoted strings* + print gettext "Hello World!"; + + • *single-quoted strings* + print gettext 'Hello World!'; + + • *the operator qq* + print gettext qq |Hello World!|; + print gettext qq >; + + The operator ‘qq’ is fully supported. You can use arbitrary + delimiters, including the four bracketing delimiters (round, angle, + square, curly) that nest. + + • *the operator q* + print gettext q |Hello World!|; + print gettext q >; + + The operator ‘q’ is fully supported. You can use arbitrary + delimiters, including the four bracketing delimiters (round, angle, + square, curly) that nest. + + • *the operator qx* + print gettext qx ;LANGUAGE=C /bin/date; + print gettext qx [/usr/bin/ls | grep '^[A-Z]*']; + + The operator ‘qx’ is fully supported. You can use arbitrary + delimiters, including the four bracketing delimiters (round, angle, + square, curly) that nest. + + The example is actually a useless use of ‘gettext’. It will invoke + the ‘gettext’ function on the output of the command specified with + the ‘qx’ operator. The feature was included in order to make the + interface consistent (the parser will extract all strings and + quote-like expressions). + + • *here documents* + print gettext <<'EOF'; + program not found in $PATH + EOF + + print ngettext <My Homepage + + EOF + + The parser will extract the entire here document, and it will appear +entirely in the resulting PO file, including the JavaScript snippet +embedded in the HTML code. If you exaggerate with constructs like the +above, you will run the risk that the translators of your package will +look out for a less challenging project. You should consider an +alternative expression here: + + print <$gettext{"My Homepage"} + + EOF + + Only the translatable portions of the code will be extracted here, +and the resulting PO file will begrudgingly improve in terms of +readability. + + You can interpolate hash lookups in all strings or quote-like +expressions that are subject to interpolation (see the manual page ‘man +perlop’ for details). Double interpolation is unsupported, however: + + # TRANSLATORS: Replace "the earth" with the name of your planet. + print gettext qq{Welcome to $gettext->{"the earth"}}; + + The ‘qq’-quoted string is recognized as an argument to ‘xgettext’ in +the first place, and checked for unsupported variable interpolation. +The dollar sign of hash-dereferencing will therefore terminate the +parser with an "unsupported interpolation" warning. + + It is valid to interpolate hash lookups in regular expressions: + + if ($var =~ /$gettext{"the earth"}/) { + print gettext "Match!\n"; + } + s/$gettext{"U. S. A."}/$gettext{"U. S. A."} $gettext{"(dial +0)"}/g; + + +File: gettext.info, Node: Parentheses, Next: Long Lines, Prev: Interpolation II, Up: Perl + +15.5.26.7 When To Use Parentheses +................................. + + In Perl, parentheses around function arguments are mostly optional. +‘xgettext’ will always assume that all recognized keywords (except for +hashes and hash references) are names of properly prototyped functions, +and will (hopefully) only require parentheses where Perl itself requires +them. All constructs in the following example are therefore ok to use: + + print gettext ("Hello World!\n"); + print gettext "Hello World!\n"; + print dgettext ($package => "Hello World!\n"); + print dgettext $package, "Hello World!\n"; + + # The "fat comma" => turns the left-hand side argument into a + # single-quoted string! + print dgettext smellovision => "Hello World!\n"; + + # The following assignment only works with prototyped functions. + # Otherwise, the functions will act as "greedy" list operators and + # eat up all following arguments. + my $anonymous_hash = { + planet => gettext "earth", + cakes => ngettext "one cake", "several cakes", $n, + still => $works, + }; + # The same without fat comma: + my $other_hash = { + 'planet', gettext "earth", + 'cakes', ngettext "one cake", "several cakes", $n, + 'still', $works, + }; + + # Parentheses are only significant for the first argument. + print dngettext 'package', ("one cake", "several cakes", $n), $discarded; + + +File: gettext.info, Node: Long Lines, Next: Perl Pitfalls, Prev: Parentheses, Up: Perl + +15.5.26.8 How To Grok with Long Lines +..................................... + + The necessity of long messages can often lead to a cumbersome or +unreadable coding style. Perl has several options that may prevent you +from writing unreadable code, and ‘xgettext’ does its best to do +likewise. This is where the dot operator (the string concatenation +operator) may come in handy: + + print gettext ("This is a very long" + . " message that is still" + . " readable, because" + . " it is split into" + . " multiple lines.\n"); + + Perl is smart enough to concatenate these constant string fragments +into one long string at compile time, and so is ‘xgettext’. You will +only find one long message in the resulting POT file. + + Note that the future Perl 6 will probably use the underscore (‘_’) as +the string concatenation operator, and the dot (‘.’) for dereferencing. +This new syntax is not yet supported by ‘xgettext’. + + If embedded newline characters are not an issue, or even desired, you +may also insert newline characters inside quoted strings wherever you +feel like it: + + print gettext ("In HTML output + embedded newlines are generally no + problem, since adjacent whitespace + is always rendered into a single + space character."); + + You may also consider to use here documents: + + print gettext <In HTML output + embedded newlines are generally no + problem, since adjacent whitespace + is always rendered into a single + space character. + EOF + + Please do not forget that the line breaks are real, i.e. they +translate into newline characters that will consequently show up in the +resulting POT file. + + +File: gettext.info, Node: Perl Pitfalls, Prev: Long Lines, Up: Perl + +15.5.26.9 Bugs, Pitfalls, And Things That Do Not Work +..................................................... + + The foregoing sections should have proven that ‘xgettext’ is quite +smart in extracting translatable strings from Perl sources. Yet, some +more or less exotic constructs that could be expected to work, actually +do not work. + + One of the more relevant limitations can be found in the +implementation of variable interpolation inside quoted strings. Only +simple hash lookups can be used there: + + print </gettext ("Sunday")/e; + + The modifier ‘e’ will cause the substitution to be interpreted as an +evaluable statement. Consequently, at runtime the function ‘gettext()’ +is called, but again, the parser fails to extract the string "Sunday". +Use a temporary variable as a simple workaround if you really happen to +need this feature: + + my $sunday = gettext "Sunday"; + s//$sunday/; + + Hash slices would also be handy but are not recognized: + + my @weekdays = @gettext{'Sunday', 'Monday', 'Tuesday', 'Wednesday', + 'Thursday', 'Friday', 'Saturday'}; + # Or even: + @weekdays = @gettext{qw (Sunday Monday Tuesday Wednesday Thursday + Friday Saturday) }; + + This is perfectly valid usage of the tied hash ‘%gettext’ but the +strings are not recognized and therefore will not be extracted. + + Another caveat of the current version is its rudimentary support for +non-ASCII characters in identifiers. You may encounter serious problems +if you use identifiers with characters outside the range of 'A'-'Z', +'a'-'z', '0'-'9' and the underscore '_'. + + Maybe some of these missing features will be implemented in future +versions, but since you can always make do without them at minimal +effort, these todos have very low priority. + + A nasty problem are brace format strings that already contain braces +as part of the normal text, for example the usage strings typically +encountered in programs: + + die "usage: $0 {OPTIONS} FILENAME...\n"; + + If you want to internationalize this code with Perl brace format +strings, you will run into a problem: + + die __x ("usage: {program} {OPTIONS} FILENAME...\n", program => $0); + + Whereas ‘{program}’ is a placeholder, ‘{OPTIONS}’ is not and should +probably be translated. Yet, there is no way to teach the Perl parser +in ‘xgettext’ to recognize the first one, and leave the other one alone. + + There are two possible work-arounds for this problem. If you are +sure that your program will run under Perl 5.8.0 or newer (these Perl +versions handle positional parameters in ‘printf()’) or if you are sure +that the translator will not have to reorder the arguments in her +translation - for example if you have only one brace placeholder in your +string, or if it describes a syntax, like in this one -, you can mark +the string as ‘no-perl-brace-format’ and use ‘printf()’: + + # xgettext: no-perl-brace-format + die sprintf ("usage: %s {OPTIONS} FILENAME...\n", $0); + + If you want to use the more portable Perl brace format, you will have +to do put placeholders in place of the literal braces: + + die __x ("usage: {program} {[}OPTIONS{]} FILENAME...\n", + program => $0, '[' => '{', ']' => '}'); + + Perl brace format strings know no escaping mechanism. No matter how +this escaping mechanism looked like, it would either give the programmer +a hard time, make translating Perl brace format strings heavy-going, or +result in a performance penalty at runtime, when the format directives +get executed. Most of the time you will happily get along with +‘printf()’ for this special case. + + +File: gettext.info, Node: PHP, Next: Pike, Prev: Perl, Up: List of Programming Languages + +15.5.27 PHP Hypertext Preprocessor +---------------------------------- + +RPMs + php + +Ubuntu packages + php + +File extension + ‘php’, ‘php3’, ‘php4’ + +String syntax + ‘"abc"’, ‘'abc'’, ‘<<. + +RPMs + appdata-tools, appstream, libappstream-glib, + libappstream-glib-builder + +Ubuntu packages + appdata-tools, appstream, libappstream-glib-dev + +File extension + ‘appdata.xml’, ‘metainfo.xml’ + +Extractor + ‘xgettext’, ‘intltool-extract’, ‘itstool’ + + +File: gettext.info, Node: Preparing ITS Rules, Prev: AppData, Up: Internationalizable Data + +16.1.6 Preparing Rules for XML Internationalization +--------------------------------------------------- + +* Menu: + +* ITS Rules:: Specifying ITS Rules +* Locating Rules:: Specifying where to find the ITS Rules + + +File: gettext.info, Node: ITS Rules, Next: Locating Rules, Up: Preparing ITS Rules + +16.1.6.1 Specifying ITS Rules +............................. + + Marking translatable strings in an XML file is done through a +separate "rule" file, making use of the Internationalization Tag Set +standard (ITS, ). The currently supported +ITS data categories are: ‘Translate’, ‘Localization Note’, ‘Elements +Within Text’, and ‘Preserve Space’. In addition to them, ‘xgettext’ +also recognizes the following extended data categories: + +‘Context’ + + This data category associates ‘msgctxt’ to the extracted text. In + the global rule, the ‘contextRule’ element contains the following: + + • A required ‘selector’ attribute. It contains an absolute + selector that selects the nodes to which this rule applies. + + • A required ‘contextPointer’ attribute that contains a relative + selector pointing to a node that holds the ‘msgctxt’ value. + + • An optional ‘textPointer’ attribute that contains a relative + selector pointing to a node that holds the ‘msgid’ value. + +‘Extended Preserve Space’ + + This data category extends the standard ‘Preserve Space’ data + category with the additional values ‘trim’ and ‘paragraph’. ‘trim’ + means to remove the leading and trailing whitespaces of the + content, but not to normalize whitespaces in the middle. + ‘paragraph’ means to normalize the content but keep the paragraph + boundaries. In the global rule, the ‘preserveSpaceRule’ element + contains the following: + + • A required ‘selector’ attribute. It contains an absolute + selector that selects the nodes to which this rule applies. + + • A required ‘space’ attribute with the value ‘default’, + ‘preserve’, ‘trim’, or ‘paragraph’. + +‘Escape Special Characters’ + + This data category indicates whether the special XML characters + (‘<’, ‘>’, ‘&’, ‘"’) are escaped with entity references. In the + global rule, the ‘escapeRule’ element contains the following: + + • A required ‘selector’ attribute. It contains an absolute + selector that selects the nodes to which this rule applies. + + • A required ‘escape’ attribute with the value ‘yes’ or ‘no’. + + • An optional ‘unescape-if’ attribute with the value ‘xml’, + ‘xhtml’, ‘html’, or ‘no’. + + The default values, ‘escape="no"’ and ‘unescape-if="no"’, should be + good for most XML file types. A rule with ‘escape="no"’, that was + necessary with GNU gettext versions before 0.23, is now redundant. + + The ‘unescape-if’ attribute is useful for XML file types which + present messages with embedded XML elements to the translator. + Such file types are for example DocBook or XHTML. If + ‘unescape-if="xml"’ is specified and the translation of a message + looks like valid XML, the usual escaping of ‘<’, ‘>’, and character + references is omitted. The resulting XML document then is likely + what the translator intended. However, if the translator did not + merely copy the XML markup from the message to the translation, but + added or removed markup, the resulting XML document may be invalid. + It is therefore useful if, after invoking ‘msgfmt’, you check the + resulting XML document against the appropriate XML schema or DTD. + + Similarly, if ‘unescape-if="xhtml"’ is specified and the + translation looks like valid XHTML, the usual escaping is omitted. + And likewise for ‘unescape-if="html"’. + + All those extended data categories can only be expressed with global +rules, and the rule elements have to have the +‘https://www.gnu.org/s/gettext/ns/its/extensions/1.0’ namespace. + + Given the following XML document in a file ‘messages.xml’: + + + + +

A translatable string

+ + +

A non-translatable string

+ + + + To extract the first text content ("A translatable string"), but not +the second ("A non-translatable string"), the following ITS rules can be +used: + + + + + + + + + + + ITS rules files must have the ‘.its’ file extension and obey the XML +schema version 1.0 encoded by ‘its.xsd10’ or the XML schema version 1.1 +encoded by ‘its.xsd11’ and its auxiliary schema ‘its-extensions.xsd’. + + +File: gettext.info, Node: Locating Rules, Prev: ITS Rules, Up: Preparing ITS Rules + +16.1.6.2 Specifying where to find the ITS Rules +............................................... + + ‘xgettext’ needs another file called "locating rules" to associate an +ITS rule with an XML file. If the above ITS file is saved as +‘messages.its’, the locating rules file would look like: + + + + + + + + + + The ‘locatingRule’ element must have a ‘pattern’ attribute, which +denotes either a literal file name or a wildcard pattern of the XML +file(1). The ‘locatingRule’ element can have child ‘documentRule’ +element, which adds checks on the content of the XML file. + + The first rule matches any file with the ‘.xml’ file extension, but +it only applies to XML files whose root element is ‘’. + + The second rule indicates that the same ITS rules file are also +applicable to any file with the ‘.msg’ file extension. The optional +‘name’ attribute of ‘locatingRule’ allows to choose rules by name, +typically with ‘xgettext’'s ‘-L’ option. + + The associated ITS rules file is indicated by the ‘target’ attribute +of ‘locatingRule’ or ‘documentRule’. If it is specified in a +‘documentRule’ element, the parent ‘locatingRule’ shouldn't have the +‘target’ attribute. + + Locating rules files must have the ‘.loc’ file extension and obey the +XML schema version 1.0 encoded by ‘locating-rules.xsd10’ or the XML +schema version 1.1 encoded by ‘locating-rules.xsd11’. Both ITS rules +files and locating rules files must be installed in the +‘$prefix/share/gettext/its’ directory. Once those files are properly +installed, ‘xgettext’ can extract translatable strings from the matching +XML files. + +16.1.6.3 Two Use-cases of Translated Strings in XML +................................................... + + After strings have been extracted from an XML file to a POT file +through ‘xgettext’ and the translator has produced a PO file with +translations, it can be used in two ways: + + • The PO file (or the MO file generated from it) can be directly + consumed by a program. + + • Or the translated strings can be merged back to the original XML + document. To do this use the ‘msgfmt’ program with the option + ‘--xml’. *Note msgfmt Invocation::, for more details about how one + calls the ‘msgfmt’ program. + + During this merge from a PO file into an XML file, it may happen + that more escaping of special characters for XML is needed than + what ‘msgfmt’ does by default. In this case, you can enforce more + escaping either throuch an ‘’ ITS rule, or through an + attribute ‘gt:escape="yes"’ on the particular XML element. + + ---------- Footnotes ---------- + + (1) Note that the file name matching is done after removing any ‘.in’ +suffix from the input file name. Thus the ‘pattern’ attribute must not +include a pattern matching ‘.in’. For example, if the input file name +is ‘foo.msg.in’, the pattern should be either ‘*.msg’ or just ‘*’, +rather than ‘*.in’. + + +File: gettext.info, Node: Localized Data, Prev: Internationalizable Data, Up: Data Formats + +16.2 Localized Data Formats +=========================== + + Here is a list of file formats that contain localized data and that +the GNU gettext tools can manipulate. + +* Menu: + +* Editable Message Catalogs:: Editable Message Catalogs +* Compiled Message Catalogs:: Compiled Message Catalogs +* Desktop Entry:: Desktop Entry files +* XML:: XML files + + +File: gettext.info, Node: Editable Message Catalogs, Next: Compiled Message Catalogs, Up: Localized Data + +16.2.1 Editable Message Catalogs +-------------------------------- + + These file formats can be used with all of the ‘msg*’ tools and with +the ‘xgettext’ program. + + If you just want to convert among these formats, you can use the +‘msgcat’ program (with the appropriate option) or the ‘xgettext’ +program. + +* Menu: + +* PO:: PO - Portable Object +* Java .properties:: Java .properties +* GNUstep .strings:: NeXTstep/GNUstep .strings + + +File: gettext.info, Node: PO, Next: Java .properties, Up: Editable Message Catalogs + +16.2.1.1 PO - Portable Object +............................. + +File extension + ‘po’ + + +File: gettext.info, Node: Java .properties, Next: GNUstep .strings, Prev: PO, Up: Editable Message Catalogs + +16.2.1.2 Java .properties +......................... + +File extension + ‘properties’ + + +File: gettext.info, Node: GNUstep .strings, Prev: Java .properties, Up: Editable Message Catalogs + +16.2.1.3 NeXTstep/GNUstep .strings +.................................. + +File extension + ‘strings’ + + +File: gettext.info, Node: Compiled Message Catalogs, Next: Desktop Entry, Prev: Editable Message Catalogs, Up: Localized Data + +16.2.2 Compiled Message Catalogs +-------------------------------- + + These file formats can be created through ‘msgfmt’ and converted back +to PO format through ‘msgunfmt’. + +* Menu: + +* MO:: MO - Machine Object +* Java ResourceBundle:: Java ResourceBundle +* C# Satellite Assembly:: C# Satellite Assembly +* C# Resource:: C# Resource +* Tcl message catalog:: Tcl message catalog +* Qt message catalog:: Qt message catalog + + +File: gettext.info, Node: MO, Next: Java ResourceBundle, Up: Compiled Message Catalogs + +16.2.2.1 MO - Machine Object +............................ + +File extension + ‘mo’ + + See section *note MO Files:: for details. + + +File: gettext.info, Node: Java ResourceBundle, Next: C# Satellite Assembly, Prev: MO, Up: Compiled Message Catalogs + +16.2.2.2 Java ResourceBundle +............................ + +File extension + ‘class’ + + For more information, see the section *note Java:: and the examples +‘hello-java’, ‘hello-java-awt’, ‘hello-java-swing’. + + +File: gettext.info, Node: C# Satellite Assembly, Next: C# Resource, Prev: Java ResourceBundle, Up: Compiled Message Catalogs + +16.2.2.3 C# Satellite Assembly +.............................. + +File extension + ‘dll’ + + For more information, see the section *note C#::. + + +File: gettext.info, Node: C# Resource, Next: Tcl message catalog, Prev: C# Satellite Assembly, Up: Compiled Message Catalogs + +16.2.2.4 C# Resource +.................... + +File extension + ‘resources’ + + For more information, see the section *note C#::. + + +File: gettext.info, Node: Tcl message catalog, Next: Qt message catalog, Prev: C# Resource, Up: Compiled Message Catalogs + +16.2.2.5 Tcl message catalog +............................ + +File extension + ‘msg’ + + For more information, see the section *note Tcl:: and the examples +‘hello-tcl’, ‘hello-tcl-tk’. + + +File: gettext.info, Node: Qt message catalog, Prev: Tcl message catalog, Up: Compiled Message Catalogs + +16.2.2.6 Qt message catalog +........................... + +File extension + ‘qm’ + + For more information, see the examples ‘hello-c++-qt’ and +‘hello-c++-kde’. + + +File: gettext.info, Node: Desktop Entry, Next: XML, Prev: Compiled Message Catalogs, Up: Localized Data + +16.2.3 Desktop Entry files +-------------------------- + + The programmer produces a desktop entry file template with only the +English strings. These strings get included in the POT file, by way of +‘xgettext’ (usually by listing the template in ‘po/POTFILES.in’). The +translators produce PO files, one for each language. Finally, an +‘msgfmt --desktop’ invocation collects all the translations in the +desktop entry file. + + For more information, see the example ‘hello-c-gnome3’. + +* Menu: + +* Icons:: Handling icons + + +File: gettext.info, Node: Icons, Up: Desktop Entry + +16.2.3.1 How to handle icons in Desktop Entry files +................................................... + + Icons are generally locale dependent, for the following reasons: + + • Icons may contain signs that are considered rude in some cultures. + For example, the high-five sign, in some cultures, is perceived as + an unfriendly "stop" sign. + • Icons may contain metaphors that are culture specific. For + example, a mailbox in the U.S. looks different than mailboxes all + around the world. + • Icons may need to be mirrored for right-to-left locales. + • Icons may contain text strings (a bad practice, but anyway). + + However, icons are not covered by GNU gettext localization, because + • Icons cannot be easily embedded in PO files, + • The need to localize an icon is rare, and the ability to do so in a + PO file would introduce translator mistakes. + + Desktop Entry files may contain an ‘Icon’ property, and this property +is localizable. If a translator wishes to localize an icon, she should +do so by bypassing the normal workflow with PO files: + 1. The translator contacts the package developers directly, sending + them the icon appropriate for her locale, with a request to change + the template file. + 2. The package developers add the icon file to their repository, and a + line + Icon[LOCALE]=ICON_FILE_NAME + to the template file. +This line remains in place when this template file is merged with the +translators' PO files, through ‘msgfmt’. + + +File: gettext.info, Node: XML, Prev: Desktop Entry, Up: Localized Data + +16.2.4 XML files +---------------- + + See the section *note Preparing ITS Rules:: and *note msgfmt +Invocation::, subsection "XML mode operations". + + +File: gettext.info, Node: Conclusion, Next: Language Codes, Prev: Data Formats, Up: Top + +17 Concluding Remarks +********************* + + We would like to conclude this GNU ‘gettext’ manual by presenting an +history of the Translation Project so far. We finally give a few +pointers for those who want to do further research or readings about +Native Language Support matters. + +* Menu: + +* History:: History of GNU ‘gettext’ +* The original ABOUT-NLS:: Historical introduction +* References:: Related Readings + + +File: gettext.info, Node: History, Next: The original ABOUT-NLS, Up: Conclusion + +17.1 History of GNU ‘gettext’ +============================= + + Internationalization concerns and algorithms have been informally and +casually discussed for years in GNU, sometimes around GNU ‘libc’, maybe +around the incoming ‘Hurd’, or otherwise (nobody clearly remembers). +And even then, when the work started for real, this was somewhat +independently of these previous discussions. + + This all began in July 1994, when Patrick D'Cruze had the idea and +initiative of internationalizing version 3.9.2 of GNU ‘fileutils’. He +then asked Jim Meyering, the maintainer, how to get those changes folded +into an official release. That first draft was full of ‘#ifdef’s and +somewhat disconcerting, and Jim wanted to find nicer ways. Patrick and +Jim shared some tries and experimentations in this area. Then, feeling +that this might eventually have a deeper impact on GNU, Jim wanted to +know what standards were, and contacted Richard Stallman, who very +quickly and verbally described an overall design for what was meant to +become ‘glocale’, at that time. + + Jim implemented ‘glocale’ and got a lot of exhausting feedback from +Patrick and Richard, of course, but also from Mitchum DSouza (who wrote +a ‘catgets’-like package), Roland McGrath, maybe David MacKenzie, +François Pinard, and Paul Eggert, all pushing and pulling in various +directions, not always compatible, to the extent that after a couple of +test releases, ‘glocale’ was torn apart. In particular, Paul Eggert - +always keeping an eye on developments in Solaris - advocated the use of +the ‘gettext’ API over ‘glocale’'s ‘catgets’-based API. + + While Jim took some distance and time and became dad for a second +time, Roland wanted to get GNU ‘libc’ internationalized, and got Ulrich +Drepper involved in that project. Instead of starting from ‘glocale’, +Ulrich rewrote something from scratch, but more conforming to the set of +guidelines who emerged out of the ‘glocale’ effort. Then, Ulrich got +people from the previous forum to involve themselves into this new +project, and the switch from ‘glocale’ to what was first named +‘msgutils’, renamed ‘nlsutils’, and later ‘gettext’, became officially +accepted by Richard in May 1995 or so. + + Let's summarize by saying that Ulrich Drepper wrote GNU ‘gettext’ in +April 1995. The first official release of the package, including PO +mode, occurred in July 1995, and was numbered 0.7. Other people +contributed to the effort by providing a discussion forum around Ulrich, +writing little pieces of code, or testing. These are quoted in the +‘THANKS’ file which comes with the GNU ‘gettext’ distribution. + + While this was being done, François adapted half a dozen of GNU +packages to ‘glocale’ first, then later to ‘gettext’, putting them in +pretest, so providing along the way an effective user environment for +fine tuning the evolving tools. He also took the responsibility of +organizing and coordinating the Translation Project. After nearly a +year of informal exchanges between people from many countries, +translator teams started to exist in May 1995, through the creation and +support by Patrick D'Cruze of twenty unmoderated mailing lists for that +many native languages, and two moderated lists: one for reaching all +teams at once, the other for reaching all willing maintainers of +internationalized free software packages. + + François also wrote PO mode in June 1995 with the collaboration of +Greg McGary, as a kind of contribution to Ulrich's package. He also +gave a hand with the GNU ‘gettext’ Texinfo manual. + + In 1997, Ulrich Drepper released the GNU libc 2.0, which included the +‘gettext’, ‘textdomain’ and ‘bindtextdomain’ functions. + + In 2000, Ulrich Drepper added plural form handling (the ‘ngettext’ +function) to GNU libc. Later, in 2001, he released GNU libc 2.2.x, +which is the first free C library with full internationalization +support. + + Ulrich being quite busy in his role of General Maintainer of GNU +libc, he handed over the GNU ‘gettext’ maintenance to Bruno Haible in +2000. Bruno added the plural form handling to the tools as well, added +support for UTF-8 and CJK locales, and wrote a few new tools for +manipulating PO files. + + +File: gettext.info, Node: The original ABOUT-NLS, Next: References, Prev: History, Up: Conclusion + +17.2 Notes on the Free Translation Project +========================================== + + This section contains the text that was, for a long time, distributed +as a file named ‘ABOUT-NLS’. + + * NOTE: * This documentation section is outdated. It it included +here for historical purposes only. + + Free software is going international! The Free Translation Project +is a way to get maintainers of free software, translators, and users all +together, so that free software will gradually become able to speak many +languages. A few packages already provide translations for their +messages. + + If you found this ‘ABOUT-NLS’ file inside a distribution, you may +assume that the distributed package does use GNU ‘gettext’ internally, +itself available at your nearest GNU archive site. But you do _not_ +need to install GNU ‘gettext’ prior to configuring, installing or using +this package with messages translated. + + Installers will find here some useful hints. These notes also +explain how users should proceed for getting the programs to use the +available translations. They tell how people wanting to contribute and +work on translations can contact the appropriate team. + +* Menu: + +* INSTALL Matters:: +* Using This Package:: +* Translating Teams:: +* Available Packages:: +* Using gettext in own code:: + + +File: gettext.info, Node: INSTALL Matters, Next: Using This Package, Up: The original ABOUT-NLS + +17.2.1 INSTALL Matters +---------------------- + + Some packages are “localizable” when properly installed; the programs +they contain can be made to speak your own native language. Most such +packages use GNU ‘gettext’. Other packages have their own ways to +internationalization, predating GNU ‘gettext’. + + By default, this package will be installed to allow translation of +messages. It will automatically detect whether the system already +provides the GNU ‘gettext’ functions. Installers may use special +options at configuration time for changing the default behaviour. The +command: + + ./configure --disable-nls + +will _totally_ disable translation of messages. + + When you already have GNU ‘gettext’ installed on your system and run +configure without an option for your new package, ‘configure’ will +probably detect the previously built and installed ‘libintl’ library and +will decide to use it. If not, you may have to to use the +‘--with-libintl-prefix’ option to tell ‘configure’ where to look for it. + + Internationalized packages usually have many ‘po/LL.po’ or +‘po/LL_CC.po’ files, where + + • LL gives an ISO 639 two-letter code identifying the language. For + some languages, a two-letter code does not exist, and a + three-letter code is used instead. + • The optional CC is an ISO 3166 two-letter code of a country or + territory. + +Unless translations have been forbidden at ‘configure’ time by using the +‘--disable-nls’ switch, all available translations are installed +together with the package. However, the environment variable ‘LINGUAS’ +may be set, prior to configuration, to limit the installed set. +‘LINGUAS’ should then contain a space separated list of locale names (of +the form ‘LL’ or ‘LL_CC’, stating which languages or language variants +are allowed. + + +File: gettext.info, Node: Using This Package, Next: Translating Teams, Prev: INSTALL Matters, Up: The original ABOUT-NLS + +17.2.2 Using This Package +------------------------- + + As a user, if your language has been installed for this package, you +only have to set the ‘LANG’ environment variable to the appropriate +‘LL_CC’ combination. If you happen to have the ‘LC_ALL’ or some other +‘LC_xxx’ environment variables set, you should unset them before setting +‘LANG’, otherwise the setting of ‘LANG’ will not have the desired +effect. Here + + • ‘LL’ is an ISO 639 two-letter language code. For some languages, a + two-letter code does not exist, and a three-letter code is used + instead. + • ‘CC’ is an ISO 3166 two-letter code of a country or territory. + +For example, let's suppose that you speak German and live in Germany. +At the shell prompt, merely execute ‘setenv LANG de_DE’ (in ‘csh’), +‘export LANG; LANG=de_DE’ (in ‘sh’) or ‘export LANG=de_DE’ (in ‘bash’). +This can be done from your ‘.login’ or ‘.profile’ file, once and for +all. + + You might think that the country code specification is redundant. +But in fact, some languages have dialects in different countries. For +example, ‘de_AT’ is used for Austria, and ‘pt_BR’ for Brazil. The +country code serves to distinguish the dialects. + + The locale naming convention of ‘LL_CC’, with ‘LL’ denoting the +language and ‘CC’ denoting the country, is the one use on systems based +on GNU libc. On other systems, some variations of this scheme are used, +such as ‘LL’ or ‘LL_CC.ENCODING’. You can get the list of locales +supported by your system for your language by running the command +‘locale -a | grep '^LL'’. + + Not all programs have translations for all languages. By default, an +English message is shown in place of a nonexistent translation. If you +understand other languages, you can set up a priority list of languages. +This is done through a different environment variable, called +‘LANGUAGE’. GNU ‘gettext’ gives preference to ‘LANGUAGE’ over ‘LANG’ +for the purpose of message handling, but you still need to have ‘LANG’ +set to the primary language; this is required by other parts of the +system libraries. For example, some Swedish users who would rather read +translations in German than English for when Swedish is not available, +set ‘LANGUAGE’ to ‘sv:de’ while leaving ‘LANG’ to ‘sv_SE’. + + Special advice for Norwegian users: The language code for Norwegian +bokmål changed from ‘no’ to ‘nb’ recently (in 2003). During the +transition period, while some message catalogs for this language are +installed under ‘nb’ and some older ones under ‘no’, it's recommended +for Norwegian users to set ‘LANGUAGE’ to ‘nb:no’ so that both newer and +older translations are used. + + In the ‘LANGUAGE’ environment variable, but not in the ‘LANG’ +environment variable, ‘LL_CC’ combinations can be abbreviated as ‘LL’ to +denote the language's main dialect. For example, ‘de’ is equivalent to +‘de_DE’ (German as spoken in Germany), and ‘pt’ to ‘pt_PT’ (Portuguese +as spoken in Portugal) in this context. + + +File: gettext.info, Node: Translating Teams, Next: Available Packages, Prev: Using This Package, Up: The original ABOUT-NLS + +17.2.3 Translating Teams +------------------------ + + For the Free Translation Project to be a success, we need interested +people who like their own language and write it well, and who are also +able to synergize with other translators speaking the same language. +Each translation team has its own mailing list. The up-to-date list of +teams can be found at the Free Translation Project's homepage, +‘https://translationproject.org/’, in the "Teams" area. + + If you'd like to volunteer to _work_ at translating messages, you +should become a member of the translating team for your own language. +The subscribing address is _not_ the same as the list itself, it has +‘-request’ appended. For example, speakers of Swedish can send a +message to ‘sv-request@li.org’, having this message body: + + subscribe + + Keep in mind that team members are expected to participate _actively_ +in translations, or at solving translational difficulties, rather than +merely lurking around. If your team does not exist yet and you want to +start one, or if you are unsure about what to do or how to get started, +please write to ‘coordinator@translationproject.org’ to reach the +coordinator for all translator teams. + + The English team is special. It works at improving and uniformizing +the terminology in use. Proven linguistic skills are praised more than +programming skills, here. + + +File: gettext.info, Node: Available Packages, Next: Using gettext in own code, Prev: Translating Teams, Up: The original ABOUT-NLS + +17.2.4 Available Packages +------------------------- + + Languages are not equally supported in all packages. The following +matrix shows the current state of internationalization, as of May 2025. +The matrix shows, in regard of each package, for which languages PO +files have been submitted to translation coordination, with a +translation percentage of at least 50%. + + Ready PO files ab af an ar ast be bg bn bn_IN ca ckb crh cs da + +-------------------------------------------------+ + a2ps | [] | + anubis | [] | + aspell | [] [] [] [] [] | + bash | [] [] [] | + beebase | | + bfd | | + binutils | [] | + bison | [] [] | + bison-runtime | [] [] [] [] | + buzztrax | [] [] | + ccd2cue | [] | + ccide | [] | + cflow | | + chambercourt | | + clisp | [] | + coreutils | [] [] [] [] | + cpio | [] [] | + cppi | [] | + cpplib | | + cryptsetup | [] [] | + datamash | [] | + denemo | [] [] [] | + dfarc | [] [] | + dialog | [] [] [] [] [] | + dico | [] | + diffutils | [] [] [] | + dink | [] [] | + direvent | [] | + doodle | [] [] | + dos2unix | [] [] | + dos2unix-man | | + e2fsprogs | [] [] [] | + enscript | [] [] | + exif | [] [] [] | + fetchmail | [] [] [] | + findutils | [] [] [] [] | + flex | [] [] [] | + freedink | [] [] [] | + fusionforge | | + gas | | + gawk | [] [] | + gcal | [] [] | + gcc | | + gdbm | | + gettext-examples | [] [] [] [] [] [] | + gettext-runtime | [] [] [] [] [] | + gettext-tools | [] [] [] | + gnubik | [] [] | + gnuchess | [] | + gnucobol | | + gnulib | [] | + gnunet | | + gnunet-gtk | | + gnutls | [] | + gold | | + gphoto2 | [] [] | + gprof | [] [] | + grep | [] [] [] [] [] | + grip | [] [] [] [] | + grub | [] [] [] | + gsasl | [] | + gss | [] | + gst-plugins-bad | [] [] [] [] | + gst-plugins-base | [] [] [] [] | + gst-plugins-good | [] [] [] [] | + gst-plugins-ugly | [] [] [] [] [] | + gstreamer | [] [] [] [] [] | + gtick | [] [] | + gtkam | [] [] [] | + gtkspell | [] [] [] [] [] [] | + gutenprint | [] [] | + hello | [] | + help2man | [] | + help2man-texi | | + i18nparse | | + idutils | [] | + kbd | [] | + klavaro | [] [] [] [] [] [] | + ld | | + libc | [] [] [] [] [] | + libexif | [] | + libextractor | [] | + libgphoto2 | [] [] | + libgphoto2_port | [] [] | + libiconv | [] [] [] [] | + libidn | [] [] | + libidn2 | [] [] | + lilypond | [] [] [] | + lordsawar | [] [] | + lynx | [] [] [] | + m4 | [] | + mailfromd | [] | + mailutils | | + make | [] [] [] | + man-db | [] [] [] [] | + man-db-manpages | | + meritous | [] | + midi-instruments | [] [] [] [] | + minicom | [] [] | + mpop | | + msmtp | | + nano | [] [] [] | + opcodes | | + parted | [] [] | + pies | | + procps-ng | | + procps-ng-man | | + psmisc | [] [] [] | + psmisc-man | | + pspp | [] [] | + pyspread | [] | + radius | [] | + recode | [] [] [] [] | + recutils | | + rush | [] | + sarg | [] | + savane | | + sed | [] [] [] [] [] [] | + sharutils | [] | + shepherd | | + shishi | | + skribilo | [] | + solfege | [] [] [] | + solfege-manual | [] | + sudo | [] [] [] [] | + sudoers | [] [] | + sysstat | [] | + tar | [] [] [] [] | + texinfo | [] [] [] | + texinfo_document | [] | + tigervnc | [] [] | + tin | [] | + tin-man | | + trader | [] | + util-linux | [] [] | + util-linux-man | | + vmm | | + vorbis-tools | [] [] | + wastesedge | [] | + wcd | [] | + wcd-man | | + wdiff | [] [] [] | + wget | [] [] [] | + wget2 | | + wincoll | | + wyslij-po | [] | + xboard | [] | + xdg-user-dirs | [] [] [] [] [] [] [] [] [] [] [] [] [] | + xkeyboard-config | [] [] [] [] [] | + xz | [] | + xz-man | | + +-------------------------------------------------+ + ab af an ar ast be bg bn bn_IN ca ckb crh cs da + 1 3 2 6 15 14 31 1 1 52 1 1 62 95 + + de el en en_GB eo es et eu fa fi fr fur ga gd + +--------------------------------------------------+ + a2ps | [] [] [] [] [] | + anubis | [] [] [] [] | + aspell | [] [] [] [] [] [] [] [] | + bash | [] [] [] [] [] | + beebase | [] [] [] | + bfd | [] [] | + binutils | [] | + bison | [] [] [] [] [] [] [] | + bison-runtime | [] [] [] [] [] [] [] [] | + buzztrax | [] [] [] [] | + ccd2cue | [] [] [] [] | + ccide | [] [] [] [] [] [] | + cflow | [] [] [] | + chambercourt | [] [] | + clisp | [] [] [] [] | + coreutils | [] [] [] [] | + cpio | [] [] [] [] [] | + cppi | [] [] [] [] [] | + cpplib | [] [] | + cryptsetup | [] [] [] | + datamash | [] [] [] [] | + denemo | | + dfarc | [] [] [] [] [] [] | + dialog | [] [] [] [] [] [] [] [] [] [] [] | + dico | [] [] [] [] | + diffutils | [] [] [] [] [] [] | + dink | [] [] [] [] [] | + direvent | [] [] [] [] | + doodle | [] [] [] [] [] [] | + dos2unix | [] [] [] [] [] | + dos2unix-man | [] [] [] | + e2fsprogs | [] [] [] | + enscript | [] [] [] [] [] [] [] | + exif | [] [] [] [] [] [] | + fetchmail | () [] [] [] [] | + findutils | [] [] [] [] [] [] [] | + flex | [] [] [] [] [] [] | + freedink | [] [] [] [] [] [] [] [] | + fusionforge | [] [] [] | + gas | [] [] [] | + gawk | [] [] [] [] | + gcal | [] [] [] | + gcc | [] [] | + gdbm | [] [] [] [] | + gettext-examples | [] [] [] [] [] [] [] | + gettext-runtime | [] [] [] [] [] [] | + gettext-tools | [] [] [] [] | + gnubik | [] [] [] [] [] [] | + gnuchess | [] [] [] [] | + gnucobol | [] [] | + gnulib | [] [] [] [] [] | + gnunet | [] | + gnunet-gtk | [] [] | + gnutls | [] [] [] [] [] | + gold | [] [] [] | + gphoto2 | () [] [] | + gprof | [] [] [] [] [] [] | + grep | [] [] [] [] [] [] [] | + grip | [] [] [] [] [] | + grub | [] [] [] [] [] | + gsasl | [] [] [] [] [] [] | + gss | [] [] [] [] [] [] | + gst-plugins-bad | [] [] [] [] [] | + gst-plugins-base | [] [] [] [] [] [] [] | + gst-plugins-good | [] [] [] [] [] [] [] | + gst-plugins-ugly | [] [] [] [] [] [] [] [] | + gstreamer | [] [] [] [] [] [] [] [] | + gtick | () [] [] [] [] [] | + gtkam | () [] [] [] [] | + gtkspell | [] [] [] [] [] [] [] [] [] | + gutenprint | [] [] [] | + hello | [] [] [] [] [] | + help2man | [] [] [] [] [] [] | + help2man-texi | [] [] [] | + i18nparse | [] [] [] () | + idutils | [] [] [] [] [] [] | + kbd | [] [] [] [] [] | + klavaro | [] [] [] [] [] [] | + ld | [] [] | + libc | [] [] [] [] | + libexif | [] [] [] | + libextractor | [] [] [] | + libgphoto2 | () [] [] | + libgphoto2_port | () [] [] [] [] [] | + libiconv | [] [] [] [] [] [] [] | + libidn | [] [] [] [] [] | + libidn2 | [] [] [] [] [] | + lilypond | [] [] [] [] | + lordsawar | [] [] | + lynx | [] [] [] [] [] | + m4 | [] [] [] [] | + mailfromd | [] [] | + mailutils | [] [] [] [] | + make | [] [] [] [] [] | + man-db | [] [] [] [] | + man-db-manpages | [] [] [] | + meritous | [] | + midi-instruments | [] [] [] [] [] [] [] [] | + minicom | [] [] [] [] | + mpop | [] [] [] [] | + msmtp | [] [] [] [] | + nano | [] [] [] [] [] [] | + opcodes | [] [] | + parted | [] [] [] [] | + pies | [] [] [] | + procps-ng | [] [] [] | + procps-ng-man | | + psmisc | [] [] [] [] [] [] | + psmisc-man | [] [] | + pspp | [] [] [] [] | + pyspread | [] [] | + radius | [] [] | + recode | [] [] [] [] [] [] | + recutils | [] [] [] | + rush | [] [] [] [] | + sarg | [] [] [] | + savane | [] [] [] | + sed | [] [] [] [] [] [] [] [] | + sharutils | [] [] [] [] | + shepherd | [] | + shishi | [] [] [] | + skribilo | [] [] [] [] | + solfege | [] [] [] [] [] [] [] | + solfege-manual | [] [] [] [] [] | + sudo | [] [] [] [] [] [] | + sudoers | [] [] [] [] | + sysstat | [] [] [] [] [] | + tar | [] [] [] [] [] [] [] | + texinfo | [] [] [] [] | + texinfo_document | [] [] | + tigervnc | [] [] [] [] [] | + tin | [] [] [] | + tin-man | [] [] | + trader | [] [] [] [] [] | + util-linux | [] [] [] | + util-linux-man | [] [] | + vmm | | + vorbis-tools | [] [] [] [] | + wastesedge | [] | + wcd | [] [] [] [] [] [] | + wcd-man | [] [] | + wdiff | [] [] [] [] [] [] [] | + wget | [] [] [] [] [] [] [] | + wget2 | [] [] [] | + wincoll | [] [] [] [] | + wyslij-po | [] [] [] [] [] | + xboard | [] [] [] | + xdg-user-dirs | [] [] [] [] [] [] [] [] [] [] [] [] | + xkeyboard-config | [] [] [] [] [] [] | + xz | [] [] [] [] | + xz-man | [] [] | + +--------------------------------------------------+ + de el en en_GB eo es et eu fa fi fr fur ga gd + 131 23 1 5 81 121 19 8 5 74 142 25 26 2 + + gl gu he hi hr hu hy id is it ja ka kk kn ko ku + +-------------------------------------------------+ + a2ps | [] [] [] [] | + anubis | [] [] [] [] | + aspell | [] [] [] [] [] | + bash | [] [] [] | + beebase | () | + bfd | | + binutils | | + bison | [] | + bison-runtime | [] [] [] [] [] [] [] | + buzztrax | | + ccd2cue | [] | + ccide | [] [] [] | + cflow | | + chambercourt | | + clisp | | + coreutils | [] [] [] [] | + cpio | [] [] [] [] [] [] | + cppi | [] [] [] [] [] [] | + cpplib | | + cryptsetup | [] | + datamash | | + denemo | | + dfarc | [] [] [] | + dialog | [] [] [] [] [] [] [] [] [] | + dico | | + diffutils | [] [] [] [] [] [] [] | + dink | [] | + direvent | [] | + doodle | [] | + dos2unix | [] [] [] [] | + dos2unix-man | [] | + e2fsprogs | [] | + enscript | [] [] | + exif | [] [] [] [] [] [] [] [] [] | + fetchmail | [] [] [] | + findutils | [] [] [] [] [] [] | + flex | | + freedink | [] [] [] [] | + fusionforge | | + gas | [] | + gawk | [] () [] | + gcal | | + gcc | | + gdbm | [] | + gettext-examples | [] [] [] [] [] [] [] | + gettext-runtime | [] [] [] [] [] [] | + gettext-tools | [] [] [] [] [] | + gnubik | [] [] [] [] | + gnuchess | [] | + gnucobol | | + gnulib | [] [] | + gnunet | | + gnunet-gtk | | + gnutls | [] [] | + gold | | + gphoto2 | [] [] [] [] [] [] | + gprof | [] [] [] [] | + grep | [] [] [] [] [] [] [] [] | + grip | [] [] [] [] | + grub | [] [] [] [] [] [] [] [] | + gsasl | [] [] [] [] | + gss | [] [] [] [] [] | + gst-plugins-bad | [] [] [] [] [] | + gst-plugins-base | [] [] [] [] [] [] | + gst-plugins-good | [] [] [] [] [] [] [] | + gst-plugins-ugly | [] [] [] [] [] [] [] | + gstreamer | [] [] [] [] [] | + gtick | [] [] [] [] | + gtkam | [] [] [] [] [] [] | + gtkspell | [] [] [] [] [] [] [] [] [] [] | + gutenprint | [] [] [] [] [] | + hello | [] [] | + help2man | [] [] [] [] | + help2man-texi | | + i18nparse | [] | + idutils | [] [] [] | + kbd | [] | + klavaro | [] [] [] [] [] [] | + ld | | + libc | [] [] [] [] [] [] | + libexif | [] | + libextractor | | + libgphoto2 | | + libgphoto2_port | [] [] [] | + libiconv | [] [] [] [] [] [] [] [] | + libidn | [] [] [] [] [] | + libidn2 | [] [] [] [] | + lilypond | [] [] | + lordsawar | [] | + lynx | [] [] [] [] | + m4 | [] | + mailfromd | | + mailutils | | + make | [] [] [] [] [] | + man-db | [] [] [] [] | + man-db-manpages | [] [] | + meritous | | + midi-instruments | [] [] [] [] [] [] [] [] [] [] [] [] | + minicom | [] [] [] [] [] | + mpop | | + msmtp | | + nano | [] [] [] [] [] [] [] [] | + opcodes | | + parted | [] [] [] [] [] [] | + pies | | + procps-ng | [] | + procps-ng-man | | + psmisc | [] [] [] [] [] [] | + psmisc-man | [] [] | + pspp | [] [] | + pyspread | | + radius | [] | + recode | [] [] [] [] [] [] | + recutils | | + rush | | + sarg | [] | + savane | [] | + sed | [] [] [] [] [] [] [] [] | + sharutils | | + shepherd | | + shishi | | + skribilo | [] | + solfege | [] [] | + solfege-manual | | + sudo | [] [] [] [] [] [] [] [] | + sudoers | [] [] [] [] [] | + sysstat | [] [] [] [] [] | + tar | [] [] [] [] [] [] | + texinfo | [] [] | + texinfo_document | [] [] | + tigervnc | [] [] [] [] | + tin | | + tin-man | | + trader | [] [] | + util-linux | [] [] [] | + util-linux-man | | + vmm | | + vorbis-tools | [] [] [] | + wastesedge | [] | + wcd | | + wcd-man | | + wdiff | [] [] [] | + wget | [] [] [] [] [] [] | + wget2 | [] [] [] [] | + wincoll | | + wyslij-po | [] [] [] [] | + xboard | | + xdg-user-dirs | [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] | + xkeyboard-config | [] [] [] [] [] [] [] [] | + xz | [] [] [] [] [] | + xz-man | [] [] | + +-------------------------------------------------+ + gl gu he hi hr hu hy id is it ja ka kk kn ko ku + 30 1 10 1 58 62 2 59 7 65 45 44 2 1 45 3 + + ky lg lt lv mk ml mn mr ms mt nb ne nl nn or pa + +-------------------------------------------------+ + a2ps | [] [] [] | + anubis | [] [] [] | + aspell | [] [] | + bash | [] [] | + beebase | [] | + bfd | | + binutils | | + bison | [] | + bison-runtime | [] [] [] [] [] [] | + buzztrax | | + ccd2cue | | + ccide | [] [] | + cflow | | + chambercourt | | + clisp | [] | + coreutils | [] [] | + cpio | [] | + cppi | | + cpplib | | + cryptsetup | | + datamash | [] [] | + denemo | [] | + dfarc | [] [] | + dialog | [] [] [] [] [] | + dico | | + diffutils | [] [] [] [] | + dink | [] | + direvent | [] | + doodle | [] | + dos2unix | [] [] | + dos2unix-man | [] | + e2fsprogs | [] | + enscript | [] | + exif | [] [] [] | + fetchmail | [] | + findutils | [] [] | + flex | [] | + freedink | [] [] [] | + fusionforge | | + gas | | + gawk | [] | + gcal | | + gcc | | + gdbm | | + gettext-examples | [] [] [] [] [] [] [] | + gettext-runtime | [] [] [] | + gettext-tools | | + gnubik | [] [] | + gnuchess | [] [] | + gnucobol | | + gnulib | [] | + gnunet | | + gnunet-gtk | | + gnutls | [] [] | + gold | | + gphoto2 | [] | + gprof | [] [] | + grep | [] [] | + grip | [] [] | + grub | [] [] [] | + gsasl | [] | + gss | | + gst-plugins-bad | [] [] [] | + gst-plugins-base | [] [] [] | + gst-plugins-good | [] [] [] | + gst-plugins-ugly | [] [] [] [] [] | + gstreamer | [] [] [] [] | + gtick | [] [] | + gtkam | [] [] [] | + gtkspell | [] [] [] [] [] [] [] | + gutenprint | [] | + hello | [] [] [] | + help2man | [] | + help2man-texi | | + i18nparse | [] | + idutils | [] [] | + kbd | | + klavaro | [] [] [] | + ld | | + libc | [] | + libexif | [] | + libextractor | [] | + libgphoto2 | [] | + libgphoto2_port | [] | + libiconv | [] [] | + libidn | [] | + libidn2 | [] [] | + lilypond | [] | + lordsawar | | + lynx | [] | + m4 | [] | + mailfromd | | + mailutils | | + make | [] | + man-db | [] | + man-db-manpages | | + meritous | | + midi-instruments | [] [] [] [] [] | + minicom | [] | + mpop | | + msmtp | | + nano | [] [] [] | + opcodes | | + parted | [] | + pies | | + procps-ng | | + procps-ng-man | | + psmisc | [] | + psmisc-man | | + pspp | [] [] | + pyspread | [] | + radius | [] | + recode | [] [] | + recutils | [] | + rush | [] | + sarg | | + savane | | + sed | [] [] | + sharutils | [] | + shepherd | | + shishi | | + skribilo | | + solfege | [] [] | + solfege-manual | [] | + sudo | [] [] | + sudoers | [] | + sysstat | [] [] [] | + tar | [] [] [] | + texinfo | [] [] | + texinfo_document | | + tigervnc | | + tin | | + tin-man | | + trader | [] | + util-linux | [] | + util-linux-man | | + vmm | | + vorbis-tools | [] | + wastesedge | [] | + wcd | [] | + wcd-man | [] | + wdiff | [] [] [] | + wget | [] [] | + wget2 | | + wincoll | | + wyslij-po | [] [] | + xboard | [] | + xdg-user-dirs | [] [] [] [] [] [] [] [] [] [] [] [] | + xkeyboard-config | [] [] | + xz | [] | + xz-man | | + +-------------------------------------------------+ + ky lg lt lv mk ml mn mr ms mt nb ne nl nn or pa + 5 1 10 17 2 1 3 1 15 2 44 1 95 5 1 3 + + pl pt pt_BR ro ru rw sk sl sq sr sv sw ta te + +-------------------------------------------------+ + a2ps | [] [] [] [] [] | + anubis | [] [] [] [] [] [] | + aspell | [] [] [] [] [] [] [] [] [] [] | + bash | [] [] [] [] [] [] | + beebase | [] [] [] | + bfd | [] [] [] [] [] | + binutils | [] [] [] [] [] | + bison | [] [] [] [] [] | + bison-runtime | [] [] [] [] [] [] [] [] [] [] | + buzztrax | [] [] [] [] | + ccd2cue | [] [] [] [] | + ccide | [] [] [] [] [] | + cflow | [] [] [] [] [] | + chambercourt | [] [] [] [] | + clisp | [] [] [] | + coreutils | [] [] [] [] [] [] [] [] | + cpio | [] [] [] [] [] [] [] | + cppi | [] [] [] [] [] | + cpplib | [] [] | + cryptsetup | [] [] [] [] [] | + datamash | [] [] [] [] | + denemo | | + dfarc | [] [] [] [] [] | + dialog | [] [] [] [] [] [] [] [] [] [] [] | + dico | [] [] [] [] [] | + diffutils | [] [] [] [] [] [] [] | + dink | [] | + direvent | [] [] [] [] [] | + doodle | [] [] [] [] [] | + dos2unix | [] [] [] [] [] [] | + dos2unix-man | [] [] [] [] [] | + e2fsprogs | [] [] [] [] [] | + enscript | [] [] [] [] [] [] [] | + exif | [] [] [] [] [] [] [] [] | + fetchmail | [] [] [] [] [] [] | + findutils | [] [] [] [] [] [] [] [] | + flex | [] [] [] [] [] [] [] | + freedink | [] [] [] [] [] [] [] | + fusionforge | | + gas | [] [] [] | + gawk | [] [] [] [] [] [] | + gcal | [] [] [] | + gcc | [] [] | + gdbm | [] [] [] [] [] [] | + gettext-examples | [] [] [] [] [] [] [] [] [] [] [] | + gettext-runtime | [] [] [] [] [] [] [] [] [] | + gettext-tools | [] [] [] [] [] [] [] [] [] | + gnubik | [] [] [] [] [] [] [] | + gnuchess | [] [] [] [] | + gnucobol | [] | + gnulib | [] [] [] [] [] [] [] | + gnunet | [] | + gnunet-gtk | [] | + gnutls | [] [] [] [] [] | + gold | [] [] | + gphoto2 | [] [] [] [] [] [] | + gprof | [] [] [] [] [] | + grep | [] [] [] [] [] [] [] [] [] [] | + grip | [] [] [] [] [] | + grub | [] [] [] [] [] [] [] [] | + gsasl | [] [] [] [] [] [] | + gss | [] [] [] [] [] [] | + gst-plugins-bad | [] [] [] [] [] [] [] [] | + gst-plugins-base | [] [] [] [] [] [] [] [] | + gst-plugins-good | [] [] [] [] [] [] [] [] | + gst-plugins-ugly | [] [] [] [] [] [] [] [] [] [] | + gstreamer | [] [] [] [] [] [] [] [] | + gtick | [] [] [] [] [] [] [] | + gtkam | [] [] [] [] [] [] [] [] | + gtkspell | [] [] [] [] [] [] [] [] [] [] [] | + gutenprint | [] [] [] [] [] | + hello | [] [] [] [] [] [] [] [] [] | + help2man | [] [] [] [] [] [] | + help2man-texi | [] [] [] [] [] | + i18nparse | [] [] [] [] | + idutils | [] [] [] [] [] [] | + kbd | [] [] [] [] [] [] [] | + klavaro | [] [] [] [] [] [] [] [] [] | + ld | [] [] [] [] | + libc | [] [] [] [] [] [] [] [] | + libexif | [] [] [] [] [] | + libextractor | [] [] [] [] | + libgphoto2 | [] [] [] | + libgphoto2_port | [] [] [] [] [] [] [] | + libiconv | [] [] [] [] [] [] [] [] | + libidn | [] [] [] [] [] | + libidn2 | [] [] [] [] [] [] | + lilypond | [] [] | + lordsawar | [] [] | + lynx | [] [] [] [] | + m4 | [] [] [] [] [] | + mailfromd | [] [] [] [] | + mailutils | [] [] [] [] | + make | [] [] [] [] [] [] [] | + man-db | [] [] [] [] [] [] [] | + man-db-manpages | [] [] [] [] [] [] [] | + meritous | [] [] [] [] | + midi-instruments | [] [] [] [] [] [] [] [] [] | + minicom | [] [] [] [] [] [] | + mpop | [] [] [] [] [] | + msmtp | [] [] [] [] [] | + nano | [] [] [] [] [] [] [] [] [] | + opcodes | [] [] [] [] | + parted | [] [] [] [] [] [] [] [] [] | + pies | [] [] [] [] | + procps-ng | [] [] [] [] | + procps-ng-man | [] [] | + psmisc | [] [] [] [] [] [] [] | + psmisc-man | [] [] [] [] [] | + pspp | [] [] [] | + pyspread | [] [] [] | + radius | [] [] [] | + recode | [] [] [] [] [] [] [] [] [] | + recutils | [] [] [] [] | + rush | [] [] [] [] [] | + sarg | [] [] [] [] | + savane | [] [] () | + sed | [] [] [] [] [] [] [] [] [] | + sharutils | [] [] [] [] [] | + shepherd | [] [] [] [] | + shishi | [] [] [] [] | + skribilo | [] [] [] [] | + solfege | [] [] [] [] [] [] | + solfege-manual | [] [] [] [] | + sudo | [] [] [] [] [] [] [] | + sudoers | [] [] [] [] [] [] [] | + sysstat | [] [] [] [] [] [] | + tar | [] [] [] [] [] [] [] [] | + texinfo | [] [] [] [] [] [] [] [] | + texinfo_document | [] [] [] [] [] [] [] | + tigervnc | [] [] [] [] [] | + tin | [] | + tin-man | | + trader | [] [] [] [] [] | + util-linux | [] [] [] [] [] [] | + util-linux-man | [] [] [] | + vmm | [] [] | + vorbis-tools | [] [] [] [] [] [] | + wastesedge | [] [] | + wcd | [] [] [] [] | + wcd-man | [] [] [] [] | + wdiff | [] [] [] [] [] [] [] | + wget | [] [] [] [] [] [] [] [] | + wget2 | [] [] [] [] [] | + wincoll | [] [] [] [] [] | + wyslij-po | [] [] [] [] [] | + xboard | [] [] [] [] [] | + xdg-user-dirs | [] [] [] [] [] [] [] [] [] [] [] [] | + xkeyboard-config | [] [] [] [] [] [] [] [] [] | + xz | [] [] [] [] [] [] | + xz-man | [] [] [] | + +-------------------------------------------------+ + pl pt pt_BR ro ru rw sk sl sq sr sv sw ta te + 99 49 113 135 85 0 37 32 11 130 131 1 8 1 + + tg th tr uk ur vi wa wo zh_CN zh_HK zh_TW + +--------------------------------------------+ + a2ps | [] [] | 20 + anubis | [] [] [] | 21 + aspell | [] [] [] [] | 34 + bash | [] [] [] [] | 23 + beebase | [] | 8 + bfd | [] | 8 + binutils | [] | 8 + bison | [] [] | 18 + bison-runtime | [] [] [] [] [] [] | 41 + buzztrax | [] [] | 12 + ccd2cue | [] [] [] [] | 14 + ccide | [] [] [] | 20 + cflow | [] [] | 10 + chambercourt | [] | 7 + clisp | | 13 + coreutils | [] [] [] [] [] | 27 + cpio | [] [] [] [] | 25 + cppi | [] [] [] | 20 + cpplib | [] [] | 6 + cryptsetup | [] [] | 13 + datamash | [] | 12 + denemo | [] [] [] | 7 + dfarc | [] | 19 + dialog | [] [] [] [] [] [] [] | 48 + dico | [] | 11 + diffutils | [] [] [] [] [] | 32 + dink | [] | 11 + direvent | [] [] | 14 + doodle | [] [] [] | 18 + dos2unix | [] [] [] [] | 23 + dos2unix-man | [] [] | 12 + e2fsprogs | [] [] [] | 16 + enscript | [] [] [] | 22 + exif | [] [] [] [] | 33 + fetchmail | [] [] | 19 + findutils | [] [] [] [] [] | 32 + flex | [] [] [] [] [] | 22 + freedink | [] [] | 27 + fusionforge | | 3 + gas | [] | 8 + gawk | [] [] [] [] | 19 + gcal | [] [] | 10 + gcc | [] | 5 + gdbm | [] [] | 13 + gettext-examples | [] [] [] [] [] [] | 44 + gettext-runtime | [] [] [] [] [] | 34 + gettext-tools | [] [] [] [] [] | 26 + gnubik | [] [] [] | 24 + gnuchess | [] [] [] | 15 + gnucobol | | 3 + gnulib | [] [] [] | 19 + gnunet | | 2 + gnunet-gtk | | 3 + gnutls | [] [] [] | 18 + gold | [] | 6 + gphoto2 | [] [] [] [] | 21 + gprof | [] [] [] | 22 + grep | [] [] [] [] [] [] | 38 + grip | [] [] [] [] [] | 25 + grub | [] [] [] [] | 31 + gsasl | [] [] [] | 21 + gss | [] [] | 20 + gst-plugins-bad | [] [] [] [] [] | 30 + gst-plugins-base | [] [] [] [] | 32 + gst-plugins-good | [] [] [] [] [] | 34 + gst-plugins-ugly | [] [] [] [] [] | 40 + gstreamer | [] [] [] [] [] | 35 + gtick | [] [] [] | 23 + gtkam | [] [] [] | 27 + gtkspell | [] [] [] [] [] [] [] [] | 51 + gutenprint | [] [] [] | 19 + hello | [] [] [] | 23 + help2man | [] [] [] | 21 + help2man-texi | [] | 9 + i18nparse | [] | 10 + idutils | [] [] [] | 21 + kbd | [] | 15 + klavaro | [] [] [] [] [] [] | 36 + ld | [] | 7 + libc | [] [] [] [] [] | 29 + libexif | [] [] | 13 + libextractor | [] [] | 11 + libgphoto2 | [] [] | 10 + libgphoto2_port | [] [] [] [] | 22 + libiconv | [] [] [] [] [] | 34 + libidn | [] [] [] | 21 + libidn2 | [] [] | 21 + lilypond | [] | 13 + lordsawar | [] | 8 + lynx | [] [] [] | 20 + m4 | [] [] | 14 + mailfromd | [] [] | 9 + mailutils | [] [] | 10 + make | [] [] [] [] | 25 + man-db | [] [] [] [] [] | 25 + man-db-manpages | [] [] [] | 15 + meritous | | 6 + midi-instruments | [] [] [] [] [] [] | 44 + minicom | [] [] | 20 + mpop | [] | 10 + msmtp | [] | 10 + nano | [] [] [] [] [] | 34 + opcodes | [] | 7 + parted | [] [] [] [] [] | 27 + pies | [] [] | 9 + procps-ng | [] [] [] | 11 + procps-ng-man | [] [] | 4 + psmisc | [] [] [] [] | 27 + psmisc-man | [] | 10 + pspp | [] [] [] | 16 + pyspread | [] | 8 + radius | [] [] | 10 + recode | [] [] [] [] | 31 + recutils | [] [] | 10 + rush | [] [] [] | 14 + sarg | | 9 + savane | [] | 7 + sed | [] [] [] [] [] | 38 + sharutils | [] [] [] | 14 + shepherd | [] | 6 + shishi | [] [] | 9 + skribilo | [] | 11 + solfege | [] [] [] | 23 + solfege-manual | [] | 12 + sudo | [] [] [] [] [] | 32 + sudoers | [] [] [] | 22 + sysstat | [] [] [] [] | 24 + tar | [] [] [] [] [] | 33 + texinfo | [] [] [] | 22 + texinfo_document | [] | 13 + tigervnc | [] [] [] [] | 20 + tin | [] [] [] | 8 + tin-man | | 2 + trader | | 14 + util-linux | [] [] [] | 18 + util-linux-man | [] | 6 + vmm | [] | 3 + vorbis-tools | [] | 17 + wastesedge | [] | 7 + wcd | [] [] [] | 15 + wcd-man | [] | 8 + wdiff | [] [] [] [] | 27 + wget | [] [] [] [] [] | 31 + wget2 | [] [] | 14 + wincoll | [] | 10 + wyslij-po | [] [] [] | 20 + xboard | [] [] [] | 13 + xdg-user-dirs | [] [] [] [] [] [] [] [] | 72 + xkeyboard-config | [] [] [] | 33 + xz | [] [] [] [] [] | 22 + xz-man | [] | 8 + +--------------------------------------------+ + 85 teams tg th tr uk ur vi wa wo zh_CN zh_HK zh_TW + 151 domains 0 11 52 125 1 87 5 1 90 5 42 2840 + + Some counters in the preceding matrix are higher than the number of +visible blocks let us expect. This is because a few extra PO files are +used for implementing regional variants of languages, or language +dialects. + + For a PO file in the matrix above to be effective, the package to +which it applies should also have been internationalized and distributed +as such by its maintainer. There might be an observable lag between the +mere existence a PO file and its wide availability in a distribution. + + If May 2025 seems to be old, you may fetch a more recent copy of this +‘ABOUT-NLS’ file on most GNU archive sites. The most up-to-date matrix +with full percentage details can be found at +‘https://translationproject.org/extra/matrix.html’. + + +File: gettext.info, Node: Using gettext in own code, Prev: Available Packages, Up: The original ABOUT-NLS + +17.2.5 Using ‘gettext’ in new packages +-------------------------------------- + + If you are writing a freely available program and want to +internationalize it you are welcome to use GNU ‘gettext’ in your +package. Of course you have to respect the GNU Lesser General Public +License which covers the use of the GNU ‘gettext’ library. This means +in particular that even non-free programs can use ‘libintl’ as a shared +library, whereas only free software can use ‘libintl’ as a static +library or use modified versions of ‘libintl’. + + Once the sources are changed appropriately and the setup can handle +the use of ‘gettext’ the only thing missing are the translations. The +Free Translation Project is also available for packages which are not +developed inside the GNU project. Therefore the information given above +applies also for every other Free Software Project. Contact +‘coordinator@translationproject.org’ to make the ‘.pot’ files available +to the translation teams. + + +File: gettext.info, Node: References, Prev: The original ABOUT-NLS, Up: Conclusion + +17.3 Related Readings +===================== + + * NOTE: * This documentation section is outdated and needs to be +revised. + + Eugene H. Dorr (‘dorre@well.com’) maintains an interesting +bibliography on internationalization matters, called +‘Internationalization Reference List’, which is available as: + ftp://ftp.ora.com/pub/examples/nutshell/ujip/doc/i18n-books.txt + + Michael Gschwind (‘mike@vlsivie.tuwien.ac.at’) maintains a Frequently +Asked Questions (FAQ) list, entitled ‘Programming for +Internationalisation’. This FAQ discusses writing programs which can +handle different language conventions, character sets, etc.; and is +applicable to all character set encodings, with particular emphasis on +ISO 8859-1. It is regularly published in Usenet groups +‘comp.unix.questions’, ‘comp.std.internat’, +‘comp.software.international’, ‘comp.lang.c’, ‘comp.windows.x’, +‘comp.std.c’, ‘comp.answers’ and ‘news.answers’. The home location of +this document is: + ftp://ftp.vlsivie.tuwien.ac.at/pub/8bit/ISO-programming + + Patrick D'Cruze (‘pdcruze@li.org’) wrote a tutorial about NLS +matters, and Jochen Hein (‘Hein@student.tu-clausthal.de’) took over the +responsibility of maintaining it. It may be found as: + ftp://sunsite.unc.edu/pub/Linux/utils/nls/catalogs/Incoming/... + ...locale-tutorial-0.8.txt.gz +This site is mirrored in: + ftp://ftp.ibp.fr/pub/linux/sunsite/ + + A French version of the same tutorial should be findable at: + ftp://ftp.ibp.fr/pub/linux/french/docs/ +together with French translations of many Linux-related documents. + + +File: gettext.info, Node: Language Codes, Next: Country Codes, Prev: Conclusion, Up: Top + +Appendix A Language Codes +************************* + + The ISO 639 standard defines two-letter codes for many languages, and +three-letter codes for more rarely used languages. All abbreviations +for languages used in the Translation Project should come from this +standard. + +* Menu: + +* Usual Language Codes:: Two-letter ISO 639 language codes +* Rare Language Codes:: Three-letter ISO 639 language codes + + +File: gettext.info, Node: Usual Language Codes, Next: Rare Language Codes, Up: Language Codes + +A.1 Usual Language Codes +======================== + + For the commonly used languages, the ISO 639-1 standard defines +two-letter codes. + +‘aa’ + Afar. +‘ab’ + Abkhazian. +‘ae’ + Avestan. +‘af’ + Afrikaans. +‘ak’ + Akan. +‘am’ + Amharic. +‘an’ + Aragonese. +‘ar’ + Arabic. +‘as’ + Assamese. +‘av’ + Avaric. +‘ay’ + Aymara. +‘az’ + Azerbaijani. +‘ba’ + Bashkir. +‘be’ + Belarusian. +‘bg’ + Bulgarian. +‘bh’ + Bihari languages. +‘bi’ + Bislama. +‘bm’ + Bambara. +‘bn’ + Bengali. +‘bo’ + Tibetan. +‘br’ + Breton. +‘bs’ + Bosnian. +‘ca’ + Catalan; Valencian. +‘ce’ + Chechen. +‘ch’ + Chamorro. +‘co’ + Corsican. +‘cr’ + Cree. +‘cs’ + Czech. +‘cu’ + Church Slavic; Old Slavonic; Church Slavonic; Old Bulgarian; Old + Church Slavonic. +‘cv’ + Chuvash. +‘cy’ + Welsh. +‘da’ + Danish. +‘de’ + German. +‘dv’ + Divehi; Dhivehi; Maldivian. +‘dz’ + Dzongkha. +‘ee’ + Ewe. +‘el’ + Greek, Modern (1453-). +‘en’ + English. +‘eo’ + Esperanto. +‘es’ + Spanish; Castilian. +‘et’ + Estonian. +‘eu’ + Basque. +‘fa’ + Persian. +‘ff’ + Fulah. +‘fi’ + Finnish. +‘fj’ + Fijian. +‘fo’ + Faroese. +‘fr’ + French. +‘fy’ + Western Frisian. +‘ga’ + Irish. +‘gd’ + Gaelic; Scottish Gaelic. +‘gl’ + Galician. +‘gn’ + Guarani. +‘gu’ + Gujarati. +‘gv’ + Manx. +‘ha’ + Hausa. +‘he’ + Hebrew. +‘hi’ + Hindi. +‘ho’ + Hiri Motu. +‘hr’ + Croatian. +‘ht’ + Haitian; Haitian Creole. +‘hu’ + Hungarian. +‘hy’ + Armenian. +‘hz’ + Herero. +‘ia’ + Interlingua (International Auxiliary Language Association). +‘id’ + Indonesian. +‘ie’ + Interlingue; Occidental. +‘ig’ + Igbo. +‘ii’ + Sichuan Yi; Nuosu. +‘ik’ + Inupiak. +‘io’ + Ido. +‘is’ + Icelandic. +‘it’ + Italian. +‘iu’ + Inuktitut. +‘ja’ + Japanese. +‘jv’ + Javanese. +‘ka’ + Georgian. +‘kg’ + Kongo. +‘ki’ + Kikuyu; Gikuyu. +‘kj’ + Kuanyama; Kwanyama. +‘kk’ + Kazakh. +‘kl’ + Kalaallisut; Greenlandic. +‘km’ + Central Khmer. +‘kn’ + Kannada. +‘ko’ + Korean. +‘kr’ + Kanuri. +‘ks’ + Kashmiri. +‘ku’ + Kurdish. +‘kv’ + Komi. +‘kw’ + Cornish. +‘ky’ + Kirghiz; Kyrgyz. +‘la’ + Latin. +‘lb’ + Luxembourgish; Letzeburgesch. +‘lg’ + Ganda. +‘li’ + Limburgan; Limburger; Limburgish. +‘ln’ + Lingala. +‘lo’ + Lao. +‘lt’ + Lithuanian. +‘lu’ + Luba-Katanga. +‘lv’ + Latvian. +‘mg’ + Malagasy. +‘mh’ + Marshallese. +‘mi’ + Maori. +‘mk’ + Macedonian. +‘ml’ + Malayalam. +‘mn’ + Mongolian. +‘mr’ + Marathi. +‘ms’ + Malay. +‘mt’ + Maltese. +‘my’ + Burmese. +‘na’ + Nauru. +‘nb’ + Bokmål, Norwegian; Norwegian Bokmål. +‘nd’ + Ndebele, North; North Ndebele. +‘ne’ + Nepali. +‘ng’ + Ndonga. +‘nl’ + Dutch; Flemish. +‘nn’ + Norwegian Nynorsk; Nynorsk, Norwegian. +‘no’ + Norwegian. +‘nr’ + Ndebele, South; South Ndebele. +‘nv’ + Navajo; Navaho. +‘ny’ + Chichewa; Nyanja. +‘oc’ + Occitan (post 1500); Provençal. +‘oj’ + Ojibwa. +‘om’ + Oromo. +‘or’ + Oriya. +‘os’ + Ossetian; Ossetic. +‘pa’ + Panjabi; Punjabi. +‘pi’ + Pali. +‘pl’ + Polish. +‘ps’ + Pushto; Pashto. +‘pt’ + Portuguese. +‘qu’ + Quechua. +‘rm’ + Romansh. +‘rn’ + Rundi. +‘ro’ + Romanian; Moldavian; Moldovan. +‘ru’ + Russian. +‘rw’ + Kinyarwanda. +‘sa’ + Sanskrit. +‘sc’ + Sardinian. +‘sd’ + Sindhi. +‘se’ + Northern Sami. +‘sg’ + Sango. +‘si’ + Sinhala; Sinhalese. +‘sk’ + Slovak. +‘sl’ + Slovenian. +‘sm’ + Samoan. +‘sn’ + Shona. +‘so’ + Somali. +‘sq’ + Albanian. +‘sr’ + Serbian. +‘ss’ + Swati. +‘st’ + Sotho, Southern. +‘su’ + Sundanese. +‘sv’ + Swedish. +‘sw’ + Swahili. +‘ta’ + Tamil. +‘te’ + Telugu. +‘tg’ + Tajik. +‘th’ + Thai. +‘ti’ + Tigrinya. +‘tk’ + Turkmen. +‘tl’ + Tagalog. +‘tn’ + Tswana. +‘to’ + Tonga (Tonga Islands). +‘tr’ + Turkish. +‘ts’ + Tsonga. +‘tt’ + Tatar. +‘tw’ + Twi. +‘ty’ + Tahitian. +‘ug’ + Uighur; Uyghur. +‘uk’ + Ukrainian. +‘ur’ + Urdu. +‘uz’ + Uzbek. +‘ve’ + Venda. +‘vi’ + Vietnamese. +‘vo’ + Volapük. +‘wa’ + Walloon. +‘wo’ + Wolof. +‘xh’ + Xhosa. +‘yi’ + Yiddish. +‘yo’ + Yoruba. +‘za’ + Zhuang; Chuang. +‘zh’ + Chinese. +‘zu’ + Zulu. + + +File: gettext.info, Node: Rare Language Codes, Prev: Usual Language Codes, Up: Language Codes + +A.2 Rare Language Codes +======================= + + For rarely used languages, the ISO 639-2 standard defines +three-letter codes. Here is the current list, reduced to only living +languages with at least one million of speakers. + +‘ace’ + Achinese. +‘awa’ + Awadhi. +‘bal’ + Baluchi. +‘ban’ + Balinese. +‘bej’ + Beja; Bedawiyet. +‘bem’ + Bemba. +‘bho’ + Bhojpuri. +‘bik’ + Bikol. +‘bin’ + Bini; Edo. +‘bug’ + Buginese. +‘ceb’ + Cebuano. +‘din’ + Dinka. +‘doi’ + Dogri. +‘fil’ + Filipino; Pilipino. +‘fon’ + Fon. +‘gon’ + Gondi. +‘gsw’ + Swiss German; Alemannic; Alsatian. +‘hil’ + Hiligaynon. +‘hmn’ + Hmong. +‘ilo’ + Iloko. +‘kab’ + Kabyle. +‘kam’ + Kamba. +‘kbd’ + Kabardian. +‘kmb’ + Kimbundu. +‘kok’ + Konkani. +‘kru’ + Kurukh. +‘lua’ + Luba-Lulua. +‘luo’ + Luo (Kenya and Tanzania). +‘mad’ + Madurese. +‘mag’ + Magahi. +‘mai’ + Maithili. +‘mak’ + Makasar. +‘man’ + Mandingo. +‘men’ + Mende. +‘min’ + Minangkabau. +‘mni’ + Manipuri. +‘mos’ + Mossi. +‘mwr’ + Marwari. +‘nap’ + Neapolitan. +‘nso’ + Pedi; Sepedi; Northern Sotho. +‘nym’ + Nyamwezi. +‘nyn’ + Nyankole. +‘pag’ + Pangasinan. +‘pam’ + Pampanga; Kapampangan. +‘raj’ + Rajasthani. +‘sas’ + Sasak. +‘sat’ + Santali. +‘scn’ + Sicilian. +‘shn’ + Shan. +‘sid’ + Sidamo. +‘srr’ + Serer. +‘suk’ + Sukuma. +‘sus’ + Susu. +‘tem’ + Timne. +‘tiv’ + Tiv. +‘tum’ + Tumbuka. +‘umb’ + Umbundu. +‘wal’ + Walamo. +‘war’ + Waray. +‘yao’ + Yao. + + +File: gettext.info, Node: Country Codes, Next: Licenses, Prev: Language Codes, Up: Top + +Appendix B Country Codes +************************ + + The ISO 3166 standard defines two character codes for many countries +and territories. All abbreviations for countries used in the +Translation Project should come from this standard. + +‘AD’ + Andorra. +‘AE’ + United Arab Emirates. +‘AF’ + Afghanistan. +‘AG’ + Antigua and Barbuda. +‘AI’ + Anguilla. +‘AL’ + Albania. +‘AM’ + Armenia. +‘AO’ + Angola. +‘AQ’ + Antarctica. +‘AR’ + Argentina. +‘AS’ + American Samoa. +‘AT’ + Austria. +‘AU’ + Australia. +‘AW’ + Aruba. +‘AX’ + Aaland Islands. +‘AZ’ + Azerbaijan. +‘BA’ + Bosnia and Herzegovina. +‘BB’ + Barbados. +‘BD’ + Bangladesh. +‘BE’ + Belgium. +‘BF’ + Burkina Faso. +‘BG’ + Bulgaria. +‘BH’ + Bahrain. +‘BI’ + Burundi. +‘BJ’ + Benin. +‘BL’ + Saint Barthelemy. +‘BM’ + Bermuda. +‘BN’ + Brunei Darussalam. +‘BO’ + Bolivia, Plurinational State of. +‘BQ’ + Bonaire, Sint Eustatius and Saba. +‘BR’ + Brazil. +‘BS’ + Bahamas. +‘BT’ + Bhutan. +‘BV’ + Bouvet Island. +‘BW’ + Botswana. +‘BY’ + Belarus. +‘BZ’ + Belize. +‘CA’ + Canada. +‘CC’ + Cocos (Keeling) Islands. +‘CD’ + Congo, The Democratic Republic of the. +‘CF’ + Central African Republic. +‘CG’ + Congo. +‘CH’ + Switzerland. +‘CI’ + Côte d'Ivoire. +‘CK’ + Cook Islands. +‘CL’ + Chile. +‘CM’ + Cameroon. +‘CN’ + China. +‘CO’ + Colombia. +‘CR’ + Costa Rica. +‘CU’ + Cuba. +‘CV’ + Cape Verde. +‘CW’ + Curaçao. +‘CX’ + Christmas Island. +‘CY’ + Cyprus. +‘CZ’ + Czech Republic. +‘DE’ + Germany. +‘DJ’ + Djibouti. +‘DK’ + Denmark. +‘DM’ + Dominica. +‘DO’ + Dominican Republic. +‘DZ’ + Algeria. +‘EC’ + Ecuador. +‘EE’ + Estonia. +‘EG’ + Egypt. +‘EH’ + Western Sahara. +‘ER’ + Eritrea. +‘ES’ + Spain. +‘ET’ + Ethiopia. +‘FI’ + Finland. +‘FJ’ + Fiji. +‘FK’ + Falkland Islands (Malvinas). +‘FM’ + Micronesia, Federated States of. +‘FO’ + Faroe Islands. +‘FR’ + France. +‘GA’ + Gabon. +‘GB’ + United Kingdom. +‘GD’ + Grenada. +‘GE’ + Georgia. +‘GF’ + French Guiana. +‘GG’ + Guernsey. +‘GH’ + Ghana. +‘GI’ + Gibraltar. +‘GL’ + Greenland. +‘GM’ + Gambia. +‘GN’ + Guinea. +‘GP’ + Guadeloupe. +‘GQ’ + Equatorial Guinea. +‘GR’ + Greece. +‘GS’ + South Georgia and the South Sandwich Islands. +‘GT’ + Guatemala. +‘GU’ + Guam. +‘GW’ + Guinea-Bissau. +‘GY’ + Guyana. +‘HK’ + Hong Kong. +‘HM’ + Heard Island and McDonald Islands. +‘HN’ + Honduras. +‘HR’ + Croatia. +‘HT’ + Haiti. +‘HU’ + Hungary. +‘ID’ + Indonesia. +‘IE’ + Ireland. +‘IL’ + Israel. +‘IM’ + Isle of Man. +‘IN’ + India. +‘IO’ + British Indian Ocean Territory. +‘IQ’ + Iraq. +‘IR’ + Iran, Islamic Republic of. +‘IS’ + Iceland. +‘IT’ + Italy. +‘JE’ + Jersey. +‘JM’ + Jamaica. +‘JO’ + Jordan. +‘JP’ + Japan. +‘KE’ + Kenya. +‘KG’ + Kyrgyzstan. +‘KH’ + Cambodia. +‘KI’ + Kiribati. +‘KM’ + Comoros. +‘KN’ + Saint Kitts and Nevis. +‘KP’ + Korea, Democratic People's Republic of. +‘KR’ + Korea, Republic of. +‘KW’ + Kuwait. +‘KY’ + Cayman Islands. +‘KZ’ + Kazakhstan. +‘LA’ + Lao People's Democratic Republic. +‘LB’ + Lebanon. +‘LC’ + Saint Lucia. +‘LI’ + Liechtenstein. +‘LK’ + Sri Lanka. +‘LR’ + Liberia. +‘LS’ + Lesotho. +‘LT’ + Lithuania. +‘LU’ + Luxembourg. +‘LV’ + Latvia. +‘LY’ + Libya. +‘MA’ + Morocco. +‘MC’ + Monaco. +‘MD’ + Moldova, Republic of. +‘ME’ + Montenegro. +‘MF’ + Saint Martin (French part). +‘MG’ + Madagascar. +‘MH’ + Marshall Islands. +‘MK’ + North Macedonia. +‘ML’ + Mali. +‘MM’ + Myanmar. +‘MN’ + Mongolia. +‘MO’ + Macao. +‘MP’ + Northern Mariana Islands. +‘MQ’ + Martinique. +‘MR’ + Mauritania. +‘MS’ + Montserrat. +‘MT’ + Malta. +‘MU’ + Mauritius. +‘MV’ + Maldives. +‘MW’ + Malawi. +‘MX’ + Mexico. +‘MY’ + Malaysia. +‘MZ’ + Mozambique. +‘NA’ + Namibia. +‘NC’ + New Caledonia. +‘NE’ + Niger. +‘NF’ + Norfolk Island. +‘NG’ + Nigeria. +‘NI’ + Nicaragua. +‘NL’ + Netherlands. +‘NO’ + Norway. +‘NP’ + Nepal. +‘NR’ + Nauru. +‘NU’ + Niue. +‘NZ’ + New Zealand. +‘OM’ + Oman. +‘PA’ + Panama. +‘PE’ + Peru. +‘PF’ + French Polynesia. +‘PG’ + Papua New Guinea. +‘PH’ + Philippines. +‘PK’ + Pakistan. +‘PL’ + Poland. +‘PM’ + Saint Pierre and Miquelon. +‘PN’ + Pitcairn. +‘PR’ + Puerto Rico. +‘PS’ + Palestine, State of. +‘PT’ + Portugal. +‘PW’ + Palau. +‘PY’ + Paraguay. +‘QA’ + Qatar. +‘RE’ + Reunion. +‘RO’ + Romania. +‘RS’ + Serbia. +‘RU’ + Russian Federation. +‘RW’ + Rwanda. +‘SA’ + Saudi Arabia. +‘SB’ + Solomon Islands. +‘SC’ + Seychelles. +‘SD’ + Sudan. +‘SE’ + Sweden. +‘SG’ + Singapore. +‘SH’ + Saint Helena, Ascension and Tristan da Cunha. +‘SI’ + Slovenia. +‘SJ’ + Svalbard and Jan Mayen. +‘SK’ + Slovakia. +‘SL’ + Sierra Leone. +‘SM’ + San Marino. +‘SN’ + Senegal. +‘SO’ + Somalia. +‘SR’ + Suriname. +‘SS’ + South Sudan. +‘ST’ + Sao Tome and Principe. +‘SV’ + El Salvador. +‘SX’ + Sint Maarten (Dutch part). +‘SY’ + Syrian Arab Republic. +‘SZ’ + Swaziland. +‘TC’ + Turks and Caicos Islands. +‘TD’ + Chad. +‘TF’ + French Southern Territories. +‘TG’ + Togo. +‘TH’ + Thailand. +‘TJ’ + Tajikistan. +‘TK’ + Tokelau. +‘TL’ + Timor-Leste. +‘TM’ + Turkmenistan. +‘TN’ + Tunisia. +‘TO’ + Tonga. +‘TR’ + Türkiye. +‘TT’ + Trinidad and Tobago. +‘TV’ + Tuvalu. +‘TW’ + Taiwan, Province of China. +‘TZ’ + Tanzania, United Republic of. +‘UA’ + Ukraine. +‘UG’ + Uganda. +‘UM’ + United States Minor Outlying Islands. +‘US’ + United States. +‘UY’ + Uruguay. +‘UZ’ + Uzbekistan. +‘VA’ + Holy See (Vatican City State). +‘VC’ + Saint Vincent and the Grenadines. +‘VE’ + Venezuela, Bolivarian Republic of. +‘VG’ + Virgin Islands, British. +‘VI’ + Virgin Islands, U.S.. +‘VN’ + Viet Nam. +‘VU’ + Vanuatu. +‘WF’ + Wallis and Futuna. +‘WS’ + Samoa. +‘YE’ + Yemen. +‘YT’ + Mayotte. +‘ZA’ + South Africa. +‘ZM’ + Zambia. +‘ZW’ + Zimbabwe. + + +File: gettext.info, Node: Licenses, Next: Program Index, Prev: Country Codes, Up: Top + +Appendix C Licenses +******************* + + The files of this package are covered by the licenses indicated in +each particular file or directory. Here is a summary: + + • The ‘libintl’ and ‘libasprintf’ libraries are covered by the GNU + Lesser General Public License (LGPL). A copy of the license is + included in *note GNU LGPL::. + + • The executable programs of this package and the ‘libgettextpo’ + library are covered by the GNU General Public License (GPL). A copy + of the license is included in *note GNU GPL::. + + • 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 included in *note GNU FDL::. + 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 included in *note GNU GPL::. + +* Menu: + +* GNU GPL:: GNU General Public License +* GNU LGPL:: GNU Lesser General Public License +* GNU FDL:: GNU Free Documentation License + + +File: gettext.info, Node: GNU GPL, Next: GNU LGPL, Up: Licenses + +C.1 GNU GENERAL PUBLIC LICENSE +============================== + + Version 2, June 1991 + + Copyright © 1989, 1991 Free Software Foundation, Inc. + + + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + +Preamble +======== + + The licenses for most software are designed to take away your freedom +to share and change it. By contrast, the GNU General Public License is +intended to guarantee your freedom to share and change free software--to +make sure the software is free for all its users. This General Public +License applies to most of the Free Software Foundation's software and +to any other program whose authors commit to using it. (Some other Free +Software Foundation software is covered by the GNU Lesser General Public +License instead.) 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 +this service 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 make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the rights. +These restrictions translate to certain responsibilities for you if you +distribute copies of the software, or if you modify it. + + For example, if you distribute copies of such a program, whether +gratis or for a fee, you must give the recipients all the rights that +you have. 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. + + We protect your rights with two steps: (1) copyright the software, +and (2) offer you this license which gives you legal permission to copy, +distribute and/or modify the software. + + Also, for each author's protection and ours, we want to make certain +that everyone understands that there is no warranty for this free +software. If the software is modified by someone else and passed on, we +want its recipients to know that what they have is not the original, so +that any problems introduced by others will not reflect on the original +authors' reputations. + + Finally, any free program is threatened constantly by software +patents. We wish to avoid the danger that redistributors of a free +program will individually obtain patent licenses, in effect making the +program proprietary. To prevent this, we have made it clear that any +patent must be licensed for everyone's free use or not licensed at all. + + The precise terms and conditions for copying, distribution and +modification follow. + +TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION +=============================================================== + + 0. This License applies to any program or other work which contains a + notice placed by the copyright holder saying it may be distributed + under the terms of this General Public License. The "Program", + below, refers to any such program or work, and a "work based on the + Program" means either the Program or any derivative work under + copyright law: that is to say, a work containing the Program or a + portion of it, either verbatim or with modifications and/or + translated into another language. (Hereinafter, translation is + included without limitation in the term "modification".) Each + licensee is addressed as "you". + + Activities other than copying, distribution and modification are + not covered by this License; they are outside its scope. The act + of running the Program is not restricted, and the output from the + Program is covered only if its contents constitute a work based on + the Program (independent of having been made by running the + Program). Whether that is true depends on what the Program does. + + 1. You may copy and distribute 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 and disclaimer of warranty; keep intact all the + notices that refer to this License and to the absence of any + warranty; and give any other recipients of the Program a copy of + this License along with the Program. + + 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 Program or any portion of + it, thus forming a work based on the Program, 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. You must cause the modified files to carry prominent notices + stating that you changed the files and the date of any change. + + b. You must cause any work that you distribute or publish, that + in whole or in part contains or is derived from the Program or + any part thereof, to be licensed as a whole at no charge to + all third parties under the terms of this License. + + c. If the modified program normally reads commands interactively + when run, you must cause it, when started running for such + interactive use in the most ordinary way, to print or display + an announcement including an appropriate copyright notice and + a notice that there is no warranty (or else, saying that you + provide a warranty) and that users may redistribute the + program under these conditions, and telling the user how to + view a copy of this License. (Exception: if the Program + itself is interactive but does not normally print such an + announcement, your work based on the Program is not required + to print an announcement.) + + These requirements apply to the modified work as a whole. If + identifiable sections of that work are not derived from the + Program, 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 Program, 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 Program. + + In addition, mere aggregation of another work not based on the + Program with the Program (or with a work based on the Program) on a + volume of a storage or distribution medium does not bring the other + work under the scope of this License. + + 3. You may copy and distribute the Program (or a work based on it, + under Section 2) in object code or executable form under the terms + of Sections 1 and 2 above provided that you also do one of the + following: + + a. 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; or, + + b. Accompany it with a written offer, valid for at least three + years, to give any third party, for a charge no more than your + cost of physically performing source distribution, a complete + machine-readable copy of the corresponding source code, to be + distributed under the terms of Sections 1 and 2 above on a + medium customarily used for software interchange; or, + + c. Accompany it with the information you received as to the offer + to distribute corresponding source code. (This alternative is + allowed only for noncommercial distribution and only if you + received the program in object code or executable form with + such an offer, in accord with Subsection b above.) + + The source code for a work means the preferred form of the work for + making modifications to it. For an executable work, 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 executable. + However, as a special exception, the source code 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. + + If distribution of executable or 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 counts as + distribution of the source code, even though third parties are not + compelled to copy the source along with the object code. + + 4. You may not copy, modify, sublicense, or distribute the Program + except as expressly provided under this License. Any attempt + otherwise to copy, modify, sublicense or distribute the Program 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. + + 5. 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 Program or its derivative works. These actions + are prohibited by law if you do not accept this License. + Therefore, by modifying or distributing the Program (or any work + based on the Program), you indicate your acceptance of this License + to do so, and all its terms and conditions for copying, + distributing or modifying the Program or works based on it. + + 6. Each time you redistribute the Program (or any work based on the + Program), the recipient automatically receives a license from the + original licensor to copy, distribute or modify the Program 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 to this License. + + 7. 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 + Program at all. For example, if a patent license would not permit + royalty-free redistribution of the Program 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 Program. + + 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. + + 8. If the distribution and/or use of the Program is restricted in + certain countries either by patents or by copyrighted interfaces, + the original copyright holder who places the Program 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. + + 9. The Free Software Foundation may publish revised and/or new + versions of the 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 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 Program does not + specify a version number of this License, you may choose any + version ever published by the Free Software Foundation. + + 10. If you wish to incorporate parts of the Program into other free + programs whose distribution conditions are different, 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 + + 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, 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. + + 12. 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 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. + + END OF TERMS AND CONDITIONS + +Appendix: 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 +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 PROGRAM'S NAME AND A BRIEF IDEA OF WHAT IT DOES. + Copyright (C) YYYY 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 2 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 . + + Also add information on how to contact you by electronic and paper +mail. + + If the program is interactive, make it output a short notice like +this when it starts in an interactive mode: + + Gnomovision version 69, Copyright (C) YEAR NAME OF AUTHOR + Gnomovision 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, the +commands you use may be called something other than ‘show w’ and ‘show +c’; they could even be mouse-clicks or menu items--whatever suits your +program. + + You should also get your employer (if you work as a programmer) or +your school, if any, to sign a "copyright disclaimer" for the program, +if necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the program + `Gnomovision' (which makes passes at compilers) written by James Hacker. + + SIGNATURE OF MOE GHOUL, 1 April 1989 + Moe Ghoul, President of Vice + + This 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. + + +File: gettext.info, Node: GNU LGPL, Next: GNU FDL, Prev: GNU GPL, Up: Licenses + +C.2 GNU LESSER GENERAL PUBLIC LICENSE +===================================== + + Version 2.1, February 1999 + + Copyright © 1991, 1999 Free Software Foundation, Inc. + + + 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--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. + + 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. + +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. + + 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. + + 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. + + 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. + + 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. + + 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 +--------------------------- + +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 AN 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.1 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, see . + + 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 MOE GHOUL, 1 April 1990 + Moe Ghoul, President of Vice + + That's all there is to it! + + +File: gettext.info, Node: GNU FDL, Prev: GNU LGPL, Up: Licenses + +C.3 GNU Free Documentation License +================================== + + Version 1.3, 3 November 2008 + + Copyright © 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. + + + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + 0. PREAMBLE + + The purpose of this License is to make a manual, textbook, or other + functional and useful document “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. + + 1. 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 + ASCII without markup, Texinfo input format, LaTeX input format, + SGML or XML using a publicly available DTD, and standard-conforming + simple HTML, PostScript or PDF designed for human modification. + Examples of transparent image formats include PNG, XCF and JPG. + Opaque formats include proprietary formats that can be read and + edited only by proprietary word processors, SGML or XML for which + the DTD and/or processing tools are not generally available, and + the machine-generated HTML, PostScript or 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. + + The "publisher" means any person or entity that distributes copies + of the Document to the public. + + 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. + + 2. 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. + + 3. 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. + + 4. 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: + + A. 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. + + B. 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. + + C. State on the Title page the name of the publisher of the + Modified Version, as the publisher. + + D. Preserve all the copyright notices of the Document. + + E. Add an appropriate copyright notice for your modifications + adjacent to the other copyright notices. + + F. 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. + + G. Preserve in that license notice the full lists of Invariant + Sections and required Cover Texts given in the Document's + license notice. + + H. Include an unaltered copy of this License. + + I. 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. + + J. 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. + + K. 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. + + L. 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. + + M. Delete any section Entitled "Endorsements". Such a section + may not be included in the Modified Version. + + N. Do not retitle any existing section to be Entitled + "Endorsements" or to conflict in title with any Invariant + Section. + + O. Preserve any Warranty Disclaimers. + + 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. + + 5. 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." + + 6. 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. + + 7. 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. + + 8. 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. + + 9. TERMINATION + + You may not copy, modify, sublicense, or distribute the Document + except as expressly provided under this License. Any attempt + otherwise to copy, modify, sublicense, or distribute it is void, + and will automatically terminate your rights under this License. + + 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, receipt of a copy of some or all of the + same material does not give you any rights to use it. + + 10. 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 + . + + 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. If the Document specifies that a proxy can + decide which future versions of this License can be used, that + proxy's public statement of acceptance of a version permanently + authorizes you to choose that version for the Document. + + 11. RELICENSING + + "Massive Multiauthor Collaboration Site" (or "MMC Site") means any + World Wide Web server that publishes copyrightable works and also + provides prominent facilities for anybody to edit those works. A + public wiki that anybody can edit is an example of such a server. + A "Massive Multiauthor Collaboration" (or "MMC") contained in the + site means any set of copyrightable works thus published on the MMC + site. + + "CC-BY-SA" means the Creative Commons Attribution-Share Alike 3.0 + license published by Creative Commons Corporation, a not-for-profit + corporation with a principal place of business in San Francisco, + California, as well as future copyleft versions of that license + published by that same organization. + + "Incorporate" means to publish or republish a Document, in whole or + in part, as part of another Document. + + An MMC is "eligible for relicensing" if it is licensed under this + License, and if all works that were first published under this + License somewhere other than this MMC, and subsequently + incorporated in whole or in part into the MMC, (1) had no cover + texts or invariant sections, and (2) were thus incorporated prior + to November 1, 2008. + + The operator of an MMC Site may republish an MMC contained in the + site under CC-BY-SA on the same site at any time before August 1, + 2009, provided the MMC is eligible for relicensing. + +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: + + Copyright (C) YEAR YOUR NAME. + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.3 + 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''. + + If you have Invariant Sections, Front-Cover Texts and Back-Cover +Texts, replace the "with...Texts." line with this: + + with the Invariant Sections being LIST THEIR TITLES, with + the Front-Cover Texts being LIST, and with the Back-Cover Texts + being LIST. + + 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. + + +File: gettext.info, Node: Program Index, Next: Option Index, Prev: Licenses, Up: Top + +Program Index +************* + +[index] +* Menu: + +* autopoint: autopoint Invocation. + (line 6) +* boldquot: msgfilter Invocation. + (line 111) +* envsubst: envsubst Invocation. (line 6) +* gettext: sh. (line 22) +* gettext <1>: gettext Invocation. (line 6) +* gettextize: gettextize Invocation. + (line 34) +* msgattrib: msgattrib Invocation. + (line 6) +* msgcat: msgcat Invocation. (line 6) +* msgcmp: msgcmp Invocation. (line 6) +* msgcomm: msgcomm Invocation. (line 6) +* msgconv: msgconv Invocation. (line 6) +* msgen: msgen Invocation. (line 6) +* msgexec: msgexec Invocation. (line 6) +* msgfilter: msgfilter Invocation. + (line 6) +* msgfmt: msgfmt Invocation. (line 6) +* msggrep: msggrep Invocation. (line 6) +* msginit: msginit Invocation. (line 6) +* msgmerge: msgmerge Invocation. (line 6) +* msgunfmt: msgunfmt Invocation. (line 6) +* msguniq: msguniq Invocation. (line 6) +* ngettext: sh. (line 22) +* ngettext <1>: ngettext Invocation. (line 6) +* quot: msgfilter Invocation. + (line 107) +* recode-sr-latin: msgfilter Invocation. + (line 101) +* xgettext: xgettext Invocation. (line 6) + + +File: gettext.info, Node: Option Index, Next: Variable Index, Prev: Program Index, Up: Top + +Option Index +************ + +[index] +* Menu: + +* --add-comments, xgettext option: xgettext Invocation. (line 98) +* --add-location, msgattrib option: msgattrib Invocation. + (line 138) +* --add-location, msgcat option: msgcat Invocation. (line 118) +* --add-location, msgcomm option: msgcomm Invocation. (line 100) +* --add-location, msgconv option: msgconv Invocation. (line 80) +* --add-location, msgen option: msgen Invocation. (line 83) +* --add-location, msgfilter option: msgfilter Invocation. + (line 161) +* --add-location, msggrep option: msggrep Invocation. (line 152) +* --add-location, msgmerge option: msgmerge Invocation. (line 157) +* --add-location, msguniq option: msguniq Invocation. (line 97) +* --add-location, xgettext option: xgettext Invocation. (line 426) +* --alignment, msgfmt option: msgfmt Invocation. (line 319) +* --backup, msgmerge option: msgmerge Invocation. (line 62) +* --boost, xgettext option: xgettext Invocation. (line 361) +* --c++, xgettext option: xgettext Invocation. (line 67) +* --check-accelerators, msgfmt option: msgfmt Invocation. (line 281) +* --check-compatibility, msgfmt option: msgfmt Invocation. (line 277) +* --check-domain, msgfmt option: msgfmt Invocation. (line 272) +* --check-format, msgfmt option: msgfmt Invocation. (line 244) +* --check-header, msgfmt option: msgfmt Invocation. (line 267) +* --check, msgfmt option: msgfmt Invocation. (line 240) +* --check, xgettext option: xgettext Invocation. (line 128) +* --clear-fuzzy, msgattrib option: msgattrib Invocation. + (line 68) +* --clear-obsolete, msgattrib option: msgattrib Invocation. + (line 74) +* --clear-previous, msgattrib option: msgattrib Invocation. + (line 81) +* --color, msgattrib option: msgattrib Invocation. + (line 119) +* --color, msgcat option: msgcat Invocation. (line 99) +* --color, msgcat option <1>: The --color option. (line 6) +* --color, msgcomm option: msgcomm Invocation. (line 81) +* --color, msgconv option: msgconv Invocation. (line 61) +* --color, msgen option: msgen Invocation. (line 64) +* --color, msgfilter option: msgfilter Invocation. + (line 138) +* --color, msggrep option: msggrep Invocation. (line 134) +* --color, msginit option: msginit Invocation. (line 96) +* --color, msgmerge option: msgmerge Invocation. (line 138) +* --color, msgunfmt option: msgunfmt Invocation. (line 103) +* --color, msguniq option: msguniq Invocation. (line 78) +* --color, xgettext option: xgettext Invocation. (line 405) +* --comment, msggrep option: msggrep Invocation. (line 86) +* --compendium, msgmerge option: msgmerge Invocation. (line 36) +* --context, gettext option: gettext Invocation. (line 16) +* --context, ngettext option: ngettext Invocation. (line 15) +* --copyright-holder, xgettext option: xgettext Invocation. (line 506) +* --csharp-resources, msgfmt option: msgfmt Invocation. (line 40) +* --csharp-resources, msgunfmt option: msgunfmt Invocation. (line 23) +* --csharp, msgfmt option: msgfmt Invocation. (line 36) +* --csharp, msgunfmt option: msgunfmt Invocation. (line 19) +* --debug, xgettext option: xgettext Invocation. (line 365) +* --default-domain, xgettext option: xgettext Invocation. (line 38) +* --desktop, msgfmt option: msgfmt Invocation. (line 49) +* --directory, msgattrib option: msgattrib Invocation. + (line 19) +* --directory, msgcat option: msgcat Invocation. (line 35) +* --directory, msgcmp option: msgcmp Invocation. (line 27) +* --directory, msgcomm option: msgcomm Invocation. (line 30) +* --directory, msgconv option: msgconv Invocation. (line 19) +* --directory, msgen option: msgen Invocation. (line 25) +* --directory, msgexec option: msgexec Invocation. (line 54) +* --directory, msgfilter option: msgfilter Invocation. + (line 34) +* --directory, msgfmt option: msgfmt Invocation. (line 18) +* --directory, msggrep option: msggrep Invocation. (line 19) +* --directory, msgmerge option: msgmerge Invocation. (line 30) +* --directory, msguniq option: msguniq Invocation. (line 26) +* --directory, xgettext option: xgettext Invocation. (line 27) +* --domain, gettext option: gettext Invocation. (line 21) +* --domain, msggrep option: msggrep Invocation. (line 70) +* --domain, ngettext option: ngettext Invocation. (line 20) +* --dry-run, autopoint option: autopoint Invocation. + (line 31) +* --dry-run, gettextize option: gettextize Invocation. + (line 64) +* --empty, msgattrib option: msgattrib Invocation. + (line 84) +* --endianness, msgfmt option: msgfmt Invocation. (line 322) +* --exclude-file, xgettext option: xgettext Invocation. (line 93) +* --expression, msgfilter option: msgfilter Invocation. + (line 87) +* --extended-regexp, msggrep option: msggrep Invocation. (line 94) +* --extract-all, xgettext option: xgettext Invocation. (line 177) +* --extracted-comment, msggrep option: msggrep Invocation. (line 90) +* --file, msgfilter option: msgfilter Invocation. + (line 91) +* --file, msggrep option: msggrep Invocation. (line 106) +* --files-from, msgcat option: msgcat Invocation. (line 30) +* --files-from, msgcomm option: msgcomm Invocation. (line 25) +* --files-from, xgettext option: xgettext Invocation. (line 19) +* --fixed-strings, msggrep option: msggrep Invocation. (line 98) +* --flag, xgettext option: xgettext Invocation. (line 293) +* --for-msgfmt, msgmerge option: msgmerge Invocation. (line 99) +* --force-po, msgattrib option: msgattrib Invocation. + (line 127) +* --force-po, msgcat option: msgcat Invocation. (line 107) +* --force-po, msgcomm option: msgcomm Invocation. (line 89) +* --force-po, msgconv option: msgconv Invocation. (line 69) +* --force-po, msgen option: msgen Invocation. (line 72) +* --force-po, msgfilter option: msgfilter Invocation. + (line 146) +* --force-po, msggrep option: msggrep Invocation. (line 142) +* --force-po, msgmerge option: msgmerge Invocation. (line 146) +* --force-po, msgunfmt option: msgunfmt Invocation. (line 111) +* --force-po, msguniq option: msguniq Invocation. (line 86) +* --force-po, xgettext option: xgettext Invocation. (line 413) +* --force, autopoint option: autopoint Invocation. + (line 27) +* --force, gettextize option: gettextize Invocation. + (line 40) +* --foreign-user, xgettext option: xgettext Invocation. (line 521) +* --from-code, xgettext option: xgettext Invocation. (line 76) +* --fuzzy, msgattrib option: msgattrib Invocation. + (line 95) +* --generated, xgettext option: xgettext Invocation. (line 556) +* --help, autopoint option: autopoint Invocation. + (line 39) +* --help, envsubst option: envsubst Invocation. (line 21) +* --help, gettext option: gettext Invocation. (line 37) +* --help, gettextize option: gettextize Invocation. + (line 69) +* --help, msgattrib option: msgattrib Invocation. + (line 188) +* --help, msgcat option: msgcat Invocation. (line 168) +* --help, msgcmp option: msgcmp Invocation. (line 69) +* --help, msgcomm option: msgcomm Invocation. (line 155) +* --help, msgconv option: msgconv Invocation. (line 130) +* --help, msgen option: msgen Invocation. (line 133) +* --help, msgexec option: msgexec Invocation. (line 77) +* --help, msgfilter option: msgfilter Invocation. + (line 211) +* --help, msgfmt option: msgfmt Invocation. (line 342) +* --help, msggrep option: msggrep Invocation. (line 200) +* --help, msginit option: msginit Invocation. (line 131) +* --help, msgmerge option: msgmerge Invocation. (line 208) +* --help, msgunfmt option: msgunfmt Invocation. (line 155) +* --help, msguniq option: msguniq Invocation. (line 147) +* --help, ngettext option: ngettext Invocation. (line 36) +* --help, xgettext option: xgettext Invocation. (line 594) +* --ignore-case, msggrep option: msggrep Invocation. (line 110) +* --ignore-file, msgattrib option: msgattrib Invocation. + (line 91) +* --indent, msgattrib option: msgattrib Invocation. + (line 131) +* --indent, msgcat option: msgcat Invocation. (line 111) +* --indent, msgcomm option: msgcomm Invocation. (line 93) +* --indent, msgconv option: msgconv Invocation. (line 73) +* --indent, msgen option: msgen Invocation. (line 76) +* --indent, msgfilter option: msgfilter Invocation. + (line 149) +* --indent, msggrep option: msggrep Invocation. (line 145) +* --indent, msgmerge option: msgmerge Invocation. (line 150) +* --indent, msgunfmt option: msgunfmt Invocation. (line 115) +* --indent, msguniq option: msguniq Invocation. (line 90) +* --indent, xgettext option: xgettext Invocation. (line 417) +* --input, msgexec option: msgexec Invocation. (line 50) +* --input, msgfilter option: msgfilter Invocation. + (line 30) +* --input, msginit option: msginit Invocation. (line 51) +* --invert-match, msggrep option: msggrep Invocation. (line 114) +* --its, xgettext option: xgettext Invocation. (line 386) +* --itstool, xgettext option: xgettext Invocation. (line 449) +* --java, msgfmt option: msgfmt Invocation. (line 30) +* --java, msgunfmt option: msgunfmt Invocation. (line 16) +* --java2, msgfmt option: msgfmt Invocation. (line 33) +* --join-existing, xgettext option: xgettext Invocation. (line 89) +* --kde, xgettext option: xgettext Invocation. (line 357) +* --keep-header, msgfilter option: msgfilter Invocation. + (line 152) +* --keyword, msgfmt option: msgfmt Invocation. (line 140) +* --keyword, xgettext option: xgettext Invocation. (line 186) +* --lang, msgcat option: msgcat Invocation. (line 93) +* --lang, msgen option: msgen Invocation. (line 57) +* --lang, msgmerge option: msgmerge Invocation. (line 130) +* --language, msgfmt option: msgfmt Invocation. (line 180) +* --language, xgettext option: xgettext Invocation. (line 57) +* --less-than, msgcat option: msgcat Invocation. (line 56) +* --less-than, msgcomm option: msgcomm Invocation. (line 51) +* --locale, msgfmt option: msgfmt Invocation. (line 83) +* --locale, msgfmt option <1>: msgfmt Invocation. (line 106) +* --locale, msgfmt option <2>: msgfmt Invocation. (line 122) +* --locale, msgfmt option <3>: msgfmt Invocation. (line 146) +* --locale, msgfmt option <4>: msgfmt Invocation. (line 184) +* --locale, msginit option: msginit Invocation. (line 84) +* --locale, msgunfmt option: msgunfmt Invocation. (line 45) +* --locale, msgunfmt option <1>: msgunfmt Invocation. (line 62) +* --locale, msgunfmt option <2>: msgunfmt Invocation. (line 78) +* --location, msggrep option: msggrep Invocation. (line 65) +* --more-than, msgcat option: msgcat Invocation. (line 61) +* --more-than, msgcomm option: msgcomm Invocation. (line 56) +* --msgctxt, msggrep option: msggrep Invocation. (line 74) +* --msgid-bugs-address, xgettext option: xgettext Invocation. (line 534) +* --msgid, msggrep option: msggrep Invocation. (line 78) +* --msgstr-prefix, xgettext option: xgettext Invocation. (line 583) +* --msgstr-suffix, xgettext option: xgettext Invocation. (line 587) +* --msgstr, msggrep option: msggrep Invocation. (line 82) +* --multi-domain, msgcmp option: msgcmp Invocation. (line 35) +* --multi-domain, msgmerge option: msgmerge Invocation. (line 96) +* --newline, msgfilter option: msgfilter Invocation. + (line 59) +* --newline, msgfilter option <1>: msgexec Invocation. (line 19) +* --no-changelog, gettextize option: gettextize Invocation. + (line 50) +* --no-convert, msgfmt option: msgfmt Invocation. (line 301) +* --no-fuzzy-matching, msgcmp option: msgcmp Invocation. (line 39) +* --no-fuzzy-matching, msgmerge option: msgmerge Invocation. (line 107) +* --no-fuzzy, msgattrib option: msgattrib Invocation. + (line 45) +* --no-git, xgettext option: xgettext Invocation. (line 489) +* --no-hash, msgfmt option: msgfmt Invocation. (line 334) +* --no-location, msgattrib option: msgattrib Invocation. + (line 134) +* --no-location, msgcat option: msgcat Invocation. (line 114) +* --no-location, msgcomm option: msgcomm Invocation. (line 96) +* --no-location, msgconv option: msgconv Invocation. (line 76) +* --no-location, msgen option: msgen Invocation. (line 79) +* --no-location, msgfilter option: msgfilter Invocation. + (line 157) +* --no-location, msggrep option: msggrep Invocation. (line 148) +* --no-location, msgmerge option: msgmerge Invocation. (line 153) +* --no-location, msguniq option: msguniq Invocation. (line 93) +* --no-location, xgettext option: xgettext Invocation. (line 420) +* --no-obsolete, msgattrib option: msgattrib Invocation. + (line 51) +* --no-redundancy, msgfmt option: msgfmt Invocation. (line 307) +* --no-translator, msginit option: msginit Invocation. (line 91) +* --no-wrap, msgattrib option: msgattrib Invocation. + (line 169) +* --no-wrap, msgcat option: msgcat Invocation. (line 149) +* --no-wrap, msgcomm option: msgcomm Invocation. (line 131) +* --no-wrap, msgconv option: msgconv Invocation. (line 111) +* --no-wrap, msgen option: msgen Invocation. (line 114) +* --no-wrap, msgfilter option: msgfilter Invocation. + (line 192) +* --no-wrap, msggrep option: msggrep Invocation. (line 183) +* --no-wrap, msginit option: msginit Invocation. (line 121) +* --no-wrap, msgmerge option: msgmerge Invocation. (line 188) +* --no-wrap, msgunfmt option: msgunfmt Invocation. (line 140) +* --no-wrap, msguniq option: msguniq Invocation. (line 128) +* --no-wrap, xgettext option: xgettext Invocation. (line 460) +* --obsolete, msgattrib option: msgattrib Invocation. + (line 99) +* --omit-header, msgcomm option: msgcomm Invocation. (line 146) +* --omit-header, xgettext option: xgettext Invocation. (line 476) +* --only-file, msgattrib option: msgattrib Invocation. + (line 87) +* --only-fuzzy, msgattrib option: msgattrib Invocation. + (line 48) +* --only-obsolete, msgattrib option: msgattrib Invocation. + (line 54) +* --output-dir, xgettext option: xgettext Invocation. (line 47) +* --output-file, msgattrib option: msgattrib Invocation. + (line 30) +* --output-file, msgcat option: msgcat Invocation. (line 46) +* --output-file, msgcomm option: msgcomm Invocation. (line 41) +* --output-file, msgconv option: msgconv Invocation. (line 30) +* --output-file, msgen option: msgen Invocation. (line 36) +* --output-file, msgfilter option: msgfilter Invocation. + (line 45) +* --output-file, msgfmt option: msgfmt Invocation. (line 59) +* --output-file, msggrep option: msggrep Invocation. (line 30) +* --output-file, msginit option: msginit Invocation. (line 61) +* --output-file, msgmerge option: msgmerge Invocation. (line 51) +* --output-file, msgunfmt option: msgunfmt Invocation. (line 93) +* --output-file, msguniq option: msguniq Invocation. (line 37) +* --output, xgettext option: xgettext Invocation. (line 42) +* --package-name, xgettext option: xgettext Invocation. (line 527) +* --package-version, xgettext option: xgettext Invocation. (line 530) +* --po-dir, gettextize option: gettextize Invocation. + (line 43) +* --previous, msgattrib option: msgattrib Invocation. + (line 77) +* --previous, msgmerge option: msgmerge Invocation. (line 111) +* --properties-input, msgattrib option: msgattrib Invocation. + (line 107) +* --properties-input, msgcat option: msgcat Invocation. (line 74) +* --properties-input, msgcmp option: msgcmp Invocation. (line 57) +* --properties-input, msgcomm option: msgcomm Invocation. (line 69) +* --properties-input, msgconv option: msgconv Invocation. (line 49) +* --properties-input, msgen option: msgen Invocation. (line 46) +* --properties-input, msgexec option: msgexec Invocation. (line 65) +* --properties-input, msgfilter option: msgfilter Invocation. + (line 126) +* --properties-input, msgfmt option: msgfmt Invocation. (line 228) +* --properties-input, msggrep option: msggrep Invocation. (line 122) +* --properties-input, msginit option: msginit Invocation. (line 72) +* --properties-input, msgmerge option: msgmerge Invocation. (line 119) +* --properties-input, msguniq option: msguniq Invocation. (line 58) +* --properties-output, msgattrib option: msgattrib Invocation. + (line 153) +* --properties-output, msgcat option: msgcat Invocation. (line 133) +* --properties-output, msgcomm option: msgcomm Invocation. (line 115) +* --properties-output, msgconv option: msgconv Invocation. (line 95) +* --properties-output, msgen option: msgen Invocation. (line 98) +* --properties-output, msgfilter option: msgfilter Invocation. + (line 176) +* --properties-output, msggrep option: msggrep Invocation. (line 167) +* --properties-output, msginit option: msginit Invocation. (line 105) +* --properties-output, msgmerge option: msgmerge Invocation. (line 172) +* --properties-output, msgunfmt option: msgunfmt Invocation. (line 124) +* --properties-output, msguniq option: msguniq Invocation. (line 112) +* --properties-output, xgettext option: xgettext Invocation. (line 440) +* --qt, msgfmt option: msgfmt Invocation. (line 46) +* --qt, xgettext option: xgettext Invocation. (line 353) +* --quiet, msgfilter option: msgfilter Invocation. + (line 96) +* --quiet, msgmerge option: msgmerge Invocation. (line 221) +* --reference, xgettext option: xgettext Invocation. (line 565) +* --regexp=, msggrep option: msggrep Invocation. (line 102) +* --repeated, msguniq option: msguniq Invocation. (line 47) +* --replace-text, msgfmt option: msgfmt Invocation. (line 192) +* --resource, msgfmt option: msgfmt Invocation. (line 79) +* --resource, msgfmt option <1>: msgfmt Invocation. (line 102) +* --resource, msgunfmt option: msgunfmt Invocation. (line 41) +* --resource, msgunfmt option <1>: msgunfmt Invocation. (line 58) +* --sentence-end, xgettext option: xgettext Invocation. (line 164) +* --set-fuzzy, msgattrib option: msgattrib Invocation. + (line 65) +* --set-obsolete, msgattrib option: msgattrib Invocation. + (line 71) +* --silent, msgfilter option: msgfilter Invocation. + (line 96) +* --silent, msgmerge option: msgmerge Invocation. (line 221) +* --sort-by-file, msgattrib option: msgattrib Invocation. + (line 181) +* --sort-by-file, msgcat option: msgcat Invocation. (line 161) +* --sort-by-file, msgcomm option: msgcomm Invocation. (line 143) +* --sort-by-file, msgconv option: msgconv Invocation. (line 123) +* --sort-by-file, msgen option: msgen Invocation. (line 126) +* --sort-by-file, msgfilter option: msgfilter Invocation. + (line 204) +* --sort-by-file, msggrep option: msggrep Invocation. (line 193) +* --sort-by-file, msgmerge option: msgmerge Invocation. (line 201) +* --sort-by-file, msguniq option: msguniq Invocation. (line 140) +* --sort-by-file, xgettext option: xgettext Invocation. (line 473) +* --sort-output, msgattrib option: msgattrib Invocation. + (line 176) +* --sort-output, msgcat option: msgcat Invocation. (line 156) +* --sort-output, msgcomm option: msgcomm Invocation. (line 138) +* --sort-output, msgconv option: msgconv Invocation. (line 118) +* --sort-output, msgen option: msgen Invocation. (line 121) +* --sort-output, msgfilter option: msgfilter Invocation. + (line 199) +* --sort-output, msggrep option: msggrep Invocation. (line 189) +* --sort-output, msgmerge option: msgmerge Invocation. (line 195) +* --sort-output, msgunfmt option: msgunfmt Invocation. (line 147) +* --sort-output, msguniq option: msguniq Invocation. (line 135) +* --sort-output, xgettext option: xgettext Invocation. (line 467) +* --source, msgfmt option: msgfmt Invocation. (line 91) +* --statistics, msgfmt option: msgfmt Invocation. (line 349) +* --strict, msgattrib option: msgattrib Invocation. + (line 147) +* --strict, msgcat option: msgcat Invocation. (line 127) +* --strict, msgcomm option: msgcomm Invocation. (line 109) +* --strict, msgconv option: msgconv Invocation. (line 89) +* --strict, msgen option: msgen Invocation. (line 92) +* --strict, msgfilter option: msgfilter Invocation. + (line 170) +* --strict, msgfmt option: msgfmt Invocation. (line 62) +* --strict, msggrep option: msggrep Invocation. (line 161) +* --strict, msgmerge option: msgmerge Invocation. (line 166) +* --strict, msgunfmt option: msgunfmt Invocation. (line 118) +* --strict, msguniq option: msguniq Invocation. (line 106) +* --strict, xgettext option: xgettext Invocation. (line 435) +* --stringtable-input, msgattrib option: msgattrib Invocation. + (line 111) +* --stringtable-input, msgcat option: msgcat Invocation. (line 78) +* --stringtable-input, msgcmp option: msgcmp Invocation. (line 61) +* --stringtable-input, msgcomm option: msgcomm Invocation. (line 73) +* --stringtable-input, msgen option: msgen Invocation. (line 50) +* --stringtable-input, msgexec option: msgexec Invocation. (line 69) +* --stringtable-input, msgfilter option: msgfilter Invocation. + (line 130) +* --stringtable-input, msgfmt option: msgfmt Invocation. (line 232) +* --stringtable-input, msggrep option: msggrep Invocation. (line 126) +* --stringtable-input, msginit option: msginit Invocation. (line 76) +* --stringtable-input, msgmerge option: msgmerge Invocation. (line 123) +* --stringtable-input, msgonv option: msgconv Invocation. (line 53) +* --stringtable-input, msguniq option: msguniq Invocation. (line 62) +* --stringtable-output, msgattrib option: msgattrib Invocation. + (line 158) +* --stringtable-output, msgcat option: msgcat Invocation. (line 138) +* --stringtable-output, msgcomm option: msgcomm Invocation. (line 120) +* --stringtable-output, msgconv option: msgconv Invocation. (line 100) +* --stringtable-output, msgen option: msgen Invocation. (line 103) +* --stringtable-output, msgfilter option: msgfilter Invocation. + (line 181) +* --stringtable-output, msggrep option: msggrep Invocation. (line 172) +* --stringtable-output, msginit option: msginit Invocation. (line 110) +* --stringtable-output, msgmerge option: msgmerge Invocation. (line 177) +* --stringtable-output, msgunfmt option: msgunfmt Invocation. (line 129) +* --stringtable-output, msguniq option: msguniq Invocation. (line 117) +* --stringtable-output, xgettext option: xgettext Invocation. (line 445) +* --style, msgattrib option: msgattrib Invocation. + (line 123) +* --style, msgcat option: msgcat Invocation. (line 103) +* --style, msgcat option <1>: The --style option. (line 6) +* --style, msgcomm option: msgcomm Invocation. (line 85) +* --style, msgconv option: msgconv Invocation. (line 65) +* --style, msgen option: msgen Invocation. (line 68) +* --style, msgfilter option: msgfilter Invocation. + (line 142) +* --style, msggrep option: msggrep Invocation. (line 138) +* --style, msginit option: msginit Invocation. (line 100) +* --style, msgmerge option: msgmerge Invocation. (line 142) +* --style, msgunfmt option: msgunfmt Invocation. (line 107) +* --style, msguniq option: msguniq Invocation. (line 82) +* --style, xgettext option: xgettext Invocation. (line 409) +* --suffix, msgmerge option: msgmerge Invocation. (line 65) +* --symlink, gettextize option: gettextize Invocation. + (line 55) +* --tag, xgettext option: xgettext Invocation. (line 333) +* --tcl, msgfmt option: msgfmt Invocation. (line 43) +* --tcl, msgunfmt option: msgunfmt Invocation. (line 26) +* --template, msgfmt option: msgfmt Invocation. (line 136) +* --template, msgfmt option <1>: msgfmt Invocation. (line 176) +* --to-code, msgcat option: msgcat Invocation. (line 86) +* --to-code, msgconv option: msgconv Invocation. (line 40) +* --to-code, msguniq option: msguniq Invocation. (line 70) +* --translated, msgattrib option: msgattrib Invocation. + (line 39) +* --trigraphs, xgettext option: xgettext Invocation. (line 347) +* --unique, msgcat option: msgcat Invocation. (line 66) +* --unique, msgcomm option: msgcomm Invocation. (line 61) +* --unique, msguniq option: msguniq Invocation. (line 51) +* --untranslated, msgattrib option: msgattrib Invocation. + (line 42) +* --update, msgmerge option: msgmerge Invocation. (line 44) +* --use-first, msgcat option: msgcat Invocation. (line 89) +* --use-first, msguniq option: msguniq Invocation. (line 73) +* --use-fuzzy, msgcmp option: msgcmp Invocation. (line 43) +* --use-fuzzy, msgfmt option: msgfmt Invocation. (line 293) +* --use-untranslated, msgcmp option: msgcmp Invocation. (line 49) +* --variables, envsubst option: envsubst Invocation. (line 15) +* --verbose, msgfmt option: msgfmt Invocation. (line 355) +* --verbose, msgmerge option: msgmerge Invocation. (line 216) +* --verbose, msgunfmt option: msgunfmt Invocation. (line 163) +* --verbose, xgettext option: xgettext Invocation. (line 602) +* --version, autopoint option: autopoint Invocation. + (line 42) +* --version, envsubst option: envsubst Invocation. (line 25) +* --version, gettext option: gettext Invocation. (line 45) +* --version, gettextize option: gettextize Invocation. + (line 72) +* --version, msgattrib option: msgattrib Invocation. + (line 192) +* --version, msgcat option: msgcat Invocation. (line 172) +* --version, msgcmp option: msgcmp Invocation. (line 73) +* --version, msgcomm option: msgcomm Invocation. (line 159) +* --version, msgconv option: msgconv Invocation. (line 134) +* --version, msgen option: msgen Invocation. (line 137) +* --version, msgexec option: msgexec Invocation. (line 81) +* --version, msgfilter option: msgfilter Invocation. + (line 215) +* --version, msgfmt option: msgfmt Invocation. (line 346) +* --version, msggrep option: msggrep Invocation. (line 204) +* --version, msginit option: msginit Invocation. (line 135) +* --version, msgmerge option: msgmerge Invocation. (line 212) +* --version, msgunfmt option: msgunfmt Invocation. (line 159) +* --version, msguniq option: msguniq Invocation. (line 151) +* --version, ngettext option: ngettext Invocation. (line 40) +* --version, xgettext option: xgettext Invocation. (line 598) +* --width, msgattrib option: msgattrib Invocation. + (line 163) +* --width, msgcat option: msgcat Invocation. (line 143) +* --width, msgcomm option: msgcomm Invocation. (line 125) +* --width, msgconv option: msgconv Invocation. (line 105) +* --width, msgen option: msgen Invocation. (line 108) +* --width, msgfilter option: msgfilter Invocation. + (line 186) +* --width, msggrep option: msggrep Invocation. (line 177) +* --width, msginit option: msginit Invocation. (line 115) +* --width, msgmerge option: msgmerge Invocation. (line 182) +* --width, msgunfmt option: msgunfmt Invocation. (line 134) +* --width, msguniq option: msguniq Invocation. (line 122) +* --width, xgettext option: xgettext Invocation. (line 454) +* --xml, msgfmt option: msgfmt Invocation. (line 52) +* -<, msgcat option: msgcat Invocation. (line 56) +* -<, msgcomm option: msgcomm Invocation. (line 51) +* ->, msgcat option: msgcat Invocation. (line 61) +* ->, msgcomm option: msgcomm Invocation. (line 56) +* -a, msgfmt option: msgfmt Invocation. (line 319) +* -a, xgettext option: xgettext Invocation. (line 177) +* -c, gettext option: gettext Invocation. (line 16) +* -c, msgfmt option: msgfmt Invocation. (line 240) +* -C, msgfmt option: msgfmt Invocation. (line 277) +* -C, msggrep option: msggrep Invocation. (line 86) +* -C, msgmerge option: msgmerge Invocation. (line 36) +* -c, ngettext option: ngettext Invocation. (line 15) +* -C, xgettext option: xgettext Invocation. (line 67) +* -c, xgettext option: xgettext Invocation. (line 98) +* -d, autopoint option: autopoint Invocation. + (line 31) +* -d, gettext option: gettext Invocation. (line 21) +* -d, gettextize option: gettextize Invocation. + (line 64) +* -D, msgattrib option: msgattrib Invocation. + (line 19) +* -D, msgcat option: msgcat Invocation. (line 35) +* -D, msgcmp option: msgcmp Invocation. (line 27) +* -D, msgcomm option: msgcomm Invocation. (line 30) +* -D, msgconv option: msgconv Invocation. (line 19) +* -D, msgen option: msgen Invocation. (line 25) +* -D, msgexec option: msgexec Invocation. (line 54) +* -D, msgfilter option: msgfilter Invocation. + (line 34) +* -D, msgfmt option: msgfmt Invocation. (line 18) +* -d, msgfmt option: msgfmt Invocation. (line 88) +* -d, msgfmt option <1>: msgfmt Invocation. (line 111) +* -d, msgfmt option <2>: msgfmt Invocation. (line 127) +* -d, msgfmt option <3>: msgfmt Invocation. (line 151) +* -d, msgfmt option <4>: msgfmt Invocation. (line 189) +* -D, msggrep option: msggrep Invocation. (line 19) +* -D, msgmerge option: msgmerge Invocation. (line 30) +* -d, msgunfmt option: msgunfmt Invocation. (line 67) +* -d, msgunfmt option <1>: msgunfmt Invocation. (line 83) +* -D, msguniq option: msguniq Invocation. (line 26) +* -d, msguniq option: msguniq Invocation. (line 47) +* -d, ngettext option: ngettext Invocation. (line 20) +* -D, xgettext option: xgettext Invocation. (line 27) +* -d, xgettext option: xgettext Invocation. (line 38) +* -e, gettext option: gettext Invocation. (line 25) +* -E, gettext option: gettext Invocation. (line 32) +* -e, msgfilter option: msgfilter Invocation. + (line 87) +* -E, msggrep option: msggrep Invocation. (line 94) +* -e, msggrep option: msggrep Invocation. (line 102) +* -e, ngettext option: ngettext Invocation. (line 24) +* -E, ngettext option: ngettext Invocation. (line 31) +* -f, autopoint option: autopoint Invocation. + (line 27) +* -f, gettextize option: gettextize Invocation. + (line 40) +* -F, msgattrib option: msgattrib Invocation. + (line 181) +* -f, msgcat option: msgcat Invocation. (line 30) +* -F, msgcat option: msgcat Invocation. (line 161) +* -f, msgcomm option: msgcomm Invocation. (line 25) +* -F, msgcomm option: msgcomm Invocation. (line 143) +* -F, msgconv option: msgconv Invocation. (line 123) +* -F, msgen option: msgen Invocation. (line 126) +* -f, msgfilter option: msgfilter Invocation. + (line 91) +* -F, msgfilter option: msgfilter Invocation. + (line 204) +* -f, msgfmt option: msgfmt Invocation. (line 293) +* -F, msggrep option: msggrep Invocation. (line 98) +* -f, msggrep option: msggrep Invocation. (line 106) +* -F, msgmerge option: msgmerge Invocation. (line 201) +* -F, msguniq option: msguniq Invocation. (line 140) +* -f, xgettext option: xgettext Invocation. (line 19) +* -F, xgettext option: xgettext Invocation. (line 473) +* -h, envsubst option: envsubst Invocation. (line 21) +* -h, gettext option: gettext Invocation. (line 37) +* -h, msgattrib option: msgattrib Invocation. + (line 188) +* -h, msgcat option: msgcat Invocation. (line 168) +* -h, msgcmp option: msgcmp Invocation. (line 69) +* -h, msgcomm option: msgcomm Invocation. (line 155) +* -h, msgconv option: msgconv Invocation. (line 130) +* -h, msgen option: msgen Invocation. (line 133) +* -h, msgexec option: msgexec Invocation. (line 77) +* -h, msgfilter option: msgfilter Invocation. + (line 211) +* -h, msgfmt option: msgfmt Invocation. (line 342) +* -h, msggrep option: msggrep Invocation. (line 200) +* -h, msginit option: msginit Invocation. (line 131) +* -h, msgmerge option: msgmerge Invocation. (line 208) +* -h, msgunfmt option: msgunfmt Invocation. (line 155) +* -h, msguniq option: msguniq Invocation. (line 147) +* -h, ngettext option: ngettext Invocation. (line 36) +* -h, xgettext option: xgettext Invocation. (line 594) +* -i, msgattrib option: msgattrib Invocation. + (line 131) +* -i, msgcat option: msgcat Invocation. (line 111) +* -i, msgcomm option: msgcomm Invocation. (line 93) +* -i, msgconv option: msgconv Invocation. (line 73) +* -i, msgen option: msgen Invocation. (line 76) +* -i, msgexec option: msgexec Invocation. (line 50) +* -i, msgfilter option: msgfilter Invocation. + (line 30) +* -i, msggrep option: msggrep Invocation. (line 110) +* -i, msginit option: msginit Invocation. (line 51) +* -i, msgmerge option: msgmerge Invocation. (line 150) +* -i, msgunfmt option: msgunfmt Invocation. (line 115) +* -i, msguniq option: msguniq Invocation. (line 90) +* -i, xgettext option: xgettext Invocation. (line 417) +* -j, msgfmt option: msgfmt Invocation. (line 30) +* -J, msggrep option: msggrep Invocation. (line 74) +* -j, msgunfmt option: msgunfmt Invocation. (line 16) +* -j, xgettext option: xgettext Invocation. (line 89) +* -k, msgfmt option: msgfmt Invocation. (line 140) +* -K, msggrep option: msggrep Invocation. (line 78) +* -k, xgettext option: xgettext Invocation. (line 186) +* -l, msgfmt option: msgfmt Invocation. (line 83) +* -l, msgfmt option <1>: msgfmt Invocation. (line 106) +* -l, msgfmt option <2>: msgfmt Invocation. (line 122) +* -l, msgfmt option <3>: msgfmt Invocation. (line 146) +* -L, msgfmt option: msgfmt Invocation. (line 180) +* -l, msgfmt option <4>: msgfmt Invocation. (line 184) +* -l, msginit option: msginit Invocation. (line 84) +* -l, msgunfmt option: msgunfmt Invocation. (line 45) +* -l, msgunfmt option <1>: msgunfmt Invocation. (line 62) +* -l, msgunfmt option <2>: msgunfmt Invocation. (line 78) +* -L, xgettext option: xgettext Invocation. (line 57) +* -m, msgcmp option: msgcmp Invocation. (line 35) +* -M, msggrep option: msggrep Invocation. (line 70) +* -m, msgmerge option: msgmerge Invocation. (line 96) +* -m, xgettext option: xgettext Invocation. (line 583) +* -M, xgettext option: xgettext Invocation. (line 587) +* -n, gettext option: gettext Invocation. (line 40) +* -n, msgattrib option: msgattrib Invocation. + (line 138) +* -n, msgcat option: msgcat Invocation. (line 118) +* -N, msgcmp option: msgcmp Invocation. (line 39) +* -n, msgcomm option: msgcomm Invocation. (line 100) +* -n, msgfilter option: msgfilter Invocation. + (line 96) +* -N, msggrep option: msggrep Invocation. (line 65) +* -N, msgmerge option: msgmerge Invocation. (line 107) +* -n, msguniq option: msguniq Invocation. (line 97) +* -n, xgettext option: xgettext Invocation. (line 426) +* -o, msgattrib option: msgattrib Invocation. + (line 30) +* -o, msgcat option: msgcat Invocation. (line 46) +* -o, msgcomm option: msgcomm Invocation. (line 41) +* -o, msgconv option: msgconv Invocation. (line 30) +* -o, msgen option: msgen Invocation. (line 36) +* -o, msgfilter option: msgfilter Invocation. + (line 45) +* -o, msgfmt option: msgfmt Invocation. (line 59) +* -o, msggrep option: msggrep Invocation. (line 30) +* -o, msginit option: msginit Invocation. (line 61) +* -o, msgmerge option: msgmerge Invocation. (line 51) +* -o, msgunfmt option: msgunfmt Invocation. (line 93) +* -o, msguniq option: msguniq Invocation. (line 37) +* -o, xgettext option: xgettext Invocation. (line 42) +* -P, msgattrib option: msgattrib Invocation. + (line 107) +* -p, msgattrib option: msgattrib Invocation. + (line 153) +* -P, msgcat option: msgcat Invocation. (line 74) +* -p, msgcat option: msgcat Invocation. (line 133) +* -P, msgcmp option: msgcmp Invocation. (line 57) +* -P, msgcomm option: msgcomm Invocation. (line 69) +* -p, msgcomm option: msgcomm Invocation. (line 115) +* -P, msgconv option: msgconv Invocation. (line 49) +* -p, msgconv option: msgconv Invocation. (line 95) +* -P, msgen option: msgen Invocation. (line 46) +* -p, msgen option: msgen Invocation. (line 98) +* -P, msgexec option: msgexec Invocation. (line 65) +* -P, msgfilter option: msgfilter Invocation. + (line 126) +* -p, msgfilter option: msgfilter Invocation. + (line 176) +* -P, msgfmt option: msgfmt Invocation. (line 228) +* -P, msggrep option: msggrep Invocation. (line 122) +* -p, msggrep option: msggrep Invocation. (line 167) +* -P, msginit option: msginit Invocation. (line 72) +* -p, msginit option: msginit Invocation. (line 105) +* -P, msgmerge option: msgmerge Invocation. (line 119) +* -p, msgmerge option: msgmerge Invocation. (line 172) +* -p, msgunfmt option: msgunfmt Invocation. (line 124) +* -P, msguniq option: msguniq Invocation. (line 58) +* -p, msguniq option: msguniq Invocation. (line 112) +* -p, xgettext option: xgettext Invocation. (line 47) +* -q, msgmerge option: msgmerge Invocation. (line 221) +* -r, msgfmt option: msgfmt Invocation. (line 79) +* -r, msgfmt option <1>: msgfmt Invocation. (line 102) +* -r, msgunfmt option: msgunfmt Invocation. (line 41) +* -r, msgunfmt option <1>: msgunfmt Invocation. (line 58) +* -s, msgattrib option: msgattrib Invocation. + (line 176) +* -s, msgcat option: msgcat Invocation. (line 156) +* -s, msgcomm option: msgcomm Invocation. (line 138) +* -s, msgconv option: msgconv Invocation. (line 118) +* -s, msgen option: msgen Invocation. (line 121) +* -s, msgfilter option: msgfilter Invocation. + (line 199) +* -s, msgmerge option: msgmerge Invocation. (line 195) +* -s, msgunfmt option: msgunfmt Invocation. (line 147) +* -s, msguniq option: msguniq Invocation. (line 135) +* -s, xgettext option: xgettext Invocation. (line 467) +* -t, msgcat option: msgcat Invocation. (line 86) +* -t, msgconv option: msgconv Invocation. (line 40) +* -T, msggrep option: msggrep Invocation. (line 82) +* -t, msguniq option: msguniq Invocation. (line 70) +* -T, xgettext option: xgettext Invocation. (line 347) +* -u, msgcat option: msgcat Invocation. (line 66) +* -u, msgcomm option: msgcomm Invocation. (line 61) +* -U, msgmerge option: msgmerge Invocation. (line 44) +* -u, msguniq option: msguniq Invocation. (line 51) +* -v, envsubst option: envsubst Invocation. (line 15) +* -V, envsubst option: envsubst Invocation. (line 25) +* -V, gettext option: gettext Invocation. (line 45) +* -V, msgattrib option: msgattrib Invocation. + (line 192) +* -V, msgcat option: msgcat Invocation. (line 172) +* -V, msgcmp option: msgcmp Invocation. (line 73) +* -V, msgcomm option: msgcomm Invocation. (line 159) +* -V, msgconv option: msgconv Invocation. (line 134) +* -V, msgen option: msgen Invocation. (line 137) +* -V, msgexec option: msgexec Invocation. (line 81) +* -V, msgfilter option: msgfilter Invocation. + (line 215) +* -V, msgfmt option: msgfmt Invocation. (line 346) +* -v, msgfmt option: msgfmt Invocation. (line 355) +* -v, msggrep option: msggrep Invocation. (line 114) +* -V, msggrep option: msggrep Invocation. (line 204) +* -V, msginit option: msginit Invocation. (line 135) +* -V, msgmerge option: msgmerge Invocation. (line 212) +* -v, msgmerge option: msgmerge Invocation. (line 216) +* -V, msgunfmt option: msgunfmt Invocation. (line 159) +* -v, msgunfmt option: msgunfmt Invocation. (line 163) +* -V, msguniq option: msguniq Invocation. (line 151) +* -V, ngettext option: ngettext Invocation. (line 40) +* -V, xgettext option: xgettext Invocation. (line 598) +* -v, xgettext option: xgettext Invocation. (line 602) +* -w, msgattrib option: msgattrib Invocation. + (line 163) +* -w, msgcat option: msgcat Invocation. (line 143) +* -w, msgcomm option: msgcomm Invocation. (line 125) +* -w, msgconv option: msgconv Invocation. (line 105) +* -w, msgen option: msgen Invocation. (line 108) +* -w, msgfilter option: msgfilter Invocation. + (line 186) +* -w, msggrep option: msggrep Invocation. (line 177) +* -w, msginit option: msginit Invocation. (line 115) +* -w, msgmerge option: msgmerge Invocation. (line 182) +* -w, msgunfmt option: msgunfmt Invocation. (line 134) +* -w, msguniq option: msguniq Invocation. (line 122) +* -w, xgettext option: xgettext Invocation. (line 454) +* -X, msggrep option: msggrep Invocation. (line 90) +* -x, xgettext option: xgettext Invocation. (line 93) + + +File: gettext.info, Node: Variable Index, Next: PO Mode Index, Prev: Option Index, Up: Top + +Variable Index +************** + +[index] +* Menu: + +* GETTEXT_LOG_UNTRANSLATED, environment variable: Prioritizing messages. + (line 22) +* GETTEXTDATADIRS, environment variable: xgettext Invocation. (line 391) +* GETTEXTDATADIRS, environment variable <1>: msgfmt Invocation. + (line 218) +* LANG, environment variable: Locale Environment Variables. + (line 15) +* LANG, environment variable <1>: gettext grok. (line 30) +* LANGUAGE, environment variable: Locale Environment Variables. + (line 11) +* LANGUAGE, environment variable <1>: gettext grok. (line 28) +* LANGUAGE, environment variable <2>: po/Rules-*. (line 11) +* LC_ALL, environment variable: Locale Environment Variables. + (line 11) +* LC_ALL, environment variable <1>: gettext grok. (line 28) +* LC_COLLATE, environment variable: Locale Environment Variables. + (line 12) +* LC_COLLATE, environment variable <1>: gettext grok. (line 29) +* LC_CTYPE, environment variable: Locale Environment Variables. + (line 12) +* LC_CTYPE, environment variable <1>: gettext grok. (line 29) +* LC_MESSAGES, environment variable: Locale Environment Variables. + (line 12) +* LC_MESSAGES, environment variable <1>: gettext grok. (line 29) +* LC_MONETARY, environment variable: Locale Environment Variables. + (line 12) +* LC_MONETARY, environment variable <1>: gettext grok. (line 29) +* LC_NUMERIC, environment variable: Locale Environment Variables. + (line 12) +* LC_NUMERIC, environment variable <1>: gettext grok. (line 29) +* LC_TIME, environment variable: Locale Environment Variables. + (line 12) +* LC_TIME, environment variable <1>: gettext grok. (line 29) +* LINGUAS, environment variable: Installers. (line 17) +* MSGEXEC_LOCATION, environment variable: msgexec Invocation. (line 21) +* MSGEXEC_MSGCTXT, environment variable: msgexec Invocation. (line 21) +* MSGEXEC_MSGID_PLURAL, environment variable: msgexec Invocation. + (line 21) +* MSGEXEC_MSGID, environment variable: msgexec Invocation. (line 21) +* MSGEXEC_PLURAL_FORM, environment variable: msgexec Invocation. + (line 21) +* MSGEXEC_PREV_MSGCTXT, environment variable: msgexec Invocation. + (line 21) +* MSGEXEC_PREV_MSGID_PLURAL, environment variable: msgexec Invocation. + (line 21) +* MSGEXEC_PREV_MSGID, environment variable: msgexec Invocation. + (line 21) +* MSGFILTER_LOCATION, environment variable: msgfilter Invocation. + (line 11) +* MSGFILTER_MSGCTXT, environment variable: msgfilter Invocation. + (line 11) +* MSGFILTER_MSGID_PLURAL, environment variable: msgfilter Invocation. + (line 11) +* MSGFILTER_MSGID, environment variable: msgfilter Invocation. + (line 11) +* MSGFILTER_PLURAL_FORM, environment variable: msgfilter Invocation. + (line 11) +* MSGFILTER_PREV_MSGCTXT, environment variable: msgfilter Invocation. + (line 11) +* MSGFILTER_PREV_MSGID_PLURAL, environment variable: msgfilter Invocation. + (line 11) +* MSGFILTER_PREV_MSGID, environment variable: msgfilter Invocation. + (line 11) +* OUTPUT_CHARSET, environment variable: Working in a Windows console. + (line 6) +* PO_STYLE, environment variable: The --style option. (line 10) +* TERM, environment variable: The TERM variable. (line 6) +* TEXTDOMAIN, environment variable: sh. (line 27) +* TEXTDOMAINDIR, environment variable: sh. (line 30) + + +File: gettext.info, Node: PO Mode Index, Next: Autoconf Macro Index, Prev: Variable Index, Up: Top + +PO Mode Index +************* + +[index] +* Menu: + +* _, PO Mode command: Main PO Commands. (line 30) +* _, PO Mode command <1>: Main PO Commands. (line 52) +* ,, PO Mode command: Marking. (line 43) +* ?, PO Mode command: Main PO Commands. (line 44) +* ?, PO Mode command <1>: Main PO Commands. (line 82) +* ., PO Mode command: Entry Positioning. (line 20) +* ., PO Mode command <1>: Entry Positioning. (line 45) +* .emacs customizations: Installation. (line 13) +* #, PO Mode command: Modifying Comments. (line 24) +* #, PO Mode command <1>: Modifying Comments. (line 45) +* <, PO Mode command: Entry Positioning. (line 29) +* <, PO Mode command <1>: Entry Positioning. (line 73) +* =, PO Mode command: Main PO Commands. (line 47) +* =, PO Mode command <1>: Main PO Commands. (line 86) +* >, PO Mode command: Entry Positioning. (line 32) +* >, PO Mode command <1>: Entry Positioning. (line 73) +* 0, PO Mode command: Main PO Commands. (line 40) +* 0, PO Mode command <1>: Main PO Commands. (line 71) +* a, PO Mode command: Auxiliary. (line 21) +* A, PO Mode command: Auxiliary. (line 28) +* A, PO Mode command <1>: Auxiliary. (line 35) +* a, PO Mode command <1>: Auxiliary. (line 39) +* auxiliary PO file: Auxiliary. (line 13) +* C-c C-a, PO Mode command: Subedit. (line 17) +* C-c C-a, PO Mode command <1>: Subedit. (line 34) +* C-c C-a, PO Mode command <2>: Auxiliary. (line 25) +* C-c C-a, PO Mode command <3>: Auxiliary. (line 48) +* C-c C-c, PO Mode command: Subedit. (line 11) +* C-c C-c, PO Mode command <1>: Subedit. (line 19) +* C-c C-k, PO Mode command: Subedit. (line 14) +* C-c C-k, PO Mode command <1>: Subedit. (line 26) +* C-j, PO Mode command: Modifying Translations. + (line 26) +* C-j, PO Mode command <1>: Modifying Translations. + (line 51) +* commands: Main PO Commands. (line 6) +* comment out PO file entry: Obsolete Entries. (line 46) +* consulting program sources: C Sources Context. (line 6) +* consulting translations to other languages: Auxiliary. (line 6) +* current entry of a PO file: Entry Positioning. (line 6) +* cut and paste for translated strings: Modifying Translations. + (line 73) +* DEL, PO Mode command: Fuzzy Entries. (line 58) +* DEL, PO Mode command <1>: Obsolete Entries. (line 32) +* DEL, PO Mode command <2>: Obsolete Entries. (line 46) +* editing comments: Modifying Comments. (line 6) +* editing multiple entries: Subedit. (line 61) +* editing translations: Modifying Translations. + (line 6) +* etags, using for marking strings: Marking. (line 17) +* exiting PO subedit: Subedit. (line 19) +* f, PO Mode command: Fuzzy Entries. (line 29) +* F, PO Mode command: Fuzzy Entries. (line 32) +* f, PO Mode command <1>: Fuzzy Entries. (line 37) +* F, PO Mode command <1>: Fuzzy Entries. (line 37) +* find source fragment for a PO file entry: C Sources Context. + (line 33) +* h, PO Mode command: Main PO Commands. (line 44) +* h, PO Mode command <1>: Main PO Commands. (line 82) +* installing PO mode: Installation. (line 13) +* k, PO Mode command: Untranslated Entries. + (line 32) +* k, PO Mode command <1>: Untranslated Entries. + (line 39) +* k, PO Mode command <2>: Modifying Translations. + (line 30) +* k, PO Mode command <3>: Modifying Translations. + (line 73) +* K, PO Mode command: Modifying Comments. (line 27) +* K, PO Mode command <1>: Modifying Comments. (line 59) +* LFD, PO Mode command: Modifying Translations. + (line 26) +* LFD, PO Mode command <1>: Modifying Translations. + (line 51) +* looking at the source to aid translation: C Sources Context. + (line 6) +* M-,, PO Mode command: Marking. (line 47) +* M-., PO Mode command: Marking. (line 50) +* M-A, PO Mode command: Auxiliary. (line 32) +* M-A, PO Mode command <1>: Auxiliary. (line 35) +* M-s, PO Mode command: C Sources Context. (line 41) +* M-S, PO Mode command: C Sources Context. (line 49) +* M-s, PO Mode command <1>: C Sources Context. (line 52) +* M-S, PO Mode command <1>: C Sources Context. (line 88) +* m, PO Mode command: Entry Positioning. (line 35) +* m, PO Mode command <1>: Entry Positioning. (line 91) +* marking strings for translation: Marking. (line 6) +* moving by fuzzy entries: Fuzzy Entries. (line 23) +* moving by obsolete entries: Obsolete Entries. (line 22) +* moving by translated entries: Translated Entries. (line 12) +* moving by untranslated entries: Untranslated Entries. + (line 18) +* moving through a PO file: Entry Positioning. (line 14) +* n, PO Mode command: Entry Positioning. (line 23) +* n, PO Mode command <1>: Entry Positioning. (line 68) +* next-error, stepping through PO file validation results: Main PO Commands. + (line 98) +* normalize, PO Mode command: Auxiliary. (line 63) +* o, PO Mode command: Obsolete Entries. (line 26) +* O, PO Mode command: Obsolete Entries. (line 29) +* o, PO Mode command <1>: Obsolete Entries. (line 35) +* O, PO Mode command <1>: Obsolete Entries. (line 35) +* obsolete active entry: Obsolete Entries. (line 46) +* p, PO Mode command: Entry Positioning. (line 26) +* p, PO Mode command <1>: Entry Positioning. (line 68) +* pending subedits: Subedit. (line 72) +* po-auto-edit-with-msgid, PO Mode variable: Modifying Translations. + (line 56) +* po-auto-fuzzy-on-edit, PO Mode variable: Translated Entries. + (line 27) +* po-auto-select-on-unfuzzy, PO Mode variable: Fuzzy Entries. (line 42) +* po-confirm-and-quit, PO Mode command: Main PO Commands. (line 61) +* po-consider-as-auxiliary, PO Mode command: Auxiliary. (line 35) +* po-consider-source-path, PO Mode command: C Sources Context. + (line 88) +* po-current-entry, PO Mode command: Entry Positioning. (line 45) +* po-cycle-auxiliary, PO Mode command: Auxiliary. (line 39) +* po-cycle-source-reference, PO Mode command: C Sources Context. + (line 52) +* po-edit-comment, PO Mode command: Modifying Comments. (line 45) +* po-edit-msgstr, PO Mode command: Modifying Translations. + (line 41) +* po-exchange-location, PO Mode command: Entry Positioning. (line 105) +* po-fade-out-entry, PO Mode command: Fuzzy Entries. (line 58) +* po-fade-out-entry, PO Mode command <1>: Obsolete Entries. (line 46) +* po-first-entry, PO Mode command: Entry Positioning. (line 73) +* po-help, PO Mode command: Main PO Commands. (line 82) +* po-ignore-as-auxiliary, PO Mode command: Auxiliary. (line 35) +* po-ignore-source-path, PO Mode command: C Sources Context. (line 88) +* po-kill-comment, PO Mode command: Modifying Comments. (line 59) +* po-kill-msgstr, PO Mode command: Untranslated Entries. + (line 39) +* po-kill-msgstr, PO Mode command <1>: Modifying Translations. + (line 73) +* po-kill-ring-save-comment, PO Mode command: Modifying Comments. + (line 59) +* po-kill-ring-save-msgstr, PO Mode command: Modifying Translations. + (line 73) +* po-last-entry, PO Mode command: Entry Positioning. (line 73) +* po-mark-translatable, PO Mode command: Marking. (line 96) +* po-msgid-to-msgstr, PO Mode command: Modifying Translations. + (line 51) +* po-next-entry, PO Mode command: Entry Positioning. (line 68) +* po-next-fuzzy-entry, PO Mode command: Fuzzy Entries. (line 37) +* po-next-obsolete-entry, PO Mode command: Obsolete Entries. (line 35) +* po-next-translated-entry, PO Mode command: Translated Entries. + (line 22) +* po-next-untranslated-entry, PO Mode command: Untranslated Entries. + (line 34) +* po-normalize, PO Mode command: Normalizing. (line 31) +* po-other-window, PO Mode command: Main PO Commands. (line 71) +* po-pop-location, PO Mode command: Entry Positioning. (line 91) +* po-previous-entry, PO Mode command: Entry Positioning. (line 68) +* po-previous-fuzzy-entry, PO Mode command: Fuzzy Entries. (line 37) +* po-previous-obsolete-entry, PO Mode command: Obsolete Entries. + (line 35) +* po-previous-translated-entry, PO Mode command: Translated Entries. + (line 22) +* po-previous-untransted-entry, PO Mode command: Untranslated Entries. + (line 34) +* po-push-location, PO Mode command: Entry Positioning. (line 91) +* po-quit, PO Mode command: Main PO Commands. (line 61) +* po-select-auxiliary, PO Mode command: Auxiliary. (line 48) +* po-select-mark-and-mark, PO Mode command: Marking. (line 96) +* po-select-source-reference, PO Mode command: C Sources Context. + (line 52) +* po-statistics, PO Mode command: Main PO Commands. (line 86) +* po-subedit-abort, PO Mode command: Subedit. (line 26) +* po-subedit-cycle-auxiliary, PO Mode command: Subedit. (line 34) +* po-subedit-exit, PO Mode command: Subedit. (line 19) +* po-subedit-mode-hook, PO Mode variable: Modifying Comments. (line 56) +* po-tags-search, PO Mode command: Marking. (line 54) +* po-undo, PO Mode command: Main PO Commands. (line 52) +* po-unfuzzy, PO Mode command: Fuzzy Entries. (line 42) +* po-validate, PO Mode command: Main PO Commands. (line 91) +* po-yank-comment, PO Mode command: Modifying Comments. (line 59) +* po-yank-msgstr, PO Mode command: Modifying Translations. + (line 96) +* Q, PO Mode command: Main PO Commands. (line 33) +* q, PO Mode command: Main PO Commands. (line 36) +* Q, PO Mode command <1>: Main PO Commands. (line 61) +* q, PO Mode command <1>: Main PO Commands. (line 61) +* r, PO Mode command: Entry Positioning. (line 39) +* r, PO Mode command <1>: Entry Positioning. (line 91) +* RET, PO Mode command: Modifying Translations. + (line 22) +* RET, PO Mode command <1>: Modifying Translations. + (line 41) +* s, PO Mode command: C Sources Context. (line 37) +* S, PO Mode command: C Sources Context. (line 45) +* s, PO Mode command <1>: C Sources Context. (line 52) +* S, PO Mode command <1>: C Sources Context. (line 88) +* starting a string translation: Modifying Translations. + (line 62) +* string normalization in entries: Normalizing. (line 30) +* subedit minor mode: Subedit. (line 6) +* t, PO Mode command: Translated Entries. (line 16) +* T, PO Mode command: Translated Entries. (line 19) +* t, PO Mode command <1>: Translated Entries. (line 22) +* T, PO Mode command <1>: Translated Entries. (line 22) +* TAB, PO Mode command: Fuzzy Entries. (line 35) +* TAB, PO Mode command <1>: Fuzzy Entries. (line 42) +* TAGS, and marking translatable strings: Marking. (line 30) +* u, PO Mode command: Untranslated Entries. + (line 25) +* U, PO Mode command: Untranslated Entries. + (line 28) +* u, PO Mode command <1>: Untranslated Entries. + (line 34) +* U, PO Mode command <1>: Untranslated Entries. + (line 34) +* use the source, Luke: C Sources Context. (line 6) +* using obsolete translations to make new entries: Modifying Translations. + (line 122) +* using translation compendia: Compendium. (line 6) +* V, PO Mode command: Main PO Commands. (line 50) +* V, PO Mode command <1>: Main PO Commands. (line 91) +* w, PO Mode command: Modifying Translations. + (line 34) +* w, PO Mode command <1>: Modifying Translations. + (line 73) +* W, PO Mode command: Modifying Comments. (line 31) +* W, PO Mode command <1>: Modifying Comments. (line 59) +* x, PO Mode command: Entry Positioning. (line 42) +* x, PO Mode command <1>: Entry Positioning. (line 105) +* y, PO Mode command: Modifying Translations. + (line 38) +* y, PO Mode command <1>: Modifying Translations. + (line 96) +* Y, PO Mode command: Modifying Comments. (line 35) +* Y, PO Mode command <1>: Modifying Comments. (line 59) + + +File: gettext.info, Node: Autoconf Macro Index, Next: Index, Prev: PO Mode Index, Up: Top + +Autoconf Macro Index +******************** + +[index] +* Menu: + +* AM_GNU_GETTEXT: AM_GNU_GETTEXT. (line 6) +* AM_GNU_GETTEXT_NEED: AM_GNU_GETTEXT_NEED. (line 6) +* AM_GNU_GETTEXT_VERSION: AM_GNU_GETTEXT_VERSION. + (line 6) +* AM_ICONV: AM_ICONV. (line 6) +* AM_PO_SUBDIRS: AM_PO_SUBDIRS. (line 6) +* AM_XGETTEXT_OPTION: AM_XGETTEXT_OPTION. (line 6) + + +File: gettext.info, Node: Index, Prev: Autoconf Macro Index, Up: Top + +General Index +************* + +[index] +* Menu: + +* _, a macro to mark strings for translation: Mark Keywords. (line 45) +* _nl_msg_cat_cntr: gettext grok. (line 59) +* ABOUT-NLS file: Installing Localizations. + (line 13) +* ABOUT-NLS file <1>: The original ABOUT-NLS. + (line 6) +* accumulating translations: Creating Compendia. (line 14) +* aclocal.m4 file: aclocal. (line 6) +* adding keywords, xgettext: xgettext Invocation. (line 190) +* ambiguities: Decent English style. + (line 23) +* ANSI encoding: Working in a Windows console. + (line 6) +* apply a filter to translations: msgfilter Invocation. + (line 8) +* apply command to all translations in a catalog: msgexec Invocation. + (line 8) +* Arabic digits: c-format. (line 34) +* attribute manipulation: msgattrib Invocation. + (line 8) +* attribute, fuzzy: Fuzzy Entries. (line 6) +* attributes of a PO file entry: Fuzzy Entries. (line 6) +* attributes, manipulating: Manipulating. (line 56) +* autoconf macros for gettext: autoconf macros. (line 6) +* autopoint program, usage: autopoint Invocation. + (line 6) +* auxiliary PO file: Auxiliary. (line 13) +* available translations: Installing Localizations. + (line 6) +* awk: gawk. (line 6) +* awk-format flag: PO Files. (line 177) +* awk, string concatenation: No string concatenation. + (line 29) +* backup old file, and msgmerge program: msgmerge Invocation. (line 62) +* bash: bash. (line 6) +* bibliography: References. (line 6) +* big picture: Overview. (line 6) +* bind_textdomain_codeset: Charset conversion. (line 26) +* Boost format strings: xgettext Invocation. (line 361) +* boost-format flag: PO Files. (line 213) +* bug report address: Introduction. (line 24) +* C and C-like languages: C. (line 6) +* C trigraphs: xgettext Invocation. (line 347) +* c-format flag: PO Files. (line 93) +* c-format, and xgettext: c-format Flag. (line 47) +* C#: C#. (line 6) +* C# mode, and msgfmt program: msgfmt Invocation. (line 36) +* C# mode, and msgunfmt program: msgunfmt Invocation. (line 19) +* C# resources mode, and msgfmt program: msgfmt Invocation. (line 40) +* C# resources mode, and msgunfmt program: msgunfmt Invocation. + (line 23) +* C#, string concatenation: No string concatenation. + (line 29) +* C#, strings with embedded expressions: No string concatenation. + (line 78) +* c++-format flag: PO Files. (line 116) +* catalog encoding and msgexec output: msgexec Invocation. (line 35) +* catclose, a catgets function: Interface to catgets. + (line 44) +* catgets, a catgets function: Interface to catgets. + (line 25) +* catgets, X/Open specification: catgets. (line 6) +* catopen, a catgets function: Interface to catgets. + (line 13) +* character encoding: Aspects. (line 66) +* charset conversion at runtime: Charset conversion. (line 6) +* charset of PO files: Header Entry. (line 103) +* check format strings: msgfmt Invocation. (line 244) +* checking of translations: Manipulating. (line 41) +* clisp: Common Lisp. (line 6) +* clisp C sources: clisp C. (line 6) +* codeset: Aspects. (line 66) +* combining two PO files: Manipulating. (line 10) +* combining two POT files: Combining POTs. (line 12) +* comments in PO files: PO Files. (line 355) +* comments, automatic: PO Files. (line 36) +* comments, extracted: PO Files. (line 36) +* comments, translator: PO Files. (line 36) +* Common Lisp: Common Lisp. (line 6) +* compare PO files: msgcmp Invocation. (line 8) +* comparison of interfaces: Comparison. (line 6) +* compatibility with X/Open msgfmt: msgfmt Invocation. (line 277) +* compendium: Compendium. (line 6) +* compendium, creating: Creating Compendia. (line 6) +* concatenate PO files: msgcat Invocation. (line 8) +* concatenating PO files into a compendium: Creating Compendia. + (line 14) +* concatenation of strings: No string concatenation. + (line 6) +* config.h.in file: config.h.in. (line 6) +* context: Contexts. (line 6) +* context, argument specification in xgettext: xgettext Invocation. + (line 190) +* context, in MO files: MO Files. (line 71) +* context, in PO files: PO Files. (line 245) +* control characters: No unusual markup. (line 6) +* convert binary message catalog into PO file: msgunfmt Invocation. + (line 8) +* convert translations to a different encoding: msgconv Invocation. + (line 8) +* converting a package to use gettext: Prerequisites. (line 6) +* country codes: Country Codes. (line 6) +* create new PO file: msginit Invocation. (line 8) +* creating a new PO file: Creating. (line 6) +* creating compendia: Creating Compendia. (line 6) +* csharp-format flag: PO Files. (line 137) +* currency symbols: Aspects. (line 79) +* D: D. (line 6) +* d-format flag: PO Files. (line 193) +* D, string concatenation: No string concatenation. + (line 29) +* D, strings with embedded expressions: No string concatenation. + (line 78) +* date format: Aspects. (line 85) +* dcngettext: Plural forms. (line 169) +* dcpgettext: Contexts. (line 56) +* dcpgettext_expr: Contexts. (line 112) +* debugging messages marked as format strings: xgettext Invocation. + (line 365) +* Desktop Entry mode, and msgfmt program: msgfmt Invocation. (line 49) +* dialect: Manipulating. (line 28) +* disabling NLS: lib/gettext.h. (line 6) +* distribution tarball: Release Management. (line 6) +* dngettext: Plural forms. (line 162) +* dollar substitution: envsubst Invocation. (line 8) +* domain ambiguities: Ambiguities. (line 6) +* dpgettext: Contexts. (line 56) +* dpgettext_expr: Contexts. (line 112) +* duplicate elimination: Manipulating. (line 45) +* duplicate removal: msguniq Invocation. (line 8) +* editing comments in PO files: Modifying Comments. (line 6) +* Editing PO Files: Editing. (line 6) +* editing translations: Modifying Translations. + (line 6) +* elisp-format flag: PO Files. (line 153) +* Emacs Lisp: Emacs Lisp. (line 6) +* Emacs PO Mode: PO Mode. (line 6) +* encoding: Aspects. (line 66) +* encoding conversion: Manipulating. (line 17) +* encoding conversion at runtime: Charset conversion. (line 6) +* encoding for your language: Header Entry. (line 132) +* encoding in MO files: MO Files. (line 82) +* encoding list: Header Entry. (line 116) +* encoding of PO files: Header Entry. (line 103) +* environment variables: envsubst Invocation. (line 8) +* envsubst program, usage: envsubst Invocation. (line 6) +* eval_gettext function, usage: eval_gettext Invocation. + (line 6) +* eval_ngettext function, usage: eval_ngettext Invocation. + (line 6) +* eval_npgettext function, usage: eval_npgettext Invocation. + (line 6) +* eval_pgettext function, usage: eval_pgettext Invocation. + (line 6) +* evolution of packages: Overview. (line 127) +* extracting parts of a PO file into a compendium: Creating Compendia. + (line 64) +* FDL, GNU Free Documentation License: GNU FDL. (line 6) +* file format, .mo: MO Files. (line 6) +* file format, .po: PO Files. (line 6) +* files, .po and .mo: Files. (line 6) +* files, .pot: Overview. (line 67) +* filter messages according to attributes: msgattrib Invocation. + (line 8) +* find common messages: msgcomm Invocation. (line 8) +* force use of fuzzy entries: msgfmt Invocation. (line 293) +* format strings: c-format Flag. (line 6) +* Free Pascal: Pascal. (line 6) +* function attribute, __format__: xgettext Invocation. (line 297) +* function attribute, __format_arg__: xgettext Invocation. (line 311) +* fuzzy entries: Fuzzy Entries. (line 6) +* fuzzy flag: PO Files. (line 83) +* gawk: gawk. (line 6) +* gcc-internal-format flag: PO Files. (line 233) +* GCC-source: GCC-source. (line 6) +* generate binary message catalog from PO file: msgfmt Invocation. + (line 8) +* generate translation catalog in English: msgen Invocation. (line 8) +* gettext files: Adjusting Files. (line 6) +* gettext installation: Installation. (line 6) +* gettext interface: Interface to gettext. + (line 6) +* gettext program, usage: gettext Invocation. (line 6) +* gettext vs catgets: Comparison. (line 6) +* gettext, a programmer's view: gettext. (line 6) +* gettext.h file: lib/gettext.h. (line 6) +* gettextize program, usage: gettextize Invocation. + (line 34) +* gfc-internal-format flag: PO Files. (line 237) +* GNOME PO file editor: Gtranslator. (line 6) +* Go: Go. (line 6) +* go-format flag: PO Files. (line 165) +* Go, string concatenation: No string concatenation. + (line 29) +* GPL, GNU General Public License: GNU GPL. (line 6) +* GUI programs: Contexts. (line 6) +* Guile: Scheme. (line 6) +* guile: Scheme. (line 6) +* Guile <1>: Scheme. (line 42) +* hash table, inside MO files: MO Files. (line 55) +* he, she, and they: Introduction. (line 15) +* header entry of a PO file: Header Entry. (line 6) +* help option: Split at paragraphs. (line 14) +* history of GNU gettext: History. (line 6) +* i18n: Concepts. (line 6) +* importing PO files: Normalizing. (line 54) +* include file libintl.h: Overview. (line 57) +* include file libintl.h <1>: Importing. (line 11) +* include file libintl.h <2>: Comparison. (line 33) +* include file libintl.h <3>: lib/gettext.h. (line 28) +* initialization: Triggering. (line 6) +* initialize new PO file: msginit Invocation. (line 8) +* initialize translations from a compendium: Using Compendia. (line 12) +* installing gettext: Installation. (line 6) +* interface to catgets: Interface to catgets. + (line 6) +* internationalization: Concepts. (line 16) +* inttypes.h: No string concatenation. + (line 151) +* inttypes.h <1>: c-format. (line 26) +* inttypes.h <2>: objc-format. (line 10) +* ISO 3166: Country Codes. (line 6) +* ISO 639: Language Codes. (line 6) +* Java: Java. (line 6) +* Java mode, and msgfmt program: msgfmt Invocation. (line 30) +* Java mode, and msgunfmt program: msgunfmt Invocation. (line 16) +* java-format flag: PO Files. (line 128) +* java-printf-format flag: PO Files. (line 133) +* Java, string concatenation: No string concatenation. + (line 29) +* javascript-format flag: PO Files. (line 141) +* JavaScript, string concatenation: No string concatenation. + (line 29) +* JavaScript, strings with embedded expressions: No string concatenation. + (line 78) +* KDE format strings: xgettext Invocation. (line 357) +* KDE PO file editor: Lokalize. (line 6) +* kde-format flag: PO Files. (line 209) +* keyboard accelerator checking: msgfmt Invocation. (line 281) +* l10n: Concepts. (line 6) +* language codes: Language Codes. (line 6) +* language selection: Locale Environment Variables. + (line 6) +* language selection at runtime: gettext grok. (line 14) +* large package: Ambiguities. (line 6) +* LGPL, GNU Lesser General Public License: GNU LGPL. (line 6) +* libiconv library: AM_ICONV. (line 20) +* libintl for C#: C#. (line 180) +* libintl for Java: Java. (line 109) +* libintl library: AM_GNU_GETTEXT. (line 43) +* librep Lisp: librep. (line 6) +* librep-format flag: PO Files. (line 157) +* License, GNU FDL: GNU FDL. (line 6) +* License, GNU GPL: GNU GPL. (line 6) +* License, GNU LGPL: GNU LGPL. (line 6) +* Licenses: Licenses. (line 6) +* LINGUAS file: po/LINGUAS. (line 6) +* link with libintl: Overview. (line 62) +* Linux: Aspects. (line 128) +* Linux <1>: Overview. (line 62) +* Linux <2>: Header Entry. (line 129) +* Lisp: Common Lisp. (line 6) +* lisp-format flag: PO Files. (line 149) +* list of translation teams, where to find: Header Entry. (line 54) +* locale categories: Aspects. (line 60) +* locale categories <1>: Aspects. (line 117) +* locale category, LC_ALL: Triggering. (line 23) +* locale category, LC_COLLATE: Triggering. (line 52) +* locale category, LC_CTYPE: Aspects. (line 66) +* locale category, LC_CTYPE <1>: Triggering. (line 23) +* locale category, LC_CTYPE <2>: Triggering. (line 52) +* locale category, LC_MESSAGES: Aspects. (line 111) +* locale category, LC_MESSAGES <1>: Triggering. (line 52) +* locale category, LC_MONETARY: Aspects. (line 79) +* locale category, LC_MONETARY <1>: Triggering. (line 52) +* locale category, LC_NUMERIC: Aspects. (line 96) +* locale category, LC_NUMERIC <1>: Triggering. (line 52) +* locale category, LC_RESPONSES: Triggering. (line 52) +* locale category, LC_TIME: Aspects. (line 85) +* locale category, LC_TIME <1>: Triggering. (line 52) +* locale program: Header Entry. (line 109) +* localization: Concepts. (line 26) +* lookup message translation: gettext Invocation. (line 9) +* lookup message translation <1>: eval_gettext Invocation. + (line 8) +* lookup message translation with context: eval_pgettext Invocation. + (line 8) +* lookup plural message translation: ngettext Invocation. (line 8) +* lookup plural message translation <1>: eval_ngettext Invocation. + (line 8) +* lookup plural message translation with context: eval_npgettext Invocation. + (line 8) +* lua-format flag: PO Files. (line 181) +* Lua, string concatenation: No string concatenation. + (line 29) +* magic signature of MO files: MO Files. (line 9) +* Makefile.in.in extensions: po/Rules-*. (line 6) +* Makevars file: po/Makevars. (line 6) +* manipulating PO files: Manipulating. (line 6) +* marking Perl sources: Perl. (line 97) +* marking string initializers: Special cases. (line 6) +* marking strings that require translation: Mark Keywords. (line 6) +* marking strings, preparations: Preparing Strings. (line 6) +* marking translatable strings: Overview. (line 34) +* markup: No unusual markup. (line 6) +* menu entries: Contexts. (line 6) +* menu, keyboard accelerator support: msgfmt Invocation. (line 281) +* merge PO files: msgcat Invocation. (line 8) +* merging two PO files: Manipulating. (line 10) +* merging two POT files: Combining POTs. (line 12) +* message catalog files location: Locating Catalogs. (line 6) +* messages: Aspects. (line 111) +* migration from earlier versions of gettext: Prerequisites. (line 6) +* mkinstalldirs file: mkinstalldirs. (line 6) +* mnemonics of menu entries: msgfmt Invocation. (line 281) +* MO file's format: MO Files. (line 6) +* modify message attributes: msgattrib Invocation. + (line 59) +* Modula-2: Modula-2. (line 6) +* Modula-2, string concatenation: No string concatenation. + (line 29) +* modula2-format flag: PO Files. (line 189) +* msgattrib program, usage: msgattrib Invocation. + (line 6) +* msgcat program, usage: msgcat Invocation. (line 6) +* msgcmp program, usage: msgcmp Invocation. (line 6) +* msgcomm program, usage: msgcomm Invocation. (line 6) +* msgconv program, usage: msgconv Invocation. (line 6) +* msgctxt: PO Files. (line 245) +* msgen program, usage: msgen Invocation. (line 6) +* msgexec program, usage: msgexec Invocation. (line 6) +* msgfilter filter and catalog encoding: msgfilter Invocation. + (line 62) +* msgfilter program, usage: msgfilter Invocation. + (line 6) +* msgfmt program, usage: msgfmt Invocation. (line 6) +* msggrep program, usage: msggrep Invocation. (line 6) +* msgid: PO Files. (line 60) +* msgid_plural: PO Files. (line 265) +* msginit program, usage: msginit Invocation. (line 6) +* msgmerge program, usage: msgmerge Invocation. (line 6) +* msgstr: PO Files. (line 60) +* msgunfmt program, usage: msgunfmt Invocation. (line 6) +* msguniq program, usage: msguniq Invocation. (line 6) +* multi-line strings: Normalizing. (line 64) +* N_, a convenience macro: Comparison. (line 41) +* Native Language Support: Concepts. (line 51) +* Natural Language Support: Concepts. (line 51) +* newlines in PO files: PO Files. (line 350) +* ngettext: Plural forms. (line 82) +* ngettext program, usage: ngettext Invocation. (line 6) +* NLS: Concepts. (line 51) +* no-awk-format flag: PO Files. (line 178) +* no-boost-format flag: PO Files. (line 214) +* no-c-format flag: PO Files. (line 94) +* no-c-format, and xgettext: c-format Flag. (line 47) +* no-c++-format flag: PO Files. (line 117) +* no-csharp-format flag: PO Files. (line 138) +* no-d-format flag: PO Files. (line 194) +* no-elisp-format flag: PO Files. (line 154) +* no-gcc-internal-format flag: PO Files. (line 234) +* no-gfc-internal-format flag: PO Files. (line 238) +* no-go-format flag: PO Files. (line 166) +* no-java-format flag: PO Files. (line 129) +* no-java-printf-format flag: PO Files. (line 134) +* no-javascript-format flag: PO Files. (line 142) +* no-kde-format flag: PO Files. (line 210) +* no-librep-format flag: PO Files. (line 158) +* no-lisp-format flag: PO Files. (line 150) +* no-lua-format flag: PO Files. (line 182) +* no-modula2-format flag: PO Files. (line 190) +* no-objc-format flag: PO Files. (line 113) +* no-object-pascal-format flag: PO Files. (line 186) +* no-perl-brace-format flag: PO Files. (line 226) +* no-perl-format flag: PO Files. (line 222) +* no-php-format flag: PO Files. (line 230) +* no-python-brace-format flag: PO Files. (line 125) +* no-python-format flag: PO Files. (line 121) +* no-qt-format flag: PO Files. (line 202) +* no-qt-plural-format flag: PO Files. (line 206) +* no-ruby-format flag: PO Files. (line 170) +* no-rust-format flag: PO Files. (line 162) +* no-scheme-format flag: PO Files. (line 146) +* no-sh-format flag: PO Files. (line 174) +* no-smalltalk-format flag: PO Files. (line 198) +* no-tcl-format flag: PO Files. (line 218) +* no-ycp-format flag: PO Files. (line 243) +* nplurals, in a PO file header: Plural forms. (line 188) +* number format: Aspects. (line 96) +* objc-format flag: PO Files. (line 112) +* Object Pascal: Pascal. (line 6) +* object-pascal-format flag: PO Files. (line 185) +* obsolete entries: Obsolete Entries. (line 6) +* OEM encoding: Working in a Windows console. + (line 6) +* optimization of gettext functions: Optimized gettext. (line 6) +* orthography: Manipulating. (line 28) +* outdigits: c-format. (line 34) +* output to stdout, xgettext: xgettext Invocation. (line 49) +* overview of gettext: Overview. (line 6) +* package and version declaration in configure.ac: configure.ac. + (line 9) +* package build and installation options: Installers. (line 6) +* package distributor's view of gettext: Installers. (line 6) +* package installer's view of gettext: Installers. (line 6) +* package maintainer's view of gettext: Maintainers. (line 6) +* paragraphs: Split at paragraphs. (line 6) +* Pascal: Pascal. (line 6) +* Perl: Perl. (line 6) +* Perl default keywords: Default Keywords. (line 6) +* Perl long lines: Long Lines. (line 6) +* Perl parentheses: Parentheses. (line 6) +* Perl pitfalls: Perl Pitfalls. (line 6) +* Perl quote-like expressions: Quote-like Expressions. + (line 6) +* Perl special keywords for hash-lookups: Special Keywords. (line 6) +* Perl unsupported string interpolation: Interpolation I. (line 6) +* Perl valid string interpolation: Interpolation II. (line 6) +* perl-brace-format flag: PO Files. (line 225) +* perl-format flag: PO Files. (line 221) +* Perl, string concatenation: No string concatenation. + (line 29) +* Perl, strings with embedded expressions: No string concatenation. + (line 78) +* pgettext: Contexts. (line 33) +* pgettext_expr: Contexts. (line 112) +* PHP: PHP. (line 6) +* php-format flag: PO Files. (line 229) +* PHP, string concatenation: No string concatenation. + (line 29) +* PHP, strings with embedded expressions: No string concatenation. + (line 78) +* Pike: Pike. (line 6) +* plural form formulas: Plural forms. (line 208) +* plural forms: Plural forms. (line 6) +* plural forms, in MO files: MO Files. (line 74) +* plural forms, in PO files: PO Files. (line 265) +* plural forms, translating: Translating plural forms. + (line 6) +* plural, in a PO file header: Plural forms. (line 188) +* PO files' format: PO Files. (line 6) +* PO mode (Emacs) commands: Main PO Commands. (line 6) +* PO template file: Template. (line 6) +* po_file_check_all: Checking API. (line 6) +* po_file_create: po_file_t API. (line 10) +* po_file_domain_header: PO Header Entry API. (line 11) +* po_file_domains: po_file_t API. (line 41) +* po_file_free: po_file_t API. (line 36) +* po_file_read: po_file_t API. (line 14) +* po_file_write: po_file_t API. (line 25) +* po_format_list: Format Type API. (line 6) +* po_format_pretty_name: Format Type API. (line 9) +* po_header_field: PO Header Entry API. (line 17) +* po_header_set_field: PO Header Entry API. (line 23) +* po_message_add_filepos: po_filepos_t API. (line 23) +* po_message_check_all: Checking API. (line 11) +* po_message_check_format: Checking API. (line 18) +* po_message_comments: po_message_t API. (line 78) +* po_message_create: po_message_t API. (line 10) +* po_message_extracted_comments: po_message_t API. (line 89) +* po_message_filepos: po_filepos_t API. (line 13) +* po_message_is_format: po_message_t API. (line 159) +* po_message_is_fuzzy: po_message_t API. (line 150) +* po_message_is_obsolete: po_message_t API. (line 141) +* po_message_is_range: po_message_t API. (line 172) +* po_message_iterator: po_message_iterator_t API. + (line 10) +* po_message_iterator_free: po_message_iterator_t API. + (line 17) +* po_message_msgctxt: po_message_t API. (line 19) +* po_message_msgid: po_message_t API. (line 30) +* po_message_msgid_plural: po_message_t API. (line 40) +* po_message_msgstr: po_message_t API. (line 53) +* po_message_msgstr_plural: po_message_t API. (line 64) +* po_message_prev_msgctxt: po_message_t API. (line 101) +* po_message_prev_msgid: po_message_t API. (line 114) +* po_message_prev_msgid_plural: po_message_t API. (line 126) +* po_message_remove_filepos: po_filepos_t API. (line 18) +* po_message_set_comments: po_message_t API. (line 83) +* po_message_set_extracted_comments: po_message_t API. (line 95) +* po_message_set_format: po_message_t API. (line 164) +* po_message_set_fuzzy: po_message_t API. (line 154) +* po_message_set_msgctxt: po_message_t API. (line 24) +* po_message_set_msgid: po_message_t API. (line 34) +* po_message_set_msgid_plural: po_message_t API. (line 46) +* po_message_set_msgstr: po_message_t API. (line 58) +* po_message_set_msgstr_plural: po_message_t API. (line 70) +* po_message_set_obsolete: po_message_t API. (line 145) +* po_message_set_prev_msgctxt: po_message_t API. (line 107) +* po_message_set_prev_msgid: po_message_t API. (line 119) +* po_message_set_prev_msgid_plural: po_message_t API. (line 133) +* po_message_set_range: po_message_t API. (line 178) +* po_next_message: po_message_iterator_t API. + (line 22) +* Pology: Other tools. (line 9) +* portability problems with sed: msgfilter Invocation. + (line 73) +* POTFILES.in file: po/POTFILES.in. (line 6) +* preparing programs for translation: Sources. (line 6) +* preparing rules for XML translation: Preparing ITS Rules. (line 6) +* preparing shell scripts for translation: Preparing Shell Scripts. + (line 6) +* problems with catgets interface: Problems with catgets. + (line 6) +* programming languages: Language Implementors. + (line 6) +* Python: Python. (line 6) +* python-brace-format flag: PO Files. (line 124) +* python-format flag: PO Files. (line 120) +* Python, string concatenation: No string concatenation. + (line 29) +* Python, strings with embedded expressions: No string concatenation. + (line 78) +* Qt format strings: xgettext Invocation. (line 353) +* Qt mode, and msgfmt program: msgfmt Invocation. (line 46) +* qt-format flag: PO Files. (line 201) +* qt-plural-format flag: PO Files. (line 205) +* quotation marks: Header Entry. (line 162) +* quotation marks <1>: po/Rules-*. (line 11) +* quote characters, use in PO files: Header Entry. (line 162) +* range: flag: PO Files. (line 296) +* recode-sr-latin program: msgfilter Invocation. + (line 101) +* related reading: References. (line 6) +* release: Release Management. (line 6) +* RSJ: RST. (line 6) +* RST: RST. (line 6) +* Ruby: Ruby. (line 6) +* ruby-format flag: PO Files. (line 169) +* Ruby, string concatenation: No string concatenation. + (line 29) +* Ruby, strings with embedded expressions: No string concatenation. + (line 78) +* Rust: Rust. (line 6) +* rust-format flag: PO Files. (line 161) +* Scheme: Scheme. (line 6) +* Scheme <1>: Scheme. (line 42) +* scheme-format flag: PO Files. (line 145) +* scripting languages: Language Implementors. + (line 6) +* search messages in a catalog: msggrep Invocation. (line 8) +* selecting message language: Locale Environment Variables. + (line 6) +* sentence end markers, xgettext: xgettext Invocation. (line 164) +* sentences: Entire sentences. (line 6) +* setting up gettext at build time: Installers. (line 6) +* setting up gettext at run time: Locale Environment Variables. + (line 6) +* several domains: Ambiguities. (line 6) +* sex: Introduction. (line 15) +* sh-format flag: PO Files. (line 173) +* she, he, and they: Introduction. (line 15) +* shell format string: envsubst Invocation. (line 8) +* shell scripts: sh. (line 6) +* Shell, string concatenation: No string concatenation. + (line 29) +* Shell, strings with embedded expressions: No string concatenation. + (line 78) +* Smalltalk: Smalltalk. (line 6) +* smalltalk-format flag: PO Files. (line 197) +* Smalltalk, string concatenation: No string concatenation. + (line 29) +* sorting msgcat output: msgcat Invocation. (line 156) +* sorting msgmerge output: msgmerge Invocation. (line 195) +* sorting msgunfmt output: msgunfmt Invocation. (line 147) +* sorting output of xgettext: xgettext Invocation. (line 467) +* specifying plural form in a PO file: Plural forms. (line 188) +* standard output, and msgcat: msgcat Invocation. (line 48) +* standard output, and msgmerge program: msgmerge Invocation. (line 53) +* string concatenation: No string concatenation. + (line 6) +* string normalization in entries: Normalizing. (line 6) +* style: Decent English style. + (line 6) +* supported languages, msgfmt: msgfmt Invocation. (line 180) +* supported languages, xgettext: xgettext Invocation. (line 57) +* supported syntax checks, xgettext: xgettext Invocation. (line 128) +* Tcl: Tcl. (line 6) +* Tcl mode, and msgfmt program: msgfmt Invocation. (line 43) +* Tcl mode, and msgunfmt program: msgunfmt Invocation. (line 26) +* tcl-format flag: PO Files. (line 217) +* Tcl, strings with embedded expressions: No string concatenation. + (line 78) +* template PO file: Overview. (line 67) +* testing .po files for equivalence: xgettext Invocation. (line 480) +* Tk's scripting language: Tcl. (line 6) +* Translate Toolkit: Other tools. (line 24) +* translated entries: Translated Entries. (line 6) +* translating menu entries: Contexts. (line 6) +* translation aspects: Aspects. (line 6) +* Translation Matrix: Installing Localizations. + (line 6) +* Translation Project: Why. (line 17) +* turning off NLS support: lib/gettext.h. (line 6) +* tutorial of gettext usage: Overview. (line 6) +* TypeScript, string concatenation: No string concatenation. + (line 29) +* TypeScript, strings with embedded expressions: No string concatenation. + (line 78) +* unify duplicate translations: msguniq Invocation. (line 8) +* untranslated entries: Untranslated Entries. + (line 6) +* update translations from a compendium: Using Compendia. (line 20) +* upgrading to new versions of gettext: Prerequisites. (line 6) +* Vala, string concatenation: No string concatenation. + (line 29) +* version control for backup files, msgmerge: msgmerge Invocation. + (line 67) +* weblate: Web based localization. + (line 6) +* Windows: Working in a Windows console. + (line 6) +* wxWidgets library: wxWidgets. (line 6) +* xargs, and output from msgexec: msgexec Invocation. (line 14) +* xerror: Error Handling. (line 15) +* xerror2: Error Handling. (line 37) +* xgettext program, usage: xgettext Invocation. (line 6) +* XML mode, and msgfmt program: msgfmt Invocation. (line 52) +* xmodmap program, and typing quotation marks: Header Entry. (line 174) +* YaST2 scripting language: YCP. (line 6) +* YCP: YCP. (line 6) +* ycp-format flag: PO Files. (line 242) + + + +Tag Table: +Node: Top2954 +Node: Introduction20196 +Node: Why21911 +Ref: Why-Footnote-125144 +Node: Concepts25300 +Node: Aspects28749 +Node: Files35347 +Node: Overview37295 +Node: Users48319 +Node: System Installation49307 +Node: Setting the GUI Locale50983 +Node: Setting the POSIX Locale52371 +Node: Locale Names53355 +Node: Locale Environment Variables56223 +Node: The LANGUAGE variable58564 +Node: Working in a Windows console61162 +Node: Installing Localizations62797 +Node: PO Files64085 +Ref: PO Files-Footnote-178506 +Node: Sources78641 +Node: Importing79945 +Node: Triggering80633 +Node: Preparing Strings84036 +Node: Decent English style85118 +Node: Entire sentences85973 +Node: Split at paragraphs88859 +Node: No string concatenation89920 +Node: No embedded URLs97498 +Node: No custom format directives98328 +Node: No unusual markup100108 +Node: Mark Keywords101563 +Node: Marking106439 +Node: Translator advice114400 +Node: c-format Flag116312 +Node: Special cases120512 +Node: Bug Report Address123296 +Node: Names125265 +Node: Libraries129564 +Node: Template132949 +Node: xgettext Invocation133770 +Node: Combining POTs159187 +Node: Creating161196 +Node: msginit Invocation162105 +Node: Header Entry166696 +Node: Updating176093 +Node: msgmerge Invocation176312 +Node: Editing183154 +Node: Web based localization184119 +Node: Lokalize185824 +Node: Gtranslator186171 +Node: Poedit186523 +Node: OmegaT186846 +Node: Virtaal187545 +Node: PO Mode188066 +Node: Installation189713 +Node: Main PO Commands191713 +Node: Entry Positioning196985 +Node: Normalizing202630 +Node: Translated Entries207187 +Node: Fuzzy Entries208596 +Node: Untranslated Entries211907 +Node: Obsolete Entries213910 +Node: Modifying Translations217213 +Node: Modifying Comments225355 +Node: Subedit229902 +Node: C Sources Context233916 +Node: Auxiliary239147 +Node: Vim242471 +Node: Compendium243136 +Node: Creating Compendia243751 +Node: Using Compendia246280 +Node: Manipulating247234 +Node: msgcat Invocation251236 +Node: msgconv Invocation256687 +Node: msggrep Invocation260666 +Node: msgfilter Invocation267462 +Node: msguniq Invocation275786 +Node: msgcomm Invocation280514 +Node: msgcmp Invocation285529 +Node: msgattrib Invocation287770 +Node: msgen Invocation293493 +Node: msgexec Invocation297890 +Node: Colorizing301196 +Node: The --color option302376 +Node: The TERM variable304242 +Node: The --style option305794 +Node: Style rules307170 +Node: Customizing less314170 +Node: Other tools315625 +Node: libgettextpo316645 +Node: Error Handling319874 +Node: po_file_t API321857 +Node: po_message_iterator_t API324071 +Node: po_message_t API325292 +Node: PO Header Entry API334154 +Node: po_filepos_t API335385 +Node: Format Type API336539 +Node: Checking API337116 +Node: Binaries338337 +Node: msgfmt Invocation338689 +Node: msgunfmt Invocation350963 +Node: MO Files355637 +Node: Programmers364644 +Node: catgets365844 +Node: Interface to catgets367250 +Node: Problems with catgets369301 +Node: gettext370223 +Node: Interface to gettext371746 +Node: Ambiguities374096 +Node: Locating Catalogs377161 +Ref: Locating Catalogs-Footnote-1378425 +Ref: Locating Catalogs-Footnote-2378655 +Node: Charset conversion378808 +Node: Contexts381326 +Node: Plural forms386928 +Ref: Plural forms-Footnote-1404257 +Node: Optimized gettext404625 +Node: Comparison405976 +Node: Using libintl.a410341 +Node: gettext grok410796 +Node: Temp Programmers413499 +Node: Temp Implementations414031 +Node: Temp catgets415418 +Node: Temp WSI417139 +Node: Temp Notes419194 +Node: Translators419708 +Node: Organization420190 +Node: Responsibilities421295 +Node: Dialects423519 +Node: Translating plural forms425280 +Node: Prioritizing messages428705 +Node: Maintainers433082 +Node: Flat and Non-Flat435049 +Node: Prerequisites436563 +Node: gettextize Invocation440714 +Node: Adjusting Files447373 +Node: po/POTFILES.in449158 +Node: po/LINGUAS450431 +Node: po/Makevars452236 +Node: po/Rules-*453225 +Node: configure.ac454780 +Node: config.guess456593 +Node: mkinstalldirs457967 +Node: aclocal458314 +Node: config.h.in460512 +Node: Makefile461279 +Node: src/Makefile463570 +Node: lib/gettext.h467801 +Node: autoconf macros470066 +Node: AM_GNU_GETTEXT471146 +Node: AM_GNU_GETTEXT_VERSION475364 +Node: AM_GNU_GETTEXT_NEED475843 +Node: AM_PO_SUBDIRS476759 +Node: AM_XGETTEXT_OPTION477591 +Node: AM_ICONV478502 +Node: Version Control Issues480879 +Node: Distributed Development481634 +Node: Files under Version Control483636 +Node: Translations under Version Control487123 +Ref: Translations under Version Control-Footnote-1489195 +Node: autopoint Invocation489285 +Node: Release Management491663 +Node: Installers492204 +Node: Programming Languages494172 +Node: Language Implementors494947 +Node: Programmers for other Languages500913 +Node: Translators for other Languages501505 +Node: c-format503673 +Node: objc-format505786 +Node: c++-format506288 +Node: python-format506852 +Node: java-format507629 +Node: csharp-format508544 +Node: javascript-format508931 +Node: scheme-format509724 +Node: lisp-format510002 +Node: elisp-format510362 +Node: librep-format510858 +Node: rust-format511261 +Node: go-format512566 +Node: ruby-format512851 +Node: sh-format513623 +Node: awk-format514471 +Node: lua-format514786 +Node: object-pascal-format515127 +Node: modula2-format515518 +Node: d-format516580 +Node: smalltalk-format516894 +Node: qt-format517421 +Node: qt-plural-format517864 +Node: kde-format518223 +Node: kde-kuit-format518655 +Node: boost-format519297 +Node: tcl-format519890 +Node: perl-format520194 +Node: php-format520989 +Node: gcc-internal-format521365 +Node: gfc-internal-format522524 +Node: ycp-format523274 +Node: Maintainers for other Languages523672 +Node: List of Programming Languages524610 +Node: C526207 +Node: Python527856 +Node: Java531036 +Node: C#537187 +Node: JavaScript546728 +Node: TypeScript547910 +Node: Scheme548935 +Node: Common Lisp550486 +Node: clisp C551362 +Node: Emacs Lisp552145 +Node: librep552951 +Node: Rust553761 +Node: Go556067 +Node: Ruby561121 +Node: sh562058 +Node: Preparing Shell Scripts563659 +Node: gettext.sh567301 +Node: gettext Invocation567993 +Node: ngettext Invocation570409 +Node: envsubst Invocation572423 +Node: eval_gettext Invocation573904 +Node: eval_ngettext Invocation574371 +Node: eval_pgettext Invocation574924 +Node: eval_npgettext Invocation575461 +Node: bash576046 +Node: gawk578085 +Node: Lua579214 +Node: Pascal580549 +Node: Modula-2582003 +Node: D582945 +Node: Smalltalk584666 +Node: Vala585791 +Node: wxWidgets586754 +Node: Tcl587776 +Node: Perl589292 +Node: General Problems592705 +Node: Default Keywords598355 +Node: Special Keywords600226 +Node: Quote-like Expressions601784 +Node: Interpolation I604101 +Node: Interpolation II608061 +Node: Parentheses610454 +Node: Long Lines611979 +Node: Perl Pitfalls613846 +Node: PHP618144 +Node: Pike619166 +Node: GCC-source619904 +Node: YCP620749 +Node: Data Formats621538 +Node: Internationalizable Data621939 +Node: POT622639 +Node: RST622914 +Node: Glade623424 +Node: GSettings623893 +Node: AppData624245 +Node: Preparing ITS Rules624854 +Node: ITS Rules625190 +Node: Locating Rules630316 +Ref: Locating Rules-Footnote-1633415 +Node: Localized Data633747 +Node: Editable Message Catalogs634231 +Node: PO634835 +Node: Java .properties635016 +Node: GNUstep .strings635222 +Node: Compiled Message Catalogs635432 +Node: MO636062 +Node: Java ResourceBundle636290 +Node: C# Satellite Assembly636641 +Node: C# Resource636921 +Node: Tcl message catalog637187 +Node: Qt message catalog637514 +Node: Desktop Entry637797 +Node: Icons638464 +Node: XML640048 +Node: Conclusion640273 +Node: History640834 +Node: The original ABOUT-NLS645216 +Node: INSTALL Matters646638 +Node: Using This Package648608 +Node: Translating Teams651878 +Node: Available Packages653393 +Node: Using gettext in own code725596 +Node: References726721 +Node: Language Codes728433 +Node: Usual Language Codes728948 +Node: Rare Language Codes733988 +Node: Country Codes735838 +Node: Licenses742960 +Node: GNU GPL744816 +Node: GNU LGPL763960 +Node: GNU FDL791989 +Node: Program Index817094 +Node: Option Index819504 +Node: Variable Index872526 +Node: PO Mode Index877614 +Node: Autoconf Macro Index894312 +Node: Index894977 + +End Tag Table + + +Local Variables: +coding: utf-8 +End: diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/info/libtextstyle.info b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/info/libtextstyle.info new file mode 100644 index 0000000000000000000000000000000000000000..c37fe1ac9442e4bbd4018c3cc73daf39c410dd64 --- /dev/null +++ b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/info/libtextstyle.info @@ -0,0 +1,2789 @@ +This is libtextstyle.info, produced by makeinfo version 7.1 from +libtextstyle.texi. + + Copyright (C) 2018-2024 Free Software Foundation, Inc. + + 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 +. + + 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 . +INFO-DIR-SECTION Software development +START-INFO-DIR-ENTRY +* GNU libtextstyle: (libtextstyle). Output of styled text. +END-INFO-DIR-ENTRY + + This manual provides documentation for the GNU ‘libtextstyle’ +library. + + +File: libtextstyle.info, Node: Top, Next: Introduction, Up: (dir) + +GNU libtextstyle +**************** + + This manual documents the GNU libtextstyle library, version 0.25. + +* Menu: + +* Introduction:: Introduction +* The user's view:: The user's perspective +* The programmer's view:: The programmer's perspective +* Licenses:: +* Function Index:: +* Variable Index:: +* Index:: + + +File: libtextstyle.info, Node: Introduction, Next: The user's view, Prev: Top, Up: Top + +1 Introduction +************** + + Text is easier to read when it is accompanied with styling +information, such as color, font attributes (weight, posture), or +underlining, and this styling is customized appropriately for the output +device. + + GNU libtextstyle provides an easy way to add styling to programs that +produce output to a console or terminal emulator window. It does this +in a way that allows the end user to customize the styling using the +industry standard, namely Cascading Style Sheets (CSS). + +* Menu: + +* Style definitions:: +* Built-in versus separate styling:: + + +File: libtextstyle.info, Node: Style definitions, Next: Built-in versus separate styling, Up: Introduction + +1.1 Style definitions +===================== + + Let's look at the traditional way styling is done for specific +programs. + + Browsers, when they render HTML, use CSS styling. + + The older approach to user-customizable text styling is that the user +associates patterns with escape sequences in an environment variable or +a command-line argument. This is the approach used, for example, by the +GNU ‘ls’ program in combination with the ‘dircolors’ program. The +processing is distributed across several steps: + 1. There is default style definition that is hard-coded in the + ‘dircolors’ program. The user can also define their own + definitions in a file such as ‘~/.dir_colors’. This style + definition contains explicit terminal escape sequences; thus, it + can only be used with consoles and terminal emulators, and each + style definition applies only to a certain class of + mostly-compatible terminal emulators. + 2. The ‘dircolors’ program, when invoked, translates such a style + definition to a sequence of shell statements that sets an + environment variable ‘LS_COLORS’. + 3. The shell executes these statements, and thus sets the environment + variable ‘LS_COLORS’. + 4. The program looks at the environment variable and emits the listed + escape sequences. + + In contrast, this library implements styling as follows: + 1. There is a default style definition in a CSS file that is part of + the same package as the stylable program. The user can also define + their own definitions in a CSS file, and set an environment + environment variable to point to it. + 2. The program looks at the environment variable, parses the CSS file, + translates the styling specifications to the form that is + appropriate for the output device (escape sequences for terminal + emulators, inline CSS and ‘’ elements for HTML output), and + emits it. + + Thus, with GNU libtextstyle, the styling has the following +properties: + • It is easier for the user to define their own styling, because the + file format is standardized and supported by numerous syntax aware + editors. + • A styling file does not depend on the particular output device. An + HTML output and a black-on-white terminal emulator can use the same + styling file. A white-on-black (or even green-on-black) terminal + emulator will need different styling, though. + • It is simpler: There is no need for a program that converts the + style specification from one format to another. + + +File: libtextstyle.info, Node: Built-in versus separate styling, Prev: Style definitions, Up: Introduction + +1.2 Built-in versus separate styling +==================================== + + There are generally two approaches for adding styling to text: + • The program that generates the text adds the styling. It does so + through interleaved statements that turn on or off specific + attributes. + • The styling gets added by a separate program, that postprocesses + the output. This separate program usually uses regular expressions + to determine which text regions to style with a certain set of text + attributes. + + The first approach produces a styling that is 100% correct, +regardless of the complexity of the text that is being output. This is +the preferred approach for example for JSON, XML, or programming +language text. + + The second approach works well if the output has a simple, +easy-to-parse format. It may produce wrong styling in some cases when +the text format is more complex. This approach is often used for +viewing log files. + + GNU libtextstyle supports both approaches; it includes an example +program for each of the two approaches. + + +File: libtextstyle.info, Node: The user's view, Next: The programmer's view, Prev: Introduction, Up: Top + +2 The end user's perspective +**************************** + + Styled output can viewed fine in a console or terminal emulator +window. + + The stylable program will typically have the following options: +‘--color’ + Use colors and other text attributes always. +‘--color=WHEN’ + Use colors and other text attributes if WHEN. WHEN may be + ‘always’, ‘never’, ‘auto’, or ‘html’. +‘--style=STYLE-FILE’ + Specify the CSS style rule file for ‘--color’. + + For more details, see the sections *note The --color option:: and +*note The --style option:: below. + + If the output does not fit on a screen, you can use ‘less -R’ to +scroll around in the styled output. For example: + PROGRAM --color ARGUMENTS | less -R + +* Menu: + +* The TERM variable:: +* The NO_COLOR variable:: +* The NO_TERM_HYPERLINKS variable:: +* Emacs:: +* The --color option:: +* The --style option:: + + +File: libtextstyle.info, Node: The TERM variable, Next: The NO_COLOR variable, Up: The user's view + +2.1 The environment variable ‘TERM’ +=================================== + + The environment variable ‘TERM’ contains a identifier for the text +window's capabilities. You can get a detailed list of these +cababilities by using the ‘infocmp’ command (for example: ‘infocmp -L1 +xterm’), using ‘man 5 terminfo’ as a reference. + + When producing text with embedded color directives, a +‘libtextstyle’-enabled program looks at the ‘TERM’ variable. Text +windows today typically support at least 8 colors. Often, however, the +text window supports 16 or more colors, even though the ‘TERM’ variable +is set to a identifier denoting only 8 supported colors. It can be +worth setting the ‘TERM’ variable to a different value in these cases. + + After setting ‘TERM’, you can verify how well it works by invoking +‘PROGRAM --color=test’, where ‘PROGRAM’ is any ‘libtextstyle’-enabled +program, and seeing whether the output looks like a reasonable color +map. + +* Menu: + +* Terminal emulators:: +* Consoles:: + + +File: libtextstyle.info, Node: Terminal emulators, Next: Consoles, Up: The TERM variable + +2.1.1 Terminal emulator programs +-------------------------------- + + The following terminal emulator programs support 256 colors and set +‘TERM=xterm-256color’ accordingly: + + • In GNOME: ‘gnome-terminal’, ‘tilda’. + • ‘rxvt-unicode’ (sets ‘TERM=rxvt-unicode-256color’). + • ‘st’ (sets ‘TERM=st-256color’). + • ‘QTerminal’. + • On macOS: ‘Terminal’, ‘iTerm2’. + + The following terminal emulator programs support 256 colors. You +only need to set ‘TERM=xterm-256color’ or similar; the programs by +default set ‘TERM’ to a value that supports only 8 colors. + + • ‘xterm’ is in many cases built with support for 256 colors. But it + sets ‘TERM=xterm’. You need to set ‘TERM=xterm-256color’. + • In GNOME: ‘guake’ (sets ‘TERM=xterm’). You need to set + ‘TERM=xterm-256color’. + • In KDE: ‘konsole’ (sets ‘TERM=xterm’). You need to set + ‘TERM=xterm-256color’ or ‘TERM=konsole-256color’. + • In KDE: ‘yakuake’ (sets ‘TERM=xterm’). You need to set + ‘TERM=xterm-256color’. + • In Enlightenment: ‘Eterm’ (sets ‘TERM=Eterm’). You need to set + ‘TERM=Eterm-256color’. + • ‘mlterm’ (sets ‘TERM=mlterm’). You need to set + ‘TERM=mlterm-256color’. + • On Windows: ‘PuTTY’ (sets ‘TERM=xterm’). You need to set + ‘TERM=xterm-256color’ or ‘TERM=putty-256color’. + • On Windows: ‘TeraTerm’ (sets ‘TERM=xterm’). You need to set + ‘TERM=xterm-256color’. + + A couple of terminal emulator programs support even the entire RGB +color space (16 million colors). To get this to work, at this date +(2019), you need three things: + • The ‘ncurses’ library version 6.1 or newer must be installed. + • You need a recent version of the respective terminal emulator + program. See for the most + recent developments in this area. + • You need to set the ‘TERM’ environment variable to the + corresponding value: ‘TERM=xterm-direct’ instead of ‘TERM=xterm’ or + ‘TERM=xterm-256color’, ‘TERM=konsole-direct’ in ‘konsole’, + ‘TERM=st-direct’ in ‘st’, ‘TERM=mlterm-direct’ in ‘mlterm’, or + ‘TERM=iterm2-direct’ in ‘iTerm2’ on macOS. + + +File: libtextstyle.info, Node: Consoles, Prev: Terminal emulators, Up: The TERM variable + +2.1.2 Consoles +-------------- + + On OpenBSD 6 consoles, ‘TERM=xterm’ produces better results than the +default ‘TERM=vt220’. + + On NetBSD 8 consoles, ‘TERM=netbsd6’ produces better results than the +default ‘TERM=vt100’. + + On Windows consoles, no ‘TERM’ setting is needed. + + +File: libtextstyle.info, Node: The NO_COLOR variable, Next: The NO_TERM_HYPERLINKS variable, Prev: The TERM variable, Up: The user's view + +2.2 The environment variable ‘NO_COLOR’ +======================================= + + The environment variable ‘NO_COLOR’ can be used to suppress styling +in the textual output. When this environment variable is set (to any +value), ‘libtextstyle’-enabled programs will not emit colors and other +text styling. + + This environment variable can be overridden by passing the +command-line option ‘--color=always’ (see *note The --color option::). + + +File: libtextstyle.info, Node: The NO_TERM_HYPERLINKS variable, Next: Emacs, Prev: The NO_COLOR variable, Up: The user's view + +2.3 The environment variable ‘NO_TERM_HYPERLINKS’ +================================================= + + The environment variable ‘NO_TERM_HYPERLINKS’ can be used to suppress +hyperlinks in the textual output. When this environment variable is set +(to any value), ‘libtextstyle’-enabled programs will not emit +hyperlinks. This may be useful for terminal emulators which produce +garbage output when they receive the escape sequence for a hyperlink. +Currently (as of 2019), this affects some versions of ‘konsole’, +‘emacs’, ‘lxterminal’, ‘guake’, ‘yakuake’, ‘rxvt’. + + +File: libtextstyle.info, Node: Emacs, Next: The --color option, Prev: The NO_TERM_HYPERLINKS variable, Up: The user's view + +2.4 Emacs as a terminal emulator +================================ + + Emacs has several terminal emulators: ‘M-x shell’ and ‘M-x term’. +‘M-x term’ has good support for styling, whereas in ‘M-x shell’ most of +the styling gets lost. + + +File: libtextstyle.info, Node: The --color option, Next: The --style option, Prev: Emacs, Up: The user's view + +2.5 The ‘--color’ option +======================== + + The ‘--color=WHEN’ option specifies under which conditions styled +(colorized) output should be generated. The WHEN part can be one of the +following: + +‘always’ +‘yes’ + The output will be colorized. + +‘never’ +‘no’ + The output will not be colorized. + +‘auto’ +‘tty’ + The output will be colorized if the output device is a tty, i.e. + when the output goes directly to a text screen or terminal emulator + window. + +‘html’ + The output will be colorized and be in HTML format. This value is + only supported by some programs. + +‘test’ + This is a special value, understood only by some programs. It is + explained in the section (*note The TERM variable::) above. + +‘--color’ is equivalent to ‘--color=yes’. The default is +‘--color=auto’. + + Thus, a command that invokes a ‘libtextstyle’-enabled program will +produce colorized output when called by itself in a command window. +Whereas in a pipe, such as ‘PROGRAM ARGUMENTS | less -R’, it will not +produce colorized output. To get colorized output in this situation +nevertheless, use the command ‘PROGRAM --color ARGUMENTS | less -R’. + + The ‘--color=html’ option will produce output that can be viewed in a +browser. This can be useful, for example, for Indic languages, because +the renderic of Indic scripts in browsers is usually better than in +terminal emulators. + + Note that the output produced with the ‘--color’ option is _not_ +consumable by programs that expect the raw text. It contains additional +terminal-specific escape sequences or HTML tags. For example, an XML +parser will give a syntax error when confronted with a colored XML +output. Except for the ‘--color=html’ case, you therefore normally +don't need to save output produced with the ‘--color’ option in a file. + + +File: libtextstyle.info, Node: The --style option, Prev: The --color option, Up: The user's view + +2.6 The ‘--style’ option +======================== + + The ‘--style=STYLE_FILE’ option specifies the style file to use when +colorizing. It has an effect only when the ‘--color’ option is +effective. + + If the ‘--style’ option is not specified, the program may consider +the value of an environment variable. It is meant to point to the +user's preferred style for such output. The name of such an environment +variable, if supported, is documented in the documentation of the +‘libtextstyle’-enabled program. + + You can also design your own styles. This is described in the next +section. + +* Menu: + +* Style rules:: How to create a style file +* Debugging style files:: How to debug a style file + + +File: libtextstyle.info, Node: Style rules, Next: Debugging style files, Up: The --style option + +2.6.1 Creating your own style files +----------------------------------- + + The same style file can be used for styling a certain type of output, +for terminal output and for HTML output. It is written in CSS +(Cascading Style Sheet) syntax. See for a +formal definition of CSS. Many HTML authoring tutorials also contain +explanations of CSS. + + In the case of HTML output, the style file is embedded in the HTML +output. In the case of text output, the style file is interpreted by +the ‘libtextstyle’-enabled program. + + You should avoid ‘@import’ statements, because + − In the case of HTML output, the files referenced by the ‘@import’ + statements would not be embedded in the HTML output. In fact, + relative file names would be interpreted relative to the resulting + HTML file. + − In the case of text output, ‘@import’s are not supported, due to a + limitation in ‘libcroco’. + + CSS rules are built up from selectors and declarations. The +declarations specify graphical properties; the selectors specify when +they apply. + + GNU libtextstyle supports simple selectors based on "CSS classes", +see the CSS2 spec, section 5.8.3. The set of CSS classes that are +supported by a ‘libtextstyle’-enabled program are documented in the +documentation of that program. + + These selectors can be combined to hierarchical selectors. For +example, assume a program supports the CSS classes ‘string’ (that +matches a string) and ‘non-ascii’ (that matches a word with non-ASCII +characters), you could write + + .string .non-ascii { color: red; } + +to highlight only the non-ASCII words inside strings. + + In text mode, pseudo-classes (CSS2 spec, section 5.11) and +pseudo-elements (CSS2 spec, section 5.12) are not supported. + + The declarations in HTML mode are not limited; any graphical +attribute supported by the browsers can be used. + + The declarations in text mode are limited to the following +properties. Other properties will be silently ignored. + +‘color’ (CSS2 spec, section 14.1) +‘background-color’ (CSS2 spec, section 14.2.1) + These properties are supported. Colors will be adjusted to match + the terminal's capabilities. Note that many terminals support only + 8 colors. + +‘font-weight’ (CSS2 spec, section 15.2.3) + This property is supported, but most terminals can only render two + different weights: ‘normal’ and ‘bold’. Values >= 600 are rendered + as ‘bold’. + +‘font-style’ (CSS2 spec, section 15.2.3) + This property is supported. The values ‘italic’ and ‘oblique’ are + rendered the same way. + +‘text-decoration’ (CSS2 spec, section 16.3.1) + This property is supported, limited to the values ‘none’ and + ‘underline’. + + +File: libtextstyle.info, Node: Debugging style files, Prev: Style rules, Up: The --style option + +2.6.2 Debugging style files +--------------------------- + + If you want to understand why the style rules in a style file produce +the output that you see, you can do so in three steps: + + 1. Run the program with the command-line option ‘--color=html’, + redirecting the output to a file. + 2. Open the resulting HTML file in a browser. + 3. Use the browser's built-in CSS debugging tool. + • In Firefox: From the pop-up menu, select "Inspect Element". + Click somewhere in the DOM tree ("Inspector" tab) and look at + the CSS declarations in the "Rules" tab. + • In Chromium: From the pop-up menu, select "Inspect". Click + somewhere in the DOM tree ("Elements" tab) and look at the CSS + declarations in the "Styles" tab. + + This technique allows you, in particular, to see which CSS +declarations override which other CSS declarations from other CSS rules. + + +File: libtextstyle.info, Node: The programmer's view, Next: Licenses, Prev: The user's view, Up: Top + +3 The programmer's perspective +****************************** + + As a programmer, enabling styling consists of the following tasks: + 1. Define the command-line options and environment variable that the + user can use to control the styling. + 2. Define the CSS classes that the user can use in the CSS file. Each + CSS class corresponds to a text role; each CSS class can be given a + different styling by the user. + 3. Change the output routines so that they take an ‘ostream_t’ object + as argument instead of a ‘FILE *’. + 4. Insert paired invocations to ‘styled_ostream_begin_css_class’, + ‘styled_ostream_end_css_class’ around each run of text with a + specific text role. + 5. Link with ‘libtextstyle’. If your package is using GNU autoconf, + you can use the ‘libtextstyle.m4’ macro from Gnulib. + 6. Prepare a default style file. + 7. Update the documentation of your package. + + The following sections go into more detail. + +* Menu: + +* Basic use:: +* Include files:: +* Link options:: +* Command-line options:: +* The output stream hierarchy:: +* Debugging the styling code:: +* What to document:: + + +File: libtextstyle.info, Node: Basic use, Next: Include files, Up: The programmer's view + +3.1 Basic use of libtextstyle +============================= + + Source code that makes use of GNU libtextstyle needs an include +statement: + + #include + + Basic use of GNU libtextstyle consists of statements like these: + + styled_ostream_t stream = + styled_ostream_create (STDOUT_FILENO, "(stdout)", TTYCTL_AUTO, + style_file_name); + ... + styled_ostream_begin_use_class (stream, css_class); + ... + ostream_write_str (stream, string); + ... + styled_ostream_end_use_class (stream, css_class); + ... + styled_ostream_free (stream); + + Before this snippet, your code needs to determine the name of the +style file to use (‘style_file_name’). If no styling is desired - the +precise condition depends on the value of ‘color_mode’ but also on your +application logic -, you should set ‘style_file_name’ to ‘NULL’. + + An object of type ‘styled_ostream_t’ is allocated. The function +‘styled_ostream_create’ allocates it; the function ‘styled_ostream_free’ +deallocates it. + + Such ‘styled_ostream_t’ supports output operations +(‘ostream_write_str’), interleaved with adding and removing CSS classes. +The CSS class in effect when an output operation is performed +determines, through the style file, the text attributes associated with +that piece of text. + +* Menu: + +* Hyperlinks:: + + +File: libtextstyle.info, Node: Hyperlinks, Up: Basic use + +3.1.1 Hyperlinks +---------------- + + Text output may contain hyperlinks. These hyperlinks are encoded +through an escape sequence, specified at Hyperlinks in terminal +emulators +(https://gist.github.com/egmontkob/eb114294efbcd5adb1944c9f3cb5feda). +Currently (as of 2024), they are displayed in many modern terminals, see +OSC8-Adoption (https://github.com/Alhadis/OSC8-Adoption). More terminal +emulators will support hyperlinks in the future. Terminal emulators +which don't support hyperlinks ignore it, except for a few terminal +emulators, for which users may need to disable the hyperlinks (see *note +The NO_TERM_HYPERLINKS variable::) if the heuristic built into +‘libtextstyle’ does not already disable them. + + To emit a hyperlink, use code like this: + + styled_ostream_t stream = ... + ... + /* Start a hyperlink. */ + styled_ostream_set_hyperlink (stream, url, NULL); + ... + /* Emit the anchor text. This can be styled text. */ + ostream_write_str (stream, "Click here!"); + ... + /* End the current hyperlink. */ + styled_ostream_set_hyperlink (stream, NULL, NULL); + + The anchor text can be styled. But the hyperlinks themselves cannot +be styled; they behave as implemented by the terminal emulator. + + +File: libtextstyle.info, Node: Include files, Next: Link options, Prev: Basic use, Up: The programmer's view + +3.2 Include files +================= + + The include file ‘’ declares all facilities defined by +the library. + + +File: libtextstyle.info, Node: Link options, Next: Command-line options, Prev: Include files, Up: The programmer's view + +3.3 Link options +================ + + The library to link with is called ‘libtextstyle’, with a +system-dependent suffix. You link with it though link options of the +form ‘-ltextstyle’ for a library installed in system locations, or +‘-LLIBDIR -ltextstyle’ for a static library installed in other +locations, or ‘-LLIBDIR -ltextstyle -Wl,-rpath,LIBDIR’ for a shared +library installed in other locations (assuming a GCC compatible compiler +and linker and no ‘libtool’), or ‘-LLIBDIR -ltextstyle -RLIBDIR’ for a +shared library installed in other locations (with ‘libtool’). +Additionally, the link options may need to include the dependencies: +‘-lm’, and ‘-lncurses’ or (on NetBSD) ‘-ltermcap’ or (on AIX) +‘-lxcurses’ or (on HP-UX) ‘-lcurses’, and on some systems also +‘-liconv’. + + It is a bit complicated to determine the right link options in a +portable way. Therefore an Autoconf macro is provided in the file +‘libtextstyle.m4’ in Gnulib, that makes this task easier. Assuming the +build system of your package is based on GNU Autoconf, you invoke it +through ‘gl_LIBTEXTSTYLE’. It searches for an installed ‘libtextstyle’. +If found, it sets and AC_SUBSTs ‘HAVE_LIBTEXTSTYLE=yes’ and the +‘LIBTEXTSTYLE’ and ‘LTLIBTEXTSTYLE’ variables, and augments the +‘CPPFLAGS’ variable, and #defines ‘HAVE_LIBTEXTSTYLE’ to 1. Otherwise, +it sets and AC_SUBSTs ‘HAVE_LIBTEXTSTYLE=no’ and ‘LIBTEXTSTYLE’ and +‘LTLIBTEXTSTYLE’ to empty. In link commands that use ‘libtool’, use +‘LTLIBTEXTSTYLE’; in link commands that don't use ‘libtool’, use +‘LIBTEXTSTYLE’. + + If you use GNU Automake, the proper place to use the link options is +‘PROGRAM_LDADD’ for programs and ‘LIBRARY_LIBADD’ for libraries. + + +File: libtextstyle.info, Node: Command-line options, Next: The output stream hierarchy, Prev: Link options, Up: The programmer's view + +3.4 Command-line options +======================== + + While you are free to provide any command-line option to enable the +styling of the output, it is good if different GNU programs use the same +command-line options for this purpose. These options are described in +the sections *note The --color option:: and *note The --style option::. +To achieve this, use the following API (declared in ‘’): + + -- Variable: bool color_test_mode + True if a ‘--color’ option with value ‘test’ has been seen. + + -- Variable: enum color_option color_mode + Stores the value of the ‘--color’ option. + + -- Variable: const char * style_file_name + Stores the value of the ‘--style’ option. + + Note: These variables, like any variables exported from shared +libraries, can only be used in executable code. You _cannot_ portably +use their address in initializers of global or static variables. This +is a restriction that is imposed by the Windows, Cygwin, and Android +platforms. + + -- Function: bool handle_color_option (const char *OPTION) + You invoke this function when, during argument parsing, you have + encountered a ‘--color’ or ‘--color=...’ option. The return value + is an error indicator: ‘true’ means an invalid option. + + -- Function: void handle_style_option (const char *OPTION) + You invoke this function when, during argument parsing, you have + encountered a ‘--style’ or ‘--style=...’ option. + + -- Function: void print_color_test (void) + Prints a color test page. You invoke this function after argument + parsing, when the ‘color_test_mode’ variable is true. + + -- Function: void style_file_prepare (const char *STYLE_FILE_ENVVAR, + const char *STYLESDIR_ENVVAR, + const char *STYLESDIR_AFTER_INSTALL, + const char *DEFAULT_STYLE_FILE) + Assigns a default value to ‘style_file_name’ if necessary. You + invoke this function after argument parsing, when ‘color_test_mode’ + is false. + + ‘STYLE_FILE_ENVVAR’ is an environment variable that, when set to a + non-empty value, specifies the style file to use. This environment + variable is meant to be set by the user. + + ‘STYLESDIR_ENVVAR’ is an environment variable that, when set to a + non-empty value, specifies the directory with the style files, or + ‘NULL’. This is necessary for running the testsuite before ‘make + install’. + + ‘STYLESDIR_AFTER_INSTALL’ is the directory with the style files + after ‘make install’. + + ‘DEFAULT_STYLE_FILE’ is the file name of the default style file, + relative to STYLESDIR. + + +File: libtextstyle.info, Node: The output stream hierarchy, Next: Debugging the styling code, Prev: Command-line options, Up: The programmer's view + +3.5 The output stream hierarchy +=============================== + + There are various classes of output streams, some of them with +styling support. These "classes" are defined in an object-oriented +programming style that resembles C++ or Java, but are actually +implemented in C with a little bit of object orientation syntax. These +definitions are preprocessed down to C. As a consequence, GNU +libtextstyle is a C library and does not need to link with the C++ +standard library. + + All these classes are declared in ‘’. + + The base output stream type is ‘ostream_t’. It is a pointer type to +a (hidden) implementation type. Similarly for the subclasses. + + When we say that ‘some_ostream_t’ is a subclass of ‘ostream_t’, what +we mean is: + • Every ‘some_ostream_t’ object can be converted to an ‘ostream_t’, + by virtue of a simple assignment. No cast is needed. + • The opposite conversion, from ‘ostream_t’ to ‘some_ostream_t’, can + also be performed, provided that the object is actually an instance + of ‘some_ostream_t’. You can test whether an object is an instance + of ‘some_ostream_t’ by invoking the method ‘bool + is_instance_of_some_ostream (ostream_t stream)’. + • Every method ‘ostream_FOOBAR’ exists also as a method + ‘some_ostream_FOOBAR’ with compatible argument types and a + compatible return type. + +* Menu: + +* The ostream class:: +* The styled_ostream class:: +* ostream subclasses without styling:: +* styled_ostream subclasses:: +* Accessors:: + + +File: libtextstyle.info, Node: The ostream class, Next: The styled_ostream class, Up: The output stream hierarchy + +3.5.1 The abstract ‘ostream’ class +---------------------------------- + + The base output stream type is ‘ostream_t’. + + It has the following methods: + + -- Function: void ostream_write_mem (ostream_t STREAM, + const void *DATA, size_t LEN) + Writes a sequence of bytes to a stream. + + -- Function: void ostream_write_str (ostream_t STREAM, + const char *STRING) + Writes a string's contents to a stream. + + -- Function: ptrdiff_t ostream_printf (ostream_t STREAM, + const char *FORMAT, ...) + -- Function: ptrdiff_t ostream_vprintf (ostream_t STREAM, + const char *FORMAT, va_list args) + Writes formatted output to a stream. + + These functions return the size of formatted output, or a negative + value in case of an error. + + -- Function: void ostream_flush (ostream_t STREAM, + ostream_flush_scope_t SCOPE) + Brings buffered data to its destination. + + -- Function: void ostream_free (ostream_t STREAM) + Closes and frees a stream. + + +File: libtextstyle.info, Node: The styled_ostream class, Next: ostream subclasses without styling, Prev: The ostream class, Up: The output stream hierarchy + +3.5.2 The abstract ‘styled_ostream’ class +----------------------------------------- + + The type for a styled output stream is ‘styled_ostream_t’. It is a +subclass of ‘ostream_t’ that adds the following methods: + + -- Function: void styled_ostream_begin_use_class + (styled_ostream_t STREAM, const char *CLASSNAME) + Starts a run of text belonging to ‘CLASSNAME’. The ‘CLASSNAME’ is + the name of a CSS class. It can be chosen arbitrarily and + customized through the CSS file. + + -- Function: void styled_ostream_end_use_class + (styled_ostream_t STREAM, const char *CLASSNAME) + Ends a run of text belonging to ‘CLASSNAME’. The + ‘styled_ostream_begin_use_class’ / ‘styled_ostream_end_use_class’ + calls must match properly. + + -- Function: const char * styled_ostream_get_hyperlink_ref + (styled_ostream_t STREAM) + Returns the referred URL of the currently set hyperlink, or ‘NULL’ + if no hyperlink attribute is currently set. + + Note: The returned string is only valid up to the next invocation + of ‘styled_ostream_set_hyperlink’. + + -- Function: const char * styled_ostream_get_hyperlink_id + (styled_ostream_t STREAM) + Returns the id of the currently set hyperlink, or ‘NULL’ if no + hyperlink attribute is currently set. + + Note: The returned string is only valid up to the next invocation + of ‘styled_ostream_set_hyperlink’. + + -- Function: void styled_ostream_set_hyperlink + (styled_ostream_t STREAM, const char *REF, const char *ID) + Sets or removes a hyperlink attribute. + + To set a hyperlink attribute, pass a non-‘NULL’ REF. REF is an + URL; it should be at most 2083 bytes long. Non-ASCII characters + should be URI-escaped (using the %nn syntax). ID is an optional + identifier. On terminal output, multiple hyperlinks with the same + ID will be highlighted together. If specified, ID should be at + most 250 bytes long. + + To remove a hyperlink attribute, pass ‘NULL’ for REF and ID. + + Hyperlinks don't nest. That is, a hyperlink attribute is enabled + only up to the next invocation of ‘styled_ostream_set_hyperlink’. + + -- Function: void styled_ostream_flush_to_current_style + (styled_ostream_t STREAM) + This function acts like ‘ostream_flush (STREAM, + FLUSH_THIS_STREAM)’, except that it leaves the destination with the + current text style enabled, instead of with the default text style. + + After calling this function, you can output strings without + newlines(!) to the underlying stream, and they will be rendered + like strings passed to ‘ostream_write_mem’, ‘ostream_write_str’, or + ‘ostream_printf’. + + +File: libtextstyle.info, Node: ostream subclasses without styling, Next: styled_ostream subclasses, Prev: The styled_ostream class, Up: The output stream hierarchy + +3.5.3 Concrete ostream subclasses without styling +------------------------------------------------- + +* Menu: + +* The file_ostream class:: Output to a FILE stream. +* The fd_ostream class:: Output to a file descriptor. +* The term_ostream class:: Output to a terminal. +* The html_ostream class:: Output to an HTML file. +* The memory_ostream class:: Output to a memory buffer, +* The iconv_ostream class:: Output with character encoding conversion. + + +File: libtextstyle.info, Node: The file_ostream class, Next: The fd_ostream class, Up: ostream subclasses without styling + +3.5.3.1 The ‘file_ostream’ class +................................ + + The ‘file_ostream’ class supports output to an ‘’ ‘FILE’ +stream. Its type is ‘file_ostream_t’. It is a subclass of ‘ostream_t’ +that adds no methods. + + It can be instantiated through this function: + + -- Function: file_ostream_t file_ostream_create (FILE *FP) + Creates an output stream referring to ‘FP’. + + Note: The resulting stream must be closed before ‘FP’ can be + closed. + + +File: libtextstyle.info, Node: The fd_ostream class, Next: The term_ostream class, Prev: The file_ostream class, Up: ostream subclasses without styling + +3.5.3.2 The ‘fd_ostream’ class +.............................. + + The ‘file_ostream’ class supports output to a file descriptor. Its +type is ‘fd_ostream_t’. It is a subclass of ‘ostream_t’ that adds no +methods. + + It can be instantiated through this function: + + -- Function: fd_ostream_t fd_ostream_create (int FD, + const char *FILENAME, bool BUFFERED) + Creates an output stream referring to the file descriptor ‘FD’. + + ‘FILENAME’ is used only for error messages. + + Note: The resulting stream must be closed before ‘FD’ can be + closed. + + +File: libtextstyle.info, Node: The term_ostream class, Next: The html_ostream class, Prev: The fd_ostream class, Up: ostream subclasses without styling + +3.5.3.3 The ‘term_ostream’ class +................................ + + The ‘term_ostream’ class supports output to a file descriptor that is +connected to a terminal emulator or console. Its type is +‘term_ostream_t’. It is a subclass of ‘ostream_t’. + + It can be instantiated through this function: + + -- Function: term_ostream_t term_ostream_create (int FD, + const char *FILENAME, ttyctl_t TTY_CONTROL) + Creates an output stream referring to the file descriptor ‘FD’. + + ‘FILENAME’ is used only for error messages. + + ‘TTY_CONTROL’ specifies the amount of control to take over the + underlying tty. + + The resulting stream will be line-buffered. + + Note: The resulting stream must be closed before ‘FD’ can be + closed. + + The class adds the following methods: + + -- Function: term_color_t term_ostream_rgb_to_color + (term_ostream_t STREAM, int RED, int GREEN, int BLUE) + Converts an RGB value (‘RED’, ‘GREEN’, ‘BLUE’ in [0..255]) to a + color, valid for this stream only. + + -- Function: term_color_t term_ostream_get_color + (term_ostream_t STREAM) + -- Function: void term_ostream_set_color (term_ostream_t STREAM, + term_color_t COLOR) + Gets/sets the text color. + + -- Function: term_color_t term_ostream_get_bgcolor + (term_ostream_t STREAM) + -- Function: void term_ostream_set_bgcolor (term_ostream_t STREAM, + term_color_t COLOR) + Gets/sets the background color. + + -- Function: term_weight_t term_ostream_get_weight + (term_ostream_t STREAM) + -- Function: void term_ostream_set_weight (term_ostream_t STREAM, + term_weight_t WEIGHT) + Gets/sets the font weight. + + -- Function: term_posture_t term_ostream_get_posture + (term_ostream_t STREAM) + -- Function: void term_ostream_set_posture (term_ostream_t STREAM, + term_posture_t POSTURE) + Gets/sets the font posture. + + -- Function: term_underline_t term_ostream_get_underline + (term_ostream_t STREAM) + -- Function: void term_ostream_set_underline (term_ostream_t STREAM, + term_underline_t UNDERLINE) + Gets/sets the text underline decoration. + + -- Function: const char * term_ostream_get_hyperlink_ref + (term_ostream_t STREAM) + Returns the referred URL of the currently set hyperlink, or ‘NULL’ + if no hyperlink attribute is currently set. + + Note: The returned string is only valid up to the next invocation + of ‘term_ostream_set_hyperlink’. + + -- Function: const char * term_ostream_get_hyperlink_id + (term_ostream_t STREAM) + Returns the id of the currently set hyperlink, or ‘NULL’ if no + hyperlink attribute is currently set. + + Note: The returned string is only valid up to the next invocation + of ‘term_ostream_set_hyperlink’. + + -- Function: void term_ostream_set_hyperlink (term_ostream_t STREAM, + const char *REF, const char *ID) + Sets or removes a hyperlink attribute. + + To set a hyperlink attribute, pass a non-‘NULL’ REF. REF is an + URL; it should be at most 2083 bytes long. Non-ASCII characters + should be URI-escaped (using the %nn syntax). ID is an optional + identifier. Multiple hyperlinks with the same ID will be + highlighted together. If specified, ID should be at most 250 bytes + long. + + To remove a hyperlink attribute, pass ‘NULL’ for REF and ID. + + Hyperlinks don't nest. That is, a hyperlink attribute is enabled + only up to the next invocation of ‘styled_ostream_set_hyperlink’. + + -- Function: void term_ostream_flush_to_current_style + (term_ostream_t STREAM) + This function acts like ‘ostream_flush (STREAM, + FLUSH_THIS_STREAM)’, except that it leaves the terminal with the + current text attributes enabled, instead of with the default text + attributes. + + After calling this function, you can output strings without + newlines(!) to the underlying file descriptor, and they will be + rendered like strings passed to ‘ostream_write_mem’, + ‘ostream_write_str’, or ‘ostream_printf’. + + +File: libtextstyle.info, Node: The html_ostream class, Next: The memory_ostream class, Prev: The term_ostream class, Up: ostream subclasses without styling + +3.5.3.4 The ‘html_ostream’ class +................................ + + The ‘html_ostream’ class supports output to any destination, in HTML +syntax. Its type is ‘html_ostream_t’. It is a subclass of ‘ostream_t’. + + It can be instantiated through this function: + + -- Function: html_ostream_t html_ostream_create (ostream_t DESTINATION) + Creates an output stream that takes input in the UTF-8 encoding and + writes it in HTML form on ‘DESTINATION’. + + This stream produces a sequence of lines. The caller is + responsible for opening the ‘’ elements before and for + closing them after the use of this stream. + + Note: The resulting stream must be closed before ‘DESTINATION’ can + be closed. + + The class adds the following methods: + + -- Function: void html_ostream_begin_span (html_ostream_t STREAM, + const char *CLASSNAME) + Starts a ‘’ element. The ‘CLASSNAME’ is + the name of a CSS class. It can be chosen arbitrarily and + customized through the CSS file. + + -- Function: void html_ostream_end_span (html_ostream_t STREAM, + const char *CLASSNAME) + Ends a ‘’ element. + + The ‘html_ostream_begin_span’ / ‘html_ostream_end_span’ calls must + match properly. + + -- Function: const char * html_ostream_get_hyperlink_ref + (html_ostream_t STREAM) + Returns the referred URL of the currently set hyperlink, or ‘NULL’ + if no hyperlink attribute is currently set. + + Note: The returned string is only valid up to the next invocation + of ‘html_ostream_set_hyperlink_ref’. + + -- Function: void html_ostream_set_hyperlink_ref + (html_ostream_t STREAM, const char *REF) + Sets or removes a hyperlink attribute. + + To set a hyperlink attribute, pass a non-‘NULL’ REF. REF is an + URL; it should be at most 2083 bytes long. Non-ASCII characters + should be URI-escaped (using the %nn syntax). + + To remove a hyperlink attribute, pass ‘NULL’ for REF. + + Hyperlinks don't nest. That is, a hyperlink attribute is enabled + only up to the next invocation of ‘html_ostream_set_hyperlink_ref’. + + -- Function: void html_ostream_flush_to_current_style + (html_ostream_t STREAM) + This function acts like ‘ostream_flush (STREAM, + FLUSH_THIS_STREAM)’, except that it leaves the destination with the + current text style enabled, instead of with the default text style. + + After calling this function, you can output strings without + newlines(!) to the underlying stream, and they will be rendered + like strings passed to ‘ostream_write_mem’, ‘ostream_write_str’, or + ‘ostream_printf’. + + +File: libtextstyle.info, Node: The memory_ostream class, Next: The iconv_ostream class, Prev: The html_ostream class, Up: ostream subclasses without styling + +3.5.3.5 The ‘memory_ostream’ class +.................................. + + The ‘memory_ostream’ class supports output to an in-memory buffer. +Its type is ‘memory_ostream_t’. It is a subclass of ‘ostream_t’. + + It can be instantiated through this function: + + -- Function: memory_ostream_t memory_ostream_create (void) + Creates an output stream that accumulates the output in a memory + buffer. + + The class adds the following method: + + -- Function: void memory_ostream_contents (memory_ostream_t STREAM, + const void **BUFP, size_t *BUFLENP) + Returns a pointer to the output accumulated so far and its size. + It stores them in ‘*BUFP’ and ‘*BUFLENP’, respectively. + + Note: These two return values become invalid when more output is + done to the stream or when the stream is freed. + + +File: libtextstyle.info, Node: The iconv_ostream class, Prev: The memory_ostream class, Up: ostream subclasses without styling + +3.5.3.6 The ‘iconv_ostream’ class +................................. + + The ‘iconv_ostream’ class supports output to any destination. Its +type is ‘iconv_ostream_t’. It is a subclass of ‘ostream_t’ that adds no +methods. + + It can be instantiated through this function: + + -- Function: iconv_ostream_t iconv_ostream_create + (const char *FROM_ENCODING, const char *TO_ENCODING, + ostream_t DESTINATION) + Creates an output stream that converts from ‘FROM_ENCODING’ to + ‘TO_ENCODING’, writing the result to ‘DESTINATION’. + + Note: The resulting stream must be closed before ‘DESTINATION’ can + be closed. + + +File: libtextstyle.info, Node: styled_ostream subclasses, Next: Accessors, Prev: ostream subclasses without styling, Up: The output stream hierarchy + +3.5.4 Concrete ‘styled_ostream’ subclasses +------------------------------------------ + +* Menu: + +* The term_styled_ostream class:: Styled output to a terminal. +* The html_styled_ostream class:: Styled output to an HTML file. +* The noop_styled_ostream class:: No-op styling. + + +File: libtextstyle.info, Node: The term_styled_ostream class, Next: The html_styled_ostream class, Up: styled_ostream subclasses + +3.5.4.1 The ‘term_styled_ostream’ class +....................................... + + The ‘term_styled_ostream’ class supports styled output to a file +descriptor that is connected to a terminal emulator or console. Its +type is ‘term_styled_ostream_t’. It is a subclass of +‘styled_ostream_t’. + + It can be instantiated through this function: + + -- Function: term_styled_ostream_t term_styled_ostream_create (int FD, + const char *FILENAME, ttyctl_t TTY_CONTROL, + const char *CSS_FILENAME) + Creates an output stream referring to the file descriptor ‘FD’, + styled with the file ‘CSS_FILENAME’. + + ‘FILENAME’ is used only for error messages. + + ‘TTY_CONTROL’ specifies the amount of control to take over the + underlying tty. + + Note: The resulting stream must be closed before ‘FD’ can be + closed. + + Returns ‘NULL’ upon failure. + + The following is a variant of this function. Upon failure, it does +not return ‘NULL’; instead, it returns a styled ‘fd_stream’ on which the +styling operations exist but are no-ops. + + -- Function: styled_ostream_t styled_ostream_create (int FD, + const char *FILENAME, ttyctl_t TTY_CONTROL, + const char *CSS_FILENAME) + Creates an output stream referring to the file descriptor ‘FD’, + styled with the file ‘CSS_FILENAME’ if possible. + + ‘FILENAME’ is used only for error messages. + + ‘TTY_CONTROL’ specifies the amount of control to take over the + underlying tty. + + Note: The resulting stream must be closed before ‘FD’ can be + closed. + + +File: libtextstyle.info, Node: The html_styled_ostream class, Next: The noop_styled_ostream class, Prev: The term_styled_ostream class, Up: styled_ostream subclasses + +3.5.4.2 The ‘html_styled_ostream’ class +....................................... + + The ‘html_styled_ostream’ class supports styled output to any +destination, in HTML syntax. Its type is ‘html_styled_ostream_t’. It +is a subclass of ‘styled_ostream_t’. + + It can be instantiated through this function: + + -- Function: html_styled_ostream_t html_styled_ostream_create + (ostream_t DESTINATION, const char *CSS_FILENAME) + Creates an output stream that takes input in the UTF-8 encoding and + writes it in HTML form on ‘DESTINATION’, styled with the file + ‘CSS_FILENAME’. + + Note: The resulting stream must be closed before ‘DESTINATION’ can + be closed. + + +File: libtextstyle.info, Node: The noop_styled_ostream class, Prev: The html_styled_ostream class, Up: styled_ostream subclasses + +3.5.4.3 The ‘noop_styled_ostream’ class +....................................... + + The ‘noop_styled_ostream’ class supports the styled output operations +to any destination. The text is output to the given destination; the +styling operations, however, do nothing. Its type is +‘noop_styled_ostream_t’. It is a subclass of ‘styled_ostream_t’. + + It can be instantiated through this function: + + -- Function: noop_styled_ostream_t noop_styled_ostream_create + (ostream_t DESTINATION, bool PASS_OWNERSHIP) + Creates an output stream that delegates to ‘DESTINATION’ and that + supports the styling operations as no-ops. + + If ‘PASS_OWNERSHIP’ is ‘true’, closing the resulting stream will + automatically close the ‘DESTINATION’. + + Note: If ‘PASS_OWNERSHIP’ is ‘false’, the resulting stream must be + closed before ‘DESTINATION’ can be closed. + + +File: libtextstyle.info, Node: Accessors, Prev: styled_ostream subclasses, Up: The output stream hierarchy + +3.5.5 Accessor functions +------------------------ + + The various concrete stream classes have methods that allow you to +retrieve the arguments passed to the respective constructor function. + + Note: While these methods allow you to retrieve the underlying +destination stream of various kinds of stream, it is not recommended to +operate on both the stream and its underlying destination stream at the +same time. Doing so can lead to undesired interactions between the two +streams. + + The ‘file_ostream’ class has this accessor method: + + -- Function: FILE * file_ostream_get_stdio_stream + (file_ostream_t STREAM) + + The ‘fd_ostream’ class has these accessor methods: + + -- Function: int fd_ostream_get_descriptor (fd_ostream_t STREAM) + -- Function: const char * fd_ostream_get_filename (fd_ostream_t STREAM) + -- Function: bool fd_ostream_is_buffered (fd_ostream_t STREAM) + + The ‘term_ostream’ class has these accessor methods: + + -- Function: int term_ostream_get_descriptor (term_ostream_t STREAM) + -- Function: const char * term_ostream_get_filename + (term_ostream_t STREAM) + -- Function: ttyctl_t term_ostream_get_tty_control + (term_ostream_t STREAM) + -- Function: ttyctl_t term_ostream_get_effective_tty_control + (term_ostream_t STREAM) + Returns the effective tty control of the stream (not + ‘TTYCTL_AUTO’). + + The ‘iconv_ostream’ class has these accessor methods: + + -- Function: const char * iconv_ostream_get_from_encoding + (iconv_ostream_t STREAM) + -- Function: const char * iconv_ostream_get_to_encoding + (iconv_ostream_t STREAM) + -- Function: ostream_t iconv_ostream_get_destination + (iconv_ostream_t STREAM) + + The ‘html_ostream’ class has this accessor method: + + -- Function: ostream_t html_ostream_get_destination + (html_ostream_t STREAM) + + The ‘term_styled_ostream’ class has these accessor methods: + + -- Function: term_ostream_t term_styled_ostream_get_destination + (term_styled_ostream_t STREAM) + -- Function: const char * term_styled_ostream_get_css_filename + (term_styled_ostream_t STREAM) + + The ‘html_styled_ostream’ class has these accessor methods: + + -- Function: ostream_t html_styled_ostream_get_destination + (html_styled_ostream_t STREAM) + -- Function: html_ostream_t html_styled_ostream_get_html_destination + (html_styled_ostream_t STREAM) + -- Function: const char * html_styled_ostream_get_css_filename + (html_styled_ostream_t STREAM) + + The ‘noop_styled_ostream’ class has these accessor methods: + + -- Function: ostream_t noop_styled_ostream_get_destination + (noop_styled_ostream_t STREAM) + -- Function: bool noop_styled_ostream_is_owning_destination + (noop_styled_ostream_t STREAM) + + +File: libtextstyle.info, Node: Debugging the styling code, Next: What to document, Prev: The output stream hierarchy, Up: The programmer's view + +3.6 Debugging the text styling support +====================================== + + If you want to understand which output of your program is associated +with which CSS classes, the simplest way is as follows: + + 1. Run the program with the command-line option ‘--color=html’, + redirecting the output to a file. + 2. Then inspect this output. Text regions associated with a CSS class + are surrounded by ‘’...‘’. + + +File: libtextstyle.info, Node: What to document, Prev: Debugging the styling code, Up: The programmer's view + +3.7 Documenting the text styling support +======================================== + + To make the text styling support available to the end user of your +package, the following need to be documented: + • The command-line options. This typically needs to be done in + several places: in the ‘--help’ output, in the ‘man’ pages (if + present), and in the documentation. + • Which programs support ‘--color=test’? + • The list of CSS classes and their meaning. This is necessary, so + that the user can create their own style file; the CSS classes are + part of the selectors in the CSS rules. + • The location of the default style file. This is a convenience, so + that the user, when creating their own style file, can start from + the default one. + • The environment variable, called ‘STYLE_FILE_ENVVAR’ above, that, + when set to a non-empty value, specifies the style file to use. + + +File: libtextstyle.info, Node: Licenses, Next: Function Index, Prev: The programmer's view, Up: Top + +Appendix A Licenses +******************* + + The files of this package are covered by the licenses indicated in +each particular file or directory. Here is a summary: + + • The ‘libtextstyle’ library and the example programs are covered by + the GNU General Public License (GPL). A copy of the license is + included in *note GNU GPL::. + + • 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 included in *note GNU FDL::. + 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 3 of the License, or (at your option) any + later version published by the Free Software Foundation (FSF). A + copy of the license is included in *note GNU GPL::. + +* Menu: + +* GNU GPL:: GNU General Public License +* GNU FDL:: GNU Free Documentation License + + +File: libtextstyle.info, Node: GNU GPL, Next: GNU FDL, Up: Licenses + +A.1 GNU GENERAL PUBLIC LICENSE +============================== + + Version 3, 29 June 2007 + + Copyright © 2007 Free Software Foundation, Inc. + + 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 . + + 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 . + + 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 . + + +File: libtextstyle.info, Node: GNU FDL, Prev: GNU GPL, Up: Licenses + +A.2 GNU Free Documentation License +================================== + + Version 1.3, 3 November 2008 + + Copyright © 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. + + + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + 0. PREAMBLE + + The purpose of this License is to make a manual, textbook, or other + functional and useful document “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. + + 1. 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 + ASCII without markup, Texinfo input format, LaTeX input format, + SGML or XML using a publicly available DTD, and standard-conforming + simple HTML, PostScript or PDF designed for human modification. + Examples of transparent image formats include PNG, XCF and JPG. + Opaque formats include proprietary formats that can be read and + edited only by proprietary word processors, SGML or XML for which + the DTD and/or processing tools are not generally available, and + the machine-generated HTML, PostScript or 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. + + The "publisher" means any person or entity that distributes copies + of the Document to the public. + + 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. + + 2. 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. + + 3. 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. + + 4. 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: + + A. 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. + + B. 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. + + C. State on the Title page the name of the publisher of the + Modified Version, as the publisher. + + D. Preserve all the copyright notices of the Document. + + E. Add an appropriate copyright notice for your modifications + adjacent to the other copyright notices. + + F. 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. + + G. Preserve in that license notice the full lists of Invariant + Sections and required Cover Texts given in the Document's + license notice. + + H. Include an unaltered copy of this License. + + I. 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. + + J. 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. + + K. 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. + + L. 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. + + M. Delete any section Entitled "Endorsements". Such a section + may not be included in the Modified Version. + + N. Do not retitle any existing section to be Entitled + "Endorsements" or to conflict in title with any Invariant + Section. + + O. Preserve any Warranty Disclaimers. + + 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. + + 5. 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." + + 6. 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. + + 7. 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. + + 8. 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. + + 9. TERMINATION + + You may not copy, modify, sublicense, or distribute the Document + except as expressly provided under this License. Any attempt + otherwise to copy, modify, sublicense, or distribute it is void, + and will automatically terminate your rights under this License. + + 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, receipt of a copy of some or all of the + same material does not give you any rights to use it. + + 10. 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 + . + + 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. If the Document specifies that a proxy can + decide which future versions of this License can be used, that + proxy's public statement of acceptance of a version permanently + authorizes you to choose that version for the Document. + + 11. RELICENSING + + "Massive Multiauthor Collaboration Site" (or "MMC Site") means any + World Wide Web server that publishes copyrightable works and also + provides prominent facilities for anybody to edit those works. A + public wiki that anybody can edit is an example of such a server. + A "Massive Multiauthor Collaboration" (or "MMC") contained in the + site means any set of copyrightable works thus published on the MMC + site. + + "CC-BY-SA" means the Creative Commons Attribution-Share Alike 3.0 + license published by Creative Commons Corporation, a not-for-profit + corporation with a principal place of business in San Francisco, + California, as well as future copyleft versions of that license + published by that same organization. + + "Incorporate" means to publish or republish a Document, in whole or + in part, as part of another Document. + + An MMC is "eligible for relicensing" if it is licensed under this + License, and if all works that were first published under this + License somewhere other than this MMC, and subsequently + incorporated in whole or in part into the MMC, (1) had no cover + texts or invariant sections, and (2) were thus incorporated prior + to November 1, 2008. + + The operator of an MMC Site may republish an MMC contained in the + site under CC-BY-SA on the same site at any time before August 1, + 2009, provided the MMC is eligible for relicensing. + +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: + + Copyright (C) YEAR YOUR NAME. + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.3 + 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''. + + If you have Invariant Sections, Front-Cover Texts and Back-Cover +Texts, replace the "with...Texts." line with this: + + with the Invariant Sections being LIST THEIR TITLES, with + the Front-Cover Texts being LIST, and with the Back-Cover Texts + being LIST. + + 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. + + +File: libtextstyle.info, Node: Function Index, Next: Variable Index, Prev: Licenses, Up: Top + +Function Index +************** + +[index] +* Menu: + +* fd_ostream_create: The fd_ostream class. (line 12) +* fd_ostream_get_descriptor: Accessors. (line 22) +* fd_ostream_get_filename: Accessors. (line 23) +* fd_ostream_is_buffered: Accessors. (line 24) +* file_ostream_create: The file_ostream class. + (line 12) +* file_ostream_get_stdio_stream: Accessors. (line 17) +* handle_color_option: Command-line options. (line 27) +* handle_style_option: Command-line options. (line 32) +* html_ostream_begin_span: The html_ostream class. + (line 24) +* html_ostream_create: The html_ostream class. + (line 11) +* html_ostream_end_span: The html_ostream class. + (line 30) +* html_ostream_flush_to_current_style: The html_ostream class. + (line 58) +* html_ostream_get_destination: Accessors. (line 49) +* html_ostream_get_hyperlink_ref: The html_ostream class. + (line 37) +* html_ostream_set_hyperlink_ref: The html_ostream class. + (line 45) +* html_styled_ostream_create: The html_styled_ostream class. + (line 12) +* html_styled_ostream_get_css_filename: Accessors. (line 65) +* html_styled_ostream_get_destination: Accessors. (line 61) +* html_styled_ostream_get_html_destination: Accessors. (line 63) +* iconv_ostream_create: The iconv_ostream class. + (line 12) +* iconv_ostream_get_destination: Accessors. (line 44) +* iconv_ostream_get_from_encoding: Accessors. (line 40) +* iconv_ostream_get_to_encoding: Accessors. (line 42) +* is_instance_of_fd_ostream: The output stream hierarchy. + (line 27) +* is_instance_of_file_ostream: The output stream hierarchy. + (line 27) +* is_instance_of_html_ostream: The output stream hierarchy. + (line 27) +* is_instance_of_html_styled_ostream: The output stream hierarchy. + (line 27) +* is_instance_of_iconv_ostream: The output stream hierarchy. + (line 27) +* is_instance_of_memory_ostream: The output stream hierarchy. + (line 27) +* is_instance_of_noop_styled_ostream: The output stream hierarchy. + (line 27) +* is_instance_of_styled_ostream: The output stream hierarchy. + (line 27) +* is_instance_of_term_ostream: The output stream hierarchy. + (line 27) +* is_instance_of_term_styled_ostream: The output stream hierarchy. + (line 27) +* memory_ostream_contents: The memory_ostream class. + (line 17) +* memory_ostream_create: The memory_ostream class. + (line 11) +* noop_styled_ostream_create: The noop_styled_ostream class. + (line 13) +* noop_styled_ostream_get_destination: Accessors. (line 70) +* noop_styled_ostream_is_owning_destination: Accessors. (line 72) +* ostream_flush: The ostream class. (line 27) +* ostream_free: The ostream class. (line 31) +* ostream_printf: The ostream class. (line 18) +* ostream_vprintf: The ostream class. (line 20) +* ostream_write_mem: The ostream class. (line 10) +* ostream_write_str: The ostream class. (line 14) +* print_color_test: Command-line options. (line 36) +* style_file_prepare: Command-line options. (line 40) +* styled_ostream_begin_use_class: The styled_ostream class. + (line 9) +* styled_ostream_create: The term_styled_ostream class. + (line 33) +* styled_ostream_end_use_class: The styled_ostream class. + (line 15) +* styled_ostream_flush_to_current_style: The styled_ostream class. + (line 53) +* styled_ostream_get_hyperlink_id: The styled_ostream class. + (line 29) +* styled_ostream_get_hyperlink_ref: The styled_ostream class. + (line 21) +* styled_ostream_set_hyperlink: The styled_ostream class. + (line 37) +* term_ostream_create: The term_ostream class. + (line 12) +* term_ostream_flush_to_current_style: The term_ostream class. + (line 95) +* term_ostream_get_bgcolor: The term_ostream class. + (line 39) +* term_ostream_get_color: The term_ostream class. + (line 33) +* term_ostream_get_descriptor: Accessors. (line 28) +* term_ostream_get_effective_tty_control: Accessors. (line 33) +* term_ostream_get_filename: Accessors. (line 29) +* term_ostream_get_hyperlink_id: The term_ostream class. + (line 71) +* term_ostream_get_hyperlink_ref: The term_ostream class. + (line 63) +* term_ostream_get_posture: The term_ostream class. + (line 51) +* term_ostream_get_tty_control: Accessors. (line 31) +* term_ostream_get_underline: The term_ostream class. + (line 57) +* term_ostream_get_weight: The term_ostream class. + (line 45) +* term_ostream_rgb_to_color: The term_ostream class. + (line 28) +* term_ostream_set_bgcolor: The term_ostream class. + (line 41) +* term_ostream_set_color: The term_ostream class. + (line 35) +* term_ostream_set_hyperlink: The term_ostream class. + (line 79) +* term_ostream_set_posture: The term_ostream class. + (line 53) +* term_ostream_set_underline: The term_ostream class. + (line 59) +* term_ostream_set_weight: The term_ostream class. + (line 47) +* term_styled_ostream_create: The term_styled_ostream class. + (line 13) +* term_styled_ostream_get_css_filename: Accessors. (line 56) +* term_styled_ostream_get_destination: Accessors. (line 54) + + +File: libtextstyle.info, Node: Variable Index, Next: Index, Prev: Function Index, Up: Top + +Variable Index +************** + +[index] +* Menu: + +* color_mode: Command-line options. (line 15) +* color_test_mode: Command-line options. (line 12) +* NO_COLOR, environment variable: The NO_COLOR variable. + (line 6) +* NO_TERM_HYPERLINKS, environment variable: The NO_TERM_HYPERLINKS variable. + (line 6) +* style_file_name: Command-line options. (line 18) +* TERM, environment variable: The TERM variable. (line 6) + + +File: libtextstyle.info, Node: Index, Prev: Variable Index, Up: Top + +General Index +************* + +[index] +* Menu: + +* --color option: The --color option. (line 6) +* --style option: The --style option. (line 6) +* : Include files. (line 6) +* Debugging: Debugging style files. (line 6) +* Debugging <1>: Debugging the styling code. + (line 6) +* FDL, GNU Free Documentation License: GNU FDL. (line 6) +* GPL, GNU General Public License: GNU GPL. (line 6) +* Include file: Include files. (line 6) +* License, GNU FDL: GNU FDL. (line 6) +* License, GNU GPL: GNU GPL. (line 6) +* Licenses: Licenses. (line 6) + + + +Tag Table: +Node: Top1342 +Node: Introduction1751 +Node: Style definitions2425 +Node: Built-in versus separate styling5107 +Node: The user's view6297 +Node: The TERM variable7317 +Node: Terminal emulators8467 +Node: Consoles10910 +Node: The NO_COLOR variable11301 +Node: The NO_TERM_HYPERLINKS variable11904 +Node: Emacs12638 +Node: The --color option13016 +Node: The --style option15029 +Node: Style rules15868 +Node: Debugging style files18773 +Node: The programmer's view19791 +Node: Basic use21051 +Node: Hyperlinks22559 +Node: Include files23893 +Node: Link options24135 +Node: Command-line options26064 +Node: The output stream hierarchy28863 +Node: The ostream class30586 +Node: The styled_ostream class31707 +Node: ostream subclasses without styling34633 +Node: The file_ostream class35277 +Node: The fd_ostream class35908 +Node: The term_ostream class36660 +Node: The html_ostream class40956 +Node: The memory_ostream class43878 +Node: The iconv_ostream class44880 +Node: styled_ostream subclasses45679 +Node: The term_styled_ostream class46116 +Node: The html_styled_ostream class47873 +Node: The noop_styled_ostream class48753 +Node: Accessors49801 +Node: Debugging the styling code52713 +Node: What to document53326 +Node: Licenses54380 +Node: GNU GPL55981 +Node: GNU FDL93526 +Node: Function Index118635 +Node: Variable Index127421 +Node: Index128150 + +End Tag Table + + +Local Variables: +coding: utf-8 +End: diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/ast/LC_MESSAGES/gettext-runtime.mo b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/ast/LC_MESSAGES/gettext-runtime.mo new file mode 100644 index 0000000000000000000000000000000000000000..1c72b2b1ec18ea18883ed540c850c50a4665c873 Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/ast/LC_MESSAGES/gettext-runtime.mo differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/be/LC_MESSAGES/gettext-runtime.mo b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/be/LC_MESSAGES/gettext-runtime.mo new file mode 100644 index 0000000000000000000000000000000000000000..7dc0fad9654f97b4d115b93a030cd88a8febdd25 Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/be/LC_MESSAGES/gettext-runtime.mo differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/be/LC_MESSAGES/gettext-tools.mo b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/be/LC_MESSAGES/gettext-tools.mo new file mode 100644 index 0000000000000000000000000000000000000000..fe4de271e1e3cdd4d3a9ccbfd271bc10c09f7dff Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/be/LC_MESSAGES/gettext-tools.mo differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/bg/LC_MESSAGES/gettext-runtime.mo b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/bg/LC_MESSAGES/gettext-runtime.mo new file mode 100644 index 0000000000000000000000000000000000000000..c9f439598855256d2805486168a70e0afd846699 Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/bg/LC_MESSAGES/gettext-runtime.mo differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/ca/LC_MESSAGES/gettext-runtime.mo b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/ca/LC_MESSAGES/gettext-runtime.mo new file mode 100644 index 0000000000000000000000000000000000000000..86b5856216cac00166c446da3b8b4fc6c9c8e4c4 Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/ca/LC_MESSAGES/gettext-runtime.mo differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/cs/LC_MESSAGES/gettext-runtime.mo b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/cs/LC_MESSAGES/gettext-runtime.mo new file mode 100644 index 0000000000000000000000000000000000000000..4a2c88760aa5fe4ad29e805f2796f5e99cf9ae38 Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/cs/LC_MESSAGES/gettext-runtime.mo differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/cs/LC_MESSAGES/gettext-tools.mo b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/cs/LC_MESSAGES/gettext-tools.mo new file mode 100644 index 0000000000000000000000000000000000000000..c3295bf6062bc7e9ef11a36260cff6b648dace1e Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/cs/LC_MESSAGES/gettext-tools.mo differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/da/LC_MESSAGES/gettext-runtime.mo b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/da/LC_MESSAGES/gettext-runtime.mo new file mode 100644 index 0000000000000000000000000000000000000000..98fe40821a84e614870e99e0227d87a8485f6c10 Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/da/LC_MESSAGES/gettext-runtime.mo differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/da/LC_MESSAGES/gettext-tools.mo b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/da/LC_MESSAGES/gettext-tools.mo new file mode 100644 index 0000000000000000000000000000000000000000..d0490c2b8ffbead2800d5d9a917e4f447771a110 Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/da/LC_MESSAGES/gettext-tools.mo differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/de/LC_MESSAGES/gettext-runtime.mo b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/de/LC_MESSAGES/gettext-runtime.mo new file mode 100644 index 0000000000000000000000000000000000000000..57301f6da7e6212bb5aa9c23ee65841f600d9f41 Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/de/LC_MESSAGES/gettext-runtime.mo differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/el/LC_MESSAGES/gettext-runtime.mo b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/el/LC_MESSAGES/gettext-runtime.mo new file mode 100644 index 0000000000000000000000000000000000000000..485e44a7c70b1acbe88c6f0524dd6e385ed39a85 Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/el/LC_MESSAGES/gettext-runtime.mo differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/el/LC_MESSAGES/gettext-tools.mo b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/el/LC_MESSAGES/gettext-tools.mo new file mode 100644 index 0000000000000000000000000000000000000000..050d175b68fabe128f9d163ccc036b13ca739a0c Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/el/LC_MESSAGES/gettext-tools.mo differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/en@boldquot/LC_MESSAGES/gettext-runtime.mo b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/en@boldquot/LC_MESSAGES/gettext-runtime.mo new file mode 100644 index 0000000000000000000000000000000000000000..12596032614ed73e93ac9ae6a97e54d87a607654 Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/en@boldquot/LC_MESSAGES/gettext-runtime.mo differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/en@quot/LC_MESSAGES/gettext-runtime.mo b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/en@quot/LC_MESSAGES/gettext-runtime.mo new file mode 100644 index 0000000000000000000000000000000000000000..7749743fea212c85051ea4d15fd5bd2175f8c9d3 Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/en@quot/LC_MESSAGES/gettext-runtime.mo differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/eo/LC_MESSAGES/gettext-runtime.mo b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/eo/LC_MESSAGES/gettext-runtime.mo new file mode 100644 index 0000000000000000000000000000000000000000..b704056c0cb0e80045b271aa0ee0830886cd10f3 Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/eo/LC_MESSAGES/gettext-runtime.mo differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/es/LC_MESSAGES/gettext-runtime.mo b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/es/LC_MESSAGES/gettext-runtime.mo new file mode 100644 index 0000000000000000000000000000000000000000..7c476ad570d624c0c2fd76c52dbc4cd29d2e9000 Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/es/LC_MESSAGES/gettext-runtime.mo differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/et/LC_MESSAGES/gettext-runtime.mo b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/et/LC_MESSAGES/gettext-runtime.mo new file mode 100644 index 0000000000000000000000000000000000000000..420b6624e537fab99d6e6519e21347cda160f1e7 Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/et/LC_MESSAGES/gettext-runtime.mo differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/et/LC_MESSAGES/gettext-tools.mo b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/et/LC_MESSAGES/gettext-tools.mo new file mode 100644 index 0000000000000000000000000000000000000000..44a0bf201e7fda363d0099bf37140ea3bdc9e5ad Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/et/LC_MESSAGES/gettext-tools.mo differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/eu/LC_MESSAGES/gettext-tools.mo b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/eu/LC_MESSAGES/gettext-tools.mo new file mode 100644 index 0000000000000000000000000000000000000000..12b95d1af10900bda92affd864606652bfc9115d Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/eu/LC_MESSAGES/gettext-tools.mo differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/fi/LC_MESSAGES/gettext-runtime.mo b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/fi/LC_MESSAGES/gettext-runtime.mo new file mode 100644 index 0000000000000000000000000000000000000000..23ca7184f5a6f09d7bfa85bb550be80acb8d0a1c Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/fi/LC_MESSAGES/gettext-runtime.mo differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/fr/LC_MESSAGES/gettext-runtime.mo b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/fr/LC_MESSAGES/gettext-runtime.mo new file mode 100644 index 0000000000000000000000000000000000000000..9946a456d18bd2e7459359839d7b6a7e8033623a Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/fr/LC_MESSAGES/gettext-runtime.mo differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/ga/LC_MESSAGES/gettext-runtime.mo b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/ga/LC_MESSAGES/gettext-runtime.mo new file mode 100644 index 0000000000000000000000000000000000000000..b1dc71a2ddb3096ef7c89a4396fb401e2689f8bb Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/ga/LC_MESSAGES/gettext-runtime.mo differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/gl/LC_MESSAGES/gettext-runtime.mo b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/gl/LC_MESSAGES/gettext-runtime.mo new file mode 100644 index 0000000000000000000000000000000000000000..5f8db3091deb89398d4672c103b0a5abda674a05 Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/gl/LC_MESSAGES/gettext-runtime.mo differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/gl/LC_MESSAGES/gettext-tools.mo b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/gl/LC_MESSAGES/gettext-tools.mo new file mode 100644 index 0000000000000000000000000000000000000000..0c98b4bc532b425470f72c1eccf13bea3d806ab3 Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/gl/LC_MESSAGES/gettext-tools.mo differ diff --git a/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/hr/LC_MESSAGES/gettext-runtime.mo b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/hr/LC_MESSAGES/gettext-runtime.mo new file mode 100644 index 0000000000000000000000000000000000000000..a777d364b3261db2f9144c0df5869e2e5b27647f Binary files /dev/null and b/miniconda3/pkgs/gettext-tools-0.25.1-h6a67909_0/share/locale/hr/LC_MESSAGES/gettext-runtime.mo differ