The Bogosity Forum

General Bogosity => The Podcast => Topic started by: MrBogosity on September 13, 2015, 05:59:59 PM

Title: Podcast for 14 September 2015
Post by: MrBogosity on September 13, 2015, 05:59:59 PM
[mp3]http://podcast.bogosity.tv/mp3s/BogosityPodcast-2015-09-14.mp3[/mp3]


Co-Hosts: Dave Turcotte, Matt Page, and Jeremiah Harding

IP Special:
This Week's Quote: "Digital files cannot be made uncopyable, any more than water can be made not wet." —Bruce Schneier
Title: Re: Podcast for 14 September 2015
Post by: evensgrey on September 14, 2015, 09:30:03 AM
How does Adobe actually encode their font rendering data?  If they use something like PostScript (which is itself a derivative of Forth) then they might actually be computer programs.  They would hardly be the only examples of programming languages that specify images.
Title: Re: Podcast for 14 September 2015
Post by: MrBogosity on September 14, 2015, 06:58:21 PM
Quote from: evensgrey on September 14, 2015, 09:30:03 AM
How does Adobe actually encode their font rendering data?  If they use something like PostScript (which is itself a derivative of Forth) then they might actually be computer programs.  They would hardly be the only examples of programming languages that specify images.

The only actual code I know of that's in them is the hinting. At any rate, Postscript is a graphics format. The fact that you use a language to describe it means nothing. Code is code, and graphics is graphics.
Title: Re: Podcast for 14 September 2015
Post by: evensgrey on September 15, 2015, 05:38:58 PM
Quote from: MrBogosity on September 14, 2015, 06:58:21 PM
The only actual code I know of that's in them is the hinting. At any rate, Postscript is a graphics format. The fact that you use a language to describe it means nothing. Code is code, and graphics is graphics.

That rather depends on the fullness of the language in question.  Scene Description Language (used to describe scenes for rendering in the Persistence Of Vision Raytrace renderer) qualifies as a programming language, for instance, and the scene descriptions are thus programs.

I think you're ignoring the fact that data isn't instructions, but instructions can generate data.  PostScript isn't a graphics format, it's a way of instructing a graphics generation system on what graphics to generate, and anything that understands PostScript properly should produce identical output to the limits of the output device.

TeX (and all the weird and wonderful packages that layer on top of it to make it easier to use) do the same thing, quite explicitly and by design.  You can go back centuries and look at Heraldry doing exactly the same thing:  Using a systematic means of describing the image in such a way that any rendering system (or person) that understands the description can render the image described identically to the limits of the renderer's abilities.
Title: Re: Podcast for 14 September 2015
Post by: MrBogosity on September 16, 2015, 05:22:55 AM
Quote from: evensgrey on September 15, 2015, 05:38:58 PMPostScript isn't a graphics format, it's a way of instructing a graphics generation system on what graphics to generate

Uh, those are the same thing. A jpg file is a way of instructing a computer to display a graphic as well. If you're going to define that as code, then ANYTHING is code!