Implement settings menu/page for selecting interface/functionality options

[aarppe]

So that users – language instructors, learners, community members, linguists – can choose exactly the functionality, dictionary sources, and labeling as well as othe behavior that they want, we should implement the following settings menu/window for selecting among all the options:

Some of Cree terms yet need some validation by Jean / Arok.

[aarppe]

• Interface language / pîkiskwêwin ta-âpacihtâhk
  • nêhiyawêwin / Plains Cree
  • English / âkayâsîmowin

---

• Dictionary sources / itwêwasinahikana
  • Cree : Words / nêhiyawêwin : itwêwina
  • Maskwacîs Cree Dictionary / nêhiyaw-pîkiskwêwinisa
  • Alberta Elders’ Cree Dictionary / alperta ohci kêhtê-ayak nêhiyaw otwêstamâkêwasinahikan

---

• Labels / kā-isi-wīhcikātēki
  • plain English / mosci-âkayâsîmowin
  • nêhiyawêwin / Plains Cree
  • emojis / kiskinowasinahikāsowina
  • linguistic / kâ-nitawi-kiskêyihtamihk pîkiskwêwina

---

• Features / kîkwây kâ-nitawēyihtaman ka-wâpahtahikawiyan?
  • show morpheme boundaries / wâpahtahin tânisi ê-isi-pâh-piskihcâyâki itwêwina (êkosi ta-nisitohtamihk icwêwinisa)
  • show Cree words translated into English phrases / wâpahtahin tânisi kâ-isi-âkayâsîwastâhk pakaski-nêhiyaw-itwêwina
  • show English phrases translated into Cree words / ?
  • show synthesized pronunciations of Cree words / wâpahtahin tânisi ê-isi-nêhiyawêhkâsomakahk ôma âpacihcikan

[aarppe]

Based on our Tech Team meeting discussion, the desired order of implementation would be the following, in part due to "customer" demand and in part due to the necessary components already being implemented:

1. Labels (making use of crk.altlabel.tsv)
2. Dictionary sources (among currently existing ones, CW vs. MD, for now)
3. Behavior + Interface <-- since these require further backend + frontend + linguistic work

[eddieantonio]

@aarppe: there's no way I will be able to implement this feature by the end of this week, and I'm off next week. I suggest we deliver this feature in tiny, incremental chunks. I have grand ideas for how the final product should look like, but I think at first, a toggle that enables "traditional/linguist mode" and one that enables "beginner mode".

In later iterations, we can customize each and every setting. e.g., I personally want full inflectional class descriptions AND emoji, because the emoji help me scan results a lot quicker.

[aarppe]

@eddieantonio I can imagine that this wouldn't necessarily happen quickly, but finally getting started on it is good enough. Having two overarching modes that implement and aggregate a set of settings was one of the suggestions in implementing optionality, so we can well start with that. But on the longer term I would really want to see full optionality (configurable via such a settings page/pop-up) so that users can choose exactly and specifically what they want. For instance, I could imagine that one could select multiple alternatives for an option, say just linguistic labels, or just emojis, or both linguistic labels and emojis - the settings page would allow for that.

[eddieantonio]

Would the pop-ups be in reverse?

That is, for the community mode, what you see initially is 1) the emojis and the 'like: X' text, and secondarily in the pop-up 2) the linguistic labels (long 'regular transitive animate verb' and short '(VTA-1)').

And for the linguistic mode, you'd initially see 1) the short linguistic label, e.g. VTA-1, and below that the full linguistic label 'regular transitive animate verb', but then secondarily in the pop-up 2) the example word case 'like: XXX' (but perhaps not the emoji).

Eventually I'd think we'd want to include the nêhiyawêwin labels in the mix.

Originally posted by @aarppe in #729 (comment)

@aarppe: could you please illustrate what you mean here? #729 was a way to get a quick turnaround for the customization (so that you have something to show AEW!)

[aarppe]

The linguist mode could work as it is, with the pop-up, but for the community mode you'd see something like the following in the pop-up (i.e. the example case in like: wîcihêw):

[dwhieb]

Arok sent us a revised version of the Plains Cree translations of the interface. I've updated the above comment with the new translations:

#708 (comment)

[aarppe]

@nienna73 Now that we have more things to choose on our options page, we could implement its contents bilingually as specified in the comment about: #708 (comment)

[aarppe]

With the exception of the interface language, the options have been implemented, though we still would want to provide Cree translations alongside the English option texts (#1137).