Printable View
Why does this not work?
I want it to use a different language.Code:FormatMessage(
FORMAT_MESSAGE_ALLOCATE_BUFFER |
FORMAT_MESSAGE_FROM_SYSTEM |
FORMAT_MESSAGE_IGNORE_INSERTS,
NULL,
dw,
MAKELANGID(LANG_AFRIKAANS, SUBLANG_DEFAULT),
(LPTSTR) &lpMsgBuf,
0, NULL );
But it puts (null) into the lpMsgBuf.
This is not a translation function... it is part of Windows error reporting mechanism that reads a messagetable resource from your executable file and formats the error message into a string.
With the FORMAT_MESSAGE_FROM_SYSTEM flag, to format a message (short for "Windows Error Message") in afrikans you will need to have a message table resource in your executable or DLL that contains both a section for afrikaans and the numerically indexed message itself in the correct format. Also be aware that this flag causes a sequence of searching the current module (exe or dll) then a series of system resources... collision in error codes can produce some very bizarre results.
Very few IDEs include Message Table editors and I've never found a free standing one so you will have to read up on it here then create and compile them manually using MC.EXE. (The only IDE I know that includes a Message Table editor is POIDE supplied with Pelles C )
Other options to format message allow you to use it with source strings in memory which may or may not make things easier for you.
Also note that if you need to print characters outside the normal 127 ASCII characters you will need to do all of this using Unicode... Which you can believe is no picnic for programmers...
FormatMessage function (Windows)
Quote:
Originally Posted by MSDN Library
EDIT... If it helps here is an error reporting function I wrote as part of an SEH library using FormatMessage()...
Code:#include <errorx.h>
#include <wchar.h>
////////////////////////////////////////////////////////////////
// Error text lookup array
//
#pragma pack(1)
typedef struct MsgText
{ unsigned long code;
wchar_t msg[60]; }
MessageText;
const MessageText Message[] =
{ EXCEPTION_ACCESS_VIOLATION,
L"Access violation: protected system resources",
EXCEPTION_DATATYPE_MISALIGNMENT,
L"A data type misalignment has caused system errors",
EXCEPTION_BREAKPOINT,
L"A breakpoint has been reached while debugging",
EXCEPTION_SINGLE_STEP,
L"Single stepping mode while debugging",
EXCEPTION_ARRAY_BOUNDS_EXCEEDED,
L"Array access outside of allocated memory",
EXCEPTION_FLT_DENORMAL_OPERAND,
L"Floating point error, bad demoromal operand",
EXCEPTION_FLT_DIVIDE_BY_ZERO,
L"Floating point error, attempting to divide by zero",
EXCEPTION_FLT_INEXACT_RESULT,
L"Floating point error, inexact result",
EXCEPTION_FLT_INVALID_OPERATION,
L"Floating point error, invalid operation attempted",
EXCEPTION_FLT_OVERFLOW,
L"Floating point error, operation caused an overflow",
EXCEPTION_FLT_STACK_CHECK,
L"Floating point error, FPU stack corrupted",
EXCEPTION_FLT_UNDERFLOW,
L"Floating point error, operation caused an underflow",
EXCEPTION_INT_DIVIDE_BY_ZERO,
L"Integer math error, attempted to divide by zero",
EXCEPTION_INT_OVERFLOW,
L"Integer math error, operation caused an overflow",
EXCEPTION_PRIV_INSTRUCTION,
L"An attempt was made to execute priveledged instructions",
EXCEPTION_IN_PAGE_ERROR,
L"Memory page protection error",
EXCEPTION_ILLEGAL_INSTRUCTION,
L"An attempt was made to execute unknown CPU instructions",
EXCEPTION_NONCONTINUABLE_EXCEPTION,
L"Too many nested exceptions have occured",
EXCEPTION_STACK_OVERFLOW,
L"Stack overflow",
EXCEPTION_INVALID_DISPOSITION,
L"An invalid disposition error has occured",
EXCEPTION_GUARD_PAGE,
L"Invalid guard page",
EXCEPTION_INVALID_HANDLE,
L"Invalid system handle",
STATUS_NO_MEMORY,
L"Out of memory",
CONTROL_C_EXIT,
L"A keyboard exit has been requested",
0xFFFFFFFF,
L"No text description is available for this error" };
/////////////////////////////////////////////////////////////////////
// Fetch Windows error string
// 1. Searches MessageTable resources for error text matching errcode
// 2. Result is placed at errtext which must be at least MAX_PATH bytes.
// 2. width = right margin, 0 = no right margin
//
void WINAPI GetErrorTextW(unsigned long errcode, wchar_t *errtext, int width)
{ // fetch the current module's handle
HMODULE hmod = GetModuleHandle(NULL);
// locate the message in the local message table
if (FormatMessageW(FORMAT_MESSAGE_FROM_HMODULE | width,
hmod,errcode,0,errtext,256,NULL))
return;
// try the system list
if(FormatMessageW(FORMAT_MESSAGE_FROM_SYSTEM | width,
NULL,errcode,0,errtext,256,NULL))
return;
// now the internal table
int x = 0;
while ((Message[x].code != errcode) &
(Message[x].code != 0xFFFFFFFF))
{ x++; }
FormatMessageW(FORMAT_MESSAGE_FROM_STRING | width,
Message[x].msg,0,0,errtext,256,NULL); }
Too bad it can not spit out windows error messages in other languages.
It can... but they have to exist someplace in your system's resources... either your own program, in a system language resource, or strings in memory.Quote:
Originally Posted by Benji Wiebe
Think about the enormous bloat in windows (as though it's not bad enough already) to have a translator function for every language...
FWIW... the underpinning here is sprintf()... all it does is format message text into a string.
Localization is usually done via string tables. The string table is a resource in your DLL or EXE and is put into the resources section so it can be loaded later. MSVS does have a string table resource editor but I have not used it much.
Yes, for general strings that's true... but windows error messages are all done through message tables....Quote:
Originally Posted by VirtualAce
MESSAGETABLE resource (Windows)
Alas, I am not the man to turn to for localization. :)Quote:
Yes, for general strings that's true... but windows error messages are all done through message tables....
The "other language" error messages are generally included in the language modules you can add to Windows Professional (or better) in versions since XP...Quote:
Originally Posted by VirtualAce
You access them either by specifying a language option or changing Locale settings in control panel.