Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add support for versification conversion to ScriptureRangeParser

Open
  • Is something wrong?
#470 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
csharp
Domain
backend

Research direction

Start by locating ScriptureRangeParser and the versification files referenced in the issue, then inspect how ranges and book identifiers are currently parsed. Use the listed MAL, PSA, DAG, SUS, and BEL conversions as checks; done means source-versification ranges convert to the expected target-versification ranges, including split ranges and renamed books.

Written by the indexing model from the issue text.

Description

Follow on from https://github.com/sillsdev/serval/issues/1013.

As Serval expects Scripture Ranges in the target versification, and Scripture Forge inputs source corpus versifications for inferencing in the source versification (as SF cannot use the versification in the JavaScript frontend, so just lists what books the source has for inferencing), we need to be able to convert a ranges such as:

  • MAL1-4 (ENG) to MAL1-3 (ORG)
  • PSA1-151 (LXX/RSO) to PSA1-150,PS2 (ENG/ORG)
  • DAG1-12 (LXX) to DAN1-12 (ENG/ORG)
  • DAG13 (ENG/RSO) to SUS1 (ORG/LXX)
  • DAG14 (ENG/RSO) to BEL1 (ORG/LXX)

(These mappings are all present in the versification files)

As an actual bug SF is encountering, this only really affects drafting from Daniel or Psalms in LXX/Russian versification to English versification.

Dominant language
C#
Stars
29
Forks
16
Avg merge
5d 5h
Merged PRs (30d)
11

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No 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.

More from sillsdev/machine

All issues in sillsdev/machine

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.