Skip to content

Comments

Fix LT-22422: record msa in lex entry for variants in XAmple#683

Merged
jasonleenaylor merged 1 commit intomainfrom
LT22422
Feb 19, 2026
Merged

Fix LT-22422: record msa in lex entry for variants in XAmple#683
jasonleenaylor merged 1 commit intomainfrom
LT22422

Conversation

@AndyBlack
Copy link
Collaborator

@AndyBlack AndyBlack commented Feb 18, 2026

Fixes LT-22422.
When producing the lexicon for XAmple, we now include the HVO for the MSA on variants. Before we just used the HVO of the lex entry and, if needed, the HVO of the lex ref. Now we always include the HVO of the MSA of the entry. This enables us to show the correct gloss and MSA info in the parse.


This change is Reviewable

Change-Id: Ice265ae442005a955be3bd0e1a9a0c1734affc31
return Tuple.Create(int.Parse(msaHvoParts[0]), msaHvoParts.Length == 2 ? int.Parse(msaHvoParts[1]) : 0);
// the msa hvo has one part or three parts separated by a period.
// in the latter case, it is the lex entry hvo, the lex ref hvo, and the msa hvo
return Tuple.Create(int.Parse(msaHvoParts[0]), msaHvoParts.Length == 3 ? int.Parse(msaHvoParts[1]) : 0,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might a user want to process an existing two-part msaHvo string?

Copy link
Collaborator Author

@AndyBlack AndyBlack Feb 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No. Users never see these. The code included here is the only thing that processes these.

@jasonleenaylor jasonleenaylor merged commit 0bde379 into main Feb 19, 2026
4 of 5 checks passed
@jasonleenaylor jasonleenaylor deleted the LT22422 branch February 19, 2026 23:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants