[chirp_devel] Language translation strategy
Dan,
in a recent message: Re: [chirp_devel] #4849, #8415 - Japanese and Chinese translation Bernhard wrote:
I know we're going away from the old way of providing translations; <...>
Can you indicate the strategy that you have decided upon for language translation?
Will it affect the coding of strings during development (continue to code as if 'gettext' is used), or just change the backend process during build to use Google or Watson apis to fill in the gaps on missing translated strings?
My lazy search on this didn't help me.
Thanks.
Can you indicate the strategy that you have decided upon for language translation?
Just gettext, but the effort hasn't been there for a long time. I'm certainly not enforcing that strings need translation and I'm not really super excited about renewing that effort.
So, mark 'em if you want, but don't do it for me :)
--Dan
participants (2)
-
Dan Smith
-
Rudolph Gutzerhagen