These are quite silly things. Firstly, why invent words instead of just using the ltters. Obviously A creates an ambiguity with "eight", but other than that, things are fine. Perhaps A should be "aye".
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:
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: