This latest post of yours (from the 27th) introduces
Thanks for another very useful Quick Fix, though I won’t quite be able to use it until it supports the standard hierarchy. Currently it assumes that the user is prepared to convert from standard to alternate, which seems unlikely to me.

I imagine the FLEx importer would be happy with either hierarchy as long as the \ps and \sn fields are paired up nicely together, though I’ve not tested this thoroughly.

What if instead, this Quick Fix first checked to see whether “MDF Unicode” or “MDF Alternate Unicode” was selected when the file was opened, and then:
- If standard, copy \ps down to just above each \sn.
- If alternate, copy \ps down to just below each \sn.

The current wording, “Push \ps down to subsequent \sn’s”, is ambiguous and therefore perfect.

Personally, I think that the alternative hierarchy is more intuitive and better matches FLEx. But from a theoretical standpoint, some linguists would disallow having a single sense with multiple parts of speech. They’d say that multiple senses must be multiple POS’s. Of course, FLEx enforces this one-to-one relationship, but MDF Alternate cannot.

Anyways, kudos again for posting this stuff publicly to make it easier to dialog about it in a way others can benefit from.

-Languist