+1 vote
568 vues

If you use the Latin alphabet with diacritics over characters, you may encounter a puzzling phenomenon in the Wordlist. You may have multiple entries of what appears to be the same word.
This happens because the Unicode standard has two ways of entering many letters with diacritics. For example, the é character can be the Unicode character 00E9, or it can be two characters, 0065 followed by 0301 (lower case e followed by combining diacritic acute). If this is the case, words containing 00E9 will not be identical with words containing 0065 + 0301, even if all the other letters are the same.

You can verify this by looking at the character inventory. This example is of a test project with two t characters, one *00E9 and one 0065 0301. You can see that it breaks down the difference between the é characters.

image

The Unicode standard does say that these sequences should be treated as identical by the software, but many programs have not managed to do that yet. Paratext does not, Microsoft Word does not either.

If you have this issue, you can fix it by doing a search and replace, for instance searching for one kind of é and replacing it with the other kind. To keep it from occurring again, translators working on the same project should either use the same keyboard file, or at least keyboard files that output the same character sequence for letters with diacritics.

Ancienne publication - affichée dans sa langue d'origine
Paratext par [Expert]
(3,3k points)

réaffiché | 568 vues

4 Réponses

0 votes
Meilleure réponse

In Paratext 7.6 (still in development), new projects will be default use
"Normal Form Composed" when saving text data - this will prevent these
differences in text that are usually caused by using different keyboards.
The “Normal Form Decomposed” can be used instead - this may be required to
make text display correctly in some fonts.

There is also a Convert Project tool in Paratext 7.6 that can be used to
change all text in a project to either NFC or NFD. The Convert Project tool
does create a new project in the process, but project history is preserved.

Ancienne publication - affichée dans sa langue d'origine
par [Administrator]
(3,4k points)
0 votes

The problem we’re into is that accent marks are being classified on their own or being grouped with the character that follows rather than with the character they modify.

image

What should we be doing differently?

Ancienne publication - affichée dans sa langue d'origine
par (448 points)

Dear drwww,

Go to Project/Language Settings and choose the Other Characters Tab. There
you will see a little tick box which says, “Non-standard diacritics follow
base character”. Tick this, and your problems should go away.

You should also make sure that the alphabetic characters tab is filled in
properly according to the “More Help” information provided on the side
slideout. You may have problems with Paratext accepting the capital form of
some of your combining diacritic characters. If you do, just put in the
lower case form(s) of the offending character(s) with a space between them.
The capitalization will be properly predicted.

Also, you should make sure to view the Characters Inventory with “Show
combinations” ticked. It won’t look right unless the tick box in the
language settings is chosen first, but it is important for making sure that
you are approving your characters properly, joined, rather than separate
from their diacritics.

Blessings,

Shegnada J.

Language Technology & Publishing Coordinator, Nigeria

GPS Text Processing Specialist

Wycliffe

+[Phone Removed]

Skype:Shegnada.James.

Ancienne publication - affichée dans sa langue d'origine
0 votes

This is actually fixed in 7.6. Even if the project is not fully normalized in the way @John+Wickberg suggests, the Wordlist will still only show one entry for these two normalized cases.

Ancienne publication - affichée dans sa langue d'origine
par [Expert]
(16,7k points)
0 votes

For additional experiences and other discussions, see (in chronological order):

  • What is Paratext's behaviour for composing/decomposing unicode characters/sequences?
  • Matches Not Found in Word List - Composed and Decomposed (whole conversation)
  • Guide: Checking > Characters Inventory (second post)

Adding keywords for search:
normalisation normalization

Ancienne publication - affichée dans sa langue d'origine
par (1,4k points)
réaffiché

Questions connexes

0 votes
0 réponses 68 vues
Il me semble que l'option espaces et caractères masqués (WHC) aura un impact significatif sur nos projets. Elle offre ... et peut-être par des retours de la part des développeurs.
Kent Spielmann 1,8k posée nov. 19, 2024
0 votes
1 réponse 274 vues
Following migration of our project to PT8, the work I had previously done in an interlinear back-translation into NT Greek appears ... . What do I need to do to fix these problems?
anon084127 105 posée oct. 27, 2017
0 votes
5 réponses 916 vues
Bonjour, j'utilise la dernière version de Paratext, WIN10 et PTXPrint. La langue Satere (SAT) utilise des ... reconnus lorsque j'essaie d'imprimer avec PTXPrint persiste ?
anon165192 116 posée févr. 21, 2023
0 votes
2 réponses 572 vues
J'ai des nombres comme 3 000 000 dans mon texte. La vérification de l'inventaire des caractères me signale une ... le vérifier comme valide. Comment puis-je résoudre ce problème ?
anon057624 136 posée sept. 6, 2021
0 votes
6 réponses 657 vues
J'essaie de changer les caractères décomposés dans mon projet (Manya - mzj) en caractères composés. Mais lorsque j' ... vous des idées sur la manière de résoudre ces problèmes ?
anon055151 176 posée mars 22, 2021
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
Dear friends, since God so loved us, we also ought to love one another.
1 John 4:11
3,060 questions
6,021 réponses
5,689 commentaires
2,035 utilisateurs