• 0 Posts
  • 29 Comments
Joined 2 years ago
cake
Cake day: June 9th, 2023

help-circle
  • No, one region (France) has a correct way to pronounce crepe. Everyone else should pronounce it the same way, otherwise they’re dumb. If there are language limitations that mean it can’t be perfectly pronounced, they should endeavour to pronounce it as close as possible given the phonemes of their language. In the case of crepe, there’s no reason not to use the “e” sound in “crept”, which would make it the correct, French pronunciation of that vowel.











  • I and presumably the rest of the Commonwealth

    Nope!

    The French version of the word has a circumflex over the e (crêpe)

    Which makes it sound like the “e” in crept or crepuscular. Both of which, unsurprisingly, sound exactly like the way the e in “crepe” is supposed to be pronounced.

    Now, I could see someone getting confused by the spelling, and assuming the weird English rule about silent "e"s applies, meaning it should be pronounced “creep”. But, that’s not the mistake people are making, for some reason they’re saying “crayp”, which is just stupid.




  • I hate these. You don’t need to program for very long before you see one of these. And, you get used to the idea that when it says there’s an error on a blank line, that it means something isn’t properly terminated on one of the previous lines. But, man, I hate these.

    At the very least, you’d hope that by now compilers/interpreters would be able to say “error somewhere between line 260 and 265”. Or, more usefully “Expected a closing ‘)’ before line 265, opening ‘(’ was on line 260”.

    Error on <blank line> just pisses me off because the compiler / interpreter should know that that isn’t true. Whoever wrote the compiler is a seasoned developer who has been hit by this kind of error message countless times. They must know how annoying it is, and yet…



  • As someone who worked in mapping, many people don’t realize how much this kind of BS actually comes up.

    The map you see in Google / Apple maps isn’t the map the whole world sees. What you see is what’s culturally / legally appropriate for viewers in your region.

    For example, in parts of India it’s legally required that Jammu and Kashmir be displayed as being part of India on their maps. On Pakistan’s maps it’s legally required to be weirdly ambiguous, with a strange open border that doesn’t properly close. The rest of the world gets dotted lines indicating it’s complicated.

    For most of the world the body of water between Korea, Japan and Vladivostok is labeled as “The Sea of Japan”, but users in Korea will see “The East Sea”. Is the body of water around Bahrain, Qatar, Kuwait, UAE, etc. the Persian Gulf or the Arabian Gulf? Depends on where you are when you ask that question.

    This even has a strange effect when all the countries involved agree that a certain geographic feature is the border, but that geographic feature is a river. Some rivers, especially ones like the Amazon river keep shifting. Sediment piles up, erosion happens, and the river shifts. The river is still the border, but now someone has to go in and adjust the political border to match the river’s new position.

    So, if Trump does do something official to rename the Gulf of Mexico, the online mapping companies (and any offline ones that are left) will probably follow the rule and rename it… for their American users. The rest of the world will still see it as the Gulf of Mexico. It will just be yet another one of those funny exceptions the companies have to keep track of while displaying maps for a certain subset of users.