OCR results differ in MinGW and MSVC

[Polevoy Dmitry]

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?

[Polevoy Dmitry (openocr-polevoy)]

It blocks quality control (by comparing smarttext output for different builds)

[Jussi Pakkanen (jpakkane)]

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.

[Yury V. Zaytsev (zyv)]

I'm getting one space (0x20) here.

[Polevoy Dmitry (openocr-polevoy)]

MSVC OCR results coincide with old Cuneiform results.

2009/2/3 Yury V. Zaytsev <email address hidden>

> I'm getting one space (0x20) here.
>
> ** Attachment added: "Ubuntu 8.04 / GCC"
> http://launchpadlibrarian.net/21930098/stda50.txt
>
> --
> OCR results differ in MinGW and MSVC
> https://bugs.launchpad.net/bugs/324242
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Linux port of Cuneiform: New
>
> Bug 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.
>
> I use 'smarttext' as output format.
>
> What OCR results do you have in your platform?
>

[Polevoy Dmitry (openocr-polevoy)]

IMHO: reason is in
rfrmt.dll

but I can't check it separatly from

cimage.dll
rdib.dll
rimage.dll
rneg.dll
rstuff.dll