Closed DavidHaslam closed 5 years ago
Preprocessing is unnecessary in this situation. You can specify the encoding on the command line. I will add this particular way of specifying UTF-8 as valid though.
This should be fixed now. test it and let me know.
Thanks. It may be next week.
I have a set of SFM files in which the translators had used:
instead of
NB. They were probably using an older version of ParaTExt when these were made.
For such situations, it might be preferable to permit relaxations to strict conformance for lines that have no semantic significance, this being one such example.
cf. All the SFM files were properly encoded as UTF-8.
Permitting relaxed conformance would obviate the need to preprocess all 66 files just to fix this niggle.