Re: MI error msgs and localization

Eli Zaretskii
2006-02-13T19:56:36Z

> From: "Bjarke Viksoe" <bviksoe@hotmail.com>
> Bcc:
> Date: Mon, 13 Feb 2006 19:37:10 +0100
>
> I translate "No symbol table loaded..." into asking the user to switch to
> debug-mode in my tool. "Unrecognized option" pop ups that the GDB version is
> too old, reinstall needed. "Thread x has terminated" refreshed the thread
> list etc etc etc. No user behind a front-end will understand "No such
> process." or "No executable file specified" by itself when the cause of this
> is some magic done by the controlling front-end.

If you _never_ display _any_ MI message verbatim, you can always
arrange for your front end to push LC_MESSAGES=C into the environment
when it runs GDB. Will this satisfy you?

I don't think GDB can in general trust that every front end does such
a thorough job of translating every message, so simply leaving the MI
messages untranslated is not a good idea at this time. Perhaps we
could come up with a smarter solution, one that would allow to
identify the messages in English _and_ display them in the local
language. Nick suggested one idea; perhaps there are others. I'd
encourage you and everyone else to suggest ideas, but I don't think a
simplistic ``don't translate any MI messages'' approach is acceptable.

> >Patches are welcome for any further MI commands that you would like to see
> >implemented.
> >
> >As stated in the manual, MI is still evolving. The best way to make it do
> >the things you want is to participate in its development.
> >
>
> Unfortunately I see this reply too often here. The number of MI questions
> are steadily increasing in this maillist. I believe that the MI interface
> will be the dominant way of using GDB in the future since more people will
> realise that there finally is a not-so-arcane way to interface with it and
> thus integration into the various editor tools becomes wide-spread. So it's
> sad to see the same basic functions with "N/A" in the documentation still.

So what would you like us to do? We are just a bunch of volunteers
maintaining GDB on our free time (well, at least most of us are).
Without new blood coming on board, how would things ever change for
the better?

In any case, thanks for your comments.