Binary Posters

In character encodings, mind adding morse (including the non-printable characters[1]), international code signals[2], and semaphore flags[3]?

Its easy overlook just how much of the information age was already present by the turn of the century. The implications of what they were doing had yet to unfold.

1. https://en.wikipedia.org/wiki/Prosigns_for_Morse_code

2. https://en.wikipedia.org/wiki/International_Code_of_Signals

3. https://en.wikipedia.org/wiki/Flag_semaphore

I like the idea.... but it's a very basic overview, and you still have to check the longer spec if you want to actually code anything... So it's a fun looking poster, but (for me personally) has nothing more than a "fun" value

take for example BMP:

https://raw.githubusercontent.com/corkami/pics/master/binary...

Starts with a BM (two bytes).. ok

File size, 0x42 but 4 bytes long.. so you have to both look at the image and the text on the right to see that you need to pad the length.

a gap??

Data start.. ok, starts at 0x36, and indeed pixel data starts there.. but why is there a gap between the size and the data start? Is it mandatory or optional? Should it be zeros, or it doesn't matter?

Header size.. 0x28.. ok.. so just the bitmap header, not the file header? from 0x0e onwards? Why is there a gap at the end? Should it be? Should it be padded to whatever random number it is?

Width, height, ok... bpp ok.

What is a nb plan?

Image size.. 12? Bytes? Pixels? ... go count to see it's bytes

Then pixel data.. ok

00 00 00 of padding, to pad to 0x41... why? How much padding should there be?

Compare this to eg. this:

https://en.wikipedia.org/wiki/BMP_file_format#Bitmap_file_he...

Offsets, sizes and explanaition of possible values. Also the gaps are explained ("Reserved; actual value depends on the application that creates the image, if created manually can be 0")

Just taking the explanation from the example would explain more: https://en.wikipedia.org/wiki/BMP_file_format#Example_1 <- this example is much more usable (if transformed to a poster format) for me personally.

(yes yes, i'm nitpicking, but the poster just made me google stuff, that should already be on the poster)

The shader characters (B0-B2) on the DOS font page don’t match up between the ASCII table and the example section below. B1 is supposed to be a checkerboard, and B0 and B2 are supposed to be inversions of each other.

(2016) and shared just over a month ago

Some previous discussion:

https://news.ycombinator.com/item?id=14061935

I am a simple man; when I see PETSCII, I upvote.

Neat, ought to etch that one some PCBs.

[45MB] page weight, for those who are casually browsing on a data plan (many images are over a megabyte despite being thumbnail-sized)