Menu
Search

Forums

Forum Index

April 26, 2003
Gravatar of Sergey GutnikovPosted by Sergey GutnikovReply
Sergey Gutnikov
Gravatar of Sergey Gutnikov


Reply
Hi Everybody,

I thing RCC.EXE has a bug in UNICODE conversion section.

I have no problems when compiling Dutch resources (code 0x0413), - but when I tried to compile Russian source (code 0x0419) - the result was absolutly wrong.

Pleace, check RCC.EXE especially for sources with characters in range 0x7F-0xFF.

Regards...

Sergey
April 26, 2003
Gravatar of Michail V. SemijonovskichPosted by Michail V. Semijonovskich
in reply to Sergey Gutnikov		Reply
Michail V. Semijonovskich
Gravatar of Michail V. Semijonovskich
Posted in reply to Sergey Gutnikov


Reply
In article <b8drss$27s3$1@digitaldaemon.com>, Sergey Gutnikov says...
>
>Hi Everybody,
>
>I thing RCC.EXE has a bug in UNICODE conversion section.
>
>I have no problems when compiling Dutch resources (code 0x0413), - but when I tried to compile Russian source (code 0x0419) - the result was absolutly wrong.
Tovarish ;)
Yes, I found this bug at least 1 month ago. Now I'm using brcc32 from borland
c++ free compiler kit. It process *.rc files with -32 directive by default, and
then I link output *.res by Digital Mars linker. Unfortunaly, all my efforts
making correct *.res files with rcc (0x19, 204,0x0419) crushed. May be Walter
fix rcc?