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, [email protected] wrote: > > From: IOhannes m zmölnig <[email protected] <mailto:[email protected]>> > To: [email protected] <mailto:[email protected]> > Subject: Re: [PD-dev] translation push > Message-ID: <[email protected] > <mailto:[email protected]>> > 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/>
_______________________________________________ Pd-dev mailing list [email protected] https://lists.puredata.info/listinfo/pd-dev
