Thanks for bringing this to our attention.
Apparently this is a problem that involves certain Windows locales, the new ABP1 Application and the (latest) ABP1 validator.
Until this has been resolved (hopefully on Monday latest) I stopped the validation of ABP1 results.
BM

Arecibo Radio Pulsar search --- Validate error
)
I have modified the ABP1 validator and started ABP1 validation again.
The ABP1 results that have been marked invalid are re-issued for validation, i.e. the new validator will have another look at them.
We should issue a new App version soon that doesn't have this problem (i.e. don't write non-ASCIi characters into the result file).
BM
BM