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

Choose between multiple sets of PT9 interlinear data

Aperta
  • Qualcosa non va?
#311 1 commento 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@jasonleenaylor ci sta già lavorando.

Dal 4/9/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

From PT team:

I have a PT9 project with four sets of interlinar data (in four different writing systems). Could the project admin select which of the projects that they want to open or convert?

Image

Not having this option is a consequence of the current design where all are automatically imported and merged.

Merged from #296: The import report prints the same language tag twice when files disagree on casing

Importing PIC reports:

Languages: English, es-MX, es, es-MX

Not a double-count: those are two files whose gloss languages resolved onto one tag. The message
drops the only thing that explains it.

The converter groups by the raw GlossLanguage string, so es-MX and es-mx stay separate
groups; tag resolution then uppercases the region subtag, so both land on es-MX. The modal maps
each group to its resolved tag with no dedupe and no disambiguation
(Pt9ImportModal.tsx:91) — foldReport dedupes books one line above and not languages.

The report already carries merge.sameTagCollisions, which groups exactly these raw values.
Nothing surfaces it, so the explanation is computed and then discarded at the UI boundary.

Options: a footnote line when sameTagCollisions is non-empty, beside the existing
missing-books note — recommended, since the collision is a fact about the files rather than about
one language; or print the raw value beside a colliding tag (es-MX (es-mx)). Deduping the list
is cheapest and wrong: the groups really are separate and their glosses really did merge onto one
key.

Decide tagIsFallback at the same time — English prints identically to a real tag though the
report flags it — since the same line decides both.

Out of scope: whether two raw groups should share a gloss key. That's a converter question;
this is only about the report saying it happened.

Size: S. Priority: Low — cosmetic, but it reads as a double-count.

PIC is the reproduction (#283).

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

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.