Talk:Metafont
This is the talk page for discussing improvements to the Metafont article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
This article has not yet been rated on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||||||||||
Please add the quality rating to the {{WikiProject banner shell}} template instead of this project banner. See WP:PIQA for details.
Please add the quality rating to the {{WikiProject banner shell}} template instead of this project banner. See WP:PIQA for details.
Please add the quality rating to the {{WikiProject banner shell}} template instead of this project banner. See WP:PIQA for details.
|
TeX or Template:TeX
I'm reverting user:Schutz's last change, until he or she defends the implicit claim that "TeX" is more correct than Knuth's own preferred form "Template:TeX". —Tamfang 08:11, 26 February 2007 (UTC)
- This was discussed on Talk:TeX. Knuth's prefered form is not Template:TeX; he wrote an entire article to explain how to typeset the logo properly (see TeX#_note-29), that is, where each letter subtly touches its neighbours. In addition, Knuth himself uses the simple form "TeX" in HTML, see for example [1] on his web site, which seems to indicate that this is his preferred form, at least in HTML. Schutz 12:47, 26 February 2007 (UTC)
As far as I know, TeX should be used when you can't use a proper "full" typographic approach (e.g. using a typewriter or in simple text file); but it seems to me that Template:TeX is very close to how the logo looks like when I write \TeX\ and print the document... (but I haven't magnified the on-screen page and measured the characters and their relative positions!) Ittakezou0 (talk) 12:12, 3 November 2008 (UTC)
Douglas Hofstadter
I recall an attack by Hofstadter on Knuth in relation to the nature of universality specifically on the basis of 'metafonts'. I believe the article in question is in 'Metamagical Themas' - 203.206.251.225 12:27, 29 April 2007 (UTC)
- Yes, I remember it too. Hofstadter's point was that the diversity of fonts cannot be captured by a manageably small number of variables. Doesn't invalidate the metafont concept for subsets of that variety, though. —Tamfang 19:13, 3 May 2007 (UTC)
Note 1
The note is wrong, at least in the online file. That cite doesn't appear in the document.
Citation; genre
The citation about getting an artist to design a font with 60 parameters does not occur in the cited document.
- Indeed. Someone needs to provide a proper citation. VasileGaburici (talk) 13:48, 2 September 2008 (UTC)
- Fixed now. VasileGaburici (talk) 14:02, 2 September 2008 (UTC)
The genre of MetaFont is definitely not "computer font". I changed it to "computer language", but if there is a more accurate genre, please correct me. --Slashme 12:43, 11 October 2007 (UTC)
Definition
According to me what is written in the preamble is wrong: METAFONT interpreter runs METAFONT code (as interpreters do), and the output is (well, can be since the interpreter can output strings to the console too, but this is not the real purpose of METAFONT) a bitmapped collection of glyphs into a single file in a specific format (gf that can be compressed in pk). The METAFONT interpreter interprets, and the result of this interpretation is not a convertion, but a generated bitmap font (and a metric file, TFM, that is the only thing [[TeX|Template:TeX]] needs to do its job).
Then, this generated bitmap font in the specific format (gf or crunched pk), can be used by any software able to use it, i.e. able to read the bitmap and embed it someway, somewhere. E.g. a DVI reader must be able to load gf/pk bitmap fonts (which are not embedded into DVI), and so must do drivers like dvips, dvipdf (these ones do convert from DVI format into other format), or engines that do not output DVI but a format that can embed bitmaps (as pdftex... and as far as I know is the only one).
So the statement that can be included in PostScript is unclear and not fully correct. It should changed to something like that can be used by softwares to show/print glyphs or something like that.
The METAFONT system and METAFONT outputs (both tfm and gf/pk) are used maily by the [[TeX|Template:TeX]] system (I mean by this that TFMs are used by (vir)tex program and bitmaps by DVI converters/readers), but this does not mean that the only place where they can be embedded is PostScript files... There's e.g. PDF too at least.
Or at least a e.g. should be added to stress the fact that the use in PostScript files is just an example among several possibility.
151.32.17.100 (talk) 00:21, 28 June 2008 (UTC)
{{primarysources}}
User:Thumperward added {{primarysources}}. This is rather ludicrous for a piece of software. 90%+ of software pages on Wikipedia do not have any peer-reviewed references. Unless User:Thumperward can come up with a good reason why METAFONT needs to meet this standard, I will remove {{primarysources}} in three days. I'm not sure if the TUGboat journal meets the stringent criteria of say, lwn.net, cough, cough, but it surely isn't edited by DEK. There's one in-depth comparison paper for the PostScript conversion methods by K. Píška. I moved it to references. VasileGaburici (talk) 18:18, 14 August 2008 (UTC)
- All articles need to meet our standards of sourcing. That most software articles fail is because most software articles are low-quality. This article should not be low-quality. We need more than one decent secondary source (preferably a lot more) before this article should be considered to be adequately referenced. Chris Cunningham (not at work) - talk 13:48, 3 November 2008 (UTC)
- All unassessed articles
- Pages using WikiProject banner shell with duplicate banner templates
- Start-Class Computing articles
- Unknown-importance Computing articles
- All Computing articles
- Mid-importance Computing articles
- WikiProject templates with unknown parameters
- Start-Class Linux articles
- Unknown-importance Linux articles
- WikiProject Linux articles