Reporting in the Latin Course - Where, What, What NOT, and How to Report
First things first - thank you all for being so eager to help improve the Latin course! The enthusiasm (and the help!) is appreciated.
Now, on to business. :)
Where to report
Please do not report in the sentence discussions!
Reporting in the sentence discussions is far less likely to be seen by the contributors, not as helpful because we can't see your exact answer (so we can't tell at a glance if it's something we've already changed that isn't yet working on the user-side, if you actually had a typo, etc.), it adds clutter to the discussion that will only confuse other learners after the problem is fixed, until someone sees it and deletes it (which is more unnecessary work for the moderators), the tools we have in the Incubator for dealing with reports can't do anything with them, etc.
Instead, please use the report button in the lesson. This goes directly to the contributors in the Incubator, where it will be seen sooner or later, gives us more useful information, works with our tools, and helps keep the forum clean and reserved for questions and answers as it's intended to be. Here is where the report button is located:
What to report
- Bad audio
- Missing or incorrect hints (but bear in mind that the hints are for the entire course, not sentence specific, so a hint may apply to one sentence but not another)
- Missing translations IF there is no error at all, not even a typo
- Incorrect existing translations
What NOT to report
- Anything containing a typo (there's a good chance it would have been accepted if it weren't for the typo, try again without the typo before reporting)
- Bugs (the contributors can't do anything about that, send a bug report instead)
- Other technical issues (those belong in the Troubleshooting forum)
- Anything in a language other than English or Latin (sorry, this course is Latin for English speakers and other languages will not be accepted)
- Anything containing an emoji (we will not be adding emojis to the translations and are not responsible for your answer being rejected if you use them)
- Questions (we have no way to respond)
- Profanity/Insults (missing translations are nothing personal, and not generally because we don't know the language, things just get missed. And we are real people reading the reports, not robots)
- The primary English answer using American English (Duo is an American company and primarily uses American English. If a British English answer is not accepted, report that, but don't expect it to be made the main answer)
- Sentences ending in prepositions (no, it's actually not a capital offence)
- Sentence not agreeing with your personal preferences (teaching you a sentence about a particular view is not pushing anything, it's teaching you how to express your own views and understand when others express theirs)
- Anything not grammatically correct, even if it's a literal translation (eg. "Marcus is boy" will not be accepted, it must have an article)
- Anything that it's already been explained in the sentence discussion why it isn't accepted (if you want to argue, do so in the sentence discussion politely and with sources)
- The audio using the Classical pronunciation instead of your favourite
- A translated/anglicised version of a name (no, we will not accept those, keep names as they are)
- The lack of slow audio (Latin uses recordings, not TTS, so will not have turtle speed)
How to report
Before reporting anything, please read the entire sentence discussion! If there's nothing in the sentence discussion about it, check a trusted source (or at least do a quick Google search) to make sure you're right. An example of where this would save us time is "Quis est ea", for which we've received multiple reports that it should be "quae", which is either plural (in which case the verb would not be "est") or a relative pronoun (when we need the interrogative pronoun). That's only one example, there are many others.
- Report missing translations as "My answer should be accepted". If you have details or an explanation to go with it, you can add these as a freewrite report (preferable if you have the option). Freewrite reports don't get tied to the answer you submitted, so it's good give a little context. Only use a sentence discussion to explain an answer if you don't have the freewrite option and it really needs an explanation. The contributors do speak both English and Latin and rarely will need an explanation, usually it will be quite obvious, including British English translations.
- Report any other issue with a sentence in a freewrite report. If that option is unavailable to you, you may use the sentence discussions as a last resort. Only do this if absolutely necessary, meaning there are no other options available (this is most likely to be the case with a translation that is accepted but should not be).
- Report issues with image exercises in a discussion in the Latin forum. Remember to note which exercise it concerns and the exact problem.
- When it comes to the report option "This sentence is unnatural or has an error", it really is too vague to be of any help. Clearing these reports is just a time sink to us.
- Report audio issues as "Audio does not sound correct." Do not report audio just because it uses Classical pronunciation.
- Questions go in the sentence discussion if they're relevant to its content or grammar, and in the relevant sub-forum if not. We're unable to directly answer questions asked through freewrite reports; it's a one-way channel.
Before reporting that your answer should be accepted, please read the sentence discussion and check that your answer doesn't contain:
- a typo
- an untranslated word
- a duplicated word
- a disagreement between the subject and the verb
- an "a/an" error (it's a classic)
- an unnatural word order
- an emoji or non-standard character
- a non-standard contraction
- slang or -very- regional regionalisms
- an English word that hasn't seen regular use for the past 500 years
- a translated name
- "Corrina" - it's "Corinna", and you'd be surprised how many reports I've seen with "Corrina" already
And double check that it isn't missing:
- a word
- an apostrophe
- an article where one is required in English
If your answer is completely identical to the translation displayed, in spelling, punctuation, and capitalisation, and still graded as incorrect, this is a bug. Any translation you're shown is present in our list of accepted translations. If you want to report it, please do so through the bug form, and remember to add a screenshot.
We know there are many missing translations at present, especially with Latin word order. We are working on it! Unfortunately, it takes time for the answers we add in the Incubator to begin to be graded as correct, sometimes two weeks or even longer. We can't control that, so you may well have an answer marked as incorrect that we've already added. Please don't assume that this is the case, still report it (we miss things, we're human!), but bear in mind that, while it's frustrating to be marked wrong for something that's perfectly fine, we're doing the best we can for you. :)
We also know that the audio doesn't have the slow/turtle speed. This is because Latin uses voice recordings rather than TTS, and will not change.
If anything's unclear, feel free to ask questions in the comments. :)
Once again, thank you all for all your help!
Ah, thanks; I'll try to remember to use them (I already have an easy shortcut key for them from Danish).
I imagine that, much of the time, it's going to treat a single ligature as a typo, however, and not give me any opportunity to send a report; some sort of coded-in solution would certainly be better.
If you're not sure, don't report. Instead, ask in the discussion if it's acceptable (don't just post it, specifically ask "Is this also correct?", making sure to specify exactly what the entire sentence is). Then if it's confirmed it's fine and you run into it again, report away!
Also, please read what other people have posted before posting your own concern. The discussions get really long, filled with people asking the same questions that have already been answered. (And ironically those users seldom come back to read if their question was answered)!
There aren't millions on any particular discussion. :) If you have a question about a particular sentence, read the discussion attached to that sentence, it's not all that long, and if it's about something general rather than a specific sentence you can use the search function on the main forum page (or Google). :)
Trofaste, when I get an e-mail saying someone has responded to a discussion I'm following and I click on it, it no longer opens on the comment but at the top of the page. This has been going on for around 6 months. Did Duolingo make a change that is causing this or do you think this is caused by something else? It has become very time consuming trying to find comments on threads, especially if they have over 50 comments, and you know some discussions have 300 to 400 + comments. I have spent over 10 minutes going up and down this page trying to find the thread of a comment I wanted to read without any luck yet. I turned in a Bug Report months ago to no avail. Update: It took six months but Duolingo finally fixed the problem.
That's because the link changes to a broken one (for example the link to your comment changes to https://forum.duolingo.com/comment/33853120$from_email%3Dcomment&comment_id%3D34044750). Change %3D to = and it should work again.
They also work on the mobile browser, by the way.
Good comments and questions are upvoted, sometimes with a lingots. There are not millions, because I can read them all, in a few minutes, for each sentences.
Really, if you do like I do, read everything, you will see you'll progress faster, as the grammatical discussions teach us more than the course itself, and trying to answer other users' questions is a real challenge.
Doing a Duolingo course without reading the grammatical forum is 80% less efficient, at least!
Please people upvote the good questions or interesting answers, make them visible with lingots and upvotes.
I only report if I'm sure, as best as I can (I've had cases (in other languages) when right after reporting I realized that I had misread something ... But in these cases I seriously scold me! ;-)).
If I'm not certain, I go to the sentence discussion to see whether others have had the same issue, and to state the issue if this is not the case.
If after the sentence discussion I'm sure that I was right, I wait for the sentence to come up again, and report it.
Let's see what others think about it. :-)
(Cross-posted with Trofaste)
Even course contributors are guilty of misreading or using the wrong language sometimes... The number of times I've reported sentences about cheese and realised just after clicking the button that I had the wrong language, after carefully scrutinising my translation for any errors, is ridiculous. If you do it in good faith and make a mistake occasionally, we won't complain. :)
You mentioned something I left out and shouldn't have... Read the discussion to see if it's already been discussed before asking! About anything. If only everyone always read the whole discussion before posting the moderators' lives would be so much easier...
Hi, thanks for the course! I really think it is a great example of the best Duolingo can offer, a nice introduction and a gentle nudge "hey, try Latin" to the general population, and a new way to practice. Yes, despite the missing alternatives and despite being short and so on. It is the first version and it is in beta. And it is made by an awesome team of volunteers! And from what I've heard, you've been doing great and adding stuff really fast. I wish it existed ten years ago, that's my only complaint. Make a time machine and deliver it to my teenage me, she'll be grateful. :-) Thanks!
Freewrite reports are a field that let you type in a report yourself instead of using one of the checkbox options. They're located in the same place as the other reports if you have them. I believe they're currently only available on Android (maybe on iOS as well, I'm not sure).
Thanks for the clarification. I've reported a number of things using both the report button and the sentence discussion. Despite that, I think this is the start of what will be a great course. The course creators are to be congratulated and thanked for all their hard (and rapid!) work.
Thanks for the cohesive guide! I would like to point out that users can't take back reports, so that may be one of the reason why there are many bad reports. There have been several instances where I report a "mistake" only to immediately realize that I misread part of the sentence (Latina lingua versus Latinis litteris is a common one for me). I apologize for sending several bad reports!
That definitely accounts for some of them, but very likely only a small percentage. On a mature course, 95% of reports are useless (99.99% in the early skills, it's a bit lower in later ones where there are more advanced sentences where it's easier to miss something or make a mistake), and I'm doubtful that the majority of those would be retracted. But I agree that it would be nice if we could.
It's hard to concentrate on the languages I SHOULD be working on (and the laundry I SHOULD be putting away ...) when I've fallen so happily in love with the Latin course. Thank you for the amazing amount of time and paperwork you have put in to this irresistible cat toy of a game.
I'd like to remind everyone to please be mindful of our guidelines. We all have personal opinions towards subjects or content that we may come across; however, we wish to keep the forums a safe environment for everyone. Simple respect goes a long way.
Instead of having a discussion here, I encourage users to report content that they believe should be reported. This can be done by using the report function in sentences, or by reporting the sentence or phrase in Abuse.
I've seen people suggest this, but it is not an option in the Duolingo backend. You have to use the recorder there as far as I understand. Perhaps someone with more Duolingo audio experience or on the staff can chime in about a workaround? Creating the audio was frustrating sometimes and we are trying to make it better. I know how to use Audacity and would love to use it for this project if possible, but I will need some guidance.
Any guidance on usage of simple present vs present continuous, like "you visit" vs "you are visiting"? It seems like the course so far uses one or the other or both for different sentences.
Also regarding synonyms, like nice/kind? And verb phrases, like making a journey, going on a journey, being on a journey, or just journeying. Can you give us any general rules for how far you want to go in accepting these kinds of variations?
Latin doesn't distinguish between simple and continuous, so both should be accepted as long as they fit the English sentence. If one isn't accepted, check to make sure there's no other error and that the sentence actually makes sense, and report.
Synonyms - check a good Latin/English dictionary. Keep in mind that words often used as sunonyms aren't always full synonyms (the ponies are nice vs the ponies are kind, for example) and make sure the meaning is the same or a valid meaning of the word you're translating. If you're not sure, then that's what the sentence discussions are for!
Verb phrases - don't go archaic (the same rule applies to English sentence structures as to words, if it hasn't seen regular use in the last 500 years don't report), but apart from that, as long as it's corect English/Latin that makes sense in the context and either means exactly the same or is also a valid meaning, go ahead and report, after checking the SD.
Thanks very much for your ongoing commitment to this course. There are a lot of us out there who have always wanted to learn Latin but in the same manner as “living languages” are taught. We’re very happy you can provide us with such a course. Please keep up the great work!
Unfortunately, there's nothing the contributors can do about that, as typo grading is done by an algorithm we can't control. I'm doing my best to get staff to prioritise improving the algorithm, but dev time is limited and they have many priorities to juggle, so it may not be done as soon as we would like.
I finished the two branches of the Latin course (early Nov, 2020) and now give my impressions: I liked it. It was fun. I especially appreciate the humor with the drunk and disruptive parrot(s). The course does a nice job of introducing important socio-cultural elements reflected in the Latin language such as the salutatio. As a beta version that only has two branches, I think I initially was expecting a lot more, but now that I've finished I see that it's clearly a work-in-progress. I tried to click occasionally on the report button when I found a problem. Not a fan of importing anachronistic terms such as California, New York, and coffee. I reported a few of the stand-alone velim sentences, but the various uses of subjunctive will become clearer to learners when the subjunctive branches get built, I would assume. Overall, it's a strong foundation on which to build. Thank you to those who took the time to build it. I have to admit that I was sad when there were no more branches!
Thank you very much!
but bear in mind that, while it's frustrating to be marked wrong for something that's perfectly fine, we're doing the best we can for you. :)
I know that. It's really amazing: I've got a reply to my report within hours. Absolutely amazing.
Many, many thanks for everything you do -- and I'll try to keep your reporting guidelines in mind.
Most of it does, yes. But there are some differences between courses (for example, for most courses we would tell you not to report a word that hasn't seen regular use for the last 500 years in either language!) and some teams have slightly different preferences (eg. some would prefer the ultra-vague reports to SD comments),and we want to keep the number of stickies on the general forum limited, so personally I think it would be better for every course to have its own version. Some actually do already, I borrowed extensively from the one Deliciae wrote for the Norwegian course (in the Weekly Norwegian series).
Thank you guys for posting these guidelines. I hope my submissions have been in line with these standards so far. :)
Something that I'd really like to recommend to admin is that they include a short freewrite report option on all platforms, in addition to the boxes, in all courses, especially in older ones. There is nothing more frustrating than finding an error which does not correspond in any possible way to the boxes present. There should at least be a box marked "other."
Btw, I just checked a report box in the Latin course. The possibilities were: audio unclear, hover suggestions missing or wrong, or the Latin sentence had a problem. But what if the English translation given were wrong? Or something else?
From what I recall of your comments that I've seen I think you've done pretty well. :) But now you've read this I'll have higher standards... ;-)
Believe me, we'd like freewrite reports to be available on all platforms as well, and we've asked for it. The choke point is probably mostly that we're asking for some modifications to the freewrite system first to make them more useful for us (on reasonably mature courses 99% of freewrites, like everything else, are useless, and we get more abuse in freewrites than any other report type).
There are often both "correct solution" and "sentence" error reports. The "correct solution" is for the sentence you were told is the correct translation, the "sentence" is for the sentence you had to translate. Those are too vague to be much help in most cases, so use "my answer should be accepted" if at all applicable (if you were shown a translation with "a apple" and had "an apple" rejected, that will do the trick), freewrite if you have it. If you have no report options except for audio and hints, you can use the SD as a very last resort. Make sure you're very clear on exactly what happened, remember we can't see anything, and also mention what device you're using and what report options you had. That will let us tell you if one of them would have been appropriate for the situation, and helps us keep up to date on what options are avaiilable.on different platforms.
Yes, that is exactly what I have done. Well, no, sometimes, rarely, I just throw my hands in the air and don't report anything, just move on. I am sorry to hear that there are vicious people out there that would abuse the reporting feature. I guess a lot of people cannot keep their emotions from taking over their brains.
For those of us who don't abuse, freewriting would be sooo much better. Just a few words of explanation in a box versus opening up the SD, searching if anyone else has discussed the concern, and getting interested in other user's concerns, responding to them... that's exactly why I sometimes spend hours on Duolingo doing what could be done much, much faster...
@iiai: Freewrite reports contain profanity/abuse/insults far too often for my liking, in my experience. I might see them more often in my main course (Japanese) just because it's got a high volume of users - or maybe because it's inherently a very frustrating language for English speakers to learn. But I find myself regularly insulted and defamed in freewrite reports, so sometimes I'd honestly prefer that they weren't on any platform at all. It's hard to want to do your best to improve a course only to come across people sending you profanity-filled insults on a regular basis, especially since some of the problems (such as audio) are out of the contribs' control...D:
@ehartz, wow, so sorry to hear about that abuse. How about this idea: to submit a freewrite, or indeed even any report, you have to enter your username and real-life name? I think the anonymity of the reports encourages abuse. They might think twice if they have to sign their name.
@jairapetyan It would be reduced some, but from the number of people who happily spam the forums where their username is visible to the whole world I don't know how much it would help. We have some other things in mind, but unfortunately dev time is limited in the Incubator just like everywhere else, and there are many other things we're asking for as well.
I just started the latin course a couple of hours ago. I use a Samsung tablet. On one of the pages the answer (multiple choice) was written over the printed text. I tried to report it but I had only the 2 standard reporting options. I know that you probably have very little to do with programming the user interface, but how do you report something like that?
I do not have a reply option for your answer, Heike so I just edit the first remarks.
I would love to use the bug report, however i do not seem to have one on my tablet.:-)
In this case, you should use the bug report and include a screenshot.
Yes, that's it. If the audio is really, really bad and you get a listening exercise you can report it for a TTS language as well (if it's really bad we can disable the type what you hear), but don't bother otherwise as we can't disable it anywhere else and can't improve it, and in all likelihood already know just how bad it is.
I'm not sure I understand. :( I started reporting audio, whenever I would not have been able to spell out the sentence from listening only. Is that the right approach or better not report such cases? Also, there was one case, where "crustula" was emphasized on the second instead of the first syllable, but I'm not 100% sure, if that is incorrect or legit. Wanted to report it just in case, but then the app broke down, as it does every once in a while on my phone :S
Just a small sample of a few reports I've cleared today that we don't want:
On "Puer non dormit, sed puella dormit.":
- The blog is not sleeping but the girl is sleeping.
- The bot does not sleep but the girl sleeps.
On "Soror in urbe est, sed frater domi est.":
- The sister is in the city but the bother is at home.
On "Livia is a woman.":
- Livia puella est.
- Livia est puella.
On "Corinna is a girl.":
- Corrina puella est.
- Corinna peulla est.
On "Quis est mater?":
- father not mother
You get the idea...
Believe me, we do that kind of thing too. After going through a couple hundred reports I can find myself staring at one wondering why it isn't green (if the reported sentence is entered in the accepted translation, it shows as green) for a full five minutes before I finally realise there's an entire word duplicated or missing.
No problem! :-) Our brains are used to automatically filling in the letters they expect from experience.
This is what makes reporting so difficult if you are not aware of the issue. We have to read our supposedly correct sentences extremely carefully before sending them.
It is a balancing act knowing whether to report. For example I myself have reported a number of things and received your very pleasant automated replies as a result when they are approved however I also suffer from dyslexia so I might not see that I’ve got a spelling mistake. Literally I might be completely and utterly unable to notice there is a letter missing - so given your very firm stance on typos It becomes an issue of report and irritate you or don’t bother and hope someone else will do so. Which do you prefer?
I also feel I must say that it’s simply not possible to ‘try it again without the typo’ unless you do the same lesson multiple times and hope that that particular question will come up again. We don’t have a ‘go back and do it again specifically button’ do we?
The firm "don't report if you have a typo" is primarily for two kinds of people. Those who know they have a typo and report anyway (many people report things they feel should be accepted as typos, which is something we can't control), and those who don't check. If you've checked carefully and don't see a typo, go ahead and report. If you're reporting in good faith, having done due diligence, we won't complain if you make a mistake sometimes. It happens to us all, even to course contributors who have spent many an error practicing their typo spotting skills. (EDIT: And this was a perfect example... I really did not see that I wrote "error" instead of "hour")
My experience is that when doing lessons, if I make a mistake on a sentence, I always get that sentence again in that very lesson, usually at the end, which means you're not only getting another chance but you're getting it soon enough to remember what you tried before.
Yes, the decision between what is and isn't a typo is made solely by an algorithm we have no control over - although in some circumstances we can ask staff to add special handling for a specific case - which usually declares it a typo if it's only one letter off and doesn't make another word. Unfortunately, with most languages it's not very good at determining what is another word right now.
Sentences ending in prepositions
I was given the sentence "Unde venis?" and the answer "From where do you come?" was not accepted. I reported it. It seems that prepositions at the end of a sentence are actively preferred over ones at the beginning.
Report any other issue with a sentence in a freewrite report.
In my experience, that option is available only on the Android app. When will it be added to the website?
They're not preferred, it's just whatever is most natural. "Where do you come from?" is more common than "From where do you come?", so it makes sense to use it as the main translation. The other should of course be accepted, it's just one answer that was missed when the sentence was created.
We have no idea when freewrites will be added to the website. We've asked for it, but there are also some changes we want made first, which is probably a large part of the hold up.
I tend to forget that the norwegians have started the unlikely rumour that they have a language of their own. (Until 1907 the official written language in Norway was Danish.....Hmmm that is now more than 100 years ago - tempus fugit).
Still, norwegians are extremely nice people so i'll just pretend to go along with the rumour.
Consonant gemination is a part Italian kept from Latin, and the biggest source of mistakes for foreign people learning Italian. Very few language geminate EVERY consonant, which makes it phonetically hard to recognise for those who don’t. Even people who’ve been in Italy for a long time and speak very fluently still make mistakes with doubles.
Loving the Latin course so far, but I have had quite a lot of perfectly correct answers marked as incorrect, even when they match the suggested correct answer word for word. The main problem is that the option to report 'My answer should have been accepted' is missing from the list of reportable incidents. Thanks so much for providing the Latin course for us :)
Could they put a warning in the course when we enroll to a new course. Because I'm very tired to see that the forum are flooded by reports about sentences, word orders, and pronunciations.
I know they don't do it on purpose, they simply don't understand how Duolingo works, even some people who attended many courses until the level 25 seem to misunderstand the way to report, and the purpose of the forums
So, I think Duolingo is guilty for this, more communication and information should be provided to the users, it would save a lot of time to everyone.
I wish we could have this, but it's not something we can do ourselves and, as usual, dev time is limited. And, unfortunately, many people wouldn't read it... It's clearly stated when a course is in Beta but some people still seem to think it should be perfect, which no course on or off Duo ever is even after years of work, let alone in Beta.
I have just reported a bunch of audio missing as other. I apologize as I just found this forum to follow and read your reporting guidelines. When I see audio missing, I think in terms of the audio being completely missing, rather than part of the audio missing. In the following example would this still be reported under audio. What I have noticed is that some word's audio is missing sometimes from a word bank word and sometimes from a hint and sometimes it is not every word in the sentence and other times it's every word in the sentence. Would all these types of conditions still be logged under audio missing as a person cannot comment which part of the audio is missing? Is it more helpful to have more information that the other category provides or as procedure do you check all aspects of the audio for a given lesson or sentence?
Yeah, I have been doing this too.
I often come across the same sentences twice in a lesson, one from Latin to English, and the other reversed, but often one of them contains the audio while the other doesn't. In these cases I report the audio as missing.
I am, however, not sure if it is intended to be like this or not. Maybe it's a feature?
The reverse sentences never contain audio. And the reason for this is very simple actually: they're in English. There's not much point in having English voice in a course for Latin when you can read the sentence anyway to be able to answer in Latin. If a sentence in Latin however does not have voice, you should absolutely report it. Especially if you're dealing with a type-what-you-hear exercise. :)
I completely disagree with the policy of not accepting anglicised names, for two reasons:
Most other courses which I am doing support this (e.g. Spanish, Gaelic) - Duolingo tends towards the informal style of language learning in which its okay to anglicize a name.
Latin has a long history of adapting names to the vernacular. In fact, most of the famous Romans are better known by their anglicized names in the English speaking world.
This is so useful! I'll be doing the Latin course sometime in the near future, so I'm looking forward to it!
I just want to apologize for being an idiot and abusing the report function for the first several days. I was using the android app from the very beginning so I didn't realize there was a comment section, forum, or heck, anything not in the app. So when it just dropped me in to translation exercises, I assumed that was it, and since the only icons are "flag" or "thought bubble" I just assumed that the bubble was for technical feedback and the flag was for questions/feedback/errors on the questions.
Salve. Thank you volunteers for making this course. I am a native Dutch speaker. I have been studying for the last year french, some Spanish, looking again into the German language and maybe will try Italian in a year (moving a bit forward from this tongue and trying Arabic, new challenge : ). Some words are in my native language. And they are explained to me now. Thank you makers.
How should improper (though popular) standard English translations be treated?
Multiple times through the early part of the course, (for example) "Me male habeo" is translated "I feel badly." But despite the popularity of this idea, it is not correct English: because "feel" is considered a verb of being, it takes a predicate adjective modifying "I" (rather than an adverb modifying "feel"). Thus, "I feel badly" is roughly equivalent to "I am incapable of feeling things," rather than "I am having negative feelings" (which would be "I feel bad").
I have hesitated to report this, since (a) it's a common (even faddish) idea in modern English, and (b) I thought perhaps the poor English might have been used intentionally to draw out some specific grammatical nuances of Latin.
I'm sorry if this has been asked, but I did not see it in the 250+ comments. When I report something, should I expect to receive a response, and if so, how? I have reported a (not large) number of my responses as should be or should not be accepted, but have no idea if my reports were ever received. Unfortunately, I cannot give you a sample of what I have reported, as I did not write them down, and do not see any way now to list my reports.
Thank you for taking the time to contribute to this course! I started it today and I must admit that I might have reported some sentences that were actually not correct, but I realized it afterwards. I deleted the comment in the sentence discussion but there's not way to "delete" the report, so for those I apologize. I'm seeing this discussion just now.
On a different matter, is there a way to "jointly" contribute to a Spanish-Latin course using this course's material? I searched on the different incubators and there's no Latin from Spanish course either in "beta", "in progress" or "hatching". And if one could use this course's material and transpose it to Spanish it would be great (I'm a Spanish native speaker if you need help with that). I didn't sign up to be a Spanish-Latin contributor because I don't actually speak Latin yet, but maybe doing a Latin-English-Spanish bridge or something?
Keep it up and thank you!
Without sounding too ungrateful of the people who volunteered their time, what should we do about some of the recordings that are difficult to understand? There's a few of the volunteers that clearly are enunciating well, but either their equipment or their environment is not the best for recording, and without headphones turned up, I can't make out what they're saying.
I am having similar problems, although in my case its the pronunciation I am stuggling with. In a lot of cases the speaker is not ending the verb clearly, so you can't distinguish between, for example habitas and habitat, so end up having to guess. Also some words seem to be mumbled so its really hard to figure out.
It's probably because, either the creators of the course don’t know another language sufficiently enough to create a Spanish-Latin, German-Latin etc. course. Or it’s that they are testing the waters with the English-Latin course (as it is in Beta right now) and will eventually work on another language to learn Latin with after it’s out of Beta.
Thank you! You beat me to it.
Once we've learned what does and does not work in the incubator (in terms of Latin) the staff can look for a team that's fluent in Latin and another language. That's their decision. This English-Latin team has nothing to do with it.
"Corinna is not a girl but a woman" is a perfectly good, grammatically correct English sentence. It's hard to introduce new words and write sentences that "flow nicely" to all of our ears with just a handful of Latin words. I think we should give the creators a break and only complain about English and Latin sentences that are grammatically incorrect or are being pronounced incorrectly.
I'd hate for them to develop sentences like "Oh, look and see. See Spot run. Run, run, run." until our vocabularies are sufficiently built up to write longer, more flowing sentences in English. But, primers are primers.
No offence to Sally, Dick, and Jane, Spot and Puff and their cousins across the pond, Peter and Jane, who did have a better primer, though.
Rather than have us report all the garbled audio, could there just be standards in place for those doing the audio recording so the audio is consistent? Simple things like don't record when there's a tv or radio on in the background or don't record quietly 3 feet away from you desktop mic.
All that said, it's a great course and this is nitpicky stuff, but these details are probably going to make or break the course's popularity.
I'm not sure if this is the right place or not. I really really enjoy the tips, but for this Latin course they're only showing up in the web view for me and not in the iOS app. Seems to me that if the tips are available in the back end data, they'd just show up if available in the iOS app.
Unfortunately the volunteer-created Tips & Notes are only available on the web, much as we wish they were on the apps too! A couple courses have staff-created "Tips" which are present in the apps as well, but only a couple of the internally maintained courses, not the volunteer-created courses like Latin.
I understand and appreciate how Duolingo can overlook typos, but in this course specifically this frequently results in me getting the correct answer when I shouldn't. For example, if I intentionally write "Discipulas" when I should write "Discipulae," Duolingo calls it a typo and I can only note the error by reading the "this is your typo" notification at the bottom. This has made it much harder for me to learn when to use each declension. Surely you can tweak the software to be just a tad stricter?
We wish we could! But the course creators are only volunteers who only create and maintain the course content. Anything technical like the algorithms determining what qualifies as a typo can only be changed by Duo staff members, and the devs are very busy and have to prioritise. So it may not be possible to get it adjusted soon, unfortunately.
Just wondering why literal translations aren't going to be accepted? My teacher always made sure we knew what the literal translation was before we turned it into fluent English. It is especially frustrating with "mihi placet." "It is pleasing to me" is just as good as "I like."
From what I've experienced "(It) pleases me" works. Maybe it's because active vs passive voice? "it is pleasing to me" (mihi placitus est) may not be literal?
Since nobody ever got back to my comments here and I guess I wasn't accepted for the incubator (???), I will now unfollow this thread. It is really annoying to get notifications for every new comment (especially the ones where the contributors angrily attack everyone else), but never get a reply to my kind & respectful questions. Do I need a more outrageous tone or what?!
I still highly appreciate the work which the contributors have put into creating this course and keep putting into improving and expanding it. I would have liked to be a part of it and contribute - or at least get some kind of response that you don't need my contribution - but there seems to be a communication barrier that I cannot overcome. So this is my surrender.
Thank you again and good luck with finding contributors in the future with these rather interesting recruitment techniques you are using!
I can't speak for the other contributors, so here is my take.
I'm a volunteer. I follow a few thousand posts like this one. I try to answer as many questions as possible, but I have a limited amount of time each day and get around two hundred emails (each day). I honestly didn't see your posts in this see of questions.
We volunteer contributors are not in charge of applications. We cannot even see them. I had no idea you applied. That's the job of a staff member.
We are not actively working on the new tree. We are just processing reports and fixing some of the audio. Until we get the green light from the staff we cannot add to the tree. It's locked. Duolingo has standards for even our volunteer work. They don't want a meandering approach to new content. In a few months we will get a message from a staff member and we'll have a zoom meeting discussing where we want to go with the tree. Then we'll make an outline of topics, narrow it down to the important ideas, etc. Only then will we flesh it out with the desired vocabulary. Then we'll write out new sentences that fit that framework. All of this will be a rough draft. Problems always come up when developing new curriculum. We then address those issues.
The current team is open to new contributors, but the staff doesn't want too many cooks spoiling the broth. They need team players who will work well with the existing team. They also need people who will commit to months of work. Some of the trees here are stagnant because the amazing contributors moved on as soon as the course launched. It's hard to find people who are actually willing to do this.