sillsdev / sillsdev/silnlp

Generated drafts follow the source project's versification; they should follow the target project's versification.

Open
#1,069 1 comment 0 reactions 2 assignees View on GitHub

@ddaspit is already working on this.

Since May 14, 2026.

bug machine pipeline 6: infer
Dominant language
Python
Stars
39
Forks
7
Avg merge
1d 9h
Merged PRs (30d)
5

Description

If the versification of the source project differs from the versification of target project, and a draft is generated for a book with a versification that differs from the source to the target, the draft will have the source project's versification. Importing this draft as-is into the target project would require the translation team to be aware of this problem and manually update the draft's versification before they import it.

As an example:

  • Original (1) versification and English (4) versification differ in the versification of MAL. In Original, there are 3 chapters; chapter 3 has vv 1-24.
  • English (4) versification has 4 chapters. Chapter 3 has vv 1-18 and Chapter 4 has vv 1-6 (i.e., MAL 3:19-24 is mapped to MAL 4:1-6).
  • If the source project uses Original and the target project uses English, a draft of MAL from the source project will follow Original versification. The translation team will need to manually move MAL 3:19-24 to MAL 4:1-6 to use the draft.

Contributor guide

No contributing guide indexed for this repository

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.