Ah, good point. Doing a string look up might not be the best thing, although maybe we can check performance metrics. It's not like there isn't string handling going on already and I doubt that gettext is doing allocations during a lookup.

On Sep 13, 2018, at 5:40 PM, pd-dev-request@lists.iem.at wrote:

From: IOhannes m zmölnig <zmoelnig@iem.at mailto:zmoelnig@iem.at> To: pd-dev@lists.iem.at mailto:pd-dev@lists.iem.at Subject: Re: [PD-dev] translation push Message-ID: <af76dab3-e406-004d-54dd-3be83d69f3b4@iem.at mailto:af76dab3-e406-004d-54dd-3be83d69f3b4@iem.at> Content-Type: text/plain; charset="utf-8"

On 9/13/18 3:00 PM, Dan Wilcox wrote:

...

For the developers, could we consider building Pd with gettext support in the core? Then we could translate most of the internal strings without having to resort to string matching on the GUI side.

what would be the benefit of that? conceptually, i *quite* like the idea of not doing translation work in the audio thread.

-------- Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/