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 five major areas: (a) forced lowercase of the vocabulary words in the preview of a lesson (for those who don't have crowns yet); (b) forced lowercase (I think) in "fill-in-the-blank" exercises for the words that go into the blank; (c) forced uppercase for the first word in multiple-choice "choose ALL that apply" exercises; (d) 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; and (e) hints may appear for a word that differs in case (e.g. the hints for Qach might show the hints for qach instead or in addition, or vice versa).
Hints: words that begin with an apostrophe, such as 'IH (beautiful), 'ej (and), or 'oH (it) do not display hints. Do not report "hints are wrong or missing" in this case -- it's a general issue and it's already on the screen. Reporting won't make anyone more aware of it or get it fixed faster.
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.
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.
LOL I don't know why. At the moment that sounds more like a Ferengi Party gone wrong, a Borg Attack and...RedShirts are the ones at ThatPlace (SIR BORG ATTACK(WHERE) STARBASE SOMEPLACE[please tell me I was just trolled thinks the captain])
Please put a link to this info in the course. Or "sticky" in the discussion, if that is possible.
When I was beta-testing the Esperanto course some years ago, I received similar information from the authors personally and through other channels, including info about what they could see/do in the backend and what not. Without that information I would perhaps have done much nonsense work and been causing much extra work to them, too.
Thanks for the info, very helpful. And Yes, I'm loving the Klingon (harder than any other language I've learned), and YES, I eagerly await the audio as the pronunciation is a very difficult aspect for me thus far, that will help immensely when it gets online. Again, thanks for the course, it's awesome!
Your course is incredible and I appreciate the thorough responses in the discussions so much! thank you!
Is the no availability of repeating lessons connected to this class still being in Beta??
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.
For me the "Discuss" button didn't work either yesterday, hence why I sent you the screenshot over Messenger.
There is an update to Issue #3. Audio is currently being added to the course. It is a long slow process, so we ask that you still please not report missing audio until you notice that it has become a rare thing to have missing audio. If you want to check it out, some audio is already on some of the exercises in the early Skills.
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.
Question: Anyway to work around the bugy sections with ' 'oH a tone today for phrases? Googles isn't coming up with ideas what some of them should say? I am guessing hitting skip (show the answer) and pasting (to work around it. Will need to suffice till the DuaLingaCoder'aTrans Er the DuoLingo weby-web people can fix those.
Mizinamo, you should edit this to correct #3 into saying audio is being added slowly.
Good idea. I've edited #3 now.
I wonder if you should also add a link to the bug report page for numbers 1 & 2.
I thought about it briefly but decided that what I wrote above still stands:
it's already on the screen. Reporting won't make anyone more aware of it or get it fixed faster.
At least I assume that programmers are aware of all of the issues in 1 and 2. So I'm not sure whether users' bug reports would be helpful at the moment.
Just started the intro courses and--is the pronunciation supposed to be super repeated, with multiple speakers saying the same thing at different volumes at different intervals?
Edit: yeah, the audio is definitely bugged out.
Ideally the volume should be all the same volume, but the contributors are all using different equipment, so you may hear variations in quality and volume.
As for "super repeated", I can't figure out what you mean, but it doesn't seem right. Each Sentence should only play once (unless you click on the blue speaker to hear it again). And each time you encounter the sentence, the software should pick one recording and just play that one for that particular encounter.
If something else is happening, please describe it in more detail so we can bring it to the attention of the programmers.
I tried without headphones and it works fine, but with headphones I get different versions of audio sometimes.
As for what happened before: The 'select words in bubbles' for "Qapla', torgh": When I clicked the blue audio button, it played, "Qapla', tor-" and then around when "tor" was being said, another, Arabic-sounding voice also started saying "Qapla" before both cut off. There was several seconds of silence before one of the voices abruptly said "torgh."
I tried again after replugging headphones and now someone cuts off at "tor-" again, but about a second later a new voice properly says "torgh."
Another example: The 'Write this in English' for "batlh" repeats the word twice.
That definitely sounds like some sort of bug. If it happens again, go to the sentence discussion for that sentence (using the speech bubble next to the flag after you get graded) and report it there. Also mention what app or program you are using (such as Chrome for Windows 10).