+1 suara
567 tampilan

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.

Postingan lama - ditampilkan dalam bahasa aslinya
Paratext oleh [Expert]
(3,3k poin)

ditampilkan kembali | 567 tampilan

4 Jawaban

0 suara
Jawaban terbaik

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.

Postingan lama - ditampilkan dalam bahasa aslinya
oleh [Administrator]
(3,4k poin)
0 suara

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?

Postingan lama - ditampilkan dalam bahasa aslinya
oleh (448 poin)

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.

Postingan lama - ditampilkan dalam bahasa aslinya
0 suara

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.

Postingan lama - ditampilkan dalam bahasa aslinya
oleh [Expert]
(16,7k poin)
0 suara

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

Postingan lama - ditampilkan dalam bahasa aslinya
oleh (1,4k poin)
ditampilkan kembali

Pertanyaan terkait

0 suara
0 jawaban 68 tampilan
Menurut saya, opsi spasi dan karakter tersembunyi (WHC) akan berdampak signifikan pada proyek kami. Opsi ini ... lain, dan mungkin mendapat tanggapan dari para pengembang.
Kent Spielmann 1,8k bertanya Nov 19, 2024
0 suara
1 jawaban 274 tampilan
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 bertanya Okt 27, 2017
0 suara
5 jawaban 915 tampilan
Halo, saya menggunakan versi terbaru Paratext, WIN10, PTXPrint. Bahasa Satere (SAT) menggunakan vokal bersuara ... ketika saya mencoba mencetak dengan PTXPrint masih berlanjut?
anon165192 116 bertanya Feb 21, 2023
0 suara
2 jawaban 572 tampilan
Saya memiliki angka seperti 3 000 000 dalam teks saya. Periksa inventaris karakter menunjukkan kesalahan: initial ... sebagai valid, bagaimana cara saya mengatasi masalah ini?
anon057624 136 bertanya Sep 6, 2021
0 suara
6 jawaban 657 tampilan
Saya sedang mencoba mengubah karakter terurai (decomposed characters) dalam proyek saya (Manya - mzj) menjadi karakter ... ada ide tentang cara menyelesaikan masalah-masalah ini?
anon055151 176 bertanya Mar 22, 2021
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
3,060 pertanyaan
6,021 jawaban
5,687 komentar
2,035 pengguna