Print Page - translation thingy

Title: translation thingy
Post by: Harry on October 03, 2007, 16:26:17

hi,

out of curiosity:
would i have to correct this in vompserver or in vdr?

from my log

Sep 30 21:29:10 emily vdr: [2529] vompserver: no translation found for 'VOMP client(s) connected' in language 1 (Deutsch)

from vompserver.c

Code Select

cString cPluginVompserver::Active(void)
{
  if(MVPClient::getNrClients() != 0) return tr("VOMP client(s) connected");
  return NULL;
}

Title: Re: translation thingy
Post by: davep on October 03, 2007, 17:07:28

In vdr. There is a description in PLUGINS.html. However beware the most recent 1.5.x versions of vdr have a completely rewritten i18n system - a lot of #IFDEFs and Makefile magic would be needed to support both.

Dave

Title: Re: translation thingy
Post by: Harry on October 03, 2007, 19:10:41

thanks for the hint...and...

forgive me.. it looks like this has to be fixed in vompserver:

QuoteIf a plugin displays texts to the user, it should implement internationalized versions of these texts and call the function

void RegisterI18n(const tI18nPhrase * const Phrases);

to register them with VDR's internationalization mechanism.

Code Select


harry@emily:/usr/local/src/VDR/PLUGINS/src/vompserver$ grep -i RegisterI18n *
harry@emily:/usr/local/src/VDR/PLUGINS/src/vompserver$

hmm.
am i missing something or was this left out intentionally?

cheers
Harry

Title: Re: translation thingy
Post by: davep on October 03, 2007, 20:53:52

Quote from: Harry on October 03, 2007, 19:10:41
hmm.
am i missing something or was this left out intentionally?

Almost certainly an accident ;) That's the only text message generated by the plugin which is intended to be seen by a user.

vdr 1.5.7 and later uses the gettext() mechanism to handle i18n, so RegisterI18n() is not used.

Dave

Loggytronic Forum

VOMP => VOMP General / MVP => Topic started by: Harry on October 03, 2007, 16:26:17