Problem with associations and decomposed characters

Question

I am trying to change the decomposed characters in my project (Manya - mzj) to composed characters. But when I try to apply this option in the Project Properties section, it will not let me select ‘Okay’.

Shot51194×1246 32.6 KB

I think the problem might have to do with the incomplete associations. I have not been able to figure out how to get my project to communicate with the associated lexical project.

shot41216×1274 29.4 KB

There may be some kind of conflict in the registry, but I have not been able to fix it. In Project Properties it shows the language as ‘Maninka (mzj)’. So it has the correct three letter code, but not the correct language name. This may trace back to a mistake I made when I first registered the project. When I go on the Paratext Registry website, everything looks as it should with the language name and code.

Shot3750×1162 24.9 KB

Shot12292×1062 171 KB

Any ideas of how to resolve these problems?

Answer 1

I think if you change the associate lexical database to “none”, then you should be able to change the normalization setting.

A word on associating a Fieldworks database to Paratext. The most important thing is that that the language codes match exactly. Fieldworks is setup to be very specific on the language identifier. I suppose that could be because many linguists work with variants of the same language. Paratext likes simple language identifiers. I will give an example of a language spoken in Tanzania, Mozambique and Malawi called Yao. Fieldworks has a facility to specify the variant of the language based on geography. So the language code is yao, but if dictionary work is done in Mozambique, it is good to have the language code yao-MZ in Fieldworks. Paratext on the other hand will work just fine with the language code yao. In a scenario like this the Fieldworks database cannot be associated to the Paratext project. The language codes in Paratext and Fieldworks have to be the same.

2021_03_22_13_22_13_Vernacular_Writing_System_Properties1308×727 112 KB

Answer 2

There does seem to be something conflicting with the language codes. In Paratext it shows the language code as mzj-LR-fonipa. I’m not sure where that code comes from, as it is not a dialect of the language or anything else I’m aware of. There is not option to change it to anything else.

Shot61798×902 34.3 KB

I am unable to change the associate lexical database to “none”. There is only the red arrow and no way to click “okay”.

Comments

“-fonipa” refers to the International Phonetic Alphabet, apparently selected in your screenshot by “IPA transcription”.

---

anon055151:

There is only the red arrow and no way to click “okay”.

If you hover over the red icon, what does it say is the problem?

---

It says, “The associated lexical project is invalid”.

Answer 3

Ah, okay. That’s likely the real problem. That error likely means that Paratext could not find FLEx at all. Which version of FLEx and Paratext are you using? There are some known compatibility issues with some combinations of FLEx/Paratext.

Answer 4

I’m using Language Explorer 9.0.15.0 and Paratext 9.1.104.59.

Answer 5

Hi @anon055151,

Would you please check if you are using 32-bit or 64-bit FieldWorks?

Go to Help > About Language Explorer:

image645×560 96.7 KB

Answer 6

It’s 64-bit FieldWorks.