view po/Makefile.mingw @ 27372:7fd1b4c73310

Connection error message changes for gg, and a few other strings changes. * Short connection error messages (phrases and short sentences) should not end in a period. This is kind of arbitrary, but I did comparisons both ways and I thought short messages looked a lot better without the period. Less cluttered, more approachable. * Connection error messages should not have trailing newlines--the UI should add a newline if it wants. * Change "token" to "captcha" in the input box prompts when creating a new account. Captcha is an increasingly common term for this. Not all users will know what it means, but "token" is not a whole lot better. And users should be able to figure out what to do using context clues, regardless of the term used. I believe we use the same term in QQ. * Put the output of g_strerror(errno) in the message when possible

# Makefile.mingw
#
# Description: Makefile to generate mo files
#

PIDGIN_TREE_TOP := ..
include $(PIDGIN_TREE_TOP)/libpurple/win32/global.mak

PACKAGE = pidgin

.SUFFIXES:
.SUFFIXES: .po .gmo

##
## SOURCES, OBJECTS
##

CATALOGS = $(patsubst %.po,%.gmo,$(wildcard *.po))

##
## RULES
##

.po.gmo:
	rm -f $@ && $(GMSGFMT) --statistics -o $@ $<

##
## TARGETS
##

.PHONY: all install clean

all: $(CATALOGS)

install: all
	mkdir -p $(PURPLE_INSTALL_PO_DIR)
	@catalogs='$(CATALOGS)'; \
	for cat in $$catalogs; do \
	  cat=`basename $$cat`; \
	  lang=`echo $$cat | sed 's/\.gmo$$//'`; \
	  dir=$(PURPLE_INSTALL_PO_DIR)/$$lang/LC_MESSAGES; \
	  mkdir -p $$dir; \
	  if test -r $$cat; then \
	    cp $$cat $$dir/$(PACKAGE).mo; \
	    echo "installing $$cat as $$dir/$(PACKAGE).mo"; \
	  else \
	    cp $(PURPLE_PO_TOP)/$$cat $$dir/$(PACKAGE).mo; \
	    echo "installing $(PURPLE_PO_TOP)/$$cat as" \
		 "$$dir/$(PACKAGE).mo"; \
	  fi; \
	done

clean:
	rm -f *.gmo