It took me awhile to figure out that 96 is hexadecimal. https://developers.google.com/protocol-buffers/docs/encoding The word hexadecimal appears nowhere. It looks like decimal to me. It would be better if the example used 160 instead of 150, so that the hexadecimal representation of the wire encoding would include the letter A.
If it were a wiki, I would just fix it, but I guess this has to go through several years of code-review at Google first. -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To view this discussion on the web visit https://groups.google.com/d/msg/protobuf/-/WHhX5Y8P9TIJ. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
