Re: [PATCH 05/19] libctf: error handling

[Nick Alcock <nick dot alcock at oracle dot com>]

On 2 May 2019, Nick Clifton uttered the following:

> Hi Nick,
>
>> +static const char *const _ctf_errlist[] = {
>> +  "File is not in CTF or ELF format",		     /* ECTF_FMT */
>
> Have you considered allowing these strings to be translated ?

Sure! But gettextization is a bigger job I haven't even looked at yet.
(e.g. do we need to gettextize all the debugging strings, too?)

I suppose we'd translate the error messages in particular via explicit
gettext() calls in ctf_errmsg()? (Of course, ctf_errmsg() can also
return a strerror() value, but I suppose libc will take care of
translating that for us.)

(But if you call gettext() explicitly, presumably you have to mark the
translatable strings in the array with something too, or they won't land
in the po files? I have no idea, and haven't read the gettext manual in
far too many years... I'd have to do some research first.)