sillsdev / sillsdev/languageforge-lexbox
Headword, component & complex-form formatting
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 9
- Forks
- 8
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 49
Description
Headword
In FLEx, always includes the homograph (if not unique) appended as subscript
Component
In FLEx:
<headword>[subscript(homograph)] [<sense-index> <sense-gloss>]
Strangely in FWL, for FLEx projects we show the homograph (not as subscript), but only if the component is associated with a sense.
Complex forms
In FLEx, just like standard headwords, because senses aren't relevant here.
However, FWL might need more, because we don't display complex-forms under specific senses, so that information is not available.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the headword, component, and complex-form formatting entry points for FLEx projects. Compare the current FWL output with the stated FLEx behavior, including homograph subscripts and sense association. Done means standard headwords, components, and complex forms display the intended homograph and sense information consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- content
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100