concerning the problem that de.pox is not generated correctly, I noticed the following: The awk scripts in the Makefile generate a po file with ISO-8859-1 encoding first. This final rule:
$(srcdir)/$(PACKAGE).pot: $(POTFILES) $(srcdir)/POTFILES.in l10n_pots
$(XGETTEXT) --join-existing --default-domain=$(PACKAGE) --directory=$(top_srcdir) \
--from-code=ISO-8859-1 \
--escape --add-comments --keyword=_ --keyword=N_ \
--keyword=qt_ --files-from=$(srcdir)/POTFILES.in \
&& test ! -f $(PACKAGE).po \
|| ( rm -f $(srcdir)/$(PACKAGE).pot \
&& mv $(PACKAGE).po $(srcdir)/$(PACKAGE).pot || true)
however changes the encoding to UTF-8. As a consequence, gettext interprets some character in the messages as a multibyte character that is broken between two lines :-( Unfortunately, I haven't found a command option that enforces ISO-8859-1.
I guess that your recent proposal to remove all non-ASCII characters will circumvent the problem though it does not really remove the cause. I think in the long term, we have to switch to UTF-8 anyway because the gettext manual says:
`--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 Python, Tcl, and
Glade input files are always assumed to be in UTF-8, regardless of
this option.IIRC glade is related to gtk. So if we support l10n for the gnome frontend (notice: we don't support it at the moment), we might have to move to UTF8 anyway.
I will wait until you commit your patch and check things afterwards.
Michael
