2009-02-02 10:29:43 |
Polevoy Dmitry |
bug |
|
|
added bug |
2009-02-02 10:29:43 |
Polevoy Dmitry |
bug |
|
|
added attachment 'STDA50.TIF' (STDA50.TIF) |
2009-02-02 10:30:21 |
Polevoy Dmitry |
bug |
|
|
added attachment 'stda50.mingw.txt' (MinGW version output) |
2009-02-02 10:31:06 |
Polevoy Dmitry |
bug |
|
|
added attachment 'stda50.msvc8.txt' (MSVC version output) |
2009-02-02 10:33:43 |
Polevoy Dmitry |
description |
In Windows OCR results differ in MinGW and MSVC. Look at line 4. One space (0x20) in MinGW version output corresponds 4 symbols (0x0D,0x0A,0x0D,0x0A) in MSVC version output |
In Windows OCR results differ in MinGW and MSVC. Look at line 4. One space (0x20) in MinGW version output corresponds 4 symbols (0x0D,0x0A,0x0D,0x0A) in MSVC version output.
I use 'smarttext' as output format.
What OCR results do you have in your platform? |
|
2009-02-02 11:29:56 |
Polevoy Dmitry |
cuneiform-linux: importance |
Undecided |
Critical |
|
2009-02-02 11:29:56 |
Polevoy Dmitry |
cuneiform-linux: statusexplanation |
|
It blocks quality control (by comparing smarttext output for different builds) |
|
2009-02-02 12:29:05 |
Jussi Pakkanen |
cuneiform-linux: importance |
Critical |
High |
|
2009-02-02 12:29:05 |
Jussi Pakkanen |
cuneiform-linux: statusexplanation |
It blocks quality control (by comparing smarttext output for different builds) |
On OSX I get one space.
I lowered the severity, because 'critical' should be reserved for issues such as "fails to build" and so on. |
|
2009-02-03 13:35:18 |
Yury V. Zaytsev |
bug |
|
|
added attachment 'stda50.txt' (Ubuntu 8.04 / GCC) |