Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add nêhiyawêwin text to settings page #38

Open
nienna73 opened this issue Mar 21, 2023 · 1 comment
Open

Add nêhiyawêwin text to settings page #38

nienna73 opened this issue Mar 21, 2023 · 1 comment

Comments

@nienna73
Copy link
Contributor

If we add all the translations directly to the page, it'll clutter the page. So instead, we can make two tabs at the top: English and nêhiyawêwin and render the settings in that language based on which one is chosen.

Implementation-wise, I see this being two different files that are rendered based on which one is chosen. So the CreeSettings page with actually be three pages that look something like...

BaseSettings:
show the tabs
have the logic for which settings to show
render the correct settings

English settings:
the current settings page

nêhiyawêwin settings:
the version of the settings page written in nêhiyawêwin

One of the last two pages gets displayed in the main content of the page.

@aarppe
Copy link

aarppe commented Mar 23, 2023

Much of the Cree / nêhiyawêwin translations can be found in the attached DOCX file:

  1. Interface language / pîkiskwêwin ta-âpacihtâhk

    • Note: = “language to be used”. ayamiwin does mean “language” in almost all Cree dialects, but is not common in Plains Cree, having been supplanted by pîkiskwêwin.
  2. Labels / kā-isi-wīhcikātēki

    • Note: “those which are so named”

    a. linguistic / kâ-nitawi-kiskêyihtamihk pîkiskwêwina *
    b. plain English / mosci-âkayâsîmowin **
    c. nêhiyawêwin / Plains Cree
    d. emojis / kiskinowasinahikāsowina ***

    • Note: “when languages are studied” = language study = Linguistics
      ** Note: this may work. We were thinking of wêhci-âkayâsîmowin “simple/easy English”, but this may sound condescending to some.
      **Note: cikāstēpisona is “pictures” in the sense of photographic images. This is not appropriate for emojis. The words we suggest would mean “guiding/teaching symbols”
  3. Features / kîkwây kâ-nitawēyihtaman ka-wâpahtahikawiyan
    Comments and suggestions for Cree itwêwina interface-JO-AEW-2.docx

    • Previous: Behaviour / isîhtwâwin – this is more cultural norms and not
    • Note: could this not be “Features” in English rather than “behaviour”?
    • this simply needs more thought - If it was “Features”, perhaps it could say kîkwây kâ-nôhtê-tôtaman? (“what do you want to do”) or kîkwây kâ-nitawēyihtaman ka-wâpahtahikawiyan? (“what do you want to be shown?”)
  4. show morpheme boundaries / wâpahtahin tânisi ê-isi-pâh-piskihcâyâki itwêwina (êkosi ta-nisitohtamihk icwêwinisa)

    • Note: “show me how the words are divided into pieces (so the little wordlings will be understood)” You could go with just the part outside of brackets.
  5. show Cree words translated into English phrases / wâpahtahin tânisi kâ-isi-âkayâsîwastâhk pakaski-nêhiyaw-itwêwina

    • Note: “show me how fluent Cree words are translated into English”
    • Important Note: this is a placeholder and not strictly accurate, as the online dictionary is nowhere near following through on a promise of translating Cree words into English phrases or sentences. Right now, the only inflected forms that translate are those with one of the three tense/aspect markers kî-, ka-, wî-. No other preverbs (or prenouns) work in translation. (I believe we have now added in the possibility of translating kî-wî- as a unit?). Clearly some things need to be cleaned up in the translation of some basic paradigms before we start making claims about being able to translate anything beyond the very basics.
  6. show synthesized pronunciations of Cree words / wâpahtahin tânisi ê-isi-nêhiyawêhkâsomakahk ôma âpacihcikan.

    • Note: “show me how this tool pretends to speak Cree / speaks Cree artificially”

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants