|WikiProject Typography||(Rated Start-class, Mid-importance)|
|WikiProject Articles for creation||(Rated Start-class)|
- 1 Someone?
- 2 A site license for the OCR-A font is very expensive
- 3 Licensing
- 4 Spacing
- 5 OCR-A Extended
- 6 Copyright Violation?
- 7 To John Sauter (and everyone else)
- 8 Commercial links
- 9 Exclamation Point versus Exclamation Mark
- 10 alternate question mark
- 11 Skala code points
- 12 Conflict of Interest suggestion
- 13 Westminster?
"so someone undertook to create a free font"
- John Sauter. From the ReadMe.txt in the Debian source package.
A site license for the OCR-A font is very expensive
The font is not licensed under the GPL, since fonts are not subject to copyright in the United States. The font is free as in no cost. I will edit the article to make this clear.
The Debian packaging is licensed under the GPL. Here is the copyright file from that package. Note that my e-mail address has changed—it is now John_Sauter@systemeyescomputerstore.com.
This package was debianized by Gürkan Sengün <email@example.com> on Wed, 2 May 2007 16:17:15 +0200.
It was downloaded from http://sourceforge.net/projects/ocr-a-font
John Sauter <J_Sauter@Empire.Net>
The Debian packaging is (C) 2007, Gürkan Sengün <firstname.lastname@example.org> and is licensed under the GPL, see `/usr/share/common-licenses/GPL'.
This seems wrong:
The font is monospaced, with the printer required to place glyphs 0.1 inch apart, and the reader required to accept any spacing between 0.9 and 0.18 inch.
You are quite correct. I could not find a citation on-line. I saw it in the ANSI documentation, but it is copyrighted and its owner does not permit it to be visible on-line. John Sauter (talk) 20:49, 26 January 2009 (UTC)
You noticed they extended OCR-A with extra characters. You liked the OCRA font because it's much better. OCR-A Extended has to support extra languages such as: Finnish, Spanish, French, German, Dutch, Swedish, Norwegian, Danish, etc. All of the capital letters (A with diaeresis, A with ring above, N with tilde, O with diaeresis, U with diaeresis) have been same. The font file name is OCRAEXT.TTF but you can edit it with Font Creator. It's bundled with MS Office Publisher 2003. All of the other Opentype fonts with truetype outlines (such as Palace Script MT, Rockwell and Andy) were installed with Publisher 2003. The font can be altered. You tried opening the font it has no problems! The middle dot was missing. Just add it to the font, and it has no problems. Ligatures fi and fl were mapped to the Private Use Area. 220.127.116.11 (talk) 05:05, 25 April 2009 (UTC) —Preceding unsigned comment added by John Sauter (talk • contribs)
I have raised the OCR-A Extended section to the top level rather than have it a subhead under Code Points, since it is a separate font. I do not have MS Office Publisher 2003 installed on my computer, so perhaps that is why I do not see the font samples correctly.
It would be better to render the characters of OCR-A Extended as images, so everyone can see what they look like. This is what was done with the characters of OCR-A. It would be sufficient, in my opinion, to show only the characters not present in OCR-A, and give their CP1252 and Mac Roman code points. John Sauter (talk) 10:57, 26 April 2009 (UTC)
I learned about a font that calls itself "OCR-A Extended" at this URL: http://www.de.newfonts.net/index.php?pa=show_font&id=142. Reading it into fontforge, I get these error messages:
The following table(s) in the font have been ignored by FontForge Ignoring 'VDMX' vertical device metrics table Glyph 2 is called ".notdef", a singularly inept choice of name (only glyph 0 may be called .notdef) FontForge will rename it. The glyph named mu is mapped to U+00B5. But its name indicates it should be mapped to U+03BC. The glyph named Omega is mapped to U+2126. But its name indicates it should be mapped to U+03A9. The glyph named Delta is mapped to U+2206. But its name indicates it should be mapped to U+0394. The glyph named fraction is mapped to U+2215. But its name indicates it should be mapped to U+2044. The glyph named fi is mapped to U+F001. But its name indicates it should be mapped to U+FB01. The glyph named fl is mapped to U+F002. But its name indicates it should be mapped to U+FB02. The glyph named periodcentered is mapped to U+2219. But its name indicates it should be mapped to U+00B7. The glyph named macron is mapped to U+02C9. But its name indicates it should be mapped to U+00AF. The glyph named foursuperior is mapped to U+F003. But its name indicates it should be mapped to U+2074.
The font appears to have many of the accented letters that are missing from OCR-A, but it does not have the OCR Hook, OCR Chair and OCR Fork characters. Is this font the same as the OCR-A Extended font that is distributed by Microsoft? John Sauter (talk) 17:47, 1 May 2009 (UTC)
None of the other font pages have the fonts displayed like this, so I have removed the font tag and panose information, and also edited the text to be clearer. I couldn't find a reference for the number of glyphs or languages present in the font anywhere? — M3TAinfo @ 23:20, 24 January 2010 (UTC)
Someone marked the following text as a possible copyright violation:
"In 1968, American Type Founders produced OCR-A, one of the first optical character recognition typefaces to meet the criteria set by the U.S. Bureau of Standards. The design is simple so that it can be easily read by a machine, but it is more difficult for the human eye to read."
The footnote, labeled "background on OCR-A from Adobe", refers to the following paragraph:
"In 1968, American Type Founders produced OCR-A, one of the first optical character recognition typefaces to meet the criteria set by the U.S. Bureau of Standards. The design is simple so that it can be read by a machine, but it is slightly more difficult for the human eye to read."
Notice that in this two-sentence excerpt, two words have been changed. It hardly seems like a copyright violation to extract a two-sentence description, particularly when it is footnoted so there is no question of its source. In the absence of an objection by the copyright owner of this text, I regard the accusation of copyright violation as frivolous.
To John Sauter (and everyone else)
John Sauter has apparently removed my edit which I intended to note (though I now realize that that's the wrong template for this meaning) that I believe the text of the first sentence from "In 1968" to "eye to read" is perhaps a copy/paste copyvio from the (first) link provided and that since WP:NOR says "Best practice is to write articles by researching the most reliable sources on the topic and summarizing what they say in your own words" (emphasis added by me) and re:WP:COPYPASTE I think the text should be changed.
Also, even though this is unrelated to this specific page, does anyone know if there is a template that transmits the meaning of the slightly intrusive Template:Copypaste as the inline-superscripted-style comment?? —Preceding unsigned comment added by 18.104.22.168 (talk) 08:30, 11 May 2010 (UTC)
You are correct, I have removed your edit suggesting that the reworded two-sentence description is a copyright violation. Before doing so, I posted my reason here in the talk page, and waited for any response from you.
If I copy-and-paste a single letter of the alphabet from a copyrighted work, that is not a copyright violation. At the other extreme, if I copy-and-paste the complete text of a 500-page novel, that is a copyright violation. Where between these extremes copy-and-paste becomes a copyright violation is unclear, and reasonable persons may differ. I believe that the slightly reworded two-sentence description is not a violation of Adobe's copyright, and apparently some font vendors agree with me. See, for example, this web site: click on the “about” tab. John Sauter (talk) 21:15, 11 May 2010 (UTC)
There are a large number of links to off-the-page sales adverts from individual font vendors, some of these masquerading as references. I found this while cleaning up after an SEO / marketeer who had a significant number of consecutive edits adding links to a commercial site. Guy (Help!) 19:45, 30 May 2010 (UTC)
- After reading the Wikipedia article on citation spam at WP:REFSPAM, I think this is a close call. The links provide useful background information about the font, in addition to the opportunity to purchase it. For example, links to commercial vendors are used when discussing the inconsistency in assigning code points to characters by those various vendors. The fact that the article contains a link to a free version also counts against a commercial motive. John Sauter (talk) 21:22, 30 May 2010 (UTC)
Exclamation Point versus Exclamation Mark
Someone changed the name of character U+0021 from Exclamation Mark to Exclamation Point. I am changing it back to Exclamation Mark because that is the name used in the Unicode code charts. See Unicode code charts: ASCII punctuation. John Sauter (talk) 22:07, 5 May 2011 (UTC)
alternate question mark
- The regular question mark has a dot at the baseline; the alternate question mark instead extends the vertical line to the baseline. This is hard to see in the article, but if you click on the glyph you can see it easily in the magnified view. John Sauter (talk) 18:53, 4 July 2011 (UTC)
Skala code points
I've removed a subsection describing the code point assignments in Matthew Skala's version of OCR-A because most of the information given there was inaccurate. For instance, it describes the character he had encoded at U+00D6 (LATIN CAPITAL LETTER O WITH DIAERESIS) as "Latin Small letter o"; on examination of the font it's clear that the letter is a modified version of the capital O - as it should be for that code point - and not of the small o, which has a different shape. Similarly, the glyph at U+00DC has no tail at lower right - it is a capital glyph, correct for that code point - but the text I removed from the article claimed that it was a lowercase u and therefore incorrect. Other items on the list depend on assumptions that punctuation glyphs encoded at their official Unicode code points are "nonstandard" because of not being encoded at their legacy ASCII code points, or that the glyph that looks like a black box and is encoded as such should really be encoded as a nonprinting control character (which is an original interpretation of the standards, to say the least). The overall impression given was that the font contained many encoding errors; since that's both false and an original interpretation (the citation given was to the font itself, a primary source, not to anything supporting the claims of incorrect encoding), I think it's inappropriate for a Wikipedia article to go into this level of detail at all. Better not to list encoding errors unless we can both find them in a secondary source and present them accurately. Maybe the other "nonstandard encoding" subsections should be removed too; I haven't dug into their respective fonts in detail yet, but it's not clear that the article should contain this information for any fonts, correctly or not. 22.214.171.124 (talk) 01:31, 26 October 2011 (UTC)
It was not my intention to imply that Matthew Skala's rendition of OCR-A was in error—only that the code points he had chosen were not the same as those detailed in section 4. Since he used the same Metafont sources as I (and others) did, I assumed that his character shapes matched the glyphs in the tables. If his shapes for U+00D6 and U+00DC look like upper-case rather than lower-case letters, then we should present his glyphs to make this clear.
I suspect that U+25A0 (black square) is a better coding for Character Erase than U+007F (delete). Perhaps Matthew Skala's codings should be presented first, and the others as deviations from his choices.
As far as the citation is concerned, what better reference than to the primary source, which is the font itself, presented as a downloadable file? That reference permits anyone to verify the summary information in the article. How could a secondary source possibly be better?
I believe that there is value in noting the different code points used for some characters by the various sources of the OCR-A font. Users of these fonts will be made aware that the various sources code some characters differently, and will not be surprised when documents are printed incorrectly when they switch sources. John Sauter (talk) 01:58, 27 October 2011 (UTC)
- I think it's problematic to present any set of codes as a base and then everything else in reference to it; with the best intentions in the world the "base" set of codes would inevitably end up getting inappropriate emphasis. A better approach might be to have a table with, say, the descriptions of the characters as rows and the fonts as columns, showing the code point used for each one without using any as a default. (Presumably limited to the characters on which any disagreement exists - there's no point regurgitating the entire ASCII set.) That kind of table might also be more convenient for readers because it makes it easier to recognize any consensus that may exist among the fonts. However, I still wonder about whether this information should be in this article in any form. It's important information, yes, but it also seems pretty squarely within Wikipedia's definition of "original research" because this kind of comparison is, as far as I can tell, published nowhere else but in this Wikipedia article. Wikipedia policy is that no information should be published only in Wikipedia: it all has to come from elsewhere, not only the individual facts but also any synthesis of them. So unless there's been a published comparison of code points in different OCR-A fonts, there shouldn't be one in Wikipedia even if the existence of one would be a valuable thing.
- I think, also, that even if you and I agree that the presentation is neutral and appropriate, the fact that you seem to be (at least, you are using the same name as) the maintainer of one of the fonts in question, creates a huge opening for third parties to raise conflict of interest objections. Understand that I'm not raising that objection myself. My own suggestion, though I realize it'd create a fair bit of extra work for you and you're welcome not to do it, is that it'd be a good thing if you prepared a code point comparison (in whatever form you think best, including if that means using your own or Skala's or any other font as a base) and published it as an article in your own space - not on Wikipedia. You've clearly got the expertise as well as access to some commercial fonts that aren't available in free public space, so your own posting would be an appropriately authoritative secondary source that the Wikipedia article could then reference instead of including verbatim. 126.96.36.199 (talk) 02:48, 28 October 2011 (UTC)
- Presenting a table of all characters on which there is disagreement over code points would be useful, but I fear that the table would be clumsy because of its size. That's why I presented as a series of lists, one per implementation. I do not have access to the commercial fonts; the lists are based on the public documentation of the fonts, and the references lead to that documentation. You are welcome to convert the information in the article into such a table, and judge for yourself whether it is better than the separate lists. Perhaps you can find an effective structure for the table that escapes me.
- I also do not agree that Wikipeia policy forbids a synthesis of referenced facts, provided that the synthesis does not advance a point of view not clearly advanced by the sources. See your reference to Original Research for details about this rule. A presentation of the differences between implementations, without any statement that any of them are “bad,” meets this rule, I think. Based on the information in the tables the reader can judge the implementations for himself, of course. John Sauter (talk) 12:33, 29 October 2011 (UTC)
Conflict of Interest suggestion
It has been suggested that I might have a conflict of interest because I produced and distributed a free implementation of the OCR-A font. I do not sell that implementation—it is freely available on SourceForge, including sources, as noted in the article. My employer at the time I produced and distributed that implementation appreciated the fact that it did not have to pay for an OCR-A font, but otherwise did not care what I did with it, and has received no benefit from my distribution.
The article claims that Westminster was "designed to be machine-readable" and has claimed this for a long time -- since 2008. Is there any proof this is true? Do any reliable references exist for this claim? Although I'm certainly no expert, it seems to me that (given Westminster's proportionally-spaced design) it was not designed to be machine-readable, but merely to visually mimic the E-13B MICR font [which is machine-readable]. The only reason I didn't go ahead and remove it was that I wanted to ask those of you who have more expertise than I do whether there's any proof it actually was designed to be machine-readable. Additionally, the article on Westminster is woefully devoid of references. Microsoft's page about Westminster says it was "made ... along the same lines" [as E-13B] but does not say that Westminster is, nor that it is not, designed to be machine-readable. Does anyone have any thoughts to add? -- 188.8.131.52 (talk) 06:15, 29 May 2013 (UTC)