Linked by Thom Holwerda on Wed 3rd Oct 2012 01:41 UTC, submitted by MOS6510
General Development "Originally published in 1978 and updated in 1988, The C Programming Language is considered a 'must-read' classic by most programmers and is generally known simply as 'K&R'. To mark the publication of an ebook version of the 1988 second edition, we interviewed coauthor Brian Kernighan about the C programming language, the book, and future trends." And an Oxford comma to boot. The way it should be.
Thread beginning with comment 537425
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: How it should be done
by dnebdal on Wed 3rd Oct 2012 12:28 UTC in reply to "How it should be done"
dnebdal
Member since:
2008-08-27

If you think that's bad, try to write a program that outputs a bare-minimum font in OTF format (that will show up with the right names on more than one OS). It's all written by people who assumes the readers will already know the general idea, none of the standards agree (or even address) what parts are optional vs. required, and certain parts (CFF, I'm looking at you) are horribly obtuse - not to mention that you have to guess which random old adobe-produced reference it's actually documented in.

(And don't get me started on the variable-length integer encoding used only in the CFF block. )

Edited 2012-10-03 12:33 UTC

Reply Parent Score: 2

RE[2]: How it should be done
by kwan_e on Wed 3rd Oct 2012 13:01 in reply to "RE: How it should be done"
kwan_e Member since:
2007-02-18

If you think that's bad, try to write a program that outputs a bare-minimum font in OTF format...


You've piqued my interest and I'll probably try it. I pretty much have the same experience with the PDF parser, in that Adobe "standards" "documentation" is really poor and all over the place.

The good thing about RFCs is that they do make it easy to look for references.

Reply Parent Score: 2

RE[3]: How it should be done
by dnebdal on Thu 4th Oct 2012 08:24 in reply to "RE[2]: How it should be done"
dnebdal Member since:
2008-08-27

It's immensely satisfying when it finally works, so go for it. ;)
Admittedly, that's true for any project where you can validate your code against existing real-world implementations - there's a moment of joy the first time you actually manage to parse an image/the ELF headers/what have you - and the first time you make a font file that appears with the right names in all OSes.

Tip: Microsoft's font validator made things easier. ( http://www.microsoft.com/typography/fontvalidator.mspx ). I still haven't found anything that will validate the CFF block, though - and that's the messiest part.

Edited 2012-10-04 08:26 UTC

Reply Parent Score: 3