Reminder: what to report and what not
Thank you for all those who are tackling this course while it's still in beta!
There are still quite a few rough places left.
Three big ones are general issues that we as course contributors cannot work on -- it's up to Duolingo developers. We've reported those issues to them and we hope they will be fixed soon, but we don't know when. In the mean time, please do not report these issues as that will not get them fixed any sooner. Reporting them will just waste your time and ours.
Capitalisation: capitalisation is often off, especially in three major areas: (a) forced lowercase (I think) in "fill-in-the-blank" exercises for the words that go into the blank; (b) forced uppercase for the first word in multiple-choice "choose ALL that apply" exercises; and (c) forced case-matching in distractor sentences in multiple-choice exercises, where a replaced word will have the same casing for its first letter as the word it replaced.
Hints: please do not simply report "hints are wrong or missing", as that report gives us no information. Please also post a comment on the relevant sentence discussion saying which hint on which word is problematic and for what reason. Thank you!
Audio: we are currently adding audio to the course, but it's a manual process limited by volunteers' time. So some sentences have audio but many others do not. Sentences near the beginning of the course are more likely to have audio than sentences later on, as it will take a while to record everything. Please do not report missing audio. Reporting it won't make us work any faster; we're doing what we can. And if there is a problem with the audio, please also leave a comment with the sentence discussion with as much detail as possible -- e.g. whether you heard a male or a female voice, whether the problem was with single-word audio or with whole-sentence audio, and which particular word had a problematic pronunciation and what it sounded like compared to what you had expected. Also, one thing (related to the general capitalisation problems) is that if a word starts with a capital Q, you may hear audio for a word with a lowercase q (which is a different letter in Klingon), e.g. you might hear the audio for qIp "hit" when you click on QIp "stupid", or you might hear no audio at all for Qe' "restaurant" because the system looks for (and fails to find) an audio file for qe' (which isn't a word). This is also a known problem that is being worked on (as of June 2020), but it may take several months before a fix is available. Please don't report this kind of error as "missing audio".
Also, please do not report "sentence is incorrect or has an error". That's too vague, and we don't know which one of possibly hundreds of alternatives you might have entered or been shown by the correction algorithm. Instead, if you believe that there is a mistake in the Klingon or the English, please report it in the sentence discussion. Please quote the entire sentence that you think is incorrect, say what you think is wrong with it, and what change you think should be made.
Saying "My answer should be right." or "Why doesn't 'look' work?" or similar things that do not quote the entire sentence are almost impossible to answer, because we cannot see the sentence that you entered or the "correction" that you might have been shown -- and often, a problem is not with a particular word but with the word order or some other thing that requires the context of the sentence.
Please give as much detail as possible in your reports.
If you see an error or an error message, a screenshot would be great if you can get one. (Upload it to an image sharing host somewhere and paste a link to it into the discussion.)
Finally, if you translate a sentence and your translation is not accepted, but you're fairly certain it should be, please DO continue to report those missing translations as "my translation should be accepted". These reports are useful.
If you are not sure whether your translation should be accepted, or if you want to add something such as "this is the way we say it New York/Canberra/Delhi", then post about it in the sentence discussion.
Please bear in mind, though, that we can't include usage from every single part of the English-speaking world; for example, "yinz" is not going to make it in even if it's very common in some regions, and "I haven't a book" might not be accepted since it's not as common as "I don't have a book" or "I haven't got a book".
(If in doubt, use [general] American English wording and grammar, as that is most likely to be among the existing alternatives already. For example, if you learn that yopwaH means "pants", think jeans rather than underwear.)
P.S. If some of those issues, such as missing hints or missing audio, make things too difficult for you: a beta course is not right for everybody. It may be better if you take a break and check back occasionally to see whether the course has come out of beta and those issues have hopefully been fixed.
On the topic of audio, rather than just checking "audio is wrong or missing," it would be more helpful if you reported, "The audio is too soft/too crackly/has a weird pause" or "The speaker seems to be saying, "De'wI'vam vIHoHrup" when she's supposed to be saying "jajlo' maHIv." Specify if it's the male or female speaker you hear the problem with, and we'll try to re-record.
Qov, I believe I remember seeing on a sentence discussion that you were willing to re-record some of the distorted but otherwise correctly pronounced entries. EDIT - I mean those that are in your voice, not those done by others.
I've noticed that entries vary a decent amount, but are either awesome, good, or what I think might be from the time when Duo re-processed all your files through a "what would this sound like if played in a submarine that is actively being flooded" filter.
I've been going back over some of the course and I don't hit these distorted entries very often, but when I do, would you like them reported, or is this more work than necessary?
I only just saw this, so I'm not sure if you will, but YES, I do want to know about the underwater recordings. You can report them individually, in the forums or you can cut and paste the sentence or word that is bad into this thread: https://forum.duolingo.com/comment/37799053.
I'm glad to hear that they are becoming fewer. They are clustered around the Cause through Time Suffixes units, because I was working fairly systematically at the time, but sometimes I jumped around, so they are in other units, too.
I'm not sure if this is an example of a systematic capitalization issue or not. While strengthening the "Pronouns" chapter, I got the "Select the missing word" question "tlhIngan jIH 'ej torgh ___ pongwIj'e'.". All the wrong answers were correctly capitalized ("bIH", "chaH" &c.) but the correct answer was miscapitalized as "'oh". Also, the "Discuss" button wouldn't work.
Yes, the 'oh thing is one of the effects of 1b above.
Sometimes deleting and re-adding the distractors (wrong words) lets them have proper capitalisation, but I haven't figured out how to change the capitalisation of the correct word reliably; it's usually uneditable and all-lowercase. (But sometimes uneditable and in some mixed case, not always the right one....)
I'm not sure about the status of Discuss not working in fill-in-the-blank exercises.
Neither of those two spellings is a possible word in Klingon. Each syllable must contain a vowel, and no syllable can begin with two consonants. The bI- prefix has a capital I as its second letter, and the verb yIt walk likewise has a capital I in the middle. The vowel I ("eye") and the consonant l ("ell") are never interchangeable. They look the same in most sans-serif fonts, but if you look closely you'll see that the "ell" has a little rightward curve at the bottom in the font used by Duolingo.
Duolingo's typo detection seems capricious to those of us not privy to the programming behind it. I sometimes wonder if even the programmers understand and can predict its behavior.