u/groovespot

I'm doing Babbel's Spanish (Spain), specifically not the LatAm one, and a lot of the audio pronounces "ll" and "y" as a hard "j" (like English "jump"). So "pollo" comes out as "pojo" instead of "poyo." My actual Spanish teacher from Spain marks this wrong every single time because it's not how spanish in Spain sounds like. That's pronunciation from Argentina/Uruguay.

So basically course labeled as "Spanish (Spain)" is teaching us to mispronounce basic vocabulary in a way that's specifically wrong for Spain, with zero indication anywhere that this is happening.

I contacted support about it, and their answer was that course is primarily based on real Spain Spanish and they deliberately mix in other regional accents anyway, which is at first okay occasionally and with some notes, but at second - means it's no longer consistently teaching actual Spain Spanish.

How many other regional quirks are silently baked into this course that I have no way of knowing about until I run into them in real life and get corrected?

UPD. Tried to continue... So basically everything is built of the wrong pronounciation. Yo = Jo. Ella = Eja. And so on.

Noticed Gemini has trouble with relative time expressions that humans use casually but that don't map cleanly onto calendar dates. Classic example: if you set a reminder late at night (like 1 AM) and say "remind me tomorrow morning," you obviously mean the next time you wake up - a few hours away. Gemini instead parses "tomorrow" as the literal next calendar date, pushing the reminder out by a full day.

The old Google Assistant handled this kind of fuzzy, conversational time reasoning brilliantly. Feels like Gemini leans too hard on strict date logic instead of inferring what the person actually means in context.

Anyone else hit similar mismatches (not just late at night) between natural phrasing and how Gemini schedules things?

Noticed Gemini has trouble with relative time expressions that humans use casually but that don't map cleanly onto calendar dates. Classic example: if you set a reminder late at night (like 1 AM) and say "remind me tomorrow morning," you obviously mean the next time you wake up - a few hours away. Gemini instead parses "tomorrow" as the literal next calendar date, pushing the reminder out by a full day.

The old Google Assistant handled this kind of fuzzy, conversational time reasoning brilliantly. Feels like Gemini leans too hard on strict date logic instead of inferring what the person actually means in context.

Anyone else hit similar mismatches (not just late at night) between natural phrasing and how Gemini schedules things?