0 votes

I have recently come across an issue, which I am now recognizing in more and more projects. Its particular symptom comes when you try to correct a word with a character that has a diacritic (.e.g. á or Á). You make the correction, and it comes back with the message, No Matches Found.

This is often because (1) there is no normalization being applied to the project
(2) the character á or Á in this project are decomposed characters, not composed (one unit).

I am told Paratext 8 stores all its data in the Word List, wherever possible, as composed. So when you click on a word in the word list, which has a correction, it then looks in the data, and does not find it, because out in the data, the á character is not composed, but decomposed.

The most robust solution for this issue is to Convert the Project - and implement a Normalization - preferably Composed.

The other solution is not to normalize the project by converting it, but to change the autocorrect keyboard, so that, instead of entering decomposed á, it enters composed á etc. And also to do a find and replace across the data, finding all the decomposed characters, and replacing them with composed characters.

Please, Paratext experts, comment on the above two solutions, as this feature is probably causing not a little frustration out there.

Paratext by (536 points)
reshown

11 Answers

0 votes

Adding keywords for search:
NFC NFD composed decomposed normalisation normalization normalise normalize normalised normalized

by (1.4k points)

Related questions

Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
And let us consider how we may spur one another on toward love and good deeds, not giving up meeting together, as some are in the habit of doing, but encouraging one another—and all the more as you see the Day approaching.
Hebrews 10:24-25
2,628 questions
5,369 answers
5,045 comments
1,420 users