Translation:There are five chairs.
True. Normally one would not pronounce it as such. I do believe that there is something wrong with the audio.
The super fast reading combined with new readings of kanji really needs to change. I need to check the comments now every time to be sure about the reading for the number kanji's.
They COULD easily add a link to SHOW/HIDE pronunciation !!
That would Clear up so many questions ! And fix the problem with poor recordings. And the problem with discerning what exactly a fat recording is actually saying, even when it's is a good recording. AND would help remind us (help us learn) proper readings/pronunciations.
That would be a low cost, Easy way for DuoLingo to create Huge value, and overcome so many shortcomings.
A single database entry added for each example sentence. That's It ! plus a single show/hide link added to the UI.
PLEASE DUOLINGO, implement this !
I will VOLUNTEER my services to add this code for you! I'm sure you can find somebody to type in the pronounciation "translation" for each sentence.
It needs only be done 1 time.
Then all sentences have a correct reading reference.
This corrects also for all those bad references, where clicking on an individual character has Audi, but the INCORRECT reading is attached! You could get away without addressing that, if the matter sentence included a full correct reading for the sentence. AND users would be on a good place for learning/referencing/remembering correct readings for all contexts/sentences provided. It would even highlight differences between common readings and less common readings, when audio for a single character differs from pronunciation(spelling) for the same characters in the context of the whole sentence.
- poor audio recordings
- audio compression issues - user comprehending due to fast speaking in audio.
- allows user to discern ambiguous sounds to reinforce correct "spelling" and pronunciation (some kana and kana combinations sound similar to different kana, and without a way to reference, it can be difficult to know/remember/learn which is actually being spoken. Sort off line a very blurry photo. where you can see it's Probably a person, but you don't know who. or, maybe it's a person, maybe something else, not sure)
- CLEARS UP INCONSISTENCIES and EXCEPTIONS in the language.
- Helps us learn COUNTERS pronunciations.
- CLEARS up all issues with different READINGS.
- removes so many AMBIGUITIES.
- help is learn/remember Spelling, Pronunciation, KANJI - a great REFERENCE tool ! - overcomes issues where your audio for a single character of a sentence was recorded using the WRONG READING. If you allow a pop up for the full sentences, then it doesn't matter too much, if there other defence is wrong. As long as we can see prounounciation for the full sentence, we are good. We are no longer confused as to what it SHOULD HAVE said. We have a pepper reference to remind ourselves. We also need not click the link for ever sentence, and comb through ALL the comments for one where a USER can Remind us the correct . We clicked on the character for that reference, Street all.
- When TILES speak the INCORRECT reading, is ok, because the full sentence shoes tree correct one.
(ALTERNATIVELY, RULES SHOULD LINK TO THE CORRECT READING FOR THE SENTENCE IN WHICH IS PROVIDED). This would be. much more involved programmatically! Sure, is more IDEAL, but my partial, is much simpler, apps users CORRECT information (Currently you are showing us INCORRECT info -- A DISSERVICE TO LEARNING). This proposal OVERCOMES such errors. Users can understand that the audio hovers will sound out A COMMON reading, not necessarily the correct reading for the sentence, BUT the PRONUNCIATION LINK/popup/hover will ALLAY show CORRECT READING FOR THAT SENTENCE.
BOOM! Proper teaching.
Minimal programming effort.
One time data entry, and "translation" expertise for each existing sentence in the database.
MASSIVE value add to DuoLingo, and Users.
I would pay for this effort, and even VOLUNTEER my time to make it happen.
Not even sure what you said, because it was ling,but you said it passionately so im gonna take your word on it
If you look on the desktop version for this lesson in the notes there is a table that outlines four counters for numbers 1 to 10.
Really wish the kanji had hiragana listed. I can't always understand this robot voice.
when you say "desu ga" you naturally are forced to pause between them unless you make a closed "n" sound so that there is no pause, that's why a lot of japanese people say it as "desu(n)ga" to cut the pause
I believe the pronunciation is "Isu ga itsutsu arimasu". "五つ" sounds like "いすつ", because it is a counter specifying an amount.
It's super fast and hard to hear, but pronunciation is actually いつつ. You have the romaji right so probably just a typo in the kana.
Does anyone else's dialect of English allow them to say "there's 5 chairs" as opposed to "there are 5 chairs" ?
The speed is awful. Never seen in anime or movies people talking at that speed and the sound is sounding wrong. Besides that, there is NO intonation whatsoever here in DUO. People should not be guided AT ALL by the audios here.
If you are asking why not to use "五ついすがあります", I also wonder why. Could someone explain it?
椅子が五つあります was marked as incorrect. Please add or help me with my autocorrection feature.
Usually in the "write what you hear" sections if you type kanji (even kanji used in the listen) you get judged incorrectly; this time, not using the kanji and writing it in hiragana was counted incorrectly. It seems both should be accepted in all cases, but consistency would be nice at least.
I wrote "there is 5 chairs" why is it wrong? English is not my first language but i do k ow there are 5 chairs
There was no "ます" for me to choose from! How am I expected to get it right when what I need to get it right isn't presented to me!
Not to mention the whole "hito"/"jin" problem, but that's for another post.
wait wasn't the order supposed to be [いす五つがあります "isu itsutsu ga arimasu"]? instead of [いすがいつつあります" isu ga itsutsu arimasu"]?
the current order sounds more accurate however on the previous ones the [が ga] was replaced afterwards, so why is that?