I think that the fix applied to #1072594 (recoding the input file from latin-1 to UTF-8) was not necessary. Changing the config of po4a to correctly specify the used encoding would have worked.
I tried to improve the error messages upstream to help future users to debug such issues, but in any case, this does not justify a RC bug against po4a, thus closing. Thanks for reporting, Mt
signature.asc
Description: This is a digitally signed message part
