2 ms·
Huh? No, when driving in Quebec or Ottawa etc, there might be an "English" way to pronounce the names (like the kind of thing my anglo self would use, bad prono
by cmrdporcupine 2y ago
Huh? No, when driving in Quebec or Ottawa etc, there might be an "English" way to pronounce the names (like the kind of thing my anglo self would use, bad pronounciation but making an attempt), but it doesn't do that... it actually just reads out this weird literal phonetic output as if it was an English word and it's unrecognizable to anybody from the area or anybody who grew up in Canada and has a basic idea of how these words are pronounced.
Even, like, names ... Duplessis or Cartier or whatever... just completely unrecognizable.
Or take the way it reads out the exits off the 401 in Toronto, reading the full bilingual sign (where there is one) with the English first and then the French part as if it was a continuation ... in English ("Sud" read out like you'd say that if it was an English word, hard D and everything.) Clearly, they should just drop the French part, but their system can't comprehend that a sign could be bilingual. Because America.
Look, I don't speak French, I'm not bilingual, and it drives me nuts when I'm in QC or even just Ottawa etc. I literally can't tell what street it's talking about, it doesn't correspond with the sign. It's incoherent.
What's mind boggling is that Google navigation is completely fine reading out Spanish words when I drive around California. C'mon.