Re: Uses for Screen OCR Technology ???


"Oliver Wong" <owong@xxxxxxxxxxxxxx> wrote in message
news:qWcOg.10941$bf5.3350@xxxxxxxxxxx

"Peter Olcott" <NoSpam@xxxxxxxxxxxxx> wrote in message
news:Px%Ng.11785$Tl4.9550@xxxxxxxxxxxxx

"Oliver Wong" <owong@xxxxxxxxxxxxxx> wrote in message
news:vg_Ng.8115$E67.2267@xxxxxxxxxxx


Does it work with the fonts "WingDing", "Symbols", or my specially
crafted "all characters are invisible" font?

It works with any machine generated character glyphs that have visible pixels
on the screen. I don't know what your {"all characters are invisible" font}
is, but if the foreground and background colors are identical, then it will
not work. No character recognition technology can possibly work if there is
nothing to recognize.

I thought I recall you exploring peering directly into RAM, so perhaps
under some conditions you could have determine what text had been entered into
a GUI control, even if such text were invisible. I'll now assume that you
don't do that, and base your recognition entirely on the set of pixels
captured.

Yes there are methods where this works some of the time. The biggest case where
this never works is when the text is first written to a memory bitmap, and the
bitmap is then copied to the screen.


In my WingDing font, the character for capital A looks like a right hand
forming the V sign (http://en.wikipedia.org/wiki/V-sign). In some other font,
that exact same glyph might be used for the character lowercase zeta. Without
peering into RAM, how would you know which of the two fonts are being used to
tell wether to recognize such as glyph as A or zeta?

- Oliver

If there is even a single pixel that is much as a single shade of difference, my
technology can know with certainty which is which. There are various heuristics
that work with great reliability if two glyphs are identical. The heuristics
generally maintain the reliability above 99%. The only case where accuracy may
possibly drop below 100% is where there are two different glyphs in the same
font instance that are identical. If two glyphs are identical, yet, the between
glyph pixel spacing is different, the SeeScreen can still determine which is
which with 100% certainty.


.

Relevant Pages

  • Re: Advice for OCR solution (or alternative)
    ... My font is not fixed width. ... between each character (sometimes more than one pixels width). ... "Roedy Green" wrote in message ...
    (comp.lang.java.help)
  • Re: Scaling faces
    ... > I'm trying to set up my emacs to give me 164 or whatever chars width ... > a system font issue - presumably I'm using bitmapped fonts which can't ... integer number of pixels wide. ... point font is 8 pixels wide per character, ...
    (comp.emacs)
  • Re: How to convert font metrics to screen metrics ?
    ... (ie reading font files), to "screen metrics"? ... Character v, Arial.ttf, Size 10 ... He's trying to figure out how many pixels wide a size 10 (Points? ...
    (comp.fonts)
  • Re: PEP 3131: Supporting Non-ASCII Identifiers
    ... bitmap representations of the glyphs to avoid the font issues) of the ... glyphs that the PEP 3131 would allow in identifiers? ... for a font that has all these characters. ... lookup a specific character, I recommend to go to the Unicode ...
    (comp.lang.python)
  • Re: Advice for OCR solution (or alternative)
    ... > My font is not fixed width. ... > between each character (sometimes more than one pixels width). ... A brute-force "identify glyph" would compare each glyph of ...
    (comp.lang.java.help)