mirror of
git://git.sv.gnu.org/nano.git
synced 2024-12-28 13:19:48 +03:00
145bb6e01a
Fuzzy strings don't contribute anything to the translations that the users get to see. They are useful only for translators, but translators fetch or receive their PO files from the TP. For nano, fuzzy strings just bloat the distribution tarball.
23 lines
825 B
Plaintext
23 lines
825 B
Plaintext
# Makefile variables for PO directory in any package using GNU gettext.
|
|
|
|
# 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_ --keyword=P_:1,2
|
|
|
|
# This is the copyright holder that gets inserted into the header of the
|
|
# $(DOMAIN).pot file. Translators are expected to disclaim their copyright.
|
|
COPYRIGHT_HOLDER = Free Software Foundation, Inc.
|
|
|
|
# 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 =
|
|
|
|
# Don't do fuzzy matching when merging the PO files against the POT file.
|
|
MSGMERGE_OPTIONS = --no-fuzzy-matching
|