summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-discuss/2013-February/009188.html
blob: 5fd68678cc84d4a60ab3dc4eb97c3f65078f9de8 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-discuss] Reading payment forms with a scanner
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Reading%20payment%20forms%20with%20a%20scanner&In-Reply-To=%3C201302141108.41619.fri%40tribun.eu%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="009187.html">
   <LINK REL="Next"  HREF="009189.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-discuss] Reading payment forms with a scanner</H1>
    <B>Morgan Leijstr&#246;m</B> 
    <A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Reading%20payment%20forms%20with%20a%20scanner&In-Reply-To=%3C201302141108.41619.fri%40tribun.eu%3E"
       TITLE="[Mageia-discuss] Reading payment forms with a scanner">fri at tribun.eu
       </A><BR>
    <I>Thu Feb 14 11:08:41 CET 2013</I>
    <P><UL>
        <LI>Previous message: <A HREF="009187.html">[Mageia-discuss] Reading payment forms with a scanner
</A></li>
        <LI>Next message: <A HREF="009189.html">[Mageia-discuss] Reading payment forms with a scanner
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#9188">[ date ]</a>
              <a href="thread.html#9188">[ thread ]</a>
              <a href="subject.html#9188">[ subject ]</a>
              <a href="author.html#9188">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>With the risk of sounding grumpy i suggest to hammer your payment provider to 
fix their bug.

I think no solution that include scanning is less time consuming than proof 
read manually typed number.
Besises, you need to proof read the scan anyway ;)

( Apart from that it would be interesting from a technical point to get OCR 
working nicely ;)  )

/Morgan

torsdagen den 14 februari 2013 09.21.36 skrev  Juergen Harms:
&gt;<i> I just had a nasty experience with an ebanking bill that got rejected
</I>&gt;<i> (without sending me a corresponding note) due to a typo.
</I>&gt;<i> 
</I>&gt;<i> Does anybody have experience/advice on using a normal scanner for
</I>&gt;<i> reading the essential fields of payment forms to make ebanking more
</I>&gt;<i> efficient and less error-prone?
</I>&gt;<i> 
</I>&gt;<i> I just did some googling and quick checks along the following lines:
</I>&gt;<i> - tile the payment forms on the scanner (I have an Epson 1260), so that
</I>&gt;<i> only the reading zone at the bottom is visible of each,
</I>&gt;<i> - scan with xsane (selecting adequate settings - different from those I
</I>&gt;<i> ordinarily use)
</I>&gt;<i> - if necessary us gimp to cut away zones with garbage that upset the OCR
</I>&gt;<i> conversion (i.e. tesseract, can be avoided by properly setting the
</I>&gt;<i> reading area in xsane)
</I>&gt;<i> - use tesseract to do OCR
</I>&gt;<i> - filter the output to throw away garbage lines, and to correct
</I>&gt;<i> characters that frequently get mis-interpreted (e.g. B-&gt;8, Z-&gt;2, O-&gt;0,
</I>&gt;<i> D-&gt;0 etc.)
</I>&gt;<i> - output the data thus produced, formatted for copy-paste into the
</I>&gt;<i> ebanking form
</I>&gt;<i> 
</I>&gt;<i> That works surprisingly well, but is excessivly complicated to handle
</I>&gt;<i> (easy to make handling mistakes, not fit to give it to my wife). Are
</I>&gt;<i> there tools that help automating these steps and integrating them into a
</I>&gt;<i> single tool? - if not, it should not be too difficult to do some
</I>&gt;<i> scripting (but I dont want to re-invent things). (And yes, I had tried
</I>&gt;<i> some years ago these small reading sticks that you slide over the form -
</I>&gt;<i> I ditched it: only works on windows, and produces an excessive amount of
</I>&gt;<i> errors).
</I>&gt;<i> 
</I>&gt;<i> Juergen
</I>
-- 
Morgan Leijstr&#246;m
</PRE>










<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="009187.html">[Mageia-discuss] Reading payment forms with a scanner
</A></li>
	<LI>Next message: <A HREF="009189.html">[Mageia-discuss] Reading payment forms with a scanner
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#9188">[ date ]</a>
              <a href="thread.html#9188">[ thread ]</a>
              <a href="subject.html#9188">[ subject ]</a>
              <a href="author.html#9188">[ author ]</a>
         </LI>
       </UL>

<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss">More information about the Mageia-discuss
mailing list</a><br>
</body></html>