Udo Richter wrote:
Markus Hahn wrote:
Hi there, now I sorted the languages as mentioned in the last i18n thread. It looks realy tidy now.
Hmmm. Imho the order of the languages is the same for VDR's i18n.c and for all the plugins, so shouldn't this break the i18n's of *all* plugins? Or do I miss something?
You're of course absolutely right here. I should have thought of this, too.
On long term, its probably best to move i18n out of the c source and into editable language definition files that can be loaded on runtime. (I think thats what Klaus meant with 'language files'.)
Yes, that's what I meant. But let's do this in version 1.5.x.
Klaus