1 to F are the normal 'un' to 'quinze'. A is 'dix'.
10 is 'seize'. 11 is 'seize et un' etc. Until 1F which is `seize et quinze'.
20 to 2F are 'vingt' until 'vingt et quinze'.
70, 80 and 90 are called 'septante', 'huitante' (Swiss-specific) and 'nonante'.
A0 is 'dixante', then we have 'onzante', 'douzante', 'treizante', 'quatorzante' and 'quinzante'.
100 is 'cent', and from there normal rules apply.
So B78D would be 'onze mille sept cents huitante treize'.
Note that 'soixante dix' is 6A, not 70.
B78D: Eleven Thousand Seven Hundred and Eighty Thirteen
See also Tolkien's famous hobbit's birthday party.
Edit: Or as suggested in the original link, A=Ten, 10=annty, 11=annty-one and 1A=annty-ten
10 is sixteen.
11 is sixteen one
A is not ten in hexadecimal.
"ten" always means 10 in any base. the number after "nine" is "deci".
0x10000 is a number more deserving of a name than 0x1000.
In effect, I want to call 0x10000 as "hex-thousand" (correlating to the number where 16-bits overflow). And 0x100000000 as "hex-million" (correlating to the 32-bit overflow number).
Of course, that leaves 0x1000 and 0x1000000 as ambiguous.
Myriad shares similarities to "Million". So maybe Myriad / Biriad / Trilliad / Quadrilliad will scale into the higher orders.
Hmm, maybe I'll make this a thing.
Every word (phrase in the case of hundred/thousand) becomes strictly one digit, as opposed to normal English where e.g. "thirteen" is actually two digits.
As, from the original french comment:
1A = dix / ten
10 = seize / sixteen
11 = seize-et-un / sixteen-one
Others have suggested 10 = onety instead of sixteen. This would be more consistent, but less idiomatic (onety is not a number in English, and hex is base sixteen).
11 78D seize-un mille sept cent octante-quatrorze.
Or, in English:
11,78D Sixteen-one thousand seven hundred eighty fourteen.
It's quite a shame, because that solution for reading hexadecimal numbers out loud is quite elegant :)
« soixante-dix » for 70 = sixty-ten
« quatre-vingt » for 80 = four-twenty
« quatre-vingt-dix » for 90 = four-twenty-ten
"Soixante-dix" would be 70 no matter how you look at it, and 0x6A is obviously "cent six".
That's why you need a new suffix as well as new names for exponentials instead of trying to retrofit existing number-naming convention. (Same thing is true for English as well)
So let this new hexadecimal suffix would be -anze, 16 ^ 3 is hexmille, 16 ^ 2 is hexcents,
0xB78D = 46989 would be "onze hexmille sept hexcents huitanze treize." or "quarante six mille neuf cents quatre-vingt neuf"
"Where is the stack base supposed to be?"
"O X 8 zillion"
"Oh, the system crashed with stack pointer at 0 X two eight zillion, something must have gone badly wrong!"
(I don't know how people pronounce that operator otherwise... I just say "colon colon".)
There might be ways to fix that with variants of those suffixes, though my first thought of “-xy”/“-xeen” might be too hard to distinguish in a noisy auditory environment.
"An additional naming system has been published online by S. R. Rogers in 2007 that tries to make the verbal representation distiguishable in any case, even when the actual number does not contain numbers A-F. Examples are listed in the tables below."
Does thousand mean the quantity itself or does it mean the decimal 1000?
In other words thousand = 1000 (dec) and 0x3E8 (hex). Are they both pronounced “thousand”? When someone says mix a thousand liters of glycol with ten kilograms of salt, both 1000 (dec) and 0x3E8 (hex) mean “thousand” each of something.
The only way to get around this is if every whole number on the number line had a unique name and could be represented by any numbering system.
Thus, I agree with you, there's value in making digits beyond 9 pronouncable for higher bases (if dealing with them enough to make devising the system worthwhile of course).
The "teen" suffix is wrong; it specifically means "ten". For instance thirteen means three+ten, so it is inappropriate to pronounce 0x13 as "thirteen". So that is to say, the pronunciation issue does not begin at 1A; we shouldn't call 0x19 "nineteen", but something else.
Similarly 0x30 shouldn't be "thirty" because that word means three times ten.
There shouldn't be any common words between hex pronunciation and decimal that denote a different integer. If we say "hundred" and the context is really clear, it can be understood as 0x100, but the context isn't always clear. Attaching "hex" after every ambiguous wording ("hundred thirty-one hex" for 0x131) is verbose. How about:
100: hent (from "cent")
1000: hil (from "mil")
10000: han (from 万 (man))
100000000: hoku (from 億 (oku))
0xDEADBEEF: deezy-ee-hent ayesy-dee han beezy-ee-hent eezy-eff.
0xF00FCBB0: efzy-hent-eff han, ceezy-bee-hent beezy.
This approach (and other approaches proposed in this thread) seems to add complexity but it's not that much better than just reading the characters normally.
> B78D would be 'onze mille sept cents huitante treize'
Or just read it: B, 7, 8, D. To space out a long hex number, read it in group of 4, with a pause.
The approach, other than it's not being shorter, also risks miscommunication due to the receiver might not be familiar with it, or due to the sound system has multiple very similar sounds (but totally will change the meaning when misheard) like -teen and -ty.
I can give an example using the system in the tweet:
2F3E: twenty frost thirty ernest -- longer to read, 7 sounds.
2F3E: 2, F, 3, E -- shorter to read, 4 sounds.
Looking at that, I don't see the benefits and trade offs of that new complexity, and that's why I asked for help :)
For a mac address I'd not summarize and just read it off in 6 pairs.
For the example representation address on the wikipedia page... 2001:0db8:85a3:0000:0000:8a2e:0370:7334 ( https://en.wikipedia.org/wiki/IPv6_address )
Two Zero Zero One Colon Delta Bravo Eight Colon Eight Five Alpha Three Colon (pause) Colon Eight Alpha Two Echo Colon Three Seven Zero Colon Seven Three Three Four.
The part in the middle might need a better way of announcing, but given the double digits in other parts of the address it seems more natural to read it as a string of characters than to alter it.
I have also seen other systems of representing the digits for hexadecimal, such as Nystrom's system (which also includes pronounciation).
And now, looking at Wikipedia, there are more. (The hex intuitor system I mentioned above is also called the Rogers system.)
Do you have more links?
0xA_ : Atta
0xB_ : Bibbity
0xC_ : City
0xD_ : Dickety
0xE_ : Ebbity
0xE_ : Fleventy
1F is just a two-syllable word. Just like "fiftysix" is.
But then you start to see the advantage of named systems, because you end up saying "aught" or "zero" a lot to distinguish "0xA" from "0xA0" within words. "A salary of one aught aught word" doesn't seem as easy to me as "a salary of one hundred thousand". So perhaps something ought to be done about 0x10 and 0x100, even if we only use them in situations that can be abbreviated like that. Maybe 0x10 is "hex", so "base 0x10" becomes literally read as "base hex".
 Of course this fixes a meaning for how many bytes are in a word, which a lot of people aren't going to be happy with. ;-)
These letters all rhyme: B, C, D, and E. "Did you say 1B or 1D?"
Such a computing lire, gem. I am going to say these first chance I get.
Therefore, might your “swan hyphen” be a corruption of an original term “swung hyphen”?
"#" was another one with many names that have consolidated over time, been decades since heard anybody refer to it as a checkerboard, which was never as elegant and can see why "hash" became the norm.
# Common: number sign; pound; pound sign; hash; sharp; crunch ; hex; [mesh]. Rare: grid; crosshatch; octothorpe; flash; <square>, pig-pen; tictactoe; scratchmark; thud; thump; splat.
So, according to the above, the most common name for # is “number sign”, and the officiall ANSI/CCITT term is “square”.
Also, in the 1975 movie Three Days of the Condor, the term “symbol for number” is used, presumably referring to #.
Also, I remember * being "splat" back in my PR1MOS and Vax days.
Sometimes single quotes to me are "ticks," with the grave accent being a "back-tick."
And while we're talking hex semantics, is it just me being old, or do lower case letters in hex values bother anyone else?
The only time I've been OK with this is when I've had to work with machines that only have seven-segment displays.
Is uppercase the older tradition? I'm ~30yo and I've been seeing both for as long as I remember.
says "The characters "a", "b", "c", "d", "e", and "f" in an IPv6 address MUST be represented in lowercase "
One Reason for this, is that it can avoid redundancy if you submit a hexdecimal nummber by phone.
"However, when a letter is spelled uppercase,people tend to specify that it is uppercase, which is unnecessary information."
If you care about typography and think mixing lower-case letters with upper-case numbers, you could argue, that oldstyle numbners aka. lower-case numbers could be a better fit.
e.g. "50" is "five-tens" instead of "fifty"
5 is kvin and 10 is dek so 50 is kvindek. If you know how to count to 10, you know how to count to 99.
100 is cent, so 500 is kvincent. 505 is kvincent kvin and 555 is kvincent kvindek kvin. Alright, now you know how to count to 999.
A "number to Esperanto" is a great exercise to code and Esperanto is a lovely language to learn. Try it!
I guess it's also no coincidence that words ending in -teen are frequently confused with and misheard for those ending in -ty.
Edit: Seems like they derive from different Germanic roots for 10.