Re: SRFI 198 Foreign Interface Errors: abusing alists for fun and non-profit hga@xxxxxx (17 Jul 2020 17:44 UTC)
Interaction of gettext and SRFI 198's localization feature Lassi Kortela (26 Jul 2020 21:21 UTC)

Re: SRFI 198 Foreign Interface Errors: abusing alists for fun and non-profit hga@xxxxxx 17 Jul 2020 17:43 UTC

> From: "Marc Nieper-Wißkirchen" <xxxxxx@nieper-wisskirchen.de>
> Date: Friday, July 17, 2020 12:35 PM
>
> Am Fr., 17. Juli 2020 um 19:22 Uhr schrieb Lassi Kortela <xxxxxx@lassi.io>:
>
>> I can try to find some existing ones for both languages. Localized error
>> messages can be quite amusing since the terminology may not be properly
>> established in the target language and the translations are often done
>> by writers who don't grasp the tech at that level of detail.
>
> I don't like localized error messages for another reason. When you
> don't know what to do with the error message (say, a compiler warning)
> and you search the web for it, it works best if everyone uses the same
> search term and not some localized version. :)

Good point.  Fortunately Lassi's API allows you to plug multiple
translations into an error before returning or raising it, if not obvious
on displaying the error object you can query the API to find out which
ones are available, and then hopefully ask for the standard English one
suitable for plugging into your favorite search engines.

- Harold