Using the glib system additionally to the Qt system would be a great step. Replacing would be not. So I am all for adding a second system just for the glib parts
> Am 04.04.2022 um 19:15 schrieb Gerald Combs <gerald@xxxxxxxxxxxxx>:
>
> On 4/4/22 9:59 AM, Guy Harris wrote:
>>> On Apr 4, 2022, at 7:51 AM, Roland Knall <rknall@xxxxxxxxx> wrote:
>>> No, I dont want to present the error code to the user. But if you create the error string in C we cannot translate it into other languages with the Qt translation system.
>> The Qt translation subsystem is not the only translation system in the universe:
>> https://web.archive.org/web/20210125161711/https://developer.gnome.org/glib/stable/glib-I18N.html
>> Glib itself requires gettext, so we can either use the gettext routines directly, or use the Glib wrappers.
>> (I use the Wayback Machine because the GLib documentation was significantly unimproved relatively recently, so that it's harder, if not impossible, to find things by *topic* rather than by function/datatype/etc. name.)
>
> The un-unimproved documentation is available at https://developer-old.gnome.org/glib/. Unfortunately developer-old.gnome.org/robots.txt disallows crawling of that, so the unimproved version is more likely to show up in search engines.
>
> If we start using GLib's translation system we should add it to https://www.transifex.com/wireshark/wireshark/ and tools/update-tx, but that shouldn't be too difficult.
> ___________________________________________________________________________
> Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives: https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe