0 votes
I know this question was asked a few years back regarding PT7 & 8 but the suggested solution there hasn't worked this time (in PT9) so I'm hoping there's another idea. Occasionally, when doing Basic Checks in a project I work with, the translators find a naarow space (Unicode 202F). It's a mystery how they get there and attempts to replace them with standard spaces (0020) don't work. The character can initially be replaced by a standard space (using the spacebar). I check it is really Unicode 0020. When Basic checks are re-run it still registers and error although the cursor goes the the beginning of the verse where there is no error.  Then at some subsequent point, the original character (202F) reappears.

I've tried all the ideas suggested by Iver Larsen to the similar question in 2018 but nothing works. One difference; when I try to use Search and Replace it says "No matches found" even though it's there in the text and Basic Checks reports it as an error. Any help will be appreciated.
Paratext by (207 points)

1 Answer

0 votes
If you can use Help > Give Feedback in Paratext then the support team can take a look at your data. Make sure that you are in the book with the 202F when you report the issue so that it shows up in your data.
by (8.4k points)
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
For where two or three gather in my name, there am I with them.
Matthew 18:20
2,633 questions
5,375 answers
5,046 comments
1,420 users