(adsbygoogle = window.adsbygoogle || []).push({}); Some Colors In Hexidecimal
#00CCFF DeepSkyBlue
#009999 DarkCyan
#009966 Teal
#009900 Green
#006600 Dark Green
#0000FF Blue
#0000CC Med. Blue
#000099 Dark Blue
#000066 Navy
#000000 Black

In mathematics and computer science, hexadecimal (also base 16, or hex) is a positional numeral system with a radix, or base, of 16. It uses sixteen distinct symbols, most often the symbols 0–9 to represent values zero to nine, and A, B, C, D, E, F (or alternatively a–f) to represent values ten to fifteen. For example, the hexadecimal number 2AF3 is equal, in decimal, to (2 × 163) + (10 × 162) + (15 × 161) + (3 × 160) , or 10,995.
Each hexadecimal digit represents four binary digits (bits) (also called a "nibble"), and the primary use of hexadecimal notation is as a human-friendly representation of binary coded values in computing and digital electronics. For example, byte values can range from 0 to 255 (decimal) but may be more conveniently represented as two hexadecimal digits in the range 00 through FF. Hexadecimal is also commonly used to represent computer memory addresses.

In situations where there is no context, hexadecimal numbers can be ambiguous and confused with numbers expressed in other bases. There are several conventions for expressing values unambiguously. A numerical subscript (itself written in decimal) can give the base explicitly: 15910 is decimal 159; 15916 is hexadecimal 159, which is equal to 34510. Other authors prefer a text subscript, such as 159decimal and 159hex, or 159d and 159h.
In linear text systems, such as those used in most computer programming environments, a variety of methods have arisen:
In URLs, character codes are written as hexadecimal pairs prefixed with %: You must login or register to view this content. where %20 is the space (blank) character (code value 20 in hex, 32 in decimal).
In XML and XHTML, characters can be expressed as hexadecimal numeric character references using the notation &#xcode;, where code is the 1- to 6-digit hex number assigned to the character in the Unicode standard. Thus ’ represents the curled right single quote (Unicode value 2019 in hex, 8217 in decimal).
Color references in HTML and CSS and X Window can be expressed with six hexdigits (two each for the red, green, and blue components, in that order) prefixed with #: white, for example, is represented #FFFFFF .[1] CSS allows 3-hexdigit abbreviations with one hexdigit per component: #FA3 abbreviates #FFAA33 (a golden orange).
*nix (Unix and related) shells, and likewise the C programming language, which was designed for Unix (and the syntactic descendants of C[2]) use the prefix 0x for numeric constants represented in hex: 0x5A3. Character and string constants may express character codes in hexadecimal with the prefix \x followed by two hex digits: '\x1B' represents the Esc control character; "\x1B[0m\x1B[25;1H" is a string containing 11 characters (plus a trailing NUL to mark the end of the string) with two embedded Esc characters.[3] To output an integer as hexadecimal with the printf function family, the format conversion code %X or %x is used.
In the Unicode standard, a character value is represented with U+ followed by the hex value: U+20AC is the Euro sign (€.
In MIME (e-mail extensions) quoted-printable encoding, characters that cannot be represented as literal ASCII characters are represented by their codes as two hexadecimal digits (in ASCII) prefixed by an equal to sign =, as in Espa=F1a to send "España" (Spain). (Hexadecimal F1, equal to decimal 241, is the code number for the lower case n with tilde in the ISO/IEC 8859-1 character set.)
In Intel-derived assembly languages, hexadecimal is denoted with a suffixed H or h: FFh or 05A3H. Some implementations require a leading zero when the first hexadecimal digit character is not a decimal digit: 0FFh
Other assembly languages (6502, AT&T, Motorola), Pascal, Delphi, some versions of BASIC (Commodore) and Forth use $ as a prefix: $5A3.
Some assembly languages (Microchip) use the notation H'ABCD' (for ABCD16).
Ada and VHDL enclose hexadecimal numerals in based "numeric quotes": 16#5A3#. For bit vector constants VHDL uses the notation x"5A3"[4].
Verilog represents hexadecimal constants in the form 8'hFF, where 8 is the number of bits in the value and FF is the hexadecimal constant.
Modula-2 and some other languages use # as a prefix: #05A3
The Smalltalk language uses the prefix 16r: 16r5A3
PostScript denotes hex with prefix 16#: 16#5A3. Binary data (such as image pixels) can be expressed as unprefixed consecutive hexadecimal pairs: AA213FD51B3801043FBC...
In early systems when a Macintosh crashed, one or two lines of hexadecimal code would be displayed under the Sad Mac to tell the user what went wrong.
Common Lisp use the prefixes #x and #16r.
MSX BASIC,[5] QuickBASIC, FreeBASIC and Visual Basic prefix hexadecimal numbers with &H: &H5A3
BBC BASIC and Locomotive BASIC use & for hex.[6]
TI-89 and 92 series uses a 0h prefix: 0h5A3
The most common format for hexadecimal on IBM mainframes (zSeries) and midrange computers (IBM System i) running the traditional OS's (zOS, zVSE, zVM, TPF, IBM i) is X'5A3', and is used in Assembler, PL/I, Cobol, JCL, scripts, commands and other places. This format was common on other (and now obsolete) IBM systems as well. Occasionally quotation marks were used instead of apostrophes.
Donald Knuth introduced the use of a particular typeface to represent a particular radix in his book The TeXbook.[7] Hexadecimal representations are written there in a typewriter typeface: 5A3
Any IPv6 address can be written as eight groups of four hexadecimal digits, where each group is separated by a colon (. This, for example, is a valid IPv6 address: 2001:0db8:85a3:0000:0000:8a2e:0370:7334
ALGOL 68 uses the prefix 16r to denote hexadecimal numbers: 16r5a3. Binary, quaternary (base-4) and octal numbers can be specified similarly.
There is no universal convention to use lowercase or uppercase for the letter digits, and each is prevalent or preferred in particular environments by community standards or convention.

The choice of the letters A through F to represent the digits above nine was not universal in the early history of computers.
During the 1950s, some installations favored using the digits 0 through 5 with a macron character ("¯") to denote the values 10–15.
Users of Bendix G-15 computers used the letters U through Z.
The Librascope LGP-30 used the letters F, G, J, K, Q and W.[8]
Bruce A. Martin of Brookhaven National Laboratory considered the choice of A–F "ridiculous" and in a 1968 letter to the editor of the CACM proposed an entirely new set of symbols based on the bit locations, which did not gain much acceptance.[9]
Soviet programmable calculators Б3-34 and similar used the symbols "−", "L", "C", "Г", "E", " " (space) on their displays.

There are no traditional numerals to represent the quantities from ten to fifteen—letters are used as a substitute—and most Western European languages lack non-decimal names for the numerals above ten. Even though English has names for several non-decimal powers (pair for the first binary power, score for the first vigesimal power, dozen, gross, and great gross for the first three duodecimal powers), no English name describes the hexadecimal powers (decimal 16, 256, 4096, 65536, ...*). Some people read hexadecimal numbers digit by digit like a phone number: 4DA is "four-dee-ay". However, the letter A sounds like "eight", C sounds like "three", and D can easily be mistaken for the "-ty" suffix: Is it 4D or forty? Other people avoid confusion by using the NATO phonetic alphabet: 4DA is "four-delta-alfa", the Joint Army/Navy Phonetic Alphabet ("four-dog-able"), or a similar ad hoc system.
Hexadecimal finger-counting scheme.
Systems of counting on digits have been devised for both binary and hexadecimal. Arthur C. Clarke suggested using each finger as an on/off bit, allowing finger counting from zero to 1023 on ten fingers. Another system for counting up to FF (255) is illustrated on the right; it seems to be an extension of an existing system for counting in twelves (dozens and grosses), that is common in South Asia and elsewhere.

The hexadecimal system can express negative numbers the same way as in decimal: −2A to represent −4210 and so on.
However, some prefer instead to express the exact bit patterns used in the processor and consider hexadecimal values best handled as signed values. This way, the negative number −4210 can be written as FFFF*FFD6 in a 32-bit CPU register, as C228*0000 in a 32-bit FPU register or C045*0000*0000*0000 in a 64-bit FPU register (assuming certain representation schemes, two's-complement in the 32-bit non-FPU instance and sign-magnitude in the FPU instances.)

Just as decimal numbers can be represented in exponential notation so too can hexadecimal. By convention, the letter p represents times two raised to the power of, whereas e serves a similar pupose in decimal. The number after the p is decimal and represents the binary exponent.
Usually the number is normalised: that is, the leading hexadecimal digit is 1 (unless the value is exactly 0).
Example: 1.3DEp42 represents 1.3DE16*×*242.
Hexadecimal exponential notation is required by the IEEE 754 binary floating-point standard. This notation can be produced by some versions of the printf family of functions by using the %a conversion.

Most computers manipulate binary data, but it is difficult for humans to work with the large number of digits for even a relatively small binary number. Although most humans are familiar with the base 10 system, it is much easier to map binary to hexadecimal than to decimal because each hexadecimal digit maps to a whole number of bits (410). This example converts 11112 to base ten. Since each position in a binary numeral can contain either a 1 or 0, its value may be easily determined by its position from the right:
00012 = 110
00102 = 210
01002 = 410
10002 = 810
Therefore:
11112 = 810 + 410 + 210 + 110
* = 1510
With surprisingly little practice, mapping 11112 to F16 in one step becomes easy: see table in Representing hexadecimal. The advantage of using hexadecimal rather than decimal increases rapidly with the size of the number. When the number becomes large, conversion to decimal is very tedious. However, when mapping to hexadecimal, it is trivial to regard the binary string as 4-digit groups and map each to a single hexadecimal digit.
This example shows the conversion of a binary number to decimal, mapping each digit to the decimal value, and adding the results.
010111101011010100102 = 26214410 + 6553610 + 3276810 + 1638410 + 819210 + 204810 + 51210 + 25610 + 6410 + 1610 + 210
* = 38792210
Compare this to the conversion to hexadecimal, where each group of four digits can be considered independently, and converted directly:
010111101011010100102 = 0101* 1110* 1011* 0101* 00102
* = 5 E B 5 216
* = 5EB5216
The conversion from hexadecimal to binary is equally direct.
The octal system can also be useful as a tool for people who need to deal directly with binary computer data. Octal represents data as three bits per character, rather than four.

Division-remainder in source base
As with all bases there is a simple algorithm for converting a representation of a number to hexadecimal by doing integer division and remainder operations in the source base. Theoretically this is possible from any base but for most humans only decimal and for most computers only binary (which can be converted by far more efficient methods) can be easily handled with this method.
Let d be the number to represent in hexadecimal, and the series hihi-1...h2h1 be the hexadecimal digits representing the number.
i*:= 1
hi*:= d mod 16
d*:= (d-hi) / 16
If d = 0 (return series hi) else increment i and go to step 2
"16" may be replaced with any other base that may be desired.
The following is a JavaScript implementation of the above algorithm for converting any number to a hexadecimal in String representation. Its purpose is to illustrate the above algorithm. To work with data seriously however, it is much more advisable to work with bitwise operators.
function toHex(d) {
var r = d % 16;
var result;
if (d-r == 0)
result = toChar(r);
else
result = toHex( (d-r)/16 ) + toChar(r);
return result;
}

function toChar(n) {
const alpha = "0123456789ABCDEF";
return alpha.charAt(n);
}

It is also possible to make the conversion by assigning each place in the source base the hexadecimal representation of its place value and then performing multiplication and addition to get the final representation. I.e. to convert the number B3AD to decimal one can split the conversion into D (1310), A (1010), 3 (310) and B (1110) then get the final result by multiplying each decimal representation by 16p, where 'p' is the corresponding position from right to left, beginning with 0. In this case we have 13*(160) + 10*(161) + 3*(162) + 11*(163), which is equal 45997 in the decimal system.

Most modern computer systems with graphical user interfaces provide a built-in calculator utility, capable of performing conversions between various radixes, generally including hexadecimal.
In Microsoft Windows, the Calculator utility can be set to Scientific mode (called Programmer mode in some versions), which allows conversions between radix 16 (hexadecimal), 10 (decimal), 8 (octal) and 2 (binary); the bases most commonly used by programmers. In Scientific Mode, the on-screen numeric keypad includes the hexadecimal digits A through F which are active when "Hex" is selected. In hex mode, however, the Windows Calculator only supports integers.

As with other numeral systems, the hexadecimal system can be used to represent rational numbers, although recurring digits are common since sixteen (10h) has only a single prime factor (two):
****½
=
0.8 ****⅙
=
0.2A ****1⁄A
=
0.19 ****1⁄E
=
0.1249
****⅓
=
0.5 ****1⁄7
=
0.249 ****1⁄B
=
0.1745D ****1⁄F
=
0.1
****¼
=
0.4 ****⅛
=
0.2 ****1⁄C
=
0.15 ****1⁄10
=
0.1
****⅕
=
0.3 ****1⁄9
=
0.1C7 ****1⁄
=
0.13B ****1⁄11
=
0.0F
where an overline denotes a recurring pattern.
For any base, 0.1 (or "1/10") is always equivalent to one divided by the representation of that base value in its own number system: Counting in base 3 is 0, 1, 2, 10 (three). Thus, whether dividing one by two for binary or dividing one by sixteen for hexadecimal, both of these fractions are written as 0.1. Because the radix 16 is a perfect square (4²), fractions expressed in hexadecimal have an odd period much more often than decimal ones, and there are no cyclic numbers (other than trivial single digits). Recurring digits are exhibited when the denominator in lowest terms has a prime factor not found in the radix; thus, when using hexadecimal notation, all fractions with denominators that are not a power of two result in an infinite string of recurring digits (such as thirds and fifths). This makes hexadecimal (and binary) less convenient than decimal for representing rational numbers since a larger proportion lie outside its range of finite representation.
All rational numbers finitely representable in hexadecimal are also finitely representable in decimal, duodecimal and sexagesimal: that is, any hexadecimal number with a finite number of digits has a finite number of digits when expressed in those other bases. Conversely, only a fraction of those finitely representable in the latter bases are finitely representable in hexadecimal. For example, decimal 0.1 corresponds to the infinite recurring representation 0.199999999999... in hexadecimal. However, hexadecimal is more efficient than bases 12 and 60 for representing fractions with powers of two in the denominator (e.g., decimal one sixteenth is 0.1 in hexadecimal, 0.09 in duodecimal, 0;3,45 in sexagesimal and 0.0625 in decimal).

The word hexadecimal is composed of hexa-, derived from the Greek έξ (hex) for "six", and -decimal, derived from the Latin for "tenth". Webster's Third New International online derives "hexadecimal" as an alteration of the all-Latin "sexadecimal" (which appears in the earlier Bendix documentation). The earliest date attested for "hexadecimal" in Merriam-Webster Collegiate online is 1954, placing it safely in the category of international scientific vocabulary (ISV). It is common in ISV to mix Greek and Latin combining forms freely. The word "sexagesimal" (for base 60) retains the Latin prefix. Donald Knuth has pointed out that the etymologically correct term is "senidenary", from the Latin term for "grouped by 16". (The terms "binary", "ternary" and "quaternary" are from the same Latin construction, and the etymologically correct term for "decimal" arithmetic is "denary".)[10] Schwartzman notes that the expected form from usual Latin phrasing would be "sexadecimal", but computer hackers would be tempted to shorten that word to "sex".[11] The etymologically proper Greek term would be hexadecadic (although in Modern Greek deca-hexadic (δεκαεξαδικός is more commonly used).

The traditional Chinese units of weight were base-16. For example, one jīn (斤 (approximately 256*grams) in the old system equals sixteen liǎng (兩 (16g). The suanpan (Chinese abacus) could be used to perform hexadecimal calculations.

Hexadecimal is sometimes used in programmer jokes because some words can be formed using hexadecimal digits. Some of these words are "dead", "beef", "babe", and with appropriate substitutions "c0ffee". Since these are quickly recognizable by programmers, debugging setups sometimes initialize memory to them to help programmers see when something has not been initialized.
An example is the magic number in Universal Mach-O files and java class file structure, which is "CAFEBABE". Single-architecture 32-bit big-endian Mach-O files have the magic number "FEEDFACE" at their beginning. "DEADBEEF" is sometimes put into uninitialized memory. Microsoft Windows XP clears its locked index.dat files with the hex codes: "0BADF00D". The Visual C++ remote debugger uses "BADCAB1E" to denote a broken link to the target system.
Two common bit patterns often employed to test hardware are 01010101 and 10101010 (their corresponding hex values are 55h and AAh, respectively). The reason for their use is to alternate between off ('0' to on ('1' or vice versa when switching between these two patterns. These two values are often used together as signatures in critical PC system sectors (e.g., the hex word, 0xAA55 which on little-endian systems is 55h followed by AAh, must be at the end of a valid Master Boot Record).
The following table shows a joke in hexadecimal:
3x12=36
2x12=24
1x12=12
0x12=18
The first three are interpreted as multiplication, but in the last, "0x" signals Hexadecimal interpretation of 12, which is 18.
Another joke based on the use of a word containing only letters from the first six in the alphabet (and thus those used in hexadecimal) is...
If only dead people understand hexadecimal, how many people understand hexadecimal?
In this case, "dead" refers to a hexadecimal number DEAD (57005 base 10), as opposed to the state of being deceased.
A Knuth reward check is one hexadecimal dollar, or $2.56.

And a picture of something light green.

Binary, but the binary is more of a soft light green. It's a mix of dark light green to counter the brightness. You are trying to make something be something when it isn't. The thread starter had his thread be with very light colors like Light Blue, Light Green and so on with small font.

I think it's spelt 'Hexadecimal', sorry if I'm being a grammar nazi.