4 ms·
Experiments with some common glyphs. (!) -- 8th suggestion, after three apparently identical "upside-down 'i'" (including an "upside-down capital 'I' with a do
by uvdiv 14y ago
Experiments with some common glyphs.
(!) -- 8th suggestion, after three apparently identical "upside-down 'i'" (including an "upside-down capital 'I' with a dot underneath")
(@) -- 1st suggestion
(#) -- not suggested. Top suggestion is "capital 'H' with stroke"
($) -- not suggested, although the 14th is an indistinguishable glyph "Canadian syllabics carrier sh" 0x165a, a phoenetic symbol for representing a Canadian aboriginal language.
(%) -- 1st suggestion
(^) -- 10th suggestion, to be fair this one is impossible
(&) -- not suggested (fried shrimp lol)
(*) -- 3rd suggestion
(?) -- 1st suggestion
(∫) -- 1st suggestion
(∂) -- 4th suggestion (1st one is same thing in boldface)
----------
This is suggests a really easy way to greatly improve the results: weight them by a prior probability (i.e., frequency of occurrence in a letter count). The OCR itself seems pretty good. Common math symbols are more likely than silly shrimps. Glyphs from common languages are more probable than esoteric ones, and real languages more than constructed ones. Plain glyphs are more common than variants (bold/italic) -- and these should be grouped together anyway. fried shrimp horseshoe.
- macleodan 14y agoWhy would you use this tool to lookup common characters found on your keyboard? Maybe a better idea is to show uncommon characters first.
- quirm 14y agoExactly, this is why priors for latin alpha characters are not set that high - you have them on your keyboard already.
- peapicker 14y ago$#& - all were my first suggestion... perhaps I draw them better than you do? :)
- Raphael 14y agodollar sign works if you draw the vertical line all the way through.
- FreeFull 14y ago& only seems to work if drawn with the top loop broken.
- JensenDied 14y agoI was only trying to see the fried shrimp http://imgur.com/Ev3gGwd http://imgur.com/Ev3gGwd
- quirm 14y agoThere is a prior probability in the results - but it's hard to balance it so that latin characters don't dominate the results if you search something else. That is why I opted for the way it is now - this is a tool to find unicode characters, you have latin characters on your keyboard. It's not really meant for OCR
- pseut 14y agoYou could do prior probability conditional on not being available on a US keyboard, or at least make that an option. edit: just read your comment elsewhere on the page indicating that you do something like what I described.