[ros-dev] Hardcoded strings
post.center at gmail.com
Tue Dec 20 15:54:54 CET 2005
Thanks guys, thanks for the help, I will have a look at the links, just
looked over cabinet, doesn't look, like it needs to be translated, they
all seem to be debug messages.
Magnus Olsen schrieb:
> you need have knowlges mage whole program unicode safe and ansic safe.
> some part of reactos that using hardcode string are often coding as ansic or
> Wchar and u need make sure the whole functions can take care of both.
> it is not only to remove one string u need look at the whole program before
> u do it. if u want try remove hardcode string then u need have basic
> knowlges of programing and lite more.
> ----- Original Message -----
> From: "Murphy, Ged (Bolton)" <MurphyG at cmpbatteries.co.uk>
> To: <fRy2oo5 at gmail.com>; "'ReactOS Development List'" <ros-dev at reactos.org>
> Sent: den 20 December 2005 13:51
> Subject: RE: [ros-dev] Hardcoded strings
>> David Hinz wrote:
>>> Somewhere in reactos/lib/cabinet I found sourcecode calling functions
>>> like err, and the strings it gave to these functions looked like
>>> something output to the user e.g. errormessages like file * couldn't
>>> be found or something like this, so I wondered, if this should be
>>> As I don't know what kind of stings should be translatable, I
>>> just asked.
>> You need to understand the context in which the message is used. If it's
>> system debug message, it will normally be hardcoded in. If it's a generic
>> Win32 error message it should be picked up with FormatMessage. These will
>> output in the users preferred language via the LANG_SYSTEM_DEFAULT or
>> LANG_USER_DEFAULT flags. Then you have simple MessageBox outputs which can
>> be picked out of a resource file, but are generally hardcoded in. There
>> many other situations and usages, but I'll stop there.
>> As already said, becoming a programmer is the only real way of
>> it all.
>>> Well, you say I should learn some things like structures of resource
>>> files, do you have any links for me?
>> There are thousands of C tutorials on the net. Here are a few:
>> Tutorials : http://www.cprogramming.com/tutorial.html
>> Forgers win32 : http://www.winprog.org/tutorial/
>> Everyone has their favourite books, but these are probably the most
>> for learning C and Windows programming:
>> K & R :
>> C Primer Plus :
>> Petzold :
>> Have fun,
More information about the Ros-dev