Finnish hyphenation of compounds: is integrating FST tech something that this project would like?
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python, tex
- Domain
- internationalization, localization
Research direction
The issue discusses integrating Finnish finite-state technology (like Pykko) for compound hyphenation. Start by examining the existing hyphenation patterns in the project, likely in pattern files. Research Pykko's MIT license and its lemma-splitting capabilities. Determine how to thin down Pykko or use a word list to avoid performance issues. Check the project's architecture for adding language-specific analysis modules.
Written by the indexing model from the issue text.
Description
Hi,
There's a wealth of Finnish-language finite-state tech (Voikko, Omorfi and Pykko off the top of my head being somewhat relevant to this) that can split compounds and lemmatize. Leveraging one of them (I'd propose pykko, perhaps somehow thinned down from the full feature set to just lemma-splitting; pykko is MIT) would allow dealing with one of the hyphenation patterns that the Institute for the Languages of Finland recommends against (https://kielitoimistonohjepankki.fi/ohje/tavutus-yleisperiaatteet/): Hyphenating compounds in places that are not compound boundaries. Compounds are common in Finnish, productive (ie. not listable; pykko can parse unknown compounds pretty well) and look really weird when mishyphenated, causing at least me to have to pause and re-read the end of the line.
I've worked with all of the FSTs above in the past in a professional capacity and could try to make a PR for integrating one of them. However, is this much language specific complexity something that this project would be OK taking on? The full pykko is somewhat slow, though perhaps a thinned down-version could be devised or a list of n-thousand most common words could be used as a way to only run analysis on a small percentage of cases. What are your takes?
- Dominant language
- TeX
- Stars
- 147
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from typst/hypher
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
kk (kazakh), cy (welsh), ga (irish) and en-gb are also permissively licensedPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 3/5 1-2 days Newbie friendliness 38/100
Similar issues
-
tui: TestEveryWordHasZh red on origin/main 221c91fae: no zh for "permission mode" (since 0b8c4bfc3)Open
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
NumberInput: an unsupported format unit throws a RangeError during render and unmounts the pageOpen
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
vercel-labs/ui#502 ·
Maintainers usually reply within 1 day
-
翻译冲突Open
Difficulty 1/5 Under an hour Newbie friendliness 78/100
fw876/helloworld#2089 ·
Maintainers usually reply within 1 day
-
3.15 تغییرات خودکار در ترجمهها
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
python/python-docs-fa#137 ·
-
good first issue translation
Difficulty 2/5 Half a day Newbie friendliness 72/100
UnkoynX777/houseguest#7 ·