scribe-org / scribe-org/Scribe-iOS

Switch gender annotation over to reference separate lexemes in a loop

Open
#401 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

blocked help wanted
Dominant language
Swift
Stars
169
Forks
109
PR merge metrics
No merged PRs in 30d

Description

Terms
Description

Scribe will be switching over its data process to be more directly based on one lexemes per data entry. At this time we combine lexemes together based on the individual strings, so in German the word Schild means sign and shield, but is one entry for us. In order to simplify the data formatting process, we'll need to remove this, which further means that the way we store genders will be different.

The current way is that if a string has multiple genders, then we'll store each of them separated by slashed, so F/M/N/C/PL and all the variants. We'll soon have a situation where we'll have one entry for every lexeme and their plural. What this means is that rather then checking to see if the string has a dash in it and then separating it, we'll need to get the gender and check to see if the string/lexeme occurs more time and then append those genders.

Contribution

Happy to discuss the work for this and help with implementation or work on it myself at some point!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the new formatting process in Scribe-Data issue 142, which blocks this work, then locate the current gender annotation handling in Scribe-iOS. Compare the existing slash-separated approach with the separate-lexeme format described here; done means genders are derived across repeated lexemes without the current string-splitting behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
swift
Domain
mobile-dev
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.