Set default interlinear view options
I maintainer di solito rispondono entro 1 giorno
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 48/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- typescript
- Ambito
- frontend
Direzione di ricerca
Start by locating the interlinear view settings and the code that persists project-specific settings between sessions. Compare the current defaults with each requested option, including the conditional morphology and free-translation behavior. Done means the listed defaults are applied consistently and user changes persist for the project.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Settings helpful to keep as view options
Continuous scroll I think users will find this option to be helpful and that it should continue to be a view setting. Interlinear work is done in a continuously horizontally scrolled window at the top. Verses are displayed in a vertically scrolling window below them. To jump to another verse to interlinearize, the user clicks on a verse in this list.
To be more familiar with PT9 users, I think the initial, default value should be off. When it is off, the interlinear analysis full verses can be viewed. With the Continuous scroll option, only the portion of the analysis that can be displayed in a single row at the top of the screen can be viewed.
Show free translation To save on screen real estate and because not every team will want to provide a free translation, I think this would be off by default unless the team had already provided free translations.
Show morphology Having this option turned on by default will provide users with the line of text that is required to specify morphology, which will be more familiar with PT9 users—and would be better for PT10 Power users. In the extension: an additional line for glossing morphological breaks is only added when the morphological breaks are added.
I do think that Show morphology is a helpful option to keep. When the word gloss is the focus, rather than the morphology, it is easier to review the glosses with this option turned off. When the Interlinearizer is included in Simple, the morphology line should be off by default.
Settings that are helpful defaults for all users (i.e. can be removed from settings)
Show verse gutter Having this option turned on cleans up the view and makes it easier to see verse breaks when scanning the text.
Show phrase controls on focus only I think that it would be better for this option to always be off so that the phrase controls can be more discoverable. With this option on, the phrase has to be clicked on and hovered over to see the controls. I don't think it's too much clutter if the controls only display when hovering over a phrase.
Show suggestions I think that this should always be on. A toggled on setting makes setting the gloss easier and would be more familiar with PT9 users. Of course, we would need to allow them to configure the source of the suggestions. For right now, the source of suggestions only comes from prior analyses and glossing. Hopefully soon there will be suggestions that could come from FLEx as well as from other sources.
Hide out-of-segment link buttons The translator/linguist can join verses (or other segmented text) to allow linking items. When toggled on, this option displays disabled links. Toggling it on hides these disabled links. It makes sense to me have this setting toggled on for all users because it would remove clutter from the view.
Scroll strip freely enables scrolling horizontally with the mouse wheel when the Continuous Scroll window is opened and the user hovers over it. I think that this option should be toggled on by default.
It would be helpful to persist settings that the user changes for a given project between Interlinearizer sessions.
- Lingua principale
- TypeScript
- Stelle
- 2
- Fork
- 0
- Merge medio
- 1g 23h
- PR unite (30g)
- 57
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
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di sillsdev/interlinearizer-extension
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
sillsdev/interlinearizer-extension#506 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
sillsdev/interlinearizer-extension#505 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 56/100
sillsdev/interlinearizer-extension#504 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 52/100
sillsdev/interlinearizer-extension#503 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 70/100
sillsdev/interlinearizer-extension#496 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di sillsdev/interlinearizer-extension
Issue simili
-
a10y a10y-audit ai-driven-qa claude
Difficoltà 2/5 1-3 ore Idoneità per principianti 86/100
linagora/twake-directory-manager#219 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
I maintainer di solito rispondono entro 1 giorno
-
type: bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 79/100
I maintainer di solito rispondono entro 1 giorno
-
0️⃣ phase/new
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno
-
Pulse v7: buildPreferencesFromTelos() bypasses telosSectionOrFile(), renders empty on unified-TELOS installsForse già presa @zephyr91 l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
danielmiessler/LifeOS#2393 ·
I maintainer di solito rispondono entro 4 giorni