Comments on: Integrating Compiler Messages

By: rightgreedba

rightgreedba — Sat, 30 Aug 2008 08:47:53 +0000

steven girl jhon are busy kitchen

By: Erik

Erik — Fri, 26 Oct 2007 04:53:04 +0000

@{Simon,required}: Not only that users have to translate their messages to be heard when asking questions. What happens if that user, giving an e.g. spanish localized error message, gets a useful answer that would help you, too? You’ll never know of it, because you don’t look for the spanish translation of your error message.

One way to prevent this AND have translations available would be to have some kind of unique error key, e.g.:

qt/src/xml/query/expr/qcastingplatform.cpp: ERROR GCC_79546731
qt/src/xml/query/expr/qcastingplatform.cpp: In member function ‘bool CastingPlatform::prepareCasting():
qt/src/xml/query/expr/qcastas.cpp:117: instantiated from here
qt/src/xml/query/expr/qcastingplatform.cpp:85: error: no matching function for call to ‘locateCaster(int)’
qt/src/xml/query/expr/qcastingplatform.cpp:93: note: candidates are: locateCaster(const bool&)

lg
Erik

By: required

required — Thu, 25 Oct 2007 02:32:36 +0000

@Simon: The problem isn’t changing the language (usually you change LC_MESSAGES for this purpose), but users filing bugs in N++ languages you don’t understand and having them to tell to translate or to change their language to English and try to reproduce the failure, so you as the one supposed to judge the bug, understand it. The problem: It costs time and the user may not be able or willing to reproduce, despite a potential valid bug he stumbled about.

By: Simon

Simon — Tue, 23 Oct 2007 18:06:53 +0000

maybe you already know about this feature already … maybe not, so I’ll tell you anyway just to be sure …

you can switch the language for excecuting individual commands like this:
LANG=c make
or
LANG=no g++ trollspeak.cpp

c means “no translation at all”. so with having this feature errors can be understood by programmers not fluent in english without using LANG (default) or by google with using LANG

hope that helps some of you

By: required

required — Tue, 23 Oct 2007 16:02:36 +0000

> Localization and translation of error-messages is a bad thing

Too true. It’s a royal PITA.

By: Marc

Marc — Tue, 23 Oct 2007 15:33:56 +0000

If you are looking at better error message, look at TeX and Intel’s C++ compiler. They include the source code and a line break (TeX) or a caret (icc) in the error message.

Oh, well, not IDE friendly.

By: niko

niko — Tue, 23 Oct 2007 14:29:12 +0000

as Sjaddow says – please don’t localize compiler-error-messages!

I did allready several times switch the locale to english and query google with this error-message – the german one didn’t help at all

By: Sjaddow

Sjaddow — Tue, 23 Oct 2007 10:38:30 +0000

Localization and translation of error-messages is a bad thing, which has prolonged my hunt for answers several times. Instead of searching using the error-message output, which for Norwegian wouldn’t probably yield to many results, you first have to find the english translation of that error-message before you have any hope of any results.

Regular users don’t use compilers, and developers shouldn’t have too much trouble understanding a few english words…