0 suara
452 tampilan

Any thoughts on why the interlinearizer is suddently generating unsual guesses with mixed upper/lower case red letters?

Here is are two examples from Gen 37.13:

Note the guess is fATHER and all the other possible guesses are also upper case.
And here is an example with a blue gloss:

Postingan lama - ditampilkan dalam bahasa aslinya
Paratext oleh (110 poin)
ditampilkan kembali | 452 tampilan

2 Jawaban

0 suara
Jawaban terbaik

I looked into your problem with the interlinear. There actually isn’t a bug in the Interlinear causing this. The problem is with the BTA project.

The problem is that the English language definition used by the BTA project got messed up and the character settings are not English settings (I’m not sure where they came from). They also define the lowercase characters as uppercase and vice versa. Because the language settings are shared between projects, this caused the settings for other English projects to also be messed up.

Fixing the characters in the English language definition (Project > Language Settings > Alphabetic Characters tab) fixed the interlinear issue.
Note that you may have to restart Paratext to see the fixed settings.

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

ditampilkan kembali

That fixed it. Thanks so much anon291708. I will retract my help ticket with Paratext and try to learn how the language definition got changed.

Postingan lama - ditampilkan dalam bahasa aslinya
0 suara

The Interlinear is making its guesses based on the “Model text for Interlinearization” that you have told it to use. Which project is that? What does its text look like?

Incidentally, our best practice approach for the Interlinearizer is to set it to use the back translation project (if you have one) as the model text.

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

ditampilkan kembali

Dear dhigby,

Thank you for responding.

We’ve been using ESV as our interlinearizer model, which isn’t an all-caps translation as you know.

We have the same problem if we use the back translation project (BTA). It is generating all-caps or mixed-caps guesses and some of them don’t make any sense.

anon242106

Postingan lama - ditampilkan dalam bahasa aslinya

This is definitely a bug, please report it from the help menu.

⁣Sent from TypeApp ​

Postingan lama - ditampilkan dalam bahasa aslinya

Thank you. I just reported it.

Postingan lama - ditampilkan dalam bahasa aslinya

Pertanyaan terkait

0 suara
1 jawaban 38 tampilan
Kami ingin menampilkan glosa Prancis di alat Parallel Passages. Glosa Prancis sudah dapat ditampilkan di jendela ... ada di jendela Parallel Passages. Bagaimana cara mencapainya?
goodgoan 347 bertanya Mar 11
0 suara
4 jawaban 1,0k tampilan
I have just upgraded a project that had an extensively populated interlinearizer (lexicon.xml and associated interlinear ... and black colors in the interlinearizer. Any thoughts?
Milt_Jones 184 bertanya Des 21, 2018
0 suara
2 jawaban 446 tampilan
Secara internal, dari mana baris parse gloss di interlinearizer mengambil informasinya? Saya mulai mencoba adaptasi menggunakan ... -04 11_21_20-Paratext 9.21264 269 13.6 KB
anon297911 424 bertanya Mar 4, 2022
+4 suara
4 jawaban 620 tampilan
Seolah-olah Paratext 8 memiliki masalah dalam memigrasi glosa interlinear jika Anda menggunakan Interlinearizer di versi 7 untuk ... apa yang salah di file yang Anda edit.
[Expert]
sewhite
3,3k
bertanya Nov 3, 2017
0 suara
3 jawaban 230 tampilan
Halo semua, Paratext saya sebelumnya berjalan dengan baik, tapi tiba-tiba menjadi sangat bermasalah/membeku. Terutama, ... alur kerja saya secara drastis. Terima kasih! Aaron
PecanMango 112 bertanya Okt 22, 2024
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,052 pertanyaan
6,011 jawaban
5,677 komentar
2,031 pengguna