Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Evaluate Checking Assistant usability feedback on interlinear glossing

Aperta
  • Qualcosa non va?
#401 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
8/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
ai, frontend

Direzione di ricerca

This is a usability review that needs product decisions before any code change. Start with the back-translation/schema.ts:6-13 definition the issue quotes, then the Back translation view, its hover card and the example list, which the issue says show no gloss. Nothing is ready to build yet: the team must first decide between an interlinear layout, a free rendering, or a rename, and whether the Interlinearizer replaces the gloss cache. Done means those decisions are recorded and split into scoped issues.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Source: paratext-assistant#182, five online sessions (Sept–Oct 2026; a linguist-translator, a linguistic advisor, two consultants and a Paratext advisor).

Context. The Checking Assistant's "Back translation" view is an AI word-by-word gloss. From the issue: "the fluent back translation for each verse was replaced by the interlinear on purpose (back-translation/schema.ts:6-13). The link and the popover are still titled 'Back translation'." The view "glosses word by word in the draft's order, with tags such as .PAST, OBJ and GEN."

1. Request: an interlinear layout (P2, #5)

  • P2: "I would hope that it's more like… interlinear, like in the Paratext 9… I would like to see both the language data and then, underneath each word, the English… without having to jump from one to another like I am doing now."
  • P2: "sometimes it would cover other things". The word hover card covers the glosses next to it.
  • Issue note: "The data exists: word alignment comes with the one call the screen already makes, so an interlinear layout needs no extra AI call."

2. Compared with an existing interlinear (P4, #9)

  • P4: "this doesn't do more than the interlinear. In fact, it probably does less."
  • "P4 noted it could help a team that has no interlinear."
  • P4 expects a back translation to show "how would this sentence sound if a mother tongue English speaker said it."
  • Proposed change: "name it for what it is, e.g. 'Word-by-word gloss (draft word order)'."

3. A free back translation as well as the gloss (P3, #12; P4 #15)

  • P3: "It's not a back translation to give the tense and relationships… It's also helpful at times to have the free back translation, which gives more of the relationship and the meaning."
  • P4: "Many consultants want a readable English one."
  • Issue: "this is a product decision. Either add a free rendering, or rename the view 'Word-by-word gloss' so people expect the right thing."

4. The gloss tags read as errors (P5, #7)

  • P5: "some of the terms are not matching exactly. You can see, like, ART…" The gloss read "all ART people PERF praise.OBJ… REL ART Joseph". Verdict: "not accurate."

5. Wrong glosses can't be corrected (P3, #6)

  • "In the verse back translation for 4:6, the word for 'happy' is glossed 'anger'."
  • P3: "Knowing what I know and that there are two mistakes in here, I would feel a little cautious about trusting it."
  • P3 asked whether an earlier answer had caused it: "I don't know if I affected that or not by what I said. Would that have had an effect?"
  • Code: "Glosses are cached per chapter and checked only against a hash of the chapter's text. No answer, ledger entry or note reaches them." The only remedy is "Gloss this chapter again", and the hint says "every later check uses it", "so a wrong gloss also feeds the Meaning checks."
  • Proposed change: "Let a user correct a word's gloss, and keep the correction."

6. Request: glosses under example verses (P5, #14)

  • About a claim on numerals, P5 said: "I can read those things, but when I cannot understand, that is a hard thing… I need to go to model text, go to back translation… a roundabout."
  • Code: "the example list shows the reference and the verse text only, with no gloss and no link to the verse."

7. Request: use the project's own back translation (P1, #19)

  • "The team has a human back translation of every completed book. P1 asked whether the analysis uses it, and whether it should." Code: "only the AI back translation exists."

Overlap with the Interlinearizer. Items 1, 5 and 7 ask for a stacked word/gloss layout, glosses that users can correct and that stay corrected, and the use of data the project already owns. The Interlinearizer provides all three, so these items are where the Assistant could use it instead of keeping its own gloss cache.

Lingua principale
TypeScript
Stelle
2
Fork
0
Merge medio
2g 7h
PR unite (30g)
45

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di sillsdev/interlinearizer-extension

Tutte le issue di sillsdev/interlinearizer-extension

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.