On Mon, May 09, 2005 at 03:28:29PM -0700, Arpad Biro wrote:
I needed to revert your change in $SUBJECT, which means I added "[encoding: UTF-8]" again to that file. I need that line because otherwise the following happens:
# ../intltool-update --pot ERROR: xgettext failed to generate PO template file because there is non-ASCII string marked for translation. Please make sure that all strings marked for translation are in uniform encoding (say UTF-8), then *prepend* the following line to POTFILES.in and rerun intltool-update:
[encoding: UTF-8]Because of this, I cannot update PO files without that line.
Bryce replied:
Hmm... Sorry, I didn't realize it had been put in intentionally. That line was causing several of us compile errors yesterday; is there any other way we could address the underlying issue?
I think I've found a solution, by looking at po/Makefile.in.in's rule for creating POTFILES from POTFILES.in: it looks as if things will work if we add a space to the end of the `[encoding: UTF-8]' line!
Doing so allows `../intltool-update --pot' for me, and `make' works, but I haven't yet tried doing a full `make distcheck' from a clean checkout. I've committed to CVS.
pjrm.