Morphology tagging in PBB documents

I have several Syriac documents in a morphological database and they are tagged either with CAL or SEDRA morphology. I would really like to create some morphologically tagged versions of these with PBB. On the wiki for PBB, I saw the example for Greek Strongs number and I know the datatypes for both the CAL and SEDRA morphologies. I have tried various ways of inserting similar milestones but for the CAL and SEDRA morphologies and nothing seems to work. Is it possible, and is so, how would I go about tagging the following word with either of the following lexicon entries?
WORD:
ܡܠܒܫ
CAL:
לבשׁ verb
peal 1 passim to clothe oneself with
pael 1 ImpArEgOst (p.p.) to wear
ethpaal 1 Syr to put on
2 Syr to invade
3 Syr to be crazy
(h)aphel 1 BibArDan,Palestinian,Syr,JBA to clothe s.o.
2 Syr to afflict with
3 JLAGal to enshroud
4 JBA to seize
ettaphal 1 Syr to be clothed
LS2 357
SEDRA:
ܠܒܫ, ܠܒ݂ܶܫ Verb. Gloss: put on; be clothed; clothe ( aphel ). Root: ܠܒܫ. Inflected form marked as Lexeme: ܠܒ݂ܶܫ. Index of Inflected Forms: ܠܒܫ.
Comments
-
I'm a bit confusing with what you're trying to do. If you're creating a lexicon or dictionary then we have to use headwords (milestones). If you're creating morphologically tagged text, that's something quite different. You could tag each word with the appropriate reference type, which would enable you to click on the word and get to a lexicon. But even that is not a morphologically tagged text, as it wouldn't include any additional lexicon information apart from the lemma.
We've not yet been given any information to indicate that creating morphologically tagged text will be possible in PBB, and it if is possible, we've not seen aything that would suggest the syntax to use.
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'm a bit confusing with what you're trying to do. If you're creating a lexicon or dictionary then we have to use headwords (milestones). If you're creating morphologically tagged text, that's something quite different. You could tag each word with the appropriate reference type, which would enable you to click on the word and get to a lexicon. But even that is not a morphologically tagged text, as it wouldn't include any additional lexicon information apart from the lemma.
We've not yet been given any information to indicate that creating morphologically tagged text will be possible in PBB, and it if is possible, we've not seen aything that would suggest the syntax to use.
Sorry, should have said links rather than milestones.
And sorry about not being clear enough. Yes, I was trying to tag each word with the appropriate reference type in order to link to the Lexicon. With what we currently know about syntax that should be possible, but I have not been able to work out the exact syntax to make it work. What do we use as the destination of the link? The Syriac/Aramaic/Hebrew word? That does not appear to work. At least with RTL languages it breaks the link from being recognized as a link.
I was at the same time trying to elicit information about what we might need to do in order to morphologically tag words in a PBB. I would hope that at minimum the syntax has been worked out.
0 -
That would be very useful to me.
0 -
James W Bennett said:
What do we use as the destination of the link? The Syriac/Aramaic/Hebrew word? That does not appear to work
Link are even more flaky in this beta than the milestones, and I have very few working correctly. I think this is a combination of bugs in the compiler and my ignorance of syntax. With regard to the latter, it's become apparent to me that most of Logos' links are more complex than we imagine. Believe it or not, the following syntax does work:
[[Test|link.pos=LEXEMEINDEX.1308|res=LLS%3A46.30.23]]
- although you often have to hack the resulting .docx file to get rid of the garbage that often prevents Logos from building links successfully.
You can replace LEXEMEINDEX.1308 with such things as INFLECTED.8788 and so on. But how you are supposed to work out what those are without a LOT of hassle, I'm not sure.
I should also point out that what I'm doing here is creating links to a specific resource, rather than doing it properly using reference types (which then open the resource that is most highly prioritised). I've struggled with reference types, I think because Logos haven't really documented how we should do this yet. The 'link' solution above should not really be considered a proper substitute for this.
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