1BUGS
2
3Reporting
4---------
5Please do not hesitate to report bugs, and if possible their fixes! If you
6send an example file, please make sure it's small. To report bugs, do one
7of the following:
8
9* go to http://sourceforge.net/bugs/?func=addbug&group_id=7147.
10 This is the preferred way to report bugs.
11
12* send it to one of the authors. Note that sometimes we may be busy, and
13we won't reply it for days. If you post using the previous method, surely
14one of the authors will read it.
15
16* use
17       diff -ru gocr_origin/ gocr_changed/ >patch
18  to create patches
19
20* if you have compiling problems, do not forget to send your configure-output
21  and the config.log file
22
23
24Known bugs (see jocr.SF.net page too)
25----------
26
27v0.51 PGM plain format = P5 is buggy (without libnetpbm), fixed in v0.52
28v0.48 cutting of double melted chars will fail (example: serif MN)
29v0.43 on dithered images gocr runs extremely long (seems to hang)
30v0.41 linker error using g++ and netpbm under SuSE-9.3
31v0.3.5
32  - segfault on some systems which do not support ifalpha(256+x)
33  - hexcode not read from database
34v0.2.5 german umlauts and i-dots are not handled correctly
35    problems high resolution fonts
36v0.2.4 I guess, there are still bugs.
37    Some systems do not handle stack in good manner (AmigaOS?).
38    gocr does extensively consume stack for recursive functions.
39    Therefore you can get memory protection failures or strange results.
40    The worst case is a huge black area. If that is a problem for you
41    request for changing it.
42    --- --- --- --- only for linux freaks --- --- ---
43    By mistake I programmed an endless rekursiv function and ...
44    SuSE6.4+linux2.2.12/13 got several "out of mem" and system CRASHED!!!
45    ulimit: stack=unlimited
46    - if text is framed, frame should be ignored, but it is not
47v0.2.3 still problems with segmentation
48  - gcc 2.95.2 (SuSE6.4) error in load_db(), => fixed (thx to jasper)
49v0.2.1
50  - some people have problems running gocr on DOS/Win95
51    I guess: stack overflow. Is someone able to analyze or fix this?
52  - large black areas on pbm-files cause a segfault on
53    Ultra/Sparc (64bit) machines running Linux (2.1.126).
54    There is a recursive function in the program which causes a
55    stack overflow, which is not detected by the linux-kernel (BUG?).
56    I look for a better solution.
57