4 ms·
For those unfamiliar with German, they read numbers aloud in a unique way. 65536 is "sixty five thousand five hundred six and thirty" (Edit: this is inaccurate)
by PennRobotics 5y ago
For those unfamiliar with German, they read numbers aloud in a unique way. 65536 is "sixty five thousand five hundred six and thirty" (Edit: this is inaccurate). I present German-endian as a common enemy!
-----
At least for me, reading 16- and/or 32-bit multi-channel sensor data and then transceiving via 8-bit radio (atmega32u4) is at least a little easier when all the endians align. No byte swapping. No jumping a pointer ahead for each byte in a packet. Most importantly, no calling swapbytes (and its relevant data casts) in Matlab reading the serial data directly off the microcontroller.
While this is all relatively straightforward to code, each extra line is another tiny chance of error, and the failure modes in streaming data are not always obvious e.g. FIFO size is a power of two but channel data is an odd number of bytes/words. Do you drop data or pause until FIFO empties? Do circular buffers increment or decrement?
Luckily, modern sensors (e.g. IMUs) I've used usually have registers to byte swap, drop LSBs when not needed, choose right or left zero bit padding, change channel order, alter FIFO behavior, interrupt at a FIFO threshold, and so on.
- TacticalMalice 5y ago"five and sixty thousand five hundred six and thirty", right? Dutch is similar and this is a source of mistakes when writing down (phone) numbers. I've resorted to calling out the digits in LTR order.
- junon 5y agoCorrect. The grouping matters, and double-digits in groupings are also reversed - "fünf und sechzig tausend fünf hundert sechs und dreißig". Another thing, years in German aren't spoken as "twenty twenty-one" as we commonly do in English, but instead the number is spoken out fully - "two-thousand one and twenty" ("zwei tausend eins und zwanzig").
- twic 5y agoIn England, the little voice in Google Maps told me to take the "B one thousand, one hundred and thirteen", when every human i know would call that road the "B one one one three".
- PennRobotics 5y agoThis is now totally off-topic, but I'd like to know if there is any Googler at all working on adding location tags to their text-to-speech model. Hearing Google Assistant/Maps mispronounce German street or city names in an American accent is very grating to the ears. The pronunciation of a location name should ignore the language spoken, right? (Ignore for a moment the edge cases, like München vs Munich... although the voice says, "Munchin'," which is wrong in both languages!) And it can't be too complicated to borrow phonemes from another language where they don't exist... Right? Your American text-to-speech algorithm encounters an umlaut, then generate the correct waveforms from a language with umlauts. (I'm sure someone reading this is jumping up and down, yelling about the "photo of a bird" xkcd.)
- Akronymus 5y agoNot really comparable to photo of a bird, because using the geographic bounds for what language spoken there should work in 99.99% of the cases. (I have my phone set to english, because I prefer it like that, despite living in austria, europe. Street names are one of the reasons I rarely ever use google maps for navigation)
- simtel20 5y agoIt's a hard problem in a way. If my language is localized to English, am I more likely to understand the native pronunciation of a street, or the English mispronunciation?
- PennRobotics 5y agoThat's true. To extend this idea, should you pronounce someone's name as they pronounce it? Even if you've only known it one way? (The German Michael is kinda... Michh-aye-ehl'.)
- simtel20 5y agoI don't understand if you're presenting this question broadly, in a vacuum? Or if you're still in the context of your question about (mis-)pronunciation of streets etc. while providing navigation for a driver whose chosen language is not the same language as the current location, and who it may be safe to assume cannot understand the local languages' pronunciation even when the alphabet is similar (e.g. an English speaker in a Portuguese speaking country is very unlikely to understand if the navigayor natively pronounces "rua da Heitor do Rio do Engenho", a name I just made up that may exist somewhere, which I think demonstrates the difficulty I'm talking about.)
- PennRobotics 5y agoAh right. My mistake. It would be five and sixty thousand ... Yuck! I guess this is exactly what we're talking about---mistakes because you are not natively familiar with a particular system, and then you miss the non-base case. For me, I got the tens digit right but not the ten thousands digit. In the memory case, it's knowing to change a pointer location because an address to a 32-bit value will start or end at a different address than a 64-bit value.
- BoxOfRain 5y agoThere’s examples of it in English too, although it’s very old-fashioned. An example would be the rhyme with “four and twenty blackbirds baked in a pie”.
- agent327 5y agoI totally hate people who repeat a phone number back to you, but with different digit grouping. How the hell am I supposed to know if that's the same number!? Just repeat it as I said it already...
- __del__ 5y agonumbers grouped in twos are great for mnemonic memorization. you'll easily come up with an association for many two digit numbers. ex. 415-222-9670 becomes: sub universal (one less than the answer to life, the universe and everything) deck (52 cards) swift (she's feeling 22) resolution (old dpi on wandows) top speed (California speed limit) now isn't "sub universal deck swift resolution top speed" easier than googling twitter hq? ;] granted, the associations have to make sense to you. for me, 96 was a toss up between nashville (code name of windows 96) and the resolution i had to train myself to remember after moving from the mac's 72.
- PaulIH 5y agoNorway used that as the standard order until 1951, when an official reform changed the language to LTR. This was due the older way of stating numbers causing confusion when reading phone numbers and similar. It's still not universal, but younger generations generally now state numbers universally left to right.
- skerit 5y agoI just can't write down phone numbers when people pronounce them that way. "Nul vierhonderdvijfenzeventig tweeëntachtig zesendertig eenennegentig"? You lost me at nul.
- JoachimS 5y agoGetting a bit off topic I guess, but in Danish you do the same AND also have base 20 for numbers over 40 and less than 100. So for example (roughly translated) is 65 "five and half of thirty". And even harder, for odd tens you get them by taking half of the base 20 number. So 55 is "five and half of thirty". https://www.babbel.com/en/magazine/counting-in-danish https://www.babbel.com/en/magazine/counting-in-danish
- dandellion 5y ago> is 65 "five and half of thirty". And even harder (...) 55 is "five and half of thirty". So you call any number "five and half of thirty"? That sounds pretty easy to be honest.
- JoachimS 5y agoOops. I meant "five and thirty" for 65. and "five and half thirty" for 55.
- kzrdude 5y agoMaybe 65 should be explained as said like "five and threesh" where "threesh" is implicitly/shortened for "three times 20". So we say: 5 + 3 x 20, but in a terse encoding. Yes, 55 is "half threesh" in the same way, that is we say 5 + half 3 x 20, but half 3 == 2.5, of course!
- JoachimS 5y agoMuch better explanation, thanks!
- agent327 5y agoIsn't it "five and sixty thousand five hunderd six and thirty"? At least that's how it is said in Dutch, and I believe German works the same way...
- PennRobotics 5y agoIt is, and what a wonderful example of how endianness can cause mistakes.
- thaumasiotes 5y ago> For those unfamiliar with German, they read numbers aloud in a unique way. 65536 is "sixty five thousand five hundred six and thirty" (Edit: this is inaccurate). I present German-endian as a common enemy! What's unique about that? Sing a song of sixpence, a pocket full of rye Four and twenty blackbirds baked in a pie When the pie was opened, the birds began to sing Wasn't that a dainty dish to set before the king?
- 8ytecoder 5y agoBased on what I have read in English novels of the 19th century (like Sherlock Holmes), I'd assume "six and thirty" was common in English as well.