Bug: Typing in transliteration doesn't respect transliteration settings

I've discovered that when you're typing in transliteration (e.g. in a morph search or Bible Word Study reference box), you must type in simplified transliteration (or is it SBL General?), rather than in the transliteration format that you've selected in Program Settings.
That's really confusing, because that means if you want to search for a word that's being displayed in a reverse interlinear, you might have to use different transliteration to search for that word. (And I know that right-click normally means this doesn't matter, but I discovered this when trying to formulate a clause search, so it does matter.)
In my case, I was interested in the lemma יצב (which means "to stand", first occurrence is Exodus 2:4). With the scientific transliteration scheme (which is the default, I think), this is transliterated as yṣb, so that's what was being displayed in the reverse interlinear. But all the input boxes expect ytsb, and I couldn't work out why my word wasn't being accepted.
So, either:
- The input boxes need to support the transliteration format you've selected.
- Or the default transliteration must be set to the one that the input boxes support, and it should say (recommended) on the label so that people don't change it unless they know what they're doing.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
Comments
-
[Y]0
-
Mark Barnes said:
I've discovered that when you're typing in transliteration (e.g. in a morph search or Bible Word Study reference box), you must type in simplified transliteration
Mark, I'm having trouble replicating this in 5.1 Beta 6. Here are some screenshots to show where I'm inputing yṣb:
Were you referring to some different text boxes, or am I misunderstanding your report?
0 -
Toby Steele said:
Mark, I'm having trouble replicating this in 5.1 Beta 6. Here are some screenshots to show where I'm inputing yṣb:
I didn't realise that if you typed 'ṣ' rather than just 's', then it would work. But realistically, if you're going to be typing characters like that, you might as well type the Hebrew. Who knows how to type ṣ?
The whole point of transliteration is that it makes it easy for those without Hebrew and Greek. It's self-defeating to use by default, a transliteration scheme that is very difficult to type.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Mark Barnes said:
I didn't realise that if you typed 'ṣ' rather than just 's', then it would work. But realistically, if you're going to be typing characters like that, you might as well type the Hebrew. Who knows how to type ṣ?
Smarter heuristics for typing in transliterated base characters would be useful. I'll pass along the suggestion.
0 -
Mark Barnes said:
I've discovered that when you're typing in transliteration (e.g. in a morph search or Bible Word Study reference box), you must type in simplified transliteration (or is it SBL General?), rather than in the transliteration format that you've selected in Program Settings.
Isn't the search selection designed to be phonetic, rather than any particular transliteration? So for example you don't need any representation for gutturals, searching for "h:al" will find words starting with an aleph or a ayin with a qamets or pathach...
0