Ruby text incorrectly above base text in diglot, even though it is not checked in either project.

Question

I have a diglot where one of the texts is an interlinear text. Even though neither text of the diglot has "Ruby Text Above" checked on the Advanced tab, the ruby text appears above the base word, which we do not want. Is this a bug to be fixed, or am I doing something wrong?

Here is the archive: Google Drive Link to Archive

Answer 1

Yes, this appears to be a bug, from what I can see. But I wonder if it will work better if the diglot (ALEPH) is the primary project, and it calls PRK as the secondary project.

Presumably you are able to get the original language above when running ALEPH independently, and it is only failing when it comes together with another text as a diglot.

Unfortunately the Archive which was submitted failed to pick up and package the interlinear folder for ALEPH. Would you please send another archive of just an ALEPH interlinear so we can replicate the issue and hopefully solve the problem.

Comments

Here is the ALEPH archive. Is that what you need?

---

I noticed today that there seems to have been a change in the behaviour of the texhacks (and other things too? I don't know) and boolean values are only getting set in the TeX file if they disagree with what python thinks is the default. If python and TeX disagree about the default, then the flag becomes uncontrollable.  That's a bit of a pain if 'sensible default for legacy projects not using UI' != 'sensible default when using the UI'.

---

Thanks for the ALEPH archive. Unfortunately it didn't contain the interlinear_prs folder as I was expecting. [Another bug/regression to be fixed!] 

However, I think we have enough information now to be able to replicate the issue and get back to you. Thanks.

However, I still wonder whether it works better "if the diglot (ALEPH) is the primary project, and it calls PRK as the secondary project"